Touching touchpad too soon after resume causes lock up and breaks init.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Medium
|
Unassigned |
Bug Description
If I try to use the touchpad the instant my laptop resumes, it will freeze. When I force it off and then boot again, I get a busybox shell. Above it are a series of mount errors, claiming "no such file or directory", and "Target filesystem does not have /sbin/init. No init found. Try passing init=bootarg."
WORKAROUND: This problem disappears when I switched back in gconf to having the screen lock on resume. So the error only happens when the screen lock has been disabled.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image (not installed)
Regression: Yes
Reproducible: Yes
ProcVersionSign
Uname: Linux 2.6.35-8-generic i686
AcpiTables: Error: command ['gksu', '-D', 'Apport', '--', '/usr/share/
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/pcmC0D0p: vanya 1393 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xefebc000 irq 44'
Mixer name : 'SigmaTel STAC9200'
Components : 'HDA:83847690,
Controls : 12
Simple ctrls : 7
Date: Thu Jul 15 10:40:30 2010
HibernationDevice: RESUME=
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100706)
MachineType: Dell Inc. Latitude D420
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
RelatedPackageV
SourcePackage: linux
dmi.bios.date: 02/02/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Latitude D420
dmi.sys.vendor: Dell Inc.
tags: | added: acpi |
tags: | added: acpi-table-checksum |
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
This problem disappears when I switched back in gconf to having the screen lock on resume. So the error only happens when the screen lock has been disabled.
(Sorry to not have mentioned that my settings were modified. It just didn't occur to me until I reinstalled and saw the screen lock again. And sorry to not update the bug report until reminded by the recent changes...)