linux-kernel - Re: RFC: PCI quirks update for 2.6.16

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]

Date:	Thu, 7 Dec 2006 21:45:56 +0100
From:	Tomek Koprowski <tomek@...rowski.org>
To:	Jean Delvare <khali@...ux-fr.org>
Cc:	Adrian Bunk <bunk@...sta.de>, Daniel Ritz <daniel.ritz@....ch>,
	Daniel Drake <dsd@...too.org>,
	Bjorn Helgaas <bjorn.helgaas@...com>,
	Linus Torvalds <torvalds@...l.org>,
	Brice Goglin <brice@...i.com>,
	"John W. Linville" <linville@...driver.com>,
	Bauke Jan Douma <bjdouma@...all.nl>, gregkh@...e.de,
	linux-kernel@...r.kernel.org, linux-pci@...ey.karlin.mff.cuni.cz
Subject: Re: RFC: PCI quirks update for 2.6.16

On Thursday 07 of December 2006 20:54, Jean Delvare wrote:

> > Tomasz Koprowski (1):
> >       PCI: SMBus unhide on HP Compaq nx6110
>
> Bug #6944 might be related to this one, so I'd not include it in
> 2.6.16-stable.

Actually, the #6944 requires more investigation. I've noticed the 
kacpid going to 100% cpu without the unhide patch applied as well. It 
happens sometimes after dehibernation, putting the laptop to sleep
and waking it up again resolves the issue. I can't figure out why.

To be on the safe side I'd suggest dumping the patch, but I really 
don't think it should fix anything.

Tomek

-- 
[ tomek@...rowski.org http://www.koprowski.org ]
[ JabberID: tomek@...kus.kom.pl   gg#: 2348134 ]
[       Life is as bad as you make it be       ]
-
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/