From: Corey Minyard <cminyard@mvista.com>
To: lkp@lists.01.org
Subject: Re: [ipmi] BUG: key ffff880fcfc51ed0 not in .data!
Date: Tue, 16 Dec 2014 07:08:47 -0600 [thread overview]
Message-ID: <54902EDF.8070605@mvista.com> (raw)
In-Reply-To: <CAADnVQJ8MT9mUbp2cyMOd-TUZh_fp+y35CGBiw+GEcbCRb+GrA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1242 bytes --]
On 12/15/2014 08:53 PM, Alexei Starovoitov wrote:
> On Fri, Dec 12, 2014 at 8:04 PM, Corey Minyard <cminyard@mvista.com> 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 <cminyard@mvista.com>
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
WARNING: multiple messages have this Message-ID (diff)
From: Corey Minyard <cminyard@mvista.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Huang Ying <ying.huang@intel.com>,
LKML <linux-kernel@vger.kernel.org>, LKP ML <lkp@01.org>
Subject: Re: [LKP] [ipmi] BUG: key ffff880fcfc51ed0 not in .data!
Date: Tue, 16 Dec 2014 07:08:47 -0600 [thread overview]
Message-ID: <54902EDF.8070605@mvista.com> (raw)
In-Reply-To: <CAADnVQJ8MT9mUbp2cyMOd-TUZh_fp+y35CGBiw+GEcbCRb+GrA@mail.gmail.com>
On 12/15/2014 08:53 PM, Alexei Starovoitov wrote:
> On Fri, Dec 12, 2014 at 8:04 PM, Corey Minyard <cminyard@mvista.com> 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 <cminyard@mvista.com>
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
next prev parent reply other threads:[~2014-12-16 13:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 3:20 [ipmi] BUG: key ffff880fcfc51ed0 not in .data! Huang Ying
2014-12-13 4:04 ` Corey Minyard
2014-12-13 4:04 ` [LKP] " Corey Minyard
2014-12-16 2:53 ` Alexei Starovoitov
2014-12-16 2:53 ` [LKP] " Alexei Starovoitov
2014-12-16 13:08 ` Corey Minyard [this message]
2014-12-16 13:08 ` Corey Minyard
-- strict thread matches above, loose matches on Subject: below --
2014-12-17 1:05 Alexei Starovoitov
2014-12-17 13:03 ` Corey Minyard
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=54902EDF.8070605@mvista.com \
--to=cminyard@mvista.com \
--cc=lkp@lists.01.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.