From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Xorg Segmentation fault now. Please help
Date: Thu, 10 Sep 2015 10:19:04 +0200 [thread overview]
Message-ID: <55F13CF8.3070706@mind.be> (raw)
In-Reply-To: <CAEzGmjDwBwLt8kynQpjj-2sKtOX6Un7TLXX1i7sH6vBODda+9A@mail.gmail.com>
On 10-09-15 09:15, Lennart Ramberg wrote:
> Hello,
>
> After having been away from Buildroot since last year, I'm at it again.
> But I had a setback;
>
> With 2014.11 the xorg-server runs allright.
> Jumping to 2015.08.1 the xorg-server won't run.
> Why might this be? Please help.
>
> Below is a part of my /var/log/Xorg.0.log after I executed 'X',
> as well as my defconfig (and there is nothing suspicious in the overlays).
> And I did a 'make clean all' first.
I know nothing about X, but here are a few tips:
- I see you are using ccache. That is still not 100% reliable, so perhaps try
again with turning ccache off and do a make clean all.
- You could disable the intel driver and enable e.g. VESA or fbdev to isolate
where the issue is.
- You could try to vary the kernel and gcc versions.
And of course, check the Xorg bug tracker.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2015-09-10 8:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-10 7:15 [Buildroot] Xorg Segmentation fault now. Please help Lennart Ramberg
2015-09-10 8:19 ` Arnout Vandecappelle [this message]
2015-09-10 13:07 ` Lennart Ramberg
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=55F13CF8.3070706@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.