From: Robert Hancock <hancockr@shaw.ca>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Yinghai Lu <yhlu.kernel@gmail.com>, Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>, Pavel Machek <pavel@ucw.cz>,
Thomas Gleixner <tglx@linutronix.de>, "H. Anvin" <hpa@zytor.com>,
Arjan van de Ven <arjan@infradead.org>
Subject: Re: x86 git tree broken (bisected)
Date: Tue, 15 Apr 2008 22:27:15 -0600 [thread overview]
Message-ID: <48058023.7080501@shaw.ca> (raw)
In-Reply-To: <fa.qs5oa+YMIJd6h2hpuGCULc8ODY4@ifi.uio.no>
Rafael J. Wysocki wrote:
> On Monday, 14 of April 2008, Yinghai Lu wrote:
>> On Mon, Apr 14, 2008 at 1:21 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
>>> On Monday, 14 of April 2008, Yinghai Lu wrote:
>>> > On Sun, Apr 13, 2008 at 5:19 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
>>> > >
>>> > > On Monday, 14 of April 2008, Yinghai Lu wrote:
>>> > > > On Sun, Apr 13, 2008 at 3:10 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
>>> > > > >
>>> > > > > On Monday, 14 of April 2008, Yinghai Lu wrote:
>>> > > > > > On Sun, Apr 13, 2008 at 9:12 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
>>> > > > > > ...
>>> > > > > > > > can you try to apply the patch i sent to you about agp bridge order
>>> > > > > > > > reading for buggy silicon?
>>> > > > > > > >
>>> > > > > > > > Please boot kernel with "debug"...
>>> > > > > > > >
>>> > > > > > > > I want to verify if you can get
>>> > > > > > > >
>>> > > > > > > > "
>>> > > > > > > > Aperture conflicts with PCI mapping.
>>> > > > > > > > "
>>> > > > > > > >
>>> > > > > > > > in your boot log...
>>> > > > > > >
>>> > > > > > > It's not present in there:
>>> > > > > > >
>>> > > > > > > rafael@albercik:~> grep Aperture failing-with-patch-dmesg.log
>>> > > > > > > Aperture too small (32 MB)
>>> > > > > > > Aperture from AGP @ de000000 size 4096 MB (APSIZE 0)
>>> > > > > > > Aperture too small (0 MB)
>>> > > > > > > agpgart: Aperture pointing to RAM
>>> > > > > > > agpgart: Aperture from AGP @ de000000 size 4096 MB
>>> > > > > > > agpgart: Aperture too small (0 MB)
>>> > > > > > >
>>> > > > > > > Full dmesg output attached.
>>> > > > > >
>>> > > > > > please check attached debug patch. and check if you can change GART
>>> > > > > > size in your BIOS setup to 64M instead of 32M
>>> > > > >
>>> > > > > Hm, what tree am I supposed to apply it too:
>>> > > > > (1) current x86 git
>>> > > > > (2) current x86 git w/ some of your previous patches (which ones in this case)
>>> > > > > (3) failing (old) x86 git
>>> > > > > (4) failing (old) x86 git w/ some of your previous patches (which ones in this
>>> > > > > case)?
>>> > > >
>>> > > > (1) current x86.git
>>> > >
>>> > > Attached is dmesg output from current x86.git with debug_gart_checking.patch
>>> > > applied.
>>> >
>>> > please test the final one ... ...
>>> >
>>> > You should get back 64M memory back.
>>>
>>> Tested (current x86.git), dmesg output attached.
>> thanks.
>>
>> looks good. as expected...
>>
>> Checking aperture...
>> AGP bridge at 00:04:00
>> Aperture from AGP @ de000000 old size 32 MB
>> Aperture size 4096 MB (APSIZE 0) is not right, using settings from NB
>> Aperture from AGP @ de000000 size 32 MB (APSIZE 0)
>> Node 0: aperture @ de000000 size 32 MB
>> Aperture too small (32 MB) than (64 MB)
>> ...
>> agpgart: Detected AGP bridge 20
>> Setting up ULi AGP.
>> agpgart: AGP aperture is 32M @ 0xde000000
>
> BTW, what exactly would be the benefit of increasing the aperture size, given
> that I use a PCI Express graphics adapter?
The kernel uses the AGP GART aperture as an IOMMU. If you have >4GB of
RAM and lots of devices with DMA addressing limits, more GART space
would help prevent the IOMMU space from being exhausted.
next parent reply other threads:[~2008-04-16 4:27 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.2mJjVaMdmV5IWp3mQiYHE1u4pHU@ifi.uio.no>
[not found] ` <fa.SO/I64FxJXD1oLBH54BTs4pc56c@ifi.uio.no>
[not found] ` <fa.fJC0A/aGr6H8XE94NUuvl1ixoc0@ifi.uio.no>
[not found] ` <fa.qs5oa+YMIJd6h2hpuGCULc8ODY4@ifi.uio.no>
2008-04-16 4:27 ` Robert Hancock [this message]
2008-04-10 19:59 x86 git tree broken Rafael J. Wysocki
2008-04-10 20:38 ` Ingo Molnar
2008-04-10 22:28 ` Rafael J. Wysocki
2008-04-11 19:26 ` x86 git tree broken (bisected) Rafael J. Wysocki
2008-04-11 20:23 ` Rafael J. Wysocki
2008-04-11 20:29 ` Rafael J. Wysocki
2008-04-11 20:26 ` Yinghai Lu
2008-04-11 20:51 ` Rafael J. Wysocki
2008-04-11 21:11 ` Yinghai Lu
2008-04-11 21:21 ` Rafael J. Wysocki
2008-04-11 21:31 ` Yinghai Lu
2008-04-13 8:24 ` Yinghai Lu
2008-04-13 8:41 ` Yinghai Lu
2008-04-13 16:14 ` Rafael J. Wysocki
2008-04-14 9:02 ` Ingo Molnar
2008-04-13 16:12 ` Rafael J. Wysocki
2008-04-13 18:07 ` Yinghai Lu
2008-04-13 18:47 ` Rafael J. Wysocki
2008-04-13 18:53 ` Yinghai Lu
2008-04-13 18:54 ` Yinghai Lu
2008-04-13 22:00 ` Yinghai Lu
2008-04-13 22:10 ` Rafael J. Wysocki
2008-04-13 22:32 ` Yinghai Lu
2008-04-13 23:41 ` Rafael J. Wysocki
2008-04-13 23:45 ` H. Peter Anvin
2008-04-14 0:09 ` Rafael J. Wysocki
2008-04-14 0:12 ` H. Peter Anvin
2008-04-14 0:19 ` Rafael J. Wysocki
2008-04-14 1:42 ` Yinghai Lu
2008-04-14 9:16 ` Ingo Molnar
2008-04-14 18:08 ` Yinghai Lu
2008-04-14 20:21 ` Rafael J. Wysocki
2008-04-14 21:06 ` Yinghai Lu
2008-04-14 21:09 ` Rafael J. Wysocki
2008-04-14 21:36 ` Yinghai Lu
2008-04-13 7:51 ` Ingo Molnar
2008-04-13 7:59 ` Yinghai Lu
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=48058023.7080501@shaw.ca \
--to=hancockr@shaw.ca \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=tglx@linutronix.de \
--cc=yhlu.kernel@gmail.com \
/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.