From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754864Ab0CDP1t (ORCPT ); Thu, 4 Mar 2010 10:27:49 -0500 Received: from mail-ew0-f220.google.com ([209.85.219.220]:64952 "EHLO mail-ew0-f220.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754708Ab0CDP1r (ORCPT ); Thu, 4 Mar 2010 10:27:47 -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=k0mnN40GTgbXg4zeQj78g0TJxWZdsG5I8QJ9f7MerVY0dkt1VaAZCI1sz0GocgXfKs G+97IGVqsE/e/ZOa7Z9NCO4XD+iGoGd/nt0GWpUKhAafzFye7i3yNWm/Sbp/2KRkLqHt bLD9u0w6eMu3J9o4r5a+LCrz0Lw86l10vTDqA= Date: Thu, 4 Mar 2010 23:30:42 +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: <20100304153042.GA4614@hack> References: <20100303230438.GA3363@invalid> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20100303230438.GA3363@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 12:04:38AM +0100, M G Berberich wrote: >Hello, > >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. Regards.