User1: User2 why is there a y in your nick
User2: Cy King
User1: User2 ah, sorry thought you were cking : )
User3: User12 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.
User3: which tells me that there's no deb-src line in apt sources.list for trusty-proposed.
User4: User8 Thanks. I'll have a look this morning.
User5: User4 please let me know too if that kernel looks ok ;)
User6: User11 that new build is doing better
User6: User11 could tools was installed, but to install tools, i need binutils >= 2.25
User6: i am still on 2.24 (i guess because i am on trusty with 3.19 kernel)
User6: perhaps i can still with --ignore-depends
User6: User11 just ran sudo dpkg --ignore-depends=binutils -i linux-tools-3.19.0-18*.deb and the package was installed
User6: User7 could you confirm that it is alright to ignore binutils dependency in this case?
User7: genkgo, i think you should be ok indeed
User6: User7 well wonderful, then i can start testing the patches
User6: :)
User8: User4 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.
User9: what's the difference between the UIO and the VFIO drivers?
User4: User8 Yeah, I'm in the office now to test. :)
User8: User4 \o/
User8: User4 Looks like we'll just barely make my 24h turnaround guess, then. :)
User4: User8 lgtm, thanks :)
User4: User5 ^^
User5: User4 ack, thanks!
User8: User4 Ta.  Releasing them all, then.
User2: good morning!
User2: 3.19.0-18-generic botched my AMD video driver (fglrx)
User7: cyking, what version did it work with before that ...
User7: cyking, and ... what does "botched" mean to you
User2: checking,
User2: Linux Main-PC 3.19.0-031900-generic
User7: cyking, ok that is a mainline kernel, did it work with any of our official kernels
User2: User7 yes -worked with the last official kernel
User7: cyking, which is the last one you actually tested, which version number
User7: as -17.17 and -18.18 are mostly identical in the video arena iirc
User2: all these kernels worked - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1453391
User10: Launchpad bug 1453391 in linux (Ubuntu) "Very slow Qualcomm Atheros AR8121/AR8113/AR8114 Gigabit or Fast Ethernet (rev b0)" [Medium,Confirmed]
User2: checking my /var/log/apt  I believe it was linux-image-extra-3.19.0-16-generic
User7: ok, so that is more believeable as there are actully some changes from -16 to -18
User7: cyking, now can you describe botched for me
User2: User7 i get the radeon driver instead of the fglrx driver.  and radeon doesn't let me work with multiple displays.
User7: did fgrlx build against -18 for you ?
User2: apw, i really just did a gui update and did not have any errors.  is there a log i can check for you?
User2: does help:  /var/log/apt:  http://pastebin.com/bea9Ck6a
User7: 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
User7: obviously subsitute in the versions you have installed of radeon
User2: apw, http://pastebin.com/7VEixiZn
User7: cyking, so that seemed to build ok, if that was the right kernel version
User7: /var/lib/dkms/nvidia-340-updates/340.76/3.19.0-16-generic/x86_64/log/make.log
User7: grrr
User7: so
User7: DKMS make.log for fglrx-updates-core-15.200 for kernel 3.19.0-16-generic (x86_64)
User7: that is the log for -16 which worked we want the one for -18
User2: User7 should i boot into -18 and try to force reinstall the dkms driver?
User2: there is no log for -18
User7: cyking, can you list the packages with 3.19.0-18.18 in their version ...
User7: dpkg -l | grep 3.19.0-18
User2: http://pastebin.com/J0ZT5TZX
User7: cyking, you don't have the headers installed for that kernel, so dkms cannot build fo rit
User7: cyking, do you have the right meta package installed for the kernel?  linux-generic ?
User2: 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?
User2: *dist-upgrade
User7: cyking, headers are pulled in by linux-headers-generic
User7: whihc is a dep of linux-generic
User7: i assume you have lost some of your meta packages somewhere along the line
User2: thanks User7 installing now. must of gotten removed accidental with all my kernel testing with my other bug im trying to deal with.
User7: cyking, very likely it got removed when you jammed something else on, apt loves to do that for you
User7: and although it is right there in front of you, i find one never notices it
User2: how do i rebuild now ?
User7: shoving the headers on should trigger the dkms build automatically
User7: you should see it in the output when you apt-get install linux-generic or whatever
User2: 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
User2: i see the  log now. thanks
User7: that looks believeable, once you get a prompt back you should be able to see the log
User7: so then a reboot should use that driver i'd say
User2: is there an idiots guide on doing a kernel bisect ?
User7: there is a wiki guide, but i normally ask joe, he is a bisect speciialist
User7: jsalisbury, ^
User2: jsalisbury seems pretty busy :)
User2: i use to kernel hack in 2.4 days but so much has changed.
User11: cyking, I actually started a bisect for your bug
User2: jsalisbury, thanks
User11: cyking, there was a build failure so I had to skip some sha1s.  I should have a kernel ready soon
User11: cking, actually the next kernel is ready.  I'll upload it and post a link in the bug
User2: jsalisbury, you are a star!
User11: :-)
User2: and you too, awp, thanks
User2: jsalisbury, ill install the *rc3.201505211629_all.deb ?
User11: cyking, You should just need: linux-image-3.13.0-031300rc3-generic_3.13.0-031300rc3.201505211629_amd64.deb
User11: cyking, just run: sudo dpkg -i linux-image-3.13.0-031300rc3-generic_3.13.0-031300rc3.201505211629_amd64.deb
User11: cyking, then reboot
User2: yup understood
User2: sudo make internet faster ?
User2: ;)
User11: heh
User2: jsalisbury, worked fine.
User11: cyking, great.  I'll update the bisect and build the next kernel
User2: wish i could see a screen cast of what you were doing ;)
User12: sbeattie, i think the trusty apparmor testing is fixed
User12: sbeattie, it worked once :-) ... we'll see for sure next week (new kernel SRU cycle)
User3: User12 hehe
User3: User12 the trusty apparmor sru should fix https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1304447 so please do comment on that bug report
User10: Launchpad bug 1304447 in apparmor (Ubuntu) "apport-bug crashing on server install" [Medium,Fix released]
User12: sbeattie, comment added
User13: 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?
User14: dsmythies, are you booting vanilla or ubuntu kernels ? ubuntu does carry some ftrace patches.
User13: I only compile the mainline kernel, using the Ubuntu kernel config.
User14: dsmythies, nothing springs to mind.
User13: I'll continue my bisection (my second one for the 4.1RC series...)
User15: jsalisbury, hi there, are you around?
User15: jsalisbury, just wanted to sync about the bisect we're doing for LP: #1201528, since I'm now in 91.69.162.6 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
User10: Launchpad bug 1201528 in linux (Ubuntu Vivid) "[INTEL DP55WG,Realtek ALC889] - Audio Playback Unavailable" [Medium,Confirmed]
User15: 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
User11: nessita, ack, thanks for the info
User15: 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?
User15: want me to re-test 3.8.0? I guess that'll be v3.8-raring?
User11: nessita, probably 3.7 final, then we can bisect between 3.7 and 3.8.  3.7 final is avaiable at:
User11: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7-raring/
User11: 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:
User11: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-raring/
User15: 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?
User11: 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.
User15: ah! that makes more sense :-)
User15: I will them test both finals, 3.7.0 and 3.8.0 and report back
User15: 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
User11: 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:
User11: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc1-raring/
User15: jsalisbury, hum, there may be something broken in my computer now, because 3.8.0 freezes the same as 3.7.0
User15: may boot without quiet and see where it freezes
User11: nessita, ok
ubuntu-kernel
Ubuntu IRC