public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Tim Blechmann <tim@klingt.org>
Cc: linux-kernel@vger.kernel.org, stern@rowland.harvard.edu, x86@kernel.org
Subject: Re: 2.6.32 regression: unable to handle kernel paging request
Date: Fri, 18 Dec 2009 12:49:05 +0900	[thread overview]
Message-ID: <4B2AFBB1.3040609@kernel.org> (raw)
In-Reply-To: <4B2A93F2.3070407@klingt.org>

Hello,

On 12/18/2009 05:26 AM, Tim Blechmann wrote:
>> trying to bisect the kernel tree,
>> 405d967dc70002991f8fc35c20e0d3cbc7614f63 seems to be the first bad commit.
>> during bisecting, i recorded several boot logs, which are attached.
> 
> removing module-common.lds from LDFLAGS_MODULE, my machine boots fine
> and without any error messages:

Looks like some necessary part of module image ends up in discarded
sections.  Before the commit, the build process kept those sections so
it worked.  The code has been there for some time now and you're the
first one to report it, so I suppose your .config is a bit different
from more usual ones.  Can you please attach it?

Thanks.

-- 
tejun

  reply	other threads:[~2009-12-18  3:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-14 19:52 2.6.32 regression: unable to handle kernel paging request Tim Blechmann
2009-12-17 12:56 ` Tim Blechmann
2009-12-17 20:26   ` Tim Blechmann
2009-12-18  3:49     ` Tejun Heo [this message]
2009-12-18  9:15       ` Tim Blechmann
2009-12-21  7:16         ` Tejun Heo
2009-12-21  9:32           ` Tim Blechmann
2009-12-24 12:06             ` Tejun Heo
2009-12-24 12:07               ` Tim Blechmann
2009-12-24 12:26                 ` Tejun Heo
2009-12-24 12:48                   ` Tejun Heo
2009-12-24 12:55                     ` Tim Blechmann
2009-12-27  9:50                     ` Tim Blechmann
2010-01-01 20:55                       ` Tim Blechmann
2010-01-02  2:23                         ` Tejun Heo

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=4B2AFBB1.3040609@kernel.org \
    --to=tj@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    --cc=tim@klingt.org \
    --cc=x86@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