From: Dmitry Artamonow <mad_soft@inbox.ru>
To: David Miller <davem@davemloft.net>
Cc: mikpe@it.uu.se, linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org
Subject: Re: [BUG sparc64] 2.6.22-rc broke X on Ultra5
Date: Sat, 9 Jun 2007 13:18:04 +0400 [thread overview]
Message-ID: <20070609091804.GA3793@sunflower.office.asoft.ru> (raw)
In-Reply-To: <20070606.162210.35662366.davem@davemloft.net>
Good day!
Sorry for intruding, but I'm seeing the same problem on my U10 with
2.6.22-rc3 and Xorg-7.1+gentoo patches.
On Wed, Jun 06, 2007 at 04:22:10PM -0700, David Miller wrote:
> 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
Xorg-7.2 (to be more precise, xorg-server-1.2.0) never worked for me, you
can see my bug on gentoo bugzilla for more info:
http://bugs.gentoo.org/show_bug.cgi?id=167052
But Xorg-7.1 worked fine on kernels up and including 2.6.21
>
> 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!
I sent David privately my .configs , Xorg.0.logs and strace logs for 2.6.21
and 2.6.22-rc3. Hope it helps.
--
Best regards,
Dmitry 'MAD' Artamonow
next prev parent reply other threads:[~2007-06-09 9:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-30 19:33 Mikael Pettersson
2007-05-30 20:01 ` David Miller
2007-06-06 23:22 ` David Miller
2007-06-09 9:18 ` Dmitry Artamonow [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-06-07 6:24 Mikael Pettersson
2007-06-07 6:25 ` David Miller
2007-05-22 8:40 Mikael Pettersson
2007-05-22 9:05 ` David Miller
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=20070609091804.GA3793@sunflower.office.asoft.ru \
--to=mad_soft@inbox.ru \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
--cc=sparclinux@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®