Bug 239874
| Summary: | Lockup during boot or immediately after | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Leslie Satenstein <lsatenstein> | ||||||||||||||
| Component: | xen | Assignee: | Xen Maintainance List <xen-maint> | ||||||||||||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||||||||||||
| Severity: | medium | Docs Contact: | |||||||||||||||
| Priority: | medium | ||||||||||||||||
| Version: | rawhide | CC: | katzj | ||||||||||||||
| Target Milestone: | --- | ||||||||||||||||
| Target Release: | --- | ||||||||||||||||
| Hardware: | All | ||||||||||||||||
| OS: | Linux | ||||||||||||||||
| Whiteboard: | Kernel | ||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||
| Last Closed: | 2007-05-24 01:53:28 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: | |||||||||||||||||
| Attachments: |
|
||||||||||||||||
|
Description
Leslie Satenstein
2007-05-11 20:07:01 UTC
The -2925.5 kernel-xen is known to be utterly broken. Please re-test with latest kernel-xen & xen RPMs available from, which have fixed at least 4 separate crash/corruption bugs: http://koji.fedoraproject.org/packages/kernel-xen-2.6/2.6.20/2925.8.fc7/ http://koji.fedoraproject.org/packages/xen/3.1.0/0.rc7.1.fc7/ NB, you must install both to get working Xen. Created attachment 154593 [details]
The boot messages
If I sent you the wrong files, or you require additional files, please advise.
Created attachment 154594 [details]
X windows log file (after Xen reboot)
Xorg logfile (current, after crash). Will also include previous one
Created attachment 154595 [details]
X windows log file (after Xen reboot)
Created attachment 154596 [details]
/var/log/Xorg.0.log.old
If you require other logs, please advise
Umm, can you please be a little more precise about exactly what is going on and which log files correspond to which behaviour? There are two log files there labelled "X windows log file (after Xen reboot)"... but after Xen reboots, haven't you then rebooted into a non-xen kernel and overwritten the X logs with new ones from the next boot? And you haven't told us if the behaviour changed with the new .8 kernel. The kernel boot messages attachment shows two separate boots, one with .8 and one non-xen, but both last until the same lines (they both end at gconfd xml warnings), so it's really unclear whether you are still seeing different behaviour from xen and non-xen. I am not an linux guru, so I thought that since your updated XEN runs to the lockup point, that you would want to see the message log, and the X-windows logs to where it locked up. In attaching the files, I did accidentally, due to a little buglet in firefox, resend one file twice, because FF did not return to update the prompt. There should only be 3 files. 2 for X and messages. If I sent the wrong ones, or incomplete please advise me, how to proceed (email me separately if you wish), and I will do for you what you need to have done. My background is more in computer system architecture (business systems, and in mathematical modeling,) and while I never compiled a kernel, I did program for years in C. You asked.. Umm, can you please be a little more precise about exactly what is going on and which log files correspond to which behaviour? I replied... I zeroed the messages file and the x-windows file. and rebooted with non-XEN in order to create the attachments. Just in case, I also included the (-1) version, a previous X log file. I presume that the X log file after the reboot back to normal made the backup version of the previous log file. There are two log files there labelled "X windows log file (after Xen reboot)"... but after Xen reboots, haven't you then rebooted into a non-xen kernel and overwritten the X logs with new ones from the next boot? And you haven't told us if the behaviour changed with the new .8 kernel. The behaviour did change. I replied I saw a cleaner boot with one message that was the result of an assert() call disappear. I was able to log to gnome for about 2 minutes. When I retried after that crash, the system appeared to lock up before the gnome prompt was presented. So, I really cannot tell you more than that. I will clear out the three log files (X windows and messages) and do the following: 1) reboot with XEN, and attempt to log into the system. I will try to use the system until a lockup occurs I will then boot with my alternate FC6 and copy to a safe place those log files, I will tell you exactly what happened. If there is a log file that I am sending that is not the right one, please advise me. The kernel boot messages attachment shows two separate boots, one with .8 and one non-xen, but both last until the same lines (they both end at gconfd xml warnings), so it's really unclear whether you are still seeing different behaviour from xen and non-xen. I reply again I will redo the test. Created attachment 154688 [details]
Boot messages from FC7 XEN
Created attachment 154689 [details]
The X windows log file
If there are other things for me to do to help you, please advise.
Currently kernel-xen-2.6.20-2925.9.fc7.i686.rpm 22-May-2007 06:04 16M [ ] kernel-xen-devel-2.6.20-2925.9.fc7.i686.rpm 22-May-2007 06:03 14M Broke the version that partially worked. Now, somewhere in the boot process, the keyboard, mouse and power interrupt switch are lost. No Gnome, no keyboard response, bad bed bad. It also resulted in some common files with the preceding version (8) so that neither boots on my system. |