Hello everyone,
Unfortunately I wasn't able to find a solution. As there was no obvious solution, I changed my card again ... But if you know how to solve my problem, I'd be pleased to read it ! Best regards, Jeanne > Le 23 mai 2019 à 07:59, Ralf Ramsauer <[email protected]> a > écrit : > > Hi all, > >> On 5/12/19 9:51 AM, Jan Kiszka wrote: >>> On 10.05.19 15:11, [email protected] wrote: >>> Hello everyone, >>> >>> I'm still trying to get my rootCell running. I have for the moment >>> connected a serial port in order to have the logs in full (in ssh the >>> communication was down before I could have the logs). After solving >>> some minor errors (such as Invalid MMIO/RAM read or IO-port) I find >>> myself with an error that I can't explain: >>> >>> >>> VT-d fault event reported by IOMMU 1: >>> Source Identifier (bus:dev.func): 03:00.0 >>> Fault Reason: 0x22 Fault Info: 38000000000 Type 0 >>> VT-d fault event reported by IOMMU 1: >>> Source Identifier (bus:dev.func): 03:00.0 >>> Fault Reason: 0x22 Fault Info: 3c000000000 Type 0 >>> VT-d fault event reported by IOMMU 1: >>> Source Identifier (bus:dev.func): 03:00.0 >>> Fault Reason: 0x22 Fault Info: 39000000000 Type 0 >>> VT-d fault event reported by IOMMU 1: >>> Source Identifier (bus:dev.func): 03:00.0 >>> Fault Reason: 0x22 Fault Info: 3b000000000 Type 0 > > hmm, sounds familiar. > > On a Dell T440, we have the *exact* same issue with a similar card: a > BCM5720, pretty similar to your BCM5719. See my thread "VT-d: IOMMU > exception with unknown fault reason"). And yes, there we have an active > link on it. > >>> >>> >>> Is the new sysfs-parser.py the cause of my trouble or is there >>> anything I missed in the configuration ? >> >> Could be. 0x22 means that the device is not present in the interrupt > > We have no modifications of the sysfs parser and face the same issue. > >> remapping >> table of IOMMU that is responsible for that device. Try changing the .iommu >> number for that device from 0 to 1 or the other way around. Or is there >> no entry >> for 03:00.0 at all? > > Jeanne, were you already able to solve this issue? > > I manually parsed (my) DMAR, and there's a ATSR structure (type 0x2) > which is ignored by the config parser. Could this be related to this > issue or can it simply be ignored? > > In this system, we have four iommus. Mario, did you already test all > possibilities for .iommu (0, 1, 2, 3)? > > Ralf > >> >> Jan >> -- You received this message because you are subscribed to the Google Groups "Jailhouse" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jailhouse-dev/D48E8F23-20F7-4588-8B6D-4C15EA2B714C%40gmail.com. For more options, visit https://groups.google.com/d/optout.
