Generated logs on Link after force reboot.

Deleted: log-042916-120845.tar.gz 1.4 MB

log-042916-120845.tar.gz 1.4 MB Download

Reproduced same issue on lumpy 7978.66.0 , 50.0.2661.91 as well. 

Removing beta blocker label.

The issue is reported as consistent and device is not functional after repro steps. Bringing back Beta blocker label.

Lots of kernel output in messages log.

Kernel warnings observed in messages log, like:

2016-04-29T12:05:52.660487-07:00 WARNING kernel: [    0.136308] ------------[ cut here ]------------
2016-04-29T12:05:52.660488-07:00 WARNING kernel: [    0.136314] WARNING: at /mnt/host/source/src/third_party/kernel/v3.8/arch/x86/mm/ioremap.c:171 __ioremap_caller+0x2cf/0x314()
2016-04-29T12:05:52.660489-07:00 WARNING kernel: [    0.136316] Hardware name: Link
2016-04-29T12:05:52.660489-07:00 INFO kernel: [    0.136317] Info: mapping multiple BARs. Your kernel is fine.
2016-04-29T12:05:52.660491-07:00 NOTICE kernel: [    0.136319] Modules linked in:
2016-04-29T12:05:52.660492-07:00 NOTICE kernel: [    0.136323] Pid: 1, comm: swapper/0 Not tainted 3.8.11 #1
2016-04-29T12:05:52.660493-07:00 NOTICE kernel: [    0.136325] Call Trace:
2016-04-29T12:05:52.660495-07:00 NOTICE kernel: [    0.136331]  [<ffffffffb1a33173>] warn_slowpath_fmt+0x65/0x90
2016-04-29T12:05:52.660496-07:00 NOTICE kernel: [    0.136335]  [<ffffffffb1a29cf0>] __ioremap_caller+0x2cf/0x314
2016-04-29T12:05:52.660497-07:00 NOTICE kernel: [    0.136338]  [<ffffffffb1a29d4c>] ioremap_nocache+0x17/0x19
2016-04-29T12:05:52.660498-07:00 NOTICE kernel: [    0.136342]  [<ffffffffb1a16707>] snb_uncore_imc_init_box+0x7c/0xb1
2016-04-29T12:05:52.660499-07:00 NOTICE kernel: [    0.136346]  [<ffffffffb1a15055>] uncore_box_init+0x2c/0x2e
2016-04-29T12:05:52.660501-07:00 NOTICE kernel: [    0.136348]  [<ffffffffb1a15227>] uncore_pci_probe+0x100/0x156
2016-04-29T12:05:52.660502-07:00 NOTICE kernel: [    0.136353]  [<ffffffffb1c00def>] pci_device_probe+0x6e/0xb0
2016-04-29T12:05:52.660503-07:00 NOTICE kernel: [    0.136357]  [<ffffffffb1ceb625>] driver_probe_device+0xa2/0x1e3
2016-04-29T12:05:52.660504-07:00 NOTICE kernel: [    0.136360]  [<ffffffffb1ceb800>] __driver_attach+0x5d/0x7f
2016-04-29T12:05:52.660505-07:00 NOTICE kernel: [    0.136363]  [<ffffffffb1ceb7a3>] ? __device_attach+0x3d/0x3d
2016-04-29T12:05:52.660506-07:00 NOTICE kernel: [    0.136367]  [<ffffffffb1cea7ea>] bus_for_each_dev+0x89/0xac
2016-04-29T12:05:52.660507-07:00 NOTICE kernel: [    0.136370]  [<ffffffffb1ceb173>] driver_attach+0x1e/0x20
2016-04-29T12:05:52.660510-07:00 NOTICE kernel: [    0.136373]  [<ffffffffb1ceadbb>] bus_add_driver+0x114/0x211
2016-04-29T12:05:52.660511-07:00 NOTICE kernel: [    0.136377]  [<ffffffffb22daee6>] ? uncore_cpu_setup+0x13/0x13
2016-04-29T12:05:52.660512-07:00 NOTICE kernel: [    0.136381]  [<ffffffffb1cebd1c>] driver_register+0x8c/0xfb
2016-04-29T12:05:52.660513-07:00 NOTICE kernel: [    0.136384]  [<ffffffffb22daee6>] ? uncore_cpu_setup+0x13/0x13
2016-04-29T12:05:52.660514-07:00 NOTICE kernel: [    0.136387]  [<ffffffffb1c00513>] __pci_register_driver+0x60/0x63
2016-04-29T12:05:52.660515-07:00 NOTICE kernel: [    0.136390]  [<ffffffffb22dafa5>] intel_uncore_init+0xbf/0x305
2016-04-29T12:05:52.660516-07:00 NOTICE kernel: [    0.136394]  [<ffffffffb22daee6>] ? uncore_cpu_setup+0x13/0x13
2016-04-29T12:05:52.660517-07:00 NOTICE kernel: [    0.136397]  [<ffffffffb1a0023c>] do_one_initcall+0x7f/0x137
2016-04-29T12:05:52.660520-07:00 NOTICE kernel: [    0.136400]  [<ffffffffb22d3c49>] kernel_init_freeable+0x112/0x190
2016-04-29T12:05:52.660521-07:00 NOTICE kernel: [    0.136404]  [<ffffffffb1eb198b>] ? rest_init+0x6f/0x6f
2016-04-29T12:05:52.660522-07:00 NOTICE kernel: [    0.136406]  [<ffffffffb1eb1999>] kernel_init+0xe/0xd6
2016-04-29T12:05:52.660558-07:00 NOTICE kernel: [    0.136411]  [<ffffffffb1ec299c>] ret_from_fork+0x7c/0xb0
2016-04-29T12:05:52.660559-07:00 NOTICE kernel: [    0.136413]  [<ffffffffb1eb198b>] ? rest_init+0x6f/0x6f
2016-04-29T12:05:52.660560-07:00 WARNING kernel: [    0.136419] ---[ end trace 29e11b9a9db8d3fe ]---

Dominik, can you take a look at this? I am wondering if this is related to some of the recent frecon changes?

In general I am not sure we want this to be a beta blocker, since VT2 is a dev mode only feature, so this should not impact normal users, lets punt it to stable. 

I set the blocker label based on the consistency, and the fact dev mode with beta channel is much popular internally. (Did not read c#3) I think it should still be a blocker - as you put as RBS. Thanks much.

It is most likely the same stuff as  crbug.com/608024 . It should be fixed in ToT.
The kernel message has nothing to do with it.

Sweet, then we should be good with the R51 today.

This should be fixed in R51 and in ToT because it looks the same as  crbug.com/608024 
I also cannot reproduce it now on ToT.
Please reopen if this is not the case.

If ketakid@ wants it fixed in R50 she can commit 3 patches starting from here https://chromium-review.googlesource.com/#/c/342100/

verified in ChromeOS build 8172.45.0, 51.0.2704.64

[Auto-generated comment by a script] We noticed that this issue is targeted for M-51; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-51 label, otherwise remove Merge-TBD label. Thanks.

[Bulk edit]

Our blockerbot script was offline; it was recently brought back online, and thus labeled many old issues (including this one) erroneously.  Removing Merge-TBD label since all milestones for this issue are already completed; no further work should be done.