mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David A. Desrosiers" <desrod@gnu-designs.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, linux-usb-devel@lists.sourceforge.net
Subject: Re: USBDEVFS_RESET deadlocks USB bus.
Date: Fri, 4 Jun 2004 16:28:56 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0406041626190.8440@aphrodite.gnu-designs.com> (raw)
In-Reply-To: <20040604200748.GA12855@kroah.com>


> Ah, can you not try the -mm1 kernel?  This problem should not be in the
> mainline kernel.  There was a locking issue in the last bk-usb patch that
> made it into the -mm1 kernel that was fixed yesterday.

	I can confirm that the last kernel this worked with was 2.6.6. We
can't get libusb working at all in 2.4 for the device detection (as you
know). I've now tried everything from 2.6.6 up to 2.6.7-rc2-mm2, including
all "official" (non-akpm) kernels in-between. Same issue.

	What I see in the logs, which may be of use, is:

May 31 21:38:08 wrath kernel: uhci_hcd 0000:00:1d.1: suspend_hc
May 31 21:38:08 wrath kernel: uhci_hcd 0000:00:1d.1: wakeup_hc
May 31 21:38:11 wrath kernel: uhci_hcd 0000:00:1d.1: suspend_hc
May 31 21:38:11 wrath kernel: uhci_hcd 0000:00:1d.1: wakeup_hc
May 31 21:38:13 wrath kernel: uhci_hcd 0000:00:1d.1: suspend_hc
May 31 21:38:13 wrath kernel: uhci_hcd 0000:00:1d.1: wakeup_hc

	..over and over and over, taking the system load gradually up, until
it no longer responds, and has to be rebooted forcibly.

d.


  reply	other threads:[~2004-06-04 20:29 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-04 19:39 Zephaniah E. Hull
2004-06-04 19:52 ` Greg KH
2004-06-04 20:02   ` Zephaniah E. Hull
2004-06-04 20:05     ` Zephaniah E. Hull
2004-06-04 20:07     ` Greg KH
2004-06-04 20:28       ` David A. Desrosiers [this message]
2004-06-04 21:06       ` Zephaniah E. Hull
2004-06-04 20:40     ` [linux-usb-devel] " Duncan Sands
2004-06-04 21:30       ` Zephaniah E. Hull
2004-06-05  7:55         ` Duncan Sands
2004-06-06  6:35           ` Zephaniah E. Hull
2004-06-07  7:05             ` Duncan Sands
2004-06-07 15:43               ` Zephaniah E. Hull
2004-06-07 19:11                 ` Duncan Sands
2004-06-07 23:13                   ` Zephaniah E. Hull
2004-06-08 20:19                     ` Duncan Sands
2004-06-18 20:02                       ` Ian Morgan
2004-06-19 13:48                         ` Duncan Sands
2004-07-02 20:47                       ` Zephaniah E. Hull
2004-07-02 21:11                         ` Alan Stern
2004-07-02 21:52                           ` Zephaniah E. Hull
2004-07-03  8:28                             ` Duncan Sands

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=Pine.LNX.4.58.0406041626190.8440@aphrodite.gnu-designs.com \
    --to=desrod@gnu-designs.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    /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

all inboxes | Powered by JetHome®