> Thanks. This should fix the real cause, and also allow for port start to > fail politely with -ENODEV. Works fine here - no more strange messages. Thank you! -- Meelis Roos ([email protected]) -- 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:
- ata4294967295: failed to start port (errno=-19)
- From: Meelis Roos <[email protected]>
- Re: ata4294967295: failed to start port (errno=-19)
- From: Alan Cox <[email protected]>
- Re: ata4294967295: failed to start port (errno=-19)
- From: Meelis Roos <[email protected]>
- [PATCH] libata: Fix early use of port printk. (Was Re: ata4294967295: failed to start port (errno=-19))
- From: Alan Cox <[email protected]>
- ata4294967295: failed to start port (errno=-19)
- Prev by Date: Re: Kernel Development & Objective-C
- Next by Date: Re: Kernel 2.6.23.9 / P35 Chipset + WD 750GB Drives (reset port)
- Previous by thread: [PATCH] libata: Fix early use of port printk. (Was Re: ata4294967295: failed to start port (errno=-19))
- Next by thread: Re: [PATCH] libata: Fix early use of port printk. (Was Re: ata4294967295: failed to start port (errno=-19))
- Index(es):
 |