VirtualBox

Ticket #1567 (closed defect: fixed)

Opened 6 years ago

Last modified 5 years ago

Crash on Linux (vmptrld)

Reported by: walkerd Owned by:
Priority: major Component: VMM
Version: VirtualBox 2.0.6 Keywords: Crash
Cc: Guest type: other
Host type: Linux

Description (last modified by frank) (diff)

After upgrade to 1.6. I observed the following crash when I tried to resume the VBox from Pause mode:

invalid opcode: 0000 [#1]
SMP 
Modules linked in: hci_usb usb_storage vboxdrv cdc_acm usbhid usbkbd rfcomm l2cap bluetooth tun uinput snd_pcm_oss snd_mixer_oss snd_usb_audio
snd_usb_lib snd_rawmidi snd_seq_device dock arc4 ecb blkcipher cryptomgr crypto_algapi pcmcia nvidia(P) iwl4965 snd_hda_intel mac80211 snd_pcm
snd_timer snd_page_alloc snd_hwdep yenta_socket rsrc_nonstatic nvidiafb cfg80211 ohci1394 snd fb_ddc i2c_algo_bit i2c_i801 ehci_hcd uhci_hcd
pcmcia_core ieee1394 soundcore psmouse vgastate usbcore i2c_core e1000
CPU:    0
EIP:    0060:[<f8b7768a>]    Tainted: P        VLI
EFLAGS: 00210046   (2.6.23 #11)
EIP is at 0xf8b7768a
eax: 00000000   ebx: 00000000   ecx: 0dbc5000   edx: 00000000
esi: 00000000   edi: f8bc5000   ebp: ef1bded4   esp: ef1bdec0
ds: 007b   es: 007b   fs: 00d8  gs: 0033  ss: 0068
Process VirtualBox (pid: 31647, ti=ef1bc000 task=f0a23a40 task.ti=ef1bc000)
Stack: 0dbc5000 00000000 f566c700 f8bc5000 00200246 ef1bdf04 f8b71f98 f8bc5000 
       ef1bdef8 00000000 c054275c c0139dc8 ef1bdf98 00000400 f8bc59c0 f566c700 
       f8bc5000 ef1bdf24 f8b790d3 f8bc5000 046aa618 000037d5 f566c700 f566c700 
Call Trace:
 [<c0139dc8>] do_futex+0x55e/0x947
 [<f8b5b0a4>] VBoxDrvLinuxIOCtl+0x34/0x196 [vboxdrv]
 [<f8b5b070>] VBoxDrvLinuxIOCtl+0x0/0x196 [vboxdrv]
 [<c0169153>] do_ioctl+0x1f/0x62
 [<c01693c6>] vfs_ioctl+0x230/0x242
 [<c016940b>] sys_ioctl+0x33/0x4c
 [<c0103e26>] sysenter_past_esp+0x5f/0x85
 [<c0360000>] rpcauth_unbindcred+0x29/0x4f
 =======================
Code: 75 11 89 f0 8b 1c 24 8b 74 24 04 8b 7c 24 08 89 ec 5d c3 8b 9f 3c e0 00 00 31 f6 8b 8f 38 e0 00 00 89 da 89 c8 89 d0 31 d2 50 51 <0f>
c7 34 24 73 05 be 5f f0 ff ff 83 c4 08 85 f6 78 c5 31 f6 c6 
EIP: [<f8b7768a>] 0xf8b7768a SS:ESP 0068:ef1bdec0

With older version it never happend.

Guest OS: Win XP.

Attachments

VBox_2.0.4.log Download (116.1 KB) - added by walkerd 5 years ago.
VBox log 2.0.4 after crash

Change History

comment:1 Changed 6 years ago by frank

  • Description modified (diff)
  • Summary changed from Crash on Linux to Crash on Linux (vmptrld)

comment:2 Changed 6 years ago by frank

Please could you update to VirtualBox 1.6.2 and provide a VBox.log file if the crashed VM session if the problem still persists?

comment:3 Changed 6 years ago by frank

  • Host type changed from other to Linux

comment:4 Changed 6 years ago by frank

  • Component changed from other to VMM

comment:5 Changed 5 years ago by walkerd

In version 2.0.4 the same bug.

invalid opcode: 0000 #5 PREEMPT SMP Modules linked in: usb_storage nvidia(P) hci_usb vboxdrv iwl4965 snd_hda_intel snd_usb_audio snd_pcm snd_timer snd_usb_lib snd_rawmidi snd_seq_device snd_hwdep snd soundcore mmc_block usbkbd ppp_async crc_ccitt ppp_generic slhc cdc_acm usbhid tun rfcomm l2cap bluetooth uinput arc4 ecb crypto_blkcipher pcmcia nvidiafb cryptomgr crypto_algapi fb_ddc i2c_algo_bit snd_page_alloc iwlcore yenta_socket i2c_i801 vgastate pcspkr psmouse rsrc_nonstatic mac80211 pcmcia_core i2c_core cfg80211 ohci1394 sdhci ieee1394 mmc_core ehci_hcd uhci_hcd usbcore e1000 [last unloaded: nvidia]

Pid: 9614, comm: VirtualBox Tainted: P R D (2.6.25.10 #1) EIP: 0060:[<f8f5fa32>] EFLAGS: 00010046 CPU: 0 EIP is at 0xf8f5fa32 EAX: 00000000 EBX: 00000000 ECX: 356ee000 EDX: 00000000 ESI: 00000000 EDI: f8a86000 EBP: de133ed0 ESP: de133ec0

DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068

Process VirtualBox (pid: 9614, ti=de132000 task=f7d0b050 task.ti=de132000) Stack: 356ee000 00000000 00000000 f8a86000 de133f00 f8f59481 f8a86000 f8fb1920

ee9d1850 f8c2e32d f8a86000 00000007 f8a869c0 f8c2b106 f8a86000 00000246 de133f20 f8f6179b f8a86000 00000282 f8c2fbf2 f8c2b106 d1c79e00 00000000

Call Trace:

[<f8c2e32d>] supdrvIOCtl+0xe07/0x123a [vboxdrv] [<f8c2b106>] VBoxDrvLinuxIOCtl+0x0/0x15f [vboxdrv] [<f8c2fbf2>] rtMemAlloc+0x29/0x47 [vboxdrv] [<f8c2b106>] VBoxDrvLinuxIOCtl+0x0/0x15f [vboxdrv] [<f8c2b383>] supdrvIOCtlFast+0x3f/0x4a [vboxdrv] [<f8c2b133>] VBoxDrvLinuxIOCtl+0x2d/0x15f [vboxdrv] [<f8c2b106>] VBoxDrvLinuxIOCtl+0x0/0x15f [vboxdrv] [<c01697f8>] vfs_ioctl+0x1c/0x5f [<c0169a6a>] do_vfs_ioctl+0x22f/0x241 [<c0131575>] do_gettimeofday+0xf/0x29 [<c0169aa8>] sys_ioctl+0x2c/0x44 [<c0103c76>] sysenter_past_esp+0x5f/0x85 =======================

Code: ff 75 0d 89 f0 8b 1c 24 8b 74 24 04 89 ec 5d c3 8b 45 08 31 f6 8b 98 68 e2 00 00 8b 88 64 e2 00 00 89 da 89 c8 89 d0 31 d2 50 51 <0f> c7 34 24 73 05 be 5f f0 ff ff 83 c4 08 85 f6 78 c6 8b 45 08 EIP: [<f8f5fa32>] 0xf8f5fa32 SS:ESP 0068:de133ec0 ---[ end trace 07810f60354d5bcf ]--- done.

Changed 5 years ago by walkerd

VBox log 2.0.4 after crash

comment:6 Changed 5 years ago by sandervl73

All you do is pause the VM and then resume it? This is quite strange.

comment:7 Changed 5 years ago by walkerd

NO! I put my host (Linux) in to stadby mode and then resume. There is another ticket open with this problem. And there is written that this issue is going to be solved in 2.0.6. So I was waiting for 2.0.6. If I put fist VM in to pause mode, it is the same.

comment:8 Changed 5 years ago by sandervl73

  • Status changed from new to closed
  • Resolution set to duplicate

Well, it's a duplicate then. Closing.

comment:9 Changed 5 years ago by walkerd

  • Status changed from closed to reopened
  • Resolution duplicate deleted

This ticket was closed because of duplicated, but also 1938 was closed from the same reason. So there is no open ticket with this issue left.

I just checked 2.0.6 if problem is already fixed as planned, but nothing happened. Here it is with 2.0.6:

invalid opcode: 0000 #1 PREEMPT SMP Modules linked in: vboxdrv usb_storage usbkbd iwl4965 ppp_async crc_ccitt ppp_generic slhc cdc_acm parport_pc parport usblp usbhid tun rfcomm l2cap uinput snd_pcm_oss snd_mixer_oss snd_usb_audio snd_usb_lib snd_rawmidi snd_seq_device snd_hwdep nvidia(P) arc4 ecb crypto_blkcipher cryptomgr nvidiafb snd_hda_intel crypto_algapi pcmcia fb_ddc i2c_algo_bit hci_usb snd_pcm iwlcore snd_timer yenta_socket snd pcspkr vgastate bluetooth i2c_i801 mac80211 psmouse soundcore rsrc_nonstatic pcmcia_core i2c_core snd_page_alloc cfg80211 sdhci ohci1394 mmc_core ieee1394 ehci_hcd uhci_hcd usbcore e1000 [last unloaded: vboxdrv]

Pid: 15123, comm: VirtualBox Tainted: P (2.6.25.10 #3) EIP: 0060:[<f8c0aaa2>] EFLAGS: 00010046 CPU: 0 EIP is at 0xf8c0aaa2 EAX: 00000000 EBX: 00000000 ECX: 2ec77000 EDX: 00000000 ESI: 00000000 EDI: f8c67000 EBP: d97bded0 ESP: d97bdec0

DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068

Process VirtualBox (pid: 15123, ti=d97bc000 task=eee5c570 task.ti=d97bc000) Stack: 2ec77000 00000000 00000000 f8c67000 d97bdf00 f8c04481 f8c67000 f8c5cbc0

eeec9e90 f8be932d f8c67000 00000007 f8c679c0 f8be6106 f8c67000 00000246 d97bdf20 f8c0c80b f8c67000 00000282 f8beabf2 f8be6106 ee871000 00000000

Call Trace:

[<f8be932d>] supdrvIOCtl+0xe07/0x123a [vboxdrv] [<f8be6106>] VBoxDrvLinuxIOCtl+0x0/0x15f [vboxdrv] [<f8beabf2>] rtMemAlloc+0x29/0x47 [vboxdrv] [<f8be6106>] VBoxDrvLinuxIOCtl+0x0/0x15f [vboxdrv] [<f8be6383>] supdrvIOCtlFast+0x3f/0x4a [vboxdrv] [<f8be6133>] VBoxDrvLinuxIOCtl+0x2d/0x15f [vboxdrv] [<f8be6106>] VBoxDrvLinuxIOCtl+0x0/0x15f [vboxdrv] [<c0169748>] vfs_ioctl+0x1c/0x5f [<c01699ba>] do_vfs_ioctl+0x22f/0x241 [<c0131558>] do_gettimeofday+0xf/0x29 [<c01699f8>] sys_ioctl+0x2c/0x44 [<c0103c76>] sysenter_past_esp+0x5f/0x85 =======================

Code: ff 75 0d 89 f0 8b 1c 24 8b 74 24 04 89 ec 5d c3 8b 45 08 31 f6 8b 98 68 e2 00 00 8b 88 64 e2 00 00 89 da 89 c8 89 d0 31 d2 50 51 <0f> c7 34 24 73 05 be 5f f0 ff ff 83 c4 08 85 f6 78 c6 8b 45 08 EIP: [<f8c0aaa2>] 0xf8c0aaa2 SS:ESP 0068:d97bdec0 ---[ end trace 237602d566fe9366 ]--- done.

This bug is there since 1.6.0. And 1.5.6 - last stable - is not available on VBox server :(((((

comment:10 Changed 5 years ago by sandervl73

  • Version changed from VirtualBox 1.6.0 to VirtualBox 2.0.6

Could you check if it's still present in 2.1.0?

comment:11 Changed 5 years ago by walkerd

Great, it passed the first test. I will run several of them during this week. If anything is still not O.K., I will update soon. Thanks

comment:12 Changed 5 years ago by frank

  • Status changed from reopened to closed
  • Resolution set to fixed

No response, apparently fixed. Closing.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use