| 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
| ||
|
Message-ID: <alpine.LFD.2.00.1005170811400.4195@i5.linux-foundation.org> Date: Mon, 17 May 2010 08:12:59 -0700 (PDT) From: Linus Torvalds <torvalds@...ux-foundation.org> To: Andreas Herrmann <andreas.herrmann3@....com> cc: Yuhong Bao <yuhongbao_386@...mail.com>, venkatesh.pallipadi@...el.com, markh@...pro.net, dmarkh@....rr.com, andi@...stfloor.org, alain@...ff.lu, linux-kernel@...r.kernel.org Subject: Re: [PATCH] x86: Disable HPET MSI on ATI SB700/SB800 On Mon, 17 May 2010, Andreas Herrmann wrote: > > FYI. I've tried to trigger the publication of errata information for that > chipset. Finally this has happened. > > The discussed problem is indeed due to an erratum. See erratum #27 in > http://support.amd.com/us/Embedded_TechDocs/46837.pdf > > The suggested workaround for this is to disable HPET MSI if LPC > devices are used. I doubt that there is a convenient way for Linux to > find out whether LPC devices are used. Thus I think the only solution > to safely avoid the problem is the currently implemented quirk to > disable HPET MSI on this chipset. Goodie. It would be good to point this out in the source too. Would you be willing to send in a patch that documents this quirk as a result of that erratum #27, so that we don't lose sight of why we're doing that odd MSI disable? Linus -- 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/
Powered by blists - more mailing lists