Messages in this thread | | | Date | Mon, 14 Jun 2010 21:26:35 -0400 | From | Jeff Garzik <> | Subject | Re: e-SATA ExpressCard - OOPS plus incrementing "ataX" on Linux-2.6.xx |
| |
On 06/14/2010 02:44 PM, Jeff Chua wrote: > On Tue, Jun 15, 2010 at 12:20 AM, Greg KH<greg@kroah.com> wrote: >> On Mon, Jun 14, 2010 at 11:16:29PM +0800, Jeff Chua wrote: > > >> This is a warning that you can ignore, it's been fixed in the latest >> tree (2.6.35-rc3). >> >> try that and see. > > Greg, > > Ok, just tried rc3 and it's fixed the 1st OOPS. > > But I'm still seeing the "ataX" incrementing from ata7 to ata8, ata9 > ... after taking out and putting back the card. It seems the interface > is still not shutting down properly. ... Any command to shutdown it > down gracefully?
The incrementing of ataX is unrelated to anything else... Each "new" ata interface gets a new id.
> ata9.00: disabled > 2010-06-15T02:32:04.531177+08:00 boston kernel: ata9.00: disabled > sd 8:0:0:0: [sdb] Synchronizing SCSI cache > sd 8:0:0:0: [sdb] Result: hostbyte=0x04 driverbyte=0x00 > sd 8:0:0:0: [sdb] Stopping disk > sd 8:0:0:0: [sdb] START_STOP FAILED > sd 8:0:0:0: [sdb] Result: hostbyte=0x04 driverbyte=0x00 > 2010-06-15T02:32:04.568687+08:00 boston kernel: sd 8:0:0:0: [sdb] > Synchronizing SCSI cache > 2010-06-15T02:32:04.568715+08:00 boston kernel: sd 8:0:0:0: [sdb] > Result: hostbyte=0x04 driverbyte=0x00 > 2010-06-15T02:32:04.568719+08:00 boston kernel: sd 8:0:0:0: [sdb] Stopping disk > 2010-06-15T02:32:04.568731+08:00 boston kernel: sd 8:0:0:0: [sdb] > START_STOP FAILED > 2010-06-15T02:32:04.568735+08:00 boston kernel: sd 8:0:0:0: [sdb] > Result: hostbyte=0x04 driverbyte=0x00 > ata9: failed to stop engine (-5) > ahci 0000:05:00.0: PCI INT A disabled > 2010-06-15T02:32:05.068765+08:00 boston kernel: ata9: failed to stop engine (-5)
"failed to stop engine" is where the driver is attempting to talk to the card, and gracefully shut things down. If the card does not exist (ie. has been removed/ejected), then this is normal behavior.
Jeff
| |