Date: Tue, 17 Oct 2006 00:02:53 +0200 (MEST)
From: Jan Engelhardt <jengelh@linux01.gwdg.de>
To: David Miller <davem@davemloft.net>
cc: andrew@walrond.org, linux-kernel@vger.kernel.org
Subject: Re: Sparc64 kernel message: BUG: soft lockup detected on CPU#3!
In-Reply-To: <20061016.135400.112621150.davem@davemloft.net>
Message-ID: <Pine.LNX.4.61.0610162358270.30479@yvahk01.tjqt.qr>
References: <20061016141127.GB9350@pelagius.h-e-r-e-s-y.com>
 <20061016164124.GC9350@pelagius.h-e-r-e-s-y.com> <20061016.135400.112621150.davem@davemloft.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 963
Lines: 28


>> >  [0000000000525990] prom_putchar+0x2c/0x34
>> 
>> I wonder; could this be a timeout during boot because the prom console
>> is hardware limited to 9600baud and its buffer is full ??
>
>PROM console is just slower than anything else for whatever
>reason.
>
>Even though PROM console drives the same output, using the
>native CONFIG_SERIAL_SUNHV is much faster and does not generate
>the timeouts.
>
>That's why I told the original poster to simply disable
>CONFIG_PROM_CONSOLE, it should never be used.

I have not seen this soft lockup so far, though I run a 2.6.16, most 
likely using CONFIG_PROM_CONSOLE (redirected to ttya by prom) because
the machine is not a SUN4V (which SUNHV seems to be for).


	-`J'
-- 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/