Bug 182184
Summary: | kernel-2.6.15-1.1955_FC5hypervisor spontaneausly reboots | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Bernd Bartmann <bernd.bartmann> |
Component: | kernel-xen | Assignee: | Juan Quintela <quintela> |
Status: | CLOSED UPSTREAM | QA Contact: | Brian Brock <bbrock> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 5 | CC: | bstein, ken.tanzer, wtogami, xen-maint |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-10-26 20:17:38 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: | |||
Bug Depends On: | |||
Bug Blocks: | 179629 |
Description
Bernd Bartmann
2006-02-20 21:47:40 UTC
Today the system did not reboot yet, but I'm seeing messages on the console (but not in /var/log/messages): (XEN) APIC error on CPU0: 02(02) (XEN) APIC error on CPU0: 02(40) (XEN) APIC error on CPU0: 40(02) (XEN) APIC error on CPU0: 02(02) (XEN) APIC error on CPU0: 02(08) (XEN) APIC error on CPU0: 08(02) (XEN) APIC error on CPU0: 02(04) (XEN) APIC error on CPU0: 04(02) I'm seeing a slight variation on this. Same kernel. When ever I boot with the FC5test3 DVD in the drive ( note: not the boot device ) the machine gets to "Setting Hostname" and spontaneously reboots. When I boot the xen kernel it gets slightly into the boot process, and then reboots. I had this problem with xen0_1955, and still with 2041. I've got a Pentium D. Here's some messages from the boot. Apologize for paraphrasing, but it scrolls by quickly and reboots. Can provide any more info requested. Thanks. Cannot bind irq 2 to guest: in use (by?) cascade (this line repeats twice, I think) I do see a "red hat nash" message, along with reading or loading physical volumes. Then: failed to create /dev/ram (or ram0?): file exists failed to create /dev/ram1 There might be a couple of lines after that, and then a reboot. My machine happily runs (non-xen) 1955_FC5smp. Could you please try to capture a serial console output from this? Add com1=38400,8n1 sync_console to the kernel=xen... line in /etc/grub.conf (assuming 38400 baud output), and console=ttyS0 console=tty to the module=vmlinuz... line. Failing that, you may be able to capture more console output by adding "noreboot" to the kernel=xen... line. Sorry I didn't see this sooner--forgot to CC. Even worse, finally threw out all my old cables a few weeks ago, so I can't capture serial output. Might be able to do so on Monday. I did try "noreboot", and there is a whole bunch of error stuff that looks like kernel panic output. Most of it still scrolled off the screen, and what was still there looked mostly related to reboot, so I didn't write it all down. The first line still visible reads: [<c010fe0c>] smp_call_function+0x69/0x110 I did notice that after the crash the light on my DVD-ROM drive was staying on, so I removed the disk in there and rebooted. At this point, the boot was successful, and I was brought to a normal graphical login. I switched to a text login, logged in as root, verified the xen0 kernel was running, and rebooted. I next tried various combinations, but the results mostly confused me. One time when I booted without the disk, I tried the graphical login (as a normal user), and it got 25% of the way through the Fedora/KDE initialization, and then froze. When I put the DVD back in my other drive (DVD burner), it booted the entire kernel, but crashed somewhere during the rest of the startup process. Without the disk in, I got a couple of crashes, and a couple of successful boots. At this moment, I am running the xen kernel (2.6.15-1.2041_FC5xen0), and was able to login. Sorry this is not all more precise. I'll try to get a hold of a serial cable, and let me know what other info would be useful in the meantime. Please re-open if this issue continues. |