[00:05] <arges> cyking: why is there a y in your nick
[00:10] <cyking> Cy King
[00:37] <arges> cyking: ah, sorry thought you were cking : )
[06:15] <sbeattie> bjf: if you look at http://kernel.ubuntu.com/testing/dagmar__3.13.0-53.89__2015-05-20_21-43-00/console_output.txt.html you'll see apt-get update pulling trusty, trusty-security, and trusty-updates Sources, but not for trusty-proposed.
[06:16] <sbeattie> which tells me that there's no deb-src line in apt sources.list for trusty-proposed.
[06:25] <pkern> infinity: Thanks. I'll have a look this morning.
[07:40] <henrix> pkern: please let me know too if that kernel looks ok ;)
[07:56] <genkgo> jsalisbury: that new build is doing better
[07:57] <genkgo> jsalisbury: could tools was installed, but to install tools, i need binutils >= 2.25
[07:58] <genkgo> i am still on 2.24 (i guess because i am on trusty with 3.19 kernel)
[07:58] <genkgo> perhaps i can still with --ignore-depends
[08:02] <genkgo> jsalisbury: just ran sudo dpkg --ignore-depends=binutils -i linux-tools-3.19.0-18*.deb and the package was installed
[08:02] <genkgo> apw: could you confirm that it is alright to ignore binutils dependency in this case?
[08:02] <apw> genkgo, i think you should be ok indeed
[08:03] <genkgo> apw: well wonderful, then i can start testing the patches
[08:03] <genkgo> :)
[08:23] <infinity> pkern: As soon as you can get me some positive "yay, it fixes the bug" results on that trusty kernel, I can unleash it on the masses.
[08:41] <niluje> what's the difference between the UIO and the VFIO drivers?
[09:13] <pkern> infinity: Yeah, I'm in the office now to test. :)
[09:13] <infinity> pkern: \o/
[09:14] <infinity> pkern: Looks like we'll just barely make my 24h turnaround guess, then. :)
[09:23] <pkern> infinity: lgtm, thanks :)
[09:23] <pkern> henrix: ^^
[09:24] <henrix> pkern: ack, thanks!
[09:25] <infinity> pkern: Ta.  Releasing them all, then.
[15:09] <cyking> good morning!
[16:15] <cyking> 3.19.0-18-generic botched my AMD video driver (fglrx)
[16:27] <apw> cyking, what version did it work with before that ...
[16:28] <apw> cyking, and ... what does "botched" mean to you
[16:28] <cyking> checking,
[16:29] <cyking> Linux Main-PC 3.19.0-031900-generic
[16:31] <apw> cyking, ok that is a mainline kernel, did it work with any of our official kernels
[16:31] <cyking> apw: yes -worked with the last official kernel
[16:32] <apw> cyking, which is the last one you actually tested, which version number
[16:32] <apw> as -17.17 and -18.18 are mostly identical in the video arena iirc
[16:32] <cyking> all these kernels worked - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1453391  
[16:35] <cyking> checking my /var/log/apt  I believe it was linux-image-extra-3.19.0-16-generic
[16:35] <apw> ok, so that is more believeable as there are actully some changes from -16 to -18
[16:35] <apw> cyking, now can you describe botched for me
[16:37] <cyking> apw: i get the radeon driver instead of the fglrx driver.  and radeon doesn't let me work with multiple displays.
[16:38] <apw> did fgrlx build against -18 for you ?
[16:39] <cyking> apw, i really just did a gui update and did not have any errors.  is there a log i can check for you?
[16:42] <cyking> does help:  /var/log/apt:  http://pastebin.com/bea9Ck6a
[16:43] <apw> cyking, there is a log in /var/lib/dkms, like here i have this for nvidia dkms package i happen to have installed: /var/lib/dkms/nvidia-340-updates/340.76/3.19.0-16-generic/x86_64/log/make.log
[16:45] <apw> obviously subsitute in the versions you have installed of radeon
[16:46] <cyking> apw, http://pastebin.com/7VEixiZn
[16:47] <apw> cyking, so that seemed to build ok, if that was the right kernel version
[16:47] <apw> /var/lib/dkms/nvidia-340-updates/340.76/3.19.0-16-generic/x86_64/log/make.log
[16:47] <apw> grrr
[16:48] <apw> so
[16:48] <apw> DKMS make.log for fglrx-updates-core-15.200 for kernel 3.19.0-16-generic (x86_64)
[16:48] <apw> that is the log for -16 which worked we want the one for -18
[16:50] <cyking> apw: should i boot into -18 and try to force reinstall the dkms driver?
[16:56] <cyking> there is no log for -18
[16:57] <apw> cyking, can you list the packages with 3.19.0-18.18 in their version ...
[16:57] <apw> dpkg -l | grep 3.19.0-18
[16:58] <cyking> http://pastebin.com/J0ZT5TZX
[16:59] <apw> cyking, you don't have the headers installed for that kernel, so dkms cannot build fo rit
[17:00] <apw> cyking, do you have the right meta package installed for the kernel?  linux-generic ?
[17:00] <cyking> strange. if i have linux-headers-3.19.0-16-generic and linux-headers-3.19.0-16 installed wouldnt apt-get update automatically install the latest?
[17:00] <cyking> *dist-upgrade
[17:01] <apw> cyking, headers are pulled in by linux-headers-generic
[17:01] <apw> whihc is a dep of linux-generic
[17:01] <apw> i assume you have lost some of your meta packages somewhere along the line
[17:02] <cyking> thanks apw: installing now. must of gotten removed accidental with all my kernel testing with my other bug im trying to deal with.
[17:03] <apw> cyking, very likely it got removed when you jammed something else on, apt loves to do that for you
[17:03] <apw> and although it is right there in front of you, i find one never notices it
[17:04] <cyking> how do i rebuild now ?
[17:04] <apw> shoving the headers on should trigger the dkms build automatically
[17:05] <apw> you should see it in the output when you apt-get install linux-generic or whatever
[17:05] <cyking> is it doing it here:   run-parts: executing /etc/kernel/header_postinst.d/dkms 3.19.0-18-generic /boot/vmlinuz-3.19.0-18-generic
[17:06] <cyking> i see the  log now. thanks
[17:06] <apw> that looks believeable, once you get a prompt back you should be able to see the log
[17:06] <apw> so then a reboot should use that driver i'd say
[17:06] <cyking> is there an idiots guide on doing a kernel bisect ?  
[17:07] <apw> there is a wiki guide, but i normally ask joe, he is a bisect speciialist
[17:07] <apw> jsalisbury, ^
[17:08] <cyking> jsalisbury seems pretty busy :)
[17:08] <cyking> i use to kernel hack in 2.4 days but so much has changed.
[17:08] <jsalisbury> cyking, I actually started a bisect for your bug
[17:09] <cyking> jsalisbury, thanks
[17:09] <jsalisbury> cyking, there was a build failure so I had to skip some sha1s.  I should have a kernel ready soon
[17:10] <jsalisbury> cking, actually the next kernel is ready.  I'll upload it and post a link in the bug
[17:10] <cyking> jsalisbury, you are a star!
[17:10] <jsalisbury> :-)
[17:10] <cyking> and you too, awp, thanks
[17:16] <cyking> jsalisbury, ill install the *rc3.201505211629_all.deb ?
[17:17] <jsalisbury> cyking, You should just need: linux-image-3.13.0-031300rc3-generic_3.13.0-031300rc3.201505211629_amd64.deb
[17:18] <jsalisbury> cyking, just run: sudo dpkg -i linux-image-3.13.0-031300rc3-generic_3.13.0-031300rc3.201505211629_amd64.deb
[17:18] <jsalisbury> cyking, then reboot
[17:19] <cyking> yup understood
[17:19] <cyking> sudo make internet faster ?
[17:19] <cyking> ;)
[17:20] <jsalisbury> heh
[17:39] <cyking> jsalisbury, worked fine.
[17:44] <jsalisbury> cyking, great.  I'll update the bisect and build the next kernel
[17:45] <cyking> wish i could see a screen cast of what you were doing ;)
[18:17] <bjf> sbeattie, i think the trusty apparmor testing is fixed
[18:18] <bjf> sbeattie, it worked once :-) ... we'll see for sure next week (new kernel SRU cycle)
[18:19] <sbeattie> bjf: hehe
[18:21] <sbeattie> bjf: the trusty apparmor sru should fix https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1304447 so please do comment on that bug report
[18:22] <bjf> sbeattie, comment added
[19:06] <dsmythies> Somewhere between kernel 4.0 and kernel 4.1RC1 "perf record" became broken. Actually the list of available "Tracepoint event"s become very much smaller. My concern is with "power:pstate_sample", which is now missing. I have started to bisect the kernel, but thought to ask here also, as I really don't have 2 days to waste. Anybody know what is going on with this?
[19:10] <rtg> dsmythies, are you booting vanilla or ubuntu kernels ? ubuntu does carry some ftrace patches.
[19:11] <dsmythies> I only compile the mainline kernel, using the Ubuntu kernel config.
[19:12] <rtg> dsmythies, nothing springs to mind.
[19:13] <dsmythies> I'll continue my bisection (my second one for the 4.1RC series...)
[20:16] <nessita> jsalisbury, hi there, are you around?
[20:20] <nessita> jsalisbury, just wanted to sync about the bisect we're doing for LP: #1201528, since I'm now in 3.8.13.1 and audio died with the underrun error. So I re-read all the comments and noticed that in commnet #39 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1201528/comments/39) I reproduced the issue with kernel 3.8.0-27-generic
[20:21] <nessita> I'm now installing latest 3.7 from http://kernel.ubuntu.com/~kernel-ppa/mainline/ which is 3.7.10 and see if audio breaks, will report in the bug
[20:54] <jsalisbury> nessita, ack, thanks for the info
[20:55] <nessita> jsalisbury, so 3.7.10 works (used skype heavily, and hangouts), and in theory 3.8.0 did not work (from comment #39). Which kernel shall I try next?
[20:56] <nessita> want me to re-test 3.8.0? I guess that'll be v3.8-raring?
[20:56] <jsalisbury> nessita, probably 3.7 final, then we can bisect between 3.7 and 3.8.  3.7 final is avaiable at:
[20:56] <jsalisbury> http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7-raring/
[20:56] <jsalisbury> nessita, it might be a good idea to test 3.8 final as well to confirm it has the bug.  3.8 final is avaiable at:
[20:57] <jsalisbury> http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-raring/
[20:57] <nessita> jsalisbury, ah, hum, I always thought that 3.7.0 (from the link you just gave me) is "older" than 3.7.10. Am I mistaken? 
[20:58] <jsalisbury> nessita, yes you are correct.  But we can't bisect between 3.7.10 and 3.8 because the tree splits as of 3.7.1.  
[20:58] <nessita> ah! that makes more sense :-)
[20:58] <nessita> I will them test both finals, 3.7.0 and 3.8.0 and report back
[21:14] <nessita> jsalisbury, kernel 3.7.0 is frozen on boot when showing the message "Loading initial ramdisk", can not reboot with ctrl+alt+del nor with alt+petsys+b, doing hard reboot, but wondering if it should boot OK
[21:15] <jsalisbury> nessita, it should boot ok.  We can skip to trying v3.8-rc1 if there are issues with 3.7 final.  3.8-rc1 is available here:
[21:15] <jsalisbury> http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc1-raring/
[21:16] <nessita> jsalisbury, hum, there may be something broken in my computer now, because 3.8.0 freezes the same as 3.7.0
[21:16] <nessita> may boot without quiet and see where it freezes
[21:16] <jsalisbury> nessita, ok