From: Nic Ferrier <nferrier@tapsellferrier.co.uk>
To: "Salyzyn, Mark" <mark_salyzyn@adaptec.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: aacraid died on kernel 2.4.27
Date: Fri, 11 Mar 2005 20:31:36 +0000 [thread overview]
Message-ID: <87br9plyaf.fsf@tapsellferrier.co.uk> (raw)
In-Reply-To: <60807403EABEB443939A5A7AA8A7458BE5A9C9@otce2k01.adaptec.com> (Mark Salyzyn's message of "Fri, 11 Mar 2005 11:06:47 -0500")
"Salyzyn, Mark" <mark_salyzyn@adaptec.com> writes:
> This is a processor based RAID card, so stability and complexity is
> virtually all rooted in the card. The problems you are experiencing are
> most probably specific to your platform, and do not show up in other
> adapters and systems that communicate with this same driver. Although
> the driver can be used to mitigate some problems in the adapter
> Firmware, it can not solve Power Supply, Hardware, Internal Firmware
> Failures, Drive or Cabling issues. All these issues need to be resolved
> first by communicating with Dell Technical Support.
>
> Sadly, all these issues can end up locking up the card or the scsi bus.
> The end result being the scsi system timing out, taking the devices
> offline, then the file-system driver panicking. Similar symptoms, wide
> variety of causes.
The machine I am having trouble with has been running MS Windows for 2
years.
I just put linux on it (with no other changes) and we get regular
(twice daily) catastrophic crashes.
Can this be a controller problem? I'm not a hardware expert but it
doesn't sound like one to me.
Nic
next prev parent reply other threads:[~2005-03-11 20:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 16:06 aacraid died on kernel 2.4.27 Salyzyn, Mark
2005-03-11 20:31 ` Nic Ferrier [this message]
2005-03-11 21:34 ` Andrew Kinney
-- strict thread matches above, loose matches on Subject: below --
2005-03-11 20:54 Salyzyn, Mark
2005-03-10 21:01 Nic Ferrier
2005-03-11 6:04 ` Ryan Anderson
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=87br9plyaf.fsf@tapsellferrier.co.uk \
--to=nferrier@tapsellferrier.co.uk \
--cc=linux-scsi@vger.kernel.org \
--cc=mark_salyzyn@adaptec.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