also sprach Alan Stern <[EMAIL PROTECTED]> [2004.10.09.1833 +0200]:
> Do you have the USB debugging option turned on in the kernel
> configuration?
Yes.
--
martin; (greetings from the heart of the sun.)
\ echo mailto: !#^."<*>"|tr "<*> mailto:"; [EMAIL PROTECTED]
invalid/exp
On Sat, 9 Oct 2004, martin f krafft wrote:
> also sprach Alan Stern <[EMAIL PROTECTED]> [2004.10.09.1823 +0200]:
> > It would help to see the dmesg log showing what happens at these times.
>
> Other than the timeout messages... nothing.
Do you have the USB debugging option turned on in the kerne
also sprach Alan Stern <[EMAIL PROTECTED]> [2004.10.09.1823 +0200]:
> It would help to see the dmesg log showing what happens at these times.
Other than the timeout messages... nothing.
--
martin; (greetings from the heart of the sun.)
\ echo mailto: !#^."<*>"|tr "<*> mailto:"
On Sat, 9 Oct 2004, martin f krafft wrote:
> I tried both with 2.6.8.1 with the following results:
>
> - the ep0in timeout messages still appear
> - stopping and starting hotplug does not seem to crash khubd
> anymore
So that patch worked.
> - starting hotplug and most every USB opera
also sprach martin f krafft <[EMAIL PROTECTED]> [2004.10.09.1508 +0200]:
> - the ep0in timeout messages still appear
[...]
> - my USB system seems to be broken. Specifically, I cannot sync
> with my Palm anymore. Curiously, my girlfriends USB media reader
> *does* work, however.
Correc
also sprach Alan Stern <[EMAIL PROTECTED]> [2004.10.08.2000 +0200]:
> The patches I sent were for 2.6.9-rc3. The first one might work
> all right 2.6.8.1 but the second one definitely won't. Below is
> a version of the second patch for 2.6.8.1.
I tried both with 2.6.8.1 with the following result
also sprach Alan Stern <[EMAIL PROTECTED]> [2004.10.08.2000 +0200]:
> No -- I said the fix _isn't_ in 2.6.9-rc3.
Sorry, I misread you.
> The patches I sent were for 2.6.9-rc3. The first one might work all right
> 2.6.8.1 but the second one definitely won't. Below is a version of the
> second p
On Fri, 8 Oct 2004, martin f krafft wrote:
> > Sometimes errors like this and the ones above are just temporary.
> > The device takes a moment to warm up and start working right. You
> > only need to worry about it if the device doesn't work in the end.
>
> I do have another device (a USB servo
also sprach Alan Stern <[EMAIL PROTECTED]> [2004.10.08.1918 +0200]:
> What kind of device is this, can you say? And did it used to work with
> earlier versions of 2.6? If it did, can you pinpoint at which release it
> stopped working?
It's a new device, so I have not used it with anything othe
On Fri, 8 Oct 2004, martin f krafft wrote:
> Okay, let's go after this, I disabled all modules that I could and
> am now going to try to see how I can reproduce the error. USB
> debugging is enabled in the kernel.
>
> To recap, the whole thing is about weird messages about ep0in
> timeouts and th
Okay, let's go after this, I disabled all modules that I could and
am now going to try to see how I can reproduce the error. USB
debugging is enabled in the kernel.
To recap, the whole thing is about weird messages about ep0in
timeouts and the inability to use the affected device. With USB
debuggi
On Tue, 5 Oct 2004, martin f krafft wrote:
> also sprach Alan Stern <[EMAIL PROTECTED]> [2004.10.05.2016 +0200]:
> > See if you can find out exactly what happens during the USB phase when you
> > stop hotplug,
>
> As in, strace?
That's one way. If the programs are simply shell scripts, you can
also sprach Alan Stern <[EMAIL PROTECTED]> [2004.10.05.2016 +0200]:
> See if you can find out exactly what happens during the USB phase when you
> stop hotplug,
As in, strace?
> Also, post the system log for that time period. And make sure you
> have turned on the USB debugging option in the ker
On Tue, 5 Oct 2004, martin f krafft wrote:
> also sprach Alan Stern <[EMAIL PROTECTED]> [2004.10.05.1754 +0200]:
> > The most important thing as far as I'm concerned is to learn what
> > sequence of operations caused the oops you got before.
>
> Okay, I think I can definitely say that the kernel
also sprach Alan Stern <[EMAIL PROTECTED]> [2004.10.05.1754 +0200]:
> The most important thing as far as I'm concerned is to learn what
> sequence of operations caused the oops you got before.
Okay, I think I can definitely say that the kernel oops only happens
when I stop hotplug. Doing so causes
also sprach Alan Stern <[EMAIL PROTECTED]> [2004.10.05.1754 +0200]:
> Which messages exactly are you seeing?
As stated in my original post:
usb 4-6: new high speed USB device using address 5
usb 4-6: control timeout on ep0in
usb 4-6: device not accepting address 5, error -71
However, it seems th
On Tue, 5 Oct 2004, martin f krafft wrote:
> Okay, I rebooted and am seeing these messages again...
Which messages exactly are you seeing?
> So now I want to try what you are proposing, but I cannot seem to
> unload hci_usb:
>
> ERROR: Module hci_usb is in use
I said to unload uhci-hcd, not
also sprach Alan Stern <[EMAIL PROTECTED]> [2004.10.04.2325 +0200]:
> Is this reproducible? What happens if you do "rmmod uhci-hcd"
> yourself by hand, without involving the hotplug programs?
Okay, I rebooted and am seeing these messages again...
So now I want to try what you are proposing, but
also sprach Alan Stern <[EMAIL PROTECTED]> [2004.10.04.2325 +0200]:
> Don't worry, your disassembly gave the answer we needed. For
> whatever reason (I don't have time to go searching for it now), in
> hcd_endpoint_disable the udev->hcpriv value stored in dev is
> a NULL pointer. Of course that's
On Fri, 1 Oct 2004, martin f krafft wrote:
> also sprach Alan Stern <[EMAIL PROTECTED]> [2004.10.01.2113 +0200]:
> > No, you should use usbcore.ko.
>
> Okay, that worked.
>
> Now, the function starts at 0x5320, so +0x74 (from the oops) gives
> 0x5394... so with +/- 5 lines of context:
>
> 0x000
also sprach Alan Stern <[EMAIL PROTECTED]> [2004.10.01.2113 +0200]:
> No, you should use usbcore.ko.
Okay, that worked.
Now, the function starts at 0x5320, so +0x74 (from the oops) gives
0x5394... so with +/- 5 lines of context:
0x537e : movl $0x0,0x44(%edx,%edi,4)
0x5386 : mov$0x
On Fri, 1 Oct 2004, martin f krafft wrote:
> Are we talking about the modules directory, or the kernel source
> tree? I have the former (obviously), but the latter does not exist
> -- this is the Debian stock kernel after all.
I was talking about the kernel source tree. But the modules directory
also sprach Alan Stern <[EMAIL PROTECTED]> [2004.10.01.2026 +0200]:
> One way to do this is to run "gdb hcd.o" from within the
> drivers/usb/core directory, and then do "disass
> hcd_endpoint_disable" at the prompt. The output isn't very
> readable because no external addresses will be given. But
On Fri, 1 Oct 2004, martin f krafft wrote:
> also sprach David Brownell <[EMAIL PROTECTED]> [2004.10.01.1930 +0200]:
> > This suggests UHCI (or the hub driver?) confused usbcore somehow.
> > Can you find out what's at that line? There's some GDB command
> > that'll turn that into a line of C code
also sprach David Brownell <[EMAIL PROTECTED]> [2004.10.01.1930 +0200]:
> This suggests UHCI (or the hub driver?) confused usbcore somehow.
> Can you find out what's at that line? There's some GDB command
> that'll turn that into a line of C code if your kernel is
> appropriately compiled; doesn't
On Thursday 30 September 2004 4:53 am, martin f krafft wrote:
>
> I have a USB device (a built-in 7-in-1 Maxxtro USB 2.0 card reader)
> in this 2.6.8.1 machine of mine, and it's acting up. I am seeing
> messages such as the following every couple of seconds:
>
> usb 4-6: new high speed USB devi
Hi folks,
After having spoken to Greg about this, I am giving it a shot on
this list (at his recommendation).
I have a USB device (a built-in 7-in-1 Maxxtro USB 2.0 card reader)
in this 2.6.8.1 machine of mine, and it's acting up. I am seeing
messages such as the following every couple of seconds
27 matches
Mail list logo
