/srv/irclogs.ubuntu.com/2015/09/08/#ubuntu-kernel.txt

=== amitk is now known as amitk-afk
Tehdastehdasapw, I didn't get the part about the machine not being representative of its kind, as many machines in the original slow fan bug report comments are claimed to run their fans faster and CPUs cooler in the fan control disengaged mode. I haven't tried tweaking thermald, as reading this https://wiki.ubuntu.com/Kernel/PowerManagement/ThermalIssues , my thermal-conf.xml and its manual page I can't understand how to redefine fan 06:50
Tehdastehdasspeeds so that 'disengaged' mode would be the new highest speed.06:50
Tehdastehdas"Currently, the Linux kernel thermal ACPI module implements these controls. So, based on the validity of configuration data, this can be a very efficient method for thermal controls. But, it was observed that many systems don’t have this configuration data or have invalid data, preventing the kernel module from taking timely action." https://01.org/linux-thermal-daemon/documentation/introduction-thermal-daemon07:07
Tehdastehdas Which channel should I go to for thermald support?07:17
rbasakIs smb on holiday? Any idea when he's back?09:36
apwrbasak, yes, and err ...10:19
apwrbasak, is this about dpdk, if so arges may be in the loop10:19
TehdastehdasI wrote about the Lenovo slow fan bug to the thermal_daemon (thermald) mailing list.10:30
rbasakapw: yeah, dpdk. Thanks. I wanted to clarify some bits about upstream's build system that smb would know, but I can look or wait until next week.10:40
apwTehdastehdas, sound like a plan10:40
apwrbasak, arges was involved in deep review so if you have queries, do ask 10:41
jpdsapw: You seen https://askubuntu.com/questions/670106/igb-detected-tx-unit-hang ?11:35
apwjpds, nope, kamal henrix a nice regression in stable for you ...11:37
henrixapw: looking12:19
henrixoh joy12:21
henrixjpds: are you able to reproduce this igb bug?12:54
jpdshenrix: Nope, I saw some people in #ubuntu-server complaining about it12:56
henrixjpds: ah, thanks.  i'll try to get a test kernel built (still looking at the bug).  i'll just add a link to that kernel in the bug (bug #1492146)12:58
ubot5bug 1492146 in linux-lts-utopic (Ubuntu) "igb Detected Tx Unit Hang" [Undecided,Confirmed] https://launchpad.net/bugs/149214612:58
jpdshenrix: Asked the person to join here12:59
henrixjpds: cook, thanks12:59
bananapieIs there a page somewhere that lists the differences between Ubuntu's kernel and vanilla kernel?13:02
rozieI was hit by kernel bug http://askubuntu.com/questions/670106/igb-detected-tx-unit-hang can I expect it to be fixed in next kernel release?13:05
rozieright now I downgraded to 3.16.0-46-generic (Ubuntu 14.04 LTS). have spare machine for tests.13:06
henrixrozie: i'm looking at that bug (bug #1492146), and i'll try to have a test kernel built in a bit13:07
ubot5bug 1492146 in linux-lts-utopic (Ubuntu) "igb Detected Tx Unit Hang" [Undecided,Confirmed] https://launchpad.net/bugs/149214613:07
henrixrozie: would you be able to test it, to see if it actually fixes the issue?13:07
roziehenrix: which solution exactly?13:11
henrixrozie: looks like a bad backport in one of the patches in the 3.16.0-48.64 kernel13:12
henrixrozie: there were a bunch of hyper-v related patches in this kernel; the test kernel will simply revert them, as i suspect that one of these patches is incorrect13:13
henrix(incorrect = bad backport)13:13
henrixrozie: i've uploaded a test kernel here: http://people.canonical.com/~henrix/lp1492146/v1/amd64/13:26
henrixrozie: i've also included in that URL the patches i'm reverting.  i believe the 'bad' one is the first one, so i had to revert them all :-/13:26
henrixrozie: if you could give it a spin would be great13:27
henrixrozie: i'll also add this URL (and request for testing) in the bug13:27
rozieOK, installing http://people.canonical.com/~henrix/lp1492146/v1/amd64/linux-image-3.16.0-48-generic_3.16.0-48.64~14.04.1~lp1492146v1_amd64.deb and http://people.canonical.com/~henrix/lp1492146/v1/amd64/linux-image-extra-3.16.0-48-generic_3.16.0-48.64~14.04.1~lp1492146v1_amd64.deb right now13:29
henrixrozie: awesome, thanks!13:30
roziebooting... I have about 1 hour left, so it would be great if we manage to fix/test it in this time13:36
roziehenrix: booted. looks stable13:37
henrixrozie: awesome, thanks.  if you're not able to reproduce the issue with this kernel, then i guess you're done for now ;)13:40
henrixrozie: we'll eventually respin this kernel again (probably today), and i'll eventually ask in the bug for people to re-test again before releasing13:40
henrix(2 'eventually' in the same sentence...)13:41
rozieI'll be probably available tomorrow around 9AM UTC13:41
roziefeel free to give specific version to test. the good thing is I have spare machine and independent access ;-)13:43
rozieif you need anything, I'm available for 45 min more today13:43
henrixrozie: awesome, thanks.  i'll ping you if i have a final version ready tomorrow13:45
rozie:-)13:58
jpdsrozie: Do you have an askubuntu account to update the page?14:27
roziejpds: I have lauhchpad, but noscript blocks CSS for askubuntu. works fine for ask.openstack14:29
jpdsHmm14:30
rozieI know, it's another channel thing ;)14:31
rozieused another browser14:33
roziejpds: can you tak a look? any other info needed?14:33
jpdsrozie: I think henrix has an eye on the ball14:34
jsalisbury**15:21
jsalisbury** Ubuntu Kernel Team Meeting - Today @ 17:00 UTC - #ubuntu-meeting15:21
jsalisbury**15:21
=== dgadomski_ is now known as dgadomski
willcookehi mjg59 - I was reading this the other day:  http://mjg59.dreamwidth.org/34868.html  -  did your patches get in to the kernel?16:12
mjg59willcooke: Still working on reverse engineering the Intel driver so I can figure out the blacklisting16:45
jsalisbury##16:55
jsalisbury## Kernel team meeting in 5 minutes16:55
jsalisbury##16:55
cristian_cjsalisbury: hi16:57
jsalisburycristian_c, hi, I never got a response from upstream.  I'll ping them again and cc the bug16:59
cristian_cjsalisbury: ok16:59
=== henrix_ is now known as henrix
=== jsalisbury changed the topic of #ubuntu-kernel to: Home: https://wiki.ubuntu.com/Kernel/ || Ubuntu Kernel Team Meeting - Tues Sep 15th, 2015 - 17:00 UTC || If you have a question just ask, and do wait around for an answer! If the question is should I file a bug for something, likely you can assume yes. || Channel logs: http://irclogs.ubuntu.com/
rtghenrix, kamal: ad1ed2a9dd4c435d6a3ce470211db9a8d107c3e0 should be added to the 3.19 stable kernel17:11
henrixrtg: wow! that patch has enough context to see the bug :)17:12
rtghenrix, yeah, it seems like a no brainer17:13
kamalrtg, henrix: jesus you're not kidding!  ack, I'll pick it up17:14
kamalrtg, do we know when it got broken?17:14
rtgkamal, the driver was added in 3.19, the locking fix came in 4.017:15
kamalrtg, good.  thanks.17:15
psivaacking: hello,17:18
psivaaNot sure if you're still interested in health-check results in http://ci.ubuntu.com/smokeng/trusty/desktop/i386/20150908/13806/health-check/17:18
ckingpsivaa, i'll just have a look...17:18
ckingpsivaa, \o/, excellent!17:19
psivaacking: There were a couple of failures in the last couple of days and since we moved the hosts the VM installation takes place, we're wondering if the failures have anything to do with the VM host migration17:19
psivaacking: one of such failures is https://jenkins.qa.ubuntu.com/view/Trusty/view/Smoke%20Testing/job/trusty-desktop-amd64-smoke-health-check/321/artifact/utah-810-trusty-amd64_master.run_2015-09-07_12-09-29.yaml/*view*/17:20
ckingpsivaa, are the failures still occurring?17:20
psivaacking: they appear to be 'flaky'. i.e a rerun passes17:20
ckinghrm, yep, the failure on the URL shown above is probably a sporadic memory allocation that skewed the rates17:21
psivaathe failed ones on https://jenkins.qa.ubuntu.com/view/Trusty/view/Smoke%20Testing/job/trusty-desktop-amd64-smoke-health-check/ have all the same test failure, but as i said they pass on reruns17:22
ckingi'll eyeball those in a while, I've got some food waiting for me to be eaten..17:23
psivaacking: sure, we'll be happy to leave that to see if that settles down. Please feel free to ping us back if you think that the host migration being any reason17:23
ckingpsivaa, let's see if it settles down, if not, then lets dig into it deeper17:40
psivaacking: sounds good17:41
=== bjf_ is now known as bjf
=== brendand_ is now known as brendand

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