From: Maximilian Mehnert <mmehnert@gmx.net>
To: linux-kernel@vger.kernel.org
Cc: linux-usb-devel@lists.sourceforge.net
Subject: Re: Kernel 2.6.0-test9, deadlock using usb-storage, eventually memory allocation bug
Date: Mon, 17 Nov 2003 22:35:14 +0100 [thread overview]
Message-ID: <1069104914.3fb93f124ef9e@fvs.dnsalias.net> (raw)
Zitat von Vedran Rodic <vedran@quark.fsb.hr>:
> I think you may be hitting the same problem I did some time ago.
>
> Please see
>
http://www.mail-archive.com/linux-usb-devel%40lists.sourceforge.net/msg17080.html
>
That was very fast! Thanks a lot!
You were absolutely right. My usb disk is working fine now.
Maximilian
--
Maximilian Mehnert <mmehnert at gmx dot net>
http://members.lycos.co.uk/endofuniverse/gpg.html
Fingerprint: 387F 5AA6 5856 2A49 C88C DA86 FBA8 5122 817B C60E
next reply other threads:[~2003-11-17 21:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-17 21:35 Maximilian Mehnert [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-11-17 19:25 Kernel 2.6.0-test9, deadlock using usb-storage, eventually memory allocation bug Maximilian Mehnert
2003-11-17 20:28 ` Vedran Rodic
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=1069104914.3fb93f124ef9e@fvs.dnsalias.net \
--to=mmehnert@gmx.net \
--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