public inbox for iommu@lists.linux-foundation.org
 help / color / mirror / Atom feed
From: "StarostaCZ@gmail.com" <starostacz@gmail.com>
To: Joerg Roedel <joro@8bytes.org>, Johan Hovold <johan@kernel.org>
Cc: iommu@lists.linux-foundation.org, linux-usb@vger.kernel.org,
	Mathias Nyman <mathias.nyman@intel.com>
Subject: Re: Linux crash when using FTDI FT232R USB to serial converter on AMD boards.
Date: Wed, 15 May 2019 09:54:43 +0200	[thread overview]
Message-ID: <4e7f0267-eba8-81c3-4036-25924ea9df98@gmail.com> (raw)
In-Reply-To: <8748125e-f360-ff0e-ea15-699bce9e7747@gmail.com>

Hello,
can I still help with this problem? It's very important for us. Thank you.

starosta

Dne 6.5.2019 v 9:10 StarostaCZ@gmail.com napsal(a):
> New test on kernel Linux version 5.1.0-050100-generic. Same problem, 
> system crash after a few seconds.
> Full kern.log: https://paste.ee/p/EmLsw
> I can do access to my pc through SSH if useful.
>
> starosta
>
> Dne 3.5.2019 v 17:37 Joerg Roedel napsal(a):
>> On Mon, Apr 29, 2019 at 11:48:47AM +0200, Johan Hovold wrote:
>>> So this is a debian 4.18 kernel seemingly crashing due to a xhci or
>>> iommu issue.
>>>
>>> Can you reproduce this on a mainline kernel?
>>>
>>> If so, please post the corresponding logs to the lists and CC the xhci
>>> and iommu maintainers (added to CC).
>> Your kernel is probably missing this upstream fix:
>>
>>     4e50ce03976f iommu/amd: fix sg->dma_address for sg->offset bigger 
>> than PAGE_SIZE
>>
>> Regards,
>>
>>     Joerg
>>
>

_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

  reply	other threads:[~2019-05-15  7:56 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <04503197-a0a9-8b35-6c65-c10f296aab57@gmail.com>
     [not found] ` <04503197-a0a9-8b35-6c65-c10f296aab57-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-04-29  9:48   ` Linux crash when using FTDI FT232R USB to serial converter on AMD boards Johan Hovold
2019-04-29  9:48     ` Johan Hovold
2019-04-29 10:51     ` StarostaCZ-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
2019-04-29 10:51       ` StarostaCZ@gmail.com
     [not found]       ` <26c4a175-dae2-3410-6924-92fe7c8ec6fe-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-04-29 11:22         ` Johan Hovold
2019-04-29 11:22           ` Johan Hovold
2019-04-29 11:48           ` StarostaCZ-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
2019-04-29 11:48             ` StarostaCZ@gmail.com
2019-05-03 15:37     ` Joerg Roedel
2019-05-06  7:09       ` StarostaCZ@gmail.com
2019-05-06  7:10       ` StarostaCZ@gmail.com
2019-05-15  7:54         ` StarostaCZ@gmail.com [this message]
2019-05-15  9:17           ` Oliver Neukum
2019-05-15  9:43             ` StarostaCZ@gmail.com
2019-05-15  9:46               ` Oliver Neukum
2019-05-15 11:21                 ` StarostaCZ@gmail.com
2019-05-15 13:54                   ` Oliver Neukum
2019-05-15 14:15                     ` StarostaCZ@gmail.com
2019-05-16  7:58                       ` Oliver Neukum
2019-05-16  8:20                         ` StarostaCZ@gmail.com
2019-05-16  8:34                           ` Oliver Neukum
2019-05-16 12:29                             ` StarostaCZ@gmail.com
2019-05-16 13:11                               ` Oliver Neukum
2019-05-16 13:36                                 ` StarostaCZ@gmail.com
2019-05-15 11:22                 ` StarostaCZ@gmail.com
2019-05-15  9:43             ` StarostaCZ@gmail.com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4e7f0267-eba8-81c3-4036-25924ea9df98@gmail.com \
    --to=starostacz@gmail.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=johan@kernel.org \
    --cc=joro@8bytes.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox