Summary: | run_posix_cpu_timers general protection fault | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Rick <rbunke> |
Component: | [OLD] Core system | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
Status: | RESOLVED CANTFIX | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Rick
2006-09-16 09:47:53 UTC
Your kernel is tainted. Please reproduce this on a session where the closed-source nvidia module is not loaded (and has not been loaded during the current boot). it changed somewhat this time: I unloaded the nvidia module got an oops but the kernel was still tainted because madwifi drivers have a precompiled portion in order stop people from fiddling with settings that might violate fcc regulations. So I unloaded atheros modules and got it to produce this oops: Unable to handle kernel NULL pointer dereference at 0000000000000000 RIP: <ffffffff80279b65>{elf_core_dump+2325} PGD 25805067 PUD 36416067 PMD 0 Oops: 0002 [1] CPU 0 Modules linked in: it87 hwmon_vid eeprom 12c_isa uhci_hcd quickcam ohci_hcd Pid: 0, comm: swapper Not Tainted 2.6.17-gento-r8 #2 RIP: 0010:[<ffffffff80279b65>] <ffffffff80279b65>{elf_core_dump+2325} RSP: 0018:ffffffff8076bfa8 EFLAGS: 0010046 RAX: 0000000000000000 RBX: ffffffff8080def8 RCX: ffff81003ff80d5f RDX: 0000000000000000 RSI: 0000000000000002 RDI: ffffffff80773298 RBP: 0000000008e00000 R08: ffffffff8080c000 R09: 0000000000000004 R10: ffff81003fbd77c0 R11: 0000000000000025 R12: 0000000000000000 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 FS: 00002b8c31481d80(0000) GS:ffffffff80805000(0000) knIGS:0000000000000000 CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b CR2: 0000000000000000 CR3: 0000000029d71000 CR4: 00000000000006e0 Process swapper (pid: 0, threadinfo ffffffff8080c000, task ffffffff8066a2e0) Stack: ffffffff80268be0 ffffffff8025ecf2 ffffffff8080def8 <EOI> ffff81003e56f540 ffffffff8066a2e0 000000749e1e5911 000000000000000a ffffffff805ed4fd ffffffff80260f1f 0000000000000025 Call Trace: <IRQ> <ffffffff80268be0>{default_idle+0} <ffffffff8025ecf2>{apic_timer_interrupt+98} <EOI> <ffffffff80260f1f>{thread_return+0} <ffffffff80268c0a>{default_idle+42} <ffffffff80248ced>{cpu_idle+61} <ffffffff8080f84f>{start_kernel+495} <ffffffff8080f255>{_sinittext+597} Code: 00 00 00 65 48 8b 04 25 00 00 00 00 48 39 c7 75 35 48 8b 47 RIP <ffffffff80279b65>{elf_core_dump+2325} RSP <ffffffff8076bfa8> CR2: 0000000000000000 <0>Kernel panic - not syncing: Attempted to kill the idle task! the comm is still swapper, but now it gives a null pointer error in elf_core_dump. This really smells like a hardware problem to me. In the last trace you posted the error actually occurred in elf_core_dump - this function is only called when a userspace process crashed. So it looks like not only did some program crash, the kernel then crashed trying to deal with the crash! To certain extent I agree with your essement. I had kernel stability problems in the past while running gentoo on this system so I ran Suse for a few weeks on the same machine and it didn't seem to have trouble. With Suse I couldn't get software configured the way I wanted it, with out recompiling many packages myself, so I switched back to gentoo. Perhaps they have more conservative settings, or some things are disabled in their kernel that I enable in my kernel. I've checked the ram with memtest on the livecd and all seems ok there. Since the comm is always swapper do you think it might be a problem with the drive my swap file is on? Or is it impossable to tell from a kernel oops where trouble might lay in the hardware? any suggestions or ideas? I'll troubleshoot from a hardware perspective, remove un-nescarry drives, cards, and make sure there are safe defaults set in bios etc. to see if I can't discover a hardware issue. I ended up replacing the hardware and my new box is stable, so it nust have been a hardware issue. |