From: Eyal Lebedinsky <eyal@eyal.emu.id.au>
To: Andre Hedrick <andre@linux-ide.org>
Cc: list linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.18: many IDE errors
Date: Mon, 25 Mar 2002 21:26:22 +1100 [thread overview]
Message-ID: <3C9EFB4E.8938BA3A@eyal.emu.id.au> (raw)
In-Reply-To: <Pine.LNX.4.10.10203250143250.6920-100000@master.linux-ide.org>
Andre Hedrick wrote:
>
> On Sun, 24 Mar 2002, Eyal Lebedinsky wrote:
>
> > If I understand correctly, the basic answer is that this is not
> > a driver issue, and not a general kernel (irq's etc.) either, but
> > a true hardware problem.
> >
> >
> > Andre Hedrick wrote:
> > >
> > > It is not a case of bad cables but maybe cable routing.
> >
> > I am not clear on what cable routing means. Can you elaborate?
>
> If you have many cable (note there are random ways to construct, odd/even)
> You can get crosstalk (aka 0x51/0x84 kernel noise). These messages are
> telling you the hardware checksum between the HOST and DEVICE failed.
> The solution is to retry, and the driver does.
[explanation of rate backoff trimmed]
Yes, I see this happening, and I agree it is a good idea.
> > I know they come up ATA-5. Here are the relevant bootup messages:
> >
> > Uniform Multi-Platform E-IDE driver Revision: 6.31
> > ide: Assuming 33MHz system bus speed for PIO modes; override with
> > idebus=xx
> > VP_IDE: IDE controller on PCI bus 00 dev 39
> > VP_IDE: chipset revision 6
> > VP_IDE: not 100% native mode: will probe irqs later
> > ide: Assuming 33MHz system bus speed for PIO modes; override with
> > idebus=xx
> > VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci00:07.1
> > ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio
> > ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:DMA
>
> First disable unmasking VIA it makes a mess. :-/
>
> This (CMD649) is a good HOST and Linux can deal nicely.
You mean IRQ unmasking? This is interesting. After bootup I see hda/c
(on VP_IDE, ide0/1) having
I/O support: 1
unmasking: 1
but hde/g/i/k (on CMD649, ide2/3/4/5) have:
I/O support: 0
unmasking: 0
So VIA unmasking is NOT disabled (I will do so) but why is the CMD649
disabled if you say it is a good chipset?
--
Eyal Lebedinsky (eyal@eyal.emu.id.au) <http://samba.org/eyal/>
next prev parent reply other threads:[~2002-03-25 10:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-24 8:03 Eyal Lebedinsky
2002-03-24 8:21 ` Andre Hedrick
2002-03-24 12:27 ` Eyal Lebedinsky
2002-03-24 22:18 ` Vojtech Pavlik
2002-03-25 10:03 ` Andre Hedrick
2002-03-25 10:26 ` Eyal Lebedinsky [this message]
2002-03-25 10:32 ` Andre Hedrick
2002-03-25 9:58 ` Eyal Lebedinsky
[not found] <Pine.LNX.4.30.0203242314350.31118-100000@mustard.heime.net>
2002-03-24 22:24 ` Eyal Lebedinsky
2002-03-25 9:22 ` Vojtech Pavlik
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=3C9EFB4E.8938BA3A@eyal.emu.id.au \
--to=eyal@eyal.emu.id.au \
--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 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®