install USB 3.0 express card under linux (Arch Linux) (tried adding kernel parameter intel_iommu=off pciehp.pciehp_force=1)

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
0
down vote

favorite












I'm trying to install a CSL USB 3.0 express card to my Arch Linux system.



However, when I do this, I get the following error message:




xhci_hcd 0000:05:00.0: xHCI host controller not responding, assume dead



xhci_hcd 0000:05:00.0: HC died; cleaning up




I googled and tried adding the following kernal parameters



intel_iommu=off


Some sites also mention



iommu


This unfortunately didn't help me anything.



I also tried to add:



pciehp pciehp_force=1


And tried to do



sudo modprobe pciehp pciehp_force=1


But Arch Linux complains that it doesn't find the kernel module pciehp.



I didn't find any information on how to install pciehp kernel module on Arch Linux. Some say, it is build into the kernel or something.



debug information:



kernel version: 4.16.6-1-ARCH



dmesg with debugging xhci_hcd enabled and with xhci_hcd greped



lspci -nn:



05:00.0 USB controller [0c03]: Renesas Technology Corp. uPD720202 USB 3.0 Host Controller [1912:0015] (rev 02)


dmesg (old without xhci_hcd-debugging and withouth grep







share|improve this question

















  • 1




    Please edit question with the line in lspci -nn that identifies the problematic controller card. Also edit question with any other messages related to this card that show up in dmesg. (Indent 4 spaces for proper formatting).
    – dirkt
    Apr 29 at 16:49










  • @dirkt I did! You may kindly edit the question posting an excerpt from the pastebin.
    – Arch Linux Tux
    Apr 29 at 17:34














up vote
0
down vote

favorite












I'm trying to install a CSL USB 3.0 express card to my Arch Linux system.



However, when I do this, I get the following error message:




xhci_hcd 0000:05:00.0: xHCI host controller not responding, assume dead



xhci_hcd 0000:05:00.0: HC died; cleaning up




I googled and tried adding the following kernal parameters



intel_iommu=off


Some sites also mention



iommu


This unfortunately didn't help me anything.



I also tried to add:



pciehp pciehp_force=1


And tried to do



sudo modprobe pciehp pciehp_force=1


But Arch Linux complains that it doesn't find the kernel module pciehp.



I didn't find any information on how to install pciehp kernel module on Arch Linux. Some say, it is build into the kernel or something.



debug information:



kernel version: 4.16.6-1-ARCH



dmesg with debugging xhci_hcd enabled and with xhci_hcd greped



lspci -nn:



05:00.0 USB controller [0c03]: Renesas Technology Corp. uPD720202 USB 3.0 Host Controller [1912:0015] (rev 02)


dmesg (old without xhci_hcd-debugging and withouth grep







share|improve this question

















  • 1




    Please edit question with the line in lspci -nn that identifies the problematic controller card. Also edit question with any other messages related to this card that show up in dmesg. (Indent 4 spaces for proper formatting).
    – dirkt
    Apr 29 at 16:49










  • @dirkt I did! You may kindly edit the question posting an excerpt from the pastebin.
    – Arch Linux Tux
    Apr 29 at 17:34












up vote
0
down vote

favorite









up vote
0
down vote

favorite











I'm trying to install a CSL USB 3.0 express card to my Arch Linux system.



However, when I do this, I get the following error message:




xhci_hcd 0000:05:00.0: xHCI host controller not responding, assume dead



xhci_hcd 0000:05:00.0: HC died; cleaning up




I googled and tried adding the following kernal parameters



intel_iommu=off


Some sites also mention



iommu


This unfortunately didn't help me anything.



I also tried to add:



pciehp pciehp_force=1


And tried to do



sudo modprobe pciehp pciehp_force=1


But Arch Linux complains that it doesn't find the kernel module pciehp.



I didn't find any information on how to install pciehp kernel module on Arch Linux. Some say, it is build into the kernel or something.



debug information:



kernel version: 4.16.6-1-ARCH



dmesg with debugging xhci_hcd enabled and with xhci_hcd greped



lspci -nn:



05:00.0 USB controller [0c03]: Renesas Technology Corp. uPD720202 USB 3.0 Host Controller [1912:0015] (rev 02)


dmesg (old without xhci_hcd-debugging and withouth grep







share|improve this question













I'm trying to install a CSL USB 3.0 express card to my Arch Linux system.



However, when I do this, I get the following error message:




xhci_hcd 0000:05:00.0: xHCI host controller not responding, assume dead



xhci_hcd 0000:05:00.0: HC died; cleaning up




I googled and tried adding the following kernal parameters



intel_iommu=off


Some sites also mention



iommu


This unfortunately didn't help me anything.



I also tried to add:



pciehp pciehp_force=1


And tried to do



sudo modprobe pciehp pciehp_force=1


But Arch Linux complains that it doesn't find the kernel module pciehp.



I didn't find any information on how to install pciehp kernel module on Arch Linux. Some say, it is build into the kernel or something.



debug information:



kernel version: 4.16.6-1-ARCH



dmesg with debugging xhci_hcd enabled and with xhci_hcd greped



lspci -nn:



05:00.0 USB controller [0c03]: Renesas Technology Corp. uPD720202 USB 3.0 Host Controller [1912:0015] (rev 02)


dmesg (old without xhci_hcd-debugging and withouth grep









share|improve this question












share|improve this question




share|improve this question








edited May 12 at 8:42
























asked Apr 29 at 14:27









Arch Linux Tux

2491313




2491313







  • 1




    Please edit question with the line in lspci -nn that identifies the problematic controller card. Also edit question with any other messages related to this card that show up in dmesg. (Indent 4 spaces for proper formatting).
    – dirkt
    Apr 29 at 16:49










  • @dirkt I did! You may kindly edit the question posting an excerpt from the pastebin.
    – Arch Linux Tux
    Apr 29 at 17:34












  • 1




    Please edit question with the line in lspci -nn that identifies the problematic controller card. Also edit question with any other messages related to this card that show up in dmesg. (Indent 4 spaces for proper formatting).
    – dirkt
    Apr 29 at 16:49










  • @dirkt I did! You may kindly edit the question posting an excerpt from the pastebin.
    – Arch Linux Tux
    Apr 29 at 17:34







1




1




Please edit question with the line in lspci -nn that identifies the problematic controller card. Also edit question with any other messages related to this card that show up in dmesg. (Indent 4 spaces for proper formatting).
– dirkt
Apr 29 at 16:49




Please edit question with the line in lspci -nn that identifies the problematic controller card. Also edit question with any other messages related to this card that show up in dmesg. (Indent 4 spaces for proper formatting).
– dirkt
Apr 29 at 16:49












@dirkt I did! You may kindly edit the question posting an excerpt from the pastebin.
– Arch Linux Tux
Apr 29 at 17:34




@dirkt I did! You may kindly edit the question posting an excerpt from the pastebin.
– Arch Linux Tux
Apr 29 at 17:34










2 Answers
2






active

oldest

votes

















up vote
1
down vote













Hm. Unless I'm overlooking something, it looks like the controller is initialized twice:



[ 5.195136] xhci_hcd 0000:05:00.0: xHCI Host Controller
[ 5.195145] xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 3
[ 5.202621] xhci_hcd 0000:05:00.0: hcc params 0x014051cf hci version 0x100 quirks 0x00000090
....
[ 5.203568] xhci_hcd 0000:05:00.0: xHCI Host Controller
[ 5.203572] xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 4
[ 5.204014] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.


The Renesas Product Info seems to say that while there are two ports each for each USB 3.0/USB 2.0 legacy root hub, there's only one root hub, so I don't understand what's going on.



If two instances of xhci_hcd are trying to control the card at the same time, then of course this will go wrong.



Next thing I'd do is to look at the xhci_hcd source, and recompile with debugging support. This requires programming experience, so if you don't know how to do that, alternatively file a bug report on whatever kernel bugtracker handles xhci_hcd, even if the devs just tell you that I am stupid and the repeated initialization is normal.



Edit



Inspecting the debug messages, this here looks very odd:



[ 2.423207] xhci_hcd 0000:05:00.0: Finished xhci_run for USB2 roothub
[ 2.423420] xhci_hcd 0000:05:00.0: Endpoint 0x81 ep reset callback called
[ 2.423547] xhci_hcd 0000:05:00.0: set port power, actual port 0 status = 0x2a0
[ 2.423563] xhci_hcd 0000:05:00.0: set port power, actual port 1 status = 0x2a0
[ 2.423613] xhci_hcd 0000:05:00.0: xHCI Host Controller
[ 2.423616] xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 2
[ 2.423621] xhci_hcd 0000:05:00.0: // Turn on HC, cmd = 0x5.
[ 2.426468] xhci_hcd 0000:05:00.0: Finished xhci_run for USB3 roothub
[ 2.426630] xhci_hcd 0000:05:00.0: Endpoint 0x81 ep reset callback called
[ 2.426798] xhci_hcd 0000:05:00.0: set port power, actual port 0 status = 0x2a0
[ 2.426819] xhci_hcd 0000:05:00.0: set port power, actual port 1 status = 0x2a0
[ 2.426893] xhci_hcd 0000:05:00.0: remove, state 1
[ 2.427674] xhci_hcd 0000:05:00.0: USB bus 2 deregistered
[ 2.427731] xhci_hcd 0000:05:00.0: remove, state 1


So after initializing everything, a reset gets called on both the USB 2.0 and the USB 3.0 root hub. They get removed, and then the driver tries to initialize the whole thing again (which is the second initialization I saw). Only this time it fails hard.



In the kernel source code, function xhci_endpoint_reset has comments along the lines "We might need to implement the config ep cmd in xhci 4.8.1" and "For now just print debug to follow the situation".



So this is definitely a case for the kernel developers. Make sure to amend the bug report with the debug output.






share|improve this answer























  • The bug-report is now here. It worked now at least once (maybe through software update). I don't now if it will work continuously - i hope so. Do you mean this by debugging xhci_hcd? Thanks for your effort and help!
    – Arch Linux Tux
    May 5 at 16:06











  • It didn't help. It still does not work after reboot. I furthermore get the error-message [ 6.561655] psmouse serio1: synaptics: Unable to initialize device. and the mouse lags, when the express card is inserted, when it doesn't work.
    – Arch Linux Tux
    May 5 at 16:18











  • Yes, the link you gave for enabling the debugging is the right one. If you mean by "it didn't help" that enabling debugging didn't solve the problem: Of course it doesn't, it isn't meant to. But now you should have lots of debugging messages in dmesg that can help in narrowing down the problem. Put it in a pastebin so I can have a look. Unplug all USB devices you don't need when booting with debugging enabled, they'll only clutter up the log. The lagging is expected if the kernel is busy writing lots of messages.
    – dirkt
    May 6 at 4:35










  • No, I mean that it worked exactly once, I could stick a USB-drive to it and everything, but this was the only time. When I rebooted it didn't work anymore. I don't know why it worked and don't know why it doesn't work now anymore. I figured out, that my kernel has CONFIG_DYNAMIC_DEBUG enabled and found debugfs mounted rw, but I cannot write to it tough. It says permission denied, even though I am logged in as root. Do you know what the problem is and why I can't write to it debugfs as root with rw mounted?
    – Arch Linux Tux
    May 6 at 17:23











  • Debugfs exposes various "files" which are just interfaces to parts of the module. The majority of them are not writeable, and just give information. Some may be writeable, but it's not a good idea to write to them unless you exactly know what you are doing, which requires reading the module code. You can't create new files (this doesn't make any sense at all). But what we need is not debugfs access, what we need are more debugging messages in dmesg to get some idea what's happening.
    – dirkt
    May 7 at 6:10

















up vote
1
down vote













I'm having the same or a similar problem. Did open a thread here:
https://bbs.archlinux.org/viewtopic.php?pid=1784837



My testing came to the result, that it showed up with kernel 4.12.8-1-ARCH.
And in another laptop, this same card works - now with linux 4.15.15.






share|improve this answer

















  • 1




    I have kernel version 4.16.6-1-ARCH running.
    – Arch Linux Tux
    May 12 at 8:41










Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);








 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f440741%2finstall-usb-3-0-express-card-under-linux-arch-linux-tried-adding-kernel-param%23new-answer', 'question_page');

);

Post as a guest






























2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
1
down vote













Hm. Unless I'm overlooking something, it looks like the controller is initialized twice:



[ 5.195136] xhci_hcd 0000:05:00.0: xHCI Host Controller
[ 5.195145] xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 3
[ 5.202621] xhci_hcd 0000:05:00.0: hcc params 0x014051cf hci version 0x100 quirks 0x00000090
....
[ 5.203568] xhci_hcd 0000:05:00.0: xHCI Host Controller
[ 5.203572] xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 4
[ 5.204014] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.


The Renesas Product Info seems to say that while there are two ports each for each USB 3.0/USB 2.0 legacy root hub, there's only one root hub, so I don't understand what's going on.



If two instances of xhci_hcd are trying to control the card at the same time, then of course this will go wrong.



Next thing I'd do is to look at the xhci_hcd source, and recompile with debugging support. This requires programming experience, so if you don't know how to do that, alternatively file a bug report on whatever kernel bugtracker handles xhci_hcd, even if the devs just tell you that I am stupid and the repeated initialization is normal.



Edit



Inspecting the debug messages, this here looks very odd:



[ 2.423207] xhci_hcd 0000:05:00.0: Finished xhci_run for USB2 roothub
[ 2.423420] xhci_hcd 0000:05:00.0: Endpoint 0x81 ep reset callback called
[ 2.423547] xhci_hcd 0000:05:00.0: set port power, actual port 0 status = 0x2a0
[ 2.423563] xhci_hcd 0000:05:00.0: set port power, actual port 1 status = 0x2a0
[ 2.423613] xhci_hcd 0000:05:00.0: xHCI Host Controller
[ 2.423616] xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 2
[ 2.423621] xhci_hcd 0000:05:00.0: // Turn on HC, cmd = 0x5.
[ 2.426468] xhci_hcd 0000:05:00.0: Finished xhci_run for USB3 roothub
[ 2.426630] xhci_hcd 0000:05:00.0: Endpoint 0x81 ep reset callback called
[ 2.426798] xhci_hcd 0000:05:00.0: set port power, actual port 0 status = 0x2a0
[ 2.426819] xhci_hcd 0000:05:00.0: set port power, actual port 1 status = 0x2a0
[ 2.426893] xhci_hcd 0000:05:00.0: remove, state 1
[ 2.427674] xhci_hcd 0000:05:00.0: USB bus 2 deregistered
[ 2.427731] xhci_hcd 0000:05:00.0: remove, state 1


So after initializing everything, a reset gets called on both the USB 2.0 and the USB 3.0 root hub. They get removed, and then the driver tries to initialize the whole thing again (which is the second initialization I saw). Only this time it fails hard.



In the kernel source code, function xhci_endpoint_reset has comments along the lines "We might need to implement the config ep cmd in xhci 4.8.1" and "For now just print debug to follow the situation".



So this is definitely a case for the kernel developers. Make sure to amend the bug report with the debug output.






share|improve this answer























  • The bug-report is now here. It worked now at least once (maybe through software update). I don't now if it will work continuously - i hope so. Do you mean this by debugging xhci_hcd? Thanks for your effort and help!
    – Arch Linux Tux
    May 5 at 16:06











  • It didn't help. It still does not work after reboot. I furthermore get the error-message [ 6.561655] psmouse serio1: synaptics: Unable to initialize device. and the mouse lags, when the express card is inserted, when it doesn't work.
    – Arch Linux Tux
    May 5 at 16:18











  • Yes, the link you gave for enabling the debugging is the right one. If you mean by "it didn't help" that enabling debugging didn't solve the problem: Of course it doesn't, it isn't meant to. But now you should have lots of debugging messages in dmesg that can help in narrowing down the problem. Put it in a pastebin so I can have a look. Unplug all USB devices you don't need when booting with debugging enabled, they'll only clutter up the log. The lagging is expected if the kernel is busy writing lots of messages.
    – dirkt
    May 6 at 4:35










  • No, I mean that it worked exactly once, I could stick a USB-drive to it and everything, but this was the only time. When I rebooted it didn't work anymore. I don't know why it worked and don't know why it doesn't work now anymore. I figured out, that my kernel has CONFIG_DYNAMIC_DEBUG enabled and found debugfs mounted rw, but I cannot write to it tough. It says permission denied, even though I am logged in as root. Do you know what the problem is and why I can't write to it debugfs as root with rw mounted?
    – Arch Linux Tux
    May 6 at 17:23











  • Debugfs exposes various "files" which are just interfaces to parts of the module. The majority of them are not writeable, and just give information. Some may be writeable, but it's not a good idea to write to them unless you exactly know what you are doing, which requires reading the module code. You can't create new files (this doesn't make any sense at all). But what we need is not debugfs access, what we need are more debugging messages in dmesg to get some idea what's happening.
    – dirkt
    May 7 at 6:10














up vote
1
down vote













Hm. Unless I'm overlooking something, it looks like the controller is initialized twice:



[ 5.195136] xhci_hcd 0000:05:00.0: xHCI Host Controller
[ 5.195145] xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 3
[ 5.202621] xhci_hcd 0000:05:00.0: hcc params 0x014051cf hci version 0x100 quirks 0x00000090
....
[ 5.203568] xhci_hcd 0000:05:00.0: xHCI Host Controller
[ 5.203572] xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 4
[ 5.204014] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.


The Renesas Product Info seems to say that while there are two ports each for each USB 3.0/USB 2.0 legacy root hub, there's only one root hub, so I don't understand what's going on.



If two instances of xhci_hcd are trying to control the card at the same time, then of course this will go wrong.



Next thing I'd do is to look at the xhci_hcd source, and recompile with debugging support. This requires programming experience, so if you don't know how to do that, alternatively file a bug report on whatever kernel bugtracker handles xhci_hcd, even if the devs just tell you that I am stupid and the repeated initialization is normal.



Edit



Inspecting the debug messages, this here looks very odd:



[ 2.423207] xhci_hcd 0000:05:00.0: Finished xhci_run for USB2 roothub
[ 2.423420] xhci_hcd 0000:05:00.0: Endpoint 0x81 ep reset callback called
[ 2.423547] xhci_hcd 0000:05:00.0: set port power, actual port 0 status = 0x2a0
[ 2.423563] xhci_hcd 0000:05:00.0: set port power, actual port 1 status = 0x2a0
[ 2.423613] xhci_hcd 0000:05:00.0: xHCI Host Controller
[ 2.423616] xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 2
[ 2.423621] xhci_hcd 0000:05:00.0: // Turn on HC, cmd = 0x5.
[ 2.426468] xhci_hcd 0000:05:00.0: Finished xhci_run for USB3 roothub
[ 2.426630] xhci_hcd 0000:05:00.0: Endpoint 0x81 ep reset callback called
[ 2.426798] xhci_hcd 0000:05:00.0: set port power, actual port 0 status = 0x2a0
[ 2.426819] xhci_hcd 0000:05:00.0: set port power, actual port 1 status = 0x2a0
[ 2.426893] xhci_hcd 0000:05:00.0: remove, state 1
[ 2.427674] xhci_hcd 0000:05:00.0: USB bus 2 deregistered
[ 2.427731] xhci_hcd 0000:05:00.0: remove, state 1


So after initializing everything, a reset gets called on both the USB 2.0 and the USB 3.0 root hub. They get removed, and then the driver tries to initialize the whole thing again (which is the second initialization I saw). Only this time it fails hard.



In the kernel source code, function xhci_endpoint_reset has comments along the lines "We might need to implement the config ep cmd in xhci 4.8.1" and "For now just print debug to follow the situation".



So this is definitely a case for the kernel developers. Make sure to amend the bug report with the debug output.






share|improve this answer























  • The bug-report is now here. It worked now at least once (maybe through software update). I don't now if it will work continuously - i hope so. Do you mean this by debugging xhci_hcd? Thanks for your effort and help!
    – Arch Linux Tux
    May 5 at 16:06











  • It didn't help. It still does not work after reboot. I furthermore get the error-message [ 6.561655] psmouse serio1: synaptics: Unable to initialize device. and the mouse lags, when the express card is inserted, when it doesn't work.
    – Arch Linux Tux
    May 5 at 16:18











  • Yes, the link you gave for enabling the debugging is the right one. If you mean by "it didn't help" that enabling debugging didn't solve the problem: Of course it doesn't, it isn't meant to. But now you should have lots of debugging messages in dmesg that can help in narrowing down the problem. Put it in a pastebin so I can have a look. Unplug all USB devices you don't need when booting with debugging enabled, they'll only clutter up the log. The lagging is expected if the kernel is busy writing lots of messages.
    – dirkt
    May 6 at 4:35










  • No, I mean that it worked exactly once, I could stick a USB-drive to it and everything, but this was the only time. When I rebooted it didn't work anymore. I don't know why it worked and don't know why it doesn't work now anymore. I figured out, that my kernel has CONFIG_DYNAMIC_DEBUG enabled and found debugfs mounted rw, but I cannot write to it tough. It says permission denied, even though I am logged in as root. Do you know what the problem is and why I can't write to it debugfs as root with rw mounted?
    – Arch Linux Tux
    May 6 at 17:23











  • Debugfs exposes various "files" which are just interfaces to parts of the module. The majority of them are not writeable, and just give information. Some may be writeable, but it's not a good idea to write to them unless you exactly know what you are doing, which requires reading the module code. You can't create new files (this doesn't make any sense at all). But what we need is not debugfs access, what we need are more debugging messages in dmesg to get some idea what's happening.
    – dirkt
    May 7 at 6:10












up vote
1
down vote










up vote
1
down vote









Hm. Unless I'm overlooking something, it looks like the controller is initialized twice:



[ 5.195136] xhci_hcd 0000:05:00.0: xHCI Host Controller
[ 5.195145] xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 3
[ 5.202621] xhci_hcd 0000:05:00.0: hcc params 0x014051cf hci version 0x100 quirks 0x00000090
....
[ 5.203568] xhci_hcd 0000:05:00.0: xHCI Host Controller
[ 5.203572] xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 4
[ 5.204014] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.


The Renesas Product Info seems to say that while there are two ports each for each USB 3.0/USB 2.0 legacy root hub, there's only one root hub, so I don't understand what's going on.



If two instances of xhci_hcd are trying to control the card at the same time, then of course this will go wrong.



Next thing I'd do is to look at the xhci_hcd source, and recompile with debugging support. This requires programming experience, so if you don't know how to do that, alternatively file a bug report on whatever kernel bugtracker handles xhci_hcd, even if the devs just tell you that I am stupid and the repeated initialization is normal.



Edit



Inspecting the debug messages, this here looks very odd:



[ 2.423207] xhci_hcd 0000:05:00.0: Finished xhci_run for USB2 roothub
[ 2.423420] xhci_hcd 0000:05:00.0: Endpoint 0x81 ep reset callback called
[ 2.423547] xhci_hcd 0000:05:00.0: set port power, actual port 0 status = 0x2a0
[ 2.423563] xhci_hcd 0000:05:00.0: set port power, actual port 1 status = 0x2a0
[ 2.423613] xhci_hcd 0000:05:00.0: xHCI Host Controller
[ 2.423616] xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 2
[ 2.423621] xhci_hcd 0000:05:00.0: // Turn on HC, cmd = 0x5.
[ 2.426468] xhci_hcd 0000:05:00.0: Finished xhci_run for USB3 roothub
[ 2.426630] xhci_hcd 0000:05:00.0: Endpoint 0x81 ep reset callback called
[ 2.426798] xhci_hcd 0000:05:00.0: set port power, actual port 0 status = 0x2a0
[ 2.426819] xhci_hcd 0000:05:00.0: set port power, actual port 1 status = 0x2a0
[ 2.426893] xhci_hcd 0000:05:00.0: remove, state 1
[ 2.427674] xhci_hcd 0000:05:00.0: USB bus 2 deregistered
[ 2.427731] xhci_hcd 0000:05:00.0: remove, state 1


So after initializing everything, a reset gets called on both the USB 2.0 and the USB 3.0 root hub. They get removed, and then the driver tries to initialize the whole thing again (which is the second initialization I saw). Only this time it fails hard.



In the kernel source code, function xhci_endpoint_reset has comments along the lines "We might need to implement the config ep cmd in xhci 4.8.1" and "For now just print debug to follow the situation".



So this is definitely a case for the kernel developers. Make sure to amend the bug report with the debug output.






share|improve this answer















Hm. Unless I'm overlooking something, it looks like the controller is initialized twice:



[ 5.195136] xhci_hcd 0000:05:00.0: xHCI Host Controller
[ 5.195145] xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 3
[ 5.202621] xhci_hcd 0000:05:00.0: hcc params 0x014051cf hci version 0x100 quirks 0x00000090
....
[ 5.203568] xhci_hcd 0000:05:00.0: xHCI Host Controller
[ 5.203572] xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 4
[ 5.204014] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.


The Renesas Product Info seems to say that while there are two ports each for each USB 3.0/USB 2.0 legacy root hub, there's only one root hub, so I don't understand what's going on.



If two instances of xhci_hcd are trying to control the card at the same time, then of course this will go wrong.



Next thing I'd do is to look at the xhci_hcd source, and recompile with debugging support. This requires programming experience, so if you don't know how to do that, alternatively file a bug report on whatever kernel bugtracker handles xhci_hcd, even if the devs just tell you that I am stupid and the repeated initialization is normal.



Edit



Inspecting the debug messages, this here looks very odd:



[ 2.423207] xhci_hcd 0000:05:00.0: Finished xhci_run for USB2 roothub
[ 2.423420] xhci_hcd 0000:05:00.0: Endpoint 0x81 ep reset callback called
[ 2.423547] xhci_hcd 0000:05:00.0: set port power, actual port 0 status = 0x2a0
[ 2.423563] xhci_hcd 0000:05:00.0: set port power, actual port 1 status = 0x2a0
[ 2.423613] xhci_hcd 0000:05:00.0: xHCI Host Controller
[ 2.423616] xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 2
[ 2.423621] xhci_hcd 0000:05:00.0: // Turn on HC, cmd = 0x5.
[ 2.426468] xhci_hcd 0000:05:00.0: Finished xhci_run for USB3 roothub
[ 2.426630] xhci_hcd 0000:05:00.0: Endpoint 0x81 ep reset callback called
[ 2.426798] xhci_hcd 0000:05:00.0: set port power, actual port 0 status = 0x2a0
[ 2.426819] xhci_hcd 0000:05:00.0: set port power, actual port 1 status = 0x2a0
[ 2.426893] xhci_hcd 0000:05:00.0: remove, state 1
[ 2.427674] xhci_hcd 0000:05:00.0: USB bus 2 deregistered
[ 2.427731] xhci_hcd 0000:05:00.0: remove, state 1


So after initializing everything, a reset gets called on both the USB 2.0 and the USB 3.0 root hub. They get removed, and then the driver tries to initialize the whole thing again (which is the second initialization I saw). Only this time it fails hard.



In the kernel source code, function xhci_endpoint_reset has comments along the lines "We might need to implement the config ep cmd in xhci 4.8.1" and "For now just print debug to follow the situation".



So this is definitely a case for the kernel developers. Make sure to amend the bug report with the debug output.







share|improve this answer















share|improve this answer



share|improve this answer








edited May 9 at 19:37


























answered Apr 29 at 19:14









dirkt

14k2930




14k2930











  • The bug-report is now here. It worked now at least once (maybe through software update). I don't now if it will work continuously - i hope so. Do you mean this by debugging xhci_hcd? Thanks for your effort and help!
    – Arch Linux Tux
    May 5 at 16:06











  • It didn't help. It still does not work after reboot. I furthermore get the error-message [ 6.561655] psmouse serio1: synaptics: Unable to initialize device. and the mouse lags, when the express card is inserted, when it doesn't work.
    – Arch Linux Tux
    May 5 at 16:18











  • Yes, the link you gave for enabling the debugging is the right one. If you mean by "it didn't help" that enabling debugging didn't solve the problem: Of course it doesn't, it isn't meant to. But now you should have lots of debugging messages in dmesg that can help in narrowing down the problem. Put it in a pastebin so I can have a look. Unplug all USB devices you don't need when booting with debugging enabled, they'll only clutter up the log. The lagging is expected if the kernel is busy writing lots of messages.
    – dirkt
    May 6 at 4:35










  • No, I mean that it worked exactly once, I could stick a USB-drive to it and everything, but this was the only time. When I rebooted it didn't work anymore. I don't know why it worked and don't know why it doesn't work now anymore. I figured out, that my kernel has CONFIG_DYNAMIC_DEBUG enabled and found debugfs mounted rw, but I cannot write to it tough. It says permission denied, even though I am logged in as root. Do you know what the problem is and why I can't write to it debugfs as root with rw mounted?
    – Arch Linux Tux
    May 6 at 17:23











  • Debugfs exposes various "files" which are just interfaces to parts of the module. The majority of them are not writeable, and just give information. Some may be writeable, but it's not a good idea to write to them unless you exactly know what you are doing, which requires reading the module code. You can't create new files (this doesn't make any sense at all). But what we need is not debugfs access, what we need are more debugging messages in dmesg to get some idea what's happening.
    – dirkt
    May 7 at 6:10
















  • The bug-report is now here. It worked now at least once (maybe through software update). I don't now if it will work continuously - i hope so. Do you mean this by debugging xhci_hcd? Thanks for your effort and help!
    – Arch Linux Tux
    May 5 at 16:06











  • It didn't help. It still does not work after reboot. I furthermore get the error-message [ 6.561655] psmouse serio1: synaptics: Unable to initialize device. and the mouse lags, when the express card is inserted, when it doesn't work.
    – Arch Linux Tux
    May 5 at 16:18











  • Yes, the link you gave for enabling the debugging is the right one. If you mean by "it didn't help" that enabling debugging didn't solve the problem: Of course it doesn't, it isn't meant to. But now you should have lots of debugging messages in dmesg that can help in narrowing down the problem. Put it in a pastebin so I can have a look. Unplug all USB devices you don't need when booting with debugging enabled, they'll only clutter up the log. The lagging is expected if the kernel is busy writing lots of messages.
    – dirkt
    May 6 at 4:35










  • No, I mean that it worked exactly once, I could stick a USB-drive to it and everything, but this was the only time. When I rebooted it didn't work anymore. I don't know why it worked and don't know why it doesn't work now anymore. I figured out, that my kernel has CONFIG_DYNAMIC_DEBUG enabled and found debugfs mounted rw, but I cannot write to it tough. It says permission denied, even though I am logged in as root. Do you know what the problem is and why I can't write to it debugfs as root with rw mounted?
    – Arch Linux Tux
    May 6 at 17:23











  • Debugfs exposes various "files" which are just interfaces to parts of the module. The majority of them are not writeable, and just give information. Some may be writeable, but it's not a good idea to write to them unless you exactly know what you are doing, which requires reading the module code. You can't create new files (this doesn't make any sense at all). But what we need is not debugfs access, what we need are more debugging messages in dmesg to get some idea what's happening.
    – dirkt
    May 7 at 6:10















The bug-report is now here. It worked now at least once (maybe through software update). I don't now if it will work continuously - i hope so. Do you mean this by debugging xhci_hcd? Thanks for your effort and help!
– Arch Linux Tux
May 5 at 16:06





The bug-report is now here. It worked now at least once (maybe through software update). I don't now if it will work continuously - i hope so. Do you mean this by debugging xhci_hcd? Thanks for your effort and help!
– Arch Linux Tux
May 5 at 16:06













It didn't help. It still does not work after reboot. I furthermore get the error-message [ 6.561655] psmouse serio1: synaptics: Unable to initialize device. and the mouse lags, when the express card is inserted, when it doesn't work.
– Arch Linux Tux
May 5 at 16:18





It didn't help. It still does not work after reboot. I furthermore get the error-message [ 6.561655] psmouse serio1: synaptics: Unable to initialize device. and the mouse lags, when the express card is inserted, when it doesn't work.
– Arch Linux Tux
May 5 at 16:18













Yes, the link you gave for enabling the debugging is the right one. If you mean by "it didn't help" that enabling debugging didn't solve the problem: Of course it doesn't, it isn't meant to. But now you should have lots of debugging messages in dmesg that can help in narrowing down the problem. Put it in a pastebin so I can have a look. Unplug all USB devices you don't need when booting with debugging enabled, they'll only clutter up the log. The lagging is expected if the kernel is busy writing lots of messages.
– dirkt
May 6 at 4:35




Yes, the link you gave for enabling the debugging is the right one. If you mean by "it didn't help" that enabling debugging didn't solve the problem: Of course it doesn't, it isn't meant to. But now you should have lots of debugging messages in dmesg that can help in narrowing down the problem. Put it in a pastebin so I can have a look. Unplug all USB devices you don't need when booting with debugging enabled, they'll only clutter up the log. The lagging is expected if the kernel is busy writing lots of messages.
– dirkt
May 6 at 4:35












No, I mean that it worked exactly once, I could stick a USB-drive to it and everything, but this was the only time. When I rebooted it didn't work anymore. I don't know why it worked and don't know why it doesn't work now anymore. I figured out, that my kernel has CONFIG_DYNAMIC_DEBUG enabled and found debugfs mounted rw, but I cannot write to it tough. It says permission denied, even though I am logged in as root. Do you know what the problem is and why I can't write to it debugfs as root with rw mounted?
– Arch Linux Tux
May 6 at 17:23





No, I mean that it worked exactly once, I could stick a USB-drive to it and everything, but this was the only time. When I rebooted it didn't work anymore. I don't know why it worked and don't know why it doesn't work now anymore. I figured out, that my kernel has CONFIG_DYNAMIC_DEBUG enabled and found debugfs mounted rw, but I cannot write to it tough. It says permission denied, even though I am logged in as root. Do you know what the problem is and why I can't write to it debugfs as root with rw mounted?
– Arch Linux Tux
May 6 at 17:23













Debugfs exposes various "files" which are just interfaces to parts of the module. The majority of them are not writeable, and just give information. Some may be writeable, but it's not a good idea to write to them unless you exactly know what you are doing, which requires reading the module code. You can't create new files (this doesn't make any sense at all). But what we need is not debugfs access, what we need are more debugging messages in dmesg to get some idea what's happening.
– dirkt
May 7 at 6:10




Debugfs exposes various "files" which are just interfaces to parts of the module. The majority of them are not writeable, and just give information. Some may be writeable, but it's not a good idea to write to them unless you exactly know what you are doing, which requires reading the module code. You can't create new files (this doesn't make any sense at all). But what we need is not debugfs access, what we need are more debugging messages in dmesg to get some idea what's happening.
– dirkt
May 7 at 6:10












up vote
1
down vote













I'm having the same or a similar problem. Did open a thread here:
https://bbs.archlinux.org/viewtopic.php?pid=1784837



My testing came to the result, that it showed up with kernel 4.12.8-1-ARCH.
And in another laptop, this same card works - now with linux 4.15.15.






share|improve this answer

















  • 1




    I have kernel version 4.16.6-1-ARCH running.
    – Arch Linux Tux
    May 12 at 8:41














up vote
1
down vote













I'm having the same or a similar problem. Did open a thread here:
https://bbs.archlinux.org/viewtopic.php?pid=1784837



My testing came to the result, that it showed up with kernel 4.12.8-1-ARCH.
And in another laptop, this same card works - now with linux 4.15.15.






share|improve this answer

















  • 1




    I have kernel version 4.16.6-1-ARCH running.
    – Arch Linux Tux
    May 12 at 8:41












up vote
1
down vote










up vote
1
down vote









I'm having the same or a similar problem. Did open a thread here:
https://bbs.archlinux.org/viewtopic.php?pid=1784837



My testing came to the result, that it showed up with kernel 4.12.8-1-ARCH.
And in another laptop, this same card works - now with linux 4.15.15.






share|improve this answer













I'm having the same or a similar problem. Did open a thread here:
https://bbs.archlinux.org/viewtopic.php?pid=1784837



My testing came to the result, that it showed up with kernel 4.12.8-1-ARCH.
And in another laptop, this same card works - now with linux 4.15.15.







share|improve this answer













share|improve this answer



share|improve this answer











answered May 11 at 19:09









whitesnow

111




111







  • 1




    I have kernel version 4.16.6-1-ARCH running.
    – Arch Linux Tux
    May 12 at 8:41












  • 1




    I have kernel version 4.16.6-1-ARCH running.
    – Arch Linux Tux
    May 12 at 8:41







1




1




I have kernel version 4.16.6-1-ARCH running.
– Arch Linux Tux
May 12 at 8:41




I have kernel version 4.16.6-1-ARCH running.
– Arch Linux Tux
May 12 at 8:41












 

draft saved


draft discarded


























 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f440741%2finstall-usb-3-0-express-card-under-linux-arch-linux-tried-adding-kernel-param%23new-answer', 'question_page');

);

Post as a guest













































































Popular posts from this blog

Peggy Mitchell

Palaiologos

The Forum (Inglewood, California)