From: Albert Max Lai <amlai@bitsorcery.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.x and DAC960 issues
Date: Tue, 16 Apr 2002 22:16:55 +0000 [thread overview]
Message-ID: <15548.41687.486102.179631@bitsorcery.com> (raw)
In-Reply-To: <20020406182101.GA27414@glamis.bard.org.il>
This is the summary of the off-list discussion and solution to my
DAC960 problem.
-Albert
On Saturday, 6 April 2002, Marc A. Volovic wrote:
> Quoth Leonard N. Zubkoff:
>
> > From: Albert Max Lai <amlai@bitsorcery.com>
> >
> > I moved the card into the slot closest to the CPU that I could, and
> > voila! everything works correctly; no lockups, ext3 works, even
> >
> > Excellent news. That's not a fix I've heard of before.
>
> Hi,
>
> Alas, it is very simple. Many (most? in my experience - Tyan, MSI, ASUS)
> motherboards leave their outer (farthest from the CPU area) PCI slots
> ___NON-bus mastering___. In most cases, this is the outermost slot, but
> sometimes it is more than one slot, but again, the outermost, leftmost.
>
> Sometimes, the masterlessness is dynamic - i.e. based on the number of
> populated slots, counting from the CPU. This is EXTREMELY rare. I saw
> it only once, I think, and on a board I did not trust even as far as
> I could toss it. (Well, I could toss it some reasonable distance, which
> I did ;-)...
>
> In some rare cases (errrr... ummmm... SOME Tyan board, I cannot
> currently remember the model) ran in the reverse direction.
>
> Populating these masterless slots with anything but a sound card (and in
> many cases even by a sound card) leads to loss of stability.
>
> Moving a board INWARD (i.e. toward the CPU) in many cases solves the
> problem.
>
> --
> ---MAV
> Linguists Do It Cunningly
> Marc A. Volovic marc@bard.org.il
next parent reply other threads:[~2002-04-16 22:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020406182101.GA27414@glamis.bard.org.il>
2002-04-16 22:16 ` Albert Max Lai [this message]
2002-04-05 5:36 2.4.x and DAC960 issues Albert Max Lai
2002-04-05 18:27 ` Marc A. Volovic
2002-04-05 18:45 ` Albert Max Lai
2002-04-05 20:13 ` Marc A. Volovic
2002-04-05 21:17 ` Marcelo Tosatti
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=15548.41687.486102.179631@bitsorcery.com \
--to=amlai@bitsorcery.com \
--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 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.