Re: Another pmap panic

2020-03-20 Thread MLH
Andrew wrote:
> I suggest updaing to the latest, delivered yesterday, which has fixes for
> every problem I have encountered or seen mentioned including this one, and
> survives low memory stress testing for me:

Thanks! Big improvement. I'm not running out of phymem now and most
of it is once again being used for disk cache and running at normal
speeds.



Re: Another pmap panic

2020-03-20 Thread Chavdar Ivanov
Thanks! Building now.

On Fri, 20 Mar 2020 at 18:27, Andrew Doran  wrote:
>
> Hi,
>
> I meant to send a note yesterday but fatigue got the better of me.
>
> I suggest updaing to the latest, delivered yesterday, which has fixes for
> every problem I have encountered or seen mentioned including this one, and
> survives low memory stress testing for me:
>
> /*  $NetBSD: pmap.c,v 1.378 2020/03/19 18:58:14 ad Exp $*/
>
> Thank you,
> Andrew
>
> On Fri, Mar 20, 2020 at 05:49:59PM +, Chavdar Ivanov wrote:
> > Hi,
> >
> > Overnight, while doing pkg_rolling-replace, my 'server' got:
> > ...
> > panic: kernel diagnostic assertion "ptp->wire_count == 1" failed: file
> >   "/home/sysbuild/src/sys/arch/x86/x86/pmap.c", line 2232
> >
> > cpu0: Begin traceback...
> > vpanic() at netbsd:vpanic+0x178
> > kern_assert() at netbsd:kern_assert+0x48
> > pmap_unget_ptp() at netbsd:pmap_unget_ptp+0x1f1
> > pmap_get_ptp() at netbsd:pmap_get_ptp+0x300
> > pmap_enter_ma() at netbsd:pmap_enter_ma+0x6fb
> > pmap_enter_default() at netbsd:pmap_enter_default+0x29
> > uvm_fault_internal() at netbsd:uvm_fault_internal+0xf2e
> > trap() at netbsd:trap+0x50a
> > --- trap (number 6) ---
> > 7f7eec2007e0:
> > cpu0: End traceback...
> >
> > dumping to dev 168,2 (offset=8, size=5225879):
> > ...
> >
> >
> > --
> > 



-- 



Re: Another pmap panic

2020-03-20 Thread Andrew Doran
Hi,

I meant to send a note yesterday but fatigue got the better of me.  

I suggest updaing to the latest, delivered yesterday, which has fixes for
every problem I have encountered or seen mentioned including this one, and
survives low memory stress testing for me:

/*  $NetBSD: pmap.c,v 1.378 2020/03/19 18:58:14 ad Exp $*/

Thank you,
Andrew

On Fri, Mar 20, 2020 at 05:49:59PM +, Chavdar Ivanov wrote:
> Hi,
> 
> Overnight, while doing pkg_rolling-replace, my 'server' got:
> ...
> panic: kernel diagnostic assertion "ptp->wire_count == 1" failed: file
>   "/home/sysbuild/src/sys/arch/x86/x86/pmap.c", line 2232
> 
> cpu0: Begin traceback...
> vpanic() at netbsd:vpanic+0x178
> kern_assert() at netbsd:kern_assert+0x48
> pmap_unget_ptp() at netbsd:pmap_unget_ptp+0x1f1
> pmap_get_ptp() at netbsd:pmap_get_ptp+0x300
> pmap_enter_ma() at netbsd:pmap_enter_ma+0x6fb
> pmap_enter_default() at netbsd:pmap_enter_default+0x29
> uvm_fault_internal() at netbsd:uvm_fault_internal+0xf2e
> trap() at netbsd:trap+0x50a
> --- trap (number 6) ---
> 7f7eec2007e0:
> cpu0: End traceback...
> 
> dumping to dev 168,2 (offset=8, size=5225879):
> ...
> 
> 
> -- 
> 


Re: Another pmap panic

2020-03-20 Thread MLH
Chavdar wrote:
> Overnight, while doing pkg_rolling-replace, my 'server' got:
> ...
> panic: kernel diagnostic assertion "ptp->wire_count == 1" failed: file
>   "/home/sysbuild/src/sys/arch/x86/x86/pmap.c", line 2232
> 
> cpu0: Begin traceback...
> vpanic() at netbsd:vpanic+0x178
> kern_assert() at netbsd:kern_assert+0x48
> pmap_unget_ptp() at netbsd:pmap_unget_ptp+0x1f1
> pmap_get_ptp() at netbsd:pmap_get_ptp+0x300
> pmap_enter_ma() at netbsd:pmap_enter_ma+0x6fb
> pmap_enter_default() at netbsd:pmap_enter_default+0x29
> uvm_fault_internal() at netbsd:uvm_fault_internal+0xf2e
> trap() at netbsd:trap+0x50a
> --- trap (number 6) ---
> 7f7eec2007e0:
> cpu0: End traceback...
> 
> dumping to dev 168,2 (offset=8, size=5225879):

