From: Greg KH <greg@kroah.com>
To: Karim Yaghmour <karim@opersys.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Weird USB errors on HD
Date: Tue, 19 Jul 2005 15:40:24 -0400 [thread overview]
Message-ID: <20050719194024.GA19937@kroah.com> (raw)
In-Reply-To: <42DD5416.6030608@opersys.com>
On Tue, Jul 19, 2005 at 03:27:18PM -0400, Karim Yaghmour wrote:
>
> That being said, shouldn't there be a way for the kernel to refuse to
> use this hd if it's not getting enough power. I don't know enough about
> USB to say, but isn't there something more elegant that could be done in
> software?
Nope, it's a hardware/electrical issue :)
thanks,
greg k-h
next prev parent reply other threads:[~2005-07-19 19:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-19 16:47 Weird USB errors on HD Karim Yaghmour
2005-07-19 19:29 ` Greg KH
2005-07-19 19:27 ` Karim Yaghmour
2005-07-19 19:40 ` Greg KH [this message]
2005-07-19 20:16 ` Lee Revell
2005-07-19 20:29 ` Greg KH
2005-07-20 14:53 ` Alistair John Strachan
2005-07-26 2:16 ` Karim Yaghmour
[not found] <4s3BX-8X-7@gated-at.bofh.it>
[not found] ` <4s66H-2ai-21@gated-at.bofh.it>
[not found] ` <4s66H-2ai-19@gated-at.bofh.it>
2005-07-27 2:34 ` Robert Hancock
2005-07-27 3:31 ` Grant Coady
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=20050719194024.GA19937@kroah.com \
--to=greg@kroah.com \
--cc=karim@opersys.com \
--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