linux-kernel - Re: [PATCH] x86: Disable HPET MSI on ATI SB700/SB800

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: <4B61562C.1010103@cfl.rr.com>
Date:	Thu, 28 Jan 2010 04:17:32 -0500
From:	Mark Hounschell <dmarkh@....rr.com>
To:	Andreas Herrmann <andreas.herrmann3@....com>
CC:	Yuhong Bao <yuhongbao_386@...mail.com>,
	venkatesh.pallipadi@...el.com, markh@...pro.net,
	andi@...stfloor.org,
	Linus Torvalds <torvalds@...ux-foundation.org>, alain@...ff.lu,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86: Disable HPET MSI on ATI SB700/SB800

On 01/25/2010 12:10 PM, Andreas Herrmann wrote:
> On Fri, Jan 22, 2010 at 11:21:06PM -0800, Yuhong Bao wrote:
>>
>>> HPET MSI on platforms with ATI SB700/SB800 as they seem to have some
>>> side-effects on floppy DMA. Do not use HPET MSI on such platforms.
> 
> Argh, will see what information I can find about this problem ...
> 
>> I think somebody from AMD should review the situation.Clearly
>   something is happening inside their southbridge.CCing Andreas
>   Herrmann from AMD.
> 
> I have the feeling that this problem should rather be fixed with a DMI
> quirk instead of disabling HPET MSI for the entire chipset.
> 
> Was the latest available BIOS installed on the affected system?
> 

You mean "systems" of different manufactures?  I will check today. Due to
mis configured filters I didn't see this until today. Sorry.

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