From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751859AbaLPNIx (ORCPT ); Tue, 16 Dec 2014 08:08:53 -0500 Received: from mail-qc0-f175.google.com ([209.85.216.175]:59533 "EHLO mail-qc0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750832AbaLPNIv (ORCPT ); Tue, 16 Dec 2014 08:08:51 -0500 Message-ID: <54902EDF.8070605@mvista.com> Date: Tue, 16 Dec 2014 07:08:47 -0600 From: Corey Minyard User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Alexei Starovoitov CC: Huang Ying , LKML , LKP ML Subject: Re: [LKP] [ipmi] BUG: key ffff880fcfc51ed0 not in .data! References: <1418354422.5745.101.camel@intel.com> <548BBAB2.7010003@mvista.com> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 12/15/2014 08:53 PM, Alexei Starovoitov wrote: > On Fri, Dec 12, 2014 at 8:04 PM, Corey Minyard wrote: >> On 12/11/2014 09:20 PM, 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 2ed09fc090fc0488e2ab27604a141679fe2ef610 ("ipmi: clean up the device handling for the bmc device") >> Thanks. The surprising thing is that this didn't give an error before. >> >> But this should be fixed in linux-next the next time. > when specifically? Is there a fix already? > Quite annoying to see this every boot: > [ 4.778018] BUG: key ffff88046458fe20 not in .data! > [ 4.778021] ------------[ cut here ]------------ > [ 4.778061] WARNING: CPU: 1 PID: 1428 at > ../kernel/locking/lockdep.c:2991 lockdep_init_map+0x4cd/0x500() Yes, should be fixed by: commit 693726299ba87a6e267993806bc1320a266e5c5e Author: Corey Minyard Date: Fri Dec 12 19:06:07 2014 -0600 ipmi: Finish cleanup of BMC attributes which should be in linux-next now. I was able to reproduce and verify that this fixed it. I've verified that the branch is correct in the repository. -corey