This bug was fixed in the package linux-source-2.6.22 - 2.6.22-15.54
---
linux-source-2.6.22 (2.6.22-15.54) gutsy-security; urgency=low
[Colin Ian King]
* usb-storage: always set the allow_restart flag
- LP: #193154
[Upstream Kernel Changes]
* [IA64] Fix unaligned handl
Have an Inspiron 1525N with Dell installed Ubuntu 7.10 and a Seagate
Freeagent external USB drive, so also this problem. Under Dell
purchased Canonical support agreement, I've opened a case. FYI, I
needed a working external for backup prior to upgrading to 8.04.
Consider me a test case.
--
Anot
SRU justification:
Impact: Seagate FreeAgent external drive still suffers from the
drive-dies-after-it-suspends bug in Gutsy.
Patch: (see attached) this small patch is backported from upstream
and is verified to work on Hardy.
Testcase: Suspend and resume with external Seagate FreeAgent drive.
** Changed in: linux-source-2.6.22 (Ubuntu)
Assignee: (unassigned) => Colin King (colin-king)
--
Another Seagate FreeAgent needs allow_restart quirk
https://bugs.launchpad.net/bugs/193154
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Ah I see. Well, most Ubuntu developers would like to live under the
motto "fix it right over fix it fast" (I hope), and the allow_restart
kernel based quirk has been adopted in Hardy already, so from a QA
standpoint it's better to backport the Hardy fix
--
Another Seagate FreeAgent needs allow_re
Ah, I think you may have misunderstood me. I agree 100% that we
shouldn't expect users to work around this problem on their own. That
would be extremely lame.
All I was trying to suggest is that instead of waiting until the next
kernel update to fix this, Ubuntu could just release an update to the
A hack is a hack, and that's exactly what the above solution is. I'm not
asking for a kernel backport solely to address this bug, I'm merely
asking for it to be considered for bundling with the next kernel update
-- bugfix updates are routinely bundled in this fashion AFAIK.
I know how to perform
Double oops. It turns out that the last udev rule I posted doesn't
always work. I can't figure out why that is, but here's a simpler rule
that seems to work all of the time.
# Set the allow_restart flag for all SCSI disks.
ACTION=="add", \
SUBSYSTEM=="scsi_disk", \
ATTR{allow_restart}="1"
(Note t
Oops, I typo'd the udev rule in my last comment. It is missing a comma.
Oddly enough, udev appears to parse it just fine, but I doubt you'll
want to rely on that.
Here's the correct version:
# Set the allow_restart flag for all USB mass storage devices
ACTION=="add", \
SUBSYSTEM=="scsi", DRIVER==
While I agree that this is a serious and very annoying bug, I don't
think a kernel backport is necessary to fix it. A simple udev rule is
all that's needed to make sure the allow_restart flag is always set.
Here's how to fix it on Gutsy:
1) Open a terminal.
2) Type [ sudo nano /etc/udev/rules.d/9
Oops never mind, I just verified behavior is correct on Hardy, likely
because of http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-
hardy.git;a=commit;h=f09e495df27d80ae77005ddb2e93df18ec24d04a, which IMO
should be backported to Gutsy's kernel
** Changed in: linux (Ubuntu)
Status: New => Fix Rel
11 matches
Mail list logo
