From: Fengguang Wu <fengguang.wu@intel.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Erico Nunes <erico.nunes@datacom.ind.br>, LKP <lkp@01.org>,
linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org,
Ye Xiaolong <xiaolong.ye@intel.com>
Subject: Re: [i2c: dev] d6760b14d4: BUG: KASAN: slab-out-of-bounds in of_device_uevent at addr ffff8800091b4c49
Date: Sat, 28 May 2016 18:14:08 +0800 [thread overview]
Message-ID: <20160528101408.GA4346@wfg-t540p.sh.intel.com> (raw)
In-Reply-To: <20160528073217.GB1714@katana>
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
x86_64-rhel:
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.
Thanks,
Fengguang
prev parent reply other threads:[~2016-05-28 10:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-28 6:30 [i2c: dev] d6760b14d4: BUG: KASAN: slab-out-of-bounds in of_device_uevent at addr ffff8800091b4c49 kernel test robot
2016-05-28 7:12 ` Wolfram Sang
2016-05-28 7:24 ` Fengguang Wu
2016-05-28 7:32 ` Wolfram Sang
2016-05-28 10:14 ` Fengguang Wu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160528101408.GA4346@wfg-t540p.sh.intel.com \
--to=fengguang.wu@intel.com \
--cc=erico.nunes@datacom.ind.br \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=wsa@the-dreams.de \
--cc=xiaolong.ye@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox