linux-kernel - Re: x86 git tree broken (bisected)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200804112223.14160.rjw@sisk.pl>
Date:	Fri, 11 Apr 2008 22:23:13 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Yinghai Lu <yinghai.lu@....com>,
	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 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@...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.

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).

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