From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Linux Kernel Mailing <linux-kernel@vger.kernel.org>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Jiri Kosina <jikos@kernel.org>,
linux-input@vger.kernel.org
Subject: [Regression] 5.3-rc1: hid_llogitech_dj does not work
Date: Thu, 25 Jul 2019 12:07:14 +0200 [thread overview]
Message-ID: <2480108.bWkXKoXas6@kreacher> (raw)
In-Reply-To: <CAHk-=wjm7FQxdF=RKa8Xe23CLNNpbGDOACewgo8e-hwDJ8TyQg@mail.gmail.com>
Hi Hans,
This is similar to a problem I reported some time ago:
https://lore.kernel.org/lkml/2268131.Lc39eCoc3j@kreacher/
and the device affected by it is the same.
The symptom is simply that the mouse just doesn't work (no reaction). If I do
"rmmod hid_llogitech_dj", it says "Killed", but the module does go away and
the mouse starts to work (through the generic code I suppose), but then
the machine hangs on attempts to suspend (nasty).
Reverting all of the hid_llogitech_dj changes between 5.2 and 5.3-rc1:
dbcbabf7da92 HID: logitech-dj: fix return value of logi_dj_recv_query_hidpp_devices
39d21e7e0043 HID: logitech-dj: make const array template static
423dfbc362b7 HID: logitech-dj: Add usb-id for the 27MHz MX3000 receiver
helps here, but the first two don't really look like they can make any difference,
so I guess I'm an unlucky owner of a MX3000 that doesn't quite work as expected.
Any help will be appreciated. :-)
Cheers,
Rafael
next prev parent reply other threads:[~2019-07-25 10:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHk-=wjm7FQxdF=RKa8Xe23CLNNpbGDOACewgo8e-hwDJ8TyQg@mail.gmail.com>
2019-06-11 21:53 ` Strange regression in hid_llogitech_dj (was: Re: Linux 5.2-rc4) Rafael J. Wysocki
2019-06-11 22:02 ` Jiri Kosina
2019-06-12 8:24 ` Rafael J. Wysocki
2019-06-12 8:31 ` Jiri Kosina
2019-06-12 8:51 ` Rafael J. Wysocki
2019-06-12 9:24 ` Jiri Kosina
2019-07-25 10:07 ` Rafael J. Wysocki [this message]
2019-07-25 15:50 ` [Regression] 5.3-rc1: hid_llogitech_dj does not work Hans de Goede
2019-07-29 15:49 ` Hans de Goede
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=2480108.bWkXKoXas6@kreacher \
--to=rjw@rjwysocki.net \
--cc=benjamin.tissoires@redhat.com \
--cc=hdegoede@redhat.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).