I just got another one :

[ 101789.993512] panic: kernel diagnostic assertion "ptp->wire_count == 1" 
failed: file "/usr/src/sys/arch/x86/x86/pmap.c", line 2232 
[ 101789.993512] cpu1: Begin traceback...
[ 101789.993512] vpanic() at netbsd:vpanic+0x178
[ 101789.993512] kern_assert() at netbsd:kern_assert+0x48
[ 101789.993512] pmap_unget_ptp() at netbsd:pmap_unget_ptp+0x1f1
[ 101789.993512] pmap_get_ptp() at netbsd:pmap_get_ptp+0x300
[ 101789.993512] pmap_enter_ma() at netbsd:pmap_enter_ma+0x6fb
[ 101789.993512] pmap_enter_default() at netbsd:pmap_enter_default+0x29
[ 101789.993512] uvm_fault_lower_enter() at netbsd:uvm_fault_lower_enter+0x111
[ 101789.993512] uvm_fault_internal() at netbsd:uvm_fault_internal+0x12b1
[ 101789.993512] trap() at netbsd:trap+0x50a
[ 101789.993512] --- trap (number 6) ---
[ 101789.993512] 6fa90c321352:
[ 101789.993512] cpu1: End traceback...

[ 101789.993512] dumping to dev 0,1 (offset=1159, size=1044333):

Built two days ago - NetBSD 9.99.50 Wed Mar 18 12:46:17

Just before it coredumped, I saw that kmem-00192 showed almost 10
million requests and only 465 releases.  I just rebooted and:
NameSize Requests Fail Releases Pgreq Pgrel Npage Hiwat Minpg Maxpg Idle
kmem-00192   2568263800  5165 0  5165  5165 0   inf0

And vmstat showed that fre memory was down to under 4M, though the
box was essentially idle.

It was mentioned that radeondrmkms might have a big memory leak.
Every time the display changes, such as even moving the mouse, the
number of kmem-00192 requests goes way up and the number of releases
pretty much never changes.



Another pmap panic

2020-03-20 Thread Chavdar Ivanov
Hi,

Overnight, while doing pkg_rolling-replace, my 'server' got:
...
panic: kernel diagnostic assertion "ptp->wire_count == 1" failed: file
  "/home/sysbuild/src/sys/arch/x86/x86/pmap.c", line 2232

cpu0: Begin traceback...
vpanic() at netbsd:vpanic+0x178
kern_assert() at netbsd:kern_assert+0x48
pmap_unget_ptp() at netbsd:pmap_unget_ptp+0x1f1
pmap_get_ptp() at netbsd:pmap_get_ptp+0x300
pmap_enter_ma() at netbsd:pmap_enter_ma+0x6fb
pmap_enter_default() at netbsd:pmap_enter_default+0x29
uvm_fault_internal() at netbsd:uvm_fault_internal+0xf2e
trap() at netbsd:trap+0x50a
--- trap (number 6) ---
7f7eec2007e0:
cpu0: End traceback...

dumping to dev 168,2 (offset=8, size=5225879):
...


-- 



Another pmap panic

2017-11-26 Thread Chavdar Ivanov
➜  crash crash -M netbsd.1.core -N netbsd.1
Crash version 8.99.7, image version 8.99.7.
System panicked: prevented access to 0x10 (SMAP)
Backtrace from time of crash is available.
crash> bt
_KERNEL_OPT_NARCNET() at 0
?() at e40043fb
vpanic() at vpanic+0x149
snprintf() at snprintf
trap() at trap+0xbea
--- trap (number 6) ---
pmap_enter_ma() at pmap_enter_ma+0xe2a
pmap_enter_default() at pmap_enter_default+0x1d
udv_fault() at udv_fault+0x151
uvm_fault_internal() at uvm_fault_internal+0x6d4
trap() at trap+0x3f0
--- trap (number 6) ---
73493a809eaf:
crash> ^D#



Happens when I start Xorg under Virtualbox. The same seems to work as good
as before on my T61p.

Aside of this, I am still getting unresponsive mouse in a rather strange
way. It doesn't work if I use 'startx', but if I start /etc/rc.d/gdm and
manage to move it before the login window appears, it is ok. Go figure...

Chavdar Ivanov