VirtualBox

Opened 15 years ago

Closed 15 years ago

#3735 closed defect (fixed)

virtualbox-2.2 crashes with message VBoxSVC[5382]: segfault at 1f6dcc0 ip 0000000001f6dcc0 sp 00007fff9ba7c918 error 15 => Fixed in SVN

Reported by: Gummibaer Owned by:
Component: other Version: VirtualBox 2.2.0
Keywords: Cc:
Guest type: other Host type: other

Description

I use debian sid/squeeze as guest operating system an let Windows XP working under Virtualbox. After upgrading from version 2.1 to 2.2 every second to third start of Windows XP fails. After pressing the start button, the Windows window opens and it happens nothing. After closing the window by pressing the terminate cross in the right corner I get in /var/log/messages the following output:

VBoxSVC[5382]: segfault at 1f6dcc0 ip 0000000001f6dcc0 sp 00007fff9ba7c918 error 1

On the other hand sometimes virtualbox starts without every problems.

Change History (10)

comment:1 by Frank Mehnert, 15 years ago

If I understood you correct, your host is Debian and your guest is Windows XP. Any chance to provide me a core dump? If so, please could you contact me directly at frank _dot_ mehnert _at_ sun _dot_ com?

comment:2 by Georg, 15 years ago

I have a similar problem.

Host Debian stable/lenny. Fully updated. VirtualBox: "virtualbox-2.2, 2.2.0-45846_Debian_lenny".

Also very "random" problems. Sometimes it work's perfectly, other times similar problems as Gummibaer.

My problems also started after upgrading to 2.2.0, but... More or less at the same time I started to use XP as guest frequently (Win2k before) and started to use an USB-card reader from the guest.

So, my problem might be related to version 2.2.0 or be related to the USB-card reader usage or...

Please let me know if I can help in hunting this bug down. I haven't gotten any core files but maybe I have to "do" something to make them appear?

BTW, A big thank's to the VirtualBox developers for this great product!

Appending some recent messages from /var/log/messages. And once again, let me know if I can provide any other useful information!

Apr 14 17:56:03 big kernel: [294308.335489] VBoxSVC[11234]: segfault at f420095f ip b7b3fec2 sp b757be8c error 5 in libc-2.7.so[b7ad1000+155000]
Apr 14 17:56:03 big kernel: [294308.335489] VBoxSVC[11234]: segfault at f420095f ip b7b3fec2 sp b757be8c error 5 in libc-2.7.so[b7ad1000+155000]
Apr 14 19:03:09 big kernel: [299019.105824] VBoxSVC[24029]: segfault at 642353c7 ip b7bdbebc sp b74fee8c error 4 in libc-2.7.so[b7b6d000+155000]
Apr 14 19:03:09 big kernel: [299019.105824] VBoxSVC[24029]: segfault at 642353c7 ip b7bdbebc sp b74fee8c error 4 in libc-2.7.so[b7b6d000+155000]
Apr 14 19:21:42 big kernel: [300358.899296] VBoxSVC[24088]: segfault at c ip b7b58f61 sp b7594ed4 error 4 in libc-2.7.so[b7aea000+155000]
Apr 14 19:21:42 big kernel: [300358.899296] VBoxSVC[24088]: segfault at c ip b7b58f61 sp b7594ed4 error 4 in libc-2.7.so[b7aea000+155000]
Apr 14 19:22:17 big kernel: [300404.063184] VBoxSVC[26878]: segfault at 98c6f28 ip 098c6f28 sp bfac9c6c error 15
Apr 14 19:22:17 big kernel: [300404.063184] VBoxSVC[26878]: segfault at 98c6f28 ip 098c6f28 sp bfac9c6c error 15
Apr 14 22:51:12 big kernel: [316357.495011] VBoxSVC[26985]: segfault at 2005880c ip b7b28ec2 sp b7445f04 error 4 in libc-2.7.so[b7aba000+155000]
Apr 14 22:51:12 big kernel: [316357.495011] VBoxSVC[26985]: segfault at 2005880c ip b7b28ec2 sp b7445f04 error 4 in libc-2.7.so[b7aba000+155000]
Apr 14 22:52:23 big kernel: [316477.006640] VBoxSVC[28853]: segfault at a104da8 ip 0a104da8 sp bfad6d9c error 15
Apr 14 22:52:23 big kernel: [316477.006640] VBoxSVC[28853]: segfault at a104da8 ip 0a104da8 sp bfad6d9c error 15


