| 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: <46BA7CFB.8020605@parkingdenied.com> Date: Thu, 09 Aug 2007 10:33:31 +0800 From: Ross Fawcett <claymen@...kingdenied.com> To: Jeff Garzik <jeff@...zik.org> CC: Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: sata_sil24 problems What would you define a media error as though? I mean my first thought is a bad block, but a scan of the disc doesn't report anything like that. It also seems to be intermittent, however recently it has been reproducible. - Ross Jeff Garzik wrote: > Ross Fawcett wrote: >> The errors I get are like these. >> >> [ 1073.018375] ata4.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 >> [ 1073.018382] ata4.00: (irq_stat 0x00020002, device error via SDB FIS) >> [ 1073.018389] ata4.00: cmd 60/80:00:80:6f:b6/00:00:04:00:00/40 tag 0 >> cdb 0x0 data 65536 in >> [ 1073.018391] res 41/40:00:f3:6f:b6/00:00:04:00:00/40 Emask >> 0x9 (media error) > > > Your device is signalling a media error. That's hardware going > ker-flop, with the controller happily reporting that fact back to us. > > Jeff > > > - > 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/ - 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