From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-scsi@vger.kernel.org,
"bugme-daemon@kernel-bugs.osdl.org"
<bugme-daemon@bugzilla.kernel.org>,
jpw@wszib.edu.pl
Subject: Re: [Bugme-new] [Bug 7444] New: BUG on drive removal with pata_cmd64x
Date: Thu, 02 Nov 2006 11:38:17 +0000 [thread overview]
Message-ID: <1162467497.11965.163.camel@localhost.localdomain> (raw)
In-Reply-To: <20061101120258.e7462f9f.akpm@osdl.org>
Ar Mer, 2006-11-01 am 12:02 -0800, ysgrifennodd Andrew Morton:
> Dunno if this is a scsi thing or an Alan thing. But it is certainly a
> thing!
> > and driver hangs in a non-functional state (neither removed nor active)
> > HOWEVER,
> > going to /sys/bus/scsi/devices/X:0:0:0/ and echo'ing 1 to delete triggers the
> > same BUG; the drive disappears from the system correctly(!) and pata_cmd64x can
> > be removed from system without further problems.
It actually looks like a refcounting problem - could be in the SCSI code
or in the libata code or in the AHCI code. I don't think it's in the
driver however as the drivers don't carry custom code in that area
> > On a subsequent docking, the drive affected by the above bug appears to be
> > confused and kernel complains about not being able to identify the drive,
> > however, after a few attempts it manages to reset the drive.
> >
That I think I understand assuming the first time you booted with the
drive plugged in ?
Alan
prev parent reply other threads:[~2006-11-02 11:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200611011240.kA1Ceaj7025489@fire-2.osdl.org>
2006-11-01 20:02 ` [Bugme-new] [Bug 7444] New: BUG on drive removal with pata_cmd64x Andrew Morton
2006-11-02 11:38 ` Alan Cox [this message]
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=1162467497.11965.163.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@osdl.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=jpw@wszib.edu.pl \
--cc=linux-scsi@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox