Hi, I'm using the gentoo-sources-2.6.24-r2 with the Sis PATA support enabled in the kernel. Now I get the following message on boot: ata2.01: failed to IDENTIFY (I/O error, err_mask=0x1) ata2: failed to recover some devices, retrying in 5 secs This is ok, because there is no device which can be detectet! But this is annoying, because this message repaets three times and the result is that I need to wait 15 secs on boot. With the gentoo-sources-2.6.22-r8 this is no problem. The message "failed to IDENTIFY" does exists, but it doesn't wait before retrying. My question: Is it possible to set the secs to zero or to deactivate scanning of some ports? (e.g with a boot parameter?) I believe the reason for this problem is, that the CDROM in my notebook is flashed to cable-select (but I'm not sure IF it is cable-select...). I didn't post this in the kernel bugzilla yet, because I couldn't test this system independent with the mainline kernel. I hope I can get help here or should I post this in the kernel bugzilla? Greetings Jan Bücken Reproducible: Always In the following a cutout of dmesg which could be interesting: pata_sis 0000:00:02.5: version 0.5.2 scsi0 : pata_sis scsi1 : pata_sis ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0x1000 irq 14 ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0x1008 irq 15 Marking TSC unstable due to: possible TSC halt in C2. Time: acpi_pm clocksource has been installed. Switched to high resolution mode on CPU 0 ata1.00: ATA-5: HITACHI_DK23DA-40, 00J0A0A1, max UDMA/100 ata1.00: 78140160 sectors, multi 16: LBA ata1.00: limited to UDMA/33 due to 40-wire cable ata1.00: configured for UDMA/33 ata2.01: failed to IDENTIFY (I/O error, err_mask=0x1) ata2: failed to recover some devices, retrying in 5 secs ata2.01: failed to IDENTIFY (I/O error, err_mask=0x1) ata2: failed to recover some devices, retrying in 5 secs ata2.01: failed to IDENTIFY (I/O error, err_mask=0x1) ata2: failed to recover some devices, retrying in 5 secs ata2.00: ATAPI: QSI CD-RW/DVD-ROM SBW-161, SX13, max UDMA/33 ata2.00: configured for UDMA/33
(In reply to comment #0) > My question: Is it possible to set the secs to zero or to deactivate scanning > of some ports? (e.g with a boot parameter?) Well, like sda=noprobe sdb=noprobe or do you mean something else?
Hi, thanks for your fast answer, but this is not what I'm looking for. I don't want to scan the ata2.01 - port or I want to set the secs to zero. I tested sd*=noprobe. It deactivate checking the device sd* if it is present (isn't it?). But there is only one PATA HDD (which is detected on ata1.00, called sda later) and one (PATA) CDROM (on ata2.00). I cannot skip the test for ata2.01 with this (It semms to me that this time on boot the devices are not assigned to one sd* yet).
(In reply to comment #0) > Hi, > I'm using the gentoo-sources-2.6.24-r2 with the Sis PATA support enabled in the > kernel. > Now I get the following message on boot: > ata2.01: failed to IDENTIFY (I/O error, err_mask=0x1) > ata2: failed to recover some devices, retrying in 5 secs > > This is ok, because there is no device which can be detectet! But this is > annoying, because this message repaets three times and the result is that I > need to wait 15 secs on boot. > With the gentoo-sources-2.6.22-r8 this is no problem. The message "failed to > IDENTIFY" does exists, but it doesn't wait before retrying. > > > My question: Is it possible to set the secs to zero or to deactivate scanning > of some ports? (e.g with a boot parameter?) > > I believe the reason for this problem is, that the CDROM in my notebook is > flashed to cable-select (but I'm not sure IF it is cable-select...). > > I didn't post this in the kernel bugzilla yet, because I couldn't test this > system independent with the mainline kernel. > I hope I can get help here or should I post this in the kernel bugzilla? > > Greetings > Jan Bücken > > Reproducible: Always > > > > > In the following a cutout of dmesg which could be interesting: > > pata_sis 0000:00:02.5: version 0.5.2 > scsi0 : pata_sis > scsi1 : pata_sis > ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0x1000 irq 14 > ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0x1008 irq 15 > Marking TSC unstable due to: possible TSC halt in C2. > Time: acpi_pm clocksource has been installed. > Switched to high resolution mode on CPU 0 > ata1.00: ATA-5: HITACHI_DK23DA-40, 00J0A0A1, max UDMA/100 > ata1.00: 78140160 sectors, multi 16: LBA > ata1.00: limited to UDMA/33 due to 40-wire cable > ata1.00: configured for UDMA/33 > ata2.01: failed to IDENTIFY (I/O error, err_mask=0x1) > ata2: failed to recover some devices, retrying in 5 secs > ata2.01: failed to IDENTIFY (I/O error, err_mask=0x1) > ata2: failed to recover some devices, retrying in 5 secs > ata2.01: failed to IDENTIFY (I/O error, err_mask=0x1) > ata2: failed to recover some devices, retrying in 5 secs > ata2.00: ATAPI: QSI CD-RW/DVD-ROM SBW-161, SX13, max UDMA/33 > ata2.00: configured for UDMA/33 > I am having the same problem with Gentoo-sources 2.6.24-r3 and with vanilla-sources 2.6.25-rc6. What is worse in my case is that the HD-Led remains lit! My board is an Asus P5W DH Deluxe. If you need more info I'll will supply that. Gerard.
Hi, because this is not really a gentoo sources bug (confirming it with vanilla) I posted it in the kernel bugzilla and the bug is assigned and I just tested a debug-patch. http://bugzilla.kernel.org/show_bug.cgi?id=10254 Maybe we can help there... Greetings Jan
Hi, there is a patch upstream request now. "[PATCH #upstream-fixes] libata: assume no device is attached if both IDENTIFYs are aborted" You can find it at http://bugzilla.kernel.org/show_bug.cgi?id=10254 (because of a little mistake you have to insert a ";" yourself or wait till it is official released) Tested it with vanilla sources (2.6.24.3), not tested it with the gentoo sources yet. Besides: The bug is set to code_fix in the kernel bugzilla, hence you cannot find it with the search of the kernel bugzilla. Follow the Link directly.
Created attachment 147000 [details, diff] the patch I described in comment 5, but sharped it up with the ";" Hi, I tested this patch from Tejun Heo (http://bugzilla.kernel.org/show_bug.cgi?id=10254) It works for me with vanilla-sources 2.6.24.3 AND gentoo-sources 2.6.24-r3 !!! Happy Easter PS: @Gerard: Please have a look at comment 12 at the kernel bugzilla bug (Link above), maybe there is work for you ;-) Tejun wants you to file a bug report there and cc him.
We'll keep an eye on this one and see when it makes Linus' development tree.
Looks like upstream committed a fix to 2.6.25. http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff_plain;h=1ffc151fcddf524d0c76709d7e7a2af0255acb6b Can someone please apply the patch to 2.6.24-gentoo-r3 and give it a whirl to be sure?
I run a diff to the patch at the link and the patch I posted, its exactly the same with some comment lines, hence I just tested the patch with gentoo-2.6.24-r3 (comment 6) Since I posted comment 6 the patched kernel is running on my system ONLY, no problems.
Fixed in gentoo-sources-2.6.24-r4 (genpatches-2.6.24-5), thanks for taking the initiative upstream
Hi, I only want to cofirm that it is fixed with gentoo-soruces 2.6.24-r4. Thanks.
mmh, one thing: should I change this to closed or leave it to fixed? For me its closed...
