mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mikael Pettersson <mikpe@it.uu.se>
To: davem@davemloft.net, 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
Date: Wed, 30 May 2007 21:33:18 +0200 (MEST)	[thread overview]
Message-ID: <200705301933.l4UJXIE0023913@alkaid.it.uu.se> (raw)

On Tue, 22 May 2007 02:05:34 -0700 (PDT), David Miller <davem@davemloft.net> wrote:
> From: Mikael Pettersson <mikpe@it.uu.se>
> Date: Tue, 22 May 2007 10:40:53 +0200
> 
> > 2.6.21 works fine on my Ultra5, but with 2.6.22-rc the X
> > server (from Aurora 2) fails to mmap() the PCI frame buffer
> > (atyfb).
> > 
> > I noticed a lot of PCI-related changes both in `dmesg' and
> > /var/log/Xorg.0.log between 2.6.21 and 2.6.22-rc, so my
> > guess is that PCI resources get broken somewhere.
> > 
> > I'll try a bisect between 2.6.21 and 2.6.22-rc1 next, but
> > I'm also willing to test patches in case anyone thinks they
> > know what the fix is.
> 
> Start your bisect with the change right before this one:
> 
> commit a2fb23af1c31ad6e0c281e56d385f803229d57fa
> Author: David S. Miller <davem@sunset.davemloft.net>
> Date:   Wed Feb 28 23:35:04 2007 -0800
> 
>     [SPARC64]: Probe PCI bus using OF device tree.
>     
>     Almost entirely taken from the 64-bit PowerPC PCI code.
>     
>     This allowed to eliminate a ton of cruft from the sparc64
>     PCI layer.
>     
>     Signed-off-by: David S. Miller <davem@davemloft.net>
> 
> Unfortunately, if the tree works right before this change,
> you can't just add this one because a subsequent fix is
> needed before ultra5/ultra10 will work again, but it's
> this one:
> 
> commit 01f94c4a6ced476ce69b895426fc29bfc48c69bd
> Author: David S. Miller <davem@ultra5.davemloft.net>
> Date:   Sun Mar 4 12:53:19 2007 -0800
> 
>     [SPARC64]: Fix sabre pci controllers with new probing scheme.

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.

/Mikael

             reply	other threads:[~2007-05-30 19:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-30 19:33 Mikael Pettersson [this message]
2007-05-30 20:01 ` David Miller
2007-06-06 23:22   ` David Miller
2007-06-09  9:18     ` Dmitry Artamonow
  -- 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=200705301933.l4UJXIE0023913@alkaid.it.uu.se \
    --to=mikpe@it.uu.se \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --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®