Yes, those stack traces were iffy. "khubd" was missing, and I saw
at least one fragmented stack frame. Bigger kernel log buffers might
help (somewhere in kconfig) ... or running without an X11 desktop.
Alan Stern wrote:
The bus_reset() procedure (which involves doing a USB port reset) has
alway
On Fri, 13 Feb 2004, Alan Stern wrote:
> On Thu, 12 Feb 2004, Guennadi Liakhovetski wrote:
>
> > And thanks for rememberring about this problem. Have you got any
> > additional information about the VIA specifics?
>
> A contact at VIA says that this particular error occurs only in USB
> controller
Greg:
This patch removes an unneeded "status" field from the UHCI driver's
URB-private data structure. The driver had been storing the status of
completed URBs there rather than in the URBs themselves. This not only is
wasteful of space but is also a cause of bugs, since the USB core relies
on u
> Are you sure you had installed my patch when you got this oops? One of
> the things my patch does is rename uhci_remove_pending_qhs() to
> uhci_remove_pending_urbps(). Unless you got rid of that part of the
> patch, I don't see how this stack dump could have arisen.
>
> Alan Stern
Did 'ma
Alan Stern wrote:
... only one RD interrupt will be generated while
the controller is suspended. So relying on RD to
> detect that a new device has been plugged in won't
> work for these badly-wired motherboards.
... and properly wired PIIX4 USB controllers that
have a genuine OC condition.
Instea
On 11 Feb 2004, Paul Fulghum wrote:
> On Wed, 2004-02-11 at 10:10, Alan Stern wrote:
> > Is there another device on
> > the system sharing the same IRQ line?
>
> Yes, the USB controller shares with the SCSI controller,
> which explains the repeated IRQ status messages.
>
> There is no way to mov
Deepak Saxena wrote:
Hello. In reply to this message I will be posting updated patches
that cleanup the USB host and core code to use the generic DMA API
instead of the PCI-specific API.
Looks good to me -- thanks! I hope Greg will merge these
(2.6.4-pre, or maybe sooner).
- Dave
Changes from
Kent Ip wrote:
Hello,
I am using a Motorola MxL chip. It has USB module. I
want to port it to linux usb subsystem so my device
can connect to desktop linux e.g. RH9 through USB.
I have read through the Linux USB guild. I would like
to know more specific information about porting USB
hardware modul
On Thu, 12 Feb 2004, Guennadi Liakhovetski wrote:
> Hello, Alan
>
> And thanks for rememberring about this problem. Have you got any
> additional information about the VIA specifics?
A contact at VIA says that this particular error occurs only in USB
controllers with revision number < 5. I thi
On Thu, 12 Feb 2004, Chris Rankin wrote:
> [Linux 2.6.2, dual Xeon (Northwood), Hyperthreaded, 1
> GB RAM, compiled with gcc version 3.2.3 20030422 (Red
> Hat Linux 3.2.3-6)]
>
> Hi,
>
> Somebody lent me a "dodgy" 512 MB SD Card, to see if I
> could read it under Linux. (It was known to fail und
In a message of Tue, 10 Feb 2004 10:20:07 EST, Alan Stern writes:
>> And now I'm off to see what these do. I'd be quite happy if I could get it
>> to work by reloading the usb module.
>
>It ought to be enough simply to reload the module for your host
>controller. You shouldn't need to reload usbc
>From [EMAIL PROTECTED] Mon Feb 9 23:12:23 2004
>> Especially if the sense code is NO SENSE. Logically that should
>> indicate the driver needed to find out whether or not there was error,
>> and it learned that there wasn't.
>For tape drives, sense key == NO SENSE is not equivalent to no erro
Le Jeudi 12 Février 2004 19:50, vous avez écrit :
> Try using "uhci" not "usb-uhci". And if you can, try it on a
> different controller driver than UHCI ... it wasn't quite clear
> from your "lspci" (very old pci.ids file!), but it looks like
> your hardware might have an EHCI controller, which wo
13 matches
Mail list logo
