[Acer Aspire X1300] Mouse and eventually keyboard freeze

[pgetto]

I've tried upgrading and fresh installs of 14.04 several times. This was done on a fresh install. Mouse freezes very quickly after login (< 1 minute or so). Trying ctrl+alt+F1 and does not switch screens and then the keyboard becomes unresponsive (can still use ssh to connect). After some of the upgrades, often also had excessive display flickering (and mouse and keyboard unresponsiveness) and saw NVRM errors in kern.log.

Tail of current kern.log:
Apr 21 09:06:14 tux2 kernel: [ 960.243734] INFO: task khubd:43 blocked for more than 120 seconds.
Apr 21 09:06:14 tux2 kernel: [ 960.243745] Not tainted 3.13.0-24-generic #46-Ubuntu
Apr 21 09:06:14 tux2 kernel: [ 960.243749] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Apr 21 09:06:14 tux2 kernel: [ 960.243753] khubd D ffff88013fd94440 0 43 2 0x00000000
Apr 21 09:06:14 tux2 kernel: [ 960.243761] ffff8801399c9b00 0000000000000002 ffff8801399c0000 ffff8801399c9fd8
Apr 21 09:06:14 tux2 kernel: [ 960.243770] 0000000000014440 0000000000014440 ffff8801399c0000 ffff880135fe0d80
Apr 21 09:06:14 tux2 kernel: [ 960.243776] ffff8800af903f50 ffff880135fe0d80 0000000000000204 ffff8800af903f30
Apr 21 09:06:14 tux2 kernel: [ 960.243788] Call Trace:
Apr 21 09:06:14 tux2 kernel: [ 960.243800] [<ffffffff81719e89>] schedule+0x29/0x70
Apr 21 09:06:14 tux2 kernel: [ 960.243809] [<ffffffff8153d795>] usb_kill_urb+0x65/0xa0
Apr 21 09:06:14 tux2 kernel: [ 960.243820] [<ffffffff810aae90>] ? prepare_to_wait_event+0x100/0x100
Apr 21 09:06:14 tux2 kernel: [ 960.243826] [<ffffffff8153c528>] usb_hcd_flush_endpoint+0x198/0x200
Apr 21 09:06:14 tux2 kernel: [ 960.243832] [<ffffffff8149a741>] ? rpm_suspend+0x4d1/0x6e0
Apr 21 09:06:14 tux2 kernel: [ 960.243838] [<ffffffff8153f589>] usb_disable_endpoint+0x59/0x90
Apr 21 09:06:14 tux2 kernel: [ 960.243844] [<ffffffff8153f606>] usb_disable_interface+0x46/0x60
Apr 21 09:06:14 tux2 kernel: [ 960.243861] [<ffffffff81541e45>] usb_unbind_interface+0x1b5/0x1c0
Apr 21 09:06:14 tux2 kernel: [ 960.243869] [<ffffffff8148e5bf>] __device_release_driver+0x7f/0xf0
Apr 21 09:06:14 tux2 kernel: [ 960.243875] [<ffffffff8148e653>] device_release_driver+0x23/0x30
Apr 21 09:06:14 tux2 kernel: [ 960.243887] [<ffffffff8148ded8>] bus_remove_device+0x108/0x180
Apr 21 09:06:14 tux2 kernel: [ 960.243893] [<ffffffff8148a989>] device_del+0x129/0x1c0
Apr 21 09:06:14 tux2 kernel: [ 960.243898] [<ffffffff8153f6d0>] usb_disable_device+0xb0/0x290
Apr 21 09:06:14 tux2 kernel: [ 960.243904] [<ffffffff8153424d>] usb_disconnect+0xad/0x200
Apr 21 09:06:14 tux2 kernel: [ 960.243909] [<ffffffff81536d05>] hub_port_connect_change+0xd5/0xb50
Apr 21 09:06:14 tux2 kernel: [ 960.243914] [<ffffffff8153e0d4>] ? usb_control_msg+0xd4/0x110
Apr 21 09:06:14 tux2 kernel: [ 960.243919] [<ffffffff81537c44>] hub_events+0x4c4/0xa20
Apr 21 09:06:14 tux2 kernel: [ 960.243925] [<ffffffff815381d5>] hub_thread+0x35/0x160
Apr 21 09:06:14 tux2 kernel: [ 960.243931] [<ffffffff810aae90>] ? prepare_to_wait_event+0x100/0x100
Apr 21 09:06:14 tux2 kernel: [ 960.243935] [<ffffffff815381a0>] ? hub_events+0xa20/0xa20
Apr 21 09:06:14 tux2 kernel: [ 960.243941] [<ffffffff8108b312>] kthread+0xd2/0xf0
Apr 21 09:06:14 tux2 kernel: [ 960.243947] [<ffffffff8108b240>] ? kthread_create_on_node+0x1d0/0x1d0
Apr 21 09:06:14 tux2 kernel: [ 960.243953] [<ffffffff8172637c>] ret_from_fork+0x7c/0xb0
Apr 21 09:06:14 tux2 kernel: [ 960.243958] [<ffffffff8108b240>] ? kthread_create_on_node+0x1d0/0x1d0

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDmesg: [ 14.204900] init: plymouth-upstart-bridge main process ended, respawning
Date: Mon Apr 21 08:51:34 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 NVIDIA Corporation C77 [GeForce 8200] [10de:084b] (rev a2) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Device [1025:0153]
InstallationDate: Installed on 2014-04-21 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Acer Aspire X1300
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=/dev/mapper/hostname-root2 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2009
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: R01-B3
dmi.board.name: WMCP78M
dmi.board.vendor: Acer
dmi.chassis.type: 3
dmi.chassis.vendor: Acer
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrR01-B3:bd04/01/2009:svnAcer:pnAspireX1300:pvr:rvnAcer:rnWMCP78M:rvr:cvnAcer:ct3:cvr:
dmi.product.name: Aspire X1300
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Mon Apr 21 08:50:26 2014
xserver.configfile: default
xserver.devices:
 input Power Button KEYBOARD, id 6
 input Power Button KEYBOARD, id 7
 input Lite-On Technology Corp. USB Multimedia Keyboard KEYBOARD, id 8
 input Lite-On Technology Corp. USB Multimedia Keyboard KEYBOARD, id 9
 input Logitech USB Optical Mouse MOUSE, id 10
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.15.1-0ubuntu2
xserver.video_driver: nouveau

[penalvch (penalvch)]

pgetto, did this problem not occur in a release prior to 14.04?

[pgetto (phil-gettos)]

No 13.10 runs fine. I have reverted back to it in one LVM and it continues to be good.

Phil Getto
+1.972.728.5514 - Office
+1.214.566.3491 - Mobile
+49.30.2430.9114 - Berlin office

> On Apr 21, 2014, at 19:19, "Christopher M. Penalver" <email address hidden> wrote:
>
> pgetto, did this problem not occur in a release prior to 14.04?
>
> ** Tags added: bios-outdated-r01.c0 regression-potential
>
> ** Changed in: xorg (Ubuntu)
> Importance: Undecided => High
>
> ** Changed in: xorg (Ubuntu)
> Status: New => Incomplete
>
> ** Summary changed:
>
> - Mouse and eventually keyboard freeze
> + [Acer Aspire X1300] Mouse and eventually keyboard freeze
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1310633
>
> Title:
> [Acer Aspire X1300] Mouse and eventually keyboard freeze
>
> Status in “xorg” package in Ubuntu:
> Incomplete
>
> Bug description:
> I've tried upgrading and fresh installs of 14.04 several times. This
> was done on a fresh install. Mouse freezes very quickly after login (<
> 1 minute or so). Trying ctrl+alt+F1 and does not switch screens and
> then the keyboard becomes unresponsive (can still use ssh to connect).
> After some of the upgrades, often also had excessive display
> flickering (and mouse and keyboard unresponsiveness) and saw NVRM
> errors in kern.log.
>
> Tail of current kern.log:
> Apr 21 09:06:14 tux2 kernel: [ 960.243734] INFO: task khubd:43 blocked for more than 120 seconds.
> Apr 21 09:06:14 tux2 kernel: [ 960.243745] Not tainted 3.13.0-24-generic #46-Ubuntu
> Apr 21 09:06:14 tux2 kernel: [ 960.243749] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> Apr 21 09:06:14 tux2 kernel: [ 960.243753] khubd D ffff88013fd94440 0 43 2 0x00000000
> Apr 21 09:06:14 tux2 kernel: [ 960.243761] ffff8801399c9b00 0000000000000002 ffff8801399c0000 ffff8801399c9fd8
> Apr 21 09:06:14 tux2 kernel: [ 960.243770] 0000000000014440 0000000000014440 ffff8801399c0000 ffff880135fe0d80
> Apr 21 09:06:14 tux2 kernel: [ 960.243776] ffff8800af903f50 ffff880135fe0d80 0000000000000204 ffff8800af903f30
> Apr 21 09:06:14 tux2 kernel: [ 960.243788] Call Trace:
> Apr 21 09:06:14 tux2 kernel: [ 960.243800] [<ffffffff81719e89>] schedule+0x29/0x70
> Apr 21 09:06:14 tux2 kernel: [ 960.243809] [<ffffffff8153d795>] usb_kill_urb+0x65/0xa0
> Apr 21 09:06:14 tux2 kernel: [ 960.243820] [<ffffffff810aae90>] ? prepare_to_wait_event+0x100/0x100
> Apr 21 09:06:14 tux2 kernel: [ 960.243826] [<ffffffff8153c528>] usb_hcd_flush_endpoint+0x198/0x200
> Apr 21 09:06:14 tux2 kernel: [ 960.243832] [<ffffffff8149a741>] ? rpm_suspend+0x4d1/0x6e0
> Apr 21 09:06:14 tux2 kernel: [ 960.243838] [<ffffffff8153f589>] usb_disable_endpoint+0x59/0x90
> Apr 21 09:06:14 tux2 kernel: [ 960.243844] [<ffffffff8153f606>] usb_disable_interface+0x46/0x60
> Apr 21 09:06:14 tux2 kernel: [ 960.243861] [<ffffffff81541e45>] usb_unbind_interface+0x1b5/0x1c0
> Apr 21 09:06:14 tux2 kernel: [ 960.243869] [<ffffffff8148e5bf>] __device_release_driver+0x7f/0xf0
> Apr 21 09:06:14 tux2 kernel: ...

[Rick Seitz (alrwseitz1)]

I had the same problem and finally got it resolved by rebooting the system.

sudo service stop light dm
sudo apt-get --purge --nvidia*
sudo apt-get install --reinstall xserver-xorg-video-nouveau
rebooted the computer logged and and used the 304.117 proprietary driver fromt he settings software and update additional drivers tab, it doesn't recognize correctly and calls it a Geforce 9200 but other than that all works fine.

[Rick Seitz (alrwseitz1)]

for on the firt step I used ctrl alt f1 to open a terminal and did the first the command lines from there.

[Tom Winterhalder (thwint)]

After upgrading to 14.04 I also have this flickering problem again. It seems that the old line in options.conf:
options nvidia NVreg_RegistryDwords="PerfLevelSrc=0x2222" NVreg_Mobile=3 NVreg_ModifyDeviceFiles=0

is not read anymore (I found this somewhere in the net and it solved the issue on 13.10).

Using modprobe --resolve-alias nvidia I found the correct driver module name which in my case is nvidia_331

When changing the module name to nvidia_331 in options.conf X doesn't start anymore. When removing the NVreg_ModifyDeviceFiles option X is starting again, but doesn't solve the problem.

I don't know if this is helpful

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[penalvch (penalvch)]

Tom Winterhalder, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report by executing the following in a terminal:
ubuntu-bug xorg

Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information.

For more on this, please see the official Ubuntu documentation:
Ubuntu X.Org Team, Ubuntu Bug Control, and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report will delay your problem being addressed as quickly as possible.

Thank you for your understanding.

[Petr Nosek (petr-nosek)]

Hi, I thing, the same problem as me:

https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1251042

[penalvch (penalvch)]

pgetto, as per http://us.acer.com/ac/en/US/content/drivers an update to your BIOS is available (R01.C0). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report.

Once the BIOS is updated, then please mark this report Status Confirmed.

Thank you for your understanding.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]