After Suspend (to RAM) Cando touchscreen stops working

Bug #783587 reported by Atheist1993
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Fedora
New
Undecided
Unassigned
linux (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

On my ACER1825PTZ (netvertible) a capacitive touch-screen (listed as Cando) is used.
It works quite well, but after suspending (and unsuspending of course) it didn't restart (i.e. it doesn't respond to any touch).
Facts:
-lsusb doesn't list (it did before suspend)
-hid-cando kernel-module is loaded
-removing and reinserting it didn't do anything
-restarting udev didn't help, too
-Ubuntu version 11.04

description: updated
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Hello Atheist1993
Can you please reproduce the bug and attach here, using below button 'Add attachment or patch' the files:
/var/log/kern.log
/var/log/kern.log.1
/var/log/dmesg
Thanks
Fabio

Changed in ubuntu:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in ubuntu:
status: Incomplete → Expired
Revision history for this message
sapiensapiens (sapiensapiens) wrote :
Changed in ubuntu:
status: Expired → Incomplete
Revision history for this message
sapiensapiens (sapiensapiens) wrote :
Revision history for this message
sapiensapiens (sapiensapiens) wrote :
Changed in ubuntu:
status: Incomplete → Confirmed
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Hello sapienssapiens
From the attached logs i can see that you are running an upstream kernel (3.0.0-rc7)
To triage your bug we need to work with a standard kernel, so if you are in natty please upgrade to oneiric, elsewhere if you are in Oneiric boot from the standard kernel and attach the requested files again.
Thanks
Fabio
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

Revision history for this message
sapiensapiens (sapiensapiens) wrote :

Hey Fabio,

Thanks for the prompt reply. I attached the following files for a vanilla kernel on a fresh Oneiric install:
/var/log/kern.log
/var/log/dmesg
/var/log/dmesg.0

There's no /var/log/kern.log.1 on my system.

I hope this helps,

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Ok, looking at kern.log we can see just at the start this error:
WARNING: at /build/buildd/linux-3.0.0/drivers/pci/dmar.c:634 warn_invalid_dmar+0x8f/0xa0()

Hardware name: Aspire 1825PTZ

Nov 13 18:59:57 malti-Aspire-1825PTZ kernel: [ 0.000000] Your BIOS is broken; DMAR reported at address 0! <----

Nov 13 18:59:57 malti-Aspire-1825PTZ kernel: [ 0.000000] BIOS vendor: INSYDE; Ver: V1.3127; Product Version: V1.3127
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

So please try to fix this reinstalling or updating your bios.
Thanks
Fabio

Changed in ubuntu:
status: Confirmed → Incomplete
Revision history for this message
sapiensapiens (sapiensapiens) wrote :

Nice catch!

But...I reinstalled the BIOS but the issue persists. Exact same output. The BIOS version I have is the latest one (V1.3127) so updating doesn't apply here.

The issue doesn't affect Windows 7.

Thanks again,

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

