On Sat, Nov 10, 2012 at 02:30:36PM +0330, A Sh wrote: > > Ah, then you probably have the xHCI driver built-in, not built as a > > module. > > What does it mean? Wow, I googled around, and even though I know what search terms to look for, there's really no good documentation on this question. I'll add a page to kernelnewbies.org. "Built-in" means that the xHCI driver is built into the core kernel binary, vmlinux. Instead of compiling it into a stand-alone module that can be unloaded and reloaded at any time, the driver is built into the binary that gets executed at boot time. Many people build in drivers in order to make their systems boot faster. Other people want to build drivers as modules in order to make sure they can unload and reload them whenever they want. You can choose to make a driver built-in or a module by running `make menuconfig` in the kernel source tree, finding your driver, and choosing 'y' (for built-in) or 'm' (for module). If you look in your .config file for the kernel you compiled (it should be in the kernel source directory), you will see a CONFIG_USB_XHCI_HCD line. If that line reads CONFIG_USB_XHCI_HCD=m then the xHCI driver is configured to be compiled as a module. If instead the line reads CONFIG_USB_XHCI_HCD=y then the xHCI driver is built-in to the vmlinux binary. I hope this answered your question! Sarah Sharp > On Sat, Nov 10, 2012 at 12:53 AM, Sarah Sharp <sarah.a.sharp@xxxxxxxxxxxxxxx > > wrote: > > > On Fri, Nov 09, 2012 at 07:32:08AM +0330, A Sh wrote: > > > No, it's not the case. > > > > > > There is no xhci.....ko either xhci.ko or xhci-hcd.ko. > > > > Ah, then you probably have the xHCI driver built-in, not built as a > > module. > > > > > Have you compiled any of 3.x recently? (if not you can find official > > > package for ubuntu here: > > > http://packages.ubuntu.com/precise/linux-image-3.2.0-32-generic) > > > > I build 3.x from the mainline kernel source, not from Ubuntu packages. > > > > Sarah Sharp > > > > > On Thu, Nov 8, 2012 at 9:03 PM, Sarah Sharp > > > <sarah.a.sharp@xxxxxxxxxxxxxxx>wrote: > > > > > > > On Thu, Nov 08, 2012 at 01:28:32PM +0330, A Sh wrote: > > > > > what about xhci.ko? > > > > > > > > The module got renamed from xhci.ko to xhci-hcd.ko in 2.6.34. > > > > > > > > Sarah Sharp > > > > > > > > > > > > > > > > > > > On Wed, Nov 7, 2012 at 10:09 PM, Sarah Sharp > > > > > <sarah.a.sharp@xxxxxxxxxxxxxxx>wrote: > > > > > > > > > > > On Wed, Nov 07, 2012 at 01:56:49PM +0330, A Sh wrote: > > > > > > > 1. There is no xhci-hcd.ko at least for 3.2 kernels( I'm sure > > either > > > > for > > > > > > > community compiled kernels or self-compiled kernels.) but it's > > the > > > > module > > > > > > > responsible for usb3 and it's being used by kernel (for example > > > > command > > > > > > > dmesg | grep xhci > > > > > > > gives a lot of xhci related messages) > > > > > > > may be it's compiled under ehci.ko or some other modules > > together. > > > > > > > If you compile kernel you'll see that.(there was xhci.ko or > > > > xhci-hcd.ko > > > > > > in > > > > > > > 2.6 versions but not in 3.2 ones) > > > > > > > 2. > > > > > > > > We try to avoid module parameters, because it's confusing. > > Also, > > > > > > distros > > > > > > > > will always leave them at the default, which means you might as > > > > well > > > > > > not > > > > > > > > have them at all. Any module parameter besides the default > > isn't > > > > going > > > > > > > > to be well-tested either. > > > > > > > > > > > > > > > > I know it's a pain to recompile a kernel, but it doesn't make > > > > sense to > > > > > > > > expose every single option to userspace. So we pick a sane > > > > default, > > > > > > and > > > > > > > > work around any quirks in the kernel driver. > > > > > > > > > > > > > > Yes this should be the routine procedure but not when there is a > > > > bunch of > > > > > > > hardware with this issue. > > > > > > > > > > > > It's really only the Fresco Logic vendor that has this issue. That > > > > > > probably means we should just add the quirk for all their > > chipsets, but > > > > > > I wanted to give them time to fix the issue (and they were aware > > of the > > > > > > issue when I talked to them about it). So far, they're on strike > > two > > > > > > for chipset revisions. If I hear about a third revision that needs > > > > this > > > > > > quirk, I'll blacklist MSI/MSI-X for all Fresco Logic chipsets. > > > > > > > > > > > > Sarah Sharp > > > > > > > > > > > > > On Tue, Nov 6, 2012 at 9:32 PM, Sarah Sharp > > > > > > > <sarah.a.sharp@xxxxxxxxxxxxxxx>wrote: > > > > > > > > > > > > > > > On Tue, Nov 06, 2012 at 11:03:10AM +0330, A Sh wrote: > > > > > > > > > > So you patched 3.2 with the patch I sent you, and it > > worked? > > > > > > > > > > > > > > > > > > yes, I did. > > > > > > > > > > > > > > > > Ok, great, I will send that patch upstream. > > > > > > > > > > > > > > > > > > You mean this one? > > > > > > > > > > > > > > > > > > >> I had also a suggestion: > > > > > > > > > >> make xhci module work in three mode: > > > > > > > > > >> 1. without msi/msi-X > > > > > > > > > >> 2. with msi and without msi-x > > > > > > > > > >> 3. with both msi and msi-x > > > > > > > > > > > > > > > > > > > That is basically what the driver does (aside from the fact > > > > that > > > > > > MSI > > > > > > > > and > > > > > > > > > > MSI-X cannot be enabled at the same time, you can only have > > > > one or > > > > > > the > > > > > > > > > > other). The driver tries to enable MSI-X, and falls back > > to > > > > MSI if > > > > > > > > that > > > > > > > > > > fails. If MSI enabling fails, it falls back to legacy IRQ > > (no > > > > MSI > > > > > > or > > > > > > > > > > MSI-X). Your hardware is just broken because it reports > > that > > > > it > > > > > > can > > > > > > > > > > provide MSI, and then fails to do so. > > > > > > > > > > > > > > > > > > Yes I was referring to that part, but I mean it can be > > possible > > > > to > > > > > > > > > implement something (module modes for instance) by which > > user can > > > > > > force > > > > > > > > > module to stop using for example MSI-X with these commands: > > > > > > > > > > > > > > > > > > # sudo rmmod xhci-hcd > > > > > > > > > # cd /lib/module/ 'kernel version' /kernel/drivers/usb/host > > > > > > > > > # sudo insmod xhci.ko interrupt_mode=1 (I don't know which > > > > module we > > > > > > > > should > > > > > > > > > implement this for as I see no xhci.ko! ) > > > > > > > > > > > > > > > > It's drivers/usb/host/xhci-hcd.ko. > > > > > > > > > > > > > > > > > where interrupt_mode can be 0,1,2 and each one is one of > > > > explained > > > > > > > > > conditions. > > > > > > > > > > > > > > > > We try to avoid module parameters, because it's confusing. > > Also, > > > > > > distros > > > > > > > > will always leave them at the default, which means you might as > > > > well > > > > > > not > > > > > > > > have them at all. Any module parameter besides the default > > isn't > > > > going > > > > > > > > to be well-tested either. > > > > > > > > > > > > > > > > I know it's a pain to recompile a kernel, but it doesn't make > > > > sense to > > > > > > > > expose every single option to userspace. So we pick a sane > > > > default, > > > > > > and > > > > > > > > work around any quirks in the kernel driver. > > > > > > > > > > > > > > > > Sarah Sharp > > > > > > > > > > > > > > > > > > > > > > > > > > On Mon, Nov 5, 2012 at 9:13 PM, Sarah Sharp > > > > > > > > > <sarah.a.sharp@xxxxxxxxxxxxxxx>wrote: > > > > > > > > > > > > > > > > > > > On Sat, Nov 03, 2012 at 09:42:18AM +0330, A Sh wrote: > > > > > > > > > > > Hello Ms.Sharp, > > > > > > > > > > > > > > > > > > > > > > I checked with 3.2 kernel(provided with my official > > > > distribution > > > > > > > > repos) > > > > > > > > > > and > > > > > > > > > > > it worked. > > > > > > > > > > > > > > > > > > > > So you patched 3.2 with the patch I sent you, and it > > worked? > > > > > > > > > > > > > > > > > > > > > Do you have any idea when it will be available in > > official > > > > distro > > > > > > > > repos? > > > > > > > > > > > > > > > > > > > > I have no control over *when* it gets in, but the patch > > will be > > > > > > marked > > > > > > > > > > for stable, and distros will be notified to pick it up. > > > > > > > > > > > > > > > > > > > > > By the way what about making the module work in three > > modes > > > > as I > > > > > > told > > > > > > > > > > > before, this way we don't have to apply patches everytime > > > > there > > > > > > is > > > > > > > > such > > > > > > > > > > > hardwares. > > > > > > > > > > > > > > > > > > > > You mean this one? > > > > > > > > > > > > > > > > > > > > > I had also a suggestion: > > > > > > > > > > > make xhci module work in three mode: > > > > > > > > > > > 1. without msi/msi-X > > > > > > > > > > > 2. with msi and without msi-x > > > > > > > > > > > 3. with both msi and msi-x > > > > > > > > > > > > > > > > > > > > That is basically what the driver does (aside from the fact > > > > that > > > > > > MSI > > > > > > > > and > > > > > > > > > > MSI-X cannot be enabled at the same time, you can only have > > > > one or > > > > > > the > > > > > > > > > > other). The driver tries to enable MSI-X, and falls back > > to > > > > MSI if > > > > > > > > that > > > > > > > > > > fails. If MSI enabling fails, it falls back to legacy IRQ > > (no > > > > MSI > > > > > > or > > > > > > > > > > MSI-X). Your hardware is just broken because it reports > > that > > > > it > > > > > > can > > > > > > > > > > provide MSI, and then fails to do so. > > > > > > > > > > > > > > > > > > > > Sarah Sharp > > > > > > > > > > > > > > > > > > > > > On Fri, Oct 19, 2012 at 12:59 AM, Sarah Sharp < > > > > > > > > > > sarah.a.sharp@xxxxxxxxxxxxxxx > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > On Thu, Oct 18, 2012 at 08:15:57AM +0330, A Sh wrote: > > > > > > > > > > > > > You told you will send me directions to compile a > > custom > > > > > > kernel. > > > > > > > > > > > > > > > > > > > > > > > > Ok, here's some instructions for how to compile a > > custom > > > > > > kernel: > > > > > > > > > > > > > > > > > > > > > > > > http://kernelnewbies.org/KernelBuild > > > > > > > > > > > > > > > > > > > > > > > > Please download the latest stable kernel (currently > > > > v3.6.2), > > > > > > patch > > > > > > > > it > > > > > > > > > > > > with the attached patch, compile, and reboot. Let me > > know > > > > if > > > > > > you > > > > > > > > have > > > > > > > > > > > > any questions about the directions. > > > > > > > > > > > > > > > > > > > > > > > > > Is it necessary to compile the whole kernel or it's > > > > possible > > > > > > to > > > > > > > > only > > > > > > > > > > > > build > > > > > > > > > > > > > related modules and parts? > > > > > > > > > > > > > > > > > > > > > > > > Unfortunately, for the first time, you'll need to > > > > re-compile > > > > > > the > > > > > > > > whole > > > > > > > > > > > > kernel. Later on, you can use the directions in the > > "Tips > > > > and > > > > > > > > Tricks" > > > > > > > > > > > > sections to just compile one module, like the xHCI > > driver. > > > > > > > > > > > > > > > > > > > > > > > > > By the way my notebook isn't with me I won't be able > > to > > > > try > > > > > > this > > > > > > > > > > perhaps > > > > > > > > > > > > in > > > > > > > > > > > > > two weeks so sorry for delay in advance. > > > > > > > > > > > > > > > > > > > > > > > > Ok. Let me know how it goes. > > > > > > > > > > > > > > > > > > > > > > > > Sarah Sharp > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Oct 18, 2012 at 12:30 AM, Sarah Sharp < > > > > > > > > > > > > sarah.a.sharp@xxxxxxxxxxxxxxx > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > Hi Ali, > > > > > > > > > > > > > > > > > > > > > > > > > > > > Sorry for the long response time! Can you try to > > > > apply the > > > > > > > > > > attached > > > > > > > > > > > > > > patch, recompile your kernel, and see if it fixes > > your > > > > > > issues? > > > > > > > > > > > > > > > > > > > > > > > > > > > > Thanks, > > > > > > > > > > > > > > Sarah Sharp > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Wed, Oct 17, 2012 at 03:51:30PM +0330, A Sh > > wrote: > > > > > > > > > > > > > > > Excuse me Ms.Sharp, > > > > > > > > > > > > > > > did you recieve my message. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I had also a suggestion: > > > > > > > > > > > > > > > make xhci module work in three mode: > > > > > > > > > > > > > > > 1. without msi/msi-X > > > > > > > > > > > > > > > 2. with msi and without msi-x > > > > > > > > > > > > > > > 3. with both msi and msi-x > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Mon, Oct 1, 2012 at 1:48 PM, A Sh < > > > > > > smr.ash1991@xxxxxxxxx> > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hello Ms.Sharp. > > > > > > > > > > > > > > > > You have requested “ lspci -vvv -n ” output. > > You > > > > can > > > > > > find > > > > > > > > it in > > > > > > > > > > > > > > > > attachments. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I think the related part is: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > 04:00.0 > > > > > > > > > > > > > > > > *0c03: 1b73:1400* (rev 01) (prog-if 30 [XHCI]) > > > > > > > > > > > > > > > > Subsystem: 1d5c:1000 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Physical Slot: 3 > > > > > > > > > > > > > > > > Control: I/O+ Mem+ BusMaster+ SpecCycle- > > > > MemWINV- > > > > > > > > VGASnoop- > > > > > > > > > > > > ParErr- > > > > > > > > > > > > > > > > Stepping- SERR- FastB2B- DisINTx+ > > > > > > > > > > > > > > > > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- > > > > > > DEVSEL=fast > > > > > > > > > > >TAbort- > > > > > > > > > > > > > > > > <TAbort- <MAbort- >SERR- <PERR- INTx- > > > > > > > > > > > > > > > > Latency: 0, Cache Line Size: 64 bytes > > > > > > > > > > > > > > > > Interrupt: pin A routed to IRQ 51 > > > > > > > > > > > > > > > > Region 0: Memory at d4600000 (32-bit, > > > > > > non-prefetchable) > > > > > > > > > > > > [size=64K] > > > > > > > > > > > > > > > > Capabilities: [50] Power Management > > version 3 > > > > > > > > > > > > > > > > Flags: PMEClk- DSI- D1- D2- > > AuxCurrent=0mA > > > > > > > > > > > > > > > > PME(D0+,D1-,D2-,D3hot+,D3cold-) > > > > > > > > > > > > > > > > Status: D0 NoSoftRst- PME-Enable- > > DSel=0 > > > > > > DScale=0 > > > > > > > > PME- > > > > > > > > > > > > > > > > Capabilities: [68] MSI: Enable+ Count=1/1 > > > > Maskable- > > > > > > > > 64bit+ > > > > > > > > > > > > > > > > Address: 00000000feeff00c Data: 41b1 > > > > > > > > > > > > > > > > Capabilities: [80] Express (v1) Endpoint, > > MSI > > > > 00 > > > > > > > > > > > > > > > > DevCap: MaxPayload 128 bytes, > > PhantFunc > > > > 0, > > > > > > > > Latency > > > > > > > > > > L0s > > > > > > > > > > > > > > <2us, L1 > > > > > > > > > > > > > > > > <32us > > > > > > > > > > > > > > > > ExtTag- AttnBtn- AttnInd- PwrInd- > > RBE+ > > > > > > FLReset- > > > > > > > > > > > > > > > > DevCtl: Report errors: Correctable- > > > > > > Non-Fatal- > > > > > > > > > > Fatal- > > > > > > > > > > > > > > > > Unsupported- > > > > > > > > > > > > > > > > RlxdOrd+ ExtTag- PhantFunc- AuxPwr- > > > > > > NoSnoop+ > > > > > > > > > > > > > > > > MaxPayload 128 bytes, MaxReadReq > > 512 > > > > bytes > > > > > > > > > > > > > > > > DevSta: CorrErr- UncorrErr- > > FatalErr- > > > > > > UnsuppReq- > > > > > > > > > > AuxPwr- > > > > > > > > > > > > > > > > TransPend- > > > > > > > > > > > > > > > > LnkCap: Port #0, Speed 2.5GT/s, > > Width > > > > x1, > > > > > > ASPM > > > > > > > > L0s > > > > > > > > > > L1, > > > > > > > > > > > > > > Latency > > > > > > > > > > > > > > > > L0 unlimited, L1 unlimited > > > > > > > > > > > > > > > > ClockPM- Surprise- LLActRep- BwNot- > > > > > > > > > > > > > > > > LnkCtl: ASPM Disabled; RCB 64 bytes > > > > > > Disabled- > > > > > > > > > > Retrain- > > > > > > > > > > > > > > CommClk+ > > > > > > > > > > > > > > > > ExtSynch- ClockPM- AutWidDis- > > BWInt- > > > > > > AutBWInt- > > > > > > > > > > > > > > > > LnkSta: Speed 2.5GT/s, Width x1, > > TrErr- > > > > > > Train- > > > > > > > > > > SlotClk+ > > > > > > > > > > > > > > > > DLActive- BWMgmt- ABWMgmt- > > > > > > > > > > > > > > > > Kernel driver in use: xhci_hcd > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Your directions about compiling a custom > > kernel is > > > > > > > > appreciated! > > > > > > > > > > > > > > > > By the way I have sent a message like this from > > > > another > > > > > > > > > > address. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Thanks for your help. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Mon, Sep 17, 2012 at 5:06 PM, A Sh < > > > > > > > > smr.ash1991@xxxxxxxxx> > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >> My laptop isn't with me now and it takes some > > time > > > > > > (about > > > > > > > > 2 > > > > > > > > > > or 3 > > > > > > > > > > > > > > weeks! > > > > > > > > > > > > > > > >> probably) for me to send you what you have > > > > requested. > > > > > > > > > > > > > > > >> And I don't have much experience on compiling > > a > > > > custom > > > > > > > > kernel > > > > > > > > > > so > > > > > > > > > > > > your > > > > > > > > > > > > > > > >> directions are appreciated. > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > >> Thanks for your help. > > > > > > > > > > > > > > > >> Ali > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > >> On Sat, Sep 15, 2012 at 12:53 AM, Sarah Sharp > > < > > > > > > > > > > > > > > > >> sarah.a.sharp@xxxxxxxxxxxxxxx> wrote: > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > >>> On Thu, Aug 30, 2012 at 11:51:54AM +0430, A > > Sh > > > > wrote: > > > > > > > > > > > > > > > >>> > Hello Ms.Sharp > > > > > > > > > > > > > > > >>> > > > > > > > > > > > > > > > >>> Greetings! Do you go by "A"? Your mail > > > > signature > > > > > > isn't > > > > > > > > very > > > > > > > > > > > > clear. > > > > > > > > > > > > > > :) > > > > > > > > > > > > > > > >>> > > > > > > > > > > > > > > > >>> > When I plug a usb Flash Drive or DVB-T to > > my > > > > USB > > > > > > 3.0 > > > > > > > > Port > > > > > > > > > > I get > > > > > > > > > > > > > > > >>> following > > > > > > > > > > > > > > > >>> > and nothing happens(USB Device isn't > > > > Recognized): > > > > > > > > > > > > > > > >>> > > > > > > > > > > > > > > > > >>> > do_IRQ: 3.176 No irq handler for > > vector > > > > (irq > > > > > > -1) > > > > > > > > > > > > > > > >>> > > > > > > > > > > > > > > > > >>> > I'm using linux kernel 3.2.0-29-generic > > from > > > > > > official > > > > > > > > > > ubuntu > > > > > > > > > > > > > > precise > > > > > > > > > > > > > > > >>> > (12.04) repository. > > > > > > > > > > > > > > > >>> > > > > > > > > > > > > > > > > >>> > The related parts of lspci -vvv, lsusb > > -vvv and > > > > > > dmesg > > > > > > > > > > outputs > > > > > > > > > > > > > > are(you > > > > > > > > > > > > > > > >>> can > > > > > > > > > > > > > > > >>> > find the complete outputs in attachments): > > > > > > > > > > > > > > > >>> > > > > > > > > > > > > > > > > >>> > *------> lspci -vvv (related part):* > > > > > > > > > > > > > > > >>> > > > > > > > > > > > > > > > > >>> > > > > > > > > > > > > > > > > >>> > 04:00.0 USB controller: Fresco Logic > > Device > > > > 1400 > > > > > > (rev > > > > > > > > 01) > > > > > > > > > > > > > > (prog-if 30 > > > > > > > > > > > > > > > >>> > [XHCI]) > > > > > > > > > > > > > > > >>> > > > > > > > > > > > > > > > >>> Can you please send me the output of `sudo > > lspci > > > > -vvv > > > > > > > > -n`? I > > > > > > > > > > > > need > > > > > > > > > > > > > > the > > > > > > > > > > > > > > > >>> PCI vendor and device ID, which this version > > of > > > > lspci > > > > > > > > doesn't > > > > > > > > > > > > > > provide. > > > > > > > > > > > > > > > >>> > > > > > > > > > > > > > > > >>> I'm wondering if you have a Fresco Logic host > > > > that > > > > > > > > doesn't > > > > > > > > > > > > support > > > > > > > > > > > > > > MSI, > > > > > > > > > > > > > > > >>> even though it claims to (see the MSI field > > in > > > > the > > > > > > > > > > Capabilities > > > > > > > > > > > > > > lines): > > > > > > > > > > > > > > > >>> > > > > > > > > > > > > > > > >>> > 04:00.0 USB controller: Fresco Logic Device > > > > 1400 > > > > > > (rev > > > > > > > > 01) > > > > > > > > > > > > (prog-if > > > > > > > > > > > > > > 30 > > > > > > > > > > > > > > > >>> [XHCI]) > > > > > > > > > > > > > > > >>> > Subsystem: Device 1d5c:1000 > > > > > > > > > > > > > > > >>> > Physical Slot: 3 > > > > > > > > > > > > > > > >>> > Control: I/O+ Mem+ BusMaster+ > > SpecCycle- > > > > > > MemWINV- > > > > > > > > > > > > VGASnoop- > > > > > > > > > > > > > > > >>> ParErr- Stepping- SERR- FastB2B- DisINTx+ > > > > > > > > > > > > > > > >>> > Status: Cap+ 66MHz- UDF- FastB2B- > > ParErr- > > > > > > > > DEVSEL=fast > > > > > > > > > > > > > > >TAbort- > > > > > > > > > > > > > > > >>> <TAbort- <MAbort- >SERR- <PERR- INTx- > > > > > > > > > > > > > > > >>> > Latency: 0, Cache Line Size: 64 bytes > > > > > > > > > > > > > > > >>> > Interrupt: pin A routed to IRQ 51 > > > > > > > > > > > > > > > >>> > Region 0: Memory at d4600000 (32-bit, > > > > > > > > > > non-prefetchable) > > > > > > > > > > > > > > > >>> [size=64K] > > > > > > > > > > > > > > > >>> > Capabilities: [50] Power Management > > > > version 3 > > > > > > > > > > > > > > > >>> > Flags: PMEClk- DSI- D1- D2- > > > > > > > > AuxCurrent=0mA > > > > > > > > > > > > > > > >>> PME(D0+,D1-,D2-,D3hot+,D3cold-) > > > > > > > > > > > > > > > >>> > Status: D0 NoSoftRst- > > PME-Enable- > > > > > > DSel=0 > > > > > > > > > > DScale=0 > > > > > > > > > > > > > > PME- > > > > > > > > > > > > > > > >>> > Capabilities: [68] MSI: Enable+ > > Count=1/1 > > > > > > > > Maskable- > > > > > > > > > > > > 64bit+ > > > > > > > > > > > > > > > >>> > Address: 00000000feeff00c > > Data: > > > > 41b1 > > > > > > > > > > > > > > > >>> > Capabilities: [80] Express (v1) > > Endpoint, > > > > > > MSI 00 > > > > > > > > > > > > > > > >>> > DevCap: MaxPayload 128 bytes, > > > > > > PhantFunc > > > > > > > > 0, > > > > > > > > > > > > Latency > > > > > > > > > > > > > > L0s > > > > > > > > > > > > > > > >>> <2us, L1 <32us > > > > > > > > > > > > > > > >>> > ExtTag- AttnBtn- > > AttnInd- > > > > > > PwrInd- > > > > > > > > > > RBE+ > > > > > > > > > > > > > > FLReset- > > > > > > > > > > > > > > > >>> > DevCtl: Report errors: > > > > Correctable- > > > > > > > > > > Non-Fatal- > > > > > > > > > > > > Fatal- > > > > > > > > > > > > > > > >>> Unsupported- > > > > > > > > > > > > > > > >>> > RlxdOrd+ ExtTag- > > > > PhantFunc- > > > > > > > > AuxPwr- > > > > > > > > > > > > NoSnoop+ > > > > > > > > > > > > > > > >>> > MaxPayload 128 bytes, > > > > > > MaxReadReq > > > > > > > > 512 > > > > > > > > > > > > bytes > > > > > > > > > > > > > > > >>> > DevSta: CorrErr- UncorrErr- > > > > FatalErr- > > > > > > > > > > UnsuppReq- > > > > > > > > > > > > > > AuxPwr- > > > > > > > > > > > > > > > >>> TransPend- > > > > > > > > > > > > > > > >>> > LnkCap: Port #0, Speed > > 2.5GT/s, > > > > > > Width x1, > > > > > > > > > > ASPM > > > > > > > > > > > > L0s > > > > > > > > > > > > > > L1, > > > > > > > > > > > > > > > >>> Latency L0 unlimited, L1 unlimited > > > > > > > > > > > > > > > >>> > ClockPM- Surprise- > > > > LLActRep- > > > > > > > > BwNot- > > > > > > > > > > > > > > > >>> > LnkCtl: ASPM Disabled; RCB 64 > > > > bytes > > > > > > > > Disabled- > > > > > > > > > > > > > > Retrain- > > > > > > > > > > > > > > > >>> CommClk+ > > > > > > > > > > > > > > > >>> > ExtSynch- ClockPM- > > > > AutWidDis- > > > > > > > > BWInt- > > > > > > > > > > > > > > AutBWInt- > > > > > > > > > > > > > > > >>> > LnkSta: Speed 2.5GT/s, Width > > x1, > > > > > > TrErr- > > > > > > > > > > Train- > > > > > > > > > > > > > > SlotClk+ > > > > > > > > > > > > > > > >>> DLActive- BWMgmt- ABWMgmt- > > > > > > > > > > > > > > > >>> > Kernel driver in use: xhci_hcd > > > > > > > > > > > > > > > >>> > > > > > > > > > > > > > > > >>> I think the dmesg shows that MSI is enabled > > for > > > > the > > > > > > host > > > > > > > > > > > > controller: > > > > > > > > > > > > > > > >>> > > > > > > > > > > > > > > > >>> > [ 1.988493] xhci_hcd 0000:04:00.0: PCI > > INT > > > > A -> > > > > > > GSI > > > > > > > > 19 > > > > > > > > > > > > (level, > > > > > > > > > > > > > > low) > > > > > > > > > > > > > > > >>> -> IRQ 19 > > > > > > > > > > > > > > > >>> > [ 1.988529] xhci_hcd 0000:04:00.0: > > setting > > > > > > latency > > > > > > > > > > timer to > > > > > > > > > > > > 64 > > > > > > > > > > > > > > > >>> > [ 1.988537] xhci_hcd 0000:04:00.0: xHCI > > Host > > > > > > > > Controller > > > > > > > > > > > > > > > >>> > [ 1.988604] xhci_hcd 0000:04:00.0: new > > USB > > > > bus > > > > > > > > > > registered, > > > > > > > > > > > > > > assigned > > > > > > > > > > > > > > > >>> bus number 3 > > > > > > > > > > > > > > > >>> > [ 2.109283] xhci_hcd 0000:04:00.0: irq > > 19, > > > > io > > > > > > mem > > > > > > > > > > 0xd4600000 > > > > > > > > > > > > > > > >>> > [ 2.109363] xhci_hcd 0000:04:00.0: irq > > 51 > > > > for > > > > > > > > MSI/MSI-X > > > > > > > > > > > > > > > >>> > > > > > > > > > > > > > > > >>> But you're getting an unhandled IRQ, so this > > > > Fresco > > > > > > > > Logic may > > > > > > > > > > > > need a > > > > > > > > > > > > > > > >>> quirk like the previous generation to avoid > > MSI. > > > > > > I'll > > > > > > > > need > > > > > > > > > > the > > > > > > > > > > > > > > vendor > > > > > > > > > > > > > > > >>> and device ID from the lspci to generate a > > new > > > > patch > > > > > > for > > > > > > > > you > > > > > > > > > > to > > > > > > > > > > > > test. > > > > > > > > > > > > > > > >>> > > > > > > > > > > > > > > > >>> Do you know how to compile a custom kernel? > > If > > > > not, > > > > > > I'll > > > > > > > > > > send > > > > > > > > > > > > you > > > > > > > > > > > > > > some > > > > > > > > > > > > > > > >>> directions. > > > > > > > > > > > > > > > >>> > > > > > > > > > > > > > > > >>> Sarah Sharp > > > > > > > > > > > > > > > >>> > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
