Re: scary message 'failed to recover some devices ... retrying' HPT370

Ar Maw, 2006-10-31 am 19:59 +0100, ysgrifennodd jurriaan:
> ata11.00: ATA-6, max UDMA/100, 488397168 sectors: LBA48
> ata11.00: ata11: dev 0 multi count 16

Found the master happily

> ata11.01: failed to IDENTIFY (I/O error, err_mask=0x1)
> ata11: failed to recover some devices, retrying in 5 secs
> ata11.01: failed to IDENTIFY (I/O error, err_mask=0x1)
> ata11: failed to recover some devices, retrying in 5 secs
> ata11.01: failed to IDENTIFY (I/O error, err_mask=0x1)
> ata11: failed to recover some devices, retrying in 5 secs

Slave probing is noisy and annoying right now because it tries too hard
but this fine (unless oyuhave a slave device)

Thanks for the report. I'll review the drive detect for the chip but I
suspect it just needs to switch to the polling probe.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • scary message 'failed to recover some devices ... retrying' HPT370
    • From: jurriaan <[email protected]>

• Prev by Date: Re: [PATCH] 0/3: Fix EH problems in libsas and implement more error handling
• Next by Date: Re: Suspend to disk: do we HAVE to use swap?
• Previous by thread: scary message 'failed to recover some devices ... retrying' HPT370
• Next by thread: [PATCH] Allow a hyphenated range in get_options, with cleanup
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]