03:24 <si1v3r> I am recompiling all the defconfig i2c kernel drivers as modules. I wonder if reloading any of them would help.

03:40 <si1v3r> Interesting. I rmmod'd i2v_exynos5 fine, then got a segmentation fault when I reloaded it. Now when attempting to rmmod it again, it says that the module is in use.

03:40 <si1v3r> mounse and keyboard are dead, am using usb now.

03:41 <si1v3r> I was able to remove and readd i2c_dev, and i2c_cros_ec_tunnel with no issue.

03:41 <si1v3r> but those ones did not affect my mouse and keyboard, so I don't think they are where the problem is.

03:42 <si1v3r> lsusb says that i2c_exynos5 is in use by -1

03:44 <si1v3r> this is all on next-20150604

03:44 <si1v3r> peach pit (11")

12:12 <javier__> si1v3r: I don't think that is well tested since exynos_defconfig builts everything as built-in

12:12 <javier__> I found that many exynos drivers were not working when building as a module because module autoloading was broken

12:12 <javier__> all those fixes are in -next now but just as an example that building things as modules is not well tested

12:13 <javier__> si1v3r: I was busy with other non-exynos stuff but I'll take a look to S2R after lunch

12:13 <javier__> si1v3r: you said that keyboard and touchpad not working on resume happens with v4.1-rc6 and today's next right?

13:19 <javier__> si1v3r: I just tested and indeed no keyboard and touchpad after resume

13:20 <Wizzup> I can confirm it doesn't work with v4.1-rc6

13:20 <Wizzup> (no clue about today's next)

13:23 <javier__> for the trackpad

13:23 <javier__> [ 43.052301] atmel_mxt_ts 8-004b: Resetting chip

13:23 <javier__> [ 46.051284] atmel_mxt_ts 8-004b: Wait for completion timed out.

13:23 <javier__> and for the keyboard

13:23 <javier__> [ 42.739546] cros-ec-spi spi2.0: spi transfer failed: -108

13:23 <javier__> these are the errors

13:32 <steev> javier__: something along these lines https://chromium.googlesource.com/chromiumos/third_party/kernel/+/68783accbd8f58809b64f34204f21c5f3f018c99%5E%21/ maybe

13:36 <javier__> steev: I don't know tbh

13:36 <javier__> I'm installing i2c-tools now to see if I can talk with the chip after a resume

13:36 <steev> theres also a commit aout i2c not starting fast enough

13:37 <steev> on resume, but im too lazy to pull the tab back open

13:37 <javier__> yeah, I wonder if the problem is the atmel_mxt and cros-ec-spi drivers or the exynos i2c and spi controllers drivers

13:37 <steev> why not both?

13:38 <steev> ah, thats a joke based on a commercial

13:39 <steev> https://www.youtube.com/watch?v=vqgSO8_cRio

13:39 <javier__> steev: oh, I see. I didn't get it before :)

13:41 <steev> it's all the rage on the internet these days

13:43 <bgamari-> Anyone from Samsung around?

16:07 <si1v3r> javier__: let me know if I can get you any useful debug info.

16:27 <Wizzup> http://sprunge.us/bYBU

16:27 <Wizzup> Also getting that after (long) usage of wifi

16:29 <si1v3r> Haven't seen that myself after a few days uptime with wifi connected.

16:29 <Wizzup> try to watch a lot of youtubes or stream internet radio :)

16:29 <Wizzup> might also a be a different fw version

16:29 <Wizzup> anyway, bbl

16:30 <si1v3r> youtube does crap out after a few minutes. Maybe that's related.

16:46 <javier__> si1v3r: will do, thanks. Seems to be related with irq not being fired after a resume

16:47 <javier__> for both the cros-ec keyboard driver and the atmel mxt touchpad drivers

17:31 <Wizzup> si1v3r: took a few hours here

18:37 <javier__> si1v3r, Wizzup: I tested with 4.1-rc6, v4.0 and v3.19 (and in all the cases S2R broke the keyboard and touchpad irq triggering)

18:38 <javier__> so it seems that the issue always were present but I just didn't notice before

18:38 <javier__> will try to dig further on this tomorrow

18:43 <si1v3r> Thanks! Its nice to be able to at least use the machine now.

18:47 <si1v3r> A younger me would probably have hacked in a usb keyboard and mouse into the laptop case. haha