From: Jesse Stockall <stockall@magma.ca>
To: linux-kernel@vger.kernel.org
Cc: linux-usb-devel@lists.sourceforge.net
Subject: Re: 2.6.7-mm6 - USB problems
Date: Tue, 06 Jul 2004 10:49:47 -0400 [thread overview]
Message-ID: <1089125387.8352.6.camel@localhost> (raw)
In-Reply-To: <20040705023120.34f7772b.akpm@osdl.org>
On Mon, 2004-07-05 at 05:31, Andrew Morton wrote:
>
> - The USB update seems deadlocky. I fixed one bug but it still causes my
> ia64 test box to lock up on boot. If it goes bad, please revert
> usb-locking-fix.patch and then revert bk-usb.patch. Retest and send a report
> to linux-kernel and linux-usb-devel@lists.sourceforge.net.
On my test system with Via chipset, no ACPI everything (mouse and
storage device) works fine.
On my main system with Via chipset and ACPI, my USB mouse does not work
at all.
Reverting usb-locking-fix.patch and bk-usb.patch makes it work again.
Jesse
--
Jesse Stockall <stockall@magma.ca>
next prev parent reply other threads:[~2004-07-06 14:50 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-05 9:31 2.6.7-mm6 Andrew Morton
2004-07-05 10:18 ` 2.6.7-mm6 Christoph Hellwig
2004-07-05 10:44 ` 2.6.7-mm6 Christoph Hellwig
2004-07-05 10:32 ` 2.6.7-mm6 Redeeman
2004-07-05 13:54 ` 2.6.7-mm6 Frieder Buerzele
2004-07-05 14:41 ` 2.6.7-mm6 Redeeman
2004-07-05 10:39 ` 2.6.7-mm6 Martin Zwickel
2004-07-05 19:04 ` 2.6.7-mm6 Jurgen Kramer
2004-07-05 20:38 ` 2.6.7-mm6 - ppc32 inconsistent kallsyms data Joseph Fannin
2004-07-05 20:54 ` Andrew Morton
2004-07-06 2:06 ` Keith Owens
2004-07-06 7:31 ` Keith Owens
2004-07-06 7:43 ` Keith Owens
2004-07-06 20:54 ` Joseph Fannin
2004-07-06 9:09 ` Rusty Russell
2004-07-06 12:28 ` Keith Owens
2004-07-05 22:52 ` 2.6.7-mm6: ALSA: vortex_asXtalkGainsAllChan multiple definitions Adrian Bunk
2004-07-05 22:56 ` [patch] 2.6.7-mm6: let CDROM_PKTCDVD depend on experimental Adrian Bunk
2004-07-06 6:49 ` USB Lockups with 2.6.7-mm6, was Re: 2.6.7-mm6 Ralf Hildebrandt
2004-07-06 12:54 ` 2.6.7-mm6 William Lee Irwin III
2004-07-06 17:51 ` 2.6.7-mm6 Dmitry Torokhov
2004-07-06 18:55 ` 2.6.7-mm6 Jan-Benedict Glaw
2004-07-06 23:12 ` 2.6.7-mm6 William Lee Irwin III
2004-07-06 23:55 ` 2.6.7-mm6 William Lee Irwin III
2004-07-07 5:15 ` 2.6.7-mm6 Dmitry Torokhov
2004-07-07 6:37 ` 2.6.7-mm6 William Lee Irwin III
2004-07-07 12:47 ` 2.6.7-mm6 Dmitry Torokhov
2004-07-07 12:55 ` 2.6.7-mm6 William Lee Irwin III
2004-07-07 16:31 ` 2.6.7-mm6 Vojtech Pavlik
2004-07-07 17:15 ` 2.6.7-mm6 Dmitry Torokhov
2004-07-07 19:05 ` 2.6.7-mm6 Vojtech Pavlik
2004-07-06 22:34 ` 2.6.7-mm6 Andrew Morton
2004-07-06 22:45 ` 2.6.7-mm6 David S. Miller
2004-07-06 22:52 ` 2.6.7-mm6 William Lee Irwin III
2004-07-06 23:07 ` 2.6.7-mm6 Russell King
2004-07-06 23:36 ` 2.6.7-mm6 William Lee Irwin III
2004-07-07 0:02 ` 2.6.7-mm6 David S. Miller
2004-07-07 2:29 ` 2.6.7-mm6 Nick Piggin
2004-07-07 7:35 ` 2.6.7-mm6 Ingo Molnar
2004-07-07 21:02 ` 2.6.7-mm6 David S. Miller
2004-07-09 2:45 ` 2.6.7-mm6 Nick Piggin
2004-07-09 2:51 ` 2.6.7-mm6 William Lee Irwin III
2004-07-09 5:09 ` 2.6.7-mm6 Nick Piggin
2004-07-09 6:29 ` 2.6.7-mm6 Ingo Molnar
2004-07-09 6:58 ` 2.6.7-mm6 William Lee Irwin III
2004-07-09 7:07 ` 2.6.7-mm6 Nick Piggin
2004-07-09 7:16 ` 2.6.7-mm6 William Lee Irwin III
2004-07-06 14:49 ` Jesse Stockall [this message]
2004-07-07 16:44 ` 2.6.7-mm6 Jesse Barnes
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=1089125387.8352.6.camel@localhost \
--to=stockall@magma.ca \
--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