Kernel 2.6.32-21.32 fails to boot Dell D505 Laptops beyond splash
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Following an update-manager upgrade of Lucid 10.4 from kernel 2.6.32-20.30 to 2.6.32-21.32, a Dell Latitude D505 laptop fails to continue after the Plymouth splash screen. The screen remains black and the system does not respond to ctrl_alt_fx nor to alt_sysreq commands. A physical power cycle is required to recover.
This is repeatable and confirmed on a second D505 laptop.
The previous kernel 2.6.32-20.30 continues to function normally.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-headers-
Regression: Yes
Reproducible: Yes
ProcVersionSign
Uname: Linux 2.6.32-20-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'I82801DBICH4'
Mixer name : 'SigmaTel STAC9750,51'
Components : 'AC97a:83847650'
Controls : 36
Simple ctrls : 23
CurrentDmesg:
[ 24.584019] eth0: no IPv6 routers present
[ 24.616017] eth1: no IPv6 routers present
Date: Fri Apr 23 12:34:24 2010
HibernationDevice: RESUME=
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release Candidate i386 (20091020.3)
MachineType: Dell Inc. Latitude D505
PackageArchitec
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANG=en_GB.utf8
SHELL=/bin/bash
RelatedPackageV
RfKill:
SourcePackage: linux
dmi.bios.date: 09/03/2004
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: 0H2049
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Latitude D505
dmi.sys.vendor: Dell Inc.
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
tags: | removed: regression-potential |
To confirm, recovery mode does boot into the CLI and the failure occurs, as above, when gdm is launched.