On 16/10/2017 20:23, Robin Murphy wrote:
> On 16/10/17 12:54, Hao Wei Tee wrote:
>> On 12/10/2017 21:36, Mathias Nyman wrote:
>>> You could try booting with xhci_hcd.dyndbg=+p added to the kernel command
>>> line.
>>
>> I can't find anything relevant... Hmm.
>
> Is your VL805 on the motherboard o
On 16/10/2017 20:23, Robin Murphy wrote:
> Is your VL805 on the motherboard or an add-on card? One other possibly
> important difference that comes to mind is that on my arm64 system Linux
> is the only agent to ever touch the xHCI - UEFI doesn't even try to
> probe it. It seems likely that a full-
On 16/10/17 12:54, Hao Wei Tee wrote:
> On 12/10/2017 21:36, Mathias Nyman wrote:
>> You could try booting with xhci_hcd.dyndbg=+p added to the kernel command
>> line.
>
> I can't find anything relevant... Hmm.
Is your VL805 on the motherboard or an add-on card? One other possibly
important diff
On 12/10/2017 21:36, Mathias Nyman wrote:
> You could try booting with xhci_hcd.dyndbg=+p added to the kernel command
> line.
I can't find anything relevant... Hmm.
Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=... rw intel_iommu=on
xhci_hcd.dyndbg=+p
ACPI: DMAR 0xDE2C20E0 78 (v
On 12.10.2017 13:48, Hao Wei Tee wrote:
On 10/10/2017 22:13, Mathias Nyman wrote:
On 10.10.2017 12:41, David Laight wrote:
From: Robin Murphy
Sent: 09 October 2017 18:39
...
- without the IOMMU, block sizes >=128K all settle down into a
suspiciously-periodic error every 2048 sectors.
On 10/10/2017 22:13, Mathias Nyman wrote:
> On 10.10.2017 12:41, David Laight wrote:
>> From: Robin Murphy
>>> Sent: 09 October 2017 18:39
>> ...
- without the IOMMU, block sizes >=128K all settle down into a
suspiciously-periodic error every 2048 sectors.
>>
>> That stinks of being
On 10/10/17 16:51, David Laight wrote:
> From: Robin Murphy
>> Sent: 10 October 2017 16:25
> ...
>>> That could 'just' be the hardware doing a 'readahead' of the ring.
>>> Somewhat annoying if it is doing that across page boundaries.
>>
>>> Although, in that case, the read values wouldn't be used b
From: Robin Murphy
> Sent: 10 October 2017 16:25
...
> > That could 'just' be the hardware doing a 'readahead' of the ring.
> > Somewhat annoying if it is doing that across page boundaries.
>
> > Although, in that case, the read values wouldn't be used because the
> > last TRB is a link.
> > So tha
On 10/10/17 15:24, David Laight wrote:
> From: Mathias Nyman
>> Sent: 10 October 2017 15:13
> ...
>> [ 428.409645] print_req_error: I/O error, dev sdb, sector 128
>> [ 428.426612] arm-smmu 2b50.iommu: Unhandled context fault: fsr=0x8,
>> iova=0xff0b1000,
>> fsynr=0x183, cb=0
>>
>> a ring seg
From: Mathias Nyman
> Sent: 10 October 2017 15:13
...
> [ 428.409645] print_req_error: I/O error, dev sdb, sector 128
> [ 428.426612] arm-smmu 2b50.iommu: Unhandled context fault: fsr=0x8,
> iova=0xff0b1000,
> fsynr=0x183, cb=0
>
> a ring segment is 256 TRBS, each *16 bytes, that ring last
On 10.10.2017 12:41, David Laight wrote:
From: Robin Murphy
Sent: 09 October 2017 18:39
...
- without the IOMMU, block sizes >=128K all settle down into a
suspiciously-periodic error every 2048 sectors.
That stinks of being a problem where either the link TRB is part
way through a USB
From: Robin Murphy
> Sent: 09 October 2017 18:39
...
> > - without the IOMMU, block sizes >=128K all settle down into a
> >suspiciously-periodic error every 2048 sectors.
That stinks of being a problem where either the link TRB is part
way through a USB packet or where a buffer fragment cross
On 09/10/17 16:49, Robin Murphy wrote:
> On 09/10/17 10:22, Mathias Nyman wrote:
>> On 08.10.2017 17:03, Hao Wei Tee wrote:
>>> Hi,
>>>
>>> I've been having DMA read faults with my VL805 xHCI controller when
>>> the Intel IOMMU
>>> is turned on:
>>>
>>> xhci_hcd :03:00.0: xHCI Host Control
On 09/10/17 10:22, Mathias Nyman wrote:
> On 08.10.2017 17:03, Hao Wei Tee wrote:
>> Hi,
>>
>> I've been having DMA read faults with my VL805 xHCI controller when
>> the Intel IOMMU
>> is turned on:
>>
>> xhci_hcd :03:00.0: xHCI Host Controller
>> xhci_hcd :03:00.0: new USB bus re
On 09/10/2017 17:22, Mathias Nyman wrote:
> On 08.10.2017 17:03, Hao Wei Tee wrote:
>> Hi,
>>
>> I've been having DMA read faults with my VL805 xHCI controller when the
>> Intel IOMMU
>> is turned on:
>>
>> xhci_hcd :03:00.0: xHCI Host Controller
>> xhci_hcd :03:00.0: new USB bus
On 08.10.2017 17:03, Hao Wei Tee wrote:
Hi,
I've been having DMA read faults with my VL805 xHCI controller when the Intel
IOMMU
is turned on:
xhci_hcd :03:00.0: xHCI Host Controller
xhci_hcd :03:00.0: new USB bus registered, assigned bus number 2
DMAR: DRHD: handling fau
16 matches
Mail list logo