| === himcesjf_ is now known as him-cesjf | ||
| tjaalton | lotuspsychje: i was wrong, the commit was in 4.19 already | 08:32 |
|---|---|---|
| tjaalton | maybe try blacklisting the module and try 5.3rc, it should flicker again | 08:33 |
| tjaalton | I don't think the bug in i915 which causes the flicker has been fixed yet | 08:46 |
| lotuspsychje | tjaalton: but the module was my eth card, would that still be valid then? | 08:54 |
| lotuspsychje | my wifi is that iwlwifi | 08:55 |
| lotuspsychje | tjaalton: whats weird, that thread i found was mentioning same intel wifi, but the commit is about r8169 | 08:56 |
| tjaalton | lotuspsychje: it's loaded, and the commit means that it's no longer blocking the cpu/gpu to enter lower power state | 09:05 |
| tjaalton | which then triggers the bug in i915 | 09:05 |
| tjaalton | it all makes sense | 09:05 |
| tjaalton | just blacklist r8169 (or unload it) and test on 5.3rc | 09:05 |
| lotuspsychje | allrighty | 09:05 |
| lotuspsychje | but 5.3 was not flickering right | 09:06 |
| lotuspsychje | only 5.0 flickering | 09:07 |
| tjaalton | because it had another commit for r8169 | 09:07 |
| lotuspsychje | ah | 09:07 |
| tjaalton | 62b1b3b3b6d3ef3 r8169: don't activate ASPM in chip if OS can't control ASPM | 09:08 |
| tjaalton | which I believe kinda reverts the older commit | 09:08 |
| lotuspsychje | ok, blacklist added, lets reboot | 09:08 |
| tjaalton | in the sense that it would no longer use lower cstates | 09:08 |
| lotuspsychje | tjaalton: you need my dmesg now with the blacklist? | 09:12 |
| tjaalton | no | 09:12 |
| tjaalton | does it flicker? | 09:12 |
| lotuspsychje | 5.3 was not flickering | 09:12 |
| tjaalton | even after blacklist? | 09:12 |
| lotuspsychje | yep | 09:12 |
| tjaalton | okay | 09:12 |
| lotuspsychje | oh wait | 09:12 |
| lotuspsychje | i forgot to delete cstate 4 | 09:13 |
| lotuspsychje | my bad | 09:13 |
| tjaalton | heh | 09:13 |
| tjaalton | also fastboot=0 | 09:13 |
| lotuspsychje | ok | 09:13 |
| tjaalton | or suspend/resume | 09:13 |
| lotuspsychje | ok here goes | 09:14 |
| lotuspsychje | hmm wifi enables anyway after a while | 09:17 |
| lotuspsychje | no flickering | 09:17 |
| lotuspsychje | r8169 0000:01:00.1: can't disable ASPM; OS doesn't have ASPM control | 09:18 |
| tjaalton | so it's loaded anyway? | 09:20 |
| tjaalton | try rmmod r8169 | 09:20 |
| lotuspsychje | tjaalton: http://dpaste.com/2JBCR5F | 09:20 |
| lotuspsychje | rmmod: ERROR: could not remove module r8169: Operation not permitted | 09:21 |
| tjaalton | how about sudo -s first.. | 09:21 |
| lotuspsychje | reboot again? | 09:22 |
| tjaalton | what? | 09:23 |
| tjaalton | how did you blacklist it? | 09:23 |
| tjaalton | 'sudo rmmod r8169' | 09:23 |
| lotuspsychje | added to /etc/modprobe.d/blacklist | 09:23 |
| tjaalton | does it work? | 09:23 |
| lotuspsychje | rmmod: ERROR: Module r8169 is not currently loaded | 09:24 |
| tjaalton | cool, does it flicker after suspend/resume | 09:24 |
| lotuspsychje | lets try | 09:24 |
| lotuspsychje | no, Fn keys brightness also work | 09:25 |
| tjaalton | what's that got do to with this? :) | 09:26 |
| lotuspsychje | tjaalton: well the Fn keys have influence on the flickering | 09:26 |
| lotuspsychje | making it flicker more | 09:26 |
| lotuspsychje | so im alwyas testing too | 09:26 |
| lotuspsychje | ok whats next :p | 09:27 |
| tjaalton | sudo cat /sys/kernel/debug/dri/0/i915_dmc_info | 09:27 |
| lotuspsychje | http://dpaste.com/16GYRN8 | 09:28 |
| tjaalton | sounds like some other device is now blocking lower power state | 09:28 |
| tjaalton | if r8169 is not loaded | 09:29 |
| tjaalton | fun | 09:29 |
| lotuspsychje | yikes | 09:29 |
| tjaalton | anyway, we should get 62b1b3b3b6d3ef3 in 5.0 | 09:29 |
| lotuspsychje | tjaalton: i dont need to test this blacklist on 5.0? | 09:30 |
| tjaalton | it wouldn't have any effect | 09:30 |
| lotuspsychje | kk | 09:30 |
| tjaalton | thing is though, that it's kinda hard to debug the actual bug in i915 because their code is now based on 5.3 where the bug doesn't happen | 09:31 |
| tjaalton | isn't triggered I mean | 09:31 |
| lotuspsychje | ah | 09:31 |
| lotuspsychje | tjaalton: if it can help, these are the kernels we all tested: http://dpaste.com/2T98DVQ | 09:34 |
| lotuspsychje | 4.15 4.18 5.2 and 5.3 were not flickering | 09:36 |
| tjaalton | 5.2? | 09:42 |
| tjaalton | surely did flicker | 09:42 |
| lotuspsychje | tested 19.10 without flickering i think | 09:44 |
| lotuspsychje | live daily | 09:44 |
| lotuspsychje | tjaalton: i can test some of my list if you want | 09:49 |
| EoflaOE | hello | 09:52 |
| lotuspsychje | hi EoflaOE | 09:53 |
| EoflaOE | hi lotuspsychje | 09:53 |
| lotuspsychje | brb | 09:55 |
| === lotus|i5 is now known as lotuspsychje | ||
| === himcesjf_ is now known as him-cesjf | ||
| tjaalton | lotuspsychje: no need to test anything, since I know what's going on | 13:50 |
| tjaalton | lotuspsychje: 5.2 has this: b75bb8a5b755d0c r8169: disable ASPM again | 14:04 |
| tjaalton | that's why it doesn't flicker | 14:05 |
| tjaalton | also, it explains why my builds with smaller config didn't flicker | 14:05 |
| lotuspsychje | tjaalton: allright, thank you for all your work, time & effort in this bug | 14:57 |
| shibboleth | current 5.0.0 -20 until -28 are all messing with the tor browser bundle | 21:56 |
| shibboleth | is this known, has anyone weighed in? | 21:57 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!