Skip to contentSkip to conversation

PROBLEM: 2.4.4 oops, will not boot

DISCUSSION Gordon Sadler 1 participant 1 message May 3, 2001 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw
Quoted 20 lines · Andrew Morton
Quoted 19 lines · Gordon Sadler
Quoted 7 lines · Andrew Morton
Quoted 5 lines · Gordon Sadler

Please CC on replies.
Attached is REPORTING-BUGS template from source, and a hand copied oops that I ran through ksymoops. I really hope this is resolved, anything further needed, just ask.

Quoted 8 lines

Unfortunately the ksymoops output doesn't show the call trace. Can you please try again? A reproducable oops is, err, rather important. The syntax to feed into ksymoops is

Call Trace: [<c0111234>] [<c0123456>] ...

Thanks.

Right, I see the problem now.. s/Calltrace/Call Trace/

Quoted 8 lines
Quoted 1 line

Reran oops through ksymoops with change to Call Trace, output attached.

Ugh. Something seems to have corrupted your slab cache data structures, so this will be real hard to pin down.

You could try setting DEBUG to 1 in mm/slab.c, see if that catches the culprit.

As requested.. changed config in one way, removed nvidia framebuffer/replaced with vesa fb. After changeing DEBUG -> 1 in mm/slab.c it produced 3 EIPs. I rebooted to 2.2.19, copied by hand, and ran through ksymoops. The attached tar is the .config, hand copy of 3 EIPs, and the ouput from ksymoops.

HTH

Gordon Sadler