comment:3 by Gummibaer, 15 years ago

I use also a USB connected card reader for HBCI banking from WinXP. I have sent the core directly to maintainer mail adress.

I would also thank the Virtualbox developers for their work.

in reply to:  3 ; comment:4 by Georg, 15 years ago

Replying to Gummibaer:

I use also a USB connected card reader for HBCI banking from WinXP.

Interesting! Attaching a lot of gory details regarding my card reader, hoping it might help someone.

I have sent the core directly to maintainer mail adress.

I don't get any core files. Hm, might have something to do with:

gb@big:~$ ulimit -c
0

Guess /etc/security/limits.conf is the place to fix. Have to do some Googeling...

Bus 002 Device 003: ID 08e6:3437 Gemplus GemPC Twin SmartCard Reader
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0         8
  idVendor           0x08e6 Gemplus
  idProduct          0x3437 GemPC Twin SmartCard Reader
  bcdDevice            1.00
  iManufacturer           1 Gemplus
  iProduct                2 USB SmartCard Reader
  iSerial                 0 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           93
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass        11 Chip/SmartCard
      bInterfaceSubClass      0 
      bInterfaceProtocol      0 
      iInterface              0 
      ChipCard Interface Descriptor:
        bLength                54
        bDescriptorType        33
        bcdCCID              1.00
        nMaxSlotIndex           0
        bVoltageSupport         7  5.0V 3.0V 1.8V 
        dwProtocols             3  T=0 T=1
        dwDefaultClock       4000
        dwMaxiumumClock      4000
        bNumClockSupported      0
        dwDataRate          10752 bps
        dwMaxDataRate      344086 bps
        bNumDataRatesSupp.      0
        dwMaxIFSD             254
        dwSyncProtocols  00000000 
        dwMechanical     00000000 
        dwFeatures       00010230
          Auto clock change
          Auto baud rate change
          NAD value other than 0x00 accpeted
          TPDU level exchange
        dwMaxCCIDMsgLen       271
        bClassGetResponse      00
        bClassEnvelope         00
        wlcdLayout           none
        bPINSupport             0 
        bMaxCCIDBusySlots       1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval              24
Device Status:     0x0002
  (Bus Powered)
  Remote Wakeup Enabled

in reply to:  4 comment:5 by Georg, 15 years ago

Replying to Ralfredo (Not always such a bright guy...):

Guess /etc/security/limits.conf is the place to fix. Have to do some Googeling...

Guess I also could follow the excellent link that Frank provided regarding getting core dumps. Me feeling stupid....

comment:6 by Georg, 15 years ago

I have done some more testing and this freeze definitely seems related to USB. This time I tried to boot about ten times. With USB enabled it always froze right after the guest window opened. If I disabled USB everything was fine.

I came up with a "kind of" workaround in un-checking the (only) USB-filter for my card reader, boot the guest OS and after that enable the USB device from the guest window top menu.

I have a core file produced by kill -4 after perhaps 30 seconds of none activity and the corresponding VBox.log, which BTW have the following last entry:

00:00:01.484 VUSB: attached 'b41d3098[proxy 08e6:3437]' to port 1

The core/log is around 5MB (compressed by gzip/bzip2 at best compression). Are you still interested in this Frank? Let me know and I mail the files to you or we make some kind of other delivery.

in reply to:  6 comment:7 by Georg, 15 years ago

Replying to Ralfredo:

Are you still interested in this Frank? Let me know and I mail the files to you or we make some kind of other delivery.

I have now delivered the files to Frank.

comment:8 by YaroZ, 15 years ago

Same problem here.

Host is Debian Lenny 2.6.26-2-amd64

