All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Erdfelt <johannes@erdfelt.com>
To: Martin Knoblauch <knobi@knobisoft.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: USB Problems with 2.4.19-pre10-ac2
Date: Thu, 13 Jun 2002 16:52:33 -0400	[thread overview]
Message-ID: <20020613165233.O16859@sventech.com> (raw)
In-Reply-To: <200206131916.16214.knobi@knobisoft.de>

On Thu, Jun 13, 2002, Martin Knoblauch <knobi@knobisoft.de> wrote:
>  on connecting an Olympus 2100UZ camera via USB for use with gphoto2
> I get the following messages from the kernel:
> 
> usb.c: registered new driver usbdevfs
> usb.c: registered new driver hub
> usb-uhci.c: $Revision: 1.275 $ time 18:05:42 Jun 13 2002
> usb-uhci.c: High bandwidth mode enabled
> usb-uhci.c: USB UHCI at I/O 0xd800, IRQ 11
> usb-uhci.c: Detected 2 ports
> usb.c: new USB bus registered, assigned bus number 1
> hub.c: USB hub found
> hub.c: 2 ports detected
> usb-uhci.c: USB UHCI at I/O 0xdc00, IRQ 11
> usb-uhci.c: Detected 2 ports
> usb.c: new USB bus registered, assigned bus number 2
> hub.c: USB hub found
> hub.c: 2 ports detected
> usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
> hub.c: USB new device connect on bus1/2, assigned device number 2
> isapnp: Scanning for PnP cards...
> isapnp: No Plug & Play device found
> usb_control/bulk_msg: timeout
> usb.c: USB device not accepting new address=2 (error=-110)
> hub.c: USB new device connect on bus1/2, assigned device number 3
> usb_control/bulk_msg: timeout
> usb.c: USB device not accepting new address=3 (error=-110)
> 
>  Suspicious are the "usb_control/bulk_msg: timeout" messages and the "not 
> accepting" stuff. Same happens with the uhci.o module. The camera works with 
> the 2.4.18-4GB kernel from SuSE8.0. So I suspect some problems with 
> 2.4.19-pre10-ac2. Unfortunatelly I cannot build 2.4.19-pre10 alone, due to 
> compilation errors.
> 
> Any idea? System in question is based on the VIA KT333 chipset, with an 
> xp2100+ CPU.

Almost definately an IRQ routing problem. Check APIC options in kernel,
try using noapic on kernel command line, etc.

JE


      parent reply	other threads:[~2002-06-13 20:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-13 17:16 USB Problems with 2.4.19-pre10-ac2 Martin Knoblauch
2002-06-13 17:36 ` Greg KH
2002-06-13 18:50   ` Martin Knoblauch
2002-06-13 19:23   ` Martin Knoblauch
2002-06-13 20:52 ` Johannes Erdfelt [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020613165233.O16859@sventech.com \
    --to=johannes@erdfelt.com \
    --cc=knobi@knobisoft.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.