Description of problem:
Well, the Xen kernel is broken...when booting the machine using kernel-xen,
then machine hangs up during boot.
May 9 21:48:45 rsc kernel: BUG: at kernel/lockdep.c:1858 trace_hardirqs_on()
May 9 21:48:45 rsc kernel: [<c1005d9a>] show_trace_log_lvl+0x1a/0x2f
May 9 21:48:45 rsc kernel: [<c1006343>] show_trace+0x12/0x14
May 9 21:48:45 rsc kernel: [<c10063be>] dump_stack+0x16/0x18
May 9 21:48:45 rsc kernel: [<c1037439>] trace_hardirqs_on+0xc4/0x143
May 9 21:48:45 rsc kernel: [<c10055d4>] restore_all+0x3b/0x3e
May 9 21:48:45 rsc kernel: =======================
Version-Release number of selected component (if applicable):
Everytime for me.
Steps to Reproduce:
1. Install the virtualization stuff using pirut
2. Change boot order
3. Boot system
No booting possible when using kernel-xen package.
Working system, not more and not less ;-)
Syslog is attached to this report. I gave the kernel two tries as you can see.
Created attachment 154426 [details]
Relevant parts from /var/log/messages
the same problem with
The lockdep bug (while it should be fixed) is fairly harmless as far as we can
Ries - when you say you have the same problem when latest kernel, are you
refering to the lockdep bug warning message, or an actual fatal hang / crash at
boot time ?
I am able to boot dom0, with warning
device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: firstname.lastname@example.org
BUG: at kernel/lockdep.c:1858 trace_hardirqs_on()
printk: 20312 messages suppressed.
4gb seg fixup, process nash-hotplug (pid 219), cs:ip 73:00279a1c
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
but I am unable to create domU's
Do the problem persist when using the new kernel-xen?
Eduardo Habkost, have you read my message ?
I have tested with kernel-xen-2.6-2.6.20-2925.8.fc7 and the problem persists
My questoin is which problem this bug is about, and what we need to close it.
We have three distinct problems reported here:
a) Crashes and hangs (same of bug 234008, but for rawhide, and solved with the
b) BUG: at kernel/lockdep.c:1858 trace_hardirqs_on() (not solved yet)
c) Not being able to create domU virtual machines (need more information)
If this bug is about (a), then it can be closed if the problem is solved. If
this is about (b), then we can keep it open until we resolve the "BUG"
message. It is up to the bug reporter to decide what is the case, so I asked
Robert about the problem he reported.
Itamar, Regarding not being able to create domUs, could you provide more
details about the problem? How you are trying to create them and what are the
error messages or unexpected behaviour you are getting? Maybe this problem is
appropriate for a separated bug report, as it seems to be independent of (a)
and (b). Are you able to create domUs using kernel-xen 2.6.19?
I am able to create domU's using xen 3.1 rc10 and a 2.6.18 kernel, compiled
if you have a ssh_key I can provide root access to the machine.
Have this bug with
-rw-r--r-- 1 root root 875161 2007-05-10 18:00 System.map-2.6.20-2925.8.fc7xen
The problem also exists with 2.6.20-2925.8.fc7xen.
this problem still persists in 2.6.20-2925.9.fc7xen
Do you still see hangs or crashes, or just the "BUG: at kernel/lockdep.c:1858
It seems that upstream xen doesn't support CONFIG_PROVE_LOCKING (. The check
for enabled interrupts on TRACE_IRQS_IRET seems to be incorrect for xen, as
they are disabled/enabled through evtchn_upcall_mask(%esi), and not
Relevant part of arch/i386/kernel/entry-xen.S:
testl $IF_MASK,PT_EFLAGS(%esp) # interrupts off?
Changing this to check evtchn_upcall_mask() may solve the problem, but I don't
know if there may be other problems related to CONFIG_PROVE_LOCKING on xen.
Disabling CONFIG_PROVE_LOCKING on kernel-xen seems to be more safe.
(In reply to comment #13)
> Do you still see hangs or crashes, or just the "BUG: at kernel/lockdep.c:1858
> trace_hardirqs_on()" persisted?
yes, the dom0 boots fine with this warning,at this moment no crashes, but I am
unable to create domU's
Itamar, could you provide more information regarding the problem you have
creating domU's? Preferably in a new bugzilla bug, as it is not related
to the lockdep warning (that is harmless).
Please detail the exact steps you are making to create the new domU domains,
error messages or unexpected behaviour you are seeing, and what was the
CONFIG_PROVE_LOCKING was disabled on F-7 CVS, and a build was submitted:
It probably won't go to Fedora 7 final, but as an additional update, however.
Itamar that looks related to my problem. I can create DomUs but if I want to
boot them, they simply crash. Xm list tells, that they are already running,
but when looking to log, they're crashed...
Eduardo, IIRC nothing is gold for now. It can slip in, if you're fast enough.
Ouch. Wrong bug closed, sorry.
this is fixed in 2.6.20-2925.10.fc7
kernel-xen-2.6-2.6.20-2925.11.fc7 has been pushed to the Fedora 7 testing repository. If problems still persist, please make note of it in this bug report.
*** Bug 244561 has been marked as a duplicate of this bug. ***
kernel-xen-2.6-2.6.20-2925.11.fc7 has been pushed to the Fedora 7 stable repository. If problems still persist, please make note of it in this bug report.