mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Cress, Andrew R" <andrew.r.cress@intel.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: 2.4.10pre10 aic7xxx problem
Date: Mon, 24 Sep 2001 17:08:54 +0200	[thread overview]
Message-ID: <20010924150854.26490@smtp.adsl.oleane.com> (raw)
In-Reply-To: <9678C2B4D848D41187450090276D1FAE1008EBA5@FMSMSX32>
In-Reply-To: <9678C2B4D848D41187450090276D1FAE1008EBA5@FMSMSX32>

>I've seen some pretty heinous bugs in Big Bear firmware of that vintage.
>I'll bet that the aic debug info will indicate that the disk goes out to
>lunch.  I used to support a large customer who had a large population of
>these disks and we went through a lot of pain debugging these drives with
>Seagate.
>The solution will likely be one or both of these changes:
>  1) Upgrade the disk firmware to 1497 or later 
>         (I have a copy if it's not readily available to you.)
>     The servo should also be 6246 or later.
>  2) Turn off SMART in mode page 1C (88 00).  Also the default number of
>retries for the factory settings are way too high.  The mode page settings
>for ST34520W should look like this:
>pg len ....
>-- --  
>01 0a c4 20 79 00 00 00 20 00 ff ff
>02 0e e0 e0 00 00 00 00 00 00 00 00 00 00 00 00
>03 16 00 00 1f 61 00 00 00 00 00 f6 02 00 00 01 00 24 00 34 40 00 00 00
>04 16 00 23 2e 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1c 20 00 00
>07 0a 0c 20 79 00 00 00 00 00 ff ff
>08 12 90 00 ff ff 00 00 ff ff ff ff 80 01 00 00 00 00 00 00
>0a 0a 00 00 00 00 00 00 ff ff 00 00
>1c 0a 88 00 00 00 00 00 00 00 00 01

Ok, thanks. I don't have the firmwares not I know how to update it on
those disks. I can try hacking the mode pages however.

The "weird" thing is that this same disk works perfectly well on MacOS
with the same HW config, and used to work fine in linux until very
recently.

Justin suggested an interrupt problem. I'll look into it in more detail,
but I don't think there's anything like that. This box (PowerMac G4) has
a quite clean interrupt mapping provided by the firmware with no interrupt
sharing, and things related to parsing that firmware didn't evolve lately
(there have been no significant change to PPC OpenPIC interrupt management
since a long time).

Regards,
Ben.



  reply	other threads:[~2001-09-24 15:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-24 13:38 Cress, Andrew R
2001-09-24 15:08 ` Benjamin Herrenschmidt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-08-17  0:01 2.4.8 aic7xxx -- continuous bus resets Justin T. Gibbs
2001-09-20 15:54 ` 2.4.10pre10 aic7xxx problem Benjamin Herrenschmidt
2001-09-20 17:10   ` Justin T. Gibbs

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=20010924150854.26490@smtp.adsl.oleane.com \
    --to=benh@kernel.crashing.org \
    --cc=andrew.r.cress@intel.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

all inboxes | Powered by JetHome®