From: Andi Kleen <ak@suse.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Tejun Heo <htejun@gmail.com>,
Srihari Vijayaraghavan <sriharivijayaraghavan@yahoo.com.au>,
Ingo Molnar <mingo@elte.hu>,
linux-ide@vger.kernel.org
Subject: Re: 2.6.24-rc & SB600 AHCI no go on >=4GB of RAM
Date: Tue, 20 Nov 2007 19:43:14 +0100 [thread overview]
Message-ID: <200711201943.14697.ak@suse.de> (raw)
In-Reply-To: <alpine.LFD.0.9999.0711201905240.25057@localhost.localdomain>
On Tuesday 20 November 2007 19:29:56 Thomas Gleixner wrote:
> On Tue, 20 Nov 2007, Andi Kleen wrote:
>
> >
> > > This requires propably working 64bit DMA, which is not possible with
> > > the SB600 controller.
> >
> > It should not no. The remapping is done into the GART which is <4GB
> > and that is the address the SB600 sees.
>
> Hmm, I just checked the boot logs of the failing 4GB kernel:
>
> BIOS-e820: 0000000100000000 - 0000000120000000 (usable)
> ...
> CPU 0: aperture @ c000000 size 32 MB
> Aperture too small (32 MB)
> No AGP bridge found
> Your BIOS doesn't leave a aperture memory hole
> Please enable the IOMMU option in the BIOS setup
> This costs you 64 MB of RAM
> Mapping aperture over 65536 KB of RAM @ c000000
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
The aperture is mapped at c000000 and c000000 + 64MB < 4GB
> Memory: 4055984k/4718592k available (2146k kernel code, 136780k reserved, 1273k data, 296k init)
>
> 4718592k * 1024 == 0x120000000
>
> So now we have addresses > 4G and I suspect that this is somehow
> related to the problem.
Yes of course -- without >4GB the PCI-GART would not be used at all
(unless you force it) and then no merging.
>
> Also is the aperture size of 32MB somehow related to this ?
This just means the BIOS didn't initialize it properly (a lot of
BIOS don't do anymore these days because they assume it's a AGP
only feature) -- that is why the kernel allocated its own over
memory.
I think we really have to find out which request freezes it.
Can you perhaps just apply this patch and post the output?
Index: linux-2.6.24-rc1-hack/arch/x86/kernel/pci-gart_64.c
===================================================================
--- linux-2.6.24-rc1-hack.orig/arch/x86/kernel/pci-gart_64.c
+++ linux-2.6.24-rc1-hack/arch/x86/kernel/pci-gart_64.c
@@ -385,13 +385,19 @@ static int gart_map_sg(struct device *de
unsigned long pages = 0;
int need = 0, nextneed;
struct scatterlist *s, *ps, *start_sg, *sgmap;
-
+
if (nents == 0)
return 0;
if (!dev)
dev = &fallback_dev;
+ if (*dev->dma_mask <= 0xffffffff) {
+ for_each_sg(sg, s, nents, i) {
+ printk("%d: map %lx len %u dir %d\n", i, sg_phys(s), s->length, dir);
+ }
+ }
+
out = 0;
start = 0;
start_sg = sgmap = sg;
Tejun can probably figure out from that output where it comes
from in libata :)
-Andi
next prev parent reply other threads:[~2007-11-20 18:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-14 11:55 2.6.24-rc & SB600 AHCI no go on >=4GB of RAM Srihari Vijayaraghavan
2007-11-14 12:17 ` Andi Kleen
2007-11-14 16:43 ` Thomas Gleixner
2007-11-14 16:46 ` Andi Kleen
2007-11-19 22:47 ` Srihari Vijayaraghavan
2007-11-20 1:03 ` Tejun Heo
2007-11-20 15:34 ` Thomas Gleixner
2007-11-20 15:44 ` Andi Kleen
2007-11-20 18:29 ` Thomas Gleixner
2007-11-20 18:43 ` Andi Kleen [this message]
2007-11-20 16:36 ` 2.6.24-rc & SB600 AHCI no go on >=4GB of RAM II Andi Kleen
2007-11-20 19:07 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2007-11-08 22:41 2.6.24-rc & SB600 AHCI no go on >=4GB of RAM Srihari Vijayaraghavan
2007-11-09 4:00 ` Tejun Heo
2007-11-12 10:56 ` Srihari Vijayaraghavan
2007-11-13 0:06 ` Srihari Vijayaraghavan
2007-11-13 3:08 ` Tejun Heo
2007-11-13 11:17 ` Srihari Vijayaraghavan
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=200711201943.14697.ak@suse.de \
--to=ak@suse.de \
--cc=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sriharivijayaraghavan@yahoo.com.au \
--cc=tglx@linutronix.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 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.