kernel-packages team mailing list archive

[Alexander Röhnsch <1177086@xxxxxxxxxxxxxxxxxx>]

Christopher, I decided to skip Raring and try again when Saucy is
released, because Raring did not work at all for me. Therefore, I do not
need a backport. But I can not speak for others.

Apparently there are quite a few who can use Raring. But they need to
annoyingly boot it several times before success. They would certainly
benefit from a backport.

Are there resources for doing a backport anyway? Out of interest, would
the whole saucy kernel be backported?


Am 21.07.2013 19:00, schrieb Christopher M. Penalver:
> Alexander Röhnsch, did you need a backport to a release prior to Saucy
> or may we close this as Status Invalid?
> 
> ** Changed in: linux (Ubuntu)
>        Status: Confirmed => 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/1177086

Title:
  amd64: "Fixing recursive fault but reboot is needed!"

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  After the completed Raring Ringtail amd64 installation every boot ends
  in the following statement "Fixing recursive fault but reboot is
  needed!". No terminal, no gui, no logs at this point. Others say they
  can boot after about 10 tries every time, but I can not. Maybe someone
  can provide logs from a successful boot, but mine are all empty. I
  attach lscpu, lshw and lspci output acquired from the Raring Ringtail
  amd64 live CD. The live mode works fine, the problem arises upon
  installation.

  I can not boot the Raring installation at all.

  Several people experiencing this bug, including me, reported it over
  at bug #1066435, but I was told that, although both bugs share the
  same behaviour, they probably originate from different problems. Also,
  bug #1175660 has a similar error message, but seems able to boot
  properly.

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