Bug 6388 - X fails to start on ppc with fbdev
Summary: X fails to start on ppc with fbdev
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/General (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: high blocker
Assignee: Xorg Project Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-25 17:30 UTC by Jory A. Pratt
Modified: 2007-02-22 14:26 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Jory A. Pratt 2006-03-25 17:30:46 UTC
Segfault during X initialization.

xauth:  creating new authority file /home/anarchy/.serverauth.5967


X Window System Version 7.0.0
Release Date: 21 December 2005
X Protocol Version 11, Revision 0, Release 7.0
Build Operating System:Linux 2.6.16-ck1 ppc
Current Operating System: Linux crazier 2.6.16-ck1 #2 Thu Mar 23 13:50:01 CST
2006 ppc
Build Date: 23 March 2006
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Mar 23 21:39:40 2006
(==) Using config file: "/etc/X11/xorg.conf"
(WW) ****INVALID IO ALLOCATION**** b: 0xf0000400 e: 0xf00004ff correcting
(EE) end of block range 0xefffffff < begin 0xf0000000

   *** If unresolved symbols were reported above, they might not
   *** be the reason for the server aborting.

Backtrace:
0: X(xf86SigHandler+0xa8) [0x1007a3ec]
1: [0x100374]
2: /usr/lib/xorg/modules/libshadow.so(shadowUpdatePacked+0x19c) [0xf5d408c]
3: /usr/lib/xorg/modules/libshadow.so [0xf5cfe98]
4: X(BlockHandler+0xdc) [0x1004674c]
5: X(WaitForSomething+0x178) [0x1017cc84]
6: X(Dispatch+0xf0) [0x10042210]
7: X(main+0x43c) [0x100261f4]
8: /lib/libc.so.6 [0xfb966f0]
9: /lib/libc.so.6 [0xfb96914]

Fatal server error:
Caught signal 11.  Server aborting

XIO:  fatal IO error 104 (Connection reset by peer) on X server ":0.0"
      after 0 requests (0 known processed) with 0 events remaining.

Xorg log:
http://dev.gentoo.org/~anarchy/Xorg.0.log

If ya need anything of particular holler and I will test.
Comment 1 Michel Dänzer 2006-03-28 19:20:13 UTC
If depth 15 is correct, I suspect this is a bug in the kernel OFfb. Looking at
the log, it claims that there's only 768 kB of video RAM, which is not enough
for 1024x768 at depth 15. There were a couple of bugs like this when the
framebuffer devices started no longer mapping all video RAM in the kernel, maybe
OFfb is still broken wrt that. Or maybe it's just running in depth 8, and you
need to fix your xorg.conf.

PS: In the future, please attach log files instead of pointing to an external site.
Comment 2 Erik Andren 2006-04-04 05:44:57 UTC
Please post your xorg.conf
Comment 3 Timo Jyrinki 2007-02-22 14:26:27 UTC
Marking broken (status null/blank) bugs in xorg with no activity in a long time as fixed. Please reopen if you think it's necessary, but first do a search if a similar bug report is already filed and in a NEW/ASSIGNED state. These bugs do not currently show in most search results as they do not have any status.

Sorry for this janitorial spam, you know where to send hate mails to when your inbox gets full of bugs you're subscribed to.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.