VirtualBox

Ticket #616 (new defect)

Opened 1 year ago

Last modified 1 month ago

Assertion failed in sems-linux.cpp(219)

Reported by: freggy Assigned to:
Priority: critical Component: VMM
Version: VirtualBox 1.6.2 Keywords:
Cc: Guest type: other
Host type: Linux

Description (Last modified by frank)

Virtualbox OSE 1.5.0 as included in Mandriva 2008.0 Cooker crashes while installing Mandriva 2008.0 i585 edition via network on Mandriva 2008.0 Cooker x86_64. This can be found in the logs: 

00:16:13.398 !!Assertion Failed!!
00:16:13.398 Expression: i < 4096
00:16:13.411 Location  : /home/mandrake/rpm/BUILD/VirtualBox-1.5.0_OSE/src/VBox/Runtime/r3/linux/sems-linux.cpp(219) int RTSemEventSignal(RTSEMEVENTINTERNAL*)
00:16:13.475 iCur=0x1 pIntEventSem=0000000000a5ccf0

Attachments

VBox.log (27.3 kB) - added by freggy on 09/03/07 22:21:27.
Vbox.log

Change History

09/03/07 22:21:27 changed by freggy

  • attachment VBox.log added.

Vbox.log

09/05/07 20:54:39 changed by freggy

Actually this seems to happen when I minimise the guest VMs window in GNOME - Mandriva Cooker 2008.0, x86_64.

01/05/08 20:32:25 changed by freggy

It seems like this problem still exists in 1.5.4. I just had the same crash on Mandriva Cooker x86_64 (Linux 2.6.24-rc6) with Virtualbox 1.5.4:

1193:59:47.780 !!Assertion Failed!! 1193:59:47.780 Expression: i < 4096 1193:59:47.780 Location : /home/mandrake/rpm/BUILD/VirtualBox-1.5.4_OSE/src/VBox/Runtime/r3/linux/sems-linux.cpp(219) int RTSemEventSignal(RTSEMEVENTINTERNAL*) 1193:59:47.810 iCur=0x1 pIntEventSem=00000000009cb000

The crash mentioned in http://vbox.innotek.de/pipermail/vbox-dev/2007-November/000394.html seems to be the same problem too.

01/05/08 20:33:30 changed by freggy

crash in a code block to improve readability: 

1193:59:47.780 
1193:59:47.780 !!Assertion Failed!!
1193:59:47.780 Expression: i < 4096
1193:59:47.780 Location  : /home/mandrake/rpm/BUILD/VirtualBox-1.5.4_OSE/src/VBox/Runtime/r3/linux/sems-linux.cpp(219) int RTSemEventSignal(RTSEMEVENTINTERNAL*)
1193:59:47.810 iCur=0x1 pIntEventSem=00000000009cb000

01/20/08 02:08:19 changed by benjamin9999

i had this same assert. 1.5.4-binary on linux 2.6.24-rc8 running win2k3 guest. this same box happens to run vmware-server 1.0.3.

02/10/08 18:21:18 changed by freggy

This still happens very often in Mandriva Cooker 2008.1 (Linux 2.6.24 - Glibc 2.7 - x86_64) and it makes Virtualbox unusable for production use. Can anybody finally take a look at this please?

03/26/08 02:28:07 changed by blueyed

The bug has been reported for VirtualBox 1.5.6 on Ubuntu at https://launchpad.net/bugs/206615. The host is Ubuntu 8.04 AMD64 (beta), the host Windows XP and it seems to happen after leaving the machine running/idle for a while.

The bug in Launchpad (https://launchpad.net/bugs/206615), provides additional debugging information, like a stacktrace.

03/26/08 09:35:15 changed by frank

Just to keep you up-to-date: This is a known issue. Still no fix available.

03/27/08 19:44:45 changed by pmatthew

I think this bug is related with preemptivity enabled in kernel... I compiled a kernel without preemptivity and it disappeared. Just a day of machine uptime, I'll send another report later ;)

04/13/08 23:32:30 changed by pmatthew

No, it's not preemptivity, it crashes less, but still aborting...

04/14/08 09:11:24 changed by frank

  • description changed.

06/25/08 17:48:53 changed by sandervl73

  • priority changed from major to critical.

06/25/08 17:48:59 changed by sandervl73

  • version changed from VirtualBox 1.5.0 to VirtualBox 1.6.2.

06/25/08 17:50:43 changed by sandervl73

Similar reports in tickets 1733 and 1746.

07/07/08 16:48:30 changed by frank

  • host changed from other to Linux.

07/10/08 10:00:42 changed by frank

  • owner changed.
  • component changed from other to VMM.

07/25/08 22:39:44 changed by vmorgo

Happens under Ubuntu Hardy Heron 64-bit edition. Core 2 Duo Penryn at 2.5 GHz, VirtualBox 1.5.6OSE as supplied as a package with Ubuntu Hardy Heron 8.04 repos.

Any other information required, please just ask! I'd sure like to know if/when this gets fixed.

© 2008 Sun Microsystems, Inc.
Contact – Privacy policy