Comment 11 for bug 1416601

Revision history for this message
Mario Limonciello (superm1) wrote :

Yes, nothing on 3.18

Originally I didn't test any of the stable releases for 3.18, it was the standard 3.18, I believe the hash assigned to the tag 'v3.18'.
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18-vivid/

It would make sense to me if it was broken somewhere in between v3.18 and v3.18.3 though as lots of stuff that goes into mainline backports to @stable.

I went back and tried the stable releases on the mainline PPA.
v3.18.1: OK
v3.18.2: OK
v3.18.3: Reproduces problem

Between 3.18 and 3.19-rc1 there's 4 commits to i2c-hid (most likely culprit driver to me)
d1c7e29e8d276c669e8790bb8be9f505ddc48888 HID: i2c-hid: prevent buffer overflow in early IRQ
721564a950fdbc07adf9c1e114b73feb97446ec2 i2c-hid / PM: Replace CONFIG_PM_RUNTIME with CONFIG_PM
6296f4a8eb86f9abcc370fb7a1a116b8441c17fd HID: i2c-hid: fix race condition reading reports
08bb7beae7fe102939fe5931222fc09e10d27cda HID: i2c-hid: print the correct data in dbg msg

Between 3.18.2 and 3.18.3 these other two stand out to me - same as they were between 3.18 and 3.19-rc1
HID: i2c-hid: prevent buffer overflow in early IRQ
HID: i2c-hid: fix race condition reading reports