linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Erik Slagter <erik@slagter.name>
To: linux-ide@vger.kernel.org
Subject: Re: SATA150TX4 atat1:command timeout
Date: Mon, 17 Oct 2005 12:08:50 +0200	[thread overview]
Message-ID: <1129543730.5945.17.camel@localhost.localdomain> (raw)
In-Reply-To: <VA.00001a59.01e2cffe@foxhill.co.uk>

[-- Attachment #1: Type: text/plain, Size: 575 bytes --]

On Fri, 2005-10-14 at 17:00 +0100, Ian Oliver wrote:
> In article <1129284030.30961.4.camel@localhost.localdomain>, Erik 
> Slagter wrote:
> > So either the PSU has solved my problem, or the disk cooler cools some
> > critical component on the disk better.
> 
> My machine has two PSUs and the disks are shared between them. I doubt 
> that power is an issue.
> 
> Will try an upgrade to Ubuntu Breezy (5.10) when I'm feeling brave!

Of course you could also try to compile your kernel yourself (like I do
and therefore I am not affected by bugs already solved)

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2115 bytes --]

  reply	other threads:[~2005-10-17 10:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-14 21:41 SATA150TX4 atat1:command timeout Francois Payette
2005-02-14 22:35 ` Jeff Garzik
2005-02-16 15:04   ` Francois Payette
2005-02-18 16:40     ` Francois Payette
2005-09-30 10:40       ` Robin Bowes
2005-10-06  9:55         ` Ian Oliver
2005-10-06 10:44           ` Erik Slagter
2005-10-13 20:37             ` Ian Oliver
2005-10-13 21:04               ` Mark Lord
2005-10-14 10:17                 ` Ian Oliver
2005-10-14 13:07                   ` Mark Lord
2005-10-14 10:00               ` Erik Slagter
2005-10-14 16:00                 ` Ian Oliver
2005-10-17 10:08                   ` Erik Slagter [this message]
2005-10-17 13:01                     ` Ian Oliver

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=1129543730.5945.17.camel@localhost.localdomain \
    --to=erik@slagter.name \
    --cc=linux-ide@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).