https://bugzilla.novell.com/show_bug.cgi?id=463596 User frank.mueller@rhoen.de added comment https://bugzilla.novell.com/show_bug.cgi?id=463596#c2 frank mueller changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |frank.mueller@rhoen.de --- Comment #2 from frank mueller 2009-01-07 15:04:57 MST --- Wolf, am i right, the problem is that you dont get interrupts in your domU ? Can you post output from domU cat /proc/interrupt. I am experiencing the same with xen from 11.0 and xen from 11.1, no interrupts passed to domU. Thanks Frank -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463596 User lbendixs@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463596#c4 --- Comment #4 from Lynn Bendixsen 2009-01-12 09:24:18 MST --- *** Bug 464252 has been marked as a duplicate of this bug. *** https://bugzilla.novell.com/show_bug.cgi?id=464252 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463596 User jbeulich@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463596#c5 Jan Beulich changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |wolf@womaro.ch --- Comment #5 from Jan Beulich 2009-01-13 02:02:19 MST --- There are several "Failed to obtain physical IRQ ..." messages in the 2.6.22 based log as well, so I'd want to clarify what device(s) you successfully passed through in 2.6.22 that you can't pass through anymore in 2.6.27. I also understand that the logs you provided are from the DomU only. We'd need to see hypervisor and Dom0 logs, too. All of that should perhaps be done after a (presumably 2.6.27.10 based) kernel update became available, as a few fixes to the interrupt handling logic were done, and with SLE11 testing (mostly the same code base) we haven't got reports about any issues in this area recently. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463596 User jbeulich@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463596#c7 --- Comment #7 from Jan Beulich 2009-01-19 01:17:08 MST --- (In reply to comment #6)

There are "Failed to obtain IRQ" messages in the log from 2.6.22 - but that does not prevent the IRQs from being obtained in the DomU.

Hmm, that doesn't make much sense. Are you sure the driver doesn't use some polling mode? Anyway, it'll be clarified once we see /proc/interrupts for both kernel versions...

I'm currently back on runnning the working 2.6.22, but will retry (and at that time also provide the additional logs you requested) when 2.6.27.10 is available. Any idea on when this will be?

No, sorry. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463596 User jbeulich@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463596#c9 Jan Beulich changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #9 from Jan Beulich 2009-02-03 03:11:08 MST --- So, the 2.6.22 log indicates that only IRQ23 was successfully obtained, and only that IRQ actually does see activity. All other IRQs are also in use by devices in Dom0, which apparently results in them being unavailable for the DomU (although the intention is for the two domains to be permitted to share them). Judging is going to be impossible until you also provide hypervisor logs for both cases. Additionally providing the Dom0 kernel logs certainly wouldn't hurt. However, based on the IRQ setup failing with -ENOSYS I think I spotted a case that indeed isn't properly handled in the newer kernel. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463596 User jbeulich@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463596#c11 Jan Beulich changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High Status|ASSIGNED |NEEDINFO Info Provider| |wolf@womaro.ch QAContact|qa@suse.de |jdouglas@novell.com --- Comment #11 from Jan Beulich 2009-02-03 03:31:31 MST --- Could you try out this patch (i.e. can you build yourself a test kernel, which needs to be installed in the DomU)? Otherwise we'll have to see how quickly we can get you one. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463596 User wolf@womaro.ch added comment https://bugzilla.novell.com/show_bug.cgi?id=463596#c13 Wolf Geldmacher changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|wolf@womaro.ch | --- Comment #13 from Wolf Geldmacher 2009-02-03 10:46:34 MST --- Created an attachment (id=269721) --> (https://bugzilla.novell.com/attachment.cgi?id=269721) Additional logs from Dom0 Pls find attached two more logs: - dmesg-dom0: output of dmesg command for Dom0 - messages-dom0: relevant content of /var/log/messages ( Xen instance 7/8 is the patched kernel - 7 surprised me; the log in the previous attachment is the boot of 8. Xen instance 9 is the good 'ol 2.6.22 kernel) Setting back the "NEEDINFO" attribute now - pls notify if you need anything else. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463596 User jbeulich@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463596#c15 --- Comment #15 from Jan Beulich 2009-02-04 04:08:13 MST --- (In reply to comment #13) Could you clarify also what you found surprising with instance 7? Its trace in dom0's log is basically identical to that of 8. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463596 Jan Beulich changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |wolf@womaro.ch -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463596 User wolf@womaro.ch added comment https://bugzilla.novell.com/show_bug.cgi?id=463596#c18 Wolf Geldmacher changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|wolf@womaro.ch | --- Comment #18 from Wolf Geldmacher 2009-02-06 00:26:30 MST --- Created an attachment (id=270683) --> (https://bugzilla.novell.com/attachment.cgi?id=270683) Logs for 2.6.27.10 patched Hi Jan, with the second patch applied 2.6.27 now works like 2.6.22 did! The DomU can use the PCI hardware again. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463596 User jbeulich@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463596#c20 Jan Beulich changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #20 from Jan Beulich 2009-02-06 01:26:25 MST --- (In reply to comment #19)

I may be a good idea, though, to create a new bugzilla entry (lower prio, related but not identical issue) for this.

I agree to that, and it all depends on you (and with the state things are I really don't think the controllers not getting their interrupts set up really work - you may just happen to only use ports hanging off the two ones that do): If you enter a new bug for this, please provide either the full serial log or, if that's difficult to achieve, 'xm dmesg' output from right after the system got up (without any VMs started) and from after the VM in question was started. The patch for the problem here was committed yesterday, but I can't tell when you an update kernel for 11.1 would have it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.