GUI freezes mouse input, system locks itself, system still functioning, crashed mouse/touch

Bug #1126109 reported by Jean Lucas
This bug report is a duplicate of:  Bug #1068994: button1 gets stuck after a while. Edit Remove
8
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubuntu-nexus7
New
Undecided
Unassigned

Bug Description

After suspend/resume cycle, system freezes when opening USC and terminal, crashes mouse/touch daemon, system still functioning in background, suspend/resume and rotate have no effect on restoring mouse/touch functionality. Had to hard reset.

ProblemType: KernelOops
DistroRelease: Ubuntu 13.04
Package: linux-image-3.1.10-9-nexus7 3.1.10-9.26
Uname: Linux 3.1.10-9-nexus7 armv7l
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.8-0ubuntu4
Architecture: armhf
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: jean 1586 F.... pulseaudio
CrashDB:
 {"impl": "launchpad",
                             "project": "ubuntu-nexus7",
                             "bug_pattern_url": "http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml",
                           }
Date: Fri Feb 15 06:04:56 2013
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=39c9552e-a9e8-45f8-862a-804a333f0796
InstallationDate: Installed on 2013-02-11 (4 days ago)
InstallationMedia: Ubuntu Raring Ringtail (development branch) - armhf (20130209-15:18)
InterpreterPath: /usr/bin/python3.3
Lspci:

Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MarkForUpload: True
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB:
 0 tegra_fb
 1 tegra_fb
ProcKernelCmdLine: tegra_wdt.heartbeat=30 tegraid=30.1.3.0.0 mem=1022M@2048M android.commchip=0 vmalloc=128M androidboot.serialno=015d24bc7d5c1006 video=tegrafb no_console_suspend=1 console=none debug_uartport=hsport usbcore.old_scheme_first=1 lp0_vec=8192@0xbddf9000 tegra_fbmem=8195200@0xabe01000 core_edp_mv=0 audio_codec=rt5640 board_info=f41:a00:1:44:2 tegraboot=sdmmc gpt gpt_sector=30535679 androidboot.bootloader=4.13 root=/dev/mmcblk0p9 ro console=tty0 access=m2 quiet splash
ProcModules: zram 8348 4 - Live 0xbf000000 (C)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.1.10-9-nexus7 N/A
 linux-backports-modules-3.1.10-9-nexus7 N/A
 linux-firmware 1.102
SourcePackage: linux-nexus7
StagingDrivers: zram
Title: suspend/resume failure
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Jean Lucas (nosebb) wrote :
description: updated
Revision history for this message
Hein van Dam (h-t-vandam) wrote :

The description in bug #1068994 doesn't fit this one as far as I can see. I have exactly the same problem as of kernel 3.8*. at least the later ones. The first gave no screen at all by the way. Previous kernels 3.7 were OK with regard to return from suspend properly.

P.S. I use a desktop which I usually set to suspend after 30 min.

Revision history for this message
Oliver Grawert (ogra) wrote :

how do you run a 3.8 kernel on a nexus7 tablet ? note that this bug is about nexus7 enablement in ubuntu

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.