From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751668AbaGaLFe (ORCPT ); Thu, 31 Jul 2014 07:05:34 -0400 Received: from mga14.intel.com ([192.55.52.115]:15436 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750859AbaGaLFc (ORCPT ); Thu, 31 Jul 2014 07:05:32 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.01,771,1400050800"; d="scan'208";a="569901706" Date: Thu, 31 Jul 2014 19:04:50 +0800 From: Fengguang Wu To: Andy Lutomirski Cc: Jet Chen , Su Tao , Yuanhan Liu , LKP , "linux-kernel@vger.kernel.org" , xen-devel@lists.xenproject.org Subject: Re: [x86_64,vsyscall] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b Message-ID: <20140731110450.GC9455@localhost> References: <20140730142923.GR16537@localhost> <20140730153315.GA29233@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jul 30, 2014 at 01:14:06PM -0700, Andy Lutomirski wrote: > On Wed, Jul 30, 2014 at 8:33 AM, Fengguang Wu wrote: > > On Wed, Jul 30, 2014 at 07:58:13AM -0700, Andy Lutomirski wrote: > >> On Wed, Jul 30, 2014 at 7:29 AM, Fengguang Wu wrote: > >> > Greetings, > >> > > >> > 0day kernel testing robot got the below dmesg and the first bad commit is > >> > > >> > git://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git x86/vsyscall > >> > commit 442aba0c6131f0c41dfc5edb6bfb88335556523f > >> > Author: Andy Lutomirski > >> > AuthorDate: Mon Jun 16 18:50:12 2014 -0700 > >> > Commit: Andy Lutomirski > >> > CommitDate: Mon Jun 30 14:32:44 2014 -0700 > >> > >> Was this a merge? > > > > It's not a merge commit. > > Hmm. It looks like that commit is from a version of x86/vsyscall > that's rather out-of-date. Is it possible that the script is testing > an old version of the tree? I haven't touched it in almost a week, I > think. The current luto/x86/vsyscall HEAD commit 1e67c32df4dddf763271c3ace52fdec66877740c has these errors: +-----------------------------------------------------------+---+ | | | +-----------------------------------------------------------+---+ | boot_successes | 1 | | boot_failures | 9 | | general_protection_fault | 3 | | RIP:crypto_ahash_setkey | 3 | | Kernel_panic-not_syncing:Fatal_exception | 8 | | backtrace:cryptomgr_test | 8 | | BUG:unable_to_handle_kernel_paging_request | 5 | | Oops | 5 | | RIP:kzfree | 5 | | Kernel_panic-not_syncing:Attempted_to_kill_init_exitcode= | 1 | | INFO:suspicious_RCU_usage | 1 | +-----------------------------------------------------------+---+ mount: can't read '/proc/mounts': No such file or directory [ 32.915296] init[1]: segfault at ffffffffff600400 ip ffffffffff600400 sp 00007fff994dc878 error 15 [ 32.916078] init[1]: segfault at ffffffffff600400 ip ffffffffff600400 sp 00007fff994dbe78 error 15 [ 32.916925] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b [ 32.916925] [ 32.917698] CPU: 0 PID: 1 Comm: init Not tainted 3.16.0-rc4-00019-g1e67c32 #1 [ 32.918301] 0000000000000000 ffff880000033cc0 ffffffff81ff4e8f ffff880000033d38 [ 32.918944] ffffffff81ff1972 ffff880000000010 ffff880000033d48 ffff880000033ce8 [ 32.919611] ffffffff82c440c0 000000000000000b 8c6318c6318c6320 00000007aa003caf [ 32.920011] Call Trace: [ 32.920011] [] dump_stack+0x19/0x1b [ 32.920011] [] panic+0xcb/0x1fb [ 32.920011] [] do_exit+0x3dd/0x80f [ 32.920011] [] ? local_clock+0x14/0x1d [ 32.920011] [] do_group_exit+0x75/0xb4 [ 32.920011] [] get_signal_to_deliver+0x48a/0x4aa [ 32.920011] [] do_signal+0x43/0x5ba [ 32.920011] [] ? lock_release_holdtime+0x6c/0x77 [ 32.920011] [] ? lock_release_non_nested+0xd0/0x21e [ 32.920011] [] ? sched_clock_cpu+0x4e/0x62 [ 32.920011] [] ? might_fault+0x4f/0x9c [ 32.920011] [] ? trace_hardirqs_off_caller+0x36/0xa5 [ 32.920011] [] ? retint_signal+0x11/0x99 [ 32.920011] [] do_notify_resume+0x24/0x53 [ 32.920011] [] retint_signal+0x4d/0x99 [ 32.920011] Kernel Offset: 0x0 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffff9fffffff) [ 32.920011] drm_kms_helper: panic occurred, switching back to text console [ 32.920011] [ 32.920011] =============================== [ 32.920011] [ INFO: suspicious RCU usage. ] [ 32.920011] 3.16.0-rc4-00019-g1e67c32 #1 Not tainted [ 32.920011] ------------------------------- [ 32.920011] include/linux/rcupdate.h:539 Illegal context switch in RCU read-side critical section! [ 32.920011] [ 32.920011] other info that might help us debug this: [ 32.920011] [ 32.920011] [ 32.920011] rcu_scheduler_active = 1, debug_locks = 0 [ 32.920011] 3 locks held by init/1: [ 32.920011] #0: (panic_lock){....+.}, at: [] panic+0x43/0x1fb [ 32.920011] #1: (rcu_read_lock){......}, at: [] rcu_lock_acquire+0x0/0x23 [ 32.920011] #2: (&dev->mode_config.mutex){+.+.+.}, at: [] drm_fb_helper_panic+0x5d/0xab [ 32.920011] [ 32.920011] stack backtrace: [ 32.920011] CPU: 0 PID: 1 Comm: init Not tainted 3.16.0-rc4-00019-g1e67c32 #1 [ 32.920011] 0000000000000000 ffff8800000339d0 ffffffff81ff4e8f ffff880000033a00 [ 32.920011] ffffffff810b8840 ffffffff82836348 000000000000024a 0000000000000000 [ 32.920011] ffff880010144008 ffff880000033a10 ffffffff810adcff ffff880000033a38 [ 32.920011] Call Trace: [ 32.920011] [] dump_stack+0x19/0x1b [ 32.920011] [] lockdep_rcu_suspicious+0xf6/0xff [ 32.920011] [] rcu_preempt_sleep_check+0x45/0x47 [ 32.920011] [] __might_sleep+0x17/0x19a [ 32.920011] [] mutex_lock_nested+0x2e/0x369 [ 32.920011] [] ? lock_release+0x154/0x185 [ 32.920011] [] ? trace_hardirqs_off+0xd/0xf [ 32.920011] [] _object_find+0x25/0x6c [ 32.920011] [] drm_mode_object_find+0x38/0x53 [ 32.920011] [] cirrus_connector_best_encoder+0x21/0x2f [ 32.920011] [] drm_crtc_helper_set_config+0x38c/0x83c [ 32.920011] [] drm_mode_set_config_internal+0x53/0xca [ 32.920011] [] restore_fbdev_mode+0x91/0xad [ 32.920011] [] drm_fb_helper_panic+0x69/0xab [ 32.920011] [] notifier_call_chain+0x61/0x8b [ 32.920011] [] __atomic_notifier_call_chain+0x7e/0xe6 [ 32.920011] [] atomic_notifier_call_chain+0xf/0x11 [ 32.920011] [] panic+0xf0/0x1fb [ 32.920011] [] do_exit+0x3dd/0x80f [ 32.920011] [] ? local_clock+0x14/0x1d [ 32.920011] [] do_group_exit+0x75/0xb4 [ 32.920011] [] get_signal_to_deliver+0x48a/0x4aa [ 32.920011] [] do_signal+0x43/0x5ba [ 32.920011] [] ? lock_release_holdtime+0x6c/0x77 [ 32.920011] [] ? lock_release_non_nested+0xd0/0x21e [ 32.920011] [] ? sched_clock_cpu+0x4e/0x62 [ 32.920011] [] ? might_fault+0x4f/0x9c [ 32.920011] [] ? trace_hardirqs_off_caller+0x36/0xa5 [ 32.920011] [] ? retint_signal+0x11/0x99 [ 32.920011] [] do_notify_resume+0x24/0x53 [ 32.920011] [] retint_signal+0x4d/0x99 [ 32.920011] Rebooting in 10 seconds.. > > > >> Is there an easy way to see exactly what was tested? > > > > This script may reproduce the error. Note that it's not 100% reproducible. > > It fails with: > > [ 1.214573] VFS: Cannot open root device "ram0" or > unknown-block(0,0): error -6 > [ 1.216567] Please append a correct "root=" boot option; here are > the available partitions: > [ 1.218692] 0b00 1048575 sr0 driver: sr Oops, github needs this link for downloading big files: https://github.com/fengguang/reproduce-kernel-bug/raw/master/initrd/yocto-minimal-i386.cgz Thanks, Fengguang