[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <86802c440804131107s7c132bc6j10ba713e50589353@mail.gmail.com>
Date: Sun, 13 Apr 2008 11:07:31 -0700
From: "Yinghai Lu" <yhlu.kernel@...il.com>
To: "Rafael J. Wysocki" <rjw@...k.pl>
Cc: "Ingo Molnar" <mingo@...e.hu>,
"Andrew Morton" <akpm@...ux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>,
"Pavel Machek" <pavel@....cz>,
"Thomas Gleixner" <tglx@...utronix.de>, "H. Anvin" <hpa@...or.com>,
"Arjan van de Ven" <arjan@...radead.org>
Subject: Re: x86 git tree broken (bisected)
On Sun, Apr 13, 2008 at 9:12 AM, Rafael J. Wysocki <rjw@...k.pl> wrote:
>
> On Sunday, 13 of April 2008, Yinghai Lu wrote:
> > On Fri, Apr 11, 2008 at 1:51 PM, Rafael J. Wysocki <rjw@...k.pl> wrote:
> > >
> > > On Friday, 11 of April 2008, Yinghai Lu wrote:
> > > > On Fri, Apr 11, 2008 at 12:26 PM, Rafael J. Wysocki <rjw@...k.pl> wrote:
> > > > > On Friday, 11 of April 2008, Rafael J. Wysocki wrote:
> > > > > > On Thursday, 10 of April 2008, Ingo Molnar wrote:
> > > > > > >
> > > > > > > * Ingo Molnar <mingo@...e.hu> wrote:
> > > > > > >
> > > > > > > > > > > First, the X server doesn't want to start (it says it couldn't
> > > > > > > > > > > mmap the framebuffer).
> > > > > > > > > >
> > > > > > > > > > could you send your .config?
> > > > > > > > >
> > > > > > > > > Attached.
> > > > > > > >
> > > > > > > > could you disable this option:
> > > > > > > >
> > > > > > > > CONFIG_NONPROMISC_DEVMEM=y
> > > > > > > >
> > > > > > > > does it help with the X problem?
> > > > > >
> > > > > > That didn't help.
> > > > > >
> > > > > > > btw., Xorg works fine here on a comparable AMD system - but i use a
> > > > > > > rather new distro (Fedora 8) which has Xorg 7.2.
> > > > > >
> > > > > > My system is an OpenSUSE 10.3 and it has Xorg 7.2 as well.
> > > > > >
> > > > > > I think the problem is somehow related to the Radeon.
> > > > >
> > > > > The bisection turned up commit ea1441bdf53692c3dc1fd2658addcf1205629661
> > > > > "x86: use bus conf in NB conf fun1 to get bus range on, on 64-bit" as the one
> > > > > causing problems.
> > > > >
> > > > > Unfortunately, I can't revert cleanly it, because there are two more commits
> > > > > depending on it in a highly nontrivial fashion, so I have reverted all three
> > > > > commits
> > > > >
> > > > > a365998cd2cecfb827469dbd57c29602c106cb83
> > > > > 44f7f90fbe7a3a99aab082f765346514b7b5c705
> > > > > ea1441bdf53692c3dc1fd2658addcf1205629661
> > > > >
> > > > > and X starts again. Also, suspend to RAM works from under X.
> > > >
> > > > please keep the three patches and applied the two attached debug patches.
> > > >
> > > > i wonder if there is some io allocation overlapping with your system.
> > >
> > > Attached is a boot dmesg output from the current x86 git tree with your two
> > > patches applied.
> > >
> > 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@...ercik:~> 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)
>
did you apply the patch like the attached that i sent you in another mail?
YH
View attachment "fix_buggy_agp_order.patch" of type "text/x-patch" (3684 bytes)
Powered by blists - more mailing lists