From: Huang Ying <ying.huang@intel.com>
To: Thierry Reding <treding@nvidia.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>, LKP ML <lkp@01.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [LKP] [drm/fb] 6cadd306033:
Date: Tue, 23 Dec 2014 13:42:02 +0800 [thread overview]
Message-ID: <1419313322.26403.57.camel@intel.com> (raw)
In-Reply-To: <1419313251.26403.56.camel@intel.com>
FYI, similar information for 4a91ebc4ec70e83a2fbca622653da22bf8afda7b
too.
Best Regards,
Huang, Ying
On Tue, 2014-12-23 at 13:40 +0800, Huang Ying wrote:
> FYI, we noticed the below changes on
>
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> commit 6cadd306033e70b4edb136815807060e168cac67 ("drm/fb-helper: Propagate errors from initial config failure")
>
>
> testbox/testcase/testparams: vm-kbuild-yocto-ia32/boot/1
>
> drm-intel/topic/ 6cadd306033e70b4edb1368158
> ---------------- --------------------------
> fail:runs %reproduction fail:runs
> | | |
> :10 100% 10:10 kmsg.drm:cirrus_modeset_init]*ERROR*cirrus_fbdev_init_failed
> :10 100% 10:10 kmsg.cirrus#:#:#:Fatal_error_during_modeset_init
> 1:10 -10% :10 kmsg.Initramfs_unpacking_failed:junk_in_compressed_archive
> 1:10 -10% :10 kmsg.BUG:kernel_boot_hang
> 1:10 -10% :10 dmesg.Initramfs_unpacking_failed
> 1:10 -10% :10 dmesg.BUG:kernel_boot_hang
> :2 50% 1:2 kmsg.BUG:kernel_test_crashed
> :2 100% 2:2 kmsg.APIC_calibration_not_consistent_with_PM-Timer:#ms_instead_of#ms
> :2 50% 1:2 kmsg.i6300esb:Unexpected_close,not_stopping_watchdog
> :2 50% 1:2 dmesg.BUG:kernel_test_crashed
>
> vm-kbuild-yocto-ia32: qemu-system-x86_64 -enable-kvm -cpu Westmere
> Memory: 320M
>
>
> To reproduce:
>
> apt-get install ruby ruby-oj
> git clone git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
> cd lkp-tests
> bin/setup-local job.yaml # the job file attached in this email
> bin/run-local job.yaml
>
>
> Disclaimer:
> Results have been estimated based on internal Intel analysis and are provided
> for informational purposes only. Any difference in system hardware or software
> design or configuration may affect actual performance.
>
>
> Thanks,
> Huang, Ying
>
> _______________________________________________
> LKP mailing list
> LKP@linux.intel.com
> _______________________________________________ LKP mailing list LKP@lists.01.org https://lists.01.org/mailman/listinfo/lkp
prev parent reply other threads:[~2014-12-23 5:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-23 5:40 [LKP] [drm/fb] 6cadd306033: Huang Ying
2014-12-23 5:42 ` Huang Ying [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=1419313322.26403.57.camel@intel.com \
--to=ying.huang@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=treding@nvidia.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