Re: ASMedia USB 3.x host controllers triggering EEH on POWER9

2020-07-17 Thread Oliver O'Halloran
On Fri, Jul 17, 2020 at 8:10 PM Forest Crossman wrote: > > > From word 2 of the PEST entry the faulting DMA address is: > > 0x203974c0. That address is interesting since it looks a lot > > like a memory address on the 2nd chip, but it doesn't have bit 59 set > > so TVE#0 is used to

Re: ASMedia USB 3.x host controllers triggering EEH on POWER9

2020-07-17 Thread Forest Crossman
> In the future you can use this script to automate some of the tedium > of parsing the eeh dumps: > https://patchwork.ozlabs.org/project/skiboot/patch/20200717044243.1195833-1-ooh...@gmail.com/ Ah, nice, thanks for showing me this! I had written my own parser that just dumped a few register

Re: ASMedia USB 3.x host controllers triggering EEH on POWER9

2020-07-17 Thread Oliver O'Halloran
On Fri, Jul 17, 2020 at 2:14 PM Forest Crossman wrote: > > Hi, all, > > I have several ASMedia USB 3.x host controllers (ASM2142 and ASM3142, > both share the same Vendor ID/Device ID pair) that I'd like to use > with a POWER9 system (a Raptor Computing Systems Talos II). > Unfortunately, while

ASMedia USB 3.x host controllers triggering EEH on POWER9

2020-07-16 Thread Forest Crossman
Hi, all, I have several ASMedia USB 3.x host controllers (ASM2142 and ASM3142, both share the same Vendor ID/Device ID pair) that I'd like to use with a POWER9 system (a Raptor Computing Systems Talos II). Unfortunately, while the kernel recognizes the controllers just fine, as soon as I plug in