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? Anton - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- References:
- Mutex debug lock failure [was Re: Bad gcc-4.1.0 leads to Power4 crashes... and power5 too, actually
- From: [email protected] (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 <[email protected]>
- Re: Mutex debug lock failure [was Re: Bad gcc-4.1.0 leads to Power4 crashes... and power5 too, actually
- From: [email protected] (Linas Vepstas)
- Mutex debug lock failure [was Re: Bad gcc-4.1.0 leads to Power4 crashes... and power5 too, actually
- Prev by Date: Re: [PATCH] MAINTAINERS: fix email for S3C2410 and S3C2440
- Next by Date: Re: Mutex debug lock failure [was Re: Bad gcc-4.1.0 leads to Power4 crashes... and power5 too, actually
- 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):
 |