[lkml]   [2016]   [May]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [i2c: dev] d6760b14d4: BUG: KASAN: slab-out-of-bounds in of_device_uevent at addr ffff8800091b4c49
On Sat, May 28, 2016 at 09:32:17AM +0200, Wolfram Sang wrote:
> > There will be simple boot tests quickly after the compile tests.
> > However boot tests typically need more time to be detected, bisected
> > and especially manual checked. We are yet to automate more boot error
> > reports.
> Thanks for the heads up. Could there be success mails for boot tests,
> too?

That may be too noisy to be useful. Boot errors may not be well
reproducible, may take different forms, and the base trees are
typically not clean -- even mainline tree has regular errors, for
example, here are the runtime error ids in kernel v4.6 with kconfig

boot_successes: 1470
boot_failures: 154
BUG:sleeping_function_called_from_invalid_context_at_kernel/irq/manage.c: 102
WARNING:at_drivers/gpu/drm/i915/intel_display.c:#intel_modeset_init[i915]: 4
drm:fw_domains_get[i915]]: 57
drm:__gen6_gt_wait_for_thread_c0[i915]]: 57
BUG:kernel_test_crashed: 4
invoked_oom-killer:gfp_mask=0x: 22
Mem-Info: 22
Kernel_panic-not_syncing:Out_of_memory_and_no_killable_processes: 18
invalid_opcode:#[##]SMP: 3
RIP:ftrace_stub: 16
Kernel_panic-not_syncing:Fatal_exception: 16
BUG:unable_to_handle_kernel: 13
Oops: 13
Out_of_memory:Kill_process: 4

However if you are still interested, we can try composing auto runtime
test report emails.


 \ /
  Last update: 2016-05-28 12:41    [W:0.032 / U:0.064 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site