From: Johannes Berg <johannes@sipsolutions.net>
To: Bob Copeland <me@bobcopeland.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-input@vger.kernel.org
Subject: Re: 2.6.26-rc3 - appletouch resume "incomplete data package"
Date: Mon, 26 May 2008 13:06:44 +0200 [thread overview]
Message-ID: <1211800004.17151.51.camel@johannes.berg> (raw)
In-Reply-To: <b6c5339f0805251324k70a3a56ci9cab5274acc2d01d@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 963 bytes --]
On Sun, 2008-05-25 at 16:24 -0400, Bob Copeland wrote:
> This appears to be a regression since 2.6.25. After resuming, I get:
>
> appletouch: incomplete data package (first byte: 2, length: 4).
> appletouch: incomplete data package (first byte: 2, length: 4).
> appletouch: incomplete data package (first byte: 2, length: 4).
> [...]
>
> And the touchpad doesn't work. This is on a first gen MacBook. I
> didn't see any changes to the driver itself in that timeframe.
> Anyone have ideas, or should I try a bisect?
I have intermittently seen this problem happen for quite a while, a
bisect will probably not help you. The "incomplete data package" message
doesn't actually seem to be related to the fact that suspend/resume
sometimes breaks the touchpad though, it seems to happen, for example,
when you switch from X to a console and back, something must be bad with
the timing, possibly even in the hardware.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2008-05-26 11:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-25 20:24 2.6.26-rc3 - appletouch resume "incomplete data package" Bob Copeland
2008-05-26 11:06 ` Johannes Berg [this message]
2008-05-30 2:56 ` Bob Copeland
2008-05-30 8:41 ` Johannes Berg
2008-05-26 12:29 ` Oliver Neukum
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=1211800004.17151.51.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=me@bobcopeland.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