[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Kernel oops when rebooting U2



Hi!

I just upgraded one of my boxen from an U1 to an U2 (swapped the disk, 
 to be frank), and it appeared to work fine for a couple hours. The U2
 has worked fine whilst I had it on my desk for testing, with both
 normal and SMP kernels.

Now I wanted to reboot it, and:

Linux newka 2.4.27-3-sparc64 #1 Fri Jun 2 07:35:41 UTC 2006 sparc64 GNU/Linux
...
INIT: Sendzs_open tts/%d0, tty overwrite.
zs_open tts/%d0, tty overwrite.
<repeat 18 times>

I waited a minute or two with nothing happening, then hit enter on the
 serial console:

Unable to handle kernel NULL pointer dereference
tsk->{mm,active_mm}->context = 0000000000000682
tsk->{mm,active_mm}->pgd = fffff80031e39000
              \|/ ____ \|/
              "@'/ .. \`@"
              /_| \__/ |_\
                 \__U_/
swapper(0): Oops
TSTATE: 0000004480f09606 TPC: 0000000000515fa0 TNPC: 0000000000515f50 Y: fffdfdd
g0: 0000000000000000 g1: 0000000000000000 g2: 0000000000000000 g3: 000000000000d
g4: fffff80000000000 g5: 0000000000000000 g6: 0000000000414000 g7: 0000000000670
o0: 0000000000000007 o1: 0000000000000001 o2: fffff80042393e58 o3: 0000000000004
o4: 00000000006c3000 o5: 0000000000000001 sp: 0000000000417211 ret_pc: 000000004
l0: fffff80060ad4000 l1: 0000000000000001 l2: 0000000000000018 l3: 0000000000001
l4: 0000000000000020 l5: 0000000000000000 l6: 00000000004dad04 l7: 00000000703bc
i0: fffff800000000c0 i1: 0000000000417d10 i2: 00000000006c5800 i3: 0000000000001
i4: 00000000000202d5 i5: 0000000000000001 i6: 00000000004172d1 i7: 0000000000510
Caller[0000000000516270]
Caller[000000000041ee04]
Caller[0000000000408994]
Caller[000000000041a544]
Caller[000000000063e6f4]
Caller[0000000000404678]
Caller[0000000000000000]
Instruction DUMP: 106fffee  84102002  106fffed <c0284000> 7fffff47  81e80000  7
Kernel panic: Aiee, killing interrupt handler!
In interrupt handler - not syncing
 Press L1-A to return to the boot prom

Needless to say, it doesn't react in any way to breaks on the serial 
 console. (And to add insult to injury, the box is in colo, and can't be 
 powercycled until tomorrow.)

Any hints on what a) the "tty overwrite"s mean, and b) how I can avoid 
 this oops in the future? Being able to reboot would be a nice 
 feature...

(Please honour the Reply-To, my subscribed address has its MX on the 
 box in question)

cheers+tia,
&rw
-- 
-- Remember, Murphy was an optimist.
--                  Peter van Hooft


Attachment: pgp7gkTRH8rNH.pgp
Description: PGP signature


Reply to: