Re: 2.5.47-ac4 panic on boot.

Justin A (ja6447@albany.edu)
Fri, 15 Nov 2002 17:59:14 -0500


Ok..that worked:

for future reference...what is the important part of the oops so I don't have
to type the useless parts?

I'm guessing just the Call Trace, which is:

pnpbios_set_resources+0x7c/0x90
pnp_activate_dev+0xe6/0x114
pnp_device_probe+0x33/0xc4
bus_match+0x37/0x5c
driver_attach+0x44/0x74
bus_add_driver+0x60/0x80
driver_register+0x69/0x84
pnp_register_driver+0x29/0x48
init+0x0/0x13c
init+0x1a/0x13c
init+0x0/0x13c
kernel_thread_helper+0x5/0xc

-- 
-Justin

On Friday 15 November 2002 05:16 pm, Andrew Morton wrote: > Justin A wrote: > > .config crashes, it oopses as soon as pnp starts, then 2 seconds later > > the previous oops comes up and it panics. > > Irritating when it does that. Here's a little patch which should > stop the machine dead after the first ooops, prevent stuff from > scrolling off the screen. > > This, with the missing touch_nmi_watchdog() would be a handy > kernel boot option, perhaps. > > > --- 25/arch/i386/kernel/traps.c~noscroll Tue Nov 12 13:13:24 2002 > +++ 25-akpm/arch/i386/kernel/traps.c Tue Nov 12 13:14:16 2002 > @@ -84,7 +84,7 @@ asmlinkage void alignment_check(void); > asmlinkage void spurious_interrupt_bug(void); > asmlinkage void machine_check(void); > > -static int kstack_depth_to_print = 24; > +static int kstack_depth_to_print = 10; > > > /* > @@ -246,6 +246,9 @@ bad: > printk("%02x ", c); > } > } > + local_irq_disable(); > + for ( ; ; ) > + ; > printk("\n"); > } > > > _

- 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/