From: Alan Cox <alan@redhat.com>
To: "David S. Miller" <davem@redhat.com>
Cc: Alan Cox <alan@redhat.com>,
B.Zolnierkiewicz@elka.pw.edu.pl, linux-ide@vger.kernel.org,
bcollins@debian.org
Subject: Re: IDE corruption datapoint
Date: Wed, 16 Jul 2003 09:24:07 -0400 (EDT) [thread overview]
Message-ID: <200307161324.h6GDO7l28802@devserv.devel.redhat.com> (raw)
In-Reply-To: <20030716060845.0e71a6e5.davem@redhat.com> from "David S. Miller" at Gor 16, 2003 06:08:45
> CONFIG_X86_GOOD_APIC is enabled, but there is no IO-APIC in this
> VAIO and /proc/interrupts shows all XT-PIC.
It matters if you have APIC/IO-APIC support enabled. In marcelo's tree
disable_irq is broken in APIC mode for non SMP.
> 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.
They really wouldn't relate to the IDE code at all. IDE or block layer
stuff is by far the most likely.
> 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?
I got mail from two people confirming some "patch" fixed it, but nobody
ever sent me the patch in question. I'd guess its making sure the PIO side
is always set up at boot
next prev parent reply other threads:[~2003-07-16 13:09 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
2003-07-16 13:24 ` Alan Cox [this message]
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=200307161324.h6GDO7l28802@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 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.