VBox host hangs immediately after power on VM with USB attached devices. VBox host cannot be started again without rebooting. On reboot kernel reports:

kern.log:Apr 22 15:47:50 pajonk kernel: [73324.690447] Xvnc[18703]: segfault at 0 ip 7fd9ba1892ab sp 7fffc2f75dd0 error 6 in libc-2.7.so[7fd9ba133000+14a000]
kern.log:Apr 22 15:48:24 pajonk kernel: [73359.225544] Xvnc[18712]: segfault at 0 ip 7f2d95b812ab sp 7fff9e96d7d0 error 6 in libc-2.7.so[7f2d95b2b000+14a000]
kern.log:Apr 22 15:49:28 pajonk kernel: [73422.906388] Xvnc[18770]: segfault at 0 ip 7fb8850f82ab sp 7fff8dee6d40 error 6 in libc-2.7.so[7fb8850a2000+14a000]
kern.log:Apr 22 18:14:55 pajonk kernel: [  316.860003] VBoxSVC[2888]: segfault at ffffffff02230697 ip 7f66501d5a1b sp 409d3ad0 error 4 in libc-2.7.so[7f6650162000+14a000]
kern.log:Apr 22 18:26:01 pajonk kernel: [  982.026328] VBoxSVC[2970]: segfault at ffffffff011597e7 ip 7fb7001afa1b sp 40858ad0 error 4 in libc-2.7.so[7fb70013c000+14a000]
kern.log:Apr 22 18:56:19 pajonk kernel: [  127.092931] VBoxSVC[2769]: segfault at ffffffff00cdb2f7 ip 7f589958fa1b sp 40e34ad0 error 4 in libc-2.7.so[7f589951c000+14a000]
kern.log:Apr 22 19:02:23 pajonk kernel: [  315.585111] VBoxSVC[2742]: segfault at ffffffff01e79877 ip 7f673096ca1b sp 41350ad0 error 4 in libc-2.7.so[7f67308f9000+14a000]
kern.log:Apr 22 19:30:12 pajonk kernel: [  241.812583] VBoxSVC[4192]: segfault at ffffffff00974877 ip 7fff0e2b0a1b sp 40e3dad0 error 4 in libc-2.7.so[7fff0e23d000+14a000]

When USB support is disabled, Windows Xp guest can boot up without any problem.

Anyway, it also boots up WITH usb support ENABLED, but only when my usb wireless adapter is physically removed from computer.

Workaround is:

  1. unplug all usb devices from your pc
  2. start your guest vm with usb support and NULL filter
  3. replug usb devices into pc when guest os boots up and than manually atach

Usb devices:

Bus 003 Device 002: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Wireless adapter details:

Bus 003 Device 002: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  idVendor           0x0bda Realtek Semiconductor Corp.
  idProduct          0x8187 RTL8187 Wireless Adapter
  bcdDevice            1.00
  iManufacturer           1 Manufacturer_Realtek_RTL8187_
  iProduct                2 RTL8187_Wireless_LAN_Adapter
  iSerial                 3 00C0CA1FF483
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           39
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          4 Wireless Network Card
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass         0 (Defined at Interface level)
      bInterfaceSubClass      0
      bInterfaceProtocol      0
      iInterface              5 Bulk-IN,Bulk-OUT,Bulk-OUT
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x03  EP 3 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  bNumConfigurations      1
Device Status:     0x0000
  (Bus Powered)

comment:9 by Frank Mehnert, 15 years ago

Summary: virtualbox-2.2 crashes with message VBoxSVC[5382]: segfault at 1f6dcc0 ip 0000000001f6dcc0 sp 00007fff9ba7c918 error 15virtualbox-2.2 crashes with message VBoxSVC[5382]: segfault at 1f6dcc0 ip 0000000001f6dcc0 sp 00007fff9ba7c918 error 15 => Fixed in SVN

comment:10 by Frank Mehnert, 15 years ago

Resolution: fixed
Status: newclosed

Please reopen if this problem persists with VirtualBox 2.2.2.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use