From: Matthias Transier <matthias.transier@gmail.com>
To: linuxppc-embedded@ozlabs.org
Subject: Segmentation fault with X.org and Coral-P drivers
Date: Wed, 4 Jan 2006 12:33:58 +0100 [thread overview]
Message-ID: <b789c2e60601040333o42d64c52n@mail.gmail.com> (raw)
Hello everybody,
I have been trying to get X.org running on a board called "Embedded
Planet EP5200C" (it seems to be a "Freescale Lite5200") and a Fujitsu
Coral-P (Rev 5.0). I am using the 2.4 kernel from denx.de and
succesfully installed gentoo-ppc on nfs. The framebuffer works, I get
a login prompt on the monitor.
Now I compiled x.org-6.8.2 (gentoo -r4) and the mb86290 driver from
denx.de. Unfortunately, it does not work and I get a segmentation
fault when trying to startx. strace produces the output attached
below.
Can anybody give me a hint how to proceed?
Regards,
Matthias
[...]
mmap(NULL, 33554432, PROT_READ|PROT_WRITE, MAP_SHARED, 6, 0) =3D 0x30042000
ioctl(6, FBIOGET_VSCREENINFO, 0x105dfa58) =3D 0
ioctl(6, FBIOPUT_VSCREENINFO, 0x105df9b8) =3D 0
ioctl(6, FBIOGET_FSCREENINFO, 0x105df974) =3D 0
ioctl(6, FBIOGET_VSCREENINFO, 0x105df9b8) =3D 0
ioctl(6, FBIOBLANK, 0x1) =3D 0
ioctl(6, FBIOPAN_DISPLAY, 0x105df9b8) =3D 0
write(0, "(=3D=3D) MB86290(0): Backing store d"..., 40) =3D 40
write(0, "(II) MB86290(0): Using XFree86 A"..., 63) =3D 63
write(0, "\tScreen to screen bit blits\n", 28) =3D 28
write(0, "\tSolid filled rectangles\n", 25) =3D 25
write(0, "\t8x8 mono pattern filled rectang"..., 36) =3D 36
write(0, "\tIndirect CPU to Screen color ex"..., 40) =3D 40
write(0, "\tSolid Lines\n", 13) =3D 13
write(0, "\tDashed Lines\n", 14) =3D 14
write(0, "(II) MB86290(0): Acceleration en"..., 38) =3D 38
ioctl(6, FBIOPUTCMAP, 0x7ffff930) =3D 0
ioctl(6, FBIOPUTCMAP, 0x7ffff930) =3D 0
ioctl(6, FBIOPUTCMAP, 0x7ffff930) =3D 0
ioctl(6, FBIOPUTCMAP, 0x7ffff930) =3D 0
ioctl(6, FBIOPUTCMAP, 0x7ffff930) =3D 0
ioctl(6, FBIOPUTCMAP, 0x7ffff930) =3D 0
ioctl(6, FBIOPUTCMAP, 0x7ffff930) =3D 0
ioctl(6, FBIOPUTCMAP, 0x7ffff930) =3D 0
ioctl(6, FBIOPUTCMAP, 0x7ffff930) =3D 0
ioctl(6, FBIOPUTCMAP, 0x7ffff930) =3D 0
ioctl(6, FBIOPUTCMAP, 0x7ffff930) =3D 0
ioctl(6, FBIOPUTCMAP, 0x7ffff930) =3D 0
ioctl(6, FBIOPUTCMAP, 0x7ffff930) =3D 0
ioctl(6, FBIOPUTCMAP, 0x7ffff930) =3D 0
ioctl(6, FBIOPUTCMAP, 0x7ffff930) =3D 0
ioctl(6, FBIOPUTCMAP, 0x7ffff930) =3D 0
ioctl(6, FBIOPUTCMAP, 0x7ffff930) =3D 0
ioctl(6, FBIOPUTCMAP, 0x7ffff930) =3D 0
ioctl(6, FBIOPUTCMAP, 0x7ffff930) =3D 0
ioctl(6, FBIOPUTCMAP, 0x7ffff930) =3D 0
ioctl(6, FBIOPUTCMAP, 0x7ffff930) =3D 0
ioctl(6, FBIOPUTCMAP, 0x7ffff930) =3D 0
ioctl(6, FBIOPUTCMAP, 0x7ffff930) =3D 0
ioctl(6, FBIOPUTCMAP, 0x7ffff930) =3D 0
ioctl(6, FBIOPUTCMAP, 0x7ffff930) =3D 0
ioctl(6, FBIOPUTCMAP, 0x7ffff930) =3D 0
ioctl(6, FBIOPUTCMAP, 0x7ffff930) =3D 0
ioctl(6, FBIOPUTCMAP, 0x7ffff930) =3D 0
ioctl(6, FBIOPUTCMAP, 0x7ffff930) =3D 0
ioctl(6, FBIOPUTCMAP, 0x7ffff930) =3D 0
ioctl(6, FBIOPUTCMAP, 0x7ffff930) =3D 0
ioctl(6, FBIOPUTCMAP, 0x7ffff930) =3D 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
rt_sigaction(SIGSEGV, {SIG_IGN}, {0x100424d0, [SEGV], SA_RESTART}, 8) =3D 0
write(2, "\n *** If unresolved symbols we"..., 112
[...]
next reply other threads:[~2006-01-04 11:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-04 11:33 Matthias Transier [this message]
2006-01-04 15:48 ` Segmentation fault with X.org and Coral-P drivers Wolfgang Denk
2006-01-04 16:19 ` Matthias Transier
2006-01-04 17:59 ` Matthias Transier
2006-01-04 21:11 ` Wolfgang Denk
2006-01-04 21:10 ` Wolfgang Denk
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=b789c2e60601040333o42d64c52n@mail.gmail.com \
--to=matthias.transier@gmail.com \
--cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).