From: Ken Lewis <kennylewis@gmail•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org
Subject: Re: [next-20091231] linux-next builds fine, but panics at runtime
Date: Tue, 12 Jan 2010 19:35:20 +0000 [thread overview]
Message-ID: <5a44caba1001121135kfdc5226y4e8b0ddf111c9d09@mail.gmail.com> (raw)
In-Reply-To: <20100112125833.60597593.sfr@canb.auug.org.au>
2010/1/12 Stephen Rothwell <sfr@canb•auug.org.au>:
> Hi Ken,
>
> On Mon, 11 Jan 2010 20:28:41 +0000 Ken Lewis <kennylewis@gmail•com> wrote:
>>
>> I'm havng some problems testing linux-next at the moment. I'm able to
>> build each release but the kernel panics at boot. The problem's been
>> about since the start of December and I haven't managed to find what
>> portion of my .config and the loophole in the build system that allow
>> this to happen. Can anyone else help me?
>>
> Have you tried building and booting (with the same config) just the
> version of Linus' kernel that those next- kernel's were built on? (Just
> as a sanity check) For next-20091231, Linus' kernel was commit
> 05a625486efc3209ae4d98e253dafa6ce0124385 (for example).
Linus' tree has built fine and works all the way through. I'll try
copying the config across and using it. BTW next-20100111 built but
panics on boot.
Thanks,
K3n
next prev parent reply other threads:[~2010-01-12 19:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-11 20:28 [next-20091231] linux-next builds fine, but panics at runtime Ken Lewis
2010-01-12 1:58 ` Stephen Rothwell
2010-01-12 19:35 ` Ken Lewis [this message]
2010-01-12 23:18 ` Ken Lewis
2010-01-14 23:12 ` Ken Lewis
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=5a44caba1001121135kfdc5226y4e8b0ddf111c9d09@mail.gmail.com \
--to=kennylewis@gmail$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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