LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: Brad Campbell <brad@wasp.net.au>, linux-kernel@vger.kernel.org
Subject: Re: libata 2.6.5->2.6.6 regression -part II
Date: Fri, 21 May 2004 10:35:26 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.3.96.1040521102100.11411A-100000@gatekeeper.tmr.com> (raw)
In-Reply-To: <200405211433.13034.bzolnier@elka.pw.edu.pl>
On Fri, 21 May 2004, Bartlomiej Zolnierkiewicz wrote:
> On Friday 21 of May 2004 14:06, Bill Davidsen wrote:
> > Bartlomiej Zolnierkiewicz wrote:
> > > On Monday 17 of May 2004 18:34, Brad Campbell wrote:
> > >>G'day all,
> > >>I caught the suggestion on my last post in the archives, but because I'm
> > >>not subscribed and wasn't cc'd I can't keep it threaded.
> > >>
> > >>I tried backing out the suggested acpi patch (No difference at all), and
> > >> I managed to get apic to work but it still hangs solid in the same
> > >> place.
> > >>
> > >>dmesg attached.
> > >>
> > >>I managed to figure out that the VIA ATA driver captures my sata drives
> > >> on the via ports, explaining why sata_via misses them, but writing data
> > >> to those drives (hde & hdg) causes dma timeouts and locks the machine.
> > >> No useful debug info produced. The machine becomes non-responsive,
> > >> throws a couple of dma timeouts to the console and then loses all
> > >> interactivity (keyboard, serial, network) forcing a reset push.
> > >>
> > >>Is there any way I can prevent the VIA ATA driver capturing this device?
> > >>Unfortunately my boot drive is on hda on the on-board VIA ATA interface
> > >> so I need it compiled in.
> > >
> > > Disable the fscking PCI IDE generic driver.
> > > [ You are not the first one tricked by it. ]
> > >
> > > AFAIR support for VIA 8237 was added to it before sata_via.c was ready.
> > > [ but my memory is... ]
> >
> > What would happen if the generic driver was initialized last? That would
> > let other more specific drivers grab devices first. The model which
> > comes to mind is a route table, smallest subnet (or in this case most
> > specific) being used first. Or would that open a whole other nest of
> > snakes?
>
> I think that you are confusing PCI IDE generic driver with IDE generic driver
> (the latter is already called after the former).
>
> Brad's problem was IDE driver (pci/generic.c) vs libata driver (sata_via.c).
I was indeed doing just that, but I guess the sense of the question is
still valid, what would the implications of doing the sata_via before the
pci/generic be? Would it address the original problem, and if so what
would break, if anything? You noted this is not the first time the
problem has been seen.
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
next prev parent reply other threads:[~2004-05-21 23:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-17 16:34 Brad Campbell
2004-05-18 13:13 ` Bartlomiej Zolnierkiewicz
2004-05-19 6:51 ` Brad Campbell
2004-05-21 12:06 ` Bill Davidsen
2004-05-21 12:33 ` Bartlomiej Zolnierkiewicz
2004-05-21 14:35 ` Bill Davidsen [this message]
2004-05-21 14:52 ` Bartlomiej Zolnierkiewicz
2004-05-18 19:52 ` Sergey Vlasov
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=Pine.LNX.3.96.1040521102100.11411A-100000@gatekeeper.tmr.com \
--to=davidsen@tmr.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=brad@wasp.net.au \
--cc=linux-kernel@vger.kernel.org \
--subject='Re: libata 2.6.5->2.6.6 regression -part II' \
/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
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).