From: Oleg Orel <oorel@vmware.com>
To: "Yu, Fenghua" <fenghua.yu@intel.com>
Cc: "Raj, Ashok" <ashok.raj@intel.com>,
"Li, Shaohua" <shaohua.li@intel.com>,
"Keshavamurthy, Anil S" <anil.s.keshavamurthy@intel.com>,
"'avi@qumranet.com'" <avi@qumranet.com>,
"'yaniv@qumranet.com'" <yaniv@qumranet.com>,
Bhavesh Davda <bhavesh@vmware.com>,
Mallik Mahalingam <mallik@vmware.com>,
Jagannath Krishnan <krishnan@vmware.com>,
Adar Dembo <adar@vmware.com>,
"'iommu@lists.linux-foundation.org'"
<iommu@lists.linux-foundation.org>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: Intel IOMMU on Dell Latitude E6400, Lenovo X200 & Dell Precision T5400
Date: Thu, 29 Jan 2009 17:28:44 -0800 [thread overview]
Message-ID: <498257CC.40902@vmware.com> (raw)
In-Reply-To: <A6AD88C3F2289247BE726C37303E1EB8927A8E8E@orsmsx505.amr.corp.intel.com>
Yu, Fenghua wrote:
>
>> We had reported more details @
>> https://bugzilla.redhat.com/show_bug.cgi?id=479996 and
>> http://bugzilla.kernel.org/show_bug.cgi?id=11821
>>
>
> Look into http://bugzilla.kernel.org/show_bug.cgi?id=11821
> and find that:
>
> wlan0: Failed to config new SSID to the low-level driver
> BUG: unable to handle kernel NULL pointer dereference at 0000000000000038
> IP: [<ffffffff8037cf1f>] pci_find_upstream_pcie_bridge+0x1f/0xa0
> ...
> [<ffffffff80386808>] get_domain_for_dev+0x58/0x620
> [<ffffffff8029574d>] ? __alloc_pages_internal+0xed/0x4f0
> [<ffffffff803870f8>] get_valid_domain_for_dev+0x18/0x150
> [<ffffffff803875e7>] intel_map_single+0x47/0x160
> [<ffffffff802b8726>] ? alloc_pages_current+0x76/0xf0
> [<ffffffff8038777f>] intel_alloc_coherent+0x7f/0xb0
> ...
>
> Wireless LAN could cause the NULL pointer access in get_domain_for_dev() which is IOMMU function.
>
> As an experiment, could you disable wireless lan on your machine and try to boot IOMMU kernel?
>
> Thanks.
>
> -Fenghua
>
Yu,
I did it already yesterday. It didn't help. It fact I had disable all
disableble devices, also, on T5400 when is failing as well, we do not
have a wireless.
prev parent reply other threads:[~2009-01-30 1:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 22:01 Intel IOMMU on Dell Latitude E6400, Lenovo X200 & Dell Precision T5400 Oleg Orel
2009-01-30 1:25 ` Yu, Fenghua
2009-01-30 1:28 ` Oleg Orel [this message]
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=498257CC.40902@vmware.com \
--to=oorel@vmware.com \
--cc=adar@vmware.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=ashok.raj@intel.com \
--cc=avi@qumranet.com \
--cc=bhavesh@vmware.com \
--cc=fenghua.yu@intel.com \
--cc=iommu@lists.linux-foundation.org \
--cc=krishnan@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mallik@vmware.com \
--cc=shaohua.li@intel.com \
--cc=yaniv@qumranet.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