From: "Carlos Fernandez Sanz" <cfs-lk@nisupu.com>
To: "Tomi Orava" <Tomi.Orava@ncircle.nullnet.fi>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: HighPoint 374
Date: Sun, 19 Oct 2003 18:48:22 +0200 [thread overview]
Message-ID: <006501c39660$cf306cf0$0514a8c0@HUSH> (raw)
In-Reply-To: <48236.192.168.9.10.1066565636.squirrel@ncircle.nullnet.fi>
> I have tested the kernel hpt374 drivers with all possible kernel
> configurations with and without ACPI/APM, local apic, io-apic and
> they don't seem to change anything in my case. I just get the following
> error message sooner or later and the whole system hangs.
>
> Sep 26 23:07:42 alderan kernel: blk: queue c0466908, I/O limit 4095Mb
> (mask 0xffffffff)
> Sep 26 23:07:42 alderan kernel: hde: dma_timer_expiry: dma status == 0x20
> Sep 26 23:07:42 alderan kernel: hde: timeout waiting for DMA
> Sep 26 23:07:42 alderan kernel: hde: timeout waiting for DMA
This is the EXACT same things I see in my logs.
>
> It might be that my problems are somehow related to the motherboards
> I've been using, as the first one is "Epox 8K9A3+ (Via KT400 chipset)"
> while the another one is "Epox 4PCA3+ (Intel 875p chipset)". But they
> are 100% reproduceble with multiple brands of disk-drives.
Mine is an Asus CUSL2, Pentium III motherboard with 512 Mb.
next prev parent reply other threads:[~2003-10-19 16:45 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-18 9:44 Carlos Fernandez Sanz
2003-10-18 10:15 ` Måns Rullgård
2003-10-19 12:13 ` Tomi Orava
2003-10-19 16:48 ` Carlos Fernandez Sanz [this message]
2003-10-19 17:16 ` Tomi Orava
2003-10-19 17:39 ` Carlos Fernandez Sanz
2003-10-19 19:27 ` Tomi Orava
2003-10-19 19:35 ` Carlos Fernandez Sanz
2003-10-19 15:59 ` Joel Smith
2003-10-19 17:24 ` Tomi Orava
2003-10-19 17:42 ` Måns Rullgård
2003-10-19 19:14 ` Tomi Orava
2003-10-19 19:27 ` Carlos Fernandez Sanz
2003-10-19 19:39 ` Tomi Orava
2003-10-19 20:12 ` Carlos Fernandez Sanz
2003-10-19 19:39 ` Måns Rullgård
2003-10-19 19:54 ` David B. Stevens
2003-10-20 8:38 ` Geller Sandor
2003-10-19 21:12 ` Joel Smith
2003-10-19 17:28 ` Carlos Fernandez Sanz
2003-10-19 21:35 ` Joel Smith
2003-10-19 19:42 Christian Guggenberger
2003-10-19 19:54 ` Tomi Orava
2003-10-19 19:57 Svetoslav Slavtchev
2003-10-19 20:30 ` Andre Hedrick
2003-10-19 20:46 ` Svetoslav Slavtchev
2003-10-19 20:51 ` Bartlomiej Zolnierkiewicz
2003-10-19 20:54 ` Svetoslav Slavtchev
2003-10-20 6:48 ` Jens Axboe
2003-10-20 7:43 ` Tomi Orava
2003-10-20 8:10 ` Svetoslav Slavtchev
2003-10-20 8:21 ` Nick Piggin
2003-10-20 8:30 ` Svetoslav Slavtchev
2003-10-19 21:51 ` Tomi Orava
2003-10-19 22:00 ` Svetoslav Slavtchev
2003-10-19 22:11 ` Svetoslav Slavtchev
2003-10-19 22:24 ` Tomi Orava
2003-10-20 7:53 ` Svetoslav Slavtchev
2003-10-20 8:03 ` Tomi Orava
2003-10-20 9:03 ` Svetoslav Slavtchev
2003-10-20 17:02 ` Carlos Fernandez Sanz
2003-10-20 19:14 ` Svetoslav Slavtchev
2003-10-20 20:23 ` Carlos Fernandez Sanz
2003-10-20 21:07 ` Svetoslav Slavtchev
2003-10-20 21:25 ` Bartlomiej Zolnierkiewicz
2003-10-20 21:25 ` Svetoslav Slavtchev
2003-10-21 18:43 ` Tomi Orava
2003-10-21 18:50 ` Tomi Orava
2003-10-21 9:23 Jindrich Makovicka
2003-10-21 16:59 ` Tomi Orava
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='006501c39660$cf306cf0$0514a8c0@HUSH' \
--to=cfs-lk@nisupu.com \
--cc=Tomi.Orava@ncircle.nullnet.fi \
--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
Powered by JetHome