All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Dibowitz <phil@ipom.com>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: linux-ide@vger.kernel.org
Subject: Re: sata_promise ata exceptions (2.6.20.6)
Date: Mon, 09 Apr 2007 09:01:10 -0700	[thread overview]
Message-ID: <461A6346.8070501@ipom.com> (raw)
In-Reply-To: <200704091018.l39AI9tg020015@harpo.it.uu.se>

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

Mikael Pettersson wrote:
> I've seen reports of issues like these with second-generation
> Promise SATA chips and SATAII (3Gbps) drives, but this is the
> first time I've seen any issues with a first-generation chip.
> 
> 1. Please try 2.6.21-rc6 plus the following two patches:
>    http://user.it.uu.se/~mikpe/linux/patches/2.6/patch-sata_promise-1-separate-sata-pata-ops-2.6.21-rc6
>    http://user.it.uu.se/~mikpe/linux/patches/2.6/patch-sata_promise-2-error_intr-2.6.21-rc6
> 
>    This probably won't eliminate the errors, but should improve
>    the level of detail in the error messages.

I'll do this tonight and send updated logs, thanks.

> 2. Try with a better power supply and verify that cooling is OK.
>    Also verify that the SATA data and power cables are firmly attached.

My power supply is well over-sized for my machine (Antec 480W), so that
shouldn't be a problem. I double checked all my SATA data and power cables.
I also tried switching from SATA-power to PATA-power cables (my drives
support both) to see if that made a difference (it didn't). I've reseated my
cables, switched cable order, etc. to see if I had a bad cable, but no
evidence I do.

>    We've seen several reports of mysterious issues that eventually
>    were traced to insufficient power supplies or poorly seated
>    PCI cards (but in your case the chip is integrated on the mobo).

Understandable. I saw several reports like that on the list, and hence tried
the above.

Thanks for your time, I'll get you updated logs tonight.

-- 
Phil Dibowitz                             phil@ipom.com
Open Source software and tech docs        Insanity Palace of Metallica
http://www.phildev.net/                   http://www.ipom.com/

"Never write it in C if you can do it in 'awk';
 Never do it in 'awk' if 'sed' can handle it;
 Never use 'sed' when 'tr' can do the job;
 Never invoke 'tr' when 'cat' is sufficient;
 Avoid using 'cat' whenever possible" -- Taylor's Laws of Programming



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

  reply	other threads:[~2007-04-09 16:01 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-09 10:18 sata_promise ata exceptions (2.6.20.6) Mikael Pettersson
2007-04-09 16:01 ` Phil Dibowitz [this message]
2007-04-09 20:26 ` Phil Dibowitz
2007-04-10 12:49 ` Tomi Orava
2007-04-13 18:36   ` Tomi Orava
2007-04-16  6:55   ` Phil Dibowitz
2007-04-16  7:02     ` Tomi Orava
2007-04-16  7:47       ` Phil Dibowitz
  -- strict thread matches above, loose matches on Subject: below --
2007-04-16  7:42 Mikael Pettersson
2007-04-14  9:27 Mikael Pettersson
2007-04-14 12:46 ` Tomi Orava
2007-04-13 21:21 Mikael Pettersson
2007-04-14  7:13 ` Tomi Orava
2007-04-19 10:55 ` Tomi Orava
2007-04-09 21:33 Mikael Pettersson
2007-04-09 22:02 ` Phil Dibowitz
2007-04-09 22:42   ` Greg Freemyer
2007-04-07 23:41 Phil Dibowitz
2007-04-08 10:43 ` Ansgar Knappheide
2007-04-09  6:13   ` Phil Dibowitz

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=461A6346.8070501@ipom.com \
    --to=phil@ipom.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=mikpe@it.uu.se \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.