From: Benjamin Gilbert <bgilbert@cs.cmu.edu>
To: Greg KH <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.36-rc1 oopses at boot time in kobject allocation
Date: Fri, 20 Aug 2010 08:48:26 -0400 [thread overview]
Message-ID: <4C6E799A.7060902@cs.cmu.edu> (raw)
In-Reply-To: <20100819203435.GA28508@suse.de>
On 08/19/2010 04:34 PM, Greg KH wrote:
> On Thu, Aug 19, 2010 at 04:22:33PM -0400, Benjamin Gilbert wrote:
>> 2.6.36-rc1 and 2.6.36-rc1-127-g763008c fail to boot for me:
>
> Can you run 'git bisect' to try to track this down?
commit f8a4bd3456b988fc73b2c291b9e01b434c8fa940
Author: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Date: Fri Jun 4 00:54:43 2010 -0700
firmware loader: embed device into firmware_priv structure
Both these structures have the same lifetime rules so instead of allocating
and managing them separately embed struct device into struct firmware_priv.
Also make sure to delete sysfs attributes ourselves instead of expecting
sysfs to clean up our mess.
Signed-off-by: Dmitry Torokhov <dtor@mail.ru>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Of note, in the original dmesg log, ipw2200 fails to find its firmware
immediately before the backtraces start. If I build ipw2200 as a module
instead, it finds its firmware and the system boots successfully.
--Benjamin Gilbert
next prev parent reply other threads:[~2010-08-20 12:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-19 20:22 2.6.36-rc1 oopses at boot time in kobject allocation Benjamin Gilbert
2010-08-19 20:34 ` Greg KH
2010-08-20 12:48 ` Benjamin Gilbert [this message]
2010-08-20 13:53 ` Ming Lei
2010-08-20 19:02 ` Benjamin Gilbert
2010-08-20 19:07 ` Greg KH
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=4C6E799A.7060902@cs.cmu.edu \
--to=bgilbert@cs.cmu.edu \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).