linux-kernel - Re: [regression] 3.7 ends in APIC panic

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] [day] [month] [year] [list]

Message-ID: <CAE9FiQX=7R8MWo9iUPdi8tt4b7yozEcjNnSh8RvsmAduAbP+LA@mail.gmail.com>
Date:	Mon, 17 Dec 2012 09:03:06 -0800
From:	Yinghai Lu <yinghai@...nel.org>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Ingo Molnar <mingo@...nel.org>,
	Bernd Schubert <bernd.schubert@...m.fraunhofer.de>,
	linux-kernel@...r.kernel.org, Borislav Petkov <bp@...en8.de>,
	Suresh Siddha <suresh.b.siddha@...el.com>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [regression] 3.7 ends in APIC panic

On Mon, Dec 17, 2012 at 8:56 AM, H. Peter Anvin <hpa@...or.com> wrote:
> On 12/17/2012 08:53 AM, Yinghai Lu wrote:
>> On Mon, Dec 17, 2012 at 6:02 AM, Ingo Molnar <mingo@...nel.org> wrote:
>>>
>>> I suspect this needs to be fixed/improved: currently it's way
>>> too easy to disable x2apic support accidentally.
>>>
>>
>> We can just enable x2apic by default when CONFIG_EMBEDDED is not set.
>>
>
> Yes, although we should expect to have to blacklist hosts more aggressively.
>
> Unfortunately we still don't have a good distinction between the
> ThinkPads that have broken BIOSes when x2apic is on and those that don't.

last version for that blacklist patch in the bugster should be ok for
thinkpad now.

BTW, when can we have ioapic id > 255 ?

system with more than 256 sockets and IIO in it, should need that
support, right?

Yinghai
--
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/