linux-kernel - Re: [PATCH] quirks: Flag up and handle the AMD 8151 Errata #24

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: <200609130906.47361.ak@suse.de>
Date:	Wed, 13 Sep 2006 09:06:47 +0200
From:	Andi Kleen <ak@...e.de>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] quirks: Flag up and handle the AMD 8151 Errata #24

On Tuesday 12 September 2006 20:45, Alan Cox wrote:
> Ar Maw, 2006-09-12 am 17:29 +0200, ysgrifennodd Andi Kleen:
> > If the system really locks up afterwards they will likely never see it
> > though?
>
> They'll see it at boot.
>
> > I just don't think the printk will that useful and if it locks up people
> > will blame Linux anyways even with printk.
>
> Which is why I also intend to make sure the drivers aren't defaulting to
> ignore but all do it properly and require a force flag. PCIPCI_FAIL
> means it doesn't work. No driver should be ignoring that flag.

Ok that would be more reasonable. Just the printk alone seems to be fairly
pointless to me.

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