public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Justin T. Gibbs" <gibbs@scsiguy.com>
To: lists@sapience.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: aic7xxx and newer kernels
Date: Tue, 10 Apr 2001 08:00:19 -0600	[thread overview]
Message-ID: <200104101400.f3AE0Js30408@aslan.scsiguy.com> (raw)
In-Reply-To: Your message of "Tue, 10 Apr 2001 08:33:40 EDT." <20010410083340.A16601@sapience.com>

>
>Justin:
>
>Ya think very buggy? I checked seagate web page and 
>unfortunately was unable to find any firmware updates
>for the barracuda drives.

I'm pretty sure you need to be up to at leaset 0005 of 
the firmware to stabilize this drive.

>Curious tho that this has worked flawlessly for well over a 
>year with all prior version of linux and win2000 as well.  
>Also a few other folks seem to have similar problems with 
>newer kernels. 

It all depends on the access pattern.  The drive will only
fail if you fill its write cache.  At that point, it will
fall off the bus, never to return.

>Do the newer drivers put a bigger demand on the drives that 
>might start to uncover the problems previously not seen? 

Depends on your settings.  If you are using the default, we
run a much larger number of concurrent transactions when
compared to the old driver.

>I did find newer firmware for the adaptec 2940u2w card 
>tho so perhaps I should upgrade that?

If you aren't having problems with your BIOS today, there is
no reason to flash the BIOS on teh 2940U2W.

>I will try turning off write cache - kernel config option right?

SCSI-Select option.

--
Justin

  reply	other threads:[~2001-04-10 14:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20010407195031.B25801@sapience.com>
     [not found] ` <200104080139.f381dZs92143@aslan.scsiguy.com>
2001-04-08  4:11   ` aic7xxx 6.1.10 and 2.4.4-pre1 lists
2001-04-08  4:42     ` lists
2001-04-09 21:19     ` Justin T. Gibbs
2001-04-10 12:33       ` aic7xxx and newer kernels lists
2001-04-10 14:00         ` Justin T. Gibbs [this message]
2001-04-10 21:37           ` lists

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=200104101400.f3AE0Js30408@aslan.scsiguy.com \
    --to=gibbs@scsiguy.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@sapience.com \
    /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