You are not logged in.
Pages: 1
Hi all,
I'm experiencing kernel panics when shutting down. My system is up to date.
No issues with boot.
I don't know what to look for or to check. I tried to boot with fallback image but shutdown gives the same messages.
after printing "power off" (until there everything is fine) it prints something like a stack backtrace...messages not understandable by me. Are they logged anywhere?
the last one is:
/etc/rc.shutdown:line 100: 1761 killed /sbin/poweroff -d -f -h -i
What can I do?
Hope you'll give some feedback
Last edited by virusso80 (2011-07-22 17:30:25)
Offline
Interesting...
Does reboot cause the same issues? You think you could grab a photo of messages after POWER OFF ?
I'm getting the same thing, but don't really know what is wrong. It's caused by TV card, and it started with mobo upgrade, so I'm leaning towards hardware/compatibility issue...
Offline
If you have VirtulBox 4.1.0 look at this:
http://www.virtualbox.org/ticket/9253
I added to /etc/rc.shutdown
modprobe -r vboxdrv
S-
Offline
Thanks for suggestions...at first sight seems that virtual box bug is the same...but i don't remember messages...then i'll look better asap. Of course I can only take a pic from screen as is...
where should i put the modprobe -r instruction?
thanks again
V
Offline
As Stebalien posted correction:
edit: /etc/rc.local.shutdown
#!/bin/bash
#
# /etc/rc.local.shutdown: Local shutdown script.
#
run as root
nano /etc/rc.local.shutdown
add line
modprobe -r vboxdrv
You could also test if problem is caused with module vboxdrv, by simply running as root command mentioned above and see if your problem persist during shutdown. To check if you have vboxdrv running use this
lsmod | grep vboxdrv
Then, by editing /etc/rc.local.shutdown you make it permanent.
S-
This solved problem with hibernation (post 7):
https://bbs.archlinux.org/viewtopic.php?id=122957
Last edited by StenM (2011-07-23 09:43:10)
Offline
thanks,
just to know, which is the effect of doing this? i mean, before it was not needed, then, why it is needed now?
Offline
thanks,
just to know, which is the effect of doing this? i mean, before it was not needed, then, why it is needed now?
This is a bug of the new version (4.1.0).. thats causes kernel panic in the turn-off time, when the modules of vbox (vboxdrv) are loaded. Probably this bug will fixed in the next version..
This bug was reported here too: https://bugs.archlinux.org/task/25187
Offline
I have no idea what caused the problem, but clearly that is relating to loaded vboxdrv module during shutdown process. "rc.local.shutdown" file is place to put any script that you willing to run before your system run a common shout down process.
Using "modprobe -r vboxdrv" solved only consequences of that error, but the error in VirtualBox remain and VB makers will fix it with new release, hopefully.
S-
PS: Please mark your topic solved
Offline
I confirm that removing vboxdrv kernel module problem does not appear anymore. Temporary solved until fixing. Thanks!
Offline
Pages: 1