From: Andi Kleen <ak@suse.de>
To: "Dieter Stüken" <stueken@conterra.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: X86_64 + VIA + 4g problems
Date: Wed, 4 Jan 2006 11:57:35 +0100 [thread overview]
Message-ID: <200601041157.35449.ak@suse.de> (raw)
In-Reply-To: <43BBA2FE.5060006@conterra.de>
On Wednesday 04 January 2006 11:27, Dieter Stüken wrote:
> Andi Kleen wrote:
> > [can you please not always drop me from cc with each reply?]
>
> sorry, I thought the other way around: it would be annoying
> to get each mail twice...
>
> I just found a mailing list "discuss@x86-64.org". Would it be
> better to turn over there, instead of polluting linux.kernel
> by this?
I already cc'ed it with the reply to your first mail, but you and your
colleague with the same problem persistently destroyed
the cc list with each reply so I gave up eventually.
No need to send it there again now.
>
> >> But swiotlb=force works well!
> >
> > This means your PCI bridge doesn't support addresses >4GB.
> >
> >> The pci-gart.c patch seems to disable dma.
> >
> > Only DMA for addresses >4GB.
> >
> > If your torture test involves more than 64MB of IO in flight
> > you might also need to increase the bounce buffer area
> > with swiotlb=128M or somesuch.
>
> I'm about to understand whats going on. So should I use the
> dma patch INSTEAD of "swiotlb=force"? I'll try that tonight.
>
> > When you not compile in the SKGE network driver does everything else work?
>
> I may test it again, but all seemed to work without any patch or
> swiotlb settings when running without the SKGE network driver.
That's likely because the SKGE driver is your only device
that can DMA >4GB. Typical lowend IDE, sound etc. devices have
already 4GB limits and would be forced through bounce buffering
anyways. The patch just forces that for all devices.
Also it's only a hack and would need to be made VIA specific. But
I'm trying to get confirmation of the problem from VIA first
because it's pretty drastic action. It's still possible that
it's only a BIOS bug or somesuch that could be worked around
by setting the right magic bits
We had a similar problem some time ago with a small number
of NF4 boards where it turned out to be a broken BIOS not
programming the bridge correclty.
One contributing factor is likely that the cheap boards are
normally not tested with 4GB RAM, and VIA is normally only found
on cheap boards.
-Andi
next prev parent reply other threads:[~2006-01-04 10:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-02 11:09 X86_64 + VIA + 4g problems Dieter Stüken
2006-01-02 12:26 ` Carsten Otto
2006-01-02 16:22 ` Andi Kleen
2006-01-02 16:52 ` Carsten Otto
2006-01-02 17:46 ` Carsten Otto
2006-01-02 19:01 ` Andi Kleen
2006-01-03 22:54 ` Carsten Otto
2006-01-03 10:04 ` Dieter Stüken
2006-01-03 13:58 ` Andi Kleen
2006-01-03 19:56 ` Dieter Stüken
2006-01-03 21:08 ` Dieter Stüken
2006-01-03 21:26 ` Andi Kleen
2006-01-04 10:27 ` Dieter Stüken
2006-01-04 10:57 ` Andi Kleen [this message]
2006-01-04 10:57 ` Dieter Stüken
[not found] <5qvTv-8f-17@gated-at.bofh.it>
[not found] ` <5qAKf-7n4-19@gated-at.bofh.it>
2006-01-02 19:18 ` Robert Hancock
2006-01-02 19:53 ` Andi Kleen
2006-01-02 20:15 ` Robert Hancock
2006-01-02 20:39 ` Andi Kleen
[not found] ` <5qBcJ-7ZZ-5@gated-at.bofh.it>
[not found] ` <5qDez-2Qf-19@gated-at.bofh.it>
[not found] ` <5r2nz-63n-233@gated-at.bofh.it>
2006-01-04 3:03 ` Robert Hancock
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=200601041157.35449.ak@suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=stueken@conterra.de \
/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