Red Hat Bugzilla – Bug 233843
Kernel Lockup after successful boot.
Last modified: 2018-04-11 08:45:56 EDT
Description of problem:
Kernel 2933 and x windows clash with full system lockup
Version-Release number of selected component (if applicable):
yum install kernel
Steps to Reproduce:
1. Boot system with new kernel
System shows the boot process in the same way as the previous kernel boots.
I see line by line following udev
Then when the gnome switch is attempted, only a black screen is present with a
locked keyboard (no lights) or mouse activity possible.
I expected this to work the same as the previous version. 2798. (system was
rebuilt just to prove point. I spent 12 hours trying to debug this and a
This is a x-windows and kernel conflict when the device is a i810 mother board.
I will try again with the default x config setup driver set to vesa. If there is
a change, I will repost.
Intel video bios is dated march 2007. Mother board is a intel 945gnt, with the
Video build 1374 PC 14.12 08/28/2006 at 16:30.16
Following further hours of boot / reboots, the problem is the incompatibilty
between my standard intel mother board, (which works for every other fedora
kernel version), the most recent mouse driver for x (2 minute to detect) and
I have reported this as a x-windows problem, but it may very well be a kernel
I on my dual core system is here to help.
My system. Intel d945gnt mother board, processors d930, 1 gig memory, sata boot
Please attempt to resolve. I know that fc7 live cd works just fine on my system.
Thanks for the bug report. We have reviewed the information you have provided
above, and there is some additional information we require that will be helpful
in our diagnosis of this issue.
Please attach your X server config file (/etc/X11/xorg.conf) and X server log
file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file
attachments using the bugzilla file attachment link below.
Could you please also try to run without any /etc/X11/xorg.conf whatsoever and
let X11 autodetect your display and video card? Attach to this bug
/var/log/Xorg.0.log from this attempt as well, please.
We will review this issue again once you've had a chance to attach this information.
Thanks in advance.
Also, please indicate whether this issue occurs when not using the Xen kernel.
I did all, as you requested, prior to writing this entry.
As you know, in Fc6, we can hit the icon during boot or the enter key during the
boot process and watch lines following udev present their list of messages
followed by ...[OK]
The process is 100 percent error free, until the logon screen is presented.
Then poof, no keyboard lights, no mouse, and no graceful shutdown via the
momentary press of the poweroff key. It did not work with vesa being
substituted, it did not work without xorg.conf and essentially, I just did a
rollback to the previous kernel, which works just fine.
I am writing this from work, and will send the xorg.conf file tonight. Please
refer to the other bug report concerning x-windows, that I filed last November
and which was not answered.
The reason I did not pursue it, is that I did the exclude=*xorg* in yum.conf, so
my system was stable. And it was until I thought that I could remove the
exclude. What a mistake....
FYI, My pc has two Fedora installations on separate hard disks. I wiped out one
FC6 and have installed FC7 (Rawhide). No problems there with rawhide test2
release, but the kernel upgrade with Rawhide locks up during the boot process at
the initialisation of ip tables. Again, this note is a an aside for Rawhide.
X-windows in Rawhide works fine... bizzare ehh.
I will backup my /usr/bin fully and any other path before I remove the exclude
files. Just want to resolve the X-Windows Kernel bug problem.
Files will be sent to you tonight (Montreal time).
Since Fedora is a serious hobby for me, my wife was a little upset at the time I
invested, but, since I am addicted to linux, instead of bars and women, it was
my comprimise message to her.
Created attachment 150980 [details]
Xorg.conf file as requested
File 1 of three
Created attachment 150981 [details]
xorg log file
One before and one more to come
Created attachment 150983 [details]
I will install the Xen update, and advise of my experience with the indicated
There is -rws--x--x 1 root root 1820676 Mar 15 22:18 Xorg that I have found,
and this version does not appear to crash my system.
Tomorrow, March 29th is FC7 test3 release day. I had planned to install it. I
will delay doing that if you would like me to retain the problem linux system
Fc7 xen is not a priority, except that it appears to run well on my system
I am adding this note to the bug. I am planning an install of Fc7 onto my
systems second hard disk. (my desktop has 2 hard disks). The primary one has the
latest 2933 kernels (xen and non xen). Both cause lockup beginning at the time
the logon prompt is offered. An earlier version of xen (2911) would lock up
randomly, and occassionally with mouse scrolling. Where is the problem and why
does the vanilla fc6 release not have these problems?
If you do not require my preserving the system for some patch tests, please
advise. I would like to help you (and of course it helps me) to have a stable
Leslie in Montreal Canada
I posted this on linuxquestions.org as more users of Fedora are on it then
review the bug list.
This bug pertains to FC6 and FC7 with full X updates. I have an intel
motherboard with the built-in i810 video. With the non-Xen version of either
linux version, I can boot and run as one expects. When I select the XEN version
of linux. the system boots, (I can watch it) and when it arrives to presenting
the logon prompt, there is a hard freeze. Sometimes I get the logo from the
Intel bios, indicating that the system crashed into the bios; sometimes, it is
dead, no mouse activity, no keyboard lights or keyboard operation. Even the
power switch is disabled. (It takes a hard reset to restart).
The non-Xen versions appear to work fine.
And I am experiencing three problems with FC7 and Gnome, perhaps again due to X.
The second problem is random. If Evolution crashes, a restart is ok, but then
randomly, Gnome appears to fail. When it does, I can open menus, but clicking to
start a program does not work. ctl-alt-backspace restarts Gnome, but it remains
broken (unable to logon via ctl-alt-f1 too).
Another quirky thing, is that randomly, Gnome will fail as above, but then the
icons on the desktop start to disappear as I try to click on them or slide a
window over one. I can then and do end up with a clean desktop. Since the mouse
and keyboard are active, the power-off button does signal a shutdown.
Until these bugs get patches I will keep Fc6 for a reference (backup) only. Re
Fc7, I will not have to wait to May 24th for the official release. I like it.
I have sent logs, and I can work with your maintainer to test any patch. What is
good for my configuration is also good for certain Dell laptops too.
WITH FC7 THE PROBLEM IS MORE SEVERE when the system is a dual core and the video
driver on the mother board is the i810.
If Virtualisation is selected during installation, then the XEN kernel and
associated packages are loaded. A non-XEN kernel is not loaded as a backup.
When initialisation is completed, after install and during the boot process, the
system locks up deader than dead. I have not tried using linux rescue, and
chgimage to then load a normal kernel.
X works ok with the normal non XEN kernel.
This problem is in FC7 and FC6. By the way, another reminder. It does not seem
to appear with the Oct 24th release of FC6. It is present in the Unity respins
of January 2007. I identified that the problem manifested itself in November of
2006, after an XORG update.
Created attachment 154684 [details]
FC7 Boot messages (log file)
Fc7 boot messages log file
Created attachment 154685 [details]
The X windows log file up to the point of the crash.
The X windows log file up to the point of the crash.
I did an update
It is fc7 test4, using the kernel listed below that is crashing
With the test version of XEN sent to me
It boots, sometimes stopping just before boot is complete, with only the
hardware system reset button available (a hard lock occurs with no keyboard or
mouse or power switch functioning with the kernel)
Now mainly it executes to where the Gnome prompt is presented. On reboot,
journal files fix up takes place.
When lockup occurs, one cannot log into the system (no keyboard, no mouse, and
no power off switch functionable to trigger a shutdown). I have also re-tried
it switching from X windows i810 driver to the vesa driver, with same problem.
Repeat, on system freeze, the only recourse is to hit the hardware system reset
button or depress the hardware power off switch for 5 seconds, and then reboot.
No problems booting with non-xen kernel.
What can I do to help? I sent log files and
Congratulations. For the first time since November last, I am able to boot XEN,
and it did not crash, lockup, or set my computer on fire (cpu = 100%, with fan
running at 100%).
As far as I am concerned, XEN is now not a bug
For the record FC7 XEN runs on
Mother Board Intel d945gnt
Processor Intel d930
Memory 1 gig ddr2
Hard disk 200 gig ide (Maxtor)
Also thank you to Ehabkost. What first name does E represent?