Mathieu - wrote:
> Mathieu - wrote:
> > Martin Pieuchot wrote:
> > > On 23/05/18(Wed) 11:14, Hrvoje Popovski wrote:
> > > > On 22.5.2018. 17:03, Theo Buehler wrote:
> > > > > I applied the diff, made syscalls, then built and installed a new
> > > > > kernel. With that, I ran into a reliable complete lockup on my x230 by
> > > > > starting in an xterm
> > > > > 
> > > > > # make -j 3 build 2>&1 | tee -a /home/theo/buildlog
> > > > > 
> > > > > and then navigating firefox to youtube and trying to start some video.
> > > > > 
> > > > > Unfortunately, I don't know how to provide you with any more useful
> > > > > information.
> > > > > 
> > > > > The machine becomes completely unresponsive, the mouse pointer is
> > > > > frozen, I'm unable to break into ddb, and the machine is no longer
> > > > > pingable.
> > > > > 
> > > > 
> > > > same as tb@. my box is having transmission, samba and nfs and everything
> > > > seemed fine until i started make -j4 build then it became unresponsive.
> > > 
> > > I need to find some time to reproduce the hang.  In the meantime if you
> > > want to try a WITNESS kernel, that might give us more clues.
> > > 
> > 
> > I did just that and the kernel still hangs without more informations.
> > 
> 
> Hello,
> 
> Finally got around to set up a working serial on vbox (that was way
> more convoluted than expected ...), and I got a nice trace with a
> WITNESS kernel: 
> 

yikes, sorry hit the send button, this trace was false, here is the good
one :

panic: acquiring blockable sleep lock with spinlock or critical section held 
(kernel_lock) &kernel_lock @ /usr/src/sys/arch/amd64/amd64/intr.c:525

Stopped at      db_enter+0x5:   popq    %rbp                                    
                                                                         
    TID    PID    UID     PRFLAGS     PFLAGS  CPU  COMMAND
* 51372  66893   1000    0x300002  0x4000000    0  chrome 
  55273  42812      0     0x14000      0x200    1  softnet

db_enter() at db_enter+0x5                                
panic() at panic+0x138    
witness_checkorder(ffffffff81a571e3,20d,0,ffffffff81d146a0,ffff8000000a2900) at
 witness_checkorder+0xd32                                                      
___mp_lock(ffff8000000a2900,ffff8000224a0e88,ffffffff81ba0ff0) at ___mp_lock+0x
72                                                                             
intr_handler(ffffff011ac75d00,ffff8000000a1f80) at intr_handler+0x40
Xintr_ioapic_level11_untramp(ffff8000224a10c0,8,ffffffff8125af50,ffff8000224a0f
50,ffffffff81b8859b,ffff8000007c1800) at Xintr_ioapic_level11_untramp+0x141    
fd_getfile(850,ffff800022506740) at fd_getfile+0x3b                        
sendit(850,ffff800022506740,85,ffff8000224a1160,0) at sendit+0x40
sys_sendto(e464fbb455fc046c,1a,0) at sys_sendto+0x63             
syscall(1a4eae263790) at syscall+0x31d              
Xsyscall_untramp(c,0,0,0,0,85) at Xsyscall_untramp+0xc0
end of kernel                                          
end trace frame: 0x1a4eae2636a0, count: 4

ddb{1}> bt                    
x86_ipi_db(ffffffff81550305) at x86_ipi_db+0x5
x86_ipi_handler() at x86_ipi_handler+0x70     
Xresume_lapic_ipi(ffff8000007b2000,4314d9ac00000001,0,0,0,be713e3) at Xresume_l
apic_ipi+0x1f                                                                  
___mp_lock(ffffff010eaf94e8,ffffff010eaf9570,ffff8000007b2000) at ___mp_lock+0x
f2                                                                             
sowakeup(ffffff010eaf9570,ffffff010eaf94e8) at sowakeup+0x96
sorwakeup(ffffff00bf5dde00) at sorwakeup+0x6a               
tcp_input(2,ffffffff819dbda0,2,6) at tcp_input+0x315d
ip_deliver(ffff80002217377c,ffff800022173780,ffff80000003c080,ffff8000221737d0)
 at ip_deliver+0x203                                                           
ipintr() at ipintr+0x5a
if_netisr(ffffffff81144830) at if_netisr+0x6a
taskq_thread(0) at taskq_thread+0x6d         
end trace frame: 0x0, count: -11 


Sorry again for the noise, the earlier trace was with a tainted kernel.

Reply via email to