All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kirill Kozmin <kozkir-8@student.luth.se>
To: Andre Hedrick <andre@linux-ide.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: VIA686A chipset crash under 2.4.2-ac20
Date: Thu, 22 Mar 2001 00:34:13 +0100	[thread overview]
Message-ID: <3AB93A75.D18A78EE@student.luth.se> (raw)
In-Reply-To: <Pine.LNX.4.10.10103161041040.14210-100000@master.linux-ide.org>

Andre Hedrick wrote:

> Okay not to worry, I now have a my hands on a VIA 686B and will look at
> the changes that happened to the VIA686A
>
> Have you run 2.2.18 plus my patches off kernel.org?
>

Ok, now its clear that I have a big troubles with hardware.
I compiled kernel 2.2.18+IDE_patches with support for VIA chipset and still get
errors of type:

kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }

before these kernel reports a long string of messages

kernel: hda: Write Cache SUCCESSED Flushing!<6>hda: Write Cache....

Probably it's not a question for this list but what should I do and how can
I determinate broken hardware? (Or configuration? I still hope that it's not a
hardware)


//Kirill


  parent reply	other threads:[~2001-03-21 23:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-15 16:22 VIA686A chipset crash under 2.4.2-ac20 kozkir-8
2001-03-16 18:11 ` Andre Hedrick
2001-03-16 18:23   ` Re[2]: " kozkir-8
2001-03-16 18:42     ` Andre Hedrick
2001-03-16 19:03       ` Kirill Kozmin
2001-03-16 19:38         ` Andre Hedrick
2001-03-16 19:50       ` VIA686B + 2.2.18 (was: VIA686A chipset crash under 2.4.2-ac20) William Park
2001-03-20 18:39         ` Andre Hedrick
2001-03-21 23:34       ` Kirill Kozmin [this message]
2001-03-26 22:28         ` VIA686b chipset and dma_intr errors, and 3c905B errors Nicholas Petreley
2001-03-27  4:19           ` Nicholas Petreley

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=3AB93A75.D18A78EE@student.luth.se \
    --to=kozkir-8@student.luth.se \
    --cc=andre@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.