On Sun, May 15, 2005 at 08:44:09AM +0900, Yoshito Komatsu wrote:
> Hello,
> 
> Thank you for your reply.
> 
> Manuel Bouyer wrote:
> 
> >On Sun, May 08, 2005 at 11:54:36PM +0900, Yoshito Komatsu wrote:
> >  
> >
> >>rf_DoAccess(c0aa200,72,1,401,0) at netbsd:rf_DoAccess+0x40
> >>raidstart(c0aa2000,c0b07000,0,0,1) at netbsd:raidstart+0x28f
> >>raidstrategy(c0b07000,1,c0a4c118,c0acc800,c09d1084) at
> >>netbsd:raidstrategy+0x136
> >>ccdstart(c0a6d000,c09cd000,0,c0a4c118,c0a4c118) at netbsd:ccdstart+0x137
> >>ccdstrategy(c09cd000,1,1,c09cd07c,0) at netbsd:ccdstrategy+0x142
> >>xbdback_do_io(c09cd000,c09cd000,c0720dc0,c0212b42,c0a4c118) at
> >>    
> >>
> >
> >OK, this is the problem. ccd will call the raidframe strategy from interrupt
> >context, and raidframe isn't expecting that. If you remplace this ccd with
> >a raid0 it should work.
> >I'll try to get ccd on top of raid fixed, though.
> >  
> >
> 
> I replace a ccd with a raid0, but Domain-0 panic still occured.

Ha yes, of course, as the problem is with raidframe and not ccd.
Sorry for the misinformation. The only way I can see to workaround this for now
is to use a vnd for guest domains :(

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la difference
--