linux-kernel - Re: AHCI - remove probing of ata2

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:	Sat, 10 Feb 2007 20:36:52 +0000
From:	Alan <alan@...rguk.ukuu.org.uk>
To:	<rol@...917.net>
Cc:	"'Robert Hancock'" <hancockr@...w.ca>,
	"'Linux Kernel Mailing List'" <linux-kernel@...r.kernel.org>
Subject: Re: AHCI - remove probing of ata2

> OK, rebooting again, with a new root device as /dev/sde1...
> No problem for the old IDE devices, they are now /dev/sdX.
> 
> But the Jmicron stuff is still broken though no more conflict :(

Thanks. That helps a lot as it narrows it down

> 
> PCI: Enabling device 0000:02:00.1 (0000 -> 0001)
> ACPI: PCI Interrupt 0000:02:00.1[B] -> GSI 16 (level, low) -> IRQ 16
> ata7: PATA max UDMA/100 cmd 0x9C00 ctl 0x9882 bmdma 0x9400 irq 16
> ata8: PATA max UDMA/100 cmd 0x9800 ctl 0x9482 bmdma 0x9408 irq 16
> scsi6 : pata_jmicron
> ata7.00: ATAPI, max UDMA/66
> ata7.00: qc timeout (cmd 0xef)
> ata7.00: failed to set xfermode (err_mask=0x4)
> ata7.00: limiting speed to UDMA/44
> ata7: failed to recover some devices, retrying in 5 secs
> ata7.00: qc timeout (cmd 0xef)
> ata7.00: failed to set xfermode (err_mask=0x4)
> ata7.00: limiting speed to PIO0
> ata7: failed to recover some devices, retrying in 5 secs
> ata7.00: qc timeout (cmd 0xef)
> ata7.00: failed to set xfermode (err_mask=0x4)
> ata7.00: disabled
> scsi7 : pata_jmicron
> ATA: abnormal status 0x7F on port 0x9807

This looks like the problems that hopefully the patches from Tejun and
from Mark Lord cured (the delay after reset and the task file clear)

> Also, I've seen a :
> 
> ata1: Spurious SDB FIS during NCQ issue=0x0 SAct=0x7ff8001f
> FIS=004040a1:00040000
> 
> What's this ? Is it really bad or just a warning ???

It's one Tejun stuck logging in for in order to investigate further.

Alan
-
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/