Custom Query (16363 matches)
Results (457 - 459 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #9287 | duplicate | vboxdrv: [ID 694835 kern.notice] NOTICE: kthread_t::t_pree mpt at 42 | ||
| Description |
After upgrading to 4.1.0, the following messages are logged when solaris boots: vboxdrv: [ID 694835 kern.notice] NOTICE: kthread_t::t_pree mpt at 42 vboxdrv: [ID 694835 kern.notice] NOTICE: cpu_t::cpu_runrun
vboxdrv: [ID 694835 kern.notice] NOTICE: cpu_t::cpu_kprunr un at 233 When the VirtualBox command is executed, it segfaults and the following message appears in the system log: genunix: [ID 269049 kern.notice] NOTICE: VirtualBox[1586] attempt to execute non-executable data at 0xfffffd7ffedec640 by uid 1001 |
|||
| #8859 | fixed | vboxdrv: 'Default Stop'-value causing trouble on recent Debian and derivatives -> fixed as of 2 Aug 2011 | ||
| Description |
The "Default Stop" comment of vboxdrv comprises just run level 1.
On Debian lenny symbolic links K*vboxdrv are established in /etc/rc{0,1,6}.d nevertheless. update-rc.d: warning: vboxdrv stop runlevel arguments (0 1 6) do not match LSB Default-Stop values (1)
which can be reproduced by running update-rc.d vboxdrv defaults. According to http://forums.virtualbox.org/viewtopic.php?f=7&t=37659 Debian derivates seem to be affcted, too. All other init-scripts belonging to VirtualBox 4.0.6 define 0, 1 and 6 as stop-runlevels, same thing for all init-scripts included in 3.2.12. |
|||
| #7672 | obsolete | vboxdrv.sys driver is not uninstalled | ||
| Description |
|
|||

