| 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: <Pine.LNX.4.64.0612191600300.20138@iabervon.org> Date: Tue, 19 Dec 2006 16:18:47 -0500 (EST) From: Daniel Barkalow <barkalow@...ervon.org> To: John M Flinchbaugh <john@...oft.com> cc: linux-kernel@...r.kernel.org Subject: Re: forcedeth trouble in 2.6.19(.1) On Tue, 19 Dec 2006, John M Flinchbaugh wrote: > I saw a mention of interrupt handling for forcedeth cards is the > 2.6.19.1 changelog, but I still see this error in 2.6.19.1. It started > in 2.6.19, and it didn't happen in 2.6.18.1. Nope; the issue fixed in 2.6.19.1 has always existed (provided you had hardware suitable to trigger it). And it was an issue of getting bogus legacy interrupts when using MSI, which would lead to some other device on the same legacy interrupt getting disabled. I'd suggest reverting 0a07bc645e818b88559d99f52ad45e35352e8228 (fixes a lockdep warning, stuff with interrupts, only build tested) as a first guess. -Daniel *This .sig left intentionally blank* - 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