Bug#566405: marked as done (Kernel 2.6.32 trunk does not boot within Virtualbox)
Your message dated Fri, 5 Jul 2013 20:14:02 +0200
with message-id <20130705181402.GA8593@pisco.westfalen.local>
and subject line Closing
has caused the Debian Bug report #566405,
regarding Kernel 2.6.32 trunk does not boot within Virtualbox
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
566405: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=566405
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: Kernel 2.6.32 trunk does not boot within Virtualbox
- From: Martijn van de Giessen <mvandegiessen@gmail.com>
- Date: Sat, 23 Jan 2010 13:25:55 +0100
- Message-id: <8f2a46861001230425h2e4eb271ua533d829959aba8a@mail.gmail.com>
Package: linux-image-2.6.686
Version: 2.6.30+21
Kernel hangs with: BUG: soft lockup - CPU#0 stuck for 61s! [modprobe:95]
The VirtualBox extensions have been installed. After this I was able
to boot the kernel once without problems, but consecutive boots all
resulted in this hanging behaviour.
Best regards,
Martijn van de Giessen
--- End Message ---
--- Begin Message ---
Hi,
your bug has been filed against the "linux-2.6" source package and was filed for
a kernel older than the recently released Debian 7.x / Wheezy with a severity
less than important.
We don't have the ressources to reproduce the complete backlog of all older kernel
bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy
or a more recent kernel from testing or unstable, please reopen the bug by sending
a mail to control@bugs.debian.org with the following three commands included in the
mail:
reopen BUGNUMBER
reassign BUGNUMBER src:linux
thanks
Cheers,
Moritz
--- End Message ---
Reply to: