The OpenBSD operating system (misc)

belenus | 20 Jun 2012 23:20

System crash due to kernel locking?

Hi,

just had one of my servers crash with the following message:

http://v68i.img-up.net/crash113b41.JPG

Was this specific issue fixed in -current with the following comment
from the daily changelog?

     "The mlock(2) and munlock(2) systemcalls no longer cause hard
      failures when the effective region is of zero length."

Best regards,
Michael

-dmesg:
OpenBSD 5.1 (GENERIC.MP) #188: Sun Feb 12 09:55:11 MST 2012
    deraadt <at> i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
cpu0: Intel(R) Xeon(R) CPU 3050  <at>  2.13GHz ("GenuineIntel" 686-class)
2.14 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,NXE,LONG,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,LAHF
real mem  = 3220504576 (3071MB)
avail mem = 3157712896 (3011MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 10/04/07, BIOS32 rev. 0  <at>  0xffe90,
SMBIOS rev. 2.4  <at>  0xfa5b0 (48 entries)
bios0: vendor Dell Computer Corporation version "A05" date 10/04/2007
bios0: Dell Computer Corporation PowerEdge 860
acpi0 at bios0: rev 2

(Continue reading)

headers

Michael Lechtermann | 20 Jun 2012 23:58

Re: System crash due to kernel locking?

Forgot to mention that since uhci was offline I wasn't able to execute
any trace or os commands.

On 20.06.12 23:20, belenus <at> bsdmail.de wrote:
> Hi,
> 
> just had one of my servers crash with the following message:
> 
> http://v68i.img-up.net/crash113b41.JPG
> 
> Was this specific issue fixed in -current with the following comment
> from the daily changelog?
> 
>      "The mlock(2) and munlock(2) systemcalls no longer cause hard
>       failures when the effective region is of zero length."
> 
> 
> Best regards,
> Michael
> 
> 
> 
> -dmesg:
> OpenBSD 5.1 (GENERIC.MP) #188: Sun Feb 12 09:55:11 MST 2012
>     deraadt <at> i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
> cpu0: Intel(R) Xeon(R) CPU 3050  <at>  2.13GHz ("GenuineIntel" 686-class)
> 2.14 GHz
> cpu0:
> FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,NXE,LONG,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,LAHF
> real mem  = 3220504576 (3071MB)

(Continue reading)

headers

Ariane van der Steldt | 21 Jun 2012 00:27

Re: System crash due to kernel locking?

On Wed, Jun 20, 2012 at 11:20:29PM +0200, belenus <at> bsdmail.de wrote:
> just had one of my servers crash with the following message:
> 
> http://v68i.img-up.net/crash113b41.JPG
> 
> Was this specific issue fixed in -current with the following comment
> from the daily changelog?
> 
>      "The mlock(2) and munlock(2) systemcalls no longer cause hard
>       failures when the effective region is of zero length."

No, that fixed locking of application memory and has nothing to do with
USB.
--

-- 
Ariane