linux-kernel - Re: [PATCH] x86: add ASRock Q1900DC-ITX mainboard reboot quirk

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: <20150331205823.67f96af0@mir>
Date:	Tue, 31 Mar 2015 20:58:23 +0200
From:	Stefan Lippers-Hollmann <s.l-h@....de>
To:	Ingo Molnar <mingo@...nel.org>
Cc:	linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	Matt Fleming <matt.fleming@...el.com>
Subject: Re: [PATCH] x86: add ASRock Q1900DC-ITX mainboard reboot quirk

Hi

On 2015-03-31, Ingo Molnar wrote:
> * Stefan Lippers-Hollmann <s.l-h@....de> wrote:
[...]
> > Searching the web seems to suggest that other Bay Trail-D mainboards 
> > might be affected as well.
> 
> Is the pattern:
> 
> > +		.ident = "ASRock Q1900DC-ITX",
> > +		.matches = {
> > +			DMI_MATCH(DMI_BOARD_VENDOR, "ASRock"),
> > +			DMI_MATCH(DMI_BOARD_NAME, "Q1900DC-ITX"),
> 
> generic enough to cover all ASRock Bay Trail-D boards?
[...]

No, it covers only the one I can personally test and confirm to require
this quirk, beyond my own ASRock Q1900DC-ITX[1], there are at least:

Celeron J1800:
 - ASRock D1800B-ITX, http://www.asrock.com/mb/Intel/D1800B-ITX/
 - ASRock D1800M, http://www.asrock.com/mb/Intel/D1800M/

Celeron J1900:
 - ASRock Q1900B-ITX, http://www.asrock.com/mb/Intel/Q1900B-ITX/
 - ASRock Q1900-ITX, http://www.asrock.com/mb/Intel/Q1900-ITX/
 - ASRock Q1900TM-ITX, http://www.asrock.com/mb/Intel/Q1900TM-ITX/
 - ASRock Q1900M Pro3, http://www.asrock.com/mb/Intel/Q1900M%20Pro3/
 - ASRock Q1900M, http://www.asrock.com/mb/Intel/Q1900M/

Pentium J2900:
 - ASRock Q2900M, http://www.asrock.com/mb/Intel/Q2900M/
 - ASRock Q2900-ITX, http://www.asrock.com/mb/Intel/Q2900-ITX/

All very similar boards, but their BIOS state might differ.

However I've never had access to any of those and could only do an
educated guess about their DMI identification[2]. While researching my
problem on the web, it seems that Baytrail-D boards from several vendors 
might be affected (e.g. Gigabyte). Sometimes apparently fixed by later 
BIOS updates, but I can only confirm the problem and workaround for my 
own ASRock Q1900DC-ITX mainboard (where all published BIOS versions are 
affected).

Regards
	Stefan Lippers-Hollmann

[1]	http://www.asrock.com/mb/Intel/Q1900DC-ITX/
[2]	I know that the very similar ASRock Q1900-ITX board uses
	DMI_MATCH(DMI_BOARD_VENDOR, "ASRock"),
	DMI_MATCH(DMI_BOARD_NAME, "Q1900-ITX"),
	but I don't have direct access to that board and can't
	check if it is also affected by this problem.

Content of type "application/pgp-signature" skipped