From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Santiago Garcia Mantinan <manty@manty.net>,
Lukas Hejtmanek <xhejtman@mail.muni.cz>
Cc: Michal Jaegermann <michal@harddata.com>, linux-kernel@vger.kernel.org
Subject: Re: Synaptics PS/2 driver and 2.6.0-test11
Date: Sun, 7 Dec 2003 19:54:31 -0500 [thread overview]
Message-ID: <200312071954.31897.dtor_core@ameritech.net> (raw)
In-Reply-To: <20031207221056.GA2990@man.beta.es>
On Sunday 07 December 2003 05:10 pm, Santiago Garcia Mantinan wrote:
> Sorry, I didn't notice this thread till now...
>
> > But why it does not hurt with kernel 2.4.22? Moreover how ACPI BIOS
> > influences synaptics driver? I do not see any BIOS call there...
>
> I have this problem reported as bug 1093 at bugme.osdl.org, my laptop
> is an ACER with intel chipset.
>
> The problem will happen even if you only check the batery status once a
> day, at that time, you can get the lost sync thing in 2.6, but not in
> 2.2, so the problem is not with the gnome applet, in fact I'm seing it
> under icewm and I have been able to reproduce it without any battery
> applet or anything like that, only running the "acpi -V" command each
> minute in a cron, that suffices for getting the errors.
>
> I believe that this should be solved, in 2.6, as it certainly doesn't
> happen on 2.4, if you want more info look at bug #1093 at
> bugme.osdl.org or if you need more details just ask for them.
>
> Hope this helps.
>
> Regards...
The difference is that GPM (I assume you are using it to get Synaptics
support) only logs "protocol violations" when in debug mode, and then it
only checks 2 first bytes. The XFree driver does check the protocol but
its messages usually don't show up in the syslog. In other words in-kernel
Synaptics driver just makes the problem apparent it seems.
>From what I saw in one case where Synaptics was loosing sync it looked
like 2 first bytes of the 6 byte packet were lost (psmouse never got them).
Would be interesting to compile i8042.c with debug and see the full flow
of a problem system...
Dmitry
next prev parent reply other threads:[~2003-12-08 0:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-30 21:46 Synaptics PS/2 driver and 2.6.0-test11 Lukas Hejtmanek
2003-11-30 22:28 ` Dmitry Torokhov
2003-11-30 22:39 ` Lukas Hejtmanek
2003-11-30 23:26 ` Dmitry Torokhov
2003-11-30 23:40 ` Lukas Hejtmanek
2003-12-01 3:25 ` Michal Jaegermann
2003-12-06 12:37 ` Kjartan Maraas
2003-12-07 19:44 ` Lukas Hejtmanek
2003-12-07 22:10 ` Santiago Garcia Mantinan
2003-12-08 0:54 ` Dmitry Torokhov [this message]
2003-12-08 9:54 ` Peter Berg Larsen
2003-12-08 18:16 ` Dmitry Torokhov
2003-12-14 23:10 ` Lukas Hejtmanek
2003-12-08 11:22 ` Santiago Garcia Mantinan
[not found] ` <20031130230144.GA2124@rivenstone.net>
2003-11-30 23:11 ` Lukas Hejtmanek
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=200312071954.31897.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=manty@manty.net \
--cc=michal@harddata.com \
--cc=xhejtman@mail.muni.cz \
/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).