On Wed, Mar 08, 2006 at 09:19:13AM +1030, Berndt Josef Wulf wrote:
> On Wednesday 08 March 2006 05:41, Manuel Bouyer wrote:
> > On Tue, Mar 07, 2006 at 04:35:12PM +0100, TlorD wrote:
> > > Greetings,
> > > 	I am trying to deploy a XEN machine which has an Adaptec 2410SA SATA
> > > RAID controller.
> > > 	NetBSD 3.0/i386 works like a charm (if using GENERIC.MPACPI), but
> > > 3.0/xen (enriched with aac0 and ld0 driver definitions bluntly copied
> > > from GENERIC.MPACPI) panics shortly after the card is recognized.
> > >
> > > Is there anything I can do to correctly use the card?
> > >
> > > Thanks for the attention.
> > >
> > >
> > > Here is the short version of the error it produces:
> > >
> > > uvm_fault (0xc061fd60, 0xc9c1b000, 0, 1) -> 0xe
> > > kernel: page fault trap, code=0
> > > Stopped in pid 0.1 (swapper) at netbsd:aac_intr+0x23: cmpb
> > > $0,0x3184(%eax) aac_intr(c08d7400,0,c08bdf9c,0c06e9ef8) at
> > > netbsd:aac_intr+0x23
> > > pirq_interrupt(c0854970,c06e9ef4,0,11,c03b0031) at
> > > netbsd:pirq_interrupt+0xf Xresume_xenev4() at netbsd:Xresume_xenev4+0x34
> >
> > Can you try to narrow down where it gets the fault, and why ?
> > It's probably dereferencing a NULL pointer but we need to find which one.
> > In my local build aac_intr+0x23 is line 790 in sys/dev/ic/aac.c
> > but it may not match your kernel (at last at first glance I can't see why
> > this would cause a fault).
> 
> 
> This is similar to the fault reported earlier including a debug trace - see  
> link below:
> 
> http://mail-index.netbsd.org/port-i386/2006/02/26/0000.html

Not really, this is a fault in the bus_dma code, while in this case
it's a fault in the driver itself. I'm not sure they're related.

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