STATUS: IDLE BUILD: 2.3_M2_rc3: 226a508da955439b881b2f0a544a3aee76e59919 ENVIRONMENT: qemu-x86 STEPS TO REPRODUCE: 1. Boot image 2. Check dmesg EXPECTED OUTCOME: No errors or fails should be present in logs ACTUAL OUTCOME: Central error: [ 40.852] (II) FBDEV(0): mode "640x480" test failed *********************** [ 40.824] (**) FBDEV(1): claimed PCI slot 0@0:2:0 [ 40.824] (II) FBDEV(1): using default device [ 40.829] (EE) Screen 0 deleted because of no matching config section. [ 40.829] (II) UnloadModule: "modesetting" [ 40.840] (==) FBDEV(0): Depth 16, (==) framebuffer bpp 16 [ 40.840] (==) FBDEV(0): RGB weight 565 [ 40.851] (==) FBDEV(0): Default visual is TrueColor [ 40.851] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0) [ 40.851] (II) FBDEV(0): hardware: VESA VGA (video memory: 16384kB) [ 40.852] (II) FBDEV(0): checking modes against framebuffer device... [ 40.852] (II) FBDEV(0): mode "640x480" test failed [ 40.852] (II) FBDEV(0): mode "640x480" test failed [ 40.852] (II) FBDEV(0): mode "640x480" test failed [ 40.853] (II) FBDEV(0): mode "640x480" ok [ 40.853] (II) FBDEV(0): checking modes against monitor... [ 40.853] (--) FBDEV(0): Virtual size is 640x480 (pitch 640) [ 40.853] (**) FBDEV(0): Mode "640x480": 36.0 MHz (scaled from 0.0 MHz), 43.3 kHz, 85.0 Hz [ 40.854] (II) FBDEV(0): Modeline "640x480"x0.0 36.00 640 696 752 832 480 481 484 509 -hsync -vsync (43.3 kHz) [ 40.854] (==) FBDEV(0): DPI set to (96, 96) [ 40.854] (II) Loading sub module "fb" [ 40.854] (II) LoadModule: "fb" [ 40.861] (II) Loading /usr/lib/xorg/modules/libfb.so [ 40.865] (II) Module fb: vendor="X.Org Foundation" ***********************
This doesn't seem related to the kernel or the BSP, did X update and now we are seeing this message ? I'm bouncing this to Ross so he can add an opinion as well. If this looks like kernel .. send it back.
Jussi can you have a look?
Jose, which image is this exactly? core-image-sato? (In reply to comment #0) > Central error: [ 40.852] (II) FBDEV(0): mode "640x480" test failed This is (II) so "informational". > [ 40.829] (EE) Screen 0 deleted because of no matching config section. This is an actual X error. I wonder if " (EE) " should be added to the list of strings that trigger this QA check...
(In reply to comment #3) > Jose, which image is this exactly? core-image-sato? > This is core-image-sato-sdk > > (In reply to comment #0) > > Central error: [ 40.852] (II) FBDEV(0): mode "640x480" test failed > > This is (II) so "informational". > > > [ 40.829] (EE) Screen 0 deleted because of no matching config section. > > This is an actual X error. I wonder if " (EE) " should be added to the list > of strings that trigger this QA check...
I can't reproduce the messages. I've tried building core-image-sato-sdk for qemux86 on both master and the m2 rc3 poky revision and running runqemu qemux86 kvm I can't see anything like the messages in the original report. I'm a bit out of ideas, I think I need more specific reproduction instructions. Alternatively, if you tell me how to run the QA images I can do that (I apparently have no idea how runqemu works nowadays, see bug 11170). Please reassign to me when appropriate, thanks.
(In reply to comment #5) > I can't reproduce the messages. I've tried building core-image-sato-sdk for > qemux86 on both master and the m2 rc3 poky revision and running > > runqemu qemux86 kvm usually we just ran $runqemu qemux86 > > I can't see anything like the messages in the original report. I'm a bit out > of ideas, I think I need more specific reproduction instructions. > > Alternatively, if you tell me how to run the QA images I can do that (I > apparently have no idea how runqemu works nowadays, see bug 11170). > > Please reassign to me when appropriate, thanks. I did a couple on test on master and cannot reproduce this issue so maybe was a corner case. will close this issue as invalid and will reopen if I saw it again.
not presented errors in Xorg all task whit xorg-lib pass success COMMIT: 226a508da955439b881b2f0a544a3aee76e59919 ENVIRONMENT: qemux86 STEPS TO REPRODUCE: 1. Boot image 2. Check dmesg EXPECTED OUTCOME: No errors or fails should be present in logs ACTUAL OUTCOME: No errors or fails should be present in logs =============================================================================== NOTE: Running task 384 of 410 (virtual:native:/home/oscar/quemux/meta/recipes-graphics/xorg-lib/libxrandr_1.5.1.bb:do_configure) NOTE: recipe libxrandr-native-1_1.5.1-r0: task do_configure: Started NOTE: recipe libxrandr-native-1_1.5.1-r0: task do_configure: Succeeded NOTE: Running task 385 of 410 (virtual:native:/home/oscar/quemux/meta/recipes-graphics/xorg-lib/libxrandr_1.5.1.bb:do_compile) NOTE: recipe libxrandr-native-1_1.5.1-r0: task do_compile: Started NOTE: recipe libxrandr-native-1_1.5.1-r0: task do_compile: Succeeded NOTE: Running task 386 of 410 (virtual:native:/home/oscar/quemux/meta/recipes-graphics/xorg-lib/libxrandr_1.5.1.bb:do_install) NOTE: recipe libxrandr-native-1_1.5.1-r0: task do_install: Started NOTE: recipe libxrandr-native-1_1.5.1-r0: task do_install: Succeeded NOTE: Running task 387 of 410 (virtual:native:/home/oscar/quemux/meta/recipes-graphics/xorg-lib/libxrandr_1.5.1.bb:do_populate_sysroot) NOTE: recipe libxrandr-native-1_1.5.1-r0: task do_populate_sysroot: Started NOTE: recipe libxrandr-native-1_1.5.1-r0: task do_populate_sysroot: Succeeded NOTE: Tasks Summary: Attempted 410 tasks of which 0 didn't need to be rerun and all succeeded. =============================================================================== full-log and screen shot for qemux86 dmesg in attachment
Created attachment 4135 [details] check dmesg
Created attachment 4136 [details] full-log
I miss putting in verified