From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@RZ.TU-Ilmenau.DE>
To: linux-kernel@vger.kernel.org
Subject: Re: linux 2.4.25, Promise 20269, DMA/IRQ problems ?
Date: Thu, 24 Jun 2004 10:37:06 +0200 [thread overview]
Message-ID: <cbe3ri$kf2$1@sea.gmane.org> (raw)
In-Reply-To: 87brjaxrto.fsf@deirdre.ambre.meuh.eu.org
Yann Droneaud <yann@droneaud.com> wrote:
> SMART and smartmontools were enabled until 21 june, I disabled them
> since there are some warning about SMART and Promise card:
> http://cvs.sourceforge.net/viewcvs.py/smartmontools/sm5/WARNINGS?sortby=date&view=markup
> but it doesn't solve the problem.
>
> The problems seems to occurs now with regularity each morning during
> the cron.daily work (Debian GNU/Linux woody), so it's probably a drive problem,
Well, this looks exactly like my 'signalling/power' issue.
Have a look at my last mail to the 'Strange DMA-errors and
system hang with Promise 20268' thread on the lkm which is
also mentioned on the page you already found.
The role smartmontools plays in this game is the same that
your cronjobs do: they put load on the devices - parallel
load on all of them and thus power consumption increases
and if the power supply works on it's upper border, on-the-
wire signal quality probably decreases.
I pointed this out in a thread 'Logs - ideas what this is
reporting' on the smartmontools-support list too.
Try to exchange power supply, IDE cables and perhaps clean
PCI slots :)
This could be a bit tricky without physical control to the
machine, but you surely will have someone who has :)
Of course, this is just a try - however, I'd bet it helps
in your case.
regards,
Mario
--
I heard, if you play a NT-CD backwards, you get satanic messages...
That's nothing. If you play it forwards, it installs NT.
prev parent reply other threads:[~2004-06-24 8:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-23 14:38 linux 2.4.25, Promise 20269, DMA/IRQ problems ? Yann Droneaud
2004-06-24 8:37 ` Mario 'BitKoenig' Holbe [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='cbe3ri$kf2$1@sea.gmane.org' \
--to=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