From: Paul Mackerras <paulus@samba.org>
To: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Cc: kernel list <linux-kernel@vger.kernel.org>,
linuxppc-dev@ozlabs.org, linux-next@vger.kernel.org,
nacc@us.ibm.com, Andrew Morton <akpm@linux-foundation.org>,
Balbir Singh <balbir@linux.vnet.ibm.com>
Subject: Re: [BUG] 2.6.25-rc2-git4 - Regression Kernel oops while running kernbench and tbench on powerpc
Date: Wed, 9 Apr 2008 09:26:11 +1000 [thread overview]
Message-ID: <18427.65299.403151.344959@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <47FB5C5A.5020104@linux.vnet.ibm.com>
Kamalesh Babulal writes:
> The kernel oops after applying the patch. Some time it takes more than
> one run to reproduce it, it was reproducible in the second run this
> time.
>
> Unrecoverable exception 4100 at c000000000008c8c
> Oops: Unrecoverable exception, sig: 6 [#1]
> SMP NR_CPUS=128 NUMA pSeries
> Modules linked in:
> NIP: c000000000008c8c LR: 000000000ff0135c CTR: 000000000ff012f0
> REGS: c000000772343bb0 TRAP: 4100 Not tainted (2.6.25-rc8-autotest)
> MSR: 8000000000001030 <ME,IR,DR> CR: 44044228 XER: 00000000
> TASK = c00000077cfa0900[13437] 'cc1' THREAD: c000000772340000 CPU: 2
> GPR00: 0000000000004000 c000000772343e30 00000000000000bb 000000000000d032
> GPR04: 00000000000000bb 0000000000000400 000000000000000a 0000000000000002
> GPR08: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
> GPR12: 0000000000000000 c000000000734000 0000000000000064 00000000ffe6df08
> GPR16: 00000000105b0000 00000000105b0000 0000000010440000 00000000105b0000
> GPR20: 00000000ffe6e008 00000000105b0000 00000000105b0000 000000000000000a
> GPR24: 000000000ffec408 0000000000000001 00000000ffe6ddca 0000000000000400
> GPR28: 000000000ffec408 00000000f7ff8000 000000000ffebff4 0000000000000400
> NIP [c000000000008c8c] restore+0x8c/0xc0
> LR [000000000ff0135c] 0xff0135c
> Call Trace:
> [c000000772343e30] [c000000000008cd4] do_work+0x14/0x2c (unreliable)
> Instruction dump:
> 7c840078 7c810164 70604000 41820028 60000000 7c4c42e6 e88d01f0 f84d01f0
> 7c841050 e84d01e8 7c422214 f84d01e8 <e9a100d8> 7c7b03a6 e84101a0 7c4ff120
That looks like the bug that was supposed to be fixed by commit
44387e9ff25267c78a99229aca55ed750e9174c7, which is in 2.6.25-rc7 and
later.
What was the SHA1 ID of the head commit for the kernel source that
gave you this oops? Did you have any other patches besides the one I
sent you applied?
Paul.
next prev parent reply other threads:[~2008-04-08 23:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-20 15:01 [BUG] 2.6.25-rc2-git4 - Regression Kernel oops while running kernbench and tbench on powerpc Kamalesh Babulal
2008-04-08 8:21 ` Paul Mackerras
2008-04-08 11:51 ` Kamalesh Babulal
2008-04-08 12:53 ` Paul Mackerras
2008-04-08 17:45 ` Kamalesh Babulal
2008-04-08 23:26 ` Paul Mackerras [this message]
2008-04-09 5:20 ` Kamalesh Babulal
2008-04-14 10:04 ` Paul Mackerras
2008-04-14 13:28 ` Kamalesh Babulal
2008-04-23 8:16 ` Paul Mackerras
2008-04-24 6:05 ` Kamalesh Babulal
2008-05-09 3:15 ` Paul Mackerras
2008-05-10 16:43 ` Kamalesh Babulal
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=18427.65299.403151.344959@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=nacc@us.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).