new kernel doesn't boot in 11.10

Bug #828962 reported by little jo
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
High
Leann Ogasawara

Bug Description

How to reproduce this bug:
-reboot on the new kernel
-computer doesn't boot

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: linux-image-3.0.0-8-generic 3.0.0-8.11
ProcVersionSignature: Ubuntu 3.0.0-7.9-generic 3.0.0
Uname: Linux 3.0.0-7-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: joseph 1365 F.... pulseaudio
CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0x38540000 irq 45'
   Mixer name : 'Realtek ALC268'
   Components : 'HDA:10ec0268,1025015b,00100101'
   Controls : 8
   Simple ctrls : 5
Date: Thu Aug 18 19:40:33 2011
HibernationDevice: RESUME=UUID=e84c429d-199c-4954-bf29-fcd80ea39942
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110802.1)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Acer AOA110
ProcEnviron:
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-7-generic root=UUID=2d9e7470-cadd-4cca-be34-04d68f7f31e8 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.0.0-7-generic N/A
 linux-backports-modules-3.0.0-7-generic N/A
 linux-firmware 1.59
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/09/2008
dmi.bios.vendor: INSYDE
dmi.bios.version: v0.3109
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Base Board Product Name
dmi.board.vendor: Intel Corp.
dmi.board.version: Base Board Version
dmi.chassis.type: 1
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnINSYDE:bvrv0.3109:bd05/09/2008:svnAcer:pnAOA110:pvr1:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
dmi.product.name: AOA110
dmi.product.version: 1
dmi.sys.vendor: Acer

Revision history for this message
little jo (littel-jo) wrote :
Revision history for this message
little jo (littel-jo) wrote :

package problem:
apt-cache policy linux-image-3.0.0-8-generic
linux-image-3.0.0-8-generic:
  Installé : 3.0.0-8.11
  Candidat : 3.0.0-8.11
 Table de version :
 *** 3.0.0-8.11 0
        500 http://fr.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages
        100 /var/lib/dpkg/status

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi,

Just curious if the 3.0.0-8.10 kernel was able to boot? I want to narrow down the the window where the regression was likely introduced. The 3.0.0-8.10 i386 deb can be found at:

https://launchpad.net/ubuntu/oneiric/i386/linux-image-3.0.0-8-generic/3.0.0-8.10

You'll want to uninstall the 3.0.0-8.11 kernel prior to installing the 3.0.0-8.10 kernel to ensure you really do boot into the 3.0.0-8.10 kernel to test. Please let us know your results. Thanks.

Changed in linux (Ubuntu):
assignee: nobody → Leann Ogasawara (leannogasawara)
importance: Undecided → High
status: New → Incomplete
Revision history for this message
little jo (littel-jo) wrote :

That's strange... Now It boots (i tried twice):
uname -a
Linux ligier 3.0.0-8-generic #11-Ubuntu SMP Fri Aug 12 20:20:03 UTC 2011 i686 i686 i386 GNU/Linux

apt-cache policy linux-image-3.0.0-8-generic
linux-image-3.0.0-8-generic:
  Installé : 3.0.0-8.11
  Candidat : 3.0.0-8.11
 Table de version :
 *** 3.0.0-8.11 0
        500 http://fr.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages
        100 /var/lib/dpkg/status

I made this mistake because the boot was longer as usually and with a lot of errors.

I think we can close the bug.

Revision history for this message
little jo (littel-jo) wrote :

> I think we can close the bug.

Well, i don't think so... I have twice the bug now.

I have a lot of line:
udevd[116]: failed to execute '/lib/udev/input_id' 'input_id /devices/virtual/input/mice': No such file or directory

Then black screen (with no disk access)
CTRL+ALT+Suppr wort to reboot.
A long press on the button on/off works to shutdown.
A small press on the button on/off has no effect.

After 2 bad tries, the kernel now boots. i doesn't hope it's a hardware problem...

Revision history for this message
the gala (1234mirkogala) wrote :

try this in terminal type

sudo cp /etc/default/grub /etc/default/grub.backup
and
sudo nano /etc/default/grub or
sudo gedit /etc/default/grub

then change to look like this

GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=off"
GRUB_CMDLINE_LINUX=""

you must add "acpi=off" whit the "quite splash"
type in terminal

sudo update grub

then restart computer that works for me

Revision history for this message
the gala (1234mirkogala) wrote :

i had new problem
now i can start without any problem but when i computer cant shutdown
i must push start button to shutdown

Revision history for this message
Grzegorz G. (grzesiek1e5) wrote :

This problem with shutdown is caused by acpi=off parameter.

ACPI is responsible for powering your PC off, so when you disable ACPI, you have to turn your PC off manually. It's not a bug.

(But inability to boot with ACPI enabled is a kernel bug.)

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Closing this bug with Won't fix as this kernel / release is no longer supported.
Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04)
Thanks!

Changed in linux (Ubuntu):
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.