linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 211479] New: hid-generic: offset (0) exceeds report_count (0)
Date: Sat, 30 Jan 2021 13:11:07 +0000	[thread overview]
Message-ID: <bug-211479-208809@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=211479

            Bug ID: 211479
           Summary: hid-generic: offset (0) exceeds report_count (0)
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.10.11
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: USB
          Assignee: drivers_usb@kernel-bugs.kernel.org
          Reporter: andreas.thalhammer@linux.com
        Regression: No

Created attachment 295005
  --> https://bugzilla.kernel.org/attachment.cgi?id=295005&action=edit
relevent dmesg part...

After updating the firmware of my Wooting Two keyboard to the newest version
(in Windows, not Linux), I get this during boot-up (output copied from dmesg):

hid-generic 0003:03EB:FF02.0006: offset (0) exceeds report_count (0)
RIP: 0010:__alloc_pages_nodemask+0x1bc/0x240

see attatchment...

There is to say that I also have a mouse and a gamepad connected, also with a
couple of input device nodes each.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2021-01-30 13:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-30 13:11 bugzilla-daemon [this message]
2021-01-30 14:00 ` [Bug 211479] hid-generic: offset (0) exceeds report_count (0) bugzilla-daemon
2021-01-30 14:05 ` bugzilla-daemon

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=bug-211479-208809@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-usb@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).