kernel-packages team mailing list archive

["Christopher M. Penalver" <christopher.m.penalver@xxxxxxxxx>]

oCean, this bug was reported a while ago and there hasn't been any
activity in it recently. We were wondering if this is still an issue? If
so, could you please test for this with the latest development release
of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
/daily-live/current/ .

If it remains an issue, could you please run the following command in
the development release from a Terminal
(Applications->Accessories->Terminal), as it will automatically gather
and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's
Status as Confirmed. Please let us know your results. Thank you for your
understanding.

** Changed in: linux (Ubuntu)
       Status: Triaged => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/511557

Title:
  Kernel 2.6.32-11 fails to boot using VirtualBox

Status in “linux” package in Ubuntu:
  Incomplete
Status in “linux” source package in Lucid:
  Triaged

Bug description:
  Using Virtualbox OSE [version: 3.0.8_ose r53138]
  Fresh install of Lucid, Alpha 2.
  Running kernel: 2.6.32-10.14 generic
  Ran all updates (ca. 170+) including kernel update to 2.6.32-11.15
  Rebooted, screen "GRUB loading" appears, then - nothing, only black screen, (virtual) machine is frozen
  Holding shift key, does show grub menu (otherwise not starting) and 2.6.32-10 still boots fine
  Choosing 2.6.32-11 recovery mode, shows:

    ] CPU supports 0 MCE banks
    ] using mwait in idle threads
    ] Performance Events: unsupported p6 CPU model 15 no PMU driver, software events only.
    ] Checking 'hlt' instruction... OK

  Booting in 2-6.32-10 kernel, succeeds, but dmesg shows

    ] weird, boot CPU (#0) not listed by the bios.
    ] Brought up 1 CPUs
    ] CPU0 attaching NULL sched-domain

  and further booting process.

  What is holding back the 32-11 version to boot?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/511557/+subscriptions