Public bug reported:
When connecting my usb stick to the computer, it is not automatically
discovered anymore. Even 'lsusb -v' does not show anything beside the
usb hub.
Instead, 'cat /proc/kmsg' produces messages like
[17180190.832000] usb 1-2: new full speed USB device using uhci_hcd and addre
hi,
that's ok, nice to see someone noticed at all :-)
i had found a workaround some time in the past, but i haven't been using
the usb stick for some time. i just tried it out again, and the bug is
still there.
i'm running feisty by now, so i should probably give you some new
diagnostic output.
...and the lsmod output.
As I said before, I'm now running Ubuntu 7.04 Feisty with kernel 2.6.20
and the problem remains. Should I move the bug to linux-source-2.6.20 or
create a bug report there with a link to this one?
If you need any other information for diagnostics, don't hesitate to
ask.
*
hi,
as promised, here is the output of dmesg on my currently running
system...
** Attachment added: "dmesg.txt"
http://librarian.launchpad.net/7492963/dmesg.txt
--
uhci_hcd generates flood of kernel messages while failing to mount usb stick
https://bugs.launchpad.net/bugs/50757
You received
Hi Johnathon,
removing the ehci_hcd module doesn't do anything (it wasn't loaded at
the time, as shown in the lsmod output). I've tried to load and remove
it again, which doesn't change anything. The sole troublemaker seems to
be the uhci_hcd module.
I remember having read something about the ker
Hi,
I've done everything and bundled it up in the attached tar file. There
is no devices.txt since there are no /dev/sd* devices even when the
stick is plugged in. hald doesn't say anything after the usual startup
mess, i.e. everything in hal.log is from _before_ attaching the stick.
Same with gvm
Hi,
with kernel 2.6.20-16-generic, the stick is working when plugged in for
the first time, although only after several scanning attempts:
[ 218.415370] usb 1-2: new full speed USB device using uhci_hcd and address 6
[ 218.919140] usb 1-2: new full speed USB device using uhci_hcd and address 7
Public bug reported:
When connecting my usb stick to the computer, it is not automatically
discovered anymore. Even 'lsusb -v' does not show anything beside the
usb hub.
Instead, 'cat /proc/kmsg' produces messages like
[17180190.832000] usb 1-2: new full speed USB device using uhci_hcd and addre
Hi,
with kernel 2.6.20-16-generic, the stick is working when plugged in for
the first time, although only after several scanning attempts:
[ 218.415370] usb 1-2: new full speed USB device using uhci_hcd and address 6
[ 218.919140] usb 1-2: new full speed USB device using uhci_hcd and address 7
hi,
that's ok, nice to see someone noticed at all :-)
i had found a workaround some time in the past, but i haven't been using
the usb stick for some time. i just tried it out again, and the bug is
still there.
i'm running feisty by now, so i should probably give you some new
diagnostic output.
...and the lsmod output.
As I said before, I'm now running Ubuntu 7.04 Feisty with kernel 2.6.20
and the problem remains. Should I move the bug to linux-source-2.6.20 or
create a bug report there with a link to this one?
If you need any other information for diagnostics, don't hesitate to
ask.
*
hi,
as promised, here is the output of dmesg on my currently running
system...
** Attachment added: "dmesg.txt"
http://librarian.launchpad.net/7492963/dmesg.txt
--
uhci_hcd generates flood of kernel messages while failing to mount usb stick
https://bugs.launchpad.net/bugs/50757
You received
Hi Johnathon,
removing the ehci_hcd module doesn't do anything (it wasn't loaded at
the time, as shown in the lsmod output). I've tried to load and remove
it again, which doesn't change anything. The sole troublemaker seems to
be the uhci_hcd module.
I remember having read something about the ker
Public bug reported:
When connecting my usb stick to the computer, it is not automatically
discovered anymore. Even 'lsusb -v' does not show anything beside the
usb hub.
Instead, 'cat /proc/kmsg' produces messages like
[17180190.832000] usb 1-2: new full speed USB device using uhci_hcd and addre
Hi,
I've done everything and bundled it up in the attached tar file. There
is no devices.txt since there are no /dev/sd* devices even when the
stick is plugged in. hald doesn't say anything after the usual startup
mess, i.e. everything in hal.log is from _before_ attaching the stick.
Same with gvm
...and the lsmod output.
As I said before, I'm now running Ubuntu 7.04 Feisty with kernel 2.6.20
and the problem remains. Should I move the bug to linux-source-2.6.20 or
create a bug report there with a link to this one?
If you need any other information for diagnostics, don't hesitate to
ask.
*
hi,
as promised, here is the output of dmesg on my currently running
system...
** Attachment added: "dmesg.txt"
http://librarian.launchpad.net/7492963/dmesg.txt
--
uhci_hcd generates flood of kernel messages while failing to mount usb stick
https://bugs.launchpad.net/bugs/50757
You received
Hi Johnathon,
removing the ehci_hcd module doesn't do anything (it wasn't loaded at
the time, as shown in the lsmod output). I've tried to load and remove
it again, which doesn't change anything. The sole troublemaker seems to
be the uhci_hcd module.
I remember having read something about the ker
Hi,
I've done everything and bundled it up in the attached tar file. There
is no devices.txt since there are no /dev/sd* devices even when the
stick is plugged in. hald doesn't say anything after the usual startup
mess, i.e. everything in hal.log is from _before_ attaching the stick.
Same with gvm
hi,
that's ok, nice to see someone noticed at all :-)
i had found a workaround some time in the past, but i haven't been using
the usb stick for some time. i just tried it out again, and the bug is
still there.
i'm running feisty by now, so i should probably give you some new
diagnostic output.
Hi,
with kernel 2.6.20-16-generic, the stick is working when plugged in for
the first time, although only after several scanning attempts:
[ 218.415370] usb 1-2: new full speed USB device using uhci_hcd and address 6
[ 218.919140] usb 1-2: new full speed USB device using uhci_hcd and address 7
Public bug reported:
When connecting my usb stick to the computer, it is not automatically
discovered anymore. Even 'lsusb -v' does not show anything beside the
usb hub.
Instead, 'cat /proc/kmsg' produces messages like
[17180190.832000] usb 1-2: new full speed USB device using uhci_hcd and addre
Hi,
with kernel 2.6.20-16-generic, the stick is working when plugged in for
the first time, although only after several scanning attempts:
[ 218.415370] usb 1-2: new full speed USB device using uhci_hcd and address 6
[ 218.919140] usb 1-2: new full speed USB device using uhci_hcd and address 7
hi,
that's ok, nice to see someone noticed at all :-)
i had found a workaround some time in the past, but i haven't been using
the usb stick for some time. i just tried it out again, and the bug is
still there.
i'm running feisty by now, so i should probably give you some new
diagnostic output.
...and the lsmod output.
As I said before, I'm now running Ubuntu 7.04 Feisty with kernel 2.6.20
and the problem remains. Should I move the bug to linux-source-2.6.20 or
create a bug report there with a link to this one?
If you need any other information for diagnostics, don't hesitate to
ask.
*
hi,
as promised, here is the output of dmesg on my currently running
system...
** Attachment added: "dmesg.txt"
http://librarian.launchpad.net/7492963/dmesg.txt
--
uhci_hcd generates flood of kernel messages while failing to mount usb stick
https://bugs.launchpad.net/bugs/50757
You received
Hi Johnathon,
removing the ehci_hcd module doesn't do anything (it wasn't loaded at
the time, as shown in the lsmod output). I've tried to load and remove
it again, which doesn't change anything. The sole troublemaker seems to
be the uhci_hcd module.
I remember having read something about the ker
Hi,
I've done everything and bundled it up in the attached tar file. There
is no devices.txt since there are no /dev/sd* devices even when the
stick is plugged in. hald doesn't say anything after the usual startup
mess, i.e. everything in hal.log is from _before_ attaching the stick.
Same with gvm
Public bug reported:
When connecting my usb stick to the computer, it is not automatically
discovered anymore. Even 'lsusb -v' does not show anything beside the
usb hub.
Instead, 'cat /proc/kmsg' produces messages like
[17180190.832000] usb 1-2: new full speed USB device using uhci_hcd and addre
Hi,
with kernel 2.6.20-16-generic, the stick is working when plugged in for
the first time, although only after several scanning attempts:
[ 218.415370] usb 1-2: new full speed USB device using uhci_hcd and address 6
[ 218.919140] usb 1-2: new full speed USB device using uhci_hcd and address 7
Public bug reported:
When connecting my usb stick to the computer, it is not automatically
discovered anymore. Even 'lsusb -v' does not show anything beside the
usb hub.
Instead, 'cat /proc/kmsg' produces messages like
[17180190.832000] usb 1-2: new full speed USB device using uhci_hcd and addre
hi,
that's ok, nice to see someone noticed at all :-)
i had found a workaround some time in the past, but i haven't been using
the usb stick for some time. i just tried it out again, and the bug is
still there.
i'm running feisty by now, so i should probably give you some new
diagnostic output.
...and the lsmod output.
As I said before, I'm now running Ubuntu 7.04 Feisty with kernel 2.6.20
and the problem remains. Should I move the bug to linux-source-2.6.20 or
create a bug report there with a link to this one?
If you need any other information for diagnostics, don't hesitate to
ask.
*
hi,
as promised, here is the output of dmesg on my currently running
system...
** Attachment added: "dmesg.txt"
http://librarian.launchpad.net/7492963/dmesg.txt
--
uhci_hcd generates flood of kernel messages while failing to mount usb stick
https://bugs.launchpad.net/bugs/50757
You received
Hi Johnathon,
removing the ehci_hcd module doesn't do anything (it wasn't loaded at
the time, as shown in the lsmod output). I've tried to load and remove
it again, which doesn't change anything. The sole troublemaker seems to
be the uhci_hcd module.
I remember having read something about the ker
Hi,
I've done everything and bundled it up in the attached tar file. There
is no devices.txt since there are no /dev/sd* devices even when the
stick is plugged in. hald doesn't say anything after the usual startup
mess, i.e. everything in hal.log is from _before_ attaching the stick.
Same with gvm
Hi,
with kernel 2.6.20-16-generic, the stick is working when plugged in for
the first time, although only after several scanning attempts:
[ 218.415370] usb 1-2: new full speed USB device using uhci_hcd and address 6
[ 218.919140] usb 1-2: new full speed USB device using uhci_hcd and address 7
hi,
that's ok, nice to see someone noticed at all :-)
i had found a workaround some time in the past, but i haven't been using
the usb stick for some time. i just tried it out again, and the bug is
still there.
i'm running feisty by now, so i should probably give you some new
diagnostic output.
...and the lsmod output.
As I said before, I'm now running Ubuntu 7.04 Feisty with kernel 2.6.20
and the problem remains. Should I move the bug to linux-source-2.6.20 or
create a bug report there with a link to this one?
If you need any other information for diagnostics, don't hesitate to
ask.
*
hi,
as promised, here is the output of dmesg on my currently running
system...
** Attachment added: "dmesg.txt"
http://librarian.launchpad.net/7492963/dmesg.txt
--
uhci_hcd generates flood of kernel messages while failing to mount usb stick
https://bugs.launchpad.net/bugs/50757
You received
Hi Johnathon,
removing the ehci_hcd module doesn't do anything (it wasn't loaded at
the time, as shown in the lsmod output). I've tried to load and remove
it again, which doesn't change anything. The sole troublemaker seems to
be the uhci_hcd module.
I remember having read something about the ker
Hi,
I've done everything and bundled it up in the attached tar file. There
is no devices.txt since there are no /dev/sd* devices even when the
stick is plugged in. hald doesn't say anything after the usual startup
mess, i.e. everything in hal.log is from _before_ attaching the stick.
Same with gvm
42 matches
Mail list logo
