[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#390978: marked as done (linux-image-2.6.17-2-686: USB support regression: USB stick fails with ehci_hcd loaded)

Your message dated Mon, 15 Dec 2008 22:49:00 -0500
with message-id <4947252C.9040007@fastmail.fm>
and subject line Re: linux-image-2.6.17-2-686: USB support regression: USB stick	fails with ehci_hcd loaded
has caused the Debian Bug report #390978,
regarding linux-image-2.6.17-2-686: USB support regression: USB stick fails with ehci_hcd loaded
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
390978: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=390978
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.17-2-686
Version: 2.6.17-9
Severity: normal

In 2.6.15-*, my USB pen drive worked normally.
In 2.6.16-* and 2.6.17-*, if I 'rmmod ehci_hcd' before inserting
it, it works normally.

But if ehci_hcd is loaded, it flakes out badly.  The way it
flakes out varies.

This is a Dell Dimension 4600.

I would be perfectly happy if I could force the kernel to recognize
the pen drive as "full speed" and not "high speed".  But I don't
really want to lose the ability to have other high speed devices.

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (990, 'testing'), (50, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages linux-image-2.6.17-2-686 depends on:
ii  module-init-tools             3.2.2-3    tools for managing Linux kernel mo
ii  yaird [linux-initramfs-tool]  0.0.12-18  Yet Another mkInitRD

Versions of packages linux-image-2.6.17-2-686 recommends:
ii  libc6-i686                   2.3.6.ds1-4 GNU C Library: Shared libraries [i

-- debconf information:
  linux-image-2.6.17-2-686/postinst/old-initrd-link-2.6.17-2-686: true
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.17-2-686/postinst/old-dir-initrd-link-2.6.17-2-686: true
  linux-image-2.6.17-2-686/preinst/lilo-initrd-2.6.17-2-686: true
  linux-image-2.6.17-2-686/preinst/failed-to-move-modules-2.6.17-2-686:
  linux-image-2.6.17-2-686/postinst/depmod-error-initrd-2.6.17-2-686: false
  linux-image-2.6.17-2-686/postinst/create-kimage-link-2.6.17-2-686: true
  linux-image-2.6.17-2-686/postinst/bootloader-test-error-2.6.17-2-686:
  linux-image-2.6.17-2-686/preinst/lilo-has-ramdisk:
  linux-image-2.6.17-2-686/prerm/removing-running-kernel-2.6.17-2-686: true
  linux-image-2.6.17-2-686/preinst/abort-overwrite-2.6.17-2-686:
  linux-image-2.6.17-2-686/preinst/already-running-this-2.6.17-2-686:
  linux-image-2.6.17-2-686/postinst/old-system-map-link-2.6.17-2-686: true
  linux-image-2.6.17-2-686/preinst/bootloader-initrd-2.6.17-2-686: true
  linux-image-2.6.17-2-686/preinst/initrd-2.6.17-2-686:
  linux-image-2.6.17-2-686/preinst/abort-install-2.6.17-2-686:
  linux-image-2.6.17-2-686/preinst/overwriting-modules-2.6.17-2-686: true
  linux-image-2.6.17-2-686/postinst/kimage-is-a-directory:
  linux-image-2.6.17-2-686/preinst/elilo-initrd-2.6.17-2-686: true
  linux-image-2.6.17-2-686/prerm/would-invalidate-boot-loader-2.6.17-2-686: true
  linux-image-2.6.17-2-686/postinst/depmod-error-2.6.17-2-686: false
  linux-image-2.6.17-2-686/postinst/bootloader-error-2.6.17-2-686:

--- End Message ---
--- Begin Message --- 
Version: 2.6.26

Moritz Muehlenhoff wrote:
> On Wed, May 14, 2008 at 09:53:20AM +0200, maximilian attems wrote:
>>> Yes, I can reproduce this bug with 2.6.18-3-686.
>>> so if you need any testing you'll have to ask.
>> please send in an update to the issue for a recent kernel aka >= 2.6.24
> 
> Nathanael,
> does #390978 still occur with more recent kernel versions?

It appears not.  I'm not actually sure which computer I reported this
with originally.

I am happy to report that on computer 1 (the most likely):
(1) My kernel correctly fails to load ehci_hcd, even though the
blacklist file was destroyed at some point.
(2) When I force-load ehci_hcd, the pen drive is still recognized
through uhci_hcd and recognized as a full speed device.

On computer 2, the pen drive is recognized through ehci_hcd as a high
speed device -- but I can't reproduce the original erratic behavior, so
I'm assuming it's gone.

> If you're running Etch, could you try to reproduce this bug
> with the 2.6.24 based kernel added in 4.0r4?
> http://packages.qa.debian.org/l/linux-2.6.24.html

But I've switched to Lenny.  (Kernel 2.6.26-1-686).  I really don't know
when the bug was fixed.

Thanks for checking back with me!

--- End Message ---
Reply to: