linux-kernel - Re: [BUG] 2.6.26-rc1 broke X on SPARC Ultra5

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: <21d7e9970806031345u4e7838fdp60bbedadd65b5f2a@mail.gmail.com>
Date:	Wed, 4 Jun 2008 06:45:57 +1000
From:	"Dave Airlie" <airlied@...il.com>
To:	"Mikael Pettersson" <mikpe@...uu.se>
Cc:	"David Miller" <davem@...emloft.net>, sparclinux@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [BUG] 2.6.26-rc1 broke X on SPARC Ultra5

>  >
>  > > Fatal server error:
>  > > xf86MapPciMem: Could not mmap PCI memory [base=0xe2000000,hostbase=0xe2000000,size=2000] (No such file or directory)
>  > >
>  > > I'll start digging through 2.6.25->2.6.26-rc1 later today,
>  > > meanwhile I've put Xorg.0.log, Xorg strace, dmesg, and .config
>  > > files for 2.6.25 (working) and 2.6.26-rc4 (failing) in
>  > > <http://user.it.uu.se/~mikpe/linux/sparc64-2.6.26-rcN-xorg-bug/>.
>  >
>  > It's likely this change below.  Unfortunately older versions of X
>  > seemingly cannot cope with a lack of PCI host controller in the PCI
>  > hierarchy exported by the kernel.
>  >
>  > That's really a bug in X, current libpciaccess based X servers work
>  > fine, and the bug fixed by this changeset is not solvable in any other
>  > reasonable way.  So unfortunately older X verions will stay not
>  > working.  Sorry.
>  >
>  > commit c26d3c0138970778fabe114df99dffb34a04b1d7
>  > Author: David S. Miller <davem@...emloft.net>
>  > Date:   Thu May 1 01:12:40 2008 -0700
>
> Confirmed. Reverting this patch from 2.6.26-rc1 made my Xorg-7.1.1 work again.
>
> It's a shame though that a bug fix needs to have such draconian consequences.
>

Wow thats a major userspace regression to ship, we'd never get away
with doing that on x86 platforms.

Dave.
--
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/