VirtualBox

Ticket #9230 (closed defect: fixed)

Opened 3 years ago

Last modified 19 months ago

Host stacktrace after resume from memory on Natty

Reported by: rfay Owned by:
Priority: blocker Component: other
Version: VirtualBox 4.0.12 Keywords:
Cc: Guest type: Linux
Host type: Linux

Description (last modified by frank) (diff)

Using 4.0.12 on Ubuntu Natty (4.0.8 has the same problem) if I suspend after starting a machine, and then resume, I get this stacktrace:

Jul 18 09:03:11 rfay-dell kernel: [ 2196.877053] Modules linked in: binfmt_misc rfcomm sco bnep l2cap vboxnetadp vboxnetflt vboxdrv 
parport_pc ppdev joydev snd_hda_codec_hdmi snd_hda_codec_idt btusb 
bluetooth snd_hda_intel snd_hda_codec snd_hwdep arc4 snd_pcm 
snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq usbhid 
snd_timer uvcvideo hid snd_seq_device videodev v4l2_compat_ioctl32 
iwlagn i915 dell_wmi sparse_keymap iwlcore mac80211 drm_kms_helper 
snd intel_ips dell_laptop dcdbas psmouse soundcore serio_raw 
cfg80211 drm snd_page_alloc i2c_algo_bit video lp parport ahci 
libahci r8169
Jul 18 09:03:11 rfay-dell kernel: [ 2196.883523]
Jul 18 09:03:11 rfay-dell kernel: [ 2196.884844] Pid: 7514, comm: VirtualBox Not tainted 2.6.38-8-generic #42-Ubuntu Dell Inc. Inspiron N5010/0WXY9J
Jul 18 09:03:11 rfay-dell kernel: [ 2196.886287] RIP: 0010:[<ffffffffa0441699>]  [<ffffffffa0441699>] 0xffffffffa0441699
Jul 18 09:03:11 rfay-dell kernel: [ 2196.888569] RSP: 0018:ffff880149fd9d50  EFLAGS: 00010246
Jul 18 09:03:11 rfay-dell kernel: [ 2196.890853] RAX: 0000000000000000 RBX: ffffc90011fc9000 RCX: 0000000000000001
Jul 18 09:03:11 rfay-dell kernel: [ 2196.893164] RDX: 00000000000000e0 RSI: 000000008005003b RDI: 0000000000006c00
Jul 18 09:03:11 rfay-dell kernel: [ 2196.895366] Switched to NOHz mode on CPU #3
Jul 18 09:03:11 rfay-dell kernel: [ 2196.897798] RBP: ffff880149fd9d98 R08: ffff8800bb28dce0 R09: 000001ff4c65822c
Jul 18 09:03:11 rfay-dell kernel: [ 2196.900133] R10: 0000000000000000 R11: 0000000000000246 R12: ffffc90011fae000
Jul 18 09:03:11 rfay-dell kernel: [ 2196.902479] R13: 0000000000000001 R14: ffffc90011fc9900 R15: 00000000fffff054
Jul 18 09:03:11 rfay-dell kernel: [ 2196.904842] FS:  00007f79eda60700(0000) GS:ffff8800bb280000(0000) knlGS:0000000000000000
Jul 18 09:03:11 rfay-dell kernel: [ 2196.907228] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Jul 18 09:03:11 rfay-dell kernel: [ 2196.909607] CR2: 00007ffffe142ff8 CR3: 0000000149f4f000 CR4: 00000000000006e0
Jul 18 09:03:11 rfay-dell kernel: [ 2196.912008] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Jul 18 09:03:11 rfay-dell kernel: [ 2196.914418] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Jul 18 09:03:11 rfay-dell kernel: [ 2196.916819] Process VirtualBox (pid: 7514, threadinfo ffff880149fd8000, task ffff8801b4685b80)
Jul 18 09:03:11 rfay-dell kernel: [ 2196.919249] Stack:
Jul 18 09:03:11 rfay-dell kernel: [ 2196.921650]  ffffffffa044613d ffff880149fd9da8 ffff880149fd9d78 0000000000000282
Jul 18 09:03:11 rfay-dell kernel: [ 2196.924117]  ffffc900129ed078 ffff880149fd9d88 ffffc90011fc9000 ffffc90011fae000
Jul 18 09:03:11 rfay-dell kernel: [ 2196.926618]  0000000000000001 ffff880149fd9de8 ffffffffa0440f8d 0000000000000282
Jul 18 09:03:11 rfay-dell kernel: [ 2196.929110] Call Trace:
Jul 18 09:03:11 rfay-dell kernel: [ 2196.931561]  [<ffffffffa03da8ea>] ? supdrvIOCtlFast+0x6a/0x70 [vboxdrv]
Jul 18 09:03:11 rfay-dell kernel: [ 2196.934030]  [<ffffffffa03d7389>] ? VBoxDrvLinuxIOCtl+0x49/0x200 [vboxdrv]
Jul 18 09:03:11 rfay-dell kernel: [ 2196.936503]  [<ffffffff8100a777>] ? __switch_to+0x157/0x2f0
Jul 18 09:03:11 rfay-dell kernel: [ 2196.938952]  [<ffffffff8117648f>] ? do_vfs_ioctl+0x8f/0x360
Jul 18 09:03:11 rfay-dell kernel: [ 2196.941383]  [<ffffffff815c059c>] ? schedule+0x3ec/0x760
Jul 18 09:03:11 rfay-dell kernel: [ 2196.943806]  [<ffffffff811767f1>] ? sys_ioctl+0x91/0xa0
Jul 18 09:03:11 rfay-dell kernel: [ 2196.946221]  [<ffffffff8100c002>] ? system_call_fastpath+0x16/0x1b
Jul 18 09:03:11 rfay-dell kernel: [ 2196.948624] Code: 89 de 4c 89 
e7 48 8b 5d e8 4c 8b 65 f0 48 89 c1 4c 8b 6d f8 c9 e9 68 3c 00 00 
b8 1f ff ff ff eb 9f 90 81 e7 ff ff ff ff 48 31 c0 <0f> 79 fe 73 06 
b8 5f f0 ff ff c3 75 05 b8 60 f0 ff ff c3 cc cc
Jul 18 09:03:11 rfay-dell kernel: [ 2196.954030] RIP  [<ffffffffa0441699>] 0xffffffffa0441699
Jul 18 09:03:11 rfay-dell kernel: [ 2196.956654]  RSP <ffff880149fd9d50>
Jul 18 09:03:11 rfay-dell kernel: [ 2197.025637] ---[ end trace 6bdb96c29a5d4514 ]---
Jul 18 09:03:28 rfay-dell kernel: [ 2214.076113] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id

This is repeatable 100% of the time.

  1. Start a VM
  2. Suspend to memory
  3. Resume

Linux rfay-dell 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:24 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

Attached are a more extensive kernel log and the VBox.log

Attachments

kern.log Download (22.1 KB) - added by rfay 3 years ago.
Kernel log from the crash

Change History

Changed 3 years ago by rfay

Kernel log from the crash

comment:1 Changed 3 years ago by rfay

I seem to be unable to attach another file. Python is croaking. Submitting here to see if it can get better...

comment:2 Changed 3 years ago by rfay

When attempting to attach the VBox.log, a python error occurred.

comment:3 Changed 3 years ago by ramshankar

  • Description modified (diff)

Sounds related to #9305

comment:4 Changed 3 years ago by frank

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

Please reopen if still relevant with VBox 4.1.2.

comment:5 Changed 3 years ago by rfay

  • Status changed from closed to reopened
  • Resolution fixed deleted

Yes, the same exact behavior in 4.1.2.

With a guest running, suspend-to-memory the host. Resume the host, and in a few moments you get the crash described above.

I believe this happens 100% of the time.

comment:6 Changed 3 years ago by rfay

A bit more information.

  1. Although this gives a full black-and-white stacktrace on the screen, it doesn't seem to be a kernel panic, as I can get X started again with ctrl-alt-del and ctrl-alt-bksp.
  2. However, when in this situation, I can never start another guest without the crash described in the initial description.

Truly insidious.

comment:7 Changed 3 years ago by rfay

And I confirm this again in 4.1.4-74291~Ubuntu~natty

Oct  8 22:14:17 rfay-dell kernel: [147378.755948] Pid: 7054, comm: VirtualBox Not tainted 2.6.38-8-generic #42-Ubuntu Dell Inc. Inspiron N5010/0WXY9J

comment:8 Changed 19 months ago by frank

  • Status changed from reopened to closed
  • Resolution set to fixed
  • Description modified (diff)

Please reopen if still relevant with VBox 4.1.22.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use