public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Peter Wächtler" <pwaechtler@loewe-komp.de>
To: Stephan von Krawczynski <skraw@ithnet.com>
Cc: greg@kroah.com, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.19-pre9, still USB freeze
Date: Wed, 29 May 2002 16:08:32 +0200	[thread overview]
Message-ID: <3CF4E0E0.9090001@loewe-komp.de> (raw)
In-Reply-To: <Pine.LNX.4.21.0205281905260.7798-100000@freak.distro.conectiva>	<20020529145010.21d01e80.skraw@ithnet.com>	<3CF4DDE8.1020305@loewe-komp.de> <20020529155849.357ee2b1.skraw@ithnet.com>

Stephan von Krawczynski wrote:
> On Wed, 29 May 2002 15:55:52 +0200
> Peter Wächtler <pwaechtler@loewe-komp.de> wrote:
> 
> 
>>Stephan von Krawczynski wrote:
>>
>>>Hello,
>>>
>>>as noted for pre8, pre9 freezes still, when connecting a sandisk SDDR-05 to
>>>USB(only device attached), and trying to mount some compact-flash. Or, as
>>>an alternative test, even with no compact flash inserted, when starting up
>>>xcdroast. Both completely freezes the machine.
>>>
>>>pre6 was ok.
>>>
>>>
>>Is that on a SMP machine?
>>
> 
> Yes, this is SMP (Asus CUV4X-D, via chipset), dual PIII.
> 
> 
>>I think usb-storage is not completely SMP safe.
>>I had occasional lockups on SMP - since I connected the readers to UP
>>I had no single lockup. At work I do write a lot of compactflashes.
>>
> 
> Interestingly everything works well with pre6, whereas pre8 and pre9 _always_
> freeze.
> 

I let my SMP box run overnight. WHEN there was a crash when writing CF
(perhaps every 2 weeks or so), THEN I got sometimes BIG problems with
writing even after a reboot - locked up again immediatly.
IIRC my workaround was to remove the modules and load them again
before using them. Yes, sounds weird.
I tried to analyse the problem but gave up. I used usb-uhci on 2.4.9
to 2.4.18-SuSE


  reply	other threads:[~2002-05-29 14:06 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-28 22:06 Linux 2.4.19-pre9 Marcelo Tosatti
2002-05-29  5:37 ` Lars Marowsky-Bree
2002-05-29  6:06   ` Greg KH
2002-05-29 12:50     ` Linux 2.4.19-pre9, still USB freeze Stephan von Krawczynski
2002-05-29 13:55       ` Peter Wächtler
2002-05-29 13:58         ` Stephan von Krawczynski
2002-05-29 14:08           ` Peter Wächtler [this message]
2002-05-29 17:14       ` Greg KH
2002-06-04 18:24       ` Bill Davidsen
2002-05-30  0:34   ` Linux 2.4.19-pre9 Marcelo Tosatti
2002-05-30  1:23     ` David S. Miller
2002-05-30  1:02       ` Marcelo Tosatti
2002-06-04 18:35       ` Bill Davidsen
2002-05-29 12:02 ` lk-changelog.pl (new version 0.21) vs. Linux 2.4.19-pre9 ChangeLog Matthias Andree
2002-05-29 12:10 ` Linux 2.4.19-pre9 ChangeLog Summary Matthias Andree
2002-05-29 23:25 ` Linux 2.4.19-pre9 J.A. Magallon
2002-05-30  9:35   ` Meelis Roos
2002-06-01 18:47 ` /proc/slab garbage Tom Vier
2002-06-01 19:02   ` Benjamin LaHaise

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=3CF4E0E0.9090001@loewe-komp.de \
    --to=pwaechtler@loewe-komp.de \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=skraw@ithnet.com \
    /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