From: Stefan Kaltenbrunner <mm-mailinglist@madness.at>
To: linux-kernel@vger.kernel.org
Subject: Serverworks CSB5 IDE-DMA Problem (2.4 and 2.6)
Date: Tue, 07 Oct 2003 18:21:06 +0200 [thread overview]
Message-ID: <3F82E7F2.5060804@madness.at> (raw)
Hello!
we have a bunch of IBM x305 here which are entrylevel 1HE servers based
on a Serverworks CSB5 chipset.
One of those has 2 120GB IDE disks in a software RAID1 and the main
userspace-application is a heavly (mostly insert/update) used
postgresql-database. The database generates a lot of sustained
IO-traffic and after some minutes (depends on the load - sometimes it
even works for one or two hours) the kernel generates the following
messages(2.4.22 and 2.6.0-test6 behave almost identically -
error-messages are from 2.6.0-test6):
hdc: dma_timer_expiry: dma status == 0x20
hdc: DMA timeout retry
hdc: timeout waiting for DMA
hdc: status timeout: status=0xd0 { Busy }
hdc: drive not ready for command
ide1: reset: success
hdc: dma_timer_expiry: dma status == 0x20
hdc: DMA timeout retry
hdc: timeout waiting for DMA
hdc: status timeout: status=0xd0 { Busy }
hdc: drive not ready for command
ide1: reset: success
hdc: dma_timer_expiry: dma status == 0x20
hdc: DMA timeout retry
hdc: timeout waiting for DMA
hdc: status timeout: status=0xd0 { Busy }
hdc: drive not ready for command
ide1: reset: success
hdc: dma_timer_expiry: dma status == 0x20
hdc: DMA timeout retry
hdc: timeout waiting for DMA
hdc: status timeout: status=0xd0 { Busy }
hdc: drive not ready for command
ide1: reset: success
hda: dma_timer_expiry: dma status == 0x60
hda: DMA timeout retry
hda: timeout waiting for DMA
hda: status timeout: status=0xd0 { Busy }
hdb: DMA disabled
hda: drive not ready for command
ide0: reset: success
blk: queue dfdee200, I/O limit 4095Mb (mask 0xffffffff)
hda: dma_timer_expiry: dma status == 0x20
hda: DMA timeout retry
hda: timeout waiting for DMA
hda: status timeout: status=0xd0 { Busy }
hda: drive not ready for command
ide0: reset: success
hda: dma_timer_expiry: dma status == 0x20
hda: DMA timeout retry
hda: timeout waiting for DMA
hda: status timeout: status=0xd0 { Busy }
hda: drive not ready for command
ide0: reset: success
after one of this events DMA on one of the disks (either hdc or hda)
gets disabled and the maschine is heavily overloaded and the database
cannot keep up any more with the incoming load of database-updates.
It's also worth mentioning that the kernel reports a "DMA disabled" only
for hdb which is the internal cd-drive and completely unused.
I do know that Serverworks IDE has been flaky (especially with the CSB4)
in the past but I thought this had been fixed in newer chipset-revisions
- is there anything I can do to solve this problem?
dmesg of the machine in question can be found at
http://www.kaltenbrunner.cc/files/dmesg.txt
many thanks
Stefan Kaltenbrunner
next reply other threads:[~2003-10-07 16:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-07 16:21 Stefan Kaltenbrunner [this message]
2003-10-09 19:22 ` Serverworks CSB5 IDE-DMA Problem (2.4 and 2.6) Bartlomiej Zolnierkiewicz
2003-10-09 19:35 ` Marcelo Tosatti
2003-10-09 19:46 ` Bartlomiej Zolnierkiewicz
2003-10-09 20:58 ` Stefan Kaltenbrunner
2003-10-09 21:13 ` Bartlomiej Zolnierkiewicz
2003-10-09 21:22 ` Stefan Kaltenbrunner
2003-10-09 21:29 ` Bartlomiej Zolnierkiewicz
2003-10-10 8:57 ` Stefan Kaltenbrunner
2003-10-10 9:27 ` Bartlomiej Zolnierkiewicz
2003-10-13 7:43 ` Stefan Kaltenbrunner
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=3F82E7F2.5060804@madness.at \
--to=mm-mailinglist@madness.at \
--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