From: Robert Hancock <hancockrwd@gmail.com>
To: Jeff Chua <jeff.chua.linux@gmail.com>
Cc: Greg KH <greg@kroah.com>,
kristen.c.accardi@intel.com, Dely Sy <dely.l.sy@intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
lkml <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Takayoshi Kochi <t-kochi@bq.jp.nec.com>,
Matthew Wilcox <willy@hp.com>
Subject: Re: e-SATA ExpressCard - OOPS plus incrementing "ataX" on Linux-2.6.xx
Date: Mon, 14 Jun 2010 17:49:09 -0600 [thread overview]
Message-ID: <4C16BFF5.7070308@gmail.com> (raw)
In-Reply-To: <AANLkTinwaYy5Z528PraVuWUsU2pJBLoq0c2hgIGirTNn@mail.gmail.com>
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
next prev parent reply other threads:[~2010-06-14 23:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-14 15:16 e-SATA ExpressCard - OOPS plus incrementing "ataX" on Linux-2.6.xx Jeff Chua
2010-06-14 16:20 ` Greg KH
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 [this message]
2010-06-15 12:08 ` Jeff Chua
2010-06-15 14:52 ` Robert Hancock
2010-06-15 16:02 ` Jeff Chua
2010-06-15 1:26 ` Jeff Garzik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C16BFF5.7070308@gmail.com \
--to=hancockrwd@gmail.com \
--cc=dely.l.sy@intel.com \
--cc=greg@kroah.com \
--cc=jeff.chua.linux@gmail.com \
--cc=kristen.c.accardi@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=t-kochi@bq.jp.nec.com \
--cc=torvalds@linux-foundation.org \
--cc=willy@hp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.