Bug 67946
Summary: | kernel crashes due to invalid paging request in pte_chain_alloc | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | marc.lefranc |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Brian Brock <bbrock> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 7.3 | CC: | jonmisc |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | athlon | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-09-30 15:39:43 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
marc.lefranc
2002-07-04 16:27:02 UTC
I just upgraded to 2.4.18-5 using rhn and I'm having the same error occur whenever I try to restart the X server or do a user logout from kde. After this occurs, I need to do a reboot (ctrl-alt-del works but ctrl-alt-backspace does not). When I boot on 2.4.18-3 kernel, I don't get this problem. Additional info: Jul 14 18:10:28 syzygy kernel: Unable to handle kernel paging request at virtual address 0100001b Jul 14 18:10:28 syzygy kernel: printing eip: Jul 14 18:10:28 syzygy kernel: c0128962 Jul 14 18:10:28 syzygy kernel: *pde = 00000000 Jul 14 18:10:28 syzygy kernel: Oops: 0000 Jul 14 18:10:28 syzygy kernel: i810 parport_pc agpgart lp parport autofs 3c59x ide-scsi scsi_mod ide-cd cdrom Jul 14 18:10:28 syzygy kernel: CPU: 0 Jul 14 18:10:28 syzygy kernel: EIP: 0010:[<c0128962>] Not tainted Jul 14 18:10:28 syzygy kernel: EFLAGS: 00013246 Jul 14 18:10:28 syzygy kernel: Jul 14 18:10:28 syzygy kernel: EIP is at unlock_page [kernel] 0x2 (2.4.18-5) Jul 14 18:10:28 syzygy kernel: eax: 01000000 ebx: c161eeb0 ecx: c161eeb0 edx: 00000000 Jul 14 18:10:28 syzygy kernel: esi: dbfb0000 edi: dec9f800 ebp: 00000000 esp: ddde1ee4 Jul 14 18:10:28 syzygy kernel: ds: 0018 es: 0018 ss: 0018 Jul 14 18:10:28 syzygy kernel: Process X (pid: 1094, stackpage=ddde1000) Jul 14 18:10:28 syzygy kernel: Stack: c161eeb0 dbfb0000 e09a2953 c161eeb0 ddb98160 ddb47000 e09a29af dec9f800 Jul 14 18:10:28 syzygy kernel: dbfb0000 00000000 bffffce0 ddde1f60 e09a2f0c dec9f800 dec9f800 00000002 Jul 14 18:10:28 syzygy kernel: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Jul 14 18:10:28 syzygy kernel: Call Trace: [<e09a2953>] i810_free_page [i810] 0x33 Jul 14 18:10:28 syzygy kernel: [<e09a29af>] i810_dma_cleanup [i810] 0x3f Jul 14 18:10:28 syzygy kernel: [<e09a2f0c>] i810_dma_init [i810] 0xac Jul 14 18:10:28 syzygy kernel: [<e099e924>] i810_ioctl [i810] 0xe4 Jul 14 18:10:28 syzygy kernel: [<c0145c47>] sys_ioctl [kernel] 0x217 Jul 14 18:10:28 syzygy kernel: [<c0109e1c>] do_IRQ [kernel] 0x9c Jul 14 18:10:28 syzygy kernel: [<c0108913>] system_call [kernel] 0x33 Jul 14 18:10:28 syzygy kernel: Jul 14 18:10:28 syzygy kernel: Jul 14 18:10:28 syzygy kernel: Code: 0f b6 50 1b 8b 1c 95 2c 55 33 c0 89 c2 69 d2 01 00 37 9e 8b Jul 14 18:10:29 syzygy kdm[1126]: IO Error in XOpenDisplay Jul 14 18:10:29 syzygy kdm[1084]: Display :0 cannot be opened Jul 14 18:10:31 syzygy kdm[1128]: IO Error in XOpenDisplay Jul 14 18:10:31 syzygy kdm[1084]: Display :0 cannot be opened Jul 14 18:10:32 syzygy kdm[1130]: IO Error in XOpenDisplay Jul 14 18:10:32 syzygy kdm[1084]: Display :0 cannot be opened Jul 14 18:10:34 syzygy kdm[1132]: IO Error in XOpenDisplay Jul 14 18:10:34 syzygy kdm[1084]: Display :0 cannot be opened Jul 14 18:10:34 syzygy kdm[1084]: Display :0 is being disabled (restarting too fast) ... [additional duplicates of messages above are removed] ... Jul 14 18:12:08 syzygy init: Id "x" respawning too fast: disabled for 5 minutes cheyspam: that is a different bug and actually fixed in http://people.redhat.com/arjanv/testkernels 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/ |