From: Simon Burley <simonb@lipsyncpost.co.uk>
To: jeff@AmeriCom.com
Cc: linux-scsi@vger.kernel.org
Subject: Re: SCSI related kernel errors with 2.4
Date: Tue, 25 Feb 2003 11:12:38 +0000 [thread overview]
Message-ID: <3E5B4FA6.86BCA343@lipsyncpost.co.uk> (raw)
In-Reply-To: 20030224204753.13977.qmail@solo.americom.com
jeff@AmeriCom.com wrote:
>
> We've been having crashes we think are related to the scsi driver, I have found other
> people with the same problem by doing google searches. It happens to people burning
> CD's, doing tape backups, and sometimes during normal operation. We never experienced
> this problem with the 2.2 kernel. We tried updating the scsi driver to the latest
> (6.2.28) and the only thing that changed is the error output is a little more
> verbose. The tape drive and the hard drive are both on the same SCSI bus, let me know
> and I can post full hardware specs. It seems when the machine is dead that the hard
> disk is unaccessable, but I can ping the machine and do simple non-disk-accessing
> tasks, its as if the scsi hard disk is offline.
>
> Is anybody aware of this bug? Should I bare with it for a while, or downgrade to 2.2?
<snipped>
Jeffrey,
I went through exactly the same thing about a year ago with a kernel
upgrade on one of my machines. You havn't said which Adaptec you're
using, but this setup was a 2940UW with one internal drive and one
external drive.
I can't explain this, but after ripping the box apart and checking
termination on the internal drive, I found that it wasn't set. Setting
it fixed the problem, as did reverting to a 2.2 kernel.
Hope that helps a little. Sorry if it seems I'm teaching granny to suck
eggs.
Simon
prev parent reply other threads:[~2003-02-25 11:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-24 20:47 SCSI related kernel errors with 2.4 jeff
2003-02-24 23:14 ` jeff
2003-02-25 11:12 ` Simon Burley [this message]
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=3E5B4FA6.86BCA343@lipsyncpost.co.uk \
--to=simonb@lipsyncpost.co.uk \
--cc=jeff@AmeriCom.com \
--cc=linux-scsi@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