Date: Thu, 5 Sep 2013 00:13:38 -0400
From: Dave Jones <davej@redhat.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Greg KH <gregkh@linuxfoundation.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        rmk+kernel@arm.linux.org.uk
Subject: Re: kobject: delayed kobject release: help find buggy drivers
Message-ID: <20130905041338.GA21090@redhat.com>
Mail-Followup-To: Dave Jones <davej@redhat.com>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Greg KH <gregkh@linuxfoundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	rmk+kernel@arm.linux.org.uk
References: <20130903185924.046EE660E91@gitolite.kernel.org>
 <20130903204442.GA22222@redhat.com>
 <20130903205527.GA6358@kroah.com>
 <87zjrt6tz4.fsf@rustcorp.com.au>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <87zjrt6tz4.fsf@rustcorp.com.au>
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 977
Lines: 26

On Wed, Sep 04, 2013 at 02:53:11PM +0930, Rusty Russell wrote:
 
 > >> With this enabled, I get a bunch of scrolling oopses immediately after
 > >> exiting the bootloader. It happens so early I can't even capture them
 > >> over usb-serial, or earlyprintk=dbgp.
 > >> 
 > >> And for whatever reason, the printk path while oopsing ignores boot_delay parameter,
 > >> so I can't even use that.
 > >> 
 > >> any ideas ?
 > >
 > > The first big bug found with this was with the module kobject code, and
 > > a fix for that should be going in through Rusty's tree to Linus for this
 > > merge window (right Rusty?)
 > 
 > Yep, just sent pull request.  The fix was the final commit there...

Crap, that isn't the bug I'm hitting.

	Dave

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