Re: x86 git tree broken (bisected)

[Rafael J. Wysocki]

On Friday, 11 of April 2008, Rafael J. Wysocki wrote:
> On Friday, 11 of April 2008, Rafael J. Wysocki wrote:
> > On Friday, 11 of April 2008, Rafael J. Wysocki wrote:
> > > On Thursday, 10 of April 2008, Ingo Molnar wrote:
> > > > 
> > > > * Ingo Molnar <mingo@xxxxxxx> 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.
> 
> Update:
> 
> With the above three commits reverted both X itself and suspend to RAM from
> X also work with the current x86-git (as of HEAD equal to
> 1192aeb957402b45f311895f124e4ca41206843c).

That also works from under a framebuffer console, so one of these commits
(presumably ea1441bdf53692c3dc1fd2658addcf1205629661) also breaks suspend on
this box.

Thanks,
Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/