From: Jonathan Nieder <jrnieder@gmail.com>
To: Ping Cheng <pinglinux@gmail.com>
Cc: dmitry.torokhov@gmail.com, "Bjørn Mork" <bjorn@mork.no>,
linux-input@vger.kernel.org,
"Jason Gerecke" <killertofu@gmail.com>,
"Chris Bagwell" <chris@cnpbagwell.com>,
"Nils Kanning" <nils@kanning.de>
Subject: Re: [RFC/PATCH] Revert "Input: wacom - add 0xE5 (MT device) support"
Date: Sat, 16 Jun 2012 17:25:45 -0500 [thread overview]
Message-ID: <20120616222545.GA1660@burratino> (raw)
In-Reply-To: <CAF8JNh+-5z7xDJrTTTE1GP5E-MD1AnWPJiC43aTbjNLGv8pbwA@mail.gmail.com>
Hi Ping,
Ping Cheng wrote:
> Here is an update on my testing (for hardware, I have to test to be
> sure). The result shows driver in upstream and 3.2.20 both work with
> TPC2FG.
Again, thanks much for this.
Nils (cc-ed) tested Linus's "master" branch (3.5-rc2+) this morning.
The outcome:
| I built the kernel from the git repository as you described. The tablet
| does not work.
|
| lsusb -t gives:
| Port 5: Dev 5, If 0, Class=HID, Driver=, 12M
|
| The dmesg output is attached. The two input files mentioned in this
| file, which are related to the wacom tablet, are not there after
| booting.
Logs at [1].
For comparison, v3.4.2 works fine. v3.4.2 plus some unrelated
Intuous5 support patches (9fee619505bd + f860e581fd47 + 9b5b95dd516a +
ae584ca47328) also works fine.
Nils also tested v3.4.2 plus the following patch.
f393ee2b814e Input: wacom - retrieve maximum number of touch points
from the HID usage table when it is supported
The exact patch used is at [2]. That produced:
| Linux video capture interface: v2.00
| ------------[ cut here ]------------
| kernel BUG at mm/slab.c:505!
| invalid opcode: 0000 [#1] SMP
[...]
| Pid: 579, comm: modprobe Not tainted 3.4.2-amd64 #1 LENOVO 42992QG/42992QG
[...]
| Call Trace:
| [<ffffffff810ef84e>] ? kfree+0x50/0x6c
| [<ffffffffa04029cd>] ? wacom_probe+0x52c/0x957 [wacom]
| [<ffffffffa006866b>] ? usb_probe_interface+0xf2/0x15d [usbcore]
which is "BUG_ON(!PageSlab(page))" in page_get_cache() and represents
a free of an invalid pointer.
Full log at [3].
Known problem? Any ideas for tracking it down?
Thanks again and hope that helps,
Jonathan
[1] http://bugs.debian.org/677164#87
[2] http://bugs.debian.org/677164#50
[3] http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=77;filename=dmesg_0001;att=1;bug=677164
next prev parent reply other threads:[~2012-06-16 22:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 1:14 [PATCH 2/2] input: wacom - add 0xE5 (MT device) support Ping Cheng
2012-04-30 4:10 ` Dmitry Torokhov
2012-06-14 21:23 ` [RFC/PATCH] Revert "Input: wacom - add 0xE5 (MT device) support" Jonathan Nieder
2012-06-14 23:51 ` Ping Cheng
2012-06-15 0:27 ` Jonathan Nieder
2012-06-15 19:08 ` Ping Cheng
2012-06-16 3:39 ` Jonathan Nieder
2012-06-16 4:01 ` Jonathan Nieder
2012-06-19 0:06 ` Ping Cheng
2012-06-16 22:25 ` Jonathan Nieder [this message]
2012-06-17 0:43 ` Chris Bagwell
2012-06-17 21:08 ` Nils Kanning
2012-06-18 2:39 ` Chris Bagwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120616222545.GA1660@burratino \
--to=jrnieder@gmail.com \
--cc=bjorn@mork.no \
--cc=chris@cnpbagwell.com \
--cc=dmitry.torokhov@gmail.com \
--cc=killertofu@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=nils@kanning.de \
--cc=pinglinux@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).