Summary: | kernel 2.6.9-gentoo-r1 oops at boot time | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | John Robinson <john.robinson+bug.gentoo.org> |
Component: | [OLD] Core system | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
My .config
The .config I used for 2.6.9-r1 Here's one that works |
Description
John Robinson
2004-10-25 06:03:15 UTC
Created attachment 42556 [details]
My .config
Please try gentoo-dev-sources-2.6.9-r1 OK, have done. It crashes again, even earlier in the boot sequence, almost instantly after init starts - I didn't notice any green and blue for the "Gentoo Linux" banner fly past. This time I get what must be a stack trace, and unless you desperately need them, I'll skip the [<xxxxxxxx>] bits... bad: scheduling while atomic! [<c02ef6bd>] schedule+0x47d/0x490 [<c0xxxxxx>] file_read_actor+0x106/0x120 [<c0xxxxxx>] sys_sched_yield+0x50/0x70 [<c0xxxxxx>] coredump_wait+0x36/0xa0 [<c0xxxxxx>] do_coredump+0xe1/0x1cd [<c0xxxxxx>] __dequeue_signal+0xf5/0x1b0 [<c0xxxxxx>] dequeue_signal+0x35/0xa0 [<c0xxxxxx>] get_signal_to_deliver+0x1f2/0x2f0 [<c0xxxxxx>] do_signal+0x9b/0x130 [<c0xxxxxx>] dput+0x195/0x1a0 [<c0xxxxxx>] __fpy+0x105/0x170 [<c0xxxxxx>] filp_close+0x59/0x90 [<c0xxxxxx>] do_page_fault+0x0/0x5f0 [<c0xxxxxx>] do_notify_resume+0x37/0x40 [<c0xxxxxx>] work_notifysig+0x13/0x15 ======================== [<c0xxxxxx>] it_real_fn+0x0/0x60 [<c0xxxxxx>] schedule+0x294/0x490 [<c0xxxxxx>] it_real_fn+0x0/0x60 [<c0xxxxxx>] schedule+0x294/0x490 [<c0xxxxxx>] it_real_fn+0x0/0x60 [<c0xxxxxx>] schedule+0x294/0x490 Kernel panic - not syncing: Aiee, killing interrupt handler! To make this kernel config originally, I just started from fresh, i.e. as soon as I'd run `emerge gentoo-dev-sources` I used `make menuconfig` and picked all the likely-looking options for my system. To try 2.6.9-r1 I copied the .config into the new source directory, and ran `make oldconfig`, and took the offered default for the extra options (except a new iptables connection tracking module where I said 'M' rather than 'N'). Created attachment 42585 [details]
The .config I used for 2.6.9-r1
Created attachment 42588 [details]
Here's one that works
This is a completely different .config; I started with the config from the
2.6.8-r9 kernel on the 2004.3-test1 LiveCD, and switched off lots of things I
don't have. Both the version I used on the 2.6.8-r10 sources and this version I
used with the 2.6.9-r1 sources boot fine, but I'd still like to know what
caused the crashes (and if possible help fix it); I'm not happy with this
current config but will make do for now.
Sorry, where I wrote __fpy in the stack trace above I meant __fput. I just tried the broken kernel again, and got a few more lines of the trace; interpret this as appearing before the one I typed in earlier: [<c0106007>] syscall_call+0x7/0xb ======================= [<c0xxxxxx>] it_real_fn+0x0/0x60 [<c0xxxxxx>] schedule+0x294/0x490 I can't immediately tell from the oops which config option is causing the problem. It's really up to you to adapt your config in small steps to narrow down the bug. You may also wish to do this on 2.6.10-rc1 incase the problem has been fixed already. Please reopen if you manage to track this down. |