From: John Donnelly <John.P.Donnelly@Oracle.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-usb@vger.kernel.org
Subject: Re: ehci-pci : WARNING: CPU: 0 PID: 347 at kernel/dma/direct.c:34
Date: Sat, 28 Mar 2020 13:05:59 -0500 [thread overview]
Message-ID: <225cfc1f-e520-cff0-404a-a67ca2bdfbef@Oracle.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.2003281135130.1088-100000@netrider.rowland.org>
On 3/28/20 10:37 AM, Alan Stern wrote:
> On Fri, 27 Mar 2020, John Donnelly wrote:
>
>> Hi,
>>
>> I am seeing this WARNING event with iommu=off when booting a DL380
>> server with a 5.4.17 kernel.
>
> ...
>
>> The end result is this USB port is not configured when
>> dma_direct_map_page() is called and it returns return
>> DMA_MAPPING_ERROR;
>>
>>
>> When I boot the server with iommu=on I don’t see this sequence :
>
> ...
>
>> On an older kernel 5.3. flavor I am not seeing this behavior, and the usbhib devices appear as expected :
>
> I forgot to mention: Since you have one kernel where the WARNING occurs
> and one where it doesn't, you can use bisection to find the commit that
> was responsible for the change in behavior. If you care to go to the
> trouble...
>
> Alan Stern
>
Hi.
Yes that is the plan ! It may take awhile.
--
Thank You,
John
next prev parent reply other threads:[~2020-03-28 18:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-28 4:11 ehci-pci : WARNING: CPU: 0 PID: 347 at kernel/dma/direct.c:34 John Donnelly
2020-03-28 7:08 ` Greg KH
2020-03-28 15:34 ` Alan Stern
2020-03-28 15:37 ` Alan Stern
2020-03-28 18:05 ` John Donnelly [this message]
2020-03-30 18:36 ` John Donnelly
2020-03-30 19:41 ` Alan Stern
2020-03-30 20:11 ` John Donnelly
2020-03-31 2:10 ` John Donnelly
2020-03-31 14:17 ` Alan Stern
2020-03-31 16:07 ` John Donnelly
2020-03-31 17:43 ` John Donnelly
2020-03-31 18:21 ` Alan Stern
2020-04-07 13:49 ` John Donnelly
2020-04-07 13:53 ` Alan Stern
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=225cfc1f-e520-cff0-404a-a67ca2bdfbef@Oracle.com \
--to=john.p.donnelly@oracle.com \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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;
as well as URLs for NNTP newsgroup(s).