I have problem with xorg

[burakpi]

My log is:

Code: Select all

[  3318.136] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[  3321.108] (EE) FBDEV(0): FBIOBLANK: Operation not permitted
[  3321.226] (EE) FBDEV(0): FBIOBLANK: Operation not permitted
[  3406.393] (EE) 
[  3406.395] (EE) Backtrace:
[  3406.397] (EE) 
[  3406.399] (EE) Segmentation fault at address 0x2f
[  3406.401] 
Fatal server error:
[  3406.402] Caught signal 11 (Segmentation fault). Server aborting
[  3406.403] 
[  3406.403] (EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
[  3406.406] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[  3406.408] (EE) 
[  3406.409] (EE) FBDEV(0): FBIOBLANK: Operation not permitted
[  3406.482] Server terminated with error (1). Closing log file.

What is wrong? I am running Midori. After some minutes, xorg gives that fatal error.

[DBryant]

Can you give more details?

What distro are you using?
Is this after several minutes of intensive browsing, or does it occur if just left to its own devices?
Is there a particular URL, or site's page that provokes the fault?
Are your visiting sites that are heavy in their use of video or other eye candy?

What steps have you taken to investigate the issue yourself.
If you run top for example, to observe processes running, do you see any one process start to consume resources? Is there an excessive number of processes being created?

[burakpi]

I am installed ArchLinux. I did the instructions given at https://github.com/MobilityLab/TransitS ... spberry-Pi and

https://wiki.archlinux.org/index.php/Cr ... _Web_Kiosk

I opened http://themes.themegoods.com/pluto_wp/ and some websites that executes some javascript galleries. So I had segmentation fault errors after 1-2 minutes.

When I tried http://www.google.com, it didn't give segmentation fault.

[DBryant]

Hmmm. I've never really found the Pi to that good for browsing the inter-web, and I don't think that I'm particularly unique in that.

The Pluto wp web-site you've given sends the CPU on my desktop to 40% and the chromium is very active and churning through plenty of memory as is cycles through its slideshows. I would expect the Pi to struggle to render this sort of graphical experience but having the underlying X seg fault is not good.

I'd suggest you wander over to the Midori development web-site and see it these sort of issues are known. They may well have suggestions there.

[sdjf]

The code you posted says to check another log to get more details, did you do that?

[ 3406.406] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.

[burakpi]

Code: Select all

[  1261.668] (==) RandR enabled
[  1261.765] (II) AIGLX: Screen 0 is not DRI2 capable
[  1261.765] (II) AIGLX: Screen 0 is not DRI capable
[  1261.829] (II) AIGLX: Loaded and initialized swrast
[  1261.829] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[  1262.375] (EE) FBDEV(0): FBIOBLANK: Operation not permitted
[  1262.494] (EE) FBDEV(0): FBIOBLANK: Operation not permitted
[  1420.602] (EE) 
[  1420.603] (EE) Backtrace:
[  1420.603] (EE) 
[  1420.604] (EE) Segmentation fault at address 0x2f
[  1420.604] 
Fatal server error:
[  1420.604] Caught signal 11 (Segmentation fault). Server aborting
[  1420.604] 
[  1420.604] (EE) 

I am getting these logs.

[sdjf]

Now that gives us something useful to follow up on. Try googling the following, there are a lot of pages where people are discussing that. One github thread says it is a normal error on the Pi, I don't think that means it is okay.

"FBDEV(0): FBIOBLANK: Operation not permitted"

You have an excellent example of the trouble. But it sounds like there is not an easy way to do what you want.

Another thread, pepedog said a fix was getting made.

Are you running ARch? Have you updated with pacman -Syu lately?

[burakpi]

Yes, I've just updated pacman.

I guess the problem is about memory. Because in first minutes, everything is ok. And with lightweight web page like google.com, everything was ok.

[deadsnow44]

Same problem here...
I had no issues for weeks until a system update. With normal usage it takes a few minutes to crash, but when I move a window rapidly, X11 crashes in a few seconds.
/var/log/errors.log says: systemd-coredump: out of memory