From: "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 06:08:45 -0700 [thread overview]
Message-ID: <20030716060845.0e71a6e5.davem@redhat.com> (raw)
In-Reply-To: <200307161247.h6GClmk07996@devserv.devel.redhat.com>
On Wed, 16 Jul 2003 08:47:48 -0400 (EDT)
Alan Cox <alan@redhat.com> wrote:
> > 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 ?
No ACPI, stock compiler from RH8.0 with all updates installed:
gcc (GCC) 3.2 20020903 (Red Hat Linux 8.0 3.2-7)
CONFIG_X86_GOOD_APIC is enabled, but there is no IO-APIC in this
VAIO and /proc/interrupts shows all XT-PIC.
Does not occur with vanilla RH 2.4.20- kernel.
WRT. the VAIO, I originally suspected some of the DMI table changes
that went into 2.4.21, but I reverted that (and nearly all of the
other i386 specific 2.4.21 changes) to no avail.
> 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
I'll do this at next opportunity. It'll take a while since it
requires a whole kernel build in order to trigger the corruption
in the final linked image :(
I'll try using the disk bashing tools from feral.com to see if
that triggers anything easily.
> > 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.
Interesting. I've never seen any evidence from Ben or anyone else who
saw the problem on Sparc say much other than "2.6.0-test1 doesn't have
the problem, 2.4.x does"
Can you show the patch in question? I guess it's in 2.6.0-test1
already?
next prev parent reply other threads:[~2003-07-16 13:03 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
2003-07-16 13:08 ` David S. Miller [this message]
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=20030716060845.0e71a6e5.davem@redhat.com \
--to=davem@redhat.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=alan@redhat.com \
--cc=bcollins@debian.org \
--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 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.