FS#25187 - Virtualbox causes kernel panic during host system shutdown

Attached to Project: Community Packages
Opened by Vytenis (DisLike) - Wednesday, 20 July 2011, 11:46 GMT
Last edited by Ionut Biru (wonder) - Tuesday, 09 August 2011, 07:20 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Ionut Biru (wonder)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 14
Private No

Details

Description:

Virtualbox causes kernel panic on every shut down on host machine after reinstalling kernel modules using /etc/rc.d/vboxdrv setup.

Virtualbox version is 4.1.0-2.

Steps to reproduce:
1) Install virtualbox
2) Setup kernel modules
3) Try to shut down machine (kernel panic occures at the very end of the shut down sequence)
This task depends upon

Closed by  Ionut Biru (wonder)
Tuesday, 09 August 2011, 07:20 GMT
Reason for closing:  Fixed
Additional comments about closing:  virtualbox 4.1.0-5
Comment by Vytenis (DisLike) - Wednesday, 20 July 2011, 11:47 GMT
Uname information:
Linux Brain 2.6.39-ARCH #1 SMP PREEMPT Sat Jul 9 15:31:04 CEST 2011 i686 Intel(R) Core(TM) Duo CPU T2450 @ 2.00GHz GenuineIntel GNU/Linux
Comment by Ionut Biru (wonder) - Wednesday, 20 July 2011, 11:55 GMT
report it to virtualbox bugtracker and it will be nice to take a picture with the panic log/trace, if is available
Comment by p.p. (MuF) - Wednesday, 20 July 2011, 13:03 GMT
Same problem with versions 4.1.0-1 and 4.1.0-2
Comment by Paulin (popo01) - Wednesday, 20 July 2011, 15:18 GMT
Same problem here
edit @wonder : ok, my bad
Comment by Ionut Biru (wonder) - Wednesday, 20 July 2011, 15:29 GMT
let me be clear enough, don't say that you are affected, is useless and noisy.

i only want for you guys to forward this bug upstream and paste the link here to follow.
Comment by Ionut Biru (wonder) - Wednesday, 20 July 2011, 16:29 GMT
upstream report

http://www.virtualbox.org/ticket/9253
Comment by Vytenis (DisLike) - Thursday, 21 July 2011, 06:36 GMT
I have been asked to supply trace/log. Unfortunately I was not able to find this information in my log files and as long as I do not have access to digital camera at the moment, I am not quite able to get it :). But, I found that this kind of information (the same panic message) has been supplied to virtualbox bug report (see link posted by Ionut Biru (wonder): http://www.virtualbox.org/ticket/9253).

Image is here:
http://ompldr.org/vOWsxMA
http://ompldr.org/vOWsxMg
Comment by martin (gpmr) - Thursday, 21 July 2011, 07:20 GMT
To prevent the kernel panic temporarily, simply unload the "vboxdrv" module manually right before you shut down your machine. To unload the loadable module simply use the command "sudo rmmod vboxdrv". As I said, this prevents the kernel panic just temporarily.
Comment by Giovanne (ginoboy) - Friday, 22 July 2011, 12:20 GMT
Really that's temporarily solution for this problem.. unload 'vboxdrv', that's what I did too.
Comment by Tilman Blumenbach (Tblue) - Sunday, 24 July 2011, 09:23 GMT
As others already said, a good workaround is to unload the vboxdrv module before halting the machine. You can automate it by adding the following to /etc/rc.local.shutdown:

modprobe -r vboxdrv
Comment by mao1234567890 (mao1234567890) - Sunday, 24 July 2011, 23:42 GMT
same problem here, if i dont unload or remove the vboxdrv module, arch through a kernel panic
i have the 4.1.0-2 version of virtualbox
sorry for my english
Comment by Paulin (popo01) - Monday, 25 July 2011, 20:57 GMT
I've noticed the same problem when switching to sleep mode, it is instantaneous.
Comment by Stephen E. Baker (TheCycoONE) - Tuesday, 26 July 2011, 16:40 GMT
Could we have a warning on install or a downgrade on the package until the issue is resolved. It's pretty serious.
Comment by Szász Márton (marcii) - Wednesday, 27 July 2011, 10:25 GMT
Same at me, even with the new 3.0-1 kernel from testing.
The problem only appears at power off, but not on reboot.
Comment by Oto Magaldadze (ottoshmidt) - Friday, 29 July 2011, 05:40 GMT
temporary workaround:

put this into /etc/rc.local.shutdown:

modprobe -r vboxdrv

source: https://bbs.archlinux.org/viewtopic.php?pid=964274

PS Tilman mentioned that above but few people paid attention I guess.
Comment by Eugene (Infy) - Monday, 08 August 2011, 19:58 GMT
Same with virtualbox 4.1.0-4 from community with kernel 3.0.1-1.
Comment by Ionut Biru (wonder) - Monday, 08 August 2011, 19:58 GMT
well, a reason for not doing packaging while drunk is this. I failed to use the right patch
Comment by Ionut Biru (wonder) - Monday, 08 August 2011, 20:25 GMT
please report back with virtualbox-4.1.0-5. be sure you recompile the modules
Comment by andrews (andrews) - Tuesday, 09 August 2011, 03:23 GMT
clean shutdown with virtualbox-4.1.0-5, thanks.

Loading...