Bug 98318
Summary: | [x86_64] Reproducible oops caused by useradd. | ||
---|---|---|---|
Product: | [Retired] Red Hat Raw Hide | Reporter: | Aleksey Nogin <aleksey> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED NOTABUG | QA Contact: | Brian Brock <bbrock> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 1.0 | CC: | jyh |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-03-11 07:59: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
Aleksey Nogin
2003-06-30 23:56:55 UTC
Just saw syslogd trip over the same thing: Unable to handle kernel paging request at virtual address ffffffffffffffff printing rip: ffffffff80163ac6 PML4 103027 PGD 2067 PMD 0 Oops: 0002 CPU 0 Pid: 408, comm: syslogd Not tainted RIP: 0010:[<ffffffff80163ac6>]{__pollwait+166} RSP: 0018:00000103fe30de18 EFLAGS: 00010206 RAX: 000000000000002f RBX: 00000103dfff4000 RCX: ffffffffffffffff RDX: 00000103dfff4000 RSI: 00000000003deff4 RDI: 0000010000019168 RBP: 00000100dff709e0 R08: 0000010000019198 R09: 00000100164ffc28 R10: 0000000000000001 R11: 0000000000000000 R12: 00000103fe30de98 R13: 00000103fdec0288 R14: 0000000000000001 R15: 0000000000000145 FS: 000000000050e280(0000) GS:ffffffff804cf600(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: ffffffffffffffff CR3: 0000000000101000 CR4: 00000000000006e0 Call Trace: [<ffffffff80163a6a>]{__pollwait+74} [<ffffffff802313c8>]{datagram_poll+24} [<ffffffff8022b36d>]{sock_poll+29} [<ffffffff80163d3f>]{do_select+351} [<ffffffff8016426b>]{sys_select+971} [<ffffffff8010f0d3>]{system_call+119} Process syslogd (pid: 408, stackpage=103fe30d000) Stack: 00000103fe30de18 0000000000000018 ffffffff80163a6a 00000103fdec66a8 00000103fdfbc880 00000100dff709e0 0000000000000000 00000103fe30df18 ffffffff802313c8 0000000000000000 ffffffff8022b36d 0000000000000000 ffffffff80163d3f 0000000000000000 7fffffffffffffff 0000000000000002 00000103fe30de98 00000103fe30df10 0000000100000246 0000000000000000 00000103dfff4000 00000000004055d3 0000000000000000 0000000000000008 0000000000000000 0000007fbffff200 00000103fdec66a8 0000000000000001 ffffffff8016426b 00000000004055e3 0000000000000001 00000008fe30de78 0000000000000000 0000000000000000 7fffffffffffffff 00000103fdec66a8 00000103fdec66b0 00000103fdec66b8 00000103fdec66c0 00000103fdec66c8 Call Trace: [<ffffffff80163a6a>]{__pollwait+74} [<ffffffff802313c8>]{datagram_poll+24} [<ffffffff8022b36d>]{sock_poll+29} [<ffffffff80163d3f>]{do_select+351} [<ffffffff8016426b>]{sys_select+971} [<ffffffff8010f0d3>]{system_call+119} Code: 48 89 29 4c 89 69 28 48 8d 71 08 65 48 8b 04 25 18 00 00 00 Turned out that this machine had a buggy BIOS and problems have disappeared after a BIOS upgrade. |