Bug 89531
Summary: | intermittent kernel oops on PIII | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Jason Vasquez <jason> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-09-30 15:40:50 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jason Vasquez
2003-04-23 20:37:39 UTC
hmmm this sounds like memory corruption or bad memory on first sight.... is there a way you can run memtest86 to test the ram ? That was my first thought as well...I let memtest86 run through 2 complete runs with 0 errors -- I can rerun again for a longer period if it seems worthwhile. I just let memtest86 run for 8 hours with 0 errors. Any other ideas? Please let me know if any other info would be helpful. Thanks, Jason FYI, I have updated to kernel 2.4.21-rc1-ac1 (non-RPM). The machine has been up 6 days now with zero kernel Oops'. (I had been seeing them previously within 24-36 hours of each other). I will continue to monitor and update this report, but things seem to be better at this point... Thanks thats good info - it implies whatever was corrupting something was a kernel bug, and better yet its fixed 8) For whatever it's worth, I have a duron based machine that's having a similar trap (regularly). It's running an uptodate redhat 9 system, with exim and inn added. Here's the trap I'm getting: > Unable to handle kernel NULL pointer dereference at virtual address > 00000074 > printing eip: > c01418c0 > *pde = 00000000 > Oops: 0000 > parport_pc lp parport nfsd lockd sunrpc autofs ppp_deflate zlib_deflate > ppp_async ppp_generic slhc 8139too mii iptable_mangle ipt_MASQUERADE > ipt_REDIRECT ipta > CPU: 0 > EIP: 0060:[<c01418c0>] Not tainted > EFLAGS: 00010202 > > EIP is at page_referenced [kernel] 0x210 (2.4.20-18.9) > eax: c1000030 ebx: 00000200 ecx: 00000000 edx: 00000001 > esi: 00000000 edi: c1b31b00 ebp: 0000000e esp: cf771f84 > ds: 0068 es: 0068 ss: 0068 > Process kscand/Normal (pid: 7, stackpage=cf771000) > Stack: cf393bc0 00000000 00000002 cf771fb4 c135b938 c135b938 c030900c > c135b98c > 00000003 c013a644 cf770000 c0125460 00000001 00000003 cf770000 > c0308f00 > cf770000 c013b484 c0308f00 00000003 00000001 c025ab4c 000009c4 > c013b3d0 > Call Trace: [<c013a644>] scan_active_list [kernel] 0x34 (0xcf771fa8)) > [<c0125460>] process_timeout [kernel] 0x0 (0xcf771fb0)) > [<c013b484>] kscand [kernel] 0xb4 (0xcf771fc8)) > [<c013b3d0>] kscand [kernel] 0x0 (0xcf771fe0)) > [<c010727d>] kernel_thread_helper [kernel] 0x5 (0xcf771ff0)) > > > Code: 8b 41 74 39 41 60 0f 43 54 24 04 45 4e 89 54 24 04 0f 89 3e Feel free to contact me if I can be of assistance. I'm building a standard 2.4.21 kernel that I'll install as soon as I get the RPM built to see if I continue to get the problem. It started the last time I upgraded the kernel kernel-2.4.20-18.9 I believe. It happened once, then waited a week to happen again, the frequency has increased since then, now it's happening several times a day. Jay Thanks for the bug report. However, Red Hat no longer maintains this version of the product. Please upgrade to the latest version and open a new bug if the problem persists. The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, and if you believe this bug is interesting to them, please report the problem in the bug tracker at: http://bugzilla.fedora.us/ |