From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754310Ab0CGPir (ORCPT ); Sun, 7 Mar 2010 10:38:47 -0500 Received: from mail-pz0-f194.google.com ([209.85.222.194]:53434 "EHLO mail-pz0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753617Ab0CGPip (ORCPT ); Sun, 7 Mar 2010 10:38:45 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:content-transfer-encoding :in-reply-to:user-agent; b=F509J76SPQe5Xl9aImez/W/cNOIpqx59xl8R1eSgATBuJ76zSo7IR7Rclc4NbvqvMt a1TsXNCDOHXT6Ws1XoBvM/ACJaz1+Nbcd2sOLM/bSgHNE7NJpcRUnXnXF8AnPFmDu1eP lDmaJvJsYspw6840BexDsNIqqc0ZyuSVGSP0c= Date: Sun, 7 Mar 2010 23:41:39 +0800 From: =?utf-8?Q?Am=C3=A9rico?= Wang To: M G Berberich Cc: =?utf-8?Q?Am=C3=A9rico?= Wang , linux-kernel@vger.kernel.org, Linux Kernel Network Developers , Greg Kroah-Hartman Subject: Re: 2.6.33 dies on modprobe Message-ID: <20100307154139.GA6227@hack> References: <20100303230438.GA3363@invalid> <20100304153042.GA4614@hack> <20100304203803.GA3267@invalid> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20100304203803.GA3267@invalid> User-Agent: Mutt/1.5.19 (2009-01-05) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Mar 04, 2010 at 09:38:03PM +0100, M G Berberich wrote: >Am Donnerstag, den 04. März schrieb Américo Wang: >> On Thu, Mar 04, 2010 at 12:04:38AM +0100, M G Berberich wrote: >> >Am Mittwoch, den 03. März schrieb Américo Wang: >> >> On Wed, Mar 3, 2010 at 5:08 PM, Américo Wang wrote: >> >> > On Wed, Mar 3, 2010 at 4:58 PM, Américo Wang wrote: >> >> >> Ok, below is my patch, I am not sure it could fix the BUG for you, >> >> >> but it could fix the WARNING. But perhaps they are related. >> >> >> >> >> >> Please give it a try. >> >> >> >> >> > >> >> > Oops! Ignore the patch, it should not be correct, I will send a >> >> > correct version soon. >> >> > Sorry. >> >> > >> >> >> >> Here we go: >> > >> >Seems to fix the warning, but not the modprobe-Oops. >> > >> >> Thanks much for your testing! >> >> Could you please try to turn on DEBUG_KOBJECT and boot your kernel >> with "initcall_debug"? And then show us your dmesg. > >If I'm doing this (enabled CONFIG_DEBUG_KERNEL and >CONFIG_DEBUG_KOBJECT), the kernel dies immediately - no output. > Ouch! CONFIG_DEBUG_KOBJECT will only enable some printk's, so I think probably it's CONFIG_DEBUG_KERNEL which breaks your booting. Could you please provide your .config? Thanks!