Re: threshold_init_device/kobject_uevent_env oops

[Ingo Molnar]

* Greg KH <gregkh@xxxxxxx> wrote:

> On Fri, Jan 25, 2008 at 01:05:40PM -0800, Yinghai Lu wrote:
> > current linus tree + x86.git
> > 
> > got
> > 
> > Calling initcall 0xffffffff80b93d98: threshold_init_device+0x0/0x3f()
> > BUG: unable to handle kernel NULL pointer dereference at 0000000000000040
> > IP: [<ffffffff80458e20>] kobject_uevent_env+0x2a/0x3d9
> 
> Does this happen on just Linus's tree?
> 
> Can you send me a .config file for this?
> 
> What is threshold_init()?  Is it something new in the x86.git tree?

no. A quick grep shows that it is in a file that _your_ changes in 
Linus' latest have touched:

  arch/x86/kernel/cpu/mcheck/mce_amd_64.c

via:

 Author: Greg Kroah-Hartman <gregkh@xxxxxxx>
 Date:   Thu Dec 20 08:13:05 2007 -0800

     Kobject: convert arch/* from kobject_unregister() to kobject_put()

 Author: Greg Kroah-Hartman <gregkh@xxxxxxx>
 Date:   Wed Dec 19 09:23:20 2007 -0800

     Kobject: change arch/x86/kernel/cpu/mcheck/mce_amd_64.c to use kobject_init_ 

 commit a521cf209c6e7042f85b2c5b16da3ffa8004fb7b
 Author: Greg Kroah-Hartman <gregkh@xxxxxxx>
 Date:   Wed Dec 19 09:23:20 2007 -0800

     Kobject: change arch/x86/kernel/cpu/mcheck/mce_amd_64.c to use kobject_creat

x86.git changed nothing to cause a crash in kobject_uevent_env(), and 
nothing has changed anything near this code anyway.

We havent had a runtime (non-boot related) crash in x86.git for quite 
some time. It's rock solid and dependable, and the only significant 
change today were your upstream kobject commits.

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/