linux-kernel - Re: [PATCH] x86: Add workaround for bug in ASUS A7V600 BIOS (rev 1005)

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: <20080530231854.GA4287@zombie.inf.tu-dresden.de>
Date:	Sat, 31 May 2008 01:18:55 +0200
From:	Bertram Felgenhauer <int-e@....de>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Bertram Felgenhauer <int-e@....de>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86: Add workaround for bug in ASUS A7V600 BIOS (rev
	1005)

Alan Cox wrote:
> On Fri, 30 May 2008 03:20:05 +0200
> Bertram Felgenhauer <int-e@....de> wrote:
> > Amazingly I have a 2.6.23.8 kernel that somehow works fine ... I'll
> > never understand why.
> 
> Probably because it has ACPI enabled and is picking ACPI IRQ routing in
> preference ?

No.

The "only" difference between the working 2.6.23.8 kernel and the
non-working one is a switch from gcc 3.4.6 to 4.1.2. I've collected
some information about this issue, comparing the 'working' 2.6.23.8
kernel with a newly compiled, patched one. (The unpatched one compiled
with 4.1.2 fails to boot.) So if anybody is interested, have a look at

    http://int-e.home.tlink.de/linux/irq/

But it's probably not worthwhile to spend a lot of time on this.

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