Port lock was not acquired
Posted: 25. Jan 2012, 01:06
Since "upgrading" from VirtualBox 4.1.6 to 4.1.8, I am now receiving in Windbg the error message "Port lock was not acquired" on a regular basis.
It seems to be output every second or two. PIIX chipset is set -- ICH makes things even less stable. After a while, I get a crash in ntkrnlmp.exe:
fffff880`02060a78 fffff800`018c8420 : fffffa80`00000000 00000000`0000000f 00000000`00000010 fffff800`0189d380 : nt!DbgBreakPointWithStatus
fffff880`02060a80 fffff800`018226f1 : fffff800`00000005 00000000`00000000 00000000`0000027f fffff800`000001df : nt!KiBugCheckDebugBreak+0x14
fffff880`02060af0 fffff800`018288cb : fffffa80`057b6b38 fffffa80`057b6000 00000000`00001000 fffff800`01873437 : hal!HalpNMIHalt+0x10d
fffff880`02060b30 fffff800`01872d8b : fffffa80`057b47e9 fffffa80`057b6968 00000000`00000020 fffff800`018362b0 : hal!HalBugCheckSystem+0x7f
fffff880`02060ba0 fffff800`018227fa : fffff800`018362b0 00000000`00000020 fffff880`02060e00 fffff880`02060e00 : nt!WheaReportHwError+0x29b
fffff880`02060c10 fffff800`018d265a : 00000000`00000000 fffff880`02060df0 fffff880`02060cb0 fffffa80`062ca590 : hal!HalHandleNMI+0xfe
fffff880`02060c40 fffff800`01a62ec2 : fffff880`02060df0 fffff880`02060cb0 fffff880`02056180 fffff880`02060e70 : nt!KiProcessNMI+0x1de
fffff880`02060cb0 fffff800`01a62d23 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxNmiInterrupt+0x82
fffff880`02060df0 fffff800`0182f58b : fffff800`01a5f22c fffff880`02056180 fffff800`0182f2e2 00000000`00000010 : nt!KiNmiInterruptStart+0x163
fffff880`0207ec58 fffff800`01a5f22c : fffff880`02056180 fffff800`0182f2e2 00000000`00000010 00000000`00000246 : hal!HalpLegacyApicEndOfInterrupt+0xb
fffff880`0207ec60 fffff880`02056180 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt+0x1c
00000000`00000246 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`02056180
Anyway, I'm going to go "downgrade" to 4.1.6 now. Probably you'll want to investigate this bug.
It seems to be output every second or two. PIIX chipset is set -- ICH makes things even less stable. After a while, I get a crash in ntkrnlmp.exe:
fffff880`02060a78 fffff800`018c8420 : fffffa80`00000000 00000000`0000000f 00000000`00000010 fffff800`0189d380 : nt!DbgBreakPointWithStatus
fffff880`02060a80 fffff800`018226f1 : fffff800`00000005 00000000`00000000 00000000`0000027f fffff800`000001df : nt!KiBugCheckDebugBreak+0x14
fffff880`02060af0 fffff800`018288cb : fffffa80`057b6b38 fffffa80`057b6000 00000000`00001000 fffff800`01873437 : hal!HalpNMIHalt+0x10d
fffff880`02060b30 fffff800`01872d8b : fffffa80`057b47e9 fffffa80`057b6968 00000000`00000020 fffff800`018362b0 : hal!HalBugCheckSystem+0x7f
fffff880`02060ba0 fffff800`018227fa : fffff800`018362b0 00000000`00000020 fffff880`02060e00 fffff880`02060e00 : nt!WheaReportHwError+0x29b
fffff880`02060c10 fffff800`018d265a : 00000000`00000000 fffff880`02060df0 fffff880`02060cb0 fffffa80`062ca590 : hal!HalHandleNMI+0xfe
fffff880`02060c40 fffff800`01a62ec2 : fffff880`02060df0 fffff880`02060cb0 fffff880`02056180 fffff880`02060e70 : nt!KiProcessNMI+0x1de
fffff880`02060cb0 fffff800`01a62d23 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxNmiInterrupt+0x82
fffff880`02060df0 fffff800`0182f58b : fffff800`01a5f22c fffff880`02056180 fffff800`0182f2e2 00000000`00000010 : nt!KiNmiInterruptStart+0x163
fffff880`0207ec58 fffff800`01a5f22c : fffff880`02056180 fffff800`0182f2e2 00000000`00000010 00000000`00000246 : hal!HalpLegacyApicEndOfInterrupt+0xb
fffff880`0207ec60 fffff880`02056180 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt+0x1c
00000000`00000246 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`02056180
Anyway, I'm going to go "downgrade" to 4.1.6 now. Probably you'll want to investigate this bug.