All of lore.kernel.org
 help / color / mirror / Atom feed
From: Srinivasa Ds <srinivasa@in.ibm.com>
To: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org,
	Balbir Singh <balbir@linux.vnet.ibm.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: kernel expection generated with 2.6.21-mm1 kernel boot up
Date: Tue, 08 May 2007 17:37:50 +0530	[thread overview]
Message-ID: <46406816.8030106@in.ibm.com> (raw)
In-Reply-To: <463F196C.9070501@linux.vnet.ibm.com>

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
> 

> 
> Faulting instruction address: 0xc0000000000cc5e4
> 
> cpu 0x1: Vector: 300 (Data Access) at [c000000005373320]
> 
>   pc: c0000000000cc5e4: .slab_free+0x6c/0x424
> 
>   lr: c00000000002fa70: .pgtable_free_tlb+0xd0/0x140
> 
>   sp: c0000000053735a0
> 
>  msr: 8000000000009032
> 

Looks like there is a bug in SLUB implementaion for ppc64 in 2.6.21-mm1.
I unmarked CONFIG_SLUB and build the kernel, its booting cleary now.

Thanks
 Srinivasa DS

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

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

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=46406816.8030106@in.ibm.com \
    --to=srinivasa@in.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=kamalesh@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.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 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.