linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tommi Kyntola <kynde@ts.ray.fi>
To: David Brownell <david-b@pacbell.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: USB Mass Storage Hangs
Date: Mon, 30 Sep 2002 13:07:19 +0300 (EEST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0209301239330.8153-100000@behemoth.ts.ray.fi> (raw)
In-Reply-To: <3D95DB7B.1040401@pacbell.net>


>  > > And are both of these devices USB 2.0 devices?  If so, you might want to
>  > > try the 2.4.20-pre kernels, it has much better USB 2.0 support than the
>  > > kernel you are using.
>  >
>  > I can still panic even the 2.4.20-pre8, by ...
> 
> Actually, even pre8 doesn't have the updates that would matter
> for something like this ... the "better" was mostly not oopsing
> if you unplug a hub (it was a hub driver bug).  You'd need some
> patches that aren't yet in Marcelo's tree, but which HAVE been
> pasted here on LKML.  (And people who've tried them have said
> the patches have improved things for them.)
> 
> Have a look at these posts, which are slightly updated versions of
> what's been posted to LKML (patches in the second two):
> 
>     http://marc.theaimsgroup.com/?l=linux-usb-devel&m=103288096812331&w=2
>     http://marc.theaimsgroup.com/?l=linux-usb-devel&m=103288089912220&w=2
>     http://marc.theaimsgroup.com/?l=linux-usb-devel&m=103283868910428&w=2
> 
> Alternatively, try this out on 2.5.latest ... those patches give
> 2.4.20-pre7 (or pre8) the same EHCI code as seen in 2.5.39, but
> if you try 2.5.39 you'll benefit from some usb-storage fixes too.

Actually I did see those posts, it's just that I've had the exact same 
problem on uhci and ohci, and because rmmod usb-storage between
unplug and plugin avoided the problem, I figured it was solely usb-storage 
related.

Besides it appears that it's more likely to be just MSystems DiskOnKey 
related, because for example a similar Fujitsu mass storage works without 
problems.
 
> And of course, if you "rmmod ehci-hcd" you'd be running using the
> companion controller (likely a NEC using "usb-ohci"), which might
> help you figure out whether the EHCI driver is even a factor in
> this case.
>
>  > Reason why I havent been moaning about this since last fall, when I first
>  > discovered this and reported, is ...
> 
> Last fall, the EHCI driver was only available to bleeding-edge hackers
> who were willing to work from CVS.  To whom did you report this?  I
> can confirm that any problem report from last fall wasn't made to the
> right people ... I surely didn't see any such report!  :)

Not about ehci, I did mail here (twice) and to sf usb-devel 
(or usb-users-devel or similar) list, but I was only talking about 
usb-storage module and DiskOnKey because, like I said, it didn't matter 
which Xhci I used, nor on what chipsets I tried it on. Late this summer I 
talked to a person who either worked for msystems (DiskOnKey manufacturer) 
or did business with them, can't remember which, and who had dug up those 
posts, and he sent mails to Matthew Dharm without reply, as far as I know. 

I know that contacting the right people is difficult, and like I said in
my previous post was that I would've looked into this and really tried 
harder, but it's just that I didn't have the time nor the need to
as aliases with the 'rmmod usb-storage' hack avoided the problem with
DiskOnKey devices.

Let me know if you want the panic prints or other tests done. 
I'll try the 2.5.39 out, but I doubt that the results will be any 
different.

-- 
Tommi Kynde Kyntola		kynde@ts.ray.fi
      "A man alone in the forest talking to himself and
       no women around to hear him. Is he still wrong?"


  reply	other threads:[~2002-09-30 10:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-28 16:40 USB Mass Storage Hangs David Brownell
2002-09-30 10:07 ` Tommi Kyntola [this message]
2002-10-01  3:04   ` David Brownell
2002-10-02 14:26     ` Oliver Neukum
  -- strict thread matches above, loose matches on Subject: below --
2002-09-27  5:38 Stephen Marz
2002-09-27  5:51 ` Greg KH
2002-09-28 14:11   ` Tommi Kyntola

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.44.0209301239330.8153-100000@behemoth.ts.ray.fi \
    --to=kynde@ts.ray.fi \
    --cc=david-b@pacbell.net \
    --cc=linux-kernel@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).