From: linas@austin.ibm.com (Linas Vepstas)
To: Anton Blanchard <anton@samba.org>
Cc: Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: Mutex debug lock failure [was Re: Bad gcc-4.1.0 leads to Power4 crashes... and power5 too, actually
Date: Wed, 20 Dec 2006 19:03:19 -0600 [thread overview]
Message-ID: <20061221010319.GE16860@austin.ibm.com> (raw)
In-Reply-To: <20061221003658.GB3048@krispykreme>
On Thu, Dec 21, 2006 at 11:36:59AM +1100, Anton Blanchard wrote:
>
> On Wed, Dec 20, 2006 at 05:46:47PM -0600, Linas Vepstas wrote:
>
> > System assert at: file: rtas_io_config.c -- line: 195
> > rio_hub_num: 10
> > drawer_num: 6
> > phb_num: 3
> > buid: 7
>
> Looks like a firmware assert. Did you pass in something dodgy to a
> config read/write op? Maybe a bad buid?
Same kernel runs fine on power5. Although it does have patches
applied, those very same patches boot fine when applied to a slightly
older kernel (2.6.19-rc4). I haven't been messing with buids or
pci config space (at least not intentionaly).
I'll try again with an unpatched, unmodified kernel.
--linas
WARNING: multiple messages have this Message-ID (diff)
From: linas@austin.ibm.com (Linas Vepstas)
To: Anton Blanchard <anton@samba.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: Mutex debug lock failure [was Re: Bad gcc-4.1.0 leads to Power4 crashes... and power5 too, actually
Date: Wed, 20 Dec 2006 19:03:19 -0600 [thread overview]
Message-ID: <20061221010319.GE16860@austin.ibm.com> (raw)
In-Reply-To: <20061221003658.GB3048@krispykreme>
On Thu, Dec 21, 2006 at 11:36:59AM +1100, Anton Blanchard wrote:
>
> On Wed, Dec 20, 2006 at 05:46:47PM -0600, Linas Vepstas wrote:
>
> > System assert at: file: rtas_io_config.c -- line: 195
> > rio_hub_num: 10
> > drawer_num: 6
> > phb_num: 3
> > buid: 7
>
> Looks like a firmware assert. Did you pass in something dodgy to a
> config read/write op? Maybe a bad buid?
Same kernel runs fine on power5. Although it does have patches
applied, those very same patches boot fine when applied to a slightly
older kernel (2.6.19-rc4). I haven't been messing with buids or
pci config space (at least not intentionaly).
I'll try again with an unpatched, unmodified kernel.
--linas
next prev parent reply other threads:[~2006-12-21 1:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-20 0:46 Bad gcc-4.1.0 leads to Power4 crashes... and power5 too, actually Linas Vepstas
2006-12-20 0:53 ` Benjamin Herrenschmidt
2006-12-20 1:02 ` Linas Vepstas
2006-12-20 1:46 ` Peter Bergner
2006-12-20 21:19 ` Linas Vepstas
2006-12-20 21:28 ` Benjamin Herrenschmidt
2006-12-20 23:03 ` Mutex debug lock failure [was " Linas Vepstas
2006-12-20 23:03 ` Linas Vepstas
2006-12-20 23:09 ` Benjamin Herrenschmidt
2006-12-20 23:09 ` Benjamin Herrenschmidt
2006-12-20 23:46 ` Linas Vepstas
2006-12-20 23:46 ` Linas Vepstas
2006-12-21 0:36 ` Anton Blanchard
2006-12-21 0:36 ` Anton Blanchard
2006-12-21 1:03 ` Linas Vepstas [this message]
2006-12-21 1:03 ` Linas Vepstas
2006-12-21 14:41 ` Ingo Molnar
2006-12-21 14:41 ` Ingo Molnar
2006-12-21 21:12 ` Linas Vepstas
2006-12-21 21:12 ` Linas Vepstas
2006-12-23 6:28 ` Alan Modra
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=20061221010319.GE16860@austin.ibm.com \
--to=linas@austin.ibm.com \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mingo@redhat.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 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.