similar to: Re: xHCI not waking up from D3 after S3 Resume on Ivybridge

After resuming more than once on battery these HP Ivybridge laptops, the XHCI devices stop working. Have anyone seen this before? I wanted to check before diving in deeper. Let me know if you have any ideas. Thanks! Facts - Xen 4.0.3, Linux 3.2.7 PVOPs - Happens on HP Ivybridge. Doesn''t happen on very similar HP Sandybridge Clash system. - Happens on battery, but not on AC. -

Hello list, Is there an easy way to remove or disable xhci driver in images/pxeboot/vmlinuz? I need to avoid USB 3.0 controller to work in xhci mode when thn ananconda is working.

Three different external hard drives (Seagate, Western Digital and noname USB 3.0 enclosure) refused to be recognized as the umass devices. Reverting /usr/src/sys/dev/bsd/controller to r248085, building and loading just xhci module makes drives appear again. Below are snippets from the log in both cases: Non working: Jul 4 14:35:17 twinhead kernel: xhci0: <XHCI (generic) USB 3.0

Hi Konrad, Due to a 2.6.37-merge-window kernel now being able to boot under Xen i was able to test my xhci controller under dom0 which i previously couldn''t. The results: A) 2.6.37-merge-window kernel baremetal: Videograbbing while doing 20 iterations of make -j6 of kernel works. B) Xen + 2.6.37-merge-window kernel as Dom0: Videograbbing while doing 20 iterations of make -j6 of kernel

On 10/02/2020 07:38 AM, H wrote: > On October 1, 2020 11:58:11 AM EDT, Bruce Ferrell <bferrell at baywinds.org> wrote: >> On 9/30/20 8:52 AM, H wrote: >>> 00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset >> Family USB 3.0 xHCI Controller >> My system has these: >> >> 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series

On 9/30/20 8:52 AM, H wrote: > 00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller My system has these: 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) 00:1d.0 USB controller: Intel Corporation 8

Hi Ben, Ok! I've removed nvidiafb from kernel config. Now linux is able to boot with the msi Geforce GT 710 card and eventually ends up displaying a slightly distorted lightdm login screen. The mouse cursor moves, but never changes to typing cursor mode when hovering the password input box, and I am also unable to enter the password, some graphics glitches in the login box too. There are

On October 1, 2020 11:58:11 AM EDT, Bruce Ferrell <bferrell at baywinds.org> wrote: >On 9/30/20 8:52 AM, H wrote: >> 00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset >Family USB 3.0 xHCI Controller >My system has these: > >00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset >Family USB xHCI (rev 05) >00:1a.0 USB controller: Intel

Hi Arnd, Sorry for sending this email directly to you, but maybe you can help me, or guide me where to look for. I am having big trouble getting the nouveau driver to work with either Geforce GT 710 or Geforce 9800 GT on an ARM armv7l Cortex-A9 with PCIe x1/x4 with linux kernel 4.15-rc. The Geforce GT 710 hangs the kernel boot process for a while and then a kernel oops occurs, due to nvidiafb,

On 10 August 2014 09:05, Charles Lepple <clepple at gmail.com> wrote: > On Aug 7, 2014, at 7:57 AM, Leith Bade <leith at leithalweapon.geek.nz> wrote: > > Error -32 is EPIPE, which means that the PC didn't see a reply from the device during the descriptor read. I don't know that we have ever successfully run one of these issues to ground. > Considering Eaton do

Hi, I am having a hard time rationalizing why virt-resize would be the cause of this issue, however it appears to definitely be the trigger, hence trying this list. My environment comprises Debian 10 hosts and guests, although this issue has also been witnessed on Debian 9 hosts running Debian9/10 guests. In all cases, stable versions of libvirt, qemu-kvm, libguestfs- tools, etc running on AMD64

Hi, > > * I'd like to see some more flexibility in the pci bar layout. Stuff > > I have in mind: > > - New devices which don't need a legacy bar can use bar 0 for > > modern. > > - One MMIO bar is enough, we can place both virtio regions and > > msi-x regions there. I'd suggest to add msi-x sub-regions to > >

Hi, > > * I'd like to see some more flexibility in the pci bar layout. Stuff > > I have in mind: > > - New devices which don't need a legacy bar can use bar 0 for > > modern. > > - One MMIO bar is enough, we can place both virtio regions and > > msi-x regions there. I'd suggest to add msi-x sub-regions to > >

Hi, I have an Optimus-enabled laptop with a GTX 1060m. I never got it to fully work with Nouveau even after Pascal support was added. I need to run the kernel with nouveau.runpm=0 to get it to work. Unfortunately without proper power mangement support, my laptop will run out of battery after about 1h30, so I'd love to get Optimus working. What I can see is that when the extra GPU is not in

On Fri, Jan 16, 2015 at 09:32:26AM +0100, Gerd Hoffmann wrote: > Hi, > > > > * I'd like to see some more flexibility in the pci bar layout. Stuff > > > I have in mind: > > > - New devices which don't need a legacy bar can use bar 0 for > > > modern. > > > - One MMIO bar is enough, we can place both virtio regions and

On Fri, Jan 16, 2015 at 09:32:26AM +0100, Gerd Hoffmann wrote: > Hi, > > > > * I'd like to see some more flexibility in the pci bar layout. Stuff > > > I have in mind: > > > - New devices which don't need a legacy bar can use bar 0 for > > > modern. > > > - One MMIO bar is enough, we can place both virtio regions and

On Wed, Jan 27, 2016 at 01:30:05PM -0500, Konrad Rzeszutek Wilk wrote: > On Sat, Jan 23, 2016 at 05:12:04PM +0100, Tommi Airikka wrote: > > Xen developers, > > > > After an upgrade of my Debian Jessie dom0 and domUs, my passthroughed > > NIC stopped working. I have very similar (the same?) problem with USB 3.0 controller. But on different software versions. > >

On Thu, May 4, 2017 at 4:21 AM, Andy Shevchenko <andriy.shevchenko at linux.intel.com> wrote: > acpi_evaluate_dsm() and friends take a pointer to a raw buffer of 16 > bytes. Instead we convert them to use uuid_le type. At the same time we > convert current users. > > acpi_str_to_uuid() becomes useless after the conversion and it's safe to > get rid of it. > > The

Source: xen Severity: normal Dear Maintainer, After an upgrade, my passthroughed NIC stopped working. I created a new jessie domU and tried to passthrough some PCI devices and found that both USB3 host controller and tg3 NIC generated these lines in domU dmesg: xen:events: Failed to obtain physical IRQ 31 xen:events: Failed to obtain physical IRQ 32 xen:events: Failed to obtain physical IRQ 33

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-6 Severity: normal Dear Maintainer, I'm trying to boot into xen/dom0 but so far all attempts have resulted in a crash followed by an automatic reboot. My hardware is Motherboard: Asus Sabertooth 990FX R2.0 CPU: AMD FX-8350 GPU: Sapphire Radeon R9 285 A trace of the kernel panic follows (full log captured over serial should