From: Jon Masters <jonathan@jonmasters.org>
To: balbir@linux.vnet.ibm.com
Cc: Sam Ravnborg <sam@ravnborg.org>,
Robert Berger <robert.berger@reliableembeddedsystems.com>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: http://patchwork.kernel.org/patch/26483/ broke my system boot
Date: Fri, 05 Jun 2009 03:17:12 -0400 [thread overview]
Message-ID: <1244186233.11597.106.camel@localhost.localdomain> (raw)
In-Reply-To: <20090604063144.GB7504@balbir.in.ibm.com>
On Thu, 2009-06-04 at 14:31 +0800, Balbir Singh wrote:
> * Sam Ravnborg <sam@ravnborg.org> [2009-06-03 21:45:26]:
>
> > On Wed, Jun 03, 2009 at 10:39:44PM +0800, Balbir Singh wrote:
> > > After spending some time figuring out why my system failed to reboot,
> > > checking config options, kernel version, modules installed. I figured
> > > out that the patch in http://patchwork.kernel.org/patch/26483/ broke
> > > the system boot on the latest mmotm. Reverting it helped my system
> > > call depmod and hence boot.
> > >
> > > The patch is really unhelpful, since the changelog is completely
> > > empty. Sigh!
> >
> > Yeah, sorry for not nak'ing it earlier. Has been busy.
> > Andrew removed it from -mm and I notified the author about the
> > problems with the patch (in private mail it seems - I just replied to what I had).
>
> Cool! Thanks for the update. I'll get the latest mmotm and test as
> well.
The general idea of using the cross-depmod is good though :) We have had
a few people recently run their newer host depmod and wonder why their
older embedded device can't read the new binary index files.
Jon.
next prev parent reply other threads:[~2009-06-05 14:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 14:39 Balbir Singh
2009-06-03 19:45 ` Sam Ravnborg
2009-06-04 6:31 ` Balbir Singh
2009-06-04 6:47 ` lkml
2009-06-04 7:32 ` Balbir Singh
2009-06-04 12:19 ` lkml
2009-06-05 7:17 ` Jon Masters [this message]
2009-06-05 19:49 ` Sam Ravnborg
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=1244186233.11597.106.camel@localhost.localdomain \
--to=jonathan@jonmasters.org \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robert.berger@reliableembeddedsystems.com \
--cc=sam@ravnborg.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
Powered by JetHome