This may be the most worthless bug report ever filed, but maybe someone
else is seeing this that can shed some light on the matter. Everything
was rock-solid with -rc3, but I've had two panics with -rc5 in as many
days. The first occurred within five minutes of booting. The second
was after nearly 48 hours of uptime. Nothing is getting written to
syslog, and the second panic happened while X11 was active, so I didn't
even get so much as a stack dump on the console -- just the flashing
keyboard leds that signaled entry into "brick emulation" mode :-(.
System is a k6-III/450 w/SCSI drives (AIC7XXX) and a Netgear FA311 NIC.
At this point, I have no idea what's triggering the panics. Doesn't
seem related to load that I can tell...
--
------------------------------------------------------------------------
Bob Tracy | "They couldn't hit an elephant at this dist- "
[email protected] | - Last words of Union General John Sedgwick,
| Battle of Spotsylvania Court House, U.S. Civil War
------------------------------------------------------------------------
FWIW, I was running 2.6.23-rc5 on my laptop (along with iwlwifi-0.1.14
for wireless) and I saw the same symptom: panic (blinking capslock)
while in X. I saw one panic out of maybe 12 hours of uptime over a
few reboots. The same system is quite stable with the stock Ubuntu
2.6.22 kernel.
My laptop is a Thinkpad X60s (core duo) so quite a different system.
I'm traveling at the moment so I probably won't be able to gather much
debugging info until next week.
- R.
On Wed, 5 Sep 2007, Roland Dreier wrote:
> FWIW, I was running 2.6.23-rc5 on my laptop (along with iwlwifi-0.1.14
> for wireless) and I saw the same symptom: panic (blinking capslock)
> while in X. I saw one panic out of maybe 12 hours of uptime over a
> few reboots. The same system is quite stable with the stock Ubuntu
> 2.6.22 kernel.
>
> My laptop is a Thinkpad X60s (core duo) so quite a different system.
>
> I'm traveling at the moment so I probably won't be able to gather much
> debugging info until next week.
-rc5 users should apply commit 5c127c58ae9bf196d787815b1bd6b0aec5aee816
(or else just move to latest -git).
[email protected] (Bob Tracy) writes:
> This may be the most worthless bug report ever filed, but maybe someone
> else is seeing this that can shed some light on the matter. Everything
> was rock-solid with -rc3, but I've had two panics with -rc5 in as many
> days. The first occurred within five minutes of booting. The second
> was after nearly 48 hours of uptime. Nothing is getting written to
> syslog, and the second panic happened while X11 was active, so I didn't
> even get so much as a stack dump on the console -- just the flashing
> keyboard leds that signaled entry into "brick emulation" mode :-(.
If you have a second machine on the network could you perhaps
set up netconsole (see Documentation/networking/netconsole.txt) and see
if it catches something?
-Andi
Satyam Sharma wrote:
> -rc5 users should apply commit 5c127c58ae9bf196d787815b1bd6b0aec5aee816
> (or else just move to latest -git).
I applied the small "net/ipv4/tcp_input.c" patch, and that seems to have
done the trick. Thanks for the pointer to the fix!
--
------------------------------------------------------------------------
Bob Tracy | "They couldn't hit an elephant at this dist- "
[email protected] | - Last words of Union General John Sedgwick,
| Battle of Spotsylvania Court House, U.S. Civil War
------------------------------------------------------------------------