public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: jimbleferret@catholic.org
To: Erik Bourget <erik@midmaine.com>, linux-kernel@vger.kernel.org
Subject: Re: CMD680, kernel 2.4.21, and heartache
Date: Fri, 03 Oct 2003 21:57:51 -0400	[thread overview]
Message-ID: <200310032157.52146.jimbleferret@catholic.org> (raw)
In-Reply-To: <87brsybm41.fsf@loki.odinnet>

On Friday 03 October 2003 07:23 am, Erik Bourget wrote:
> Day 0: 8 new NFS servers go online, they are P4-2.4GHz boxes
> with two each 120GB Samsung drives attached to CMD680/SiI680
> IDE controllers.  They run Debian stable on a 2.4.21 kernel,
> with SMP enabled though they are uniproc boxes, running
> NFSv3-via-TCP and reiserfs.  CMD680/siimage support compiled
> in, obviously.  Software RAID, mirroring drives.
>
> Out of 8 boxes:
>
> *) One has crashed hard.  I'm about to drive to the datacenter
> to plug in a KVM and take a picture.
> *) Three have had DMA turned off and have given extremely
> spooky errors. Read below.

I've been having very similar problems with a box here.  Just put 
Gentoo on it, and started having weird errors almost immediately 
- libraries not being found, all the way to gcc being unable to 
make executables.  Occasionally, I'd get a full lock - network 
was dead from the outside, and locally everything was frozen.  
The logs pointed to the same things - 'hda: status error: 
status=0x58 { DriveReady SeekComplete DataRequest },'  'hda: 
timeout waiting for DMA' and then a 'reset: success,' but it 
didn't seem that way.  Turning off DMA didn't seem to have any 
effect on gcc problems or lockups.

The Maxtor utility said everything was ok, and I had been using 
FreeBSD on it for months with no problems there.  Heat isn't a 
problem.

I then took out SiS5513 support (CONFIG_BLK_DEV_SIS5513), and I 
haven't had any problems since.  DMA is back on, and I've had a 
couple of timeouts and resets, but only 3 or 4 in ~10 hours, and 
no lockups or other noticeable weirdness.

Kernel version is gentoo-sources 2.4.20-r7, but I think that has 
patches from >=2.4.21.  I haven't tried any other sources.

Drive is a Maxtor 8 Gig, 90871U2.

Board is a PCChips M571.


      parent reply	other threads:[~2003-10-04  1:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-03 11:23 CMD680, kernel 2.4.21, and heartache Erik Bourget
2003-10-03 11:59 ` John Bradford
2003-10-03 12:23   ` Erik Bourget
2003-10-03 12:40     ` John Bradford
2003-10-03 12:48     ` Erik Bourget
2003-10-03 13:11       ` John Bradford
2003-10-03 18:10       ` Tomasz Rola
2003-10-03 18:22         ` Erik Bourget
2003-10-03 18:47           ` John Bradford
2003-10-04  1:57 ` jimbleferret [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=200310032157.52146.jimbleferret@catholic.org \
    --to=jimbleferret@catholic.org \
    --cc=erik@midmaine.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