Summary: | kernel panic in booting mm-sources 2.6.0-test5-mm4 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | FRLinux <frlinux> |
Component: | [OLD] Core system | Assignee: | x86-kernel (DEPRECATED) <x86-kernel> |
Status: | RESOLVED WONTFIX | ||
Severity: | major | CC: | tseng |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | config file for 26-test5-mm4 |
Description
FRLinux
2003-09-24 06:33:16 UTC
Created attachment 18261 [details]
config file for 26-test5-mm4
Please add the kernel OOPS, and stick it through ksymoops *on the faulty kernel* so we can see if anything Gentoo-related is to blame. If we can't really see anything Gentoo-related, we'll have to close this bug as INVALID as this is an upstream problem. if this patch fixes it then it's a known issue: http://kernel.lpbproductions.com/2.6/mm/2.6.0-test5-mm4-devfsd-fix I recompiled the new kernel with ksym and emerged ksymoops from portage but it refers to a *running* kernel whereas mine dies before completing the boot. Steph PS = patch was already applied to my kernel. Essentially, we need a stack trace, one way or another. It might come with one already if you enabled the symbols during compilation [if so, can you write them down or something and send them over to us] or you can scour around the ksymoops and see if you can salvage the data somehow. Thanks. Are you using mm-sources from the ebuild in portage? I have already included that patch that should fix this bug. If not, I don't see this as being a Gentoo bug at all. If so, lets try and find out why the patch doesnt fix the issue in your case. Thx, Brandon * ping * Ouch sorry for the *lag* i thought i actually had replied to you. All revisions on the kernel like test{6,7,8,9}-mmX work fine, so i think i'll close it. Steph |