kernel-packages team mailing list archive

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

oCean, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/511557/comments/11
regarding this being fixed with an update. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line and then choosing a new status in the revealed drop down
box. You can learn more about bug statuses at
https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time
to report this bug and helping to make Ubuntu better. Please submit any
future bugs you may find.

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

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

-- 
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:
  Invalid
Status in “linux” source package in Lucid:
  Invalid

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