From: Greg KH <gregkh@suse.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: Yinghai Lu <yhlu.kernel@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: threshold_init_device/kobject_uevent_env oops
Date: Fri, 25 Jan 2008 14:47:11 -0800 [thread overview]
Message-ID: <20080125224711.GA6323@suse.de> (raw)
In-Reply-To: <20080125223556.GB24708@elte.hu>
On Fri, Jan 25, 2008 at 11:35:56PM +0100, Ingo Molnar wrote:
>
> * Greg KH <gregkh@suse.de> 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
Ok, those are pretty much just search/and/replace type changes, but I
have been running x86-64 boxes with these changes in place.
That's why I'm interested if Linus's tree right now shows this problem,
and if I can get a .config of the offending kernel to try to reproduce
it and fix it myself.
thanks,
greg k-h
next prev parent reply other threads:[~2008-01-25 22:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-25 21:05 threshold_init_device/kobject_uevent_env oops Yinghai Lu
2008-01-25 22:15 ` Greg KH
2008-01-25 22:35 ` Ingo Molnar
2008-01-25 22:47 ` Greg KH [this message]
2008-01-25 22:50 ` Greg KH
2008-01-26 6:04 ` Yinghai Lu
2008-01-26 6:14 ` Greg KH
2008-01-26 7:08 ` Yinghai Lu
2008-01-26 7:24 ` Greg KH
2008-01-26 7:35 ` Greg KH
2008-01-26 21:26 ` Yinghai Lu
2008-01-25 23:12 ` Yinghai Lu
2008-01-25 23:08 ` Greg KH
2008-01-25 23:20 ` Yinghai Lu
2008-01-26 6:22 ` Greg KH
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=20080125224711.GA6323@suse.de \
--to=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.org \
--cc=yhlu.kernel@gmail.com \
/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.