From: Greg KH on
On Mon, Jun 14, 2010 at 11:16:29PM +0800, Jeff Chua wrote:
> Hi,
>
> I just buy an e-SATA ExpressCard and trying on my notebook. It's able
> to see the external SATA harddisk. On initial boot, I'm seeing the
> following OOPS.
>
>
> 2010-06-14T16:43:21.077256+08:00 boston kernel: scsi 6:0:0:0:
> Direct-Access ATA SAMSUNG MCCOE64G PS10 PQ: 0 ANSI: 5
> 2010-06-14T16:43:21.077258+08:00 boston kernel: sd 6:0:0:0: [sdb]
> 125045424 512-byte logical blocks: (64.0 GB/59.6 GiB)
> 2010-06-14T16:43:21.077260+08:00 boston kernel: sd 6:0:0:0: Attached
> scsi generic sg1 type 0
> 2010-06-14T16:43:21.077261+08:00 boston kernel: sd 6:0:0:0: [sdb]
> Write Protect is off
> 2010-06-14T16:43:21.077264+08:00 boston kernel: sd 6:0:0:0: [sdb] Mode
> Sense: 00 3a 00 00
> 2010-06-14T16:43:21.077266+08:00 boston kernel: sd 6:0:0:0: [sdb]
> Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> 2010-06-14T16:43:21.077267+08:00 boston kernel: sdb: sdb1
> 2010-06-14T16:43:21.077268+08:00 boston kernel: sd 6:0:0:0: [sdb]
> Attached SCSI disk
> 2010-06-14T16:43:21.077270+08:00 boston kernel: ------------[ cut here
> ]------------
> 2010-06-14T16:43:21.077272+08:00 boston kernel: WARNING: at
> fs/sysfs/dir.c:451 sysfs_add_one+0x82/0x95()
> 2010-06-14T16:43:21.077273+08:00 boston kernel: Hardware name: 5413FGA
> 2010-06-14T16:43:21.077276+08:00 boston kernel: sysfs: cannot create
> duplicate filename
> '/devices/pci0000:00/0000:00:1c.3/0000:05:00.0/slot'

This is a warning that you can ignore, it's been fixed in the latest
tree (2.6.35-rc3).

try that and see.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Greg KH on
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(a)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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Robert Hancock on
On 06/14/2010 12:44 PM, Jeff Chua wrote:
> On Tue, Jun 15, 2010 at 12:20 AM, Greg KH<greg(a)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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Jeff Garzik on
On 06/14/2010 02:44 PM, Jeff Chua wrote:
> On Tue, Jun 15, 2010 at 12:20 AM, Greg KH<greg(a)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



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