public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ian Chilton <mailinglist@ichilton.co.uk>
To: Leopold Gouverneur <lgouv@pi.be>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Anyone use HPT366 + UDMA in Linux?
Date: Fri, 15 Nov 2002 16:28:33 +0000	[thread overview]
Message-ID: <20021115162833.GA3717@buzz.ichilton.co.uk> (raw)
In-Reply-To: <20021115162704.GA1059@gouv>

Hello,

> I am using an IBM-DTLA-307030 with HPT366

I am also using an IBM disk (can't rember the model number of hand but
it's a 45GB) with an Abit BP6.


> transfer rate to udma3 (44MB/s) in the HPT bios. You can also do it with
> hdparm if your boot disk is not on that controler. Trying udma4 resulted
> in _massive_ corruption (never tried recently).

It seemed to work for a while but then things went screwy and I kept
getting I/O errors all the time which needed a hard reset - could't even
shut down.

I also noticed things like this in the log:

Nov 14 23:26:40 buzz kernel: hda: status error:
status=0x58 { DriveReady SeekComplete DataRequest }
Nov 14 23:26:40 buzz kernel: hda: drive not ready for command
Nov 14 23:28:47 buzz kernel: hda: status error:
status=0x58 { DriveReady SeekComplete DataRequest }
Nov 14 23:28:47 buzz kernel: hda: drive not ready for command
Nov 14 23:29:00 buzz kernel: APIC error on CPU0: 02(02)

Is this anything like you got?

I'll try to drop it in the bios tonight (it is my boot drive). Are you
using hdparm commands at all or just setting the bios to udma3?


> HPT366 support in kernel configuration.

I am not sure I did this but I'll check. Maybe it's just working as a
normal ide interface or something?


Thanks!


Bye for Now,

Ian


                                \|||/ 
                                (o o)
 /---------------------------ooO-(_)-Ooo---------------------------\
 |  Ian Chilton                  Web: http://www.ichilton.co.uk    |
 |  E-Mail: ian@ichilton.co.uk   Backup: ian@linuxfromscratch.org  | 
 |-----------------------------------------------------------------|
 |            There are 10 types of people in the world:           |
 |        Those who understand binary, and those who don't.        |
 \-----------------------------------------------------------------/


  reply	other threads:[~2002-11-15 16:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-15 12:35 Anyone use HPT366 + UDMA in Linux? Ian Chilton
2002-11-15 14:39 ` Alan Cox
2002-11-15 18:42   ` Ian Chilton
2002-11-15 19:10     ` Samuel Flory
2002-11-15 22:44       ` Ian Chilton
2002-11-15 22:15   ` Miloslaw Smyk
2002-11-15 22:51     ` Ian Chilton
2002-11-15 23:29       ` Miloslaw Smyk
2002-11-16 11:18     ` Zdenek SUTR Kaminski
2002-11-15 16:27 ` Leopold Gouverneur
2002-11-15 16:28   ` Ian Chilton [this message]
     [not found]     ` <20021115173120.GA1152@gouv>
2002-11-15 18:34       ` Ian Chilton
2002-11-15 19:15         ` Samuel Flory
2002-11-16  0:19     ` Kevin Krieser
  -- strict thread matches above, loose matches on Subject: below --
2002-11-15 21:04 Ian Castle

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=20021115162833.GA3717@buzz.ichilton.co.uk \
    --to=mailinglist@ichilton.co.uk \
    --cc=ian@ichilton.co.uk \
    --cc=lgouv@pi.be \
    --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