Red Hat Bugzilla – Bug 244372
Last kernel update makes X crash
Last modified: 2008-03-16 15:33:32 EDT
Description of problem:
Since last kernel update, the graphical server can't start. The boot process is
text-only and at the end a box showing that X can't start pops up.
Switching back to the previous version (2.6.20-1.2316.fc5) solves the problem.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. At grub screen choose to boot on version 2.6.20-1.2319.fc5
2. The boot is text-only
3. Instead of the login manager, a text pop up appears saying that X can't start
X doesn't start at all
The usual graphical boot process/login
Here's the backtrace in X.org server logs:
(WW) ****INVALID IO ALLOCATION**** b: 0x1800 e: 0x1807 correcting^G
*** If unresolved symbols were reported above, they might not
*** be the reason for the server aborting.
0: /usr/bin/Xorg(xf86SigHandler+0x87) [0x80b8757]
2: /usr/lib/xorg/modules/drivers/i810_drv.so [0x149b08]
3: /usr/lib/xorg/modules/drivers/i810_drv.so [0x14d512]
4: /usr/bin/Xorg(InitOutput+0x99a) [0x80a237a]
5: /usr/bin/Xorg(main+0x276) [0x806ffc6]
6: /lib/libc.so.6(__libc_start_main+0xdc) [0xbd14e4]
7: /usr/bin/Xorg(FontFileCompleteXLFD+0xb1) [0x806f511]
Adam, can you explain this message?
This is probably a kernel thing, where some PCI resources don't get claimed
properly, but why does X crash?
Fedora Core 5 and Fedora Core 6 are no longer maintained. Is this bug still
present in Fedora 7 or Fedora 8?
No, you can close the bug