NetBSD 5.1/i386 won't start on ASUS EeeTOP 1610PT

2011-06-15 Thread Marc Balmer
Hi NetBSD 5.1 runs fine on an ASUS EeeTOP 1602 touch-screen PC. Yesterday I got hold of a slightly newer model, the EeeTOP 1610PT (1.6 GHz Intel ATOM CPU, 2 GB RAM, touchscreen). The boot loader will load NetBSD and the installer kmod, but when it should start the kernel (i.e. the kernel

uvm locking inconsistency

2011-06-15 Thread Matthias Drochner
A fresh kernel panics for me with a KASSERT about a lock not held - see attachment. uvm_pgalloc() was called from amap_cow_now() -- the anon is freshly allocated, so the reason for the panic is obvious. (and it seems better to relax the check than to acquire the lock for no good reason) Am I the

Re: uvm locking inconsistency

2011-06-15 Thread Matthias Drochner
m.droch...@fz-juelich.de said: see attachment here is it Forschungszentrum Juelich GmbH 52425

Re: uvm locking inconsistency

2011-06-15 Thread Manuel Bouyer
On Wed, Jun 15, 2011 at 08:02:12PM +0200, Matthias Drochner wrote: A fresh kernel panics for me with a KASSERT about a lock not held - see attachment. uvm_pgalloc() was called from amap_cow_now() -- the anon is freshly allocated, so the reason for the panic is obvious. (and it seems better

Re: uvm locking inconsistency

2011-06-15 Thread Mindaugas Rasiukevicius
Matthias Drochner m.droch...@fz-juelich.de wrote: A fresh kernel panics for me with a KASSERT about a lock not held - see attachment. uvm_pgalloc() was called from amap_cow_now() -- the anon is freshly allocated, so the reason for the panic is obvious. (and it seems better to relax the

5.1 USB panic on second removal of memory stick

2011-06-15 Thread Bob Lee
I'm working on a PowerPC system, and have a problem when I remove the usb memory stick the second time. That is insert memory stick, remove memory stick, insert memory stick, and remove memory stick. At this point the system panics, with 'ehci_rem_qh: ED not found'. Anyone

Re: uvm locking inconsistency

2011-06-15 Thread Jukka Ruohonen
On Wed, Jun 15, 2011 at 09:30:17PM +0200, Manuel Bouyer wrote: I fear so, sadly. I think DIAGNOSTIC should be back in x86 GENERIC kernels on HEAD (this can be switched off in release branches) Contrary, I think every viable debug option (DIAGNOSTIC + LOCKDEBUG at least) should be enabled in

re: uvm locking inconsistency

2011-06-15 Thread matthew green
On Wed, Jun 15, 2011 at 09:30:17PM +0200, Manuel Bouyer wrote: I fear so, sadly. I think DIAGNOSTIC should be back in x86 GENERIC kernels on HEAD (this can be switched off in release branches) Contrary, I think every viable debug option (DIAGNOSTIC + LOCKDEBUG at least) should be enabled

Re: uvm locking inconsistency

2011-06-15 Thread Masao Uebayashi
On Thu, Jun 16, 2011 at 1:34 PM, Jukka Ruohonen jruoho...@iki.fi wrote: On Wed, Jun 15, 2011 at 09:30:17PM +0200, Manuel Bouyer wrote: I fear so, sadly. I think DIAGNOSTIC should be back in x86 GENERIC kernels on HEAD (this can be switched off in release branches) Contrary, I think every