From: Alan Cox <alan@redhat.com>
To: "David S. Miller" <davem@redhat.com>
Cc: B.Zolnierkiewicz@elka.pw.edu.pl, alan@redhat.com,
linux-ide@vger.kernel.org, bcollins@debian.org
Subject: Re: IDE corruption datapoint
Date: Wed, 16 Jul 2003 08:47:48 -0400 (EDT) [thread overview]
Message-ID: <200307161247.h6GClmk07996@devserv.devel.redhat.com> (raw)
In-Reply-To: <20030716042020.780126b9.davem@redhat.com> from "David S. Miller" at Gor 16, 2003 04:20:20
> FWIW, just like my alim5x3 based Sparcs, I have to boot with ide=nodma
> on my VAIO laptop which uses PIIX chipsets, otherwise I get data
> corruptions.
Ok thats I think a first ever and only report for the VAIO. Are you using
ACPI and what compiler are you using ? Do you have APIC support enabled ?
Does it occur with a vanilla Red Hat 2.4.20- kernel ?
> On the VAIO it shows up as corrupted kernel builds. The build
> is successful but the images won't boot properly, rebuilding
> the same kernel tree with ide=nodma results in a working image.
> This shows up with both 2.4.21 and 2.4.22-current.
If you cp lots of data around then compare what is the error pattern,
thats basically essential info to debug this as is the drive data,
mode selected and so on
> This suggests, at least to me, that it's something generic in
> the IDE layer of 2.4.x vanilla vs. 2.6.0-test1 that's causing
> the problems, rather than a chipset specific issue.
That would be unlikely since someone found the ali problem with
sparc/alpha but just never bothered to send a patch to fix it.
Alan
next prev parent reply other threads:[~2003-07-16 12:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-16 11:20 IDE corruption datapoint David S. Miller
2003-07-16 12:47 ` Alan Cox [this message]
2003-07-16 13:08 ` David S. Miller
2003-07-16 13:24 ` Alan Cox
2003-07-16 13:27 ` David S. Miller
2003-07-16 13:38 ` Alan Cox
2003-07-16 13:36 ` David S. Miller
2003-07-16 14:28 ` Ben Collins
2003-07-16 14:34 ` Alan Cox
2003-07-16 14:34 ` David S. Miller
[not found] ` <20030716233646.4d69c52d.davem@redhat.com>
2003-07-17 16:38 ` Ben Collins
2003-07-17 21:46 ` David S. Miller
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=200307161247.h6GClmk07996@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=bcollins@debian.org \
--cc=davem@redhat.com \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).