public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Gerard H. Pille" <g.h.p@skynet.be>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, greg@kroah.com
Subject: Re: usb on amd-756 broken since 2.6.6
Date: Sat, 02 Oct 2004 18:08:26 +0100	[thread overview]
Message-ID: <1096736877.25292.2.camel@localhost.localdomain> (raw)
In-Reply-To: <415EA6FC.2080807@skynet.be>

On Sad, 2004-10-02 at 14:02, Gerard H. Pille wrote: 
> The last kernel on which I could succesfully mount /proc/bus/usb and 
> "cat /proc/bus/usb/devices" is 2.6.5, since then, the cat hangs.  I am 
> not sure if the trouble starts with 2.6.6 or 2.6.7, since I can not boot 
> with 2.6.6, the boot hangs on the hdd, a cdrom.  If I could find patches 
>   to get 2.6.6 working, I might be able to further narrow it down.
> 
> In /var/log/messages, I only see this "kernel: usb 1-2: control timeout 
> on ep0in".

This is not AMD specific - the core USB code is broken in the event of
that control timeout occuring. I see the same hang on an Intel ICH6M
platform.

I've done a quick review of the semaphores and didn't see an obvious
cause although I did find a glaring error on a different unused path.
(Oh and although it isn't fixed - that isnt how busses pluralises either
)

--- drivers/usb/core/hcd.c~	2004-10-02 19:01:30.764022672 +0100
+++ drivers/usb/core/hcd.c	2004-10-02 19:01:30.784019632 +0100
@@ -708,6 +708,7 @@
 		bus->busnum = busnum;
 	} else {
 		printk (KERN_ERR "%s: too many buses\n", usbcore_name);
+		up(&usb_bus_list_lock);
 		return -E2BIG;
 	}
 


      reply	other threads:[~2004-10-02 18:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-02 13:02 usb on amd-756 broken since 2.6.6 Gerard H. Pille
2004-10-02 17:08 ` Alan Cox [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=1096736877.25292.2.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=g.h.p@skynet.be \
    --cc=greg@kroah.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox