public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell Cattelan <cattelan@thebarn.com>
To: Andre Pang <ozone@algorithm.com.au>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: usb-uhci + SMP -> bad
Date: Tue, 14 Aug 2001 11:01:19 -0500	[thread overview]
Message-ID: <3B794B4F.1000303@thebarn.com> (raw)
In-Reply-To: <20010814002131.A26321@bubba.toscano.org> <E15Wdc6-00016N-00@the-village.bc.nu> <997794181.326309.1471.nullmailer@bozar.algorithm.com.au>

Andre Pang wrote:

>On Tue, Aug 14, 2001 at 01:48:06PM +0100, Alan Cox wrote:
>
>>>	- use the uhci USB driver when I'm using a USB printer.  If I
>>>	  use the usb-uhci driver with my USB printer, the whole system
>>>	  locks.  This has been reported a few times on LKML,
>>>	  linux-usb-users, and linux-usb-developers and nobody helped,
>>>	  but a few people wrote back with "me too"s.  It was broken in
>>>	  the trasnition from 2.4.3 to 2.4.4 and only seems to affect
>>>	  SMP systems.  I just gave up on USB printing and went back to
>>>	  my parallel port.
>>>
>>usb-uhci seems to not be SMP safe. Ultimately we don't need both uhci
>>drivers so that hasnt been one that worried me.  Probably we should drop
>>the other uhci driver over time (2.5 maybe)
>>
>
>i'd just thought i'd verify that usb-uchi seems to be causing
>some havoc on SMP boxes.
>
>i've had complete crashes (Alt-SysRq-s doesn't respond) when i
>try to print stuff to a USB printer using the usb-uchi and
>printer modules.  this is on an SMP box.
>
>however -- 2.4.2 works perfectly for that.  it broke from 2.4.4
>onward (tried 2.4.[5-7], i'm presuming .8 hasn't fixed the
>problem.)
>
>if anybody wants me to help them diagnose the problem, i'd be
>more than happy to, but i'm not sure where to start at the
>moment.
>

Note the usb sound driver does that same thing even on a UP box (with 
SMP kernel and UP kernel)

I've tried to debug the problem but setting nmi_watchdog=1 at boot time 
does seem
to catch the problem so I don't have much to go on.

If you haven't set nmi_watchdog yet you may want to try it and see if 
you have
better luck.

And yes comfirmed 2.4.3 works 2.4.[45678] does not.


-Russell Cattelan



  reply	other threads:[~2001-08-14 18:30 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-13  7:43 Are we going too fast? PinkFreud
2001-08-13  8:52 ` Brian
2001-08-13  8:55 ` Francois Romieu
2001-08-13 10:09   ` Chris Wilson
2001-08-13 11:09     ` szonyi calin
2001-08-14  4:21   ` Pete Toscano
2001-08-14 12:48     ` Alan Cox
2001-08-14 13:03       ` usb-uhci + SMP -> bad Andre Pang
2001-08-14 16:01         ` Russell Cattelan [this message]
2001-08-14 22:30       ` Are we going too fast? Paul G. Allen
2001-08-13 10:03 ` Gérard Roudier
2001-08-13 10:29   ` Justin Guyett
2001-08-13 12:56     ` Andrzej Krzysztofowicz
2001-08-13 16:54     ` Gérard Roudier
2001-08-13 13:11 ` Alan Cox
2001-08-14 18:51   ` Anders Larsen
2001-08-14 20:29     ` Anders Larsen
2001-08-13 13:46 ` hugang
2001-08-13 13:55 ` Anton Altaparmakov
2001-08-13 17:16 ` Stephen Satchell
2001-08-13 21:01 ` A warning (was: Re: Are we going too fast?) Nico Schottelius

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=3B794B4F.1000303@thebarn.com \
    --to=cattelan@thebarn.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ozone@algorithm.com.au \
    /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