From: Joerg Roedel <joro@8bytes.org>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6.35] AMD-Vi: Enabling IOMMU at 0000:00:00.2 cap 0x40 BUG: unable to handle kernel NULL pointer dereference at 0000000000000198
Date: Tue, 10 Aug 2010 20:01:22 +0200 [thread overview]
Message-ID: <20100810180122.GR23755@8bytes.org> (raw)
In-Reply-To: <419601760.20100810185745@eikelenboom.it>
On Tue, Aug 10, 2010 at 06:57:45PM +0200, Sander Eikelenboom wrote:
> The requested info is attached.
> So that would mean a bios problem ? (those are not on my wishlist :-p)
Yeah, looks like a BIOS problem. But the driver should handle that
without crashing the system, so there is a bug in the driver too.
Problem is:
AMD-Vi: DEV_ALIAS_RANGE devid: 0a:01.0 flags: 00 devid_to: 0a:00.0
AMD-Vi: DEV_RANGE_END devid: 0a:1f.7
This means that PCI devices from 0a:01.0 to 0a:1f.7 may use their own
device-id or 0a:00.0. But a device which id 0a:00.0 is not present in
the system. From the lspci output this looks like your USB3 controler
should alias to 09:00.0. I prepare a patch for you to fix the crash but
I can't guarantee that your USB3 controler will work afterwards. If you
see IO-Page-Faults please report them to me.
Joerg
next prev parent reply other threads:[~2010-08-10 18:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1154489525.20100810164850@eikelenboom.it>
[not found] ` <20100810162606.GQ23755@8bytes.org>
2010-08-10 16:57 ` [2.6.35] AMD-Vi: Enabling IOMMU at 0000:00:00.2 cap 0x40 BUG: unable to handle kernel NULL pointer dereference at 0000000000000198 Sander Eikelenboom
2010-08-10 18:01 ` Joerg Roedel [this message]
2010-08-10 18:05 ` Sander Eikelenboom
2010-08-10 20:28 ` Joerg Roedel
2010-08-10 20:36 ` Sander Eikelenboom
2010-08-10 20:47 ` Joerg Roedel
2010-08-10 20:57 ` Sander Eikelenboom
2010-08-10 21:25 ` Joerg Roedel
2010-08-10 21:48 ` Sander Eikelenboom
2010-08-10 21:36 ` Sander Eikelenboom
2010-08-10 22:02 ` Joerg Roedel
2010-08-10 22:24 ` Joerg Roedel
2010-08-11 17:54 ` Sander Eikelenboom
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=20100810180122.GR23755@8bytes.org \
--to=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@eikelenboom.it \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.