All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
To: michael@ellerman.id.au
Cc: linuxppc-dev@ozlabs.org, Balbir Singh <balbir@linux.vnet.ibm.com>
Subject: Re: kernel expection generated with 2.6.21-mm1 kernel boot up
Date: Mon, 07 May 2007 18:03:45 +0530	[thread overview]
Message-ID: <463F1CA9.40501@linux.vnet.ibm.com> (raw)
In-Reply-To: <1178538912.24522.12.camel@concordia.ozlabs.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 824 bytes --]

***********************
Warning: Your file, device-tress.tar.bz, contains more than 32 files after decompression and cannot be scanned.
***********************


Michael Ellerman wrote:
> On Mon, 2007-05-07 at 16:30 +0530, Kamalesh Babulal wrote:
>   
>> Hi,
>>
>> I tried compiling and booting up with 2.6.21-mm1 kernel
>> on the following machine
>>
>> Architecture      :    PPC64
>> CPU Type           :    POWER5 (gr)
>> Machine Type    :    CHRP IBM,9117-570
>> Base OS              :    Fedora Core 5
>>
>>     
>
>   
>> [boot]0012 Setup Arch
>>
>> Node 0 active with no memory
>>     
>
> This looks bad.
>
> Can you attach a tarball of /proc/device-tree from the system (booted
> with a different kernel obviously).
>
> cheers
>
>   
Find the tarball of the /proc/device-tree attached.

Thanks,
Kamalesh Babulal.


[-- Attachment #2: device-tress.tar.bz --]
[-- Type: application/x-bzip, Size: 12769 bytes --]

  reply	other threads:[~2007-05-07 12:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-07 11:00 kernel expection generated with 2.6.21-mm1 kernel boot up Kamalesh Babulal
2007-05-07 11:55 ` Michael Ellerman
2007-05-07 12:33   ` Kamalesh Babulal [this message]
2007-05-08 12:04     ` Srinivasa Ds
2007-05-08 16:23       ` Linas Vepstas
2007-05-08 23:45         ` Benjamin Herrenschmidt
  -- strict thread matches above, loose matches on Subject: below --
2007-05-07 12:19 Kamalesh Babulal
2007-05-08 12:07 ` Srinivasa Ds
2007-05-08 18:22   ` Christoph Lameter
2007-05-09  8:26     ` Srinivasa Ds
2007-05-09 15:50       ` Hugh Dickins

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=463F1CA9.40501@linux.vnet.ibm.com \
    --to=kamalesh@linux.vnet.ibm.com \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=michael@ellerman.id.au \
    /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.