Have you tried by any chance tried a 3.8 with aac enabled? This seems to go wrong in em and not aac.
On Thu, Sep 22, 2005 at 04:49:14PM -0500, eric wrote: > On Thu, 2005-09-22 at 16:06:39 -0500, Marco Peereboom proclaimed... > > > What do the crashes look like? > > Sometimes I can get to DDB, other times it will just crash so bad I can't > even get console. > > I could get this much out of it when I did the PR report. > > uvm_fault(0xd7e12a20, 0xcffa5000, 0, 1) -> e > kernel: page fault trap, code=0 > Stopped at pmap_enter+0xdd: movl 0(%edx,%eax,4),%edx > ddb{1}> > Entering Direct mode...Server = foo > > ddb{1}> trace > pmap_enter(d05ff6c0,e973b000,36ce8000,7,23,e973b000,e9e7dc78,d7e00cd4) > at pmap_ > enter+0xdd > uvm_fault(d05c3e60,e973b000,0,3,80) at uvm_fault+0x1165 > trap() at trap+0x5ef > --- trap (number 6) --- > em_encap(d1895800,d7da6200,0,0) at em_encap+0x3cd > em_start_locked(d1895830,d7b9c01a,4a8,d7b9c010,d1895830,d19a3000,d004,d02453fe, > e9e7de90,d7b9c002,e9e7de40,d02457f6,d1895830,d7da6200,e9e7de90,d024428e,30,d7da > 6200,e9e7de90,0,d1952180,d7da000b,e9e7dea0,d0243780,d19a3000,d1895830,d7da6200, > d024376d,80,e9e7de90,d7da6200,e9e7de9e,d7da6200,d19a3000,20000000,d01dab41,e9e7 > de98,e9e7de9c,d01ebcba,b0,d1895830,d1895030,66699000,60000a4,fc7f35d6,a0008,e9e > 7ded0,d024342a,d19a3000,d7da6200,d7e04000,d01ec011,0,d01020c6,e9e7deb8,1,d05e6d > 20,d7e00cd4,e9e7def0,d01021f5,c) at em_start_locked+0x6e > em_start(d1895830,d7da6200,e9e7de90,d024428e,30) at em_start+0x20 > bridge_ifenqueue(d19a3000,d1895830,d7da6200,d024376d,80) at > bridge_ifenqueue+0x > ce > bridgeintr_frame(d19a3000,d7da6200,d7e04000,d01ec011) at > bridgeintr_frame+0x2f0 > > bridgeintr(c,d7e00cd4,d05e2880,d03146cd,e9e7df18) at bridgeintr+0x1e > Xsoftnet() at Xsoftnet+0x59 > --- interrupt --- > end(4,9,3c0f6bc8,64,d0102100) at 0xe9e7df80 > ddb{1}> ps > PID PPID PGRP UID S FLAGS WAIT COMMAND > 255 21564 21564 32767 3 0x2004186 bpf ngrep > 21564 19514 21564 0 3 0x2004087 pause sh > 19514 7545 19514 1002 3 0x2004086 pause ksh > 7545 21602 21602 1002 3 0x2000184 select sshd > 21602 13521 21602 0 3 0x2004084 netio sshd > 6527 23131 6527 1002 3 0x2004086 ttyin ksh > 23131 2010 2010 1002 3 0x2000184 select sshd > 2010 13521 2010 0 3 0x2004084 netio sshd > 13521 1 13521 0 3 0x2000084 select sshd > 1092 2849 29166 0 3 0x2000084 select ntam > 22697 1 22697 0 3 0x2004086 ttyin getty > 30168 1 30168 0 3 0x2004086 ttyin getty > 11773 1 11773 0 3 0x2000084 select cron > 31414 1 31414 0 3 0x2000087 nanosleep barnyard > 27805 1 27805 65532 2 0x104 snort > * 2849 29166 29166 0 7 0x4 ntam > 29166 1 29166 0 7 0x4 ntam > 10053 1 10053 0 3 0x2040184 select sendmail > 26108 0 0 0 3 0x2100204 acct acct > 14928 1 14928 0 3 0x2000084 poll ntpd > 15437 1 7617 83 3 0x2000186 poll ntpd > 5646 31689 31689 74 3 0x2000184 bpf pflogd > 31689 1 31689 0 3 0x2000084 netio pflogd > 17322 6669 6669 73 2 0x2000184 syslogd > 6669 1 6669 0 3 0x2000084 netio syslogd > 10 0 0 0 3 0x2100204 usbtsk usbtask > 9 0 0 0 3 0x2100204 usbevt usb0 > 8 0 0 0 3 0x2100204 kmalloc kmthread > 7 0 0 0 3 0x2100204 crypto_wa crypto > 6 0 0 0 3 0x2100204 aiodoned aiodoned > 5 0 0 0 3 0x2100204 syncer update > 4 0 0 0 3 0x2100204 cleaner cleaner > 3 0 0 0 3 0x100204 reaper reaper > 2 0 0 0 3 0x2100204 pgdaemon pagedaemon > 1 0 1 0 3 0x2004084 wait init > 0 -1 0 0 3 0x2080204 scheduler swapper > > > Fell free to contact Adaptec and let them know that you are having issues > > with their raid card. > > Last time I did that, I got the standard "Open wha?" > > They're idiots, and we don't buy their stuff anymoer. Unfortunately, I'm an > idiot for still having to run one of them :) > > Thanks. > > - Eric