From: Johannes Berg <johannes@sipsolutions.net>
To: Andres Freund <andres@anarazel.de>
Cc: Tomas Winkler <tomasw@gmail.com>,
Muli Ben-Yehuda <muli@il.ibm.com>, Jeff Garzik <jeff@garzik.org>,
linux-kernel@vger.kernel.org,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: bad DMAR interaction with iwlagn and SATA
Date: Tue, 07 Oct 2008 10:37:16 +0200 [thread overview]
Message-ID: <1223368636.3778.64.camel@johannes.berg> (raw)
In-Reply-To: <200810061632.08375.andres@anarazel.de>
[-- Attachment #1: Type: text/plain, Size: 618 bytes --]
On Mon, 2008-10-06 at 16:32 +0200, Andres Freund wrote:
> > Andres, can you post your config?
> Sure, my current running one is attached.
> The config I had the error with was exactly the same just with CONFIG_DMAR and
> e1000e enabled (but is overwritten now)...
>
> Its no problem trying another branch more debugging options or so if needed.
No, I was just wondering whether x86-64 had something like powerpc's
CONFIG_64K_PAGES, but it doesn't seem to. 2M-page support seems to be
used always dependent on the CPU, but I have no idea you can tell
whether or not your CPU supports that.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2008-10-07 16:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-25 13:11 Andres Freund
2008-09-26 2:11 ` Jeff Garzik
2008-09-26 2:18 ` Andres Freund
2008-09-26 2:41 ` Jeff Garzik
2008-09-26 14:47 ` Muli Ben-Yehuda
2008-09-26 15:12 ` Johannes Berg
2008-09-26 23:30 ` Tomas Winkler
2008-09-29 8:27 ` Andres Freund
2008-09-29 8:40 ` Tomas Winkler
2008-10-06 12:26 ` Johannes Berg
2008-10-06 14:32 ` Andres Freund
2008-10-07 8:37 ` Johannes Berg [this message]
2008-10-07 17:04 ` Kyle McMartin
2008-10-07 17:08 ` Johannes Berg
2008-09-26 15:10 ` Johannes Berg
2008-09-29 8:26 ` Andres Freund
2008-10-06 22:11 Boris Fersing
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=1223368636.3778.64.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=andres@anarazel.de \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=muli@il.ibm.com \
--cc=tomasw@gmail.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
all inboxes | Powered by JetHome®