Re: vm panic

2003-01-22 Thread Jake Burkholder
Apparently, On Thu, Jan 23, 2003 at 11:45:13AM +0800,
David Xu said words to the effect of;

 panic: lockmgr: locking against myself
 Debugger(panic)
 Stopped at Debugger+0x54: xchgl %ebx,in_Debugger.0
 dbtrace
 Debugger(c0381630,c03e4ee0,c037fd14,da447c28,1) at Debugger+0x54
 panic(c037fd14,0,c037fc88,eb,1fb) at panic+0xab
 lockmgr(c138e85c,2,0,c3c150e0,c3c1514) at lockmgr+0x512
 _vm_map_lock_read(c138e280,c039bc27,896,238d3c,527) at _vm_map_lock_read+0x5a
 vm_map_check_protection(c138e80,826400,826500,2,c03b1980) at 
vm_map_check_protection+0x31
 useracc(8264fc4,8,2,1,c038b1f) at useracc+0x7d
 nanosleep(c3c150e0,da447d10,c039f3e,407,2) at nonosleep+0x53
 syscall(bfbf002f,804002f,826002f,bfbffbe0,804a420) at syscall+0x28e
 Xint0x80_syscall() at Xint0x80_syscall+0x1d
 --- syscall (240, FreeBSD ELF32, nanosleep), eip = 0x280b0853, esp = 0x8264fb8, ebp 
= 0x8264fd4
 
 At the time, I am running ksetest, a kse based threaded program.
 Is the vm still not safe to run threaded program?
 
 David Xu
 

Don't know if this is the problem or not but the lockmgr code uses the
pid as the lock cookie, so it can't distinguish 2 threads from the same
process acquiring a lock.

I noticed that netbsd has fixed this for lwps.

Jake

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: VM panic

2002-08-21 Thread Mark Murray

 What kind of value do you use for N? It looks like lately the makefiles
 are too aggressive when using -j, so you end up with N * N * 2 processes
 running simultaneously. On my -current box with 128M RAM, I used -j13
 for a long time, but that runs out of swap nowadays, so I'm using -j4
 which does work.

My machine is a PentiumMMX/200 x 2 SMP. I'm slowly working down from
-j13, and I'm now at -j5 with the same panic.

M
-- 
o   Mark Murray
\_
O.\_Warning: this .sig is umop ap!sdn

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: VM panic

2002-08-19 Thread Jason



Matthew N. Dodd wrote:

On Sat, 17 Aug 2002, Mark Murray wrote:
  

If I do a make -jN world build on my dual MMX/200 box, I usually end
up in tears (well, a panic anyway). This is completely reproducible, and
the panic always happens in swapout_procs while vmdaemon is running.

Anyone else getting this?



I'm amazed you've got a dual Pentium running -CURRENT at all.

both of mine haven't worked with SMP kernels for months. (dual P54C and
dual P55C).

  

Wierd, I have it running just peachy on a dual P3 900 box

Jason


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: VM panic

2002-08-19 Thread Chris Hedley

On Mon, 19 Aug 2002, Jason wrote:
 Wierd, I have it running just peachy on a dual P3 900 box

It runs mostly okay on my dual P3/600, although for the last couple of
months it has a tendency to panic with a bdwrite: buffer is not busy on
average 2-3 times a day (per approx 15 hour run)  Such is the price of
staying on the bleeding edge, I suppose.  :)

Chris.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: VM panic

2002-08-19 Thread Matthew N. Dodd

On Mon, 19 Aug 2002, Jason wrote:
 Wierd, I have it running just peachy on a dual P3 900 box

Just so nobody else replies to this with something similar we're talking
about PENTIUMS.

Not the P3, P2, Alpha or anything else.

-- 
| Matthew N. Dodd  | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD  |
| [EMAIL PROTECTED] |   2 x '84 Volvo 245DL| ix86,sparc,pmax |
| http://www.jurai.net/~winter |  For Great Justice!  | ISO8802.5 4ever |


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: VM panic

2002-08-19 Thread Terry Lambert

Matthew N. Dodd wrote:
 On Mon, 19 Aug 2002, Jason wrote:
  Wierd, I have it running just peachy on a dual P3 900 box
 
 Just so nobody else replies to this with something similar we're talking
 about PENTIUMS.
 
 Not the P3, P2, Alpha or anything else.

Yes.  My ASUS Dual P90 machine has the same problem.  I just thought
it was the MP Spec compliance level of the BIOS, and gave up running
-current.  I guess it's not just me.  8-(.

-- Terry

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: VM panic

2002-08-19 Thread Matthew N. Dodd

On Mon, 19 Aug 2002, Terry Lambert wrote:
 Yes.  My ASUS Dual P90 machine has the same problem.  I just thought it
 was the MP Spec compliance level of the BIOS, and gave up running
 -current.  I guess it's not just me.  8-(.

Its likely that we've got the same motherboard.

Mine is a PCI/E-P54NP4 running 133s clocked at 120.

I've also got a Tyan S1564D running a pair of 166MMX CPUs.

It doesn't seem to be related to drivers or to the compiler.

I haven't yet ruled out other parts of the toolchain.

My last good build was 1 March 2002.

Checking out a tree even as far back as mid-Feb doesn't yeild a good
kernel though.

I'm at a loss.

-- 
| Matthew N. Dodd  | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD  |
| [EMAIL PROTECTED] |   2 x '84 Volvo 245DL| ix86,sparc,pmax |
| http://www.jurai.net/~winter |  For Great Justice!  | ISO8802.5 4ever |


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: VM panic

2002-08-18 Thread Matthew N. Dodd

On Sat, 17 Aug 2002, Mark Murray wrote:
 If I do a make -jN world build on my dual MMX/200 box, I usually end
 up in tears (well, a panic anyway). This is completely reproducible, and
 the panic always happens in swapout_procs while vmdaemon is running.

 Anyone else getting this?

I'm amazed you've got a dual Pentium running -CURRENT at all.

both of mine haven't worked with SMP kernels for months. (dual P54C and
dual P55C).

-- 
| Matthew N. Dodd  | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD  |
| [EMAIL PROTECTED] |   2 x '84 Volvo 245DL| ix86,sparc,pmax |
| http://www.jurai.net/~winter |  For Great Justice!  | ISO8802.5 4ever |


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: VM panic

2002-08-18 Thread David Wolfskill

Date: Sun, 18 Aug 2002 20:44:52 -0400 (EDT)
From: Matthew N. Dodd [EMAIL PROTECTED]

On Sat, 17 Aug 2002, Mark Murray wrote:
 If I do a make -jN world build on my dual MMX/200 box, I usually end
 up in tears (well, a panic anyway). This is completely reproducible, and
 the panic always happens in swapout_procs while vmdaemon is running.

 Anyone else getting this?

I'm not.

I'm amazed you've got a dual Pentium running -CURRENT at all.

I'm not.

both of mine haven't worked with SMP kernels for months. (dual P54C and
dual P55C).

freebeast(5.0-C)[2] uname -a
FreeBSD freebeast.catwhisker.org 5.0-CURRENT FreeBSD 5.0-CURRENT #4: Sun Aug 18 
09:16:14 PDT 2002 
[EMAIL PROTECTED]:/common/S4/obj/usr/src/sys/FREEBEAST  i386

Copyright (c) 1992-2002 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 5.0-CURRENT #4: Sun Aug 18 09:16:14 PDT 2002
[EMAIL PROTECTED]:/common/S4/obj/usr/src/sys/FREEBEAST
Preloaded elf kernel /boot/kernel/kernel at 0xc0496000.
Preloaded elf module /boot/kernel/acpi.ko at 0xc04960a8.
Calibrating clock(s) ... TSC clock: 876474687 Hz, i8254 clock: 1193294 Hz
CLK_USE_I8254_CALIBRATION not specified - using default frequency
Timecounter i8254  frequency 1193182 Hz
CLK_USE_TSC_CALIBRATION not specified - using old calibration method
CPU: Pentium III/Pentium III Xeon/Celeron (876.40-MHz 686-class CPU)
  Origin = GenuineIntel  Id = 0x68a  Stepping = 10
  Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CM
OV,PAT,PSE36,MMX,FXSR,SSE
real memory  = 536805376 (524224K bytes)
Physical memory chunk(s):
0x1000 - 0x0009efff, 647168 bytes (158 pages)
0x004c - 0x1ffe7fff, 531791872 bytes (129832 pages)
avail memory = 515960832 (503868K bytes)
Programming 24 pins in IOAPIC #0
IOAPIC #0 intpin 2 - irq 0
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
 cpu0 (BSP): apic id:  0, version: 0x00040011, at 0xfee0
 cpu1 (AP):  apic id:  1, version: 0x00040011, at 0xfee0
 io0 (APIC): apic id:  2, version: 0x00178011, at 0xfec0
bios32: Found BIOS32 Service Directory header at 0xc00faf20
bios32: Entry = 0xfb390 (c00fb390)  Rev = 0  Len = 1
pcibios: PCI BIOS entry at 0xf+0xb3c0
pnpbios: Found PnP BIOS data at 0xc00fbde0
pnpbios: Entry = f:be10  Rev = 1.0
Other BIOS signatures found:
null: null device, zero device
random: entropy source
mem: memory  I/O
Pentium Pro MTRR support enabled
SMP: CPU0 bsp_apic_configure():
 lint0: 0x00010700 lint1: 0x0400 TPR: 0x0010 SVR: 0x01ff
pci_open(1):mode 1 addr port (0x0cf8) is 0x8060
pci_open(1a):   mode1res=0x8000 (0x8000)
pci_cfgcheck:   device 0 [class=06] [hdr=00] is there (id=30911106)
Using $PIR table, 8 entries at 0xc00fde30


More info available on request; I didn't want to spam the list too much
(this time).

Cheers,
david   (links to my resume at http://www.catwhisker.org/~david)
-- 
David H. Wolfskill  [EMAIL PROTECTED]
To paraphrase David Hilbert, there can be no conflicts between the
discipline of systems administration and Microsoft, since they have
nothing in common.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: VM panic

2002-08-18 Thread Yuri Victorovich

 I'm amazed you've got a dual Pentium running -CURRENT at all.

 both of mine haven't worked with SMP kernels for months. (dual P54C and
 dual P55C).

I am running SMP CURRENT kernel on 4-Alpha processors .  No problems
for a lot of months.

Yuri.



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: VM panic

2002-08-18 Thread Dan Nelson

In the last episode (Aug 18), David Wolfskill said:
 From: Matthew N. Dodd [EMAIL PROTECTED]
  I'm amazed you've got a dual Pentium running -CURRENT at all.
 
 I'm not.
 
  both of mine haven't worked with SMP kernels for months. (dual P54C
  and dual P55C).
 
 freebeast(5.0-C)[2] uname -a
 CPU: Pentium III/Pentium III Xeon/Celeron (876.40-MHz 686-class CPU)
   Origin = GenuineIntel  Id = 0x68a  Stepping = 10
   
Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE

A Pentium III is not a Pentium, by a long shot.  Or is it the other way
around. :)  P54C is your classic 586 Pentium. P55C is a Pentium/MMX.

-- 
Dan Nelson
[EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: VM panic

2002-08-17 Thread John Hay

 
 If I do a make -jN world build on my dual MMX/200 box, I usually end
 up in tears (well, a panic anyway). This is completely reproducible, and
 the panic always happens in swapout_procs while vmdaemon is running.
 
 Anyone else getting this?

What kind of value do you use for N? It looks like lately the makefiles
are too aggressive when using -j, so you end up with N * N * 2 processes
running simultaneously. On my -current box with 128M RAM, I used -j13
for a long time, but that runs out of swap nowadays, so I'm using -j4
which does work.

John
-- 
John Hay -- [EMAIL PROTECTED] / [EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message