From: slash.tmp@free.fr (Mason)
To: linux-arm-kernel@lists.infradead.org
Subject: Panic in quirk_usb_early_handoff
Date: Mon, 6 Mar 2017 16:45:36 +0100 [thread overview]
Message-ID: <7bfbe98c-0bee-a13d-0c85-508645e97c58@free.fr> (raw)
In-Reply-To: <063D6719AE5E284EB5DD2968C1650D6DCFE78D44@AcuExch.aculab.com>
On 06/03/2017 16:27, David Laight wrote:
> Mason wrote:
>>
>>> So the kernel panics in xhci_find_next_ext_cap()
>>> ( drivers/usb/host/xhci-ext-caps.h:122 )
>>> http://lxr.free-electrons.com/source/drivers/usb/host/xhci-ext-caps.h?v=4.9#L122
>>>
>>> Any idea how this can happen?
>>>
>>> base = ioremap_nocache(pci_resource_start(pdev, 0), len);
>>>
>>> Could I be passing garbage to ioremap_nocache?
>>
>> Oh...
>>
>> I have just now understood what Ard wrote a few days ago.
>>
>> The issue was that, on this platform, the PCI configuration space
>> and memory space are multiplexed; in other words they reside at
>> the same physical address, with a bit in MMIO to choose one or
>> the other.
>
> Time to shoot another hardware engineer.
He's in CC :-)
> Hopefully it isn't an SMP system - but I wouldn't put it past them.
This is a dual- and quad- Cortex A9 MP platform :-(
Regards.
next prev parent reply other threads:[~2017-03-06 15:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 16:18 Panic in quirk_usb_early_handoff Mason
2017-03-03 17:10 ` Mason
2017-03-03 17:15 ` Mason
2017-03-03 19:02 ` Robin Murphy
2017-03-03 22:09 ` Mason
2017-03-04 0:24 ` Mason
2017-03-04 8:07 ` Ard Biesheuvel
2017-03-04 15:51 ` Alan Stern
2017-03-04 16:57 ` Mason
2017-03-04 17:16 ` Ard Biesheuvel
2017-03-04 17:29 ` Mason
2017-03-04 18:27 ` Ard Biesheuvel
2017-03-06 12:42 ` Mason
2017-03-06 13:49 ` Mason
2017-03-06 15:27 ` David Laight
2017-03-06 15:45 ` Mason [this message]
2017-03-06 15:58 ` David Laight
2017-03-06 14:30 ` Robin Murphy
2017-03-06 14:56 ` Mason
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=7bfbe98c-0bee-a13d-0c85-508645e97c58@free.fr \
--to=slash.tmp@free.fr \
--cc=linux-arm-kernel@lists.infradead.org \
/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