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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: Mutex debug lock failure [was Re: Bad gcc-4.1.0 leads to Power4 crashes... and power5 too, actually
- From: Ingo Molnar <mingo@redhat.com>
- Re: Mutex debug lock failure [was Re: Bad gcc-4.1.0 leads to Power4 crashes... and power5 too, actually
- References:
- Mutex debug lock failure [was Re: Bad gcc-4.1.0 leads to Power4 crashes... and power5 too, actually
- From: linas@austin.ibm.com (Linas Vepstas)
- Re: Mutex debug lock failure [was Re: Bad gcc-4.1.0 leads to Power4 crashes... and power5 too, actually
- From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
- Re: Mutex debug lock failure [was Re: Bad gcc-4.1.0 leads to Power4 crashes... and power5 too, actually
- From: linas@austin.ibm.com (Linas Vepstas)
- Re: Mutex debug lock failure [was Re: Bad gcc-4.1.0 leads to Power4 crashes... and power5 too, actually
- From: Anton Blanchard <anton@samba.org>
- Mutex debug lock failure [was Re: Bad gcc-4.1.0 leads to Power4 crashes... and power5 too, actually
- Prev by Date: Re: Mutex debug lock failure [was Re: Bad gcc-4.1.0 leads to Power4 crashes... and power5 too, actually
- Next by Date: [PATCH -mm 2/4] swsusp: Change code ordering in disk.c
- Previous by thread: Re: Mutex debug lock failure [was Re: Bad gcc-4.1.0 leads to Power4 crashes... and power5 too, actually
- Next by thread: Re: Mutex debug lock failure [was Re: Bad gcc-4.1.0 leads to Power4 crashes... and power5 too, actually
- Index(es):
![]() |