From: divya <dipraksh@linux.vnet.ibm.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: linuxppc-dev@ozlabs.org, mikey@neuling.org, linux-next@vger.kernel.org
Subject: Re: Power machines fail to boot after build being successful
Date: Mon, 30 Aug 2010 11:43:51 +0530 [thread overview]
Message-ID: <4C7B4C1F.7010003@linux.vnet.ibm.com> (raw)
In-Reply-To: <20100827120144.1736a2f6.sfr@canb.auug.org.au>
On Friday 27 August 2010 07:31 AM, Stephen Rothwell wrote:
> Hi Mikey,
>
> On Fri, 27 Aug 2010 11:15:46 +1000 Michael Neuling<mikey@neuling.org> wrote:
>
>>
>>> After successfully building the kernel version
>>> 2.6.36-rc2-git4(commitid d4348c678977c) with the config file
>>> attached(used make oldconfig), P5 and P6 power machines fails to
>>> reboot with the following logs
>>>
>>> Logs collected while rebooting into today next, same occurs with the
>>> upstream kernel too.
>>>
>> This will fix your problem:
>> http://patchwork.ozlabs.org/patch/62757/
>>
> I have seen something similar in my linux-next boot tests, so I will add
> this patch to linux-next for today.
>
Hi,
The same problem occurs on the linux-tree , now that since the patch is integrated into linux-next,
im not able to find the problem with linux-next-20100827.
When will the patch be integrated with the linux-tree.
Thanks
Divya
next prev parent reply other threads:[~2010-08-30 6:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-26 11:26 Power machines fail to boot after build being successful divya
2010-08-27 0:46 ` Tony Breeds
2010-08-27 0:46 ` Tony Breeds
2010-08-27 1:15 ` Michael Neuling
2010-08-27 1:15 ` Michael Neuling
2010-08-27 2:01 ` Stephen Rothwell
2010-08-27 2:01 ` Stephen Rothwell
2010-08-30 6:13 ` divya [this message]
2010-08-30 6:49 ` Michael Neuling
2010-08-30 6:49 ` Michael Neuling
2010-08-30 7:35 ` divya
2010-08-30 7:35 ` divya
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=4C7B4C1F.7010003@linux.vnet.ibm.com \
--to=dipraksh@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mikey@neuling.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.