* Re: e-SATA ExpressCard - OOPS plus incrementing "ataX" on Linux-2.6.xx
2010-06-14 18:44 ` Jeff Chua
@ 2010-06-14 19:35 ` Greg KH
2010-06-14 20:17 ` Jeff Chua
2010-06-14 23:49 ` Robert Hancock
2010-06-15 1:26 ` Jeff Garzik
2 siblings, 1 reply; 10+ messages in thread
From: Greg KH @ 2010-06-14 19:35 UTC (permalink / raw)
To: Jeff Chua
Cc: kristen.c.accardi, Dely Sy, Linus Torvalds, lkml,
Rafael J. Wysocki, Takayoshi Kochi, Matthew Wilcox
On Tue, Jun 15, 2010 at 02:44:36AM +0800, 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.
Note, it was not an oops, just a warning, and would not cause any
problems.
> 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?
I don't know, maybe the libata developers can help you out here.
good luck,
greg k-h
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: e-SATA ExpressCard - OOPS plus incrementing "ataX" on Linux-2.6.xx
2010-06-14 19:35 ` Greg KH
@ 2010-06-14 20:17 ` Jeff Chua
0 siblings, 0 replies; 10+ messages in thread
From: Jeff Chua @ 2010-06-14 20:17 UTC (permalink / raw)
To: Greg KH
Cc: kristen.c.accardi, Dely Sy, Linus Torvalds, lkml,
Rafael J. Wysocki, Takayoshi Kochi, Matthew Wilcox
On Tue, Jun 15, 2010 at 3:35 AM, Greg KH <greg@kroah.com> wrote:
> On Tue, Jun 15, 2010 at 02:44:36AM +0800, 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.
>
> Note, it was not an oops, just a warning, and would not cause any
> problems.
Ok, understood.
>> 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?
> I don't know, maybe the libata developers can help you out here.
> good luck,
Cool. Hopefully someone has the solution.
Thanks!
Jeff
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: e-SATA ExpressCard - OOPS plus incrementing "ataX" on Linux-2.6.xx
2010-06-14 18:44 ` Jeff Chua
2010-06-14 19:35 ` Greg KH
@ 2010-06-14 23:49 ` Robert Hancock
2010-06-15 12:08 ` Jeff Chua
2010-06-15 1:26 ` Jeff Garzik
2 siblings, 1 reply; 10+ messages in thread
From: Robert Hancock @ 2010-06-14 23:49 UTC (permalink / raw)
To: Jeff Chua
Cc: Greg KH, kristen.c.accardi, Dely Sy, Linus Torvalds, lkml,
Rafael J. Wysocki, Takayoshi Kochi, Matthew Wilcox
On 06/14/2010 12: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 ataX number incrementing is normal (it always increments when an ATA
host is initialized, it doesn't appear the numbers get reused). The
other messages are the expected result when you surprise-remove the
card. I think there should be a way to trigger the hotplug code to
disable the device before you eject it, but I'm not sure what that is
supposed to be - maybe echo 1 to /sys/device/pci_somethingorother/remove ?
>
> 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)
> 2010-06-15T02:32:05.068797+08:00 boston kernel: ahci 0000:05:00.0: PCI
> INT A disabled
>
>
>
> Thanks,
> Jeff
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: e-SATA ExpressCard - OOPS plus incrementing "ataX" on Linux-2.6.xx
2010-06-14 23:49 ` Robert Hancock
@ 2010-06-15 12:08 ` Jeff Chua
2010-06-15 14:52 ` Robert Hancock
0 siblings, 1 reply; 10+ messages in thread
From: Jeff Chua @ 2010-06-15 12:08 UTC (permalink / raw)
To: Robert Hancock, Jeff Garzik
Cc: Greg KH, kristen.c.accardi, Dely Sy, Linus Torvalds, lkml,
Rafael J. Wysocki, Matthew Wilcox
On Tue, Jun 15, 2010 at 7:49 AM, Robert Hancock <hancockrwd@gmail.com> wrote:
> The ataX number incrementing is normal (it always increments when an ATA
> host is initialized, it doesn't appear the numbers get reused). The other
> messages are the expected result when you surprise-remove the card. I think
> there should be a way to trigger the hotplug code to disable the device
> before you eject it, but I'm not sure what that is supposed to be - maybe
> echo 1 to /sys/device/pci_somethingorother/remove ?
Robert,
Thanks for the pointer. I found this "remove" is in
/sys/bus/pci/devices/0000:05:00.0/remove
# echo 1 >/sys/bus/pci/devices/0000:05:00.0/remove
ata14.00: disabled
sd 17:0:0:0: [sdb] Synchronizing SCSI cache
sd 17:0:0:0: [sdb] Result: hostbyte=0x04 driverbyte=0x00
sd 17:0:0:0: [sdb] Stopping disk
sd 17:0:0:0: [sdb] START_STOP FAILED
sd 17:0:0:0: [sdb] Result: hostbyte=0x04 driverbyte=0x00
ahci 0000:05:00.0: PCI INT A disabled
It's getter better. Next is to really shutdown the "sdb" hard disk. Is
that possible? Would be nice to make the "sd 17:0:0:0: [sdb]
START_STOP FAILED" go away gracefully. Any command to do that?
On Tue, Jun 15, 2010 at 9:26 AM, Jeff Garzik <jeff@garzik.org> wrote:
> The incrementing of ataX is unrelated to anything else... Each "new" ata interface gets a new id.
Jeff,
With the "remove" command working, it'll be nice to make "ahci"
_reuse_ the interface now that it's removed cleanly. I'm just afaid
that each time the card is removed and reinserted, the ataXX interface
kept incrementing and will eventually does harm to the kernel?
> "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.
Ok, that's fixed with "echo 1 >/sys/bus/pci/devices/0000:05:00.0/remove".
Thanks,
Jeff
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: e-SATA ExpressCard - OOPS plus incrementing "ataX" on Linux-2.6.xx
2010-06-15 12:08 ` Jeff Chua
@ 2010-06-15 14:52 ` Robert Hancock
2010-06-15 16:02 ` Jeff Chua
0 siblings, 1 reply; 10+ messages in thread
From: Robert Hancock @ 2010-06-15 14:52 UTC (permalink / raw)
To: Jeff Chua
Cc: Jeff Garzik, Greg KH, kristen.c.accardi, Dely Sy, Linus Torvalds,
lkml, Rafael J. Wysocki, Matthew Wilcox
On Tue, Jun 15, 2010 at 6:08 AM, Jeff Chua <jeff.chua.linux@gmail.com> wrote:
> On Tue, Jun 15, 2010 at 7:49 AM, Robert Hancock <hancockrwd@gmail.com> wrote:
>
>> The ataX number incrementing is normal (it always increments when an ATA
>> host is initialized, it doesn't appear the numbers get reused). The other
>> messages are the expected result when you surprise-remove the card. I think
>> there should be a way to trigger the hotplug code to disable the device
>> before you eject it, but I'm not sure what that is supposed to be - maybe
>> echo 1 to /sys/device/pci_somethingorother/remove ?
>
> Robert,
>
> Thanks for the pointer. I found this "remove" is in
> /sys/bus/pci/devices/0000:05:00.0/remove
>
> # echo 1 >/sys/bus/pci/devices/0000:05:00.0/remove
>
> ata14.00: disabled
> sd 17:0:0:0: [sdb] Synchronizing SCSI cache
> sd 17:0:0:0: [sdb] Result: hostbyte=0x04 driverbyte=0x00
> sd 17:0:0:0: [sdb] Stopping disk
> sd 17:0:0:0: [sdb] START_STOP FAILED
> sd 17:0:0:0: [sdb] Result: hostbyte=0x04 driverbyte=0x00
> ahci 0000:05:00.0: PCI INT A disabled
>
>
> It's getter better. Next is to really shutdown the "sdb" hard disk. Is
> that possible? Would be nice to make the "sd 17:0:0:0: [sdb]
> START_STOP FAILED" go away gracefully. Any command to do that?
Try echoing 1 to the file for the SCSI disk's "delete" file, something
like: /sys/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/delete
>
>
> On Tue, Jun 15, 2010 at 9:26 AM, Jeff Garzik <jeff@garzik.org> wrote:
>
>> The incrementing of ataX is unrelated to anything else... Each "new" ata interface gets a new id.
>
> Jeff,
>
> With the "remove" command working, it'll be nice to make "ahci"
> _reuse_ the interface now that it's removed cleanly. I'm just afaid
> that each time the card is removed and reinserted, the ataXX interface
> kept incrementing and will eventually does harm to the kernel?
I don't think so, it's just a number used to associate debug output
for the device. I suppose if you did it 2 billion times it might wrap
negative but even that would just be cosmetic..
>
>
>> "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.
>
> Ok, that's fixed with "echo 1 >/sys/bus/pci/devices/0000:05:00.0/remove".
>
>
>
> Thanks,
> Jeff
>
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: e-SATA ExpressCard - OOPS plus incrementing "ataX" on Linux-2.6.xx
2010-06-15 14:52 ` Robert Hancock
@ 2010-06-15 16:02 ` Jeff Chua
0 siblings, 0 replies; 10+ messages in thread
From: Jeff Chua @ 2010-06-15 16:02 UTC (permalink / raw)
To: Robert Hancock
Cc: Jeff Garzik, Greg KH, kristen.c.accardi, Dely Sy, Linus Torvalds,
lkml, Rafael J. Wysocki, Matthew Wilcox
On Tue, Jun 15, 2010 at 10:52 PM, Robert Hancock <hancockrwd@gmail.com> wrote:
> Try echoing 1 to the file for the SCSI disk's "delete" file, something
> like: /sys/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/delete
Very nice. That works!
sd 20:0:0:0: [sdb] Synchronizing SCSI cache
sd 20:0:0:0: [sdb] Stopping disk
ata17.00: disabled
/sys has so much cool things there, but I just didn't know what they were.
Thank you so much!
Jeff.
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: e-SATA ExpressCard - OOPS plus incrementing "ataX" on Linux-2.6.xx
2010-06-14 18:44 ` Jeff Chua
2010-06-14 19:35 ` Greg KH
2010-06-14 23:49 ` Robert Hancock
@ 2010-06-15 1:26 ` Jeff Garzik
2 siblings, 0 replies; 10+ messages in thread
From: Jeff Garzik @ 2010-06-15 1:26 UTC (permalink / raw)
To: Jeff Chua
Cc: Greg KH, kristen.c.accardi, Dely Sy, Linus Torvalds, lkml,
Rafael J. Wysocki, Takayoshi Kochi, Matthew Wilcox
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
^ permalink raw reply [flat|nested] 10+ messages in thread