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 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...).



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...).




Re: pagedaemon: deadlock detected

2007-08-03 Thread Timo Schoeler

thus Chris Kuethe spake:

On 8/2/07, Timo Schoeler [EMAIL PROTECTED] wrote:

hi,

i have an amd64 system running for about six months now flawlessly
(however, due to following -current, not with uptimes 10 days).

today it crashed twice when i had two torrents active (not very big
ones, one 900MByte and one 1300MByte in size -- i did use this machine
for far bigger ones, with rtorrent running several instances in
parallel, without problems).


check out PRs 5517 and 5496 - they include a diff which may help you.

CK


hi,

i applied the patch to a -current system checked out and built about 
twelve hours ago; since then the machine runs happily with both rtorrent 
instances.


if i can provide more information on this issue especially with regards 
to why it did *not* fix the problem on Frank Denis' Net4801, please let 
me know.


thanks again  best,

timo



pagedaemon: deadlock detected

2007-08-02 Thread Timo Schoeler

hi,

i have an amd64 system running for about six months now flawlessly 
(however, due to following -current, not with uptimes 10 days).


today it crashed twice when i had two torrents active (not very big 
ones, one 900MByte and one 1300MByte in size -- i did use this machine 
for far bigger ones, with rtorrent running several instances in 
parallel, without problems).


the hardware is okay, i'm sure it is; the machine uses ECC RAM and is 
cooled very good (besides running on an Athlon64 3500+ EE SFF, which 
means a TDP of 35Watt) with several big fans and a gigantic 
copper/heatpipe heatspreader on the CPU to make it SILENT.


unfortunately, the machine does NOT have a serial port that could 
provide some more information, i'm stuck on the console which spits out:


'pagedaemon: deadlock detected'

in very high speed. i can still change between the tty's, but cannot 
type to login or anything else. ssh is dead. apache dies. didn't try 
ICMP, though.


dmesg applied -- thanks for any hint!

timo

---

OpenBSD 4.2-beta (GENERIC) #6: Tue Jul 31 10:43:55 CEST 2007
[EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/GENERIC
real mem = 1055444992 (1006MB)
avail mem = 1013542912 (966MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.3 @ 0xf (70 entries)
bios0: ASUSTek Computer INC. M2NPV-VM
acpi0 at mainbus0: rev 0
acpi0: tables DSDT FACP SSDT MCFG APIC
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 4 (HUB0)
acpicpu0 at acpi0 PSS
acpicpu1 at acpi0
acpitz0 at acpi0, critical temperature: 75 degC
acpibtn0 at acpi0: PWRB
cpu0 at mainbus0: (uniprocessor)
cpu0: AMD Athlon(tm) 64 Processor 3500+, 2204.92 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,CX16,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW
cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 
64b/line 16-way L2 cache

cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative
cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative
cpu0: PowerNow! K8 2204 MHz: speeds: 2200 2000 1800 1000 MHz
pci0 at mainbus0 bus 0: configuration mode 1
NVIDIA C51 Host rev 0xa2 at pci0 dev 0 function 0 not configured
NVIDIA C51 Memory rev 0xa2 at pci0 dev 0 function 1 not configured
NVIDIA C51 Memory rev 0xa2 at pci0 dev 0 function 2 not configured
NVIDIA C51 Memory rev 0xa2 at pci0 dev 0 function 3 not configured
NVIDIA C51 Memory rev 0xa2 at pci0 dev 0 function 4 not configured
NVIDIA C51 Memory rev 0xa2 at pci0 dev 0 function 5 not configured
NVIDIA C51 Memory rev 0xa2 at pci0 dev 0 function 6 not configured
NVIDIA C51 Memory rev 0xa2 at pci0 dev 0 function 7 not configured
ppb0 at pci0 dev 2 function 0 NVIDIA C51 PCIE rev 0xa1
pci1 at ppb0 bus 1
ppb1 at pci0 dev 3 function 0 NVIDIA C51 PCIE rev 0xa1
pci2 at ppb1 bus 2
ppb2 at pci0 dev 4 function 0 NVIDIA C51 PCIE rev 0xa1
pci3 at ppb2 bus 3
vga1 at pci0 dev 5 function 0 NVIDIA GeForce 6150 rev 0xa2
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
NVIDIA MCP51 Host rev 0xa2 at pci0 dev 9 function 0 not configured
pcib0 at pci0 dev 10 function 0 NVIDIA MCP51 ISA rev 0xa3
nviic0 at pci0 dev 10 function 1 NVIDIA MCP51 SMBus rev 0xa3
iic0 at nviic0
iic1 at nviic0
NVIDIA MCP51 Memory rev 0xa3 at pci0 dev 10 function 2 not configured
ohci0 at pci0 dev 11 function 0 NVIDIA MCP51 USB rev 0xa3: irq 5, 
version 1.0, legacy support

ehci0 at pci0 dev 11 function 1 NVIDIA MCP51 USB rev 0xa3: irq 10
usb0 at ehci0: USB revision 2.0
uhub0 at usb0: NVIDIA EHCI root hub, rev 2.00/1.00, addr 1
pciide0 at pci0 dev 13 function 0 NVIDIA MCP51 IDE rev 0xa1: DMA, 
channel 0 configured to compatibility, channel 1 configured to compatibility

pciide0: channel 0 disabled (no drives)
atapiscsi0 at pciide0 channel 1 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: _NEC, DVD_RW ND-4570A, 1.02 SCSI0 
5/cdrom removable

cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
pciide1 at pci0 dev 14 function 0 NVIDIA MCP51 SATA rev 0xa1: DMA
pciide1: using irq 5 for native-PCI interrupt
wd0 at pciide1 channel 0 drive 0: WDC WD2500YD-01NVB1
wd0: 16-sector PIO, LBA48, 239372MB, 490234752 sectors
wd0(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 5
pciide2 at pci0 dev 15 function 0 NVIDIA MCP51 SATA rev 0xa1: DMA
pciide2: using irq 11 for native-PCI interrupt
ppb3 at pci0 dev 16 function 0 NVIDIA MCP51 PCI-PCI rev 0xa2
pci4 at ppb3 bus 4
TI TSB43AB22 FireWire rev 0x00 at pci4 dev 5 function 0 not configured
pciide3 at pci4 dev 8 function 0 Promise PDC40718 rev 0x02: DMA
wd1 at pciide3 channel 3 drive 0: WDC WD2500YD-01NVB1
wd1: 16-sector PIO, LBA48, 239372MB, 490234752 sectors
wd1(pciide3:3:0): using BIOS timings, Ultra-DMA mode 6
pciide3: using irq 5 for native-PCI interrupt
fxp0 at pci4 dev 9 function 0 Intel 8255x rev 0x0c, i82550: irq 11, 
address 00:02:b3:8e:29:83

inphy0 at fxp0 phy 1: i82555 10/100

[followup] pagedaemon: deadlock detected

2007-08-02 Thread Timo Schoeler

hi,

maybe this is somewhat connected to kernel/5496 and kernel/5517?

i'll apply the patch and track this issue. any hints appreciated.

thanks,

timo



Re: pagedaemon: deadlock detected

2007-08-02 Thread Chris Kuethe
On 8/2/07, Timo Schoeler [EMAIL PROTECTED] wrote:
 hi,

 i have an amd64 system running for about six months now flawlessly
 (however, due to following -current, not with uptimes 10 days).

 today it crashed twice when i had two torrents active (not very big
 ones, one 900MByte and one 1300MByte in size -- i did use this machine
 for far bigger ones, with rtorrent running several instances in
 parallel, without problems).

check out PRs 5517 and 5496 - they include a diff which may help you.

CK

-- 
GDB has a 'break' feature; why doesn't it have 'fix' too?



Re: pagedaemon: deadlock detected

2007-08-02 Thread xSAPPYx
What does df -i show? maybe you filled up a disk or ran out of inodes?

On 8/2/07, Timo Schoeler [EMAIL PROTECTED] wrote:
 hi,

 i have an amd64 system running for about six months now flawlessly
 (however, due to following -current, not with uptimes 10 days).

 today it crashed twice when i had two torrents active (not very big
 ones, one 900MByte and one 1300MByte in size -- i did use this machine
 for far bigger ones, with rtorrent running several instances in
 parallel, without problems).

 the hardware is okay, i'm sure it is; the machine uses ECC RAM and is
 cooled very good (besides running on an Athlon64 3500+ EE SFF, which
 means a TDP of 35Watt) with several big fans and a gigantic
 copper/heatpipe heatspreader on the CPU to make it SILENT.

 unfortunately, the machine does NOT have a serial port that could
 provide some more information, i'm stuck on the console which spits out:

 'pagedaemon: deadlock detected'

 in very high speed. i can still change between the tty's, but cannot
 type to login or anything else. ssh is dead. apache dies. didn't try
 ICMP, though.

 dmesg applied -- thanks for any hint!

 timo

 ---

 OpenBSD 4.2-beta (GENERIC) #6: Tue Jul 31 10:43:55 CEST 2007
  [EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/GENERIC
 real mem = 1055444992 (1006MB)
 avail mem = 1013542912 (966MB)
 mainbus0 at root
 bios0 at mainbus0: SMBIOS rev. 2.3 @ 0xf (70 entries)
 bios0: ASUSTek Computer INC. M2NPV-VM
 acpi0 at mainbus0: rev 0
 acpi0: tables DSDT FACP SSDT MCFG APIC
 acpitimer0 at acpi0: 3579545 Hz, 24 bits
 acpiprt0 at acpi0: bus 0 (PCI0)
 acpiprt1 at acpi0: bus 4 (HUB0)
 acpicpu0 at acpi0 PSS
 acpicpu1 at acpi0
 acpitz0 at acpi0, critical temperature: 75 degC
 acpibtn0 at acpi0: PWRB
 cpu0 at mainbus0: (uniprocessor)
 cpu0: AMD Athlon(tm) 64 Processor 3500+, 2204.92 MHz
 cpu0:
 FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,CX16,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW
 cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB
 64b/line 16-way L2 cache
 cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative
 cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative
 cpu0: PowerNow! K8 2204 MHz: speeds: 2200 2000 1800 1000 MHz
 pci0 at mainbus0 bus 0: configuration mode 1
 NVIDIA C51 Host rev 0xa2 at pci0 dev 0 function 0 not configured
 NVIDIA C51 Memory rev 0xa2 at pci0 dev 0 function 1 not configured
 NVIDIA C51 Memory rev 0xa2 at pci0 dev 0 function 2 not configured
 NVIDIA C51 Memory rev 0xa2 at pci0 dev 0 function 3 not configured
 NVIDIA C51 Memory rev 0xa2 at pci0 dev 0 function 4 not configured
 NVIDIA C51 Memory rev 0xa2 at pci0 dev 0 function 5 not configured
 NVIDIA C51 Memory rev 0xa2 at pci0 dev 0 function 6 not configured
 NVIDIA C51 Memory rev 0xa2 at pci0 dev 0 function 7 not configured
 ppb0 at pci0 dev 2 function 0 NVIDIA C51 PCIE rev 0xa1
 pci1 at ppb0 bus 1
 ppb1 at pci0 dev 3 function 0 NVIDIA C51 PCIE rev 0xa1
 pci2 at ppb1 bus 2
 ppb2 at pci0 dev 4 function 0 NVIDIA C51 PCIE rev 0xa1
 pci3 at ppb2 bus 3
 vga1 at pci0 dev 5 function 0 NVIDIA GeForce 6150 rev 0xa2
 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
 wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
 NVIDIA MCP51 Host rev 0xa2 at pci0 dev 9 function 0 not configured
 pcib0 at pci0 dev 10 function 0 NVIDIA MCP51 ISA rev 0xa3
 nviic0 at pci0 dev 10 function 1 NVIDIA MCP51 SMBus rev 0xa3
 iic0 at nviic0
 iic1 at nviic0
 NVIDIA MCP51 Memory rev 0xa3 at pci0 dev 10 function 2 not configured
 ohci0 at pci0 dev 11 function 0 NVIDIA MCP51 USB rev 0xa3: irq 5,
 version 1.0, legacy support
 ehci0 at pci0 dev 11 function 1 NVIDIA MCP51 USB rev 0xa3: irq 10
 usb0 at ehci0: USB revision 2.0
 uhub0 at usb0: NVIDIA EHCI root hub, rev 2.00/1.00, addr 1
 pciide0 at pci0 dev 13 function 0 NVIDIA MCP51 IDE rev 0xa1: DMA,
 channel 0 configured to compatibility, channel 1 configured to compatibility
 pciide0: channel 0 disabled (no drives)
 atapiscsi0 at pciide0 channel 1 drive 0
 scsibus0 at atapiscsi0: 2 targets
 cd0 at scsibus0 targ 0 lun 0: _NEC, DVD_RW ND-4570A, 1.02 SCSI0
 5/cdrom removable
 cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
 pciide1 at pci0 dev 14 function 0 NVIDIA MCP51 SATA rev 0xa1: DMA
 pciide1: using irq 5 for native-PCI interrupt
 wd0 at pciide1 channel 0 drive 0: WDC WD2500YD-01NVB1
 wd0: 16-sector PIO, LBA48, 239372MB, 490234752 sectors
 wd0(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 5
 pciide2 at pci0 dev 15 function 0 NVIDIA MCP51 SATA rev 0xa1: DMA
 pciide2: using irq 11 for native-PCI interrupt
 ppb3 at pci0 dev 16 function 0 NVIDIA MCP51 PCI-PCI rev 0xa2
 pci4 at ppb3 bus 4
 TI TSB43AB22 FireWire rev 0x00 at pci4 dev 5 function 0 not configured
 pciide3 at pci4 dev 8 function 0 Promise PDC40718 rev 0x02: DMA
 wd1 at pciide3 channel 3 drive 0: WDC WD2500YD-01NVB1
 wd1: 16-sector PIO, LBA48, 239372MB, 490234752 sectors
 wd1(pciide3:3:0): using BIOS timings

Re: pagedaemon: deadlock detected

2007-08-02 Thread Timo Schoeler

thus xSAPPYx spake:


What does df -i show? maybe you filled up a disk or ran out of inodes?


no, the hard drives are barely used; maximum inodes used is 15% (on /); 
the rest is way lower than 10%.



On 8/2/07, Timo Schoeler [EMAIL PROTECTED] wrote:

hi,

i have an amd64 system running for about six months now flawlessly
(however, due to following -current, not with uptimes 10 days).

today it crashed twice when i had two torrents active (not very big
ones, one 900MByte and one 1300MByte in size -- i did use this machine
for far bigger ones, with rtorrent running several instances in
parallel, without problems).

the hardware is okay, i'm sure it is; the machine uses ECC RAM and is
cooled very good (besides running on an Athlon64 3500+ EE SFF, which
means a TDP of 35Watt) with several big fans and a gigantic
copper/heatpipe heatspreader on the CPU to make it SILENT.

unfortunately, the machine does NOT have a serial port that could
provide some more information, i'm stuck on the console which spits out:

'pagedaemon: deadlock detected'

in very high speed. i can still change between the tty's, but cannot
type to login or anything else. ssh is dead. apache dies. didn't try
ICMP, though.

dmesg applied -- thanks for any hint!




Re: pagedaemon: deadlock detected

2007-08-02 Thread Jean Raby
On 8/2/07, Chris Kuethe [EMAIL PROTECTED] wrote:
 On 8/2/07, Timo Schoeler [EMAIL PROTECTED] wrote:
  hi,
 
  i have an amd64 system running for about six months now flawlessly
  (however, due to following -current, not with uptimes 10 days).
 
  today it crashed twice when i had two torrents active (not very big
  ones, one 900MByte and one 1300MByte in size -- i did use this machine
  for far bigger ones, with rtorrent running several instances in
  parallel, without problems).

 check out PRs 5517 and 5496 - they include a diff which may help you.

I had several similar cases with an Apple macmini (i386),  also
running a couple of rtorrent instances.
Needless to say, there is no serial console on this box...
so i didn't see the pagedaemon: deadlock detected msg, but the
symptoms were quite similar: ping works, all tcp services seems to
complete connection but no data is transmitted, i could plug an usb
keyboard, it attached correctly, but couldn't type anything.

The box is running -current from about 2 weeks ago (I don't have
access to the box right now, it has frozen again I guess...)

I'll try the patch and report back.

 CK

 --
 GDB has a 'break' feature; why doesn't it have 'fix' too?



Re: pagedaemon: deadlock detected

2007-08-02 Thread Frank Denis

Le Thu, Aug 02, 2007 at 12:55:44PM -0400, Jean Raby ecrivait :

I had several similar cases with an Apple macmini (i386),  also
running a couple of rtorrent instances.
Needless to say, there is no serial console on this box...
so i didn't see the pagedaemon: deadlock detected msg, but the
symptoms were quite similar: ping works, all tcp services seems to
complete connection but no data is transmitted, i could plug an usb
keyboard, it attached correctly, but couldn't type anything.


 This is something that still happens on my Net4801 with -current, even
with that patch applied.