/srv/irclogs.ubuntu.com/2020/02/11/#ubuntu-kernel.txt

ryuoI submitted a Ubuntu bug for a rather simple issue and haven't heard anything yet. Any ideas when someone will respond? https://bugs.launchpad.net/ubuntu/+source/linux/+bug/186249806:29
ubot5Ubuntu bug 1862498 in linux (Ubuntu) "Nuvision NES11 needs silead touchscreen quirks" [Undecided,Confirmed]06:29
=== cpaelzer__ is now known as cpaelzer
tjaaltonryuo: you should send the patch upstream06:52
ryuotjaalton: normally i would but i've been blown off before. last time i got more results by using an indirect channel.06:53
tjaaltonso you're kinda asking others to do the work?06:58
ryuoto an extent, i guess. i already did a lot of the work devising my patch.07:01
tjaaltonyeah but it would have to go upstream07:01
ryuoi know, but i'm a nobody. i would likely just get ignored like i have before.07:02
ryuosigh.07:02
tjaaltonso you've sent the patch to linux-input@vger.kernel.org?07:18
ryuotjaalton: not this time  but last time i had a patch07:34
ryuotjaalton: sent.07:53
tjaaltongood07:55
ryuothough i expect to be summarily ignored like before.07:55
tjaaltonproperly git formatted?07:55
ryuoshould be. i used git send-email07:56
tjaaltonok07:56
apwryuo: add that info a link to the upstream submission to the bug08:14
apwmakes it easier to find08:15
=== cpaelzer__ is now known as cpaelzer
FragginRighti seem to be missing the dvb kernel headers on my 16.04 machine. how might i get them installed? i've been searching for a while now13:59
FragginRightmy google fu seems to be failing me :)14:00
cezary_zukowskiDoes the newest (Out-of-memory) OOM killer supports cgroups?15:10
cezary_zukowskiHi :)15:11
apwi thought that oom was related to memory cgroups when in use; but one should really test it15:26
cezary_zukowskiOkay, thanks.16:19
nerdykidHi!  I need to have dkms copy a firmware file along with the compiled kernel module automatically.  My /usr/src/tn40xx-003/dkms.conf: https://pastebin.com/1VvuWYNf    I need dkms to copy /usr/src/tn40xx-003/x3310fw_0_3_4_0_9445.hdr to the same directory as the compiled .ko module.  Anyone know how to do this?18:18
=== ben_r_ is now known as ben_r
apwnerdykid (N,BFTL), if the dkms package is packaged up in a .deb you do it in that .deb context.  here is an example worked though in our wiki https://wiki.ubuntu.com/kengyu/dh_dkms20:54
chilukanyone else having issues with screen brightness on the 5.4 kernel+focal?21:46
apwchiluk, not me21:47
chilukapw intel graphics?21:47
apwchiluk, yep21:47
sforsheeme neither, and yes intel graphics21:47
chilukI'm completely unclear what software stack is involved in making that happen.21:47
sforsheeI don't think it's consistent, depends on the model21:48
chilukit was working afair until moving to the 5.4... that being said a bunch of other things probably changed at the same time as well.21:48
chilukalso good to see you guys are still kicking.21:49
sforsheechiluk: look at /sys/class/backlight, should point you to your driver I think21:49
sforsheenot dead yet ;-)21:49
chilukyep intel_backlight21:50
sforsheemine too21:51
tyhickschiluk, sforshee: I'm having screen brightness issues - reported in bug #186152121:51
ubot5bug 1861521 in linux-signed-5.4 (Ubuntu) "[FOCAL][REGRESSION] HP EliteBook 840 G5 screen brightness cannot be controlled" [Medium,Confirmed] https://launchpad.net/bugs/186152121:51
tyhicksI'm hoping to spend some time on that bug in the next couple days21:51
tyhicksintel_backlight for me, too21:51
chilukhey hey .. another old name..21:51
tyhickshey chiluk :)21:51
chilukalthough I'm ona dell over here.21:52
tyhickschiluk: any chance you have a screen with a built-in privacy filter?21:53
tyhicksthe hp_wmi warnings I pasted into the bug are likely not related so we still could be seeing the same issue21:53
chilukI do not but it is a touch screen.21:53
sforsheeI have a dell and a lenovo which are both working with intel_backlight21:53
chilukI'm on a inspiron 5540 which is a i9-9880H generation.21:54
chilukcould be a generational thing.21:54
chiluksforshee I'm calling your shit old.21:54
chiluk;)21:54
chiluktyhicks how new is that?21:55
tyhicks$ glxinfo | grep Device Device: Mesa DRI Intel(R) UHD Graphics 620 (Kabylake GT2)  (0x5917)21:55
tyhicksbah21:55
tyhicksbad paste21:55
sforsheemy dell is old, xps 13 with an i5-5200U21:55
sforsheebut my lenovo is brand spanking new, i7-10510U21:55
tyhickschiluk: glxinfo shows "Device: Mesa DRI Intel(R) UHD Graphics 620 (Kabylake GT2)  (0x5917)"21:55
chilukt$ glxinfo | grep Device21:56
chiluk    Device: Mesa DRI Intel(R) UHD Graphics 630 (Coffeelake 3x8 GT2)  (0x3e9b)21:56
tyhicksso I'm gen9 according to https://en.wikipedia.org/wiki/List_of_Intel_graphics_processing_units#Gen921:56
sforsheeDevice: Mesa DRI Intel(R) UHD Graphics (Comet Lake 3x8 GT2)  (0x9b41)21:57
tyhickssame gen9 for chiluk 21:57
sforsheeso maybe a gen 9 thing, I've got gen 1021:57
tyhicksI've got another gen9 I can test with, too21:57
chilukI'm going to quick check that the 5.3. kernel works 21:58
chilukYep 5.3 works.  Looks like a 5.4 regression.22:04
tyhicksmy other gen9 works fine under 5.4.0-12-generic22:06
tyhicksDevice: Mesa DRI Intel(R) HD Graphics 515 (Skylake GT2)  (0x191e)22:06
tyhicksit is also an HP22:06
chiluknope ... that's a skylake carry-over gpu it looks like.22:06
chilukprobably gen 7 or 8 gpu..22:07
tyhicksskylake is gen9 gpu22:07
tyhicksthe CPU is m5-6Y5422:08
tyhicksit is in that Gen9 table on wikipedia and there are a lot of references out there that say skylakes are the first gen9 gpu22:09
chiluknope shares core bits with hd 53022:09
chilukcheck code name column on wikipedia.22:10
chilukit's a different sku than the hd 6xx we have22:10
tyhicksI'm not arguing that22:10
tyhicksI'm arguing that it is still a gen922:11
chilukI'm saying that it's older ... 22:11
tyhicksI'm actively working on another i915 bug, using that laptop, and am 100% sure that changes I make to gen9_init_indirectctx_bb() have an effect22:12
chilukI bet sforshee 's 10510u has a newer gpu than either of us.22:12
tyhicksyou're going to have to say something other than "nope" to convince me that it isn't a gen9 gpu :)22:12
chilukwell you know more than me at this point.. 22:12
sforsheeyeah I guess it's actually a gen 1122:13
chilukI  just started looking at this ..22:13
tyhickswell intel's mapping from model numbers to generations is confusing so I would take your word if I haven't been screwing with this other bug all day22:14
tjaaltonskl, kbl, cfl, cml are all gen922:15
tjaaltongpu22:15
tjaaltonicl is gen1122:15
tjaaltongen10 (cnl, cannon lake) never really took off22:15
chilukyeah ... you can't map based on cpu model number or even age..22:16
tjaaltoncml and icl both have cpu models named after 10xxx22:17
tjaaltonwhich is even more confusing22:17
chiluksforshee should 1861521 be against linux-signed or linux-generic?  seems like linux-signed would only be used for secure boot issues.22:21
sforsheechiluk: yes not signed, the source package will be linux-5.422:22
tyhickssforshee: that's the source package that was ubuntu-bug picked for me22:32
sforsheetyhicks: good deal, thanks for letting me know22:36
tyhicksnow that I think about it, I think I saw a bug report for that22:38
tyhicksno, it was related but different - bug #186144622:39
ubot5bug 1861446 in apport (Ubuntu Focal) "on focal 'ubuntu-bug linux' doesn't automatically collect kernel artifacts" [High,In progress] https://launchpad.net/bugs/186144622:39
sforsheetyhicks: huh, I wonder what mechanism is deciding that 'ubuntu-bug linux' should map to linux-signed-5.422:41
tyhickssforshee: I'm not sure - I was surprised that it mapped to anything *-5.4 so I figured it was intentional and correct22:42
apwsforshee, i think it is the other way, it is using uname -r to find the linux-image-<foo> package and mapping that to linux-signed-5.4 via apt-cache22:43
sforsheeapw: ok, that sounds believable22:44
tyhicksso that means that https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bugs?field.status:list=NEW is receiving reports but perhaps not being monitored22:45
tyhickssome others in https://bugs.launchpad.net/ubuntu/+source/linux-signed-5.4/+bugs?field.status:list=NEW as well22:46
apwsforshee, somewhere we have a bot which moves things to linux etc22:46
aberranthi all22:47
aberrantcan someone please give me some guidance around clock sources? I'm seeing extremely high drift with my eoan setup, clocksource is tsc. What recommendations do you all have?22:47
aberrantmy options are tsc hpet acpi_pm 22:50
apwhmm, not sure i've seen anything like that; have you tried switching to hpet 22:51
aberrantI haven't yet22:54
aberrantmy drift according to chrony is over 830 ppm22:54
aberrantthat seems... really high.22:55
aberrantit's causing ntpd to fail, since the max drift is 500ppm22:55
apwtsc drift is often seen when an older kernel is run on very new kit which has new c-states for instance22:55
aberranthpet is giving me 6ppm22:57
aberrantI'm not running an old kernel, though22:57
aberrantI'm running a custom one based on 5.0.x22:57
aberranton an AMD 3400G22:57
aberrantbut yeah, my guess is it's idle or c-states that's causing the tsc problem. Even though hpet is less efficient, I'll switch to using it.22:58
aberrantok, rebooting to check if this works. Thanks.23:02
chilukaberrant not sure if this is related..https://www.tomshardware.com/reviews/amd-ryzen-clock-bug-benchmark-scores,6312.html23:03
chiluklooks like ryzen had some clock bugs in general.23:04
aberrantperhaps, but I'm not OCing23:05
aberrantbrb though - rebooting to make sure hpet is now default23:05
aberrant_ok, that worked23:10
=== aberrant_ is now known as aberrant
aberranthpet is the better option for keeping drift low.23:11
aberrantnot sure whether the tsc drift is report-worthy, but I wouldn't even know what to put in the report.23:23

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!