[04:42] hi, my system hangs on reboot (but not on shutdown) and i need to plug off/plug back the power to make it respond - what's the best way to debug the kernel - find out exactly where the reboot code is? [07:52] teward, yep thermald is one of ours ... [07:53] memeka (N,BFTL), there are a number of ways to skin the reboot cat, and normally you would try them all to see which works and add a quirk to select that one === Guest37468 is now known as memguy === marga_ is now known as marga [15:16] apw: still around? (sorry i wasn't around at 03:52 local) [15:17] apw: or kernel team, before I poke hggdh or the quality list admins to silence something that should probably be squished, https://lists.ubuntu.com/archives/ubuntu-quality/2016-July/006585.html may be of interest, regarding why something was fix released for wily but didn't fix things (and possibly didn't fix for Trusty) [15:18] wrt bug #1543046 [15:18] bug 1543046 in thermald (Ubuntu Wily) "thermald spamming kernel log when updating powercap RAPL powerlimit" [High,Fix released] https://launchpad.net/bugs/1543046 [15:19] cking, ^ this is a thermald thing that is marked fixed but seemingly not so [15:19] apw: no confirmation of still existing for Trusty [15:19] and i need guidance for the Wily side [15:19] i.e. "Would it be fixed before EOL and would it do any good to change the bug status for wily" [15:19] asking as bugcontrol not QA :P [15:20] s/bugcontrol/bug triage/ [15:20] apw, ok, I'll look at it on monday, although I'm surprised by this :-/ [15:22] cking: without taking a look at it, can you give me a best guess as to whether this close to Wily EOL we actually care about getting this fixed before it EOLs? [15:22] I can understand it needs poked for Trusty if it still exists, I don't see justification for Wily which dies off in 20 days [15:22] (as a bug triager, not a kernel guy) [15:22] cking, plus we're aren't gonna updatethe kernel anymore [15:23] teward, well, I know the code well, so it's trivial for me to eyeball and I can turn it around on monday quite easily as long as nothing higher priority hits me over the weekend [15:23] ack [15:23] when is wily EOL now? [15:23] 28th [15:23] message went out from infinity yesterday [15:23] over the announce lists [15:24] ok, I'll see what I can to monday, I was pretty sure I tested this on my x220, but oh well, I screwed it up I guess [15:24] cking: i'll reply saying it's in the Kernel Team's hands now, and to stop the bickering on the QA list [15:24] is there a kernel ML you want me to CC on with that reply? [15:25] teward, I'd prefer for me to just update the bug report [15:25] ack [15:25] cking: i'll leave it be and say it's back in the Kernel team's hands, and to leave it be until such time one of the team's members reply to the bug. [15:25] it's still needing an anti-drama squish. [15:25] (on the quality ml) [15:27] it's not going to kill anyone, it's been like tyhat for a while without much drama [15:27] indeed. there's drama between two people on the ML [15:27] they need more beer [15:27] and *that* needs squished (it's no longer just a report of 'marked fixed but not fixed') [15:27] they need to upgrade to xenial [15:27] +1 rtg [15:32] rtg: that's what i said in my reply to the thread heh [15:32] but, alas, end users will be end users, so... :: [15:32] :P * [15:47] teward: OTOH, php4fan has just earned moderation on the ML. [15:47] hggdh: oh joy [15:47] I still think php4fan and Teo Teo to be one and the same [15:47] hggdh: this wouldn't be the same guy from before would it? (I recently pruned all my mailing list messages from my main inbox, CBA to pull up the archive) [15:48] ahh that's the one I was thinking about [15:48] hggdh: funny story, I was going to ping you on it privately, too, and ask for some higher power to be called forth, but lunch was calling first :P [15:48] thanks for the FYI [15:49] yw. Pity, though. This person uses Wily for his "production", and still does not understand the difference between LTS and interim [15:50] hggdh: hey, that's 50% of the Ask Ubuntu people, it's why I started posting the EOL notices. [15:50] so people aren't all "WHY THE [censored] DID MY POST GET CLOSED WHAT IS EOL WHAT IS THIS ..." [15:50] *rolls eyes* [15:51] good idea. [16:08] teward, I've prepared a fix, I'll get the user to test it from a PPA and upload it once they verify it works [16:09] cking: ack [18:59] curious does anybody know what db000000-db7fffff : RAM buffer i have tried to read from it and i cann't do that i just curious on what it is used for some kind of buffer cache or something but don't understand it (how it is used,why , and what is using it) [19:03] memguy: If a region of RAM doesn't end on a 64MB boundary and there's nothing else allocated there, the kernel reserves the space to reduce the probability that there's actual RAM there being used by the firmware [19:03] Otherwise you might map an mmio device on top of it [19:06] wait so what happens if the region ends on 64MB boundry [19:06] i guess i don't see the point of it and why they named if ram buffer [20:24] curious is there a cpu feature or flag that has something to do with cpu temperature because i have seen /dev/temperature or other devices and read into it a little bit. Can processors detect there temperature there running at like they can with voltage and frequency settings thru power management [20:26] i am curious if there is a /proc/cpuinfo flag name for this which would control the setting range of what the cpu temperature range it will run at before halting to resume that range . would be a cool feature to beable to turn off and on [20:27] in conjunction with p-state and t-state and c-state [20:39] I guess alot of this can be obtained from ACPI but was curious on if there is a flag and dedicated cpu feature for all this processor temperature,freq, cpu voltage/current [20:39] spped