From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760598AbYAYWw2 (ORCPT ); Fri, 25 Jan 2008 17:52:28 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758156AbYAYWwI (ORCPT ); Fri, 25 Jan 2008 17:52:08 -0500 Received: from ns1.suse.de ([195.135.220.2]:51894 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759040AbYAYWwF (ORCPT ); Fri, 25 Jan 2008 17:52:05 -0500 Date: Fri, 25 Jan 2008 14:50:36 -0800 From: Greg KH To: Ingo Molnar Cc: Yinghai Lu , Linux Kernel Mailing List , Linus Torvalds Subject: Re: threshold_init_device/kobject_uevent_env oops Message-ID: <20080125225036.GB6323@suse.de> References: <86802c440801251305u21517078y12ff68ef3015aaae@mail.gmail.com> <20080125221548.GA15172@suse.de> <20080125223556.GB24708@elte.hu> <20080125224711.GA6323@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080125224711.GA6323@suse.de> User-Agent: Mutt/1.5.16 (2007-06-09) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jan 25, 2008 at 02:47:11PM -0800, Greg KH wrote: > On Fri, Jan 25, 2008 at 11:35:56PM +0100, Ingo Molnar wrote: > > > > * Greg KH 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: [] 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. Oh wait, I do see a change. We are now (finally) emitting a kobject uevent for these devices, which somehow the code can't handle properly. Let me go poke this some more, unfortunatly I don't have any AMD 64 boxes here anymore, only Intel based processors, so I can't run this module... thanks, greg k-h