[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <48926FC3.3000706@keyaccess.nl>
Date: Fri, 01 Aug 2008 04:06:59 +0200
From: Rene Herman <rene.herman@...access.nl>
To: Ingo Molnar <mingo@...e.hu>
CC: Linus Torvalds <torvalds@...ux-foundation.org>,
Suresh Siddha <suresh.b.siddha@...el.com>,
Wim Van Sebroeck <wim@...ana.be>,
Pádraig Brady <P@...igBrady.com>,
Andi Kleen <andi@...stfloor.org>,
"H. Peter Anvin" <hpa@...or.com>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"arjan@...ux.intel.com" <arjan@...ux.intel.com>,
"roland@...hat.com" <roland@...hat.com>,
"drepper@...hat.com" <drepper@...hat.com>,
"mikpe@...uu.se" <mikpe@...uu.se>,
"chrisw@...s-sol.org" <chrisw@...s-sol.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [patch 0/9] x86, xsave: xsave/xrstor support
On 01-08-08 00:50, Ingo Molnar wrote:
> there are a handful of old ISA-ish drivers that can crash randconfig
> kernels in various ways. [indefinite lockups, crashes, stomped-over
> hardware, non-working keyboard, etc.]
>
> I mapped most of them out via many months of trial-and-error - but it
> would still be nice to have some separate config option to disable the
> known ones. CONFIG_ALLOW_NON_GENERIC or something like that - which i
> would unset in the randconfig runs.
>
> ( They are not CONFIG_BROKEN per se, because often it's hardware that
> cannot be probed in any reliable way - the driver just assumes it's
> there. )
If you have a list, I might be able to do something about some of them.
Rene.
--
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/
Powered by blists - more mailing lists