All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Svetoslav Slavtchev" <svetljo@gmx.de>
To: Andre Hedrick <andre@linux-ide.org>
Cc: linux-kernel@vger.kernel.org, bkz@linux-ide.org
Subject: Re: HighPoint 374
Date: Sun, 19 Oct 2003 22:46:26 +0200 (MEST)	[thread overview]
Message-ID: <7755.1066596386@www23.gmx.net> (raw)
In-Reply-To: Pine.LNX.4.10.10310191329150.15306-100000@master.linux-ide.org

> 
> You do not enable TCQ on highpoint without using the hosted polling timer.
> Oh and I have not added it, and so hit Bartlomiej up for the additions.

good info :-)

but it sometimes seems to enable it

the 4 drives are identical,
and the drive failing is almost always different

and this doesn't explain the md/ lvm corupption,
even when TCQ is not enabled both in 2.4 and 2.5
 
/dev/hda:

ATA device, with non-removable media
powers-up in standby; SET FEATURES subcmd spins-up.
        Model Number:       IC35L080AVVA07-0
        Serial Number:      VNC402A4CVHNEA
        Firmware Revision:  VA4OA52A
Standards:
        Used: ATA/ATAPI-5 T13 1321D revision 1
        Supported: 5 4 3 2 & some of 6
Configuration:
        Logical         max     current
        cylinders       16383   16383
        heads           16      16
        sectors/track   63      63
        --
        CHS current addressable sectors:   16514064
        LBA    user addressable sectors:  160836480
        device size with M = 1024*1024:       78533 MBytes
        device size with M = 1000*1000:       82348 MBytes (82 GB)
Capabilities:
        LBA, IORDY(can be disabled)
        bytes avail on r/w long: 52     Queue depth: 32
        Standby timer values: spec'd by Standard, no device specific minimum
        R/W multiple sector transfer: Max = 16  Current = 0
        Advanced power management level: unknown setting (0x0000)
        Recommended acoustic management value: 128, current value: 254
        DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5
             Cycle time: min=120ns recommended=120ns
        PIO: pio0 pio1 pio2 pio3 pio4
             Cycle time: no flow control=240ns  IORDY flow control=120ns
Commands/features:
        Enabled Supported:
           *    NOP cmd
           *    READ BUFFER cmd
           *    WRITE BUFFER cmd
           *    Host Protected Area feature set
                Release interrupt
           *    Look-ahead
           *    Write cache
           *    Power Management feature set
                Security Mode feature set
           *    SMART feature set
           *    Mandatory FLUSH CACHE command
           *    Device Configuration Overlay feature set
.................................................................
           *    READ/WRITE DMA QUEUED
...................................................................

> > i have the same problems with epox 8k9a3+,
> > and may be even strange ones
> > (like fs coruption when soft raid & / or lvm is used)
> > 
> > and i never had the problems with 8k5a3+,
> > the drives were actually taken from the 8k5a3+
> > when it died (me silly tried to update to XP2700)
> > 
> > really strange, isn't it
> > 
> > both boards should be the same, except
> > 8k5a3+ uses kt333
> > 8k9a3+ uses kt400
> > 
> > only mainboard change -> hell of a lot unresolved problems
> > 
> > 
> > svetljo
> > kernels used 2.4.21-2.4.23-pre3 2.6.0-test3-test7bk8
> > 
> > and a nice log when i try to enable TCQ
> > 
> > all Trace: [<c0235ee3>]  [<c022e834>]  [<c025b0ef>]  [<c026e0ed>] 
> > [<c025c7e2>]  [<c026e080>]  [<c010df03>]  [<c010e233>]  [<c010c7d8>]
> > Badness in as_remove_dispatched_request at
> drivers/block/as-iosched.c:102
> 2
> > Call Trace: [<c0235ee3>]  [<c022e834>]  [<c025b0ef>]  [<c026e0ed>] 
> > [<c025c7e2>]  [<c026e080>]  [<c010df03>]  [<c010e233>]  [<c010c7d8>]
> > Badness in as_remove_dispatched_request at
> drivers/block/as-iosched.c:102
> 2
> > Call Trace: [<c0235ee3>]  [<c022e834>]  [<c025b0ef>]  [<c026e0ed>] 
> > [<c025c7e2>]  [<c026e080>]  [<c010df03>]  [<c010e233>]  [<c010c7d8>]
> > Badness in as_remove_dispatched_request at
> drivers/block/as-iosched.c:102
> 2
> > Call Trace: [<c0235ee3>]  [<c022e834>]  [<c025b0ef>]  [<c026e0ed>] 
> > [<c025c7e2>]  [<c026e080>]  [<c010df03>]  [<c010e233>]  [<c010c7d8>]
> > 
> > 
> > -- 
> > NEU FÜR ALLE - GMX MediaCenter - für Fotos, Musik, Dateien...
> > Fotoalbum, File Sharing, MMS, Multimedia-Gruß, GMX FotoService
> > 
> > Jetzt kostenlos anmelden unter http://www.gmx.net
> > 
> > +++ GMX - die erste Adresse für Mail, Message, More! +++
> > 
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel"
> i
> n
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at  http://www.tux.org/lkml/
> > 
> 

-- 
NEU FÜR ALLE - GMX MediaCenter - für Fotos, Musik, Dateien...
Fotoalbum, File Sharing, MMS, Multimedia-Gruß, GMX FotoService

Jetzt kostenlos anmelden unter http://www.gmx.net

+++ GMX - die erste Adresse für Mail, Message, More! +++


  reply	other threads:[~2003-10-19 20:46 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-19 19:57 HighPoint 374 Svetoslav Slavtchev
2003-10-19 20:30 ` Andre Hedrick
2003-10-19 20:46   ` Svetoslav Slavtchev [this message]
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
  -- 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=7755.1066596386@www23.gmx.net \
    --to=svetljo@gmx.de \
    --cc=andre@linux-ide.org \
    --cc=bkz@linux-ide.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.