linux-kernel - Re: Bisecting tip/auto-x86-next?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <d1af83620806200440g3bdbff03va0883b2ddb6f0ddb@mail.gmail.com>
Date:	Fri, 20 Jun 2008 08:40:07 -0300
From:	"Kevin Winchester" <kjwinchester@...il.com>
To:	"Pavel Machek" <pavel@...e.cz>
Cc:	"Ingo Molnar" <mingo@...e.hu>, "Ingo Molnar" <mingo@...hat.com>,
	"Thomas Gleixner" <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
	"Yinghai Lu" <yhlu.kernel@...il.com>,
	"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: Bisecting tip/auto-x86-next?

On Fri, Jun 20, 2008 at 7:49 AM, Pavel Machek <pavel@...e.cz> wrote:
> Hi!
>
>> * Kevin Winchester <kjwinchester@...il.com> wrote:
>
>> > Hi,
>> >
>> > I am trying to track down a problem I reported here:
>> >
>> > http://lkml.org/lkml/2008/6/11/431
>
> Can you try iommu=memaper=2 ?

I should have mentioned that in the original post - I tried
iommu=memaper=2, and got the identical result (including the message
asking me to try iommu=memaper=2).  Perhaps the message should not be
printed if the user did actually provide that boot option.

>
> Is it amd64 machine?

Yes it is, UP.

Thanks,

-- 
Kevin Winchester
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/