From: bugme-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 12120] [Block layer or SCSI] requests aborted too early during check_partition()
Date: Sat, 29 Nov 2008 07:12:35 -0800 (PST) [thread overview]
Message-ID: <20081129151235.C9895108041@picon.linux-foundation.org> (raw)
In-Reply-To: <bug-12120-11613@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=12120
------- Comment #1 from anonymous@kernel-bugs.osdl.org 2008-11-29 07:12 -------
Reply-To: stefanr@s5r6.in-berlin.de
On 29 Nov, bugme-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=12120
>
> Summary: [Block layer or SCSI] requests aborted too early during
> check_partition()
> Product: IO/Storage
> Version: 2.5
> KernelVersion: 2.6.28-rc
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: SCSI
> AssignedTo: linux-scsi@vger.kernel.org
> ReportedBy: stefan-r-bz@s5r6.in-berlin.de
> OtherBugsDependingO 11808
> nThis:
> Regression: 1
>
>
> Latest working kernel version: 2.6.27.4
> Earliest failing kernel version: 2.6.28-rc6 (I didn't test earlier -rcs yet)
>
> Hardware Environment: OxSemi 912 and 92x based FireWire harddisks
>
>
> See http://marc.info/?l=linux-scsi&m=122774022130397 --
> Disks may still spin their motor up when the kernel attempts to read
> partitions. In kernel 2.6.27, this was handled transparently. But since
> 2.6.28-rc?, the kernel immediately aborts the associated requests and sets the
> new scsi_device offline.
>
>
I tried a workaround in firewire-sbp2: Check whether the new sdev is
offline right after scsi_add_device. If so, remove the sdev and try
everything again. However,
- a regression still remains because the addition of the HDD takes
about 30...40 seconds instead of only a few seconds like in 2.6.27.
- The workaround works with OXFW912 and OXUF922, but not with
OXUF924DSB. Login retries don't succeed with the latter at all.
- The workaround would be very hard to implement in the older
ieee1394/sbp2 driver.
- Other hardware besides FireWire may be affected.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2008-11-29 15:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-29 13:19 [Bug 12120] New: [Block layer or SCSI] requests aborted too early during check_partition() bugme-daemon
2008-11-29 15:12 ` Stefan Richter
2008-11-29 18:35 ` James Bottomley
2008-11-29 15:12 ` bugme-daemon [this message]
2008-11-29 18:36 ` [Bug 12120] " bugme-daemon
2008-11-29 19:29 ` bugme-daemon
2008-11-29 19:32 ` bugme-daemon
2008-11-29 19:54 ` James Bottomley
2008-11-29 21:30 ` Stefan Richter
2008-11-29 21:45 ` Stefan Richter
2008-11-30 0:08 ` James Bottomley
2008-11-30 9:44 ` Stefan Richter
2008-11-30 16:16 ` James Bottomley
2008-11-29 19:55 ` bugme-daemon
2008-11-29 21:30 ` bugme-daemon
2008-11-29 21:45 ` bugme-daemon
2008-11-30 0:08 ` bugme-daemon
2008-11-30 9:44 ` bugme-daemon
2008-11-30 16:16 ` bugme-daemon
2008-12-04 1:15 ` bugme-daemon
2008-12-04 6:38 ` bugme-daemon
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=20081129151235.C9895108041@picon.linux-foundation.org \
--to=bugme-daemon@bugzilla.kernel.org \
--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