On Thu, Jan 06, 2011 at 08:23:14PM +0200, Pasi Kärkkäinen wrote:
> On Thu, Jan 06, 2011 at 07:36:28PM +0200, Pasi Kärkkäinen wrote:
> > Hello,
> > First of all.. big thanks to everyone involved in upstreaming Xen dom0
> > bits!
> > I just tried upstream pvops 2.6.37 dom0 kernel on one of my machines, and
> > it worked
> > out-of-the-box ! Even nouveau kms/modesetting worked just fine.
> > There was non-fatal BUG/traceback though:
> > Full dmesg log available at:
> > http://pasik.reaktio.net/xen/logs/dmesg-2.6.37-1.xendom0.fc15.x86_64-kms-modesetting.txt
> Additional data.. latest xen/stable-2.6.32.x dom0 kernel (18.104.22.168) doesn't
> have this BUG/traceback.
Sorry for the noise.. it seems this is a bug in the xhci driver in 2.6.37.
It's already fixed upstream but the fix is not in 2.6.37.
I noticed the bugreport from lkml, it seems to happen also on baremetal for
(it didn't for me).
Well.. at least it was not xen dom0 specific bug :)
From: Greg KH <gregkh@xxxxxxx>
To: Robert Hancock <hancockrwd@xxxxxxxxx>
Cc: Sarah Sharp <sarah.a.sharp@xxxxxxxxxxxxxxx>,
Date: Wed, 5 Jan 2011 16:30:03 -0800
Subject: Re: Sleeping function called from invalid context in 2.6.37 xhci_hcd
On Wed, Jan 05, 2011 at 06:22:03PM -0600, Robert Hancock wrote:
> Just saw this on booting up on the latest Fedora Rawhide kernel
> based on 2.6.37. Looks like we were trying to do a runtime suspend
> on the xHCI USB controller and it disabled MSI-X while interrupts
> were disabled?
Known issue, patches came in too late to make it for .37, hopefully will
show up in .38-rc and then get backported to .37. They are on the
linux-usb mailing list if you need them now.
Hope this helps,
Xen-devel mailing list