[Bug 246067] Re: Kernel panic during boot after upgrading to kernel 2.6.26.3-generic

Scott Wegner swegner2 at gmail.com
Sat Jul 19 21:47:32 UTC 2008


I'm also able to boot without any problem.  I'm using VirtualBox 1.6.2
(not OSE), with x86 Hardy alpha 2, kernel version 2.6.26-4.  I do have
"VT-x/AMD-V" enabled, and I believe I also was able to boot alpha 1
with this option as well.

I'm not home this weekend, so I won't be able to test with VT-x/AMD-V
off.  If nobody else has responded by late Sunday, I can give it a
try.

On Sat, Jul 19, 2008 at 3:02 PM, Jon Packard <jon at linux.devlin85.com> wrote:
> peter76: Thanks very much for your input on this. I would be interested
> to know if you have either VT-x or AMD-V enabled (Virtual machine
> settings > General > Advanced). If so, try disabling it and see if you
> are still able to boot the latest Intrepid kernel. Also, which version
> of Virtualbox or Virtualbox-OSE (Open Source Edition) are you using?
> Thanks!
>
> --
> Kernel panic during boot after upgrading to kernel 2.6.26.3-generic
> https://bugs.launchpad.net/bugs/246067
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in The Linux Kernel: Invalid
> Status in "linux" source package in Ubuntu: Confirmed
>
> Bug description:
> Running Intrepid Alpha1 in a Virtualbox 1.6.2 guest. Host is Hardy.
>
> linux-image-2.6.26-3-generic:
>  Installed: 2.6.26-3.9
>  Candidate: 2.6.26-3.9
>  Version table:
>  *** 2.6.26-3.9 0
>        500 http://us.archive.ubuntu.com intrepid/main Packages
>        100 /var/lib/dpkg/status
>
> Expected result: System boots correctly.
>
> Actual result: System fails to boot with kernel panic errors.
>
> Errors on screen (see attached for screen shot):
> Code: Bad EIP value.
> Kernel panic - not syncing: Attempted to kill the idle task!
>
> I can boot to linux-image-2.6.26-2-generic without any problems after the upgrade.
>

-- 
Kernel panic during boot after upgrading to kernel 2.6.26.3-generic
https://bugs.launchpad.net/bugs/246067
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.




More information about the kernel-bugs mailing list