fc7t4 updates hangs laptop

Franky Van Liedekerke liedekef at telenet.be
Sat May 12 12:46:03 UTC 2007


On Sat, 12 May 2007 13:52:36 +0200
Franky Van Liedekerke <liedekef at telenet.be> wrote:

> Hi,
> 
> I booted my laptop from the f7t4 live CD and this worked just fine for
> me. I then installed it to my hard drive, again without issues (nice
> work, btw)
> Rebooting the PC, and everything was just fine. But then pup came on,
> telling me about 40 updates were available (just one hour before I
> wrote this). So me, being a good user, clicked on ok when asked for
> installing these. Now after the updates where finished, I needed to
> reboot my machine (new kernel). Now it seems the newly installed
> kernel (kernel.i686 2.6.21-1.3116.fc7) isn't working too good, since
> it blocked my pc everytime after finishing starting up (really
> freezes: my shift lock and numlock leds are blinking and the rest is
> all freezed up). The old kernel is still fine though
> (2.6.20-1.3104.fc7). Anybody else with this kind of problem? Any idea
> how to debug this?
> 
> Franky
> 

some more info:
I just managed to switch to text console just before the crash, and
these are the last lines that popped up:

BUG: warning at drivers/input/serio/i8042.c:831/i8042_panic_blink() not
tainted

I then added i8042.panicblink=0 to the kernel startup line, and then
the real error appeared. These are the lines visible on the console:

Code: 00 00 8b 4d bc c7 04 24 bb b9 9b e0 89 44 24 0c 89 54 24 08 89 4c
24 04 e8
 ba e0 a6 df e9 8f 01 00 00 89 5d d4 83 7b 64 00 74 04 <0f> 0b eb fe 8b
45 d8 83
 e8 04 89 45 d0 03 83 a8 00 00 00 89 83
EIP: [<e09b9ebd>] sis900_interrupt+0x1f4/0x5d7 [sis900] SS:ESP
0068:c079ff70
Kernel panic - not syncing: Fatal exception in interrupt
BUG: warning at kernel/panic.c:137/panic() (Not tainted)
 [<c04061e9>] show_trace_log_lvl+0x1a/0x2f
 [<c04067ad>] show_trace+0x12/0x14
 [<c0406831>] dump_stack+0x16/0x18
 [<c0427574>] panic+0x185/0x195
 [<c0406737>] die+0x20d/0x242
 [<c061695f>] do_trap+0x79/0x91
 [<c0406bfa>] do_invalid_op+0x97/0xa1
 [<c0416734>] error_code+0x7c/0x84
 [<c0458b6e>] handle_IRQ_event+0x1a/0x46
 [<c045a07b>] handle_level_irq+0x90/0xd9
 [<c0407540>] do_IRQ+0xb1/0xd9

Any tips?

Franky


Franky




More information about the fedora-test-list mailing list