From: Justin A <ja6447@albany.edu>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.47-ac4 panic on boot.
Date: Fri, 15 Nov 2002 17:59:14 -0500 [thread overview]
Message-ID: <200211151759.14830.ja6447@albany.edu> (raw)
In-Reply-To: <3DD5723E.CED7AE1A@digeo.com>
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");
> }
>
>
> _
next prev parent reply other threads:[~2002-11-15 22:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-15 5:59 2.5.47-ac4 panic on boot Justin A
2002-11-15 6:33 ` Andrew Morton
2002-11-15 7:54 ` Justin A
2002-11-15 8:28 ` Andrew Morton
2002-11-15 22:12 ` Justin A
2002-11-15 22:16 ` Andrew Morton
2002-11-15 22:59 ` Justin A [this message]
2002-11-15 22:02 ` Samuli Suonpaa
2002-11-15 22:36 ` Justin A
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200211151759.14830.ja6447@albany.edu \
--to=ja6447@albany.edu \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox