linux-kernel - Re: e-SATA ExpressCard - OOPS plus incrementing "ataX" on Linux-2.6.xx

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]

Message-ID: <4C16D6CB.9050704@garzik.org>
Date:	Mon, 14 Jun 2010 21:26:35 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Jeff Chua <jeff.chua.linux@...il.com>
CC:	Greg KH <greg@...ah.com>, kristen.c.accardi@...el.com,
	Dely Sy <dely.l.sy@...el.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	lkml <linux-kernel@...r.kernel.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	Takayoshi Kochi <t-kochi@...jp.nec.com>,
	Matthew Wilcox <willy@...com>
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@...ah.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



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