My touchpad doesn't work anymore after https://github.com/freebsd/freebsd-src/commit/13d00a43cba4c35fcc9e0ab567baf530126a6348 It works fine if I revert this commit. This is a Dell Precision 3520 iichid0: <DLL07A9:00 044E:120B I2C HID device> at addr 0x2c irq 51 on iicbus7 hidbus0: <HID bus> on iichid0 hms0: <DLL07A9:00 044E:120B Mouse> on hidbus0 hms0: 3 buttons and [XYWH] coordinates ID=1 Not sure if it's the same problem as bug #280290, creating a new one.
Can you share a verbose dmesg with and without this commit ?
Created attachment 252985 [details] bad
Created attachment 252986 [details] good
CC'ing wulf I've recompiled a kernel with IICHID_DEBUG and did what wulf@ asked in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280290#c2 without 13d00a43cba4 (working touchpad): hkbd0: detached iichid0: iichid device close iichid0: HID command I2C_HID_CMD_SET_POWER(1) hkbd0: detached hms0: detached hidbus0: detached iichid0: detached iicbus7: <unknown card> at addr 0x2c iichid0: <DLL07A9:00 044E:120B I2C HID device> at addr 0x2c irq 51 on iicbus7 hidbus0: <HID bus> on iichid0 hms0: <DLL07A9:00 044E:120B Mouse> on hidbus0 hms0: 3 buttons and [XYWH] coordinates ID=1 hkbd0: <DLL07A9:00 044E:120B Keyboard> on hidbus0 kbd2 at hkbd0 after issuing kldunload iichid, the touchpad stopped working. with 13d00a43cba4 (non working touchpad): hkbd0: detached iichid0: iichid device close hms0: detached hidbus0: detached iichid0: detached iicbus7: <unknown card> at addr 0x2c iichid0: <DLL07A9:00 044E:120B I2C HID device> at addr 0x2c irq 51 on iicbus7 hidbus0: <HID bus> on iichid0 hms0: <DLL07A9:00 044E:120B Mouse> on hidbus0 hms0: 3 buttons and [XYWH] coordinates ID=1 hkbd0: <DLL07A9:00 044E:120B Keyboard> on hidbus0 kbd2 at hkbd0
Created attachment 253580 [details] wait_for_reset.patch I guess that compiling driver into kernel changes a winner of a race between HID hardware reset and iichid children initialization. Test attached patch. Amongst other things it adds a waiting for HID device reset acknowledge that fixes the race.
(In reply to Vladimir Kondratyev from comment #5) It's still broken.
*** This bug has been marked as a duplicate of bug 280290 ***