mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Henrik Persson <nix@syndicalist.net>
To: "Mario 'BitKoenig' Holbe" <Mario.Holbe@RZ.TU-Ilmenau.DE>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Strange DMA-errors and system hang with Promise 20268
Date: Mon, 08 Mar 2004 14:30:43 +0100	[thread overview]
Message-ID: <1078752642.1239.14.camel@vega> (raw)
In-Reply-To: <c2dsha$psd$1@sea.gmane.org>

On Sun, 2004-03-07 at 02:05, Mario 'BitKoenig' Holbe wrote:
> Same here:
> 
> Mar  4 01:01:06 darkside kernel: hde: dma_timer_expiry: dma status == 0x21
> Mar  5 01:02:00 darkside kernel: hde: dma_timer_expiry: dma status == 0x21
> Mar  6 01:10:22 darkside kernel: hde: dma_timer_expiry: dma status == 0x21
> 
> Can you somehow correlate this to start of S.M.A.R.T selftests?

Nope. To this date I wasn't running anything of the sort. I ran a few
selftest now though.. Nothing happened..

> I suspect it having something to do with 2.4.25 new "One last
> read after the timeout" in ide-iops.c and accessing the drive
> while selftest running (possibly especially short selftest).
> Here, daily at 01:00 smartmontools runs smart short selftests
> and a bit later the machine hangs.
> Today, I disabled that job and the machine stays stable.

This happens every now and then.. Sometimes once a week or once a month.
Sometimes it's once per hour. I can't correlate this behaviour with any
activity that the box in question is doing (mysql, nfsd)..

> > error another device, but it's allways a device on the promise
> > controller, fails.
> 
> Dito... PDC20269 U133TX2
> CONFIG_BLK_DEV_PDC202XX_NEW=y
> 
> And until now it was always hde connected to the promise
> controller.
> 
> > I've seen this behaviour with 2.4.25, 2.4.24 and 2.4.23 (I think).
> 
> My machine did run at least since:
> Jan 18 09:41:21 darkside kernel: Linux version 2.4.24
> ...
> Feb 28 01:43:48 darkside kernel: Linux version 2.4.24
> Feb 28 04:58:47 darkside kernel: Linux version 2.4.25
> 
> First time the problem occured was Mar  4 01:01:06.

I've had those problems for at least a month. ;/

I just have no clue what's wrong with the damn thing.

-- 
Henrik Persson <nix@syndicalist.net>


  reply	other threads:[~2004-03-08 13:30 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-06 19:47 Henrik Persson
2004-03-06 19:55 ` Henrik Persson
2004-03-07  1:05 ` Mario 'BitKoenig' Holbe
2004-03-08 13:30   ` Henrik Persson [this message]
2004-03-10 11:50     ` Bruce Allen
2004-03-10 12:36       ` Mario 'BitKoenig' Holbe
2004-03-10 15:00         ` Henrik Persson
2004-03-11  9:36           ` Bruce Allen
2004-03-11 14:31             ` Henrik Persson
2004-03-10 15:41       ` Mario 'BitKoenig' Holbe
2004-03-11  9:25         ` Bruce Allen
2004-05-19 17:20   ` Sebastian
2004-05-19 17:28     ` Mario 'BitKoenig' Holbe
2004-05-19 18:12       ` Sebastian
     [not found]         ` <1648.128.150.143.219.1084992082.squirrel@webmail.seven4sky.com>
2004-05-19 20:12           ` Strange DMA-errors... (was: ...and system hang with Promise 20268) Sebastian
2004-05-19 23:47             ` Mario 'BitKoenig' Holbe
2004-05-20  9:23         ` Strange DMA-errors and system hang with Promise 20268 Bruce Allen
2004-05-20 10:35           ` Strange DMA-errors and system hang with SMART (was: ...and system hang with Promise 20268) Sebastian
2004-05-23 12:46             ` Bruce Allen
2004-06-02 19:00               ` Sebastian
2004-06-03 15:06                 ` Bruce Allen
2004-05-29 14:42   ` Strange DMA-errors and system hang with Promise 20268 Mario 'BitKoenig' Holbe
2004-05-29 22:51     ` Gene Heskett
2004-05-30 10:41     ` Henrik Persson
2004-06-04 20:09     ` Bruce Allen
     [not found] ` <200405052339.i45NdXsx003369@darkside.22.kls.lan>
     [not found]   ` <1083849053.6994.10.camel@vega>
2004-05-06 14:22     ` Mario 'BitKoenig' Holbe

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=1078752642.1239.14.camel@vega \
    --to=nix@syndicalist.net \
    --cc=Mario.Holbe@RZ.TU-Ilmenau.DE \
    --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®