EMGD will cause calltrace on BayTrail BSP. Steps reproduce: 1. sudo dd if=~/disk2/poky/meta-intel/meta-baytrail/binary/core-image-sato-baytrail64.hddimg of=/dev/sdc 2. boot it on Bakersport/BayleyBay 3. on the terminal: $dmesg | grep "Call Trace" [ 0.800328] ------------[ cut here ]------------ [ 0.800346] WARNING: at /home/ilab/build/baytrail/tmp/work/baytrail64-poky-linux/linux-yocto/3.8.0+gitAUTOINC+cad4929004676d4ca62eac39e22a02aef7db686c_19f949f52599ba7c3f67a5897ac6be14bfcb1200-r5.1/linux/mm/page_alloc.c:2376 __alloc_pages_nodemask+0x3c2/0xa10() [ 0.800368] Hardware name: VALLEYVIEW B0 PLATFORM [ 0.800375] Modules linked in: [ 0.800385] Pid: 1, comm: swapper/0 Not tainted 3.8.0-yocto-standard #1 [ 0.800393] Call Trace: [ 0.800407] [<ffffffff81035e4f>] warn_slowpath_common+0x7f/0xc0 [ 0.800419] [<ffffffff81035eaa>] warn_slowpath_null+0x1a/0x20 [ 0.800429] [<ffffffff810eff12>] __alloc_pages_nodemask+0x3c2/0xa10 [ 0.800441] [<ffffffff810efd00>] ? __alloc_pages_nodemask+0x1b0/0xa10 [ 0.800454] [<ffffffff8178dbab>] ? _raw_spin_lock+0x1b/0x40 [ 0.800465] [<ffffffff8178d966>] ? _raw_spin_unlock+0x16/0x40 [ 0.800476] [<ffffffff8178d966>] ? _raw_spin_unlock+0x16/0x40 [ 0.800489] [<ffffffff81776b35>] ? klist_put+0x75/0xb0 [ 0.800499] [<ffffffff810f0577>] __get_free_pages+0x17/0x50 [ 0.800510] [<ffffffff81125769>] kmalloc_order_trace+0x39/0xf0 [ 0.800524] [<ffffffff814b8667>] reg_alloc_vlv+0x57/0xf0 [ 0.800535] [<ffffffff814b7519>] _reg_init+0xe9/0x120 [ 0.800545] [<ffffffff81492ec7>] igd_module_init+0x47/0xb0 [ 0.800558] [<ffffffff8143b59f>] emgd_startup_hal+0x1f/0x30 [ 0.800568] [<ffffffff8143bd2a>] emgd_driver_load+0x33a/0x950 [ 0.800580] [<ffffffff8141ddc6>] drm_get_pci_dev+0x186/0x2c0 [ 0.800592] [<ffffffff8143a450>] emgd_pci_probe+0x20/0x30 [ 0.800604] [<ffffffff81379bec>] pci_device_probe+0x9c/0xe0 [ 0.800615] [<ffffffff814bfabb>] driver_probe_device+0x7b/0x240 [ 0.800627] [<ffffffff814bfd2b>] __driver_attach+0xab/0xb0 [ 0.800638] [<ffffffff814bfc80>] ? driver_probe_device+0x240/0x240 [ 0.800649] [<ffffffff814bdd75>] bus_for_each_dev+0x55/0x90 [ 0.800660] [<ffffffff814bf5fe>] driver_attach+0x1e/0x20 [ 0.800670] [<ffffffff814bf190>] bus_add_driver+0x190/0x260 [ 0.800682] [<ffffffff81cfcd67>] ? drm_core_init+0x136/0x136 [ 0.800693] [<ffffffff814c03f7>] driver_register+0x77/0x170 [ 0.800704] [<ffffffff81cfcc31>] ? agp_intel_init+0x2c/0x2c [ 0.800714] [<ffffffff81cfcd67>] ? drm_core_init+0x136/0x136 [ 0.800725] [<ffffffff81379d1b>] __pci_register_driver+0x4b/0x50 [ 0.800736] [<ffffffff8141e015>] drm_pci_init+0x115/0x130 [ 0.800747] [<ffffffff81cfcd67>] ? drm_core_init+0x136/0x136 [ 0.800757] [<ffffffff81cfcd8f>] emgd_init+0x28/0x2a [ 0.800769] [<ffffffff810002f2>] do_one_initcall+0x122/0x170 [ 0.800781] [<ffffffff81cd6cb6>] kernel_init_freeable+0x139/0x1c3 [ 0.800792] [<ffffffff81cd65b0>] ? do_early_param+0x8d/0x8d [ 0.800802] [<ffffffff81777290>] ? rest_init+0x80/0x80 [ 0.800812] [<ffffffff8177729e>] kernel_init+0xe/0xf0 [ 0.800823] [<ffffffff817953dc>] ret_from_fork+0x7c/0xb0 [ 0.800833] [<ffffffff81777290>] ? rest_init+0x80/0x80 [ 0.800852] ---[ end trace e7227173c35c6757 ]--- [ 0.972745] edid_parse_cea ERROR: Unknown Tag Code! : 7 [ 0.972757] edid_parse_cea ERROR: Unknown Tag Code! : 0 [ 0.972766] edid_parse_cea ERROR: Unknown Tag Code! : 0 [ 0.972794] hdmi_open ERROR: Unsupported port number for internal HDMI [ 0.972805] hdmi_open ERROR: Unsupported port number for internal HDMI [ 0.972816] hdmi_open ERROR: Unsupported port number for internal HDMI [ 0.972826] hdmi_open ERROR: Unsupported port number for internal HDMI [ 0.973644] i2c_aux_read_regs_vlv ERROR: AUX channel failed to write start.
Created attachment 1660 [details] the dmesg log add the dmesg log
We can reproduce the issue and assign it to Nuhairi to investigate.
Any updates on this bug?
Created attachment 1688 [details] a fix patch to this bug Hi, I attached a fix patch to this bug, please review it.
Hi, I found the golden release still has the same problem. Any progress on this bug? Fupan
EMGD does not have any future release for Yocto Bay Trail (E3800). Please contact your Intel representative (PAE) if you need the bug fix. Another option is to use newer version of Yocto BSP that come with different (open source) graphic driver.