Re: Fwd: Re: Bug 198731 "USB devices not seen with newest kernel"
Am Montag, den 05.03.2018, 16:27 +0200 schrieb Mathias Nyman: > On 26.02.2018 16:05, Oliver Neukum wrote: > > > > Am Dienstag, den 13.02.2018, 13:56 -0800 schrieb The Real Bev: > > > > > it looks like a relatively old issue with D3 on some instances of XHCI. > > > > Yep, The "Host halt failed, -19" (ENODEV) is seen when xhci driver tries to > halt the host during setup, polling a mmio register but reading only > 0x. > > Which I guess is expected if controller is still on D3. > > No idea why this controller fails to change from D3 to D0. > Any PCI changes betewen 4.8 and 4.9? commit 4132a577a0a7e75b938d2ae49c7a16b358f60661 Author: Lukas Wunner Date: Sun Sep 18 05:39:20 2016 +0200 PCI: Afford direct-complete to devices with non-standard PM commit cc7cc02bada84f0d707aa5b6d2ef8728a2e1f911 Author: Lukas Wunner Date: Sun Sep 18 05:39:20 2016 +0200 PCI: Query platform firmware for device power state commit a6a64026c0cd1a76a0c8ab1c05a421aa4821887b Author: Lukas Wunner Date: Sun Sep 18 05:39:20 2016 +0200 PCI: Recognize D3cold in pci_update_current_state() commit a0d2a959d3da343554523d26902de1d40a9e5c28 Author: Lukas Wunner Date: Sun Sep 18 05:39:20 2016 +0200 PCI: Avoid unnecessary resume after direct-complete Could you test with a revert of a0d2a959d3da343554523d26902de1d40a9e5c28 ? Regards Oliver -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Fwd: Re: Bug 198731 "USB devices not seen with newest kernel"
On 26.02.2018 16:05, Oliver Neukum wrote: Am Dienstag, den 13.02.2018, 13:56 -0800 schrieb The Real Bev: I went back to the distribution kernel for 64-bit 14.2 slackware -- 4.14.18. During boot, dmesg displays the following errors: [ 15.850711] xhci_hcd :09:00.0: not ready 4195ms after FLR; waiting [ 20.458401] xhci_hcd :09:00.0: not ready 8291ms after FLR; waiting [ 29.161245] xhci_hcd :09:00.0: not ready 16483ms after FLR; waiting [ 46.058397] xhci_hcd :09:00.0: not ready 32867ms after FLR; waiting [ 82.922254] xhci_hcd :09:00.0: not ready 65635ms after FLR; giving up [ 83.261301] xhci_hcd :09:00.0: Refused to change power state, currently in D3 [ 83.352431] xhci_hcd :09:00.0: xHCI Host Controller [ 83.387291] xhci_hcd :09:00.0: new USB bus registered, assigned bus number 11 [ 83.699853] xhci_hcd :09:00.0: Host halt failed, -19 [ 83.731151] xhci_hcd :09:00.0: can't setup: -19 [ 83.764138] xhci_hcd :09:00.0: USB bus 11 deregistered [ 83.821909] xhci_hcd :09:00.0: init :09:00.0 fail, -19 This is the same problem I've had for 4.9.79, 4.15.2 and now 4.14.18. There is clearly a problem. I give up. I'm just going to live with it. Hi Mathias, it looks like a relatively old issue with D3 on some instances of XHCI. Yep, The "Host halt failed, -19" (ENODEV) is seen when xhci driver tries to halt the host during setup, polling a mmio register but reading only 0x. Which I guess is expected if controller is still on D3. No idea why this controller fails to change from D3 to D0. Any PCI changes betewen 4.8 and 4.9? -Mathias -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Fwd: Re: Bug 198731 "USB devices not seen with newest kernel"
Am Dienstag, den 13.02.2018, 13:56 -0800 schrieb The Real Bev: > I went back to the distribution kernel for 64-bit 14.2 slackware -- > 4.14.18. During boot, dmesg displays the following errors: > > [ 15.850711] xhci_hcd :09:00.0: not ready 4195ms after FLR; waiting > [ 20.458401] xhci_hcd :09:00.0: not ready 8291ms after FLR; waiting > [ 29.161245] xhci_hcd :09:00.0: not ready 16483ms after FLR; waiting > [ 46.058397] xhci_hcd :09:00.0: not ready 32867ms after FLR; waiting > [ 82.922254] xhci_hcd :09:00.0: not ready 65635ms after FLR; giving up > [ 83.261301] xhci_hcd :09:00.0: Refused to change power state, > currently in D3 > [ 83.352431] xhci_hcd :09:00.0: xHCI Host Controller > [ 83.387291] xhci_hcd :09:00.0: new USB bus registered, assigned > bus number 11 > [ 83.699853] xhci_hcd :09:00.0: Host halt failed, -19 > [ 83.731151] xhci_hcd :09:00.0: can't setup: -19 > [ 83.764138] xhci_hcd :09:00.0: USB bus 11 deregistered > [ 83.821909] xhci_hcd :09:00.0: init :09:00.0 fail, -19 > > This is the same problem I've had for 4.9.79, 4.15.2 and now 4.14.18. > There is clearly a problem. I give up. I'm just going to live with it. Hi Mathias, it looks like a relatively old issue with D3 on some instances of XHCI. Regards Oliver -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Fwd: Re: Bug 198731 "USB devices not seen with newest kernel"
On 02/13/2018 12:46 AM, Greg KH wrote: On Mon, Feb 12, 2018 at 10:16:56AM -0800, The Real Bev wrote: On 02/11/2018 09:50 PM, Greg KH wrote: > On Fri, Feb 09, 2018 at 12:25:44PM -0800, The Real Bev wrote: > > On 02/09/2018 05:13 AM, Greg KH wrote: > > > On Thu, Feb 08, 2018 at 01:00:02PM -0800, The Real Bev wrote: > > > > I think I have found a bug in the linux kernel 4.9.79. The problem > > > > is in the performance of the driver for the Renesas Technology Corp. > > > > uPD720201 > > > > PCI-e USB host controller. > > > > > > > > My system has an Intel I7 960 cpu. The USB controller works when accessed > > > > using the driver in the 4.8.10 kernel. Within the last few days > > > > I compiled the 4.9.79 kernel using the same .config file as for > > > > the 4.8.10 kernel except that I accepted the default for all kernel > > > > options not already contained in the old config file. In other words, > > > > starting with the .config file for the 4.8.10 kernel I did > > > > make oldconfig > > > > and defaulted on every question. > > > > > > > > Under the new kernel the system sees the host control via > > > > lspci: > > > > 09:00.0 USB controller: Renesas Technology Corp. uPD720201 USB 3.0 Host > > > > Controller (rev 03) > > > > > > > > However nothing comes up in dmesg when I plug a device into the controller. > > > > > > Odds are you might have missed a build option for your system. Can you > > > go back to your 4.8.y .config file and look at the new options to be > > > sure that there was not one for the Renesas hardware you have? > > > > > > Also, 4.9 is really old, it's recommended you use something more modern, > > > like 4.14 or even better yet, 4.15. > > > > 4.9 was the latest kernel when I updated :-( They're coming thick and fast, > > aren't they? > > 4.9 was released in December of 2016, a long time ago in kernel > development. > > > I built the 4.15.2 kernel using the .config derived from the 4.8.10 kernel. > > I just don't have the energy to respond to every single difference in the > > config file > > (never had to do that in the past), and just accept the defaults. The > > following lines > > appeared while booting the 4.15.2 kernel: > > Again, odds are you are missing something you really need here. Odds > are you are missing something like CONFIG_USB_XHCI_PCI or some other > XHCI build option. > > I recommend trying a distro kernel on this machine, and if that works, > running 'make localmodconfig' with that distro kernel running to get a > working configuration file. Distro kernels are too old. You need a better distro :) Both Fedora and Arch Linux and probably openSUSE all have 4.14 kernels, if not 4.15 already. The XHCI options are already modules. Here's the appropriate part of the config file. Can you see a problem? Are you sure you are loading all of the needed modules properly? Again, please try a modern distro. I went back to the distribution kernel for 64-bit 14.2 slackware -- 4.14.18. During boot, dmesg displays the following errors: [ 15.850711] xhci_hcd :09:00.0: not ready 4195ms after FLR; waiting [ 20.458401] xhci_hcd :09:00.0: not ready 8291ms after FLR; waiting [ 29.161245] xhci_hcd :09:00.0: not ready 16483ms after FLR; waiting [ 46.058397] xhci_hcd :09:00.0: not ready 32867ms after FLR; waiting [ 82.922254] xhci_hcd :09:00.0: not ready 65635ms after FLR; giving up [ 83.261301] xhci_hcd :09:00.0: Refused to change power state, currently in D3 [ 83.352431] xhci_hcd :09:00.0: xHCI Host Controller [ 83.387291] xhci_hcd :09:00.0: new USB bus registered, assigned bus number 11 [ 83.699853] xhci_hcd :09:00.0: Host halt failed, -19 [ 83.731151] xhci_hcd :09:00.0: can't setup: -19 [ 83.764138] xhci_hcd :09:00.0: USB bus 11 deregistered [ 83.821909] xhci_hcd :09:00.0: init :09:00.0 fail, -19 This is the same problem I've had for 4.9.79, 4.15.2 and now 4.14.18. There is clearly a problem. I give up. I'm just going to live with it. -- Cheers, Bev "I wish I had more time to seek out the dark forces and join their hellish crusade."-- Clarice -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
