Date: Wed, 06 Jun 2007 16:22:10 -0700 (PDT)
Message-Id: <20070606.162210.35662366.davem@davemloft.net>
To: mikpe@it.uu.se
Cc: linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org
Subject: Re: [BUG sparc64] 2.6.22-rc broke X on Ultra5
From: David Miller <davem@davemloft.net>
In-Reply-To: <20070530.130140.97293476.davem@davemloft.net>
References: <200705301933.l4UJXIE0023913@alkaid.it.uu.se>
	<20070530.130140.97293476.davem@davemloft.net>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1594
Lines: 46

From: David Miller <davem@davemloft.net>
Date: Wed, 30 May 2007 13:01:40 -0700 (PDT)

> From: Mikael Pettersson <mikpe@it.uu.se>
> Date: Wed, 30 May 2007 21:33:18 +0200 (MEST)
> 
> > You were spot on. 2.6.21 + patches up to but not including
> > the first one above works. Adding that one gave me a kernel
> > that wouldn't boot (hung after "uncompressing kernel").
> > Adding the second one above gave me a kernel that booted, but
> > where X failed to mmap() the frame buffer as I described.
> 
> Thanks for all of your testing.
> 
> I'll try to figure this out on one of my Ultra5's here.

So I did some more digging, got my ultra5 running and I can't
get it to work with both 2.6.20 and 2.6.22-rc4 :-)  This is
with xorg-7.2, and they both fail with:

xf86MapPciMem: Could not mmap ...

which I assume is the error you're seeing.

Investigation reveals that X.org is erroneously trying to
do PCI mmap ioctl()'s on /sys/bus/pci/devices/*/config
files which is very very wrong.  Again this happens for me
with both 2.6.20 and 2.6.22

Can you just quickly strace "Xorg" startup in the working
and non-working case?  Just a simple:

	strace -o x.log Xorg

would for both cases be fine.

You can email it to me privately, and I'll post here my
analysis with the relevant portions quoted so we don't
flood the list with strace dumps :-)

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