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
| ||
|
Date: Wed, 02 Jan 2008 23:17:23 -0500 From: Mark Lord <lkml@....ca> To: Robert Hancock <hancockr@...w.ca> Cc: Allen Martin <AMartin@...dia.com>, Jeff Garzik <jeff@...zik.org>, Tejun Heo <htejun@...il.com>, Gabor Gombas <gombasg@...aki.hu>, linux-kernel@...r.kernel.org, linux-ide@...r.kernel.org, Kuan Luo <kluo@...dia.com>, Peer Chen <pchen@...dia.com> Subject: Re: sata_nv + ADMA + Samsung disk problem Robert Hancock wrote: .. > From some of the traces I took previously (posted on LKML as "sata_nv > ADMA controller lockup investigation" way back in Feb 07), what seems to > occur is that when the second command is issued very rapidly (within > less than 20 microseconds, or potentially longer) after the previous > command's completion, the ADMA status changes from 0x500 (STOPPED and > IDLE) to 0x400 (just IDLE) as it typically does, but then it sticks > there, no interrupt is ever raised, and CPB response flags remain at 0. .. Assuming that NVidia got their ADMA core logic from Pacific Digital (the inventors), then it may have some of the same bugs as the original. One of those bugs is that the aGO trigger is sampled in a "racey" way, such that it sometimes may miss a recent addition to the ring. The *only* way to guarantee things with the original Pacific Digital core was to (1) always retrigger aGO for a full ring scan with each new addition, and (2) poll periodically (every half second or so) rather than relying exclusively on the IRQ actually working.. Dunno about the NVidia version. Cheers -- 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