/srv/irclogs.ubuntu.com/2015/01/20/#ubuntu-kernel.txt

rsalvetiapw: mind taking care of https://bugs.launchpad.net/ubuntu/+source/linux-manta/+bug/1412543 ?00:40
ubot5Launchpad bug 1412543 in Canonical System Image "udev bridge fails to get events from kernel (missing FHANDLE)" [High,Confirmed]00:40
=== gerald is now known as Guest3853
apwrsalveti, see it09:20
=== morgan is now known as yossarianuk
yossarianukchris112: you can use the 3.18.x kernels from mainline in 14.10 09:23
yossarianukthe kernels in mainline ppa use the version they are targeted for - however just because 3.18 doesn't have 'utopic' in the version names does't mean they don't work in utopic ...09:25
=== hugbot is now known as swordsmanz
chris112yossarianuk, thx for the info. is it save to use the btrfs tools of utopic?11:13
yossarianukchris112: that I am not 100% sure of.11:19
yossarianuk(not used btrfs in ubuntu yet at all - only opensuse / neptuneos)11:20
rsalvetiapw: thanks12:11
apwrsalveti, i am assuming the normal plan and uploading them to the CKT PPA12:11
rsalvetiapw: yeah, just ping me once you get the packages in there12:11
rsalvetiI'll validate and copy them around12:11
apwrsalveti, will do, mako is building, working on the otehrs now12:12
rsalvetigreat, thanks a lot12:12
=== spideyman is now known as Guest32025
apwrsalveti, ok it is all uploaded and building ... should be done in about an hour12:57
Odd_BlokeI'm running the kernel tests in an Azure instance and have got to: https://pastebin.canonical.com/123777/13:09
Odd_BlokeNothing has happened in almost 20 minutes.13:09
Odd_BlokeIs this a slow test, or has something broken?13:09
apwOdd_Bloke, is that the ASLR test, i think it has to try several thousand times to check the distribution is random13:13
apwOdd_Bloke, i cannot however say that i have run those recently to have a feel for how long13:13
smbYeah that test runs ages13:17
smbages being something of 40min+ depending on hw 13:23
rsalvetiapw: thanks13:28
thellHello. After a year of having hardware that seemed to enjoy crashing (almost daily) I now have a stable (for a week) non crashing core i7 4700MQ with i915 video driver while running Utopic with 3.19rc4! Woohoo!15:00
thellMy question is: What should I be monitoring for backporting of changes (I presume it was something in the drm-intel-next in Dec) to get back inline with Utopic kernels?15:00
Odd_Blokeapw: smb: Thanks for the info.15:33
jsalisbury##15:36
jsalisbury## Kernel team meeting today @ 17:00 UTC15:36
jsalisbury##15:36
trippehthell: there was just a bunch of intel gfx fixes that went into the upstream stable trees (not released yet)15:37
* thell cheers!15:38
thelltrippeh: I assume I should watch the changes file in the utopic kernel releases. Do you have a link of where you saw this so I can have an idea of what to watch for?15:39
dsmythiesI'll ask my questions after a few lines, they are related to (are exactly):16:28
bjfcmagina, can you verify LP: #1404335 ?16:28
ubot5Launchpad bug 1404335 in linux (Ubuntu) "xgene: BUG: soft lockup - CPU#0 stuck for 23s! [halt:2059] on poweroff" [Medium,Confirmed] https://launchpad.net/bugs/140433516:28
dsmythieshttps://bugs.debian.org/cgi-bin/bugreport.cgi?bug=76571716:28
ubot5Debian bug 765717 in src:linux "linux-image-3.16-2-amd64: High CPU load with linux-image-3.16-2-amd64" [Normal,Fixed]16:28
dsmythieshttps://lkml.org/lkml/2014/11/5/90516:28
dsmythiesThe patch was submitted on Nov 6th, which I assume was in time for the 3.19 merge window, but it still doesn't appear in 3.19RC5.16:29
dsmythiesI cannot find any other references for it, nor any "ACK".16:29
dsmythiesIs there any to determine the status of the patch? Or might it be in limbo?16:29
dsmythiesShould I enter a launchpad bug report to track the issue within the Ubuntu context?16:29
apwdsmythies, that sounds familiar16:32
dsmythiesapw, I was helping someone on Ubuntu forums with this issue. I saw you made a post on another thread there yesterday. I am now wondering how to follow up to ensure this get resolved.16:34
apwdsmythies, ok the one i thought it was, it wasn't :) ... so ... yes please lets file a bug against "linux", using "ubuntu-bug linux"16:37
dsmythiesO.K. thanks.16:37
jsalisbury##16:50
jsalisbury## Ubuntu Kernel Team Meeting - in 10 minutes - #ubuntu-meeting16:50
jsalisbury##16:50
jsalisbury##17:00
jsalisbury## Meeting starting now17:00
jsalisbury##17:00
=== jsalisbury changed the topic of #ubuntu-kernel to: Home: https://wiki.ubuntu.com/Kernel/ || Ubuntu Kernel Team Meeting - Tues January 27th, 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.
Odd_BlokeI'm beginning to think we may need to skip that stack collision test on (at least) Azure; about to hit the three hour mark. >.<17:42
apwOdd_Bloke, you may be able to change the iteration count on that one, though it is likely hard coded17:44
Odd_Blokeapw: It is hard-coded, regrettably.17:46
apwOdd_Bloke, well "patch" can fix it then17:46
apwif [ on hypervisor ]; then patch -p1 hyperv.patch17:47
Odd_BlokeAh, good point.17:47
apwOdd_Bloke, it would be good to let one finish to find out how how long a "bazillion" iterations take, so you have a framework to work out a good "finish in 10m" number :)17:48
Odd_BlokeWill see how it does on GCE (currently running the full qa suite there) to decide how to go about it.17:48
Odd_BlokeYeah, will definitely leave it going in to the evening.17:48
apwOdd_Bloke, though ... it would be a lot more sensible if the iterations stuff did somethign saner, liek "run for 5m" 17:50
apwOdd_Bloke, and it would maek a lot of sense to tell #security that this is out of control slow, and get a recommendation17:50
apwOdd_Bloke, they may say ... if it isn't at least 10k iters its not worth doing sort of thing17:51
Odd_BlokeYeah, good idea.17:52
Odd_BlokeI'll probably also look at splitting it out of the main run (in a downstream semi-hacky sort of a way) so it can get its own instance to run on.17:53
Odd_BlokeThat'll let us run it in parallel with the other tests, so it taking X minutes will be slightly less painful.17:54
apwOdd_Bloke, a good plan, if you come up with a way to run the tests as groups or whatever "--not-aslr" "--not-all --aslr" or whatever, we should feed that back to the master17:55
Odd_BlokeSounds like a problem for Tomorrodd_Bloke.18:01
apwOdd_Bloke, :) i know that man18:02
soeehi, gusy when 3.18.3 will make its way into Vivid ?19:45
=== pgraner is now known as pgraner-afk
apwsoee, after the freeze for A221:45
soeeapw: thank you22:16
* RAOF looks for a target to poor bees into.22:56
=== SturmFlut is now known as SturmFlut|AFK

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