Bastanteroma, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 10, 2012. Please see this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases
We were wondering if this is still an issue in a supported release? If so, could you please provide the information following https://wiki.ubuntu.com/DebuggingKernelSuspend ? As well, could you please confirm this issue exists with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/daily/current/ . If the issue remains, could you please run the following command from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report: apport-collect -p linux <replace-with-bug-number> Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested and remove the tag: needs-upstream-testing This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the text: needs-upstream-testing If this bug is fixed in the mainline kernel, please add the following tags: kernel-fixed-upstream kernel-fixed-upstream-VERSION-NUMBER where VERSION-NUMBER is the version number of the kernel you tested. If the mainline kernel does not fix this bug, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-VERSION-NUMBER where VERSION-NUMBER is the version number of the kernel you tested. If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags: kernel-unable-to-test-upstream kernel-unable-to-test-upstream-VERSION-NUMBER where VERSION-NUMBER is the version number of the kernel you tested. Please let us know your results. Thank you for your understanding. Helpful Bug Reporting Tips: https://help.ubuntu.com/community/ReportingBugs ** Description changed: 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 ProcVersionSignature: Ubuntu 2.6.35-8.13-generic 2.6.35-rc5 Uname: Linux 2.6.35-8-generic i686 AcpiTables: Error: command ['gksu', '-D', 'Apport', '--', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 1: 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 + **** 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/controlC0: vanya 1393 F.... pulseaudio - /dev/snd/pcmC0D0p: vanya 1393 F...m pulseaudio + USER PID ACCESS COMMAND + /dev/snd/controlC0: vanya 1393 F.... pulseaudio + /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,102801d6,00102201' - Controls : 12 - Simple ctrls : 7 + Card hw:0 'Intel'/'HDA Intel at 0xefebc000 irq 44' + Mixer name : 'SigmaTel STAC9200' + Components : 'HDA:83847690,102801d6,00102201' + Controls : 12 + Simple ctrls : 7 Date: Thu Jul 15 10:40:30 2010 HibernationDevice: RESUME=UUID=35d2389b-8d41-44b4-8045-0e716c8e0b78 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100706) MachineType: Dell Inc. Latitude D420 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-8-generic root=UUID=ec1cd2d8-23a2-45d8-8191-908b344ffe64 ro quiet splash ProcEnviron: - LANG=en_US.UTF-8 - SHELL=/bin/bash + LANG=en_US.UTF-8 + SHELL=/bin/bash RelatedPackageVersions: linux-firmware 1.37 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.:bvrA06:bd02/02/2008:svnDellInc.:pnLatitudeD420:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D420 dmi.sys.vendor: Dell Inc. ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/605912 Title: Touching touchpad too soon after resume causes lock up and breaks init. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/605912/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
