On Tue, Jan 08, 2008 at 11:32:33PM -0800, Bob McGowan wrote:
> Package: linux-image-2.6.18-5-amd64
> Version: 2.6.18.dfsg.1-17
> Severity: normal
>
> I have a usb 2.0 160 GB disk drive which I've been trying to use with my
> HP laptop, but after some period of time (usually short, less than 2
> minutes) the disk would "die".
>
> Research led to a possible solution, using sdparm to clear STANDBY,
> which is set by default for this drive (Seagate Freeagent Go). This
> seemed to work, initially, but it didn't "hold". Checked the STANDBY
> state, it was still cleared.
>
> And, other usb 2.0 devices also failed to work. Extensive further
> research and testing showed that all these devices would work for a
> short period of time before failing.
>
> The light dawned when I noted that the usb 2.0 interface uses IRQ 7,
> which was getting disabled shortly after startup, due to a spurious
> interrupt (nobody cared).
>
> With a usb device inserted while booting, or quickly attached after
> booting, along with mounting the disk device, there were no spurious
> interrupts, and the device remained usable. That is, until it/they
> waswere unmounted, at which point, with no usb 2.0 devices, a spurious
> interrupt would happen and usb 2.0 would not work any more.
>
> As proof of concept, I've moved my full system to the Freeagent disk and
> can boot to it, and run for hours, without issues.
>
> I have also booted a Suse 9.1 Live CD and have used the usb 2.0 devices
> without problems, even though dmesg does have one spurious interrupt
> error related to irq 7. The kernel version is 2.6.4
>
> My system is an HP Pavilion dv9000. The usb 2.0 hardware is reported as:
Did you upgrade to Lenny in the mean time? If so, did it fix the problem.
Cheers,
Moritz
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
