kernel-packages team mailing list archive

[Thomas Schweikle <919961@xxxxxxxxxxxxxxxxxx>]

** Changed in: linux (Ubuntu)
       Status: Confirmed => Fix Released

-- 
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/919961

Title:
  Rescue mode not usable with latest kernel

Status in “linux” package in Ubuntu:
  Fix Released

Bug description:
  If booting the lates kernel "linux-image-3.0.0-15-server", rescue mode
  is not usable. The system will boot into rescue mode, then show the
  menu, but no keypress is accepted. You can't select any entry using
  up- and down-arrow keys, enter isn't accepted, tab is ignored.

  Booting kernel "linux-image-3.0.0-14-server" all is ok again.

  The same applies for all other latest kernels for all other Ubuntu-
  Versions:

  Ubuntu 10.04 LTS: "linux-image-2.6.32-38-virtual" does not work with rescue mode, while "linux-image-2.6.32-37-virtual" works
  Ubuntu 10.10: "linux-image-2.6.35-32-server" does not work with rescue mode, while "linux-image-2.6.35-31-server" works
  Ubuntu 11.04: "linux-image-2.6.38-13-server" does not work with rescue mode, while "linux-image-2.6.38-12-server" works
  Ubuntu 11.10: "linux-image-3.0.0-15-server" does not work with rescue mode, while "linux-image-3.0.0-14-server" works
  Ubuntu 12.04: "linux-image-3.2.0-9-generic" does not work with rescue mode, while "linux-image-3.2.0-8-generic" works

  For plain vanilla kernels: "linux-image-3.1.10" doe not work with rescue mode, while "linux-image-3.1.9" works
  Other plain vanilla kernels I did not test. 

  All tests where done using kvm-qemu and VMwareWorkstation/Player 7 or
  8

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: linux-image (not installed)
  ProcVersionSignature: Ubuntu 3.0.0-14.23-server 3.0.9
  Uname: Linux 3.0.0-14-server x86_64
  AcpiTables:
   Error: command ['sudo', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 1: Sorry, try again.
   Sorry, try again.
   Sorry, try again.
   sudo: 3 incorrect password attempts
  AlsaDevices:
   total 0
   crw-rw---- 1 root audio 116,  1 2012-01-22 11:09 seq
   crw-rw---- 1 root audio 116, 33 2012-01-22 11:09 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  Date: Sun Jan 22 12:01:29 2012
  HibernationDevice: RESUME=UUID=f8a560f8-2358-4179-8350-3ba1009f3772
  InstallationMedia: Ubuntu-Server 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: FUJITSU PRIMERGY RX300 S6
  PciMultimedia:
   
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=de_DE.UTF-8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-14-server root=UUID=bc692d1e-ddb7-4a4b-b240-95da6efeabc0 ro recovery nomodeset
  RelatedPackageVersions:
   linux-restricted-modules-3.0.0-14-server N/A
   linux-backports-modules-3.0.0-14-server  N/A
   linux-firmware                           1.60
  RfKill: Error: [Errno 2] No such file or directory
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/06/2010
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: 6.00 Rev. 1.08.2619.N1
  dmi.board.asset.tag: -
  dmi.board.name: D2619
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D2619-N15 WGS10 GS02
  dmi.chassis.asset.tag: YL6T019858
  dmi.chassis.type: 23
  dmi.chassis.vendor: FUJITSU
  dmi.chassis.version: RX300S6R1
  dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvr6.00Rev.1.08.2619.N1:bd10/06/2010:svnFUJITSU:pnPRIMERGYRX300S6:pvrGS01:rvnFUJITSU:rnD2619:rvrS26361-D2619-N15WGS10GS02:cvnFUJITSU:ct23:cvrRX300S6R1:
  dmi.product.name: PRIMERGY RX300 S6
  dmi.product.version: GS01
  dmi.sys.vendor: FUJITSU

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