https://bugzilla.novell.com/show_bug.cgi?id=641900
https://bugzilla.novell.com/show_bug.cgi?id=641900#c11
--- Comment #11 from Jan Beulich 2010-09-30 07:40:56 UTC ---
The log doesn't tell much, but at least it clarifies it's not the problem I was
suspecting. Instead, especially the instance on Sep 16 suggest a more general
interrupt handling problem, as a SATA device also suffered. Later instances
with the 8139 don't, however - did you reconfigure the system in some way (e.g.
was the interrupt shared originally, and now it isn't)?
We'll need /var/log/boot.msg for both a native and a Xen kernel boot, and we'll
need access to Xen's console (if the system is still usable once this state is
reached, "xm debug-key" and "xm dmesg" command will do, but if it isn't a
serial console is going to be unavoidable).
One other thing to try would be passing "cpuidle=0" to Xen. And of course I
assume you already installed the recently released Xen update, and know the
issue is not solved by this.
Finally, it would also be useful to know whether the latest kernel-of-the-day
(ftp://ftp.suse.com/pub/projects/kernel/kotd/openSUSE-11.3/x86_64/, 2.6.36-rc
based, but specifically with some rework of the interrupt handling) would help.
--
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.