mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Tomi Orava" <Tomi.Orava@ncircle.nullnet.fi>
To: "Svetoslav Slavtchev" <svetljo@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: HighPoint 374
Date: Mon, 20 Oct 2003 11:03:42 +0300 (EEST)	[thread overview]
Message-ID: <45855.194.237.142.24.1066637022.squirrel@ncircle.nullnet.fi> (raw)
In-Reply-To: <975.1066636403@www51.gmx.net>



>> Are you capable of trying if the hdparm -m0 trick
>> works for you ?
>
> you mean the fs corruption on soft raid or the interupts problem ?
> i dumped the raid setup as i couldn't find a way to debug it
> and my drives are pretty full again, but i'll try to free some space

I meant the interrupt problem, because if that problem exists
there doesn't seem to be a reasonable way to figure out what
is the reason for the filesystem corruption.

> for the interupts
> with test7-bk8  , acpi=off pci=noacpi &
> hdparm  -m0 -d1 -X69  /dev/hd[a,e,g]
> hdparm  -m16 -d1 -X69  /dev/hd[a,e,g]
> i don't see timeouts
> if i omit -m i do see them sometimes

Ok, so if I understood you correctly, the interrupt problem
persists _only_ if you leave the multiple sector setting on
its default setting ? If you explicitly disable it, or set
it to maximum it works fine ? Does it work with any value ?

> (i see them both with -m and without -m if i try to use TCQ )

I'd really like to see the stable series working properly
before jumping into the 2.6-series test kernels ... Although,
I'm still wondering how come TCQ is known to work with 370-chip
as Jens said, but not with 374-chip ...

Regards,
Tomi Orava

-- 
Tomi.Orava@ncircle.nullnet.fi

  reply	other threads:[~2003-10-20  8:03 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2003-10-21  9:23 Jindrich Makovicka
2003-10-21 16:59 ` Tomi Orava
2003-10-19 19:42 Christian Guggenberger
2003-10-19 19:54 ` Tomi Orava
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
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

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=45855.194.237.142.24.1066637022.squirrel@ncircle.nullnet.fi \
    --to=tomi.orava@ncircle.nullnet.fi \
    --cc=linux-kernel@vger.kernel.org \
    --cc=svetljo@gmx.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

all inboxes | Powered by JetHome®