Bug 37503
Summary: | [lmsensors] Unresponsive system after "kernel BUG at memory.c:358!" | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Nitin Dahyabhai <nitind> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED ERRATA | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | CC: | alan |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-06-09 17:09:05 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
Nitin Dahyabhai
2001-04-25 03:20:30 UTC
The machine runs fine if you don't have the lmsensors module loaded ? No, I haven't been able to reproduce that exact error. I ran into the following two errors while trying to reproduce it, but I suspect a partially hardware related cause at this point. Unable to handle kernel paging request at virtual address 7564705d printing eip: c01339b8 pgd entry cf86a754: 0000000000000000 pmd entry cf86a754: 0000000000000000 ... pmd not present! Oops: 0000 CPU: 0 EIP: 0010:[<c01339b8>] EFLAGS: 00010206 eax: 75646f6d ebx: d5b831a0 ecx: cfbc0320 edx: 00001000 esi: 00001000 edi: 00000000 ebp: 00001000 esp: cf86df90 ds: 0018 es: 0018 ss: 0018 Process cc1 (pid: 4280, stackpage=cf86d000) Stack: cf86dfbc dea5f640 cfb28000 dea5f640 cf86c000 00000000 cf86c000 00000006 cf86c000 401508e0 4015e000 bfffe648 c010901b 00000000 4015e000 00001000 401508e0 4015e000 bfffe648 00000003 0000002b 0000002b 00000003 40101f44 Call Trace: [<c010901b>] Code: f6 80 f0 00 00 00 01 74 0a 6a 01 50 e8 c7 50 01 00 5f 5d 89 kernel BUG at page_alloc.c:90! invalid operand: 0000 CPU: 0 EIP: 0010:[<c012d0ea>] EFLAGS: 00010282 eax: 0000001f ebx: 00000000 ecx: 00000005 edx: 00000000 esi: 00000000 edi: c10cc384 ebp: 00000000 esp: ce1b3ea8 ds: 0018 es: 0018 ss: 0018 Process rm (pid: 23050, stackpage=ce1b3000) Stack: c020ea7b c020ec89 0000005a c10cc384 c0135b93 c10cc384 00000000 c10cc384 c10cc384 c10cc384 c10cc384 00000000 c0124d6c c10cc384 00000000 c19e3a00 c285b1a0 000001a0 c285b00c ce1b3f0c cc913108 00000000 bfffed68 c0124e2d Call Trace: [<c020ea7b>] [<c020ec89>] [<c0135b93>] [<c0124d6c>] [<c0124e2d>] [<c 0147b57>] [<c0158b4f>] [<c0158b61>] [<c014643c>] [<c013fb6c>] [<c013fc39>] [<c010901b>] Code: 0f 0b 83 c4 0c 8b 47 18 83 e0 20 74 16 6a 5c 68 89 ec 20 c0 Closing. Seems to match the VIA chipset flaw that 2.4.9 and later work around. If it stil occurs feel free to re-open |