* wandboard-dual, master-next, Xorg segfault
@ 2014-10-02 19:09 Trevor Woerner
2014-10-02 19:17 ` John Weber
0 siblings, 1 reply; 6+ messages in thread
From: Trevor Woerner @ 2014-10-02 19:09 UTC (permalink / raw)
To: meta-freescale
Hi,
I haven't been playing with my wandboard-dual in a while, but last night
I built a new image for it and tested. Coincidentally I started by
running whatever was leftover on my CF card, and it ran fine (i.e. I ran
glxgears, etc).
With the new image, however, the Xorg server segfaults very quickly
after starting. Here is what I found in its log file:
[3512951.484] (EE)
Backtrace:
[3512951.484]
(EE)
[3512951.484] (EE) Segmentation fault at address
0xd8
[3512951.484]
(EE)
Fatal server
error:
[3512951.484] (EE) Caught signal 11 (Segmentation fault). Server
aborting
[3512951.484]
(EE)
[3512951.484] (EE)
Has anyone else seen this or have any ideas what I can try?
Best regards,
Trevor
Build Configuration:
BB_VERSION = "1.24.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "openSUSE-project-13.1"
TARGET_SYS = "arm-poky-linux-gnueabi"
MACHINE = "wandboard-dual"
DISTRO = "poky"
DISTRO_VERSION = "1.7"
TUNE_FEATURES = "arm armv7a vfp neon callconvention-hard cortexa9"
TARGET_FPU = "vfp-neon"
meta
meta-yocto =
"(detachedfrom0389b3b):0389b3b7e8004373320689750ecf877ae5cc6da9"
meta-oe =
"(detachedfrom0d01e1b):0d01e1b72333f49c29d1a27ad844c4cd9f90341c"
meta-fsl-arm =
"(detachedfromda9230e):da9230ee148e192ac8613f587c0f29a73d2da107"
meta-fsl-arm-extra =
"(detachedfrom8f2c0ff):8f2c0ffc973e0ac0e520a6f57d7bbef63e0a4d6a"
meta-fsl-demos =
"contrib/tlwoerner/glive_install_fix:16199439a1cfe4685532954d047c8cfdc1105107"
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: wandboard-dual, master-next, Xorg segfault
2014-10-02 19:09 wandboard-dual, master-next, Xorg segfault Trevor Woerner
@ 2014-10-02 19:17 ` John Weber
2014-10-02 19:36 ` Otavio Salvador
0 siblings, 1 reply; 6+ messages in thread
From: John Weber @ 2014-10-02 19:17 UTC (permalink / raw)
To: meta-freescale
On 10/2/14, 2:09 PM, Trevor Woerner wrote:
> Hi,
>
> I haven't been playing with my wandboard-dual in a while, but last night
> I built a new image for it and tested. Coincidentally I started by
> running whatever was leftover on my CF card, and it ran fine (i.e. I ran
> glxgears, etc).
>
> With the new image, however, the Xorg server segfaults very quickly
> after starting. Here is what I found in its log file:
>
> [3512951.484] (EE)
> Backtrace:
> [3512951.484]
> (EE)
> [3512951.484] (EE) Segmentation fault at address
> 0xd8
> [3512951.484]
> (EE)
> Fatal server
> error:
> [3512951.484] (EE) Caught signal 11 (Segmentation fault). Server
> aborting
> [3512951.484]
> (EE)
> [3512951.484] (EE)
>
>
> Has anyone else seen this or have any ideas what I can try?
Hi Trevor - This could be due to Wandboard kernel not being updated to
3.10.31_1.1.0 in master-next.
John
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: wandboard-dual, master-next, Xorg segfault
2014-10-02 19:17 ` John Weber
@ 2014-10-02 19:36 ` Otavio Salvador
2014-10-02 22:06 ` Trevor Woerner
2014-10-03 13:25 ` Trevor Woerner
0 siblings, 2 replies; 6+ messages in thread
From: Otavio Salvador @ 2014-10-02 19:36 UTC (permalink / raw)
To: John Weber; +Cc: meta-freescale
On Thu, Oct 2, 2014 at 4:17 PM, John Weber <rjohnweber@gmail.com> wrote:
>
> On 10/2/14, 2:09 PM, Trevor Woerner wrote:
>>
>> Hi,
>>
>> I haven't been playing with my wandboard-dual in a while, but last night
>> I built a new image for it and tested. Coincidentally I started by
>> running whatever was leftover on my CF card, and it ran fine (i.e. I ran
>> glxgears, etc).
>>
>> With the new image, however, the Xorg server segfaults very quickly
>> after starting. Here is what I found in its log file:
>>
>> [3512951.484] (EE)
>> Backtrace:
>> [3512951.484]
>> (EE)
>> [3512951.484] (EE) Segmentation fault at address
>> 0xd8
>> [3512951.484]
>> (EE)
>> Fatal server
>> error:
>> [3512951.484] (EE) Caught signal 11 (Segmentation fault). Server
>> aborting
>> [3512951.484]
>> (EE)
>> [3512951.484] (EE)
>>
>>
>> Has anyone else seen this or have any ideas what I can try?
>
> Hi Trevor - This could be due to Wandboard kernel not being updated to
> 3.10.31_1.1.0 in master-next.
Yes; the kernel needs update due newer GPU drivers.
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: wandboard-dual, master-next, Xorg segfault
2014-10-02 19:36 ` Otavio Salvador
@ 2014-10-02 22:06 ` Trevor Woerner
2014-10-02 22:26 ` John Weber
2014-10-03 13:25 ` Trevor Woerner
1 sibling, 1 reply; 6+ messages in thread
From: Trevor Woerner @ 2014-10-02 22:06 UTC (permalink / raw)
To: Otavio Salvador, John Weber; +Cc: meta-freescale
On 10/02/14 15:36, Otavio Salvador wrote:
> On Thu, Oct 2, 2014 at 4:17 PM, John Weber <rjohnweber@gmail.com> wrote:
>> Hi Trevor - This could be due to Wandboard kernel not being updated to
>> 3.10.31_1.1.0 in master-next.
> Yes; the kernel needs update due newer GPU drivers.
Just out of curiosity, I'm interested in knowing what source of
information you people follow? How does one find out the latest kernels
and get notifications when they come out? Do these come from Freescale?
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: wandboard-dual, master-next, Xorg segfault
2014-10-02 22:06 ` Trevor Woerner
@ 2014-10-02 22:26 ` John Weber
0 siblings, 0 replies; 6+ messages in thread
From: John Weber @ 2014-10-02 22:26 UTC (permalink / raw)
To: Trevor Woerner; +Cc: meta-freescale, Otavio Salvador
[-- Attachment #1: Type: text/plain, Size: 933 bytes --]
On Thursday, October 2, 2014, Trevor Woerner <trevor.woerner@linaro.org>
wrote:
>
> On 10/02/14 15:36, Otavio Salvador wrote:
> > On Thu, Oct 2, 2014 at 4:17 PM, John Weber <rjohnweber@gmail.com
> <javascript:;>> wrote:
> >> Hi Trevor - This could be due to Wandboard kernel not being updated to
> >> 3.10.31_1.1.0 in master-next.
> > Yes; the kernel needs update due newer GPU drivers.
>
> Just out of curiosity, I'm interested in knowing what source of
> information you people follow? How does one find out the latest kernels
> and get notifications when they come out? Do these come from Freescale?
>
Actually, the subject of 3.10.31 beta was one of great debate on this
very email list, as the update would undoubtedly break machines that didn't
make the upgrade. In then end it was actually put to a vote and the
decision was to put it in master-next so that it wouldn't break too many
machines in 1.7.
[-- Attachment #2: Type: text/html, Size: 1309 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: wandboard-dual, master-next, Xorg segfault
2014-10-02 19:36 ` Otavio Salvador
2014-10-02 22:06 ` Trevor Woerner
@ 2014-10-03 13:25 ` Trevor Woerner
1 sibling, 0 replies; 6+ messages in thread
From: Trevor Woerner @ 2014-10-03 13:25 UTC (permalink / raw)
To: Otavio Salvador, John Weber; +Cc: meta-freescale
On 10/02/14 15:36, Otavio Salvador wrote:
> On Thu, Oct 2, 2014 at 4:17 PM, John Weber <rjohnweber@gmail.com> wrote:
>> Hi Trevor - This could be due to Wandboard kernel not being updated to
>> 3.10.31_1.1.0 in master-next.
> Yes; the kernel needs update due newer GPU drivers.
Thanks for the feedback, master works much better.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2014-10-03 13:25 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-10-02 19:09 wandboard-dual, master-next, Xorg segfault Trevor Woerner
2014-10-02 19:17 ` John Weber
2014-10-02 19:36 ` Otavio Salvador
2014-10-02 22:06 ` Trevor Woerner
2014-10-02 22:26 ` John Weber
2014-10-03 13:25 ` Trevor Woerner
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.