From Kern.log attached in #7
Nov 13 18:59:57 malti-Aspire-1825PTZ kernel: [ 0.000000] WARNING: at /build/buildd/linux-3.0.0/drivers/pci/dmar.c:634 warn_invalid_dmar+0x8f/0xa0()
Nov 13 18:59:57 malti-Aspire-1825PTZ kernel: [ 0.000000] Hardware name: Aspire 1825PTZ
Nov 13 18:59:57 malti-Aspire-1825PTZ kernel: [ 0.000000] Your BIOS is broken; DMAR reported at address 0!
Nov 13 18:59:57 malti-Aspire-1825PTZ kernel: [ 0.000000] BIOS vendor: INSYDE; Ver: V1.3127; Product Version: V1.3127
Nov 13 18:59:57 malti-Aspire-1825PTZ kernel: [ 0.000000] Modules linked in:
Nov 13 18:59:57 malti-Aspire-1825PTZ kernel: [ 0.000000] Pid: 0, comm: swapper Not tainted 3.0.0-12-generic #20-Ubuntu
Nov 13 18:59:57 malti-Aspire-1825PTZ kernel: [ 0.000000] Call Trace:
Nov 13 18:59:57 malti-Aspire-1825PTZ kernel: [ 0.000000] [<ffffffff8105e83f>] warn_slowpath_common+0x7f/0xc0
Nov 13 18:59:57 malti-Aspire-1825PTZ kernel: [ 0.000000] [<ffffffff815f613f>] ? bad_to_user+0x7e9/0x7e9
Nov 13 18:59:57 malti-Aspire-1825PTZ kernel: [ 0.000000] [<ffffffff8105e8df>] warn_slowpath_fmt_taint+0x3f/0x50
Nov 13 18:59:57 malti-Aspire-1825PTZ kernel: [ 0.000000] [<ffffffff81ae7584>] ? early_ioremap+0x13/0x15
Nov 13 18:59:57 malti-Aspire-1825PTZ kernel: [ 0.000000] [<ffffffff81add125>] ? __acpi_map_table+0x13/0x19
Nov 13 18:59:57 malti-Aspire-1825PTZ kernel: [ 0.000000] [<ffffffff81323d7f>] warn_invalid_dmar+0x8f/0xa0
Nov 13 18:59:57 malti-Aspire-1825PTZ kernel: [ 0.000000] [<ffffffff8136b0f4>] ? acpi_tb_verify_table+0x54/0x58
Nov 13 18:59:57 malti-Aspire-1825PTZ kernel: [ 0.000000] [<ffffffff81affa90>] check_zero_address+0x57/0xff
Nov 13 18:59:57 malti-Aspire-1825PTZ kernel: [ 0.000000] [<ffffffff815f613f>] ? bad_to_user+0x7e9/0x7e9
Nov 13 18:59:57 malti-Aspire-1825PTZ kernel: [ 0.000000] [<ffffffff81affb4e>] detect_intel_iommu+0x16/0xad
Nov 13 18:59:57 malti-Aspire-1825PTZ kernel: [ 0.000000] [<ffffffff81ad8a13>] pci_iommu_alloc+0x44/0x6f
Nov 13 18:59:57 malti-Aspire-1825PTZ kernel: [ 0.000000] [<ffffffff81ae6fd9>] mem_init+0x19/0xec
Nov 13 18:59:57 malti-Aspire-1825PTZ kernel: [ 0.000000] [<ffffffff81ad0a2c>] start_kernel+0x1d5/0x3df
Nov 13 18:59:57 malti-Aspire-1825PTZ kernel: [ 0.000000] [<ffffffff81ad0388>] x86_64_start_reservations+0x132/0x136
Nov 13 18:59:57 malti-Aspire-1825PTZ kernel: [ 0.000000] [<ffffffff81ad0140>] ? early_idt_handlers+0x140/0x140
Nov 13 18:59:57 malti-Aspire-1825PTZ kernel: [ 0.000000] [<ffffffff81ad0459>] x86_64_start_kernel+0xcd/0xdc
Nov 13 18:59:57 malti-Aspire-1825PTZ kernel: [ 0.000000] ---[ end trace a7919e7f17c0a725 ]---
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

Revision history for this message
fgossart (fabrice-gossart) wrote :

having a 1825ptz, I have the same bug when suspend and BIOS is V1.3127
I tried with some kernels 3.0XX and 3.1XX
ubuntu is 11.10 64

Revision history for this message
fgossart (fabrice-gossart) wrote :

I try now the kernel 3.2 RC2

My wireless is not active now

But suspend touchscreen bug is fixed.

affects: ubuntu → linux (Ubuntu)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
mweyen (mweyen) wrote :

i have the same problem as described with the latest precise beta version (and before with oneiric). Acer 1825PTZ here too

tags: added: natty oneiric precise
Revision history for this message
Brad Figg (brad-figg) wrote : Test with newer development kernel (3.2.0-23.36)

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.2.0-23.36
Revision history for this message
mweyen (mweyen) wrote :

seems to be fixed for me in precise with the updates of now

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

@Atheist1993

Can you apply the latest updates and see if the latest kernel also fixes this bug for you?

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.