From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Kyle McMartin <kmcmarti-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: tegra on 3.11
Date: Thu, 05 Sep 2013 15:14:23 -0600 [thread overview]
Message-ID: <5228F42F.50904@wwwdotorg.org> (raw)
In-Reply-To: <20130904183815.GC16338-nxOev/eQj6CGu0OVIAPS5KfLeoKvNuZc@public.gmane.org>
On 09/04/2013 12:38 PM, Kyle McMartin wrote:
>>> [ 29.198018] PCI: enabling device 0000:01:00.0 (0140 -> 0143)
>>> [ 29.198180] Unhandled fault: imprecise external abort (0x406) at
>>> 0xb6f49000
>>> [ 29.205136] Internal error: : 406 [#1] SMP ARM
>>>
>>> looks to be the first time we touch the HW in rtl_init_one.
>>>
>>> Seen anything similar, or should I start debugging further?
>>
>> PCIe isn't expected to work usefully until 3.12, unless you've manually
>> merged in Thierry's Tegra PCIe driver rewrite. It's probably worth
>> disabling it in your .config file.
>
> fwiw, the problem was CONFIG_PCIEPORTBUS in our config, I've not had
> a chance to track down what the issue actually is, but that driver
> busted things in 3.11.
Ah, I guess if you build the R8169 driver as a module, and disable
CONFIG_CPU_IDLE, then it will work fine on TrimSlice in v3.11.
I have reproduced the issue you see with CONFIG_PCIEPORTBUS in v3.11.
So, at least it isn't an isolated incident. That said, I don't intend to
look into it since there's an easy workaround, and ...
The good news is that in v3.12 with the new PCIe driver,
(a) You don't need to build R8169 as a module; built-in will work fine.
(b) You don't need to disable CPUIDLE; the code disables the problematic
idle state automatically iff a PCIe device is detected.
(c) CONFIG_PCIEPORTBUS is enabled in tegra_defconfig, and everything
still works fine.
next prev parent reply other threads:[~2013-09-05 21:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 15:04 tegra on 3.11 Kyle McMartin
[not found] ` <20130820150418.GI27560-nxOev/eQj6CGu0OVIAPS5KfLeoKvNuZc@public.gmane.org>
2013-08-20 19:18 ` Stephen Warren
[not found] ` <5213C0F2.9060909-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-08-20 20:50 ` Kyle McMartin
[not found] ` <20130827213445.GI8764@redacted.bos.redhat.com>
[not found] ` <521D1D7F.7060006@wwwdotorg.org>
[not found] ` <521D1D7F.7060006-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-09-04 18:38 ` Kyle McMartin
[not found] ` <20130904183815.GC16338-nxOev/eQj6CGu0OVIAPS5KfLeoKvNuZc@public.gmane.org>
2013-09-05 21:14 ` Stephen Warren [this message]
[not found] ` <5228F42F.50904-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-09-05 21:43 ` Kyle McMartin
2013-12-03 10:30 ` Thierry Reding
[not found] ` <20131203103043.GI21178-AwZRO8vwLAwmlAP/+Wk3EA@public.gmane.org>
2013-12-03 16:44 ` Kyle McMartin
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=5228F42F.50904@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=kmcmarti-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.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