Bug 60091 - Kernel panic while working in MS Word launched in VirtualBox
Summary: Kernel panic while working in MS Word launched in VirtualBox
Status: RESOLVED INVALID
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - Intel) (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: intel-gfx-bugs@lists.freedesktop.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-25 11:49 UTC by Žygimantas Beručka
Modified: 2013-06-25 12:50 UTC (History)
3 users (show)

See Also:
Kernel Version: 3.10-rc7
Subsystem:
Regression: No
Bisected commit-id:


Attachments
Another image of the panic message (789.64 KB, image/jpeg)
2013-06-25 11:50 UTC, Žygimantas Beručka
Details
Image of the panic message (883.83 KB, image/jpeg)
2013-06-25 11:52 UTC, Žygimantas Beručka
Details

Description Žygimantas Beručka 2013-06-25 11:49:16 UTC
I just had a kernel panic while working in MS Word launched in VirtualBox 4.2.10 on Ubuntu 13.04. No idea what happened. It happened on my new Samsung NP530U3C machine with i5-3317U CPU and Intel HD4000 graphics. I have never experienced anything like this before on my previous i3-2310M/Intel HD3000 machine while doing the same tasks despite the fact that I ran 3.9 and some early 3.10-rc kernels on that machine too.

I am running a mainline 3.10-rc7 kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.10-rc7-saucy/ since I want to have the latest Samsung UEFI anti-bricking code to avoid bricking my laptop.

The DRI category I have assigned might be incorrect as I have no clue what happened and just saw some messages related to DRI system. I am attaching some screenshots of the panic messages. Pardon for the bad picture quality.
Comment 1 Žygimantas Beručka 2013-06-25 11:50:21 UTC
Created attachment 105981 [details]
Another image of the panic message
Comment 2 Žygimantas Beručka 2013-06-25 11:52:42 UTC
Created attachment 105991 [details]
Image of the panic message
Comment 3 Chris Wilson 2013-06-25 12:17:49 UTC
Right, it is not a DRI panic - just the DRI panic handler is printing the message. I believe vbox loads a binary kernel module and taints the kernel, so unless you can reproduce the issue without vbox loaded, you want to ask the vbox developers first.
Comment 4 Daniel Vetter 2013-06-25 12:30:29 UTC
Yeah, until this is confirmed to be reproducible without vbox it's very very likely not our bug. drm/i915 is just shot as the messenger in the panic path.
Comment 5 Žygimantas Beručka 2013-06-25 12:50:44 UTC
Okay, thank you. I'll see what happens in the future.

Note You need to log in before you can comment on or make changes to this bug.