public inbox for linux-kernel@vger.kernel.org
 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,
	Sebastian <sebastian@expires0604.datenknoten.de>,
	Bruce Allen <ballen@gravity.phys.uwm.edu>
Subject: Re: Strange DMA-errors and system hang with Promise 20268
Date: Sun, 30 May 2004 12:41:26 +0200	[thread overview]
Message-ID: <1085913685.3431.9.camel@vega> (raw)
In-Reply-To: <20040529144256.GA399@darkside.22.kls.lan>

On Sat, 2004-05-29 at 16:42, Mario 'BitKoenig' Holbe wrote:
> Hi,
> 
> On Sun, Mar 07, 2004 at 02:05:46AM +0100, Mario 'BitKoenig' Holbe wrote:
> > Mar  4 01:01:06 darkside kernel: hde: dma_timer_expiry: dma status == 0x21
> 
> hmmm, it seems I solved the issue in my case.
> 
> I did just connect the two disks on the Promise to a second separate
> power supply and everything works rock-stable and survives all things
> that went wrong before (parallel fsck, parallel hdparm -t as well as
> 'normal operation' over days).
> Things remain stable even with the WDC disk connected back to the
> Promise, which was heavy unstable before.
> 
> Moreover, when I connect the disks back to the machines internal power
> supply, the problems arise again - immediately.
> 
> IMHO, this does also explain, why the problems happen while heavy I/O
> (parallel over all disks) and/or while S.M.A.R.T selftests are running
> (also: parallel over all disks).
> 
> Well, I thought, a 300W power supply would be enough for 1GHz P-III
> and 4 disks. And it definitely was enough for a long time.
> 
> Most likely, the power supply just aged and its capacity decreased.
> 
> Perhaps, the disks consume more power with newer kernels, but while
> crawling the lkm archives I found similar reports also for 2.4.19.
> 
> I have no idea, why always the disks connected to the Promise
> controller did fail. Perhaps, the Promise is more sensitive regarding
> signal quality on the IDE wire.
> 
> I have no idea, why my WDC disk failed when connected to the Promise,
> while others did work far more stable. Perhaps, the WDC disks signal
> quality under low-power is more bad than the one of other disks.
> 
> I have no idea, why the WDC disk did work well when it was connected
> to the onboard controller. Perhaps, the lower signal quality of the
> WDC (if so) and the sensitivity of the Promise (if so) added together
> was too much at all.
> 
> 
> Henrik, Sebastian: if you still have problems, this is probably
> something to test for you.

Well. I don't have those problems anymore but..I have a question..
Should the box freeze just because there is some powerfailures? :/

-- 
Henrik Persson <nix@syndicalist.net>


  parent reply	other threads:[~2004-05-30 10:41 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-06 19:47 Strange DMA-errors and system hang with Promise 20268 Henrik Persson
2004-03-06 19:55 ` Henrik Persson
2004-03-07  1:05 ` Mario 'BitKoenig' Holbe
2004-03-08 13:30   ` Henrik Persson
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 [this message]
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=1085913685.3431.9.camel@vega \
    --to=nix@syndicalist.net \
    --cc=Mario.Holbe@RZ.TU-Ilmenau.DE \
    --cc=ballen@gravity.phys.uwm.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sebastian@expires0604.datenknoten.de \
    /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