* Re: [LKP] [ipmi] BUG: key ffff880fcfc51ed0 not in .data!
[not found] <1418354422.5745.101.camel@intel.com>
@ 2014-12-13 4:04 ` Corey Minyard
2014-12-16 2:53 ` Alexei Starovoitov
0 siblings, 1 reply; 5+ messages in thread
From: Corey Minyard @ 2014-12-13 4:04 UTC (permalink / raw)
To: Huang Ying; +Cc: LKML, LKP ML
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.
Thanks again,
-corey
>
>
> +------------------------------------------------------------+------------+------------+
> | | 8425c1276b | 2ed09fc090 |
> +------------------------------------------------------------+------------+------------+
> | boot_successes | 9 | 6 |
> | boot_failures | 1 | 23 |
> | Out_of_memory:Kill_process | 1 | 3 |
> | BUG:key#not_in.data | 0 | 19 |
> | WARNING:at_kernel/locking/lockdep.c:#lockdep_init_map() | 0 | 10 |
> | BUG:unable_to_handle_kernel | 0 | 19 |
> | Oops | 0 | 19 |
> | RIP:kernfs_name_hash | 0 | 19 |
> | Kernel_panic-not_syncing:Fatal_exception | 0 | 19 |
> | backtrace:lockdep_init_map | 0 | 10 |
> | backtrace:warn_slowpath_fmt | 0 | 10 |
> | backtrace:ipmi_register_smi | 0 | 19 |
> | backtrace:try_smi_init | 0 | 19 |
> | backtrace:init_ipmi_si | 0 | 19 |
> | backtrace:kernel_init_freeable | 0 | 19 |
> | WARNING:at_kernel/locking/lockdep.c:#lockdep_trace_alloc() | 0 | 9 |
> | backtrace:__get_free_pages | 0 | 9 |
> | backtrace:init_espfix_ap | 0 | 9 |
> | BUG:kernel_boot_hang | 0 | 1 |
> +------------------------------------------------------------+------------+------------+
>
>
> [ 33.605171] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
> [ 33.605172] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
> [ 33.605176] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
> [ 33.775374] BUG: key ffff880fcfc51ed0 not in .data!
> [ 33.780822] ------------[ cut here ]------------
> [ 33.785982] WARNING: CPU: 18 PID: 1 at kernel/locking/lockdep.c:2991 lockdep_init_map+0x116/0x141()
> [ 33.798116] DEBUG_LOCKS_WARN_ON(1)
> [ 33.801719] Modules linked in:
> [ 33.805346] CPU: 18 PID: 1 Comm: swapper/0 Not tainted 3.18.0-next-20141208 #4
> [ 33.813408] Hardware name: Intel Corporation S2600WP/S2600WP, BIOS SE5C600.86B.02.02.0002.122320131210 12/23/2013
> [ 33.824862] 0000000000000009 ffff88080f6dbbb8 ffffffff82d71b35 00000000001d03f0
> [ 33.833161] ffff88080f6dbc08 ffff88080f6dbbf8 ffffffff810c8f39 ffff880fcfc51ed0
> [ 33.841445] ffffffff810ff31d ffff880fcfc64f50 ffff880fcfc51ed0 0000000000000000
> [ 33.849739] Call Trace:
> [ 33.852467] [<ffffffff82d71b35>] dump_stack+0x4c/0x65
> [ 33.858204] [<ffffffff810c8f39>] warn_slowpath_common+0xa1/0xbb
> [ 33.864910] [<ffffffff810ff31d>] ? lockdep_init_map+0x116/0x141
> [ 33.871615] [<ffffffff810c8f99>] warn_slowpath_fmt+0x46/0x48
> [ 33.878030] [<ffffffff810ff31d>] lockdep_init_map+0x116/0x141
> [ 33.884544] [<ffffffff81242e4a>] __kernfs_create_file+0x8c/0xdb
> [ 33.891249] [<ffffffff81243641>] sysfs_add_file_mode_ns+0xd6/0x17f
> [ 33.898245] [<ffffffff81243716>] sysfs_create_file_ns+0x2c/0x2e
> [ 33.904953] [<ffffffff81b291eb>] device_create_file+0x44/0x89
> [ 33.911466] [<ffffffff8182041d>] ipmi_register_smi+0x705/0x92d
> [ 33.918079] [<ffffffff810f8df0>] ? signal_pending_state+0x31/0x31
> [ 33.924981] [<ffffffff818227b7>] try_smi_init+0x58b/0x723
> [ 33.931105] [<ffffffff81824b86>] init_ipmi_si+0x7d7/0x983
> [ 33.937229] [<ffffffff818243af>] ? cleanup_ipmi_si+0xab/0xab
> [ 33.943647] [<ffffffff8100216c>] do_one_initcall+0xed/0x17b
> [ 33.949967] [<ffffffff843fb11c>] kernel_init_freeable+0x1ec/0x279
> [ 33.956869] [<ffffffff82d60b4a>] ? rest_init+0xca/0xca
> [ 33.962703] [<ffffffff82d60b58>] kernel_init+0xe/0xdf
> [ 33.968440] [<ffffffff82d9607c>] ret_from_fork+0x7c/0xb0
> [ 33.974467] [<ffffffff82d60b4a>] ? rest_init+0xca/0xca
> [ 33.980303] ---[ end trace 831fe511de8a7740 ]---
> [ 33.985468] BUG: key ffff880fcfc51ea0 not in .data!
>
>
>
> Thanks,
> Huang, Ying
>
>
>
> _______________________________________________
> LKP mailing list
> LKP@linux.intel.com
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [LKP] [ipmi] BUG: key ffff880fcfc51ed0 not in .data!
2014-12-13 4:04 ` [LKP] [ipmi] BUG: key ffff880fcfc51ed0 not in .data! Corey Minyard
@ 2014-12-16 2:53 ` Alexei Starovoitov
2014-12-16 13:08 ` Corey Minyard
0 siblings, 1 reply; 5+ messages in thread
From: Alexei Starovoitov @ 2014-12-16 2:53 UTC (permalink / raw)
To: Corey Minyard; +Cc: Huang Ying, LKML, LKP ML
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()
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [LKP] [ipmi] BUG: key ffff880fcfc51ed0 not in .data!
2014-12-16 2:53 ` Alexei Starovoitov
@ 2014-12-16 13:08 ` Corey Minyard
0 siblings, 0 replies; 5+ messages in thread
From: Corey Minyard @ 2014-12-16 13:08 UTC (permalink / raw)
To: Alexei Starovoitov; +Cc: Huang Ying, LKML, LKP ML
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [LKP] [ipmi] BUG: key ffff880fcfc51ed0 not in .data!
2014-12-17 1:05 Alexei Starovoitov
@ 2014-12-17 13:03 ` Corey Minyard
0 siblings, 0 replies; 5+ messages in thread
From: Corey Minyard @ 2014-12-17 13:03 UTC (permalink / raw)
To: Alexei Starovoitov, Corey Minyard; +Cc: Huang Ying, LKML, LKP ML, Huang Ying
On 12/16/2014 07:05 PM, Alexei Starovoitov wrote:
> On Tue, Dec 16, 2014 at 5:08 AM, Corey Minyard <cminyard@mvista.com> wrote:
>> 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.
> thanks. cleared the warning for me as well:
> Tested-by: Alexei Starovoitov <ast@plumgrid.com>
>
> Are you planning to send a pull request
> before the merge window is over or for rc2 ?
Yes, I believe I will. I was planning to wait until it was in
linux-next for a little while, but a "Tested-by" from you and Huang Ying
would give me more confidence :).
-corey
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [LKP] [ipmi] BUG: key ffff880fcfc51ed0 not in .data!
@ 2014-12-17 1:05 Alexei Starovoitov
2014-12-17 13:03 ` Corey Minyard
0 siblings, 1 reply; 5+ messages in thread
From: Alexei Starovoitov @ 2014-12-17 1:05 UTC (permalink / raw)
To: Corey Minyard; +Cc: Huang Ying, LKML, LKP ML
On Tue, Dec 16, 2014 at 5:08 AM, Corey Minyard <cminyard@mvista.com> wrote:
> 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.
thanks. cleared the warning for me as well:
Tested-by: Alexei Starovoitov <ast@plumgrid.com>
Are you planning to send a pull request
before the merge window is over or for rc2 ?
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2014-12-17 13:04 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <1418354422.5745.101.camel@intel.com>
2014-12-13 4:04 ` [LKP] [ipmi] BUG: key ffff880fcfc51ed0 not in .data! Corey Minyard
2014-12-16 2:53 ` Alexei Starovoitov
2014-12-16 13:08 ` Corey Minyard
2014-12-17 1:05 Alexei Starovoitov
2014-12-17 13:03 ` Corey Minyard
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).