STATUS: FAILED BUILD: 2.0.1_RC2:dd0ba9ea4a11ab15348d4fe3574e4b28784db82f ENVIRONMENT: genericx86-64-LSB on NUC IMAGE: core-image-lsb-sdk STEPS TO REPRODUCE: Parse dmesg log and all log files in /var/log for keywords like: "error" , "failed" , "cannot", "can't" etc. Filter out the known and invalid errors or errors that appear in certain situations and need to be ignored. The image can be found at the following link: http://autobuilder.yoctoproject.org/pub/releases/yocto-2.0.1.rc2/machines/genericx86-64-lsb/core-image-lsb-sdk-genericx86-64.hddimg EXPECTED OUTCOME: No errors or fails should be present in logs ACTUAL OUTCOME: This error appears: Central error: [ 0.463667] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear. | *********************** | Jan 26 18:16:49 genericx86-64 kernel: hid-generic 0003:04F3:0103.0002: input: USB HID v1.11 Device [HID 04f3:0103] on usb-0000:00:14.0-3/input1 | Jan 26 18:16:49 genericx86-64 kernel: usb 2-4: new low-speed USB device number 3 using xhci_hcd | Jan 26 18:16:49 genericx86-64 kernel: usb 2-4: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes | Jan 26 18:16:49 genericx86-64 kernel: input: HP HP as /devices/pci0000:00/0000:00:14.0/usb2/2-4/2-4:1.0/0003:03F0:0C4A.0003/input/input9 | Jan 26 18:16:49 genericx86-64 kernel: hid-generic 0003:03F0:0C4A.0003: input: USB HID v1.11 Mouse [HP HP] on usb-0000:00:14.0-4/input0 | Jan 26 18:16:49 genericx86-64 kernel: usb 2-7: new full-speed USB device number 4 using xhci_hcd | Jan 26 18:16:49 genericx86-64 kernel: usb 2-7: No LPM exit latency info found. Power management will be impacted. | Jan 26 18:16:49 genericx86-64 kernel: Switched to clocksource tsc | Jan 26 18:16:49 genericx86-64 kernel: uvesafb: Getting VBE info block failed (eax=0x4f00, err=1) | Jan 26 18:16:49 genericx86-64 kernel: uvesafb: vbe_init() failed with -22 | Jan 26 18:16:49 genericx86-64 kernel: uvesafb: probe of uvesafb.0 failed with error -22 | Jan 26 18:16:49 genericx86-64 kernel: <30>udevd[113]: starting version 182 | Jan 26 18:16:49 genericx86-64 kernel: snd_hda_intel 0000:00:03.0: enabling device (0000 -> 0002) | Jan 26 18:16:49 genericx86-64 kernel: snd_hda_intel 0000:00:1b.0: enabling device (0000 -> 0002) | Jan 26 18:16:49 genericx86-64 kernel: snd_hda_intel 0000:00:03.0: irq 60 for MSI/MSI-X | Jan 26 18:16:49 genericx86-64 kernel: snd_hda_intel 0000:00:1b.0: irq 61 for MSI/MSI-X | Jan 26 18:16:49 genericx86-64 kernel: Too many HDMI devices | Jan 26 18:16:49 genericx86-64 kernel: Consider building the kernel with CONFIG_SND_DYNAMIC_MINORS=y | Jan 26 18:16:49 genericx86-64 kernel: Adding 5860348k swap on /dev/sda3. Priority:-1 extents:1 across:5860348k SS | Jan 26 18:16:49 genericx86-64 kernel: random: dd urandom read with 109 bits of entropy available | Jan 26 18:16:49 genericx86-64 kernel: random: nonblocking pool is initialized
I don't have NUC now to repeat this issue, need to find some way to reproduce it.
I have to assign this back to reporter for more information. Now I have got NUC gen 6 but cannot reproduce two errors in log attached. For this DRM error: "Central error: [ 0.463667] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out" My NUC gen 6 has new issues with graphic in UEFI boot with genericx86_64 build (minimal and lsb). So I tested it in legacy boot mode. Cannot reproduce this error. Please reporter let us know: () If this issue can still be seen in NUC you have () model info of impacted NUC device if issue is still there. For another uvesafb issue, " uvesafb: Getting VBE info block failed " This issue is same as https://bugzilla.yoctoproject.org/show_bug.cgi?id=6584. The fix has been back ported to Jethro from master, so I don't think this error still effective. Cristina, If you still see the first DRM error with recent builds on that NUC, please help to provide the necessary info and feel free to assign it bake to me. Thanks lot!
On jethro 2.0.1_rc6, poky: 5b12268f6e17574999f91628a60e21711cf62ee4 core-image-sato-sdk the issue cannot be reproduced. Since the error is no longer present we could close it and reopen if needed.
Set it as verified.