public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kees Bakker <rnews@altium.nl>
To: Luca Barbieri <ldb@ldb.ods.org>
Cc: Greg KH <greg@kroah.com>,
	Linux-Kernel ML <linux-kernel@vger.kernel.org>,
	Linux-USB-Users <linux-usb-users@lists.sourceforge.net>
Subject: Re: USB broken in 2.5.4[56]
Date: 08 Nov 2002 17:06:47 +0100	[thread overview]
Message-ID: <si4rasuju0.fsf@koli.tasking.nl> (raw)
In-Reply-To: <1036701797.2841.17.camel@ldb>

>>>>> "Luca" == Luca Barbieri <ldb@ldb.ods.org> writes:

>> Anyway, which USB drivers are you using?  That might help us narrow this
>> down a bit.

Luca> speedtouch              8932   3
Luca> hid                    39652   0 (unused)
Luca> uhci-hcd               27900   0 (unused)
Luca> usbcore                88372   2 [speedtouch hid uhci-hcd]

Luca> Anyway the problems are obviously either in the USB core or in the uhci
Luca> driver.

For what it's worth. On my system I have problems with 2.5.4[56]. And they
seem to be related to USB. When I boot with nousb it boots OK. But without
this option I get OOPSes and panics everywhere. The system is happy with
2.5.44.

Some of these OOPSes happen during shutdown in device_shutdown. But panics
during boot are happening too. And then all I see on my screen is that the
call-trace in is reap_timer_fnc somewhere.

I've tried switching on USB_DEBUG, but that didn't help much. Neither the
DEBUG=1 in drivers/base/power.c.

My machine has a MSI K7T266 Pro motherboard with Athlon 1.3GHz. It has a
VIA chipset, 82C686b+VT8233. Harddisk: IBM Deskstar 60GXP, 40Gb.

I'm using CONFIG_USB_UHCI_HCD_ALT=y

		Kees

      parent reply	other threads:[~2002-11-08 16:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-06 13:20 USB broken in 2.5.4[56] Luca Barbieri
2002-11-06 18:30 ` Greg KH
2002-11-07 20:43   ` Luca Barbieri
2002-11-08  7:43     ` Greg KH
2002-11-08  7:50       ` Greg KH
2002-11-08 16:06     ` Kees Bakker [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=si4rasuju0.fsf@koli.tasking.nl \
    --to=rnews@altium.nl \
    --cc=greg@kroah.com \
    --cc=kees.bakker@altium.nl \
    --cc=ldb@ldb.ods.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-users@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