Bug 7543

Summary: [BeagleboneBlack] some error message in Xorg.log
Product: [Build System, Metadata & Runtime] BSPs Reporter: Yi Zhao <yi.zhao>
Component: bsps-meta-yoctoAssignee: Kevin Hao <kexin.hao>
Status: VERIFIED WONTFIX QA Contact: Yi Zhao <yi.zhao>
Severity: normal    
Priority: Low CC: alexandru.c.georgescu, dave.lerner, ke.zou, ross.burton, yi.zhao, zhangle.yang
Version: 1.8   
Target Milestone: 1.9   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: New (Never tested)
Verified: Documentation change: No (bug/feature does not impact docs)
Bug Depends on: 7561    
Bug Blocks:    
Attachments:
Description Flags
xorg.log none

Description Yi Zhao 2015-03-31 07:45:00 UTC 
Created attachment 2460 [details]
xorg.log

Git rev: master/8b3d3e7c957ad06c390886487f69aeb8e145da6a

Image location: http://autobuilder.yoctoproject.org/pub/releases/yocto-1.8_M4.rc1/machines/beaglebone/

There are some error messages in Xorg.0.log:
##########################
[1858061.801] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[1858061.801] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[1858061.801] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[1858061.801] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[1858061.801] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[1858061.801] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[1858061.801] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[1858061.801] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
##########################

When reboot the system, I got some errors for Xorg:
##########################
Stopping XServer
xinit: connection to X server lost

waiting for X server to shut down Stopping Connection Manager
Stopping Telephony daemon
(EE) 
Fatal server error:
(EE) xf86CloseConsole: VT_ACTIVATE failed: Input/output error
(EE) 
(EE) 
Please consult the The X.Org Foundation support 
         at http://wiki.x.org
 for help. 
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
(EE) 
(EE) 
FatalError re-entered, aborting
(EE) xf86CloseConsole: VT_ACTIVATE failed: Input/output error
(EE) 
Stopping rpcbind daemon...
done.
Stopping Linux NFC daemon
Deconfiguring network interfaces... done.
Sending all processes the TERM signal...
Error VT_WAITACTIVE failed
: Interrupted system call

xinit: unexpected signal 15
###########################
Comment 1 Ross Burton 2015-04-02 15:10:58 UTC 
From the IM when talking about the related crash:

"17:57:19 alanc: won't stop the server from failing to release VT's, should just avoid crashing while aborting"

I'm wondering if those are to be considered "normal".
Comment 2 Ross Burton 2015-04-02 15:57:44 UTC 
<ajax> normal if you're using drm's fbdev emulation
<ajax> whether it's desirable i guess depends on whether you have other fbdev apps touching the colormap and have some expectatin about how that'd work
<ajax> but since that's unlikely, it's probably harmless and we could reasonably squash it.

Sounds like it's nothing to worry about.
Comment 3 Ross Burton 2015-04-02 16:26:14 UTC 
<daniels> rburton: perfectly normal
<Jasper> Anyway, the kernel telling you using colormaps on an fbdev isn't supported in 2015 is very normal

TL;DR: don't use -fbdev driver.  I've filed #7561 for this.
Comment 4 Alexandru Georgescu 2015-04-09 15:32:58 UTC 
found during 1.8_M4.rc2 testing
fido:33558eacc8a2d3dce3396b9ab2fd0773ac5076bc
Comment 5 Dave Lerner 2015-06-01 14:27:10 UTC 
*** Bug 7750 has been marked as a duplicate of this bug. ***
Comment 6 Kevin Hao 2015-06-03 07:03:14 UTC 
The errors seem pretty normal when using fbdev driver.
Comment 7 Yi Zhao 2015-09-08 07:03:17 UTC 
Verified it