Re: Sparc t5120 firmware problem

2015-02-02 Thread Stefan Johansson
 Hello!
  
 I have a Sun Sparc t5120 that cannot start ldomd after a firmware
 upgrade. It’s possible to start ldomd before I have divided the
 machine into several guest domains. Afterwards it just hangs when
 trying to start ldomd and the machine is unresponsive (answers on
 ping though). Ldomd does not give any error messages.
 
 I've got almost the same hardware as you but I show a slightly
 newer version of the sysfw:
 
 Properties:
 ...
 hypervisor_version = Hypervisor 1.10.7.g 2014/07/10 11:46
 macaddress = 00:21:28:16:2d:a8
 maxbootfail = 3
 obp_version = OpenBoot 4.33.6.f 2014/07/10 10:23
 post_version = POST 4.33.6.f 2014/07/10 10:32
 send_break_action = (Cannot show property)
 status = Solaris running
 sysfw_version = Sun System Firmware 7.4.8.a 2014/10/12 09:18
 
 Getting older versions of the firmware without a support contract is a
 pain... But I'll try tomorrow for you. Do you know what version you
 where at before you upgraded? How old you want to try? 

I really appreciate your help!
I was at version 7.2.7.d but I think it would be safe to go to version 7.2.11
which is the latest one in the 7.2 series. After that the hypervisor version 
goes
from 1.7.x to 1.9.x (in firmware version 7.3.0). 
I don’t know if my problem is caused by a newer version of the hypervisor.
Maybe one of the developers can answer which versions are supported by OpenBSD?

 
 Don't read too much into the fact that mine is working fine since I'm
 running slowaris on the cdom with OpenBSD-stable in ldoms so it's
 probably apples and oranges. The three OpenBSD ldoms I run are all
 working fabulously though (Thanks everyone that worked on the sun4v
 stuff).
 
 Up until now how has OpenBSD been doing for the primary? I'd love to
 ditch Solaris there too but I've got a large NAS hanging off this
 box and I rather like managing it with zfs.



Sparc t5120 firmware problem

2015-02-01 Thread Stefan Johansson
Hello!

I have a Sun Sparc t5120 that cannot start ldomd after a firmware upgrade.
It’s possible to start ldomd before I have divided the machine into several 
guest domains.
Afterwards it just hangs when trying to start ldomd and the machine is 
unresponsive (answers on ping though).
Ldomd does not give any error messages.

Does anyone have any idea why?
Right now my plan is to downgrade the firmware. Does anyone have a known 
working version to provide me?
I only have version 7.4.8 and nothing older.

Output from showhost in ALOM:
Sun System Firmware 7.4.8 2014/07/10 13:15

Host flash versions:
 Hypervisor 1.10.7.g 2014/07/10 11:46
 OpenBoot 4.33.6.f 2014/07/10 10:23
 POST 4.33.6.f 2014/07/10 10:32

My ldom.conf:
domain primary {
  vcpu 16
  memory 8064M
}

domain ldom1 {
  vcpu 16
  memory 8G
  vdisk /dev/sd0c
  vdisk /home/ldom/ldom1/miniroot.fs
  vnet
  vnet
}

domain ldom2 {
  vcpu 16
  memory 8G
  vdisk /dev/sd2c
  vdisk /home/ldom/ldom2/miniroot.fs
  vnet
  vnet
}

domain ldom3 {
  vcpu 16
  memory 8G
  vdisk /dev/sd3c
  vdisk /home/ldom/ldom3/miniroot.fs
  vnet
  vnet
}

dmesg from primary domain:
console is /virtual-devices@100/console@1
Copyright (c) 1982, 1986, 1989, 1991, 1993
 The Regents of the University of California.  All rights reserved.
Copyright (c) 1995-2015 OpenBSD. All rights reserved.  http://www.OpenBSD.org

OpenBSD 5.7-beta (GENERIC.MP) #447: Thu Jan 22 18:38:23 MST 2015
 dera...@sparc64.openbsd.org:/usr/src/sys/arch/sparc64/compile/GENERIC.MP
real mem = 8455716864 (8064MB)
avail mem = 8303960064 (7919MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root: SPARC Enterprise T5120
cpu0 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz
cpu1 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz
cpu2 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz
cpu3 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz
cpu4 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz
cpu5 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz
cpu6 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz
cpu7 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz
cpu8 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz
cpu9 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz
cpu10 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz
cpu11 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz
cpu12 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz
cpu13 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz
cpu14 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz
cpu15 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz
vbus0 at mainbus0
flashprom at vbus0 not configured
tpm at vbus0 not configured
cbus0 at vbus0
vldc0 at cbus0
vldcp0 at vldc0 chan 0x14: ivec 0x228, 0x229 channel spds
sunvts at vldc0 chan 0x6 not configured
sunmc at vldc0 chan 0x7 not configured
explorer at vldc0 chan 0x8 not configured
led at vldc0 chan 0x9 not configured
flashupdate at vldc0 chan 0xa not configured
ipmi at vldc0 chan 0xc not configured
system-management at vldc0 chan 0xd not configured
vldc1 at cbus0
spfma at vldc1 chan 0x5 not configured
vldc2 at cbus0
vldcp1 at vldc2 chan 0x0: ivec 0x200, 0x201 channel hvctl
ldom-primary at vldc2 chan 0x1 not configured
fmactl at vldc2 chan 0x3 not configured
vldcp2 at vldc2 chan 0x19: ivec 0x232, 0x233 channel ldom-ldom1
vldcp3 at vldc2 chan 0x1f: ivec 0x23e, 0x23f channel ldom-ldom2
vldcp4 at vldc2 chan 0x25: ivec 0x24a, 0x24b channel ldom-ldom3
vldc3 at cbus0
ldmfma at vldc3 chan 0x4 not configured
virtual-domain-service at cbus0 not configured
vcc0 at cbus0
vcctty0 at vcc0 chan 0x18: ivec 0x230, 0x231 domain ldom1
vcctty1 at vcc0 chan 0x1e: ivec 0x23c, 0x23d domain ldom2
vcctty2 at vcc0 chan 0x24: ivec 0x248, 0x249 domain ldom3
vds0 at cbus0
vdsp0 at vds0 chan 0x1a: ivec 0x234, 0x235
vdsp1 at vds0 chan 0x1b: ivec 0x236, 0x237
vdsp2 at vds0 chan 0x20: ivec 0x240, 0x241
vdsp3 at vds0 chan 0x21: ivec 0x242, 0x243
vdsp4 at vds0 chan 0x26: ivec 0x24c, 0x24d
vdsp5 at vds0 chan 0x27: ivec 0x24e, 0x24f
vsw0 at cbus0
vnet0 at vsw0 chan 0x1c: ivec 0x238, 0x239
vnet1 at vsw0 chan 0x1d: ivec 0x23a, 0x23b
vnet2 at vsw0 chan 0x22: ivec 0x244, 0x245
vnet3 at vsw0 chan 0x23: ivec 0x246, 0x247
vnet4 at vsw0 chan 0x28: ivec 0x250, 0x251
vnet5 at vsw0 chan 0x29: ivec 0x252, 0x253
vrng0 at vbus0
vcons0 at vbus0: ivec 0x111, console
vrtc0 at vbus0
vpci0 at mainbus0: bus 2 to 18, dvma map 8000-
pci0 at vpci0
ppb0 at pci0 dev 0 function 0 PLX PEX 8533 rev 0xaa
pci1 at ppb0 bus 3
ppb1 at pci1 dev 1 function 0 PLX PEX 8533 rev 0xaa
pci2 at ppb1 bus 4
ppb2 at pci2 dev 0 function 0 PLX PEX 8517 rev 0xad
pci3 at ppb2 bus 5
ppb3 at pci3 dev 1 function 0 PLX PEX 8517 rev 0xad
pci4 at ppb3 bus 6
ppb4 at pci4 dev 0 function 0 PLX PEX 8112 rev 0xaa
pci5 at ppb4 bus 7
ohci0 at pci5 dev 0 function 0 NEC USB rev 0x43: ivec 0x16, version 1.0

Routerboard RB600 and hifn(4)

2012-01-23 Thread Stefan Johansson
Hello!

Does anyone on the list have experience with a hifn(4) card (such as the
Soekris vpn1411)
in a Routerboard RB600?
I'm using it for an ipsec tunnel (isakmpd between RB600 and an other OpenBSD
i386 box)
and would like to know if it will give me any performance increase before I
purchase one?

Today I get about 12 Mb/s through the tunnel and 60-70 Mb/s outside.
I am measuring this with iperf on OpenBSD 5.0 and the RB600 CPU is set to
533MHz.

/Stefan



fmt_scaled, linking problem

2010-10-23 Thread Stefan Johansson
Hello!

I am wondering if anyone else has seen this problem in the latest current \
snapshots.
I have a C-program that uses the fmt_scaled function from util.h.
This program compiled and linked fine a couple of weeks ago but now I get the
\
following error:

/tmp//ccUmAX34.o(.text+0x34): In function `main':
: undefined reference to `fmt_scaled'
collect2: ld returned 1 exit status


It will compile if I run `gcc -c` without linking.
Just to demonstrate i tried this little piece of code:

#include errno.h
#include stdio.h
#include util.h

int main(int argc, char *argv[]) {
char buf[FMT_SCALED_STRSIZE];
   long long ninput = 10483892;
   if (fmt_scaled(ninput, buf) == 0)
printf(%lld - %s\n, ninput, buf);
else
   fprintf(stderr, fmt scaled failed (errno %d), errno);
}

Any hints would be very much appreciated.

Here is my dmesg:
OpenBSD 4.8-current (GENERIC.MP) #479: Thu Oct 21 00:10:43 MDT 2010
   dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
cpu0: Pentium(R) Dual-Core CPU E5400 @ 2.70GHz (GenuineIntel 686-class) 2.71
GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,EST,TM2,SSSE3,CX1
6,xTPR,PDCM,XSAVE
real mem  = 1071947776 (1022MB)
avail mem = 1044389888 (996MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 05/15/09, BIOS32 rev. 0 @ 0xfac90,
SMBIOS rev. 2.5 @ 0x3ff9c000 (46 entries)
bios0: vendor Dell Inc. version 1.4.3 date 05/15/2009
bios0: Dell Inc. PowerEdge R200
acpi0 at bios0: rev 2
acpi0: sleep states S0 S4 S5
acpi0: tables DSDT FACP APIC SPCR HPET MCFG WD__ SLIC ERST HEST BERT EINJ SSDT
SSDT SSDT
acpi0: wakeup devices PCI0(S5)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: apic clock running at 200MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Pentium(R) Dual-Core CPU E5400 @ 2.70GHz (GenuineIntel 686-class) 2.71
GHz
cpu1:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,EST,TM2,SSSE3,CX1
6,xTPR,PDCM,XSAVE
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 2
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (PEX1)
acpiprt2 at acpi0: bus 2 (SBE0)
acpiprt3 at acpi0: bus 3 (SBE4)
acpiprt4 at acpi0: bus 4 (SBE5)
acpiprt5 at acpi0: bus 5 (COMP)
acpicpu0 at acpi0: PSS
acpicpu1 at acpi0: PSS
bios0: ROM list: 0xc/0x9000 0xc9000/0x1000 0xca000/0x1800 0xcb800/0x5c00
0xec000/0x4000!
ipmi at mainbus0 not configured
cpu0: Enhanced SpeedStep 2701 MHz: speeds: 2700, 2400, 2200, 2000, 1800, 1600,
1400, 1200 MHz
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 Intel 3200/3210 Host rev 0x01
ppb0 at pci0 dev 1 function 0 Intel 3200/3210 PCIE rev 0x01: apic 2 int 16
(irq 15)
pci1 at ppb0 bus 1
mpi0 at pci1 dev 0 function 0 Symbios Logic SAS1068E rev 0x08: apic 2 int 16
(irq 15)
scsibus0 at mpi0: 112 targets
sd0 at scsibus0 targ 0 lun 0: Dell, VIRTUAL DISK, 1028 SCSI3 0/direct fixed
sd0: 152064MB, 512 bytes/sec, 311427072 sec total
sd1 at scsibus0 targ 4 lun 0: ATA, WDC WD15EARS-00Z, 0A80 SCSI3 0/direct
fixed
sd1: 1430799MB, 512 bytes/sec, 2930277168 sec total
sd2 at scsibus0 targ 6 lun 0: ATA, ST31500341AS, CC1G SCSI3 0/direct fixed
sd2: 1430799MB, 512 bytes/sec, 2930277168 sec total
sd3 at scsibus0 targ 7 lun 0: ATA, WDC WD10EADS-00M, 0A01 SCSI3 0/direct
fixed
sd3: 953869MB, 512 bytes/sec, 1953525168 sec total
ppb1 at pci0 dev 28 function 0 Intel 82801I PCIE rev 0x02: apic 2 int 16
(irq 15)
pci2 at ppb1 bus 2
ppb2 at pci0 dev 28 function 4 Intel 82801I PCIE rev 0x02
pci3 at ppb2 bus 3
bge0 at pci3 dev 0 function 0 Broadcom BCM5721 rev 0x21, BCM5750 C1
(0x4201): apic 2 int 16 (irq 15), address a4:ba:db:df:ae:2a
brgphy0 at bge0 phy 1: BCM5750 10/100/1000baseT PHY, rev. 0
ppb3 at pci0 dev 28 function 5 Intel 82801I PCIE rev 0x02
pci4 at ppb3 bus 4
bge1 at pci4 dev 0 function 0 Broadcom BCM5721 rev 0x21, BCM5750 C1
(0x4201): apic 2 int 17 (irq 14), address a4:ba:db:df:ae:2b
brgphy1 at bge1 phy 1: BCM5750 10/100/1000baseT PHY, rev. 0
uhci0 at pci0 dev 29 function 0 Intel 82801I USB rev 0x02: apic 2 int 21
(irq 11)
uhci1 at pci0 dev 29 function 1 Intel 82801I USB rev 0x02: apic 2 int 20
(irq 10)
uhci2 at pci0 dev 29 function 2 Intel 82801I USB rev 0x02: apic 2 int 21
(irq 11)
ehci0 at pci0 dev 29 function 7 Intel 82801I USB rev 0x02: apic 2 int 21
(irq 11)
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1
ppb4 at pci0 dev 30 function 0 Intel 82801BA Hub-to-PCI rev 0x92
pci5 at ppb4 bus 5
vga1 at pci5 dev 5 function 0 ATI ES1000 rev 0x02
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
radeondrm0 at vga1: apic 2 int 19 

pagedaemon: deadlock detected! on 4.3 macppc

2008-11-10 Thread Stefan Johansson

Hello!

My G4 mac running OpenBSD 4.3 hung today with the following message in  
dmesg:


deadlock detected!
pagedaemon: deadlock detected!

The above repeated several times.
I have tried looking in the log files for some explanation but I  
haven't found any clue myself.
Maybe someone here could guide me in the right direction or knows what  
happened based on the attached dmesg and /var/log/messages



Excerpt from /var/log/messages at the time of the incident:

Nov 10 12:41:29 g4 openvpn[25511]: Data Channel Encrypt: Cipher 'BF- 
CBC' initialized with 128 bit key
Nov 10 12:41:29 g4 openvpn[25511]: Data Channel Encrypt: Using 160 bit  
message hash 'SHA1' for HMAC authentication
Nov 10 12:41:29 g4 openvpn[25511]: Data Channel Decrypt: Cipher 'BF- 
CBC' initialized with 128 bit key
Nov 10 12:41:29 g4 openvpn[25511]: Data Channel Decrypt: Using 160 bit  
message hash 'SHA1' for HMAC authentication
Nov 10 12:41:29 g4 openvpn[25511]: Control Channel: TLSv1, cipher  
TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA

Nov 10 16:56:55 g4 syslogd: start
Nov 10 16:56:55 g4 /bsd: eadlock detected!
Nov 10 16:56:55 g4 /bsd: pagedaemon: deadlock detected!
Nov 10 16:56:55 g4 last message repeated 103 times
Nov 10 16:56:55 g4 /bsd: [ using 395092 bytes of bsd ELF symbol table ]
Nov 10 16:56:55 g4 /bsd: console out [ATY,BlueStone_A]console in  
[keyboard] USB found
Nov 10 16:56:55 g4 /bsd: using parent ATY,BlueStoneParent:: memaddr  
9800 size 800, : consaddr 9c008000, : ioaddr 9002, size  
2: memtag 8000, iot

ag 8000: width 1680 linebytes 1792 height 1050 depth 8

dmesg:

deadlock detected!
pagedaemon: deadlock detected!
pagedaemon: deadlock detected!
...
#repeated on multiple lines

pagedaemon: deadlock detected!
[ using 395092 bytes of bsd ELF symbol table ]
console out [ATY,BlueStone_A]console in [keyboard] USB found
using parent ATY,BlueStoneParent:: memaddr 9800 size 800, :  
consaddr 9c008000, : ioaddr 9002, size 2: memtag 8000, iotag  
8000: width 1680 linebytes 1792 height 1050 depth 8

Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California.  All rights  
reserved.

Copyright (c) 1995-2008 OpenBSD. All rights reserved.  http://www.OpenBSD.org

OpenBSD 4.3 (GENERIC) #1670: Wed Mar 12 11:12:33 MDT 2008
[EMAIL PROTECTED]:/usr/src/sys/arch/macppc/compile/GENERIC
real mem = 1073741824 (1024MB)
avail mem = 1033433088 (985MB)
mainbus0 at root: model PowerMac3,5
cpu0 at mainbus0: 7450 (Revision 0x201): 799 MHz: 256KB L2 cache
mem0 at mainbus0
spdmem0 at mem0: 256MB SDRAM non-parity PC133CL2
spdmem1 at mem0: 512MB SDRAM non-parity PC133CL3
spdmem2 at mem0: 256MB SDRAM non-parity PC133CL2
memc0 at mainbus0: uni-n
kiic0 at memc0 offset 0xf8001000
iic0 at kiic0
mpcpcibr0 at mainbus0 pci: uni-north, Revision 0xff
pci0 at mpcpcibr0 bus 0
pchb0 at pci0 dev 11 function 0 Apple Uni-N2 AGP rev 0x00
vgafb0 at pci0 dev 16 function 0 ATI Radeon 7500 QW rev 0x00, mmio
wsdisplay0 at vgafb0 mux 1: console (std, vt100 emulation)
mpcpcibr1 at mainbus0 pci: uni-north, Revision 0x0
pci1 at mpcpcibr1 bus 0
pchb1 at pci1 dev 11 function 0 Apple Uni-N2 Host rev 0x00
re0 at pci1 dev 18 function 0 D-Link Systems DGE-528T rev 0x10:  
RTL8169/8110SB (0x1000), irq 52, address 00:21:91:11:da:ce

rgephy0 at re0 phy 7: RTL8169S/8110S PHY, rev. 3
ahc0 at pci1 dev 19 function 0 Adaptec AIC-7850 rev 0x03: irq 53
scsibus0 at ahc0: 8 targets
macobio0 at pci1 dev 23 function 0 Apple Keylargo rev 0x03
openpic0 at macobio0 offset 0x4: version 0x4614 little endian
macgpio0 at macobio0 offset 0x50
macgpio1 at macgpio0 irq 47
programmer-switch at macgpio0 not configured
gpio5 at macgpio0 not configured
gpio6 at macgpio0 not configured
gpio11 at macgpio0 not configured
extint-gpio15 at macgpio0 not configured
extint-gpio16 at macgpio0 not configured
escc-legacy at macobio0 offset 0x12000 not configured
zsc0 at macobio0 offset 0x13000: irq 22,23
zstty0 at zsc0 channel 0
zstty1 at zsc0 channel 1
tumbler0 at macobio0 offset 0x1: irq 30,1,2
timer at macobio0 offset 0x15000 not configured
adb0 at macobio0 offset 0x16000 irq 25: via-pmu, 0 targets
apm0 at adb0: battery flags 0x9, 0% charged
kiic1 at macobio0 offset 0x18000
iic1 at kiic1
wdc0 at macobio0 offset 0x1f000 irq 19: DMA
wd0 at wdc0 channel 0 drive 0: ST340016A
wd0: 16-sector PIO, LBA, 39097MB, 80070686 sectors
wd1 at wdc0 channel 0 drive 1: IC35L090AVV207-0
wd1: 16-sector PIO, LBA48, 78533MB, 160836480 sectors
wd0(wdc0:0:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 4
wd1(wdc0:0:1): using PIO mode 4, DMA mode 2, Ultra-DMA mode 4
wdc1 at macobio0 offset 0x2 irq 20: DMA
atapiscsi0 at wdc1 channel 0 drive 0
scsibus1 at atapiscsi0: 2 targets
cd0 at scsibus1 targ 0 lun 0: HL-DT-ST, CD-RW GCE-8240B, 1.05 SCSI0  
5/cdrom removable

atapiscsi1 at wdc1 channel 0 drive 1
scsibus2 at atapiscsi1: 2 targets
sd0 at scsibus2 targ 0 lun 0: IOMEGA, ZIP 250, 41.S SCSI0 0/direct  
removable

sd0: drive offline
cd0(wdc1:0:0): using 

Re: pagedaemon: deadlock detected! on 4.3 macppc

2008-11-10 Thread Stefan Johansson

Thank you very much!

I will update to 4.4 + patch.

/Stefan

10 nov 2008 kl. 20.44 skrev Tobias Ulmer:


On Mon, Nov 10, 2008 at 05:56:13PM +0100, Stefan Johansson wrote:

Hello!

My G4 mac running OpenBSD 4.3 hung today with the following message  
in

dmesg:

deadlock detected!
pagedaemon: deadlock detected!

The above repeated several times.
I have tried looking in the log files for some explanation but I  
haven't

found any clue myself.
Maybe someone here could guide me in the right direction or knows  
what

happened based on the attached dmesg and /var/log/messages


simplified:

It means the kernel run out of memory. When it is low on memory, the  
pagedaemon

wakes up and tries to move pages to swap and other things.
If in the process of doing that, the kernel really runs out of  
memory, it will
start to wake itself up, basically looping around the pagedaemon to  
get

some memory to free more memory...

The message tells you that it detected this situation and hopes  
that one

of your processes gives up and releases some. Usually however that
doesn't happen ;)

Update to 4.4+patches (not just release, there's an important fix you
want...).