| 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: Sat, 02 Feb 2008 20:20:06 +0900 From: Tejun Heo <htejun@...il.com> To: Mao Rui <maorui@...ad.com> CC: 'Alan Cox' <alan@...rguk.ukuu.org.uk>, linux-kernel@...r.kernel.org Subject: Re: SATA DOM is not identified by ata_piix module Mao Rui wrote: > Hi, > > No difference... :-( > > Here is the log. > > [ 26.729011] scsi0 : ata_piix > [ 26.729067] scsi1 : ata_piix > [ 26.729095] ata1: SATA max UDMA/133 cmd 0x1880 ctl 0x1874 bmdma 0x1860 > irq 18 > [ 26.729097] ata2: SATA max UDMA/133 cmd 0x1878 ctl 0x1870 bmdma 0x1868 > irq 18 > [ 26.894043] ata1.00: ATA-6: WDC WD2500SD-01KCB0, 08.02D08, max UDMA/133 > [ 26.894046] ata1.00: 488397168 sectors, multi 16: LBA48 > [ 26.910218] ata1.00: configured for UDMA/133 > [ 57.043651] ata2.00: qc timeout (cmd 0x91) > [ 57.043656] ata2.00: failed to IDENTIFY (INIT_DEV_PARAMS failed, > err_mask=0x4) > [ 57.043659] ata2: failed to recover some devices, retrying in 5 secs > [ 92.177684] ata2.00: qc timeout (cmd 0x91) > [ 92.177688] ata2.00: failed to IDENTIFY (INIT_DEV_PARAMS failed, > err_mask=0x4) Ah.. Timeout. Hmmm... Interesting. Maybe the device just should be blacklisted such that INIT_DEV_PARAMS is not issued. Can you please just comment out the INIT_DEV_PARAMS block and see how it works and post full boot log? -- tejun -- 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