From: Greg KH <gregkh@linuxfoundation.org>
To: Dave Jones <davej@redhat.com>,
Rusty Russell <rusty@rustcorp.com.au>,
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
Date: Wed, 4 Sep 2013 21:57:45 -0700 [thread overview]
Message-ID: <20130905045745.GA18876@kroah.com> (raw)
In-Reply-To: <20130905041338.GA21090@redhat.com>
On Thu, Sep 05, 2013 at 12:13:38AM -0400, Dave Jones wrote:
> 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.
Any chance to get a oops traceback?
greg k-h
next prev parent reply other threads:[~2013-09-05 4:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130903185924.046EE660E91@gitolite.kernel.org>
2013-09-03 20:44 ` kobject: delayed kobject release: help find buggy drivers Dave Jones
2013-09-03 20:55 ` Greg KH
2013-09-04 5:23 ` Rusty Russell
2013-09-05 4:13 ` Dave Jones
2013-09-05 4:57 ` Greg KH [this message]
2013-09-05 5:00 ` Dave Jones
2013-09-05 5:19 ` Dave Jones
2013-09-05 15:34 ` Greg KH
2013-09-05 15:47 ` Dave Jones
2013-09-05 17:35 ` Russell King - ARM Linux
2013-09-05 18:13 ` Dave Jones
2013-09-05 19:29 ` Dave Jones
2013-09-05 21:11 ` Dave Jones
2013-09-05 21:26 ` Dave Jones
2013-09-05 21:44 ` Russell King - ARM Linux
2013-09-06 1:11 ` Dave Jones
2013-09-06 7:59 ` Russell King - ARM Linux
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=20130905045745.GA18876@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=rusty@rustcorp.com.au \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox