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
> > > > 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
> > >
> > > 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
> > 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 0000:09:00.0: not ready 4195ms after FLR; waiting
[ 20.458401] xhci_hcd 0000:09:00.0: not ready 8291ms after FLR; waiting
[ 29.161245] xhci_hcd 0000:09:00.0: not ready 16483ms after FLR; waiting
[ 46.058397] xhci_hcd 0000:09:00.0: not ready 32867ms after FLR; waiting
[ 82.922254] xhci_hcd 0000:09:00.0: not ready 65635ms after FLR; giving up
[ 83.261301] xhci_hcd 0000:09:00.0: Refused to change power state,
currently in D3
[ 83.352431] xhci_hcd 0000:09:00.0: xHCI Host Controller
[ 83.387291] xhci_hcd 0000:09:00.0: new USB bus registered, assigned
bus number 11
[ 83.699853] xhci_hcd 0000:09:00.0: Host halt failed, -19
[ 83.731151] xhci_hcd 0000:09:00.0: can't setup: -19
[ 83.764138] xhci_hcd 0000:09:00.0: USB bus 11 deregistered
[ 83.821909] xhci_hcd 0000:09:00.0: init 0000: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.
"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