/srv/irclogs.ubuntu.com/2014/02/24/#ubuntu-kernel.txt

infinityapw: Diffing powerpc64-smp/powerpc and generic/ppc64el configs is an interesting read.00:05
infinityapw: I'd expect them to be nearly identical except for default CPU twiddles and maybe some PS3 crap.00:06
miseria"crimen legal es diabolico; crimen ilegal es satanico. ¿donde esta el terrorista?: hay uno, es inmortal y se llama tiempo" bienvenidos: http://castroruben.com *temo_a_un_ser_sin_rival*00:55
=== gerald is now known as Guest61019
=== mwhudson is now known as zz_mwhudson
ppisatimoin07:58
=== e11bits_ is now known as e11bits
apwinfinity, yep, the config is a mess, and we all know how much fun a review is08:49
* apw yawns the yawn of mondayness08:52
* infinity still needs the elusive sleep of Sunday nightness before he can get to Monday yawning.08:53
infinityzequence: lowlatency SRU ping.09:14
infinityBenC: ppc SRU ping.09:14
apwppisati, hey ... you boneblack config patches, could you look at repeating those for unstable ?10:27
ppisatiapw: i'll do10:27
ppisatiapw: done, let me do a test build and i'll send it10:48
zequenceinfinity: All kernels uploaded and waiting to build11:09
ppisati_apw: actually T/unstable FTBFS - http://paste.ubuntu.com/6986421/11:10
ppisati_apw: DRM_MSM11:11
apwppisati_, oh yeah so it does, you fixing that or i can put it on my list for later11:13
ppisati_apw: doing it, else i can't test my bbone config changes there11:13
apwppisati_, ack11:14
ppisatiapw: actually T/unstable FTBFS11:14
apwppisati, it build on x86 for me11:15
apwwell 45m ago it did11:15
apwppisati, ok i have just pushed a few pulled forward changes to unstable11:16
apwppisati, not sure they would affect you but do match what i build-tested on x86 successfully11:16
apw(pulled forward == a resync with changes falling into master-next)11:17
apw(pulled forward == a resync with changes falling into master-next)11:17
apwppisati_, did you see my msg about pshing ?11:18
ppisati_apw: failed building armhf11:18
ppisati_apw: just saw it, i'll rebase11:19
=== davmor2_ is now known as davmor2
apwppisati_, i expect it'll do that same, but worth a try indeed11:23
apwhenrix, i am futzing with some android cves to try and get them off of our non-android view11:24
apwhenrix, so prepare for carnage when the tooling loses its mind over what i added11:24
henrixapw: ack, thanks. i'm not doing any cve work this morning, so feel free to break everything :)11:25
ppisati_and another one...11:26
ppisati_http://paste.ubuntu.com/6986491/11:28
rick_hmorning all, I'm working on getting trusty working on an air and it worked once, but then updates killed it and reinstalls aren't helping. It dies in boot at "Booting SMP configuration" per https://www.dropbox.com/s/behviox991o01o1/2014-02-23%2016.15.15.jpg11:30
rick_hany ideas I can use to follow up/file a bug?11:30
ppisati_that's weird11:31
rick_hthat's a boot where I edited the grub stanza to not be quiet, noapic, and nomoseset (though it's intel graphics and all the stuff I see around nomodeset is nvidia/ati stuff)11:32
apwppisati_, isn't bad_udelay meant to be missing, and something like a range check failure11:32
ppisati_bah11:32
apwrick_h, sounds bad ... which air is it?  file a bug with working kernel you had, and mention the broken one, though i thought we had a bunch of airs working ok around here11:33
ppisati_at least bbone doesn't break anything11:33
rick_hapw: it's a 2013 11". More details here http://askubuntu.com/questions/425267/issue-booting-14-04-on-macbook-air11:33
rick_hapw: I can't get it to work again, even on the -8 kernerl. I thought the upgrade to the -11 was what killed it but I've reinstalled off the same usb media 3 times and can't get it to boot once after install11:34
rick_hit's got me confused as the very first time I installed and rebooted it worked. I installed updates and it broke. I thought it was something with grub, but seems more kernelish11:34
apwrick_h, could easily be, apple don't want you running linux so they don't help keep it working11:35
apwrick_h, have you tried like a saucy live cd ?11:35
apwlive image11:35
rick_hapw: no, the live image for trusty works. I used that to go back and do the reinstalls. I also used it to try to update-grub on it and see if something was off that a grub reset would fix11:36
rick_hso I can boot reliably off of that daily iso each time11:36
rick_hjust not after install is completed11:36
apwand which kernel does the daily iso have in it11:36
rick_hgood call, /me goes to get it and boot it again11:37
apwrick_h, i would also say try booting it nr_cpus=1 on the kernel command line11:38
apwnever know might make it start at least11:38
rick_hapw: k, will do11:38
apwrick_h, and if you do another install when the install is finished but before you reboot one needs to see what kernel that has11:39
apwyou should be able to open a terminal C-A-t stylee, and check the linux-image-* package version11:39
apwon your disk, by mounting it up and chrooting in11:40
rick_hthe daily iso I've got is using 3.13.0-8 3.13.0.8.1211:42
rick_hthat's what works repeatedly to get the installs up11:42
rick_hand that's what's installed as well. 11:43
=== gerald is now known as Guest24610
apwif you don't install updates during the install then it would definatly stay the saem11:45
rick_hyea11:45
rick_htrying the single cpu thing now11:46
rick_his that a "set nr_cpus=1" or does that go in the linux stanza?11:46
apwwell if that is the last thing it says on boot, then it has to most likely be a kernel issue, or a bootloader init issue, so i would file a bug against 'linux' to start with, and let us know the bug number so we can see if someone has the same h/w you do11:46
rick_hapw: rgr11:46
apwno it is a kernel command line change, so where like 'quiet debug'11:47
apwsplash wahtever11:47
rick_hcool, that boots11:48
rick_hwell got to the init list11:48
rick_hthere we go, lightdm asking for password11:48
rick_hapw: ok, thanks. from this install I can run XXX to file the bug so it grabs my hardware info?11:49
apw'ubuntu-bug linux' from the command line11:49
apwand include the cpu hack which got you booting11:50
infinityOf course, the first thing people will ask is to upgrade to the latest kernel and try again, so that might be worth doing now. :P11:50
apwthere being a new kernel on there :)11:51
rick_hheh, networkless atm booo11:52
apwhenrix, ok that seems to have worked right, panic over11:55
henrixapw: cool, and looks like 2 cves are now gone from the matrix11:55
apwhenrix, yeah, finally got those to go away11:56
ppisati_apw: bbone changes for T/unstable sent, i'll let you deal with the FTBFSs11:57
apwppisati_, thanks11:58
rick_hapw: thanks, filed bug with notes #1284085. Had to file from the liveusb boot because of the wireless issue, but it had the same kernel so hopefully ok12:22
apwbug #128408512:23
ubot2`Launchpad bug 1284085 in linux (Ubuntu) "unable to boot after install on 2013 macbook air" [Undecided,New] https://launchpad.net/bugs/128408512:23
apwrick_h, you should try updating that kernel to -12 and see if that works any better12:24
rick_hapw: I'll try to find a way to update it. 12:25
rick_hcheck out the latest daily iso, maybe it's in tere12:26
apwppisati_, is it you who does the ti-omap4 updates for SRU ?12:44
apwrick_h, and i assume you have tried booting without the noacpi option12:46
rick_hapw: correct, it still hangs at that SMP section12:54
=== Trevinho__ is now known as Trevinho
psivaaapw: just noticed, running command 'top' takes up about 2.3% cpu with Linux ubuntu-phablet 3.4.0-4-mako #25. would someone be able to take a look why this could be?13:19
apwpsivaa, is that a lot ?13:22
apwtakes .7 on my big laptop13:23
psivaaapw: it appears so. we check for 97.5% idle time *using top command13:23
apwyou run top to find out if the box is idle?13:24
psivaaso top itself taking up 2.3+ will always make that test fail13:24
psivaaapw: yes, we run top about 10 times with some time interval to see if the system has settled down before running other autopilot tests13:24
apwpsivaa, was it ever anything other than 2.3% or could it be that what this is doing on a lame cpu like that will always be 2.3%13:25
* cking wonders how much cpu top uses nowadays on these devices...13:26
ograapw, it was below that in the past ... we have a test called systemsettle that runs top 10 times in a row, the average idle needs to be better than 97.5%13:26
psivaaapw: so this behaviour is only after a new kernel update. earlier we used to have someting like http://q-jenkins.ubuntu-ci:8080/job/trusty-touch-mako-smoke-daily/27/artifact/clientlogs/ubuntu_weather_app/topbefore.log/*view*/13:26
ograit used to be better until the switch to android 4.4 13:27
psivaaabout .1%13:27
apwanyhow, it seems to me a daft way to get the idle time, when it is reported in /proc/stat13:27
* ogra didnt write the test ... 13:28
* apw didn't write the test either13:28
ograbut i can see that it massively degraded since the weekend13:28
apwyes, but perhaps that isn't top13:28
ograthere are other processes too that expose higher CPU load though 13:28
ogra(pulse mainly) 13:28
ograbut that top jumped that high is also significantly noticeable13:28
* apw laughs, pulse on a phone, yeah ... lets do that13:29
ograofono needs it 13:29
ogra(well, telepathy does)13:29
* apw still laughs13:29
apwpulse that machine eater here13:29
ckingogra, so which ones of these have changed, considering you have output from top it should be obvious?13:29
ograit used to behave too for the last 200 images :P13:29
ograyou would have to flip the whole android stack13:35
ograwhich makes the testing moot 13:35
apwthere is only 197,000 lines of change between the two13:37
ograah, easy then13:37
ograping me back for dinner about the responsible line please 13:37
ogra:P13:37
apwogra, so what phablet-flash incantation do i need to get the image that is showing this13:37
ographablet-flash is dead ... you want ubuntu-device-flash 13:38
apwok, what ubuntu-device-flash incantation do i need13:38
ograubuntu-device-flash -channel=trusty-proposed -bootstrap=true13:38
apwand ... where does it come from13:38
ograon mako, manta or flo ... 13:38
apwgiven my lovely shiney updated 20m ago trusty box doesn't have it13:38
ograeither trusty archive or for pre-trusty from the phablet-team ppa13:38
ograogra@styx:~/Devel/branches/rootstock-ng$ apt-cache policy ubuntu-device-flash|grep 50013:39
ogra        500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages13:39
ograshould be in universe13:39
apwogra, so if my phone has a -3 and is therefore pre this change yes?13:40
apwpsivaa, what top incation do you use to get this 2.3% number 13:40
ograsystem-image-cli -i 13:40
ogracheck the image version 13:40
ogra202 was the last android 4.2 one 13:40
ograyou should see something like 206 if your device is recent13:41
apw15313:41
ograwow13:41
ograthats ancient13:41
apwso, this is pre the change to 4.4 right? and top says top is taking 2.3%13:41
apwthough that is from looking at the screen and not at however how ps... is doing it13:42
apw 2613 root      20   0    2556   1128    732 R  2.3  0.1   0:01.06 top          13:42
ograhttps://jenkins.qa.ubuntu.com/job/trusty-touch-mako-smoke-daily/79/artifact/clientlogs/ubuntu_calculator_app/topafter.log/*view*/13:42
ograthere you see that it bups up to 36% at times 13:42
apwthere is little supprise at that, have you seen just how much output this thing produces13:43
ograthis is from image 196: https://jenkins.qa.ubuntu.com/job/trusty-touch-mako-smoke-daily/64/artifact/clientlogs/ubuntu_calculator_app/topafter.log/*view*/13:44
ografor comparison13:44
ograand it was constantly like this 13:44
ograhmm, in faxct 13:45
ograapw, i see the 37% there as well at times ... i wonder if psivaa is just hunting fleas here 13:45
ogra(btw the test was written by asac ... not sure why he didn parse /proc instead)13:46
* ogra waits for psivaa to come back13:48
ograi dont really think it is tops fault 13:48
=== e11bits_ is now known as e11bits
=== fish__ is now known as fish_
apwtop is a very cpu intensive thing, it is doing 3 or file open and reads per process on your system for every single sample13:54
apwogra, ubuntu-device-flash seems to just hang anyhow, is there a trick to this new undocumented interface?13:54
ograapw, no, its the same thing in green^Wgo13:57
ograjust a rewrite of the python tool in go ... 13:58
ograit should behave and function no different than phablet-flash did (less racy though)13:58
ograpsivaa, so looking at older logs, top always spiked to something like 36% inbeteen 14:01
ograso i dont think this is something new14:01
psivaaogra: aiui when the settle test starts to run, 'top' always takes about 20% +, but then it settles down to .1% ish soon enough so that it dint influence the test14:07
psivaabut now it stays on 2.+ %14:07
ograpsivaa, i see it even on 196 spike to 36% during the run14:07
psivaaogra: would you mind pasting the top log please. i am only seeing that on the first iteration it goes to some large value and then on the comes down14:13
ograpsivaa, https://jenkins.qa.ubuntu.com/job/trusty-touch-mako-smoke-daily/64/artifact/clientlogs/music_app/topbefore.log/*view*/14:14
ograat least three times in there 14:15
ogra*during* the tests ... not at the beginning or end 14:15
psivaaogra: yea i see that. but the test will pass as soon as we see at least one top run where the idle time goes above 97.514:18
ograpsivaa, right, i just think it isnt an issue with top 14:18
ograit doesnt behave differently 14:19
psivaaogra: ok, yea, i was only concerned that it stayed at a constant level 2.3 % in the current image when it was only spiking in the past. probably something else then14:20
=== psivaa is now known as psivaa-afk-bbl
apwpsivaa-afk-bbl, ogra, ok this is accounted for by a change to what is reported in /proc/stat (which is consumed by top)14:36
ograaha14:36
apwbasically when the machine is idle, cpus are turned off complely, in the previous kernel the offline cpus counted as 100% idle, now the do not14:37
apwthey no longer exist when off, so if you busy the one online cpu it counts more14:37
ograyeah14:38
ograwe need to adjust the test 14:38
ogra(and someone should re-write it to not use top)14:38
=== bdmurray_ is now known as bdmurray
=== yofel_ is now known as yofel
BenCinfinity: building15:39
=== psivaa-afk-bbl is now known as psivaa
psivaaapw: ogra ack, thanks15:55
=== elmo_ is now known as elmo
apwogra, ok so phone in either the bootloader or recovery, flash does nothing obvious, so i cannot tell if it is doing it, or not, though if i remove the phone it doens't notice so i assume not16:35
ograapw, complaints go to sergiusens 16:36
ogra:)16:36
ograapw, the code is go at least :)16:36
* apw gives up, 2 hours is enough, someone else can do the testing16:37
sergiusensapw, there's a landing in the train with hints16:37
apwsergiusens, but how do i diagnose it right now16:37
sergiusensapw, what are you running?16:37
apwubuntu-device-flash -channel=trusty-proposed -bootstrap=true -device=mako16:37
sergiusensapw, are you in the android bootloader?16:37
apwdevice cause without it pukes about getprops being missing16:38
sergiusensno need to use device flag16:38
apwsergiusens, looks like the bootloader to me, the green thing on its back16:38
apwit pukes without the device flag16:38
sergiusensapw, does it say fastboot mode on the screen?16:38
apwor does nothing16:38
apwsergiusens, in red, yes16:38
sergiusensapw, ok, might be a bug in the flags package which I'm changing (still under review)16:39
sergiusensapw, run it like ubuntu-device-flash --channel trusty-proposed --bootstrap16:39
apwsergiusens, ok so i pulled out the usb and put it back in, after booting it to the bootloader, and it has done something16:40
apwso i suspect there is an ordering issue here16:40
sergiusensapw, can you strace it?16:41
apwsergiusens, it looks to have done whatever it was meant to and exited now16:41
apwand the phione is doing something plausible.  so it seems lpugging in the phone then moving it to bootloader does not work16:42
apwreplugging it once in bootloader seems to have unstuck it16:42
sergiusensapw, I tried that though16:42
sergiusensapw, let me try again and see if I can reproduce16:42
apwbeyond me, hopfully you put some hints in there that tell you what it is trying so you can tell :)16:43
=== alexblig- is now known as alexbligh
=== kees_ is now known as kees
=== chiluk` is now known as chiluk
=== zz_mwhudson is now known as mwhudson
=== mwhudson is now known as zz_mwhudson
=== zz_mwhudson is now known as mwhudson
=== mjg59` is now known as mjg59
=== fmasi is now known as Guest26924
hallynapw: sforshee: hi, any new thoughts on the overlayfs xattr patch?23:20
infinityBenC: \o/23:56

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