=== mwhudson is now known as zz_mwhudson
=== zz_mwhudson is now known as mwhudson
ppisati1 2 3 test...07:31
=== mwhudson is now known as zz_mwhudson
smbppisati, nobody is here to hear you screaming. :)08:19
ppisatinobody can hear you scream! :)08:19
ppisatilet me start mumble so you can hear it at least... :)08:20
* apw yawns09:09
* apw has a vision of ppisati being attached to large electrodes ... bzzzzztttt09:10
apwRAOF, Beeeees :)09:12
=== psivaa_ is now known as psivaa
=== zz_mwhudson is now known as mwhudson
=== mwhudson is now known as zz_mwhudson
phillwhi, please do not laugh :P when using make to compile a kernel up, how do I specify which .config file to use? 12:13
phillwI've made what I believe are the changes I want using menuconfig and saved the resulting file as .myconfig12:18
phillwsorry about that, the build a new kernel cooked my laptop! I'm stansferring over to the dedicated server :)12:28
=== ricmm_ is now known as ricmm
eagles0513875apw: re the multitouch patch can you follow up as I never got a response on the kernel input mailing list and it has been more then a few days13:40
rtgapw, 3.13.0-3 seems to have wrecked my user experience on a Dell M1710. nouveau crashes almost immediately.13:47
apwrtg, woh unexpected, was there anything much in there at all ?13:47
rtgjust the rebase to -rc8 AFAICT13:48
rtg-2 works fine13:48
rtgguess I'll try the vanilla kernels first13:48
apwrtg, when you say crash does it bug ?13:48
rtgapw, all I get is the tail end of the stack dump13:49
rtgcan't tell if its bugging or not13:49
apwis it locked so hard you cannot get in ?13:52
apwphillw, depends if you are talking about a "make" in a mainline tree where it uses .config, or a debian package where it is "harder"13:52
apwrtg might be worth seing if you can boot it without graphics and the ssh in tail -f /var/log/syslog and then start X13:55
phillwapw I was at http://bodhizazen.net/Tutorials/kernel#easy and had worked out which pentium chips I wanted etc.... then headed to http://bodhizazen.net/Tutorials/kernel#Compile but suspect that I need to tell that command the name of my .config file?13:56
rtgapw, ack - rebooting to vanilla -rc7 and -rc8 just to be sure13:57
rtgapw, the last line printed with vanilla -rc8 is :14:08
rtgdrivers/video/fbmem.c:                  printk(KERN_INFO "fb: conflicting fb hw usage 14:08
rtgthat is without the  splash screen14:08
smbHey that sounds a bit like the framebuffer eject problem all over the place again14:09
rtgsmb, weren't you looking at a bug like that ?14:10
smbrtg, VMs and cirrus14:10
ubot2Launchpad bug 1269401 in linux (Ubuntu) "[Trusty] Switching framebuffers fails on VMs using cirrus" [Medium,Confirmed]14:10
smbI was told there should be a user-space fix that prevents load of the generic fb for certain cases14:11
smbIn theory also cirrus but something seems to have gone amiss14:11
* henrix remembers something like that on lkml...14:11
smbMain problem is plymouth doing something with the current fb even without splash14:12
smbSo releasing the current one for another one cannot free resources14:13
apwrtg, hrm, nasty14:13
rtgapw, at least there are some google hits on that string14:14
apwnot sure why the -rc7->-rc8 would expose that any more than before14:14
rtgapw, dunno. back in a asec, gonna migrate to my workstation so I can mess with this laptop and not disappear constantly.14:15
apwrtg, any luck ?14:31
rtgapw, uh, working on a couple of distractions. I'll get back to it in a sec14:33
phillwsmb rtg https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1080674 it goes back a lot further :) As no one will fix it, I just use the work around.14:36
ubot2Launchpad bug 1080674 in cairo "[QEMU] Corrupted desktop screen for raring desktop installation in QEMU guest (Cirrus graphics). Affects KVM but not VBox." [Medium,Confirmed]14:36
smbphillw, Without looking into the bug... likely that is the background gfx issue when not using the cirrus drm driver... 14:39
smbWhich iirc is a bug in the cirrus x driver in conjunction with probably llvm-pipe + unity14:40
smband no nobody seems to care much about that14:40
phillwsmb I did run with that bug for a while, but there is a limit as to how many brick walls you wish to bash your head on :)14:40
smbSure and given the (not)performance of using llvm-pipe for 3d gfx anyway there seems to be a lost ground for running desktop in a VM (warning: very personal and opinion)14:42
phillwsmb I'm not a kernel person! but the word 'cirrus' causes my ears to pick up, as I still have to use https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1080674/comments/43 when installing desktop systems into KVM14:44
ubot2Launchpad bug 1080674 in cairo "[QEMU] Corrupted desktop screen for raring desktop installation in QEMU guest (Cirrus graphics). Affects KVM but not VBox." [Medium,Confirmed]14:44
smbphillw, Right the current better option is to use a different virtual gfx card. If we can solve the race with the framebuffer you would have a kernel-mode-settting driver (the mentioned cirrus module) which then gets you X to use a generic kvm drivers which gives not corrupted gfx14:49
smb*shat should be generic kms14:49
phillwsmb: like forrest gump, simple be, simple do. That work around works for me.. as to if https://bugs.freedesktop.org/show_bug.cgi?id=58574 will ever be fixed? Well, let's just say I'm not holding my breath :)14:52
ubot2Freedesktop bug 58574 in Driver/cirrus "pixmap regression with cirrus graphics driver" [Normal,New]14:52
smbphillw, Neither would I (hold my breath) :)14:54
phillwhe he,,, well, I'm back to build a kernel on a VM that will not over heat and shut down... I'll be able to state how 12.04lts server to 14.04 lts server goes when I have made a new kernel :)14:56
eagles0513875apw: ping15:07
=== manjo` is now known as manjo
rtgapw, -rc8+ may have solved the problem16:00
phillwrtg: is it worth me trying http://bodhizazen.net/Tutorials/kernel and build a kernel, as the server spent 2 hours on upgrading to 14.04 and still has 3.8.0 as the kernel (NOT what I spent 2 hours waiting for)16:10
phillwrtg: I have linux-3.13-rc8 on the VM.... your call :)16:12
rtgphillw, you upgraded to trusty and you _still_ have the raring kernel ?16:12
phillwrtg: indeed.... but that is a server test issue... i actually need trusty for a community respin16:13
phillwrtg: ali@amjjawad:~/src$ uname -a16:14
phillwLinux amjjawad 3.8.0-29-generic #42~precise1-Ubuntu SMP Wed Aug 14 16:19:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux16:14
rtgI assume you rebooted ?16:15
phillwyou assume correctly :)16:15
rtgdpkg -l|grep linux-image16:15
phillwali@amjjawad:~/src$ Linux amjjawad 3.8.0-29-generic #42~precise1-Ubuntu SMP Wed Aug 14 16:19:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux16:16
phillwNo command 'Linux' found, did you mean:16:16
phillw Command 'linux' from package 'user-mode-linux' (universe)16:16
phillwLinux: command not found16:16
phillwali@amjjawad:~/src$ 16:16
phillwrtg:  this worked better16:17
phillwali@amjjawad:~/src$ dpkg -l | grep linux-image16:17
phillwii  linux-image-3.8.0-29-generic                          3.8.0-29.42~precise1                                      amd64        Linux kernel image for version 3.8.0 on 64 bit x86 SMP16:17
rtgcat /etc/lsb-release16:18
phillwrtg: ali@amjjawad:~/src$ cat /etc/lsb-release 16:19
phillwDISTRIB_DESCRIPTION="Ubuntu Trusty Tahr (development branch)"16:19
phillwali@amjjawad:~/src$ 16:19
rtgphillw, you upgraded from 12.04 ?16:19
phillwindeed, my best guess is that the server kernel was not allowed to update.... server kernels are funny things!16:20
phillwserver was 12.04.316:21
rtgphillw, hmm, I may know what happened. guess I'd better go fix that.16:22
phillwthat's fine. can you ping me on #phillw (in case I have left here) to let me know what to do to bring that test area for 14.04 "up to speed". many thanks :)16:23
BenCapw: I'm having serious issues with 3.13. When it hits initramfs, I get immediate kernel stack overflow in random processes16:24
BenCapw: Are you guys syncing to a newer -rc soon?16:24
rtgBenC, we're up to -rc8 now. then next one should be the 3.13 release16:26
BenCrtg: I may have rebased before you did -rc8. When was that?16:32
rtga couple days ago I think. apw did it16:32
BenCNope, I'm on rc816:33
BenCLet me check upstream tree and see if there's anything of interest16:33
phillwrc8 is the latest they advertise on https://www.kernel.org/ no doubt, there is another link I should look at :)16:35
apwBenC, hrm, thats very odd indeed stack overflow as in stack space exceeded implosions ?16:36
rtgBenC, there is on poerpc patch after -rc816:36
BenCapw: As in, something is recursively going on inside the kernel, through a sys call from userspace16:37
BenCUnsure if the details, because it's no certain process or syscall16:37
apwrtg, perhaps we should do an interim re16:38
apwrtg, perhaps we should do an interim rebase, if they sound plausible16:38
rtgapw, I'm thinking about rebasing against tip for the nouveau fix16:38
apwthat said, i don't think this one powerpc fix can be relevant16:39
rtgapw, it definitely blocks on console_lock() in -rc8, but works with tip. there are 4 patches that look to be of interest16:39
apwbut if you needed to do it for that ... that'd be worth it16:39
apwas we are still rebasing and all16:39
BenCI'll inspect the patches and see if it fixes me before rebasing on your update16:39
rtgapw, you have anything in the pipe yu wanna commit ?16:40
apwBenC, this doesn't look hopeful, it is all old h/w16:40
BenCOk, first I'll back out all of my sauce and see if that alleviates the issue16:41
BenCBest to make sure of that first16:41
apwrtg, nothing other than whats already pushed, i am trialing splitting out the hyper-v tools into their own tools package, might make maintenace easier and slim the virtual images16:41
rtgapw, ack, then I'll package and upload16:41
phillwif you guys would like a VM (OVH) I do still have a free one with unique ipV4. build it, break it as often as you wish :)16:49
phillwrtg please give me a ping when you have it fixed (or a note to phillw@phillw.net ) It seams I now have a queue :)17:22
bjf[afk]phillw, that's what bugs are for ... have you filed one?17:26
phillwbjf[afk]:  Nope I did not, as rtg sated that he saw the issue, I saw no reason to "raise paper work". We are sill in alpha area and a chat is often better than a bug report.... unless some one wants to get into the "I closed most bugs" report.... which the kernel team do not play in :D17:29
=== bjf[afk] is now known as bjf
bjfphillw, "paper work" is for just such a thing .. so you get notified of fixes. this has nothing to do with bug-games people play17:31
phillwbjf: I arrived here to ask a question, the question has been asked and an answer given. Had the person who is solving the issue wished a bug report to be raised, I'm quite sure he would have asked me to do so..... When it comes to devs... I approach quietly and do as I'm told :)17:35
=== zz_mwhudson is now known as mwhudson
phillwbjf: I cannot file a bug for the in ability to move from 12.04 to 14.04 at kernel level. As it is a server, the log in sequence to try and register a bug is none working19:50
bjfjsalisbury, we want to keep an eye on bug 126991720:06
ubot2Launchpad bug 1269917 in linux (Ubuntu) "Kernel GPF" [Undecided,Incomplete] https://launchpad.net/bugs/126991720:06
jsalisburybjf, ack20:06
bjfjsalisbury, that apport collect failed to capture dmesg. i've not seen that HookError_source_linux.txt msg before.20:08
jsalisburybjf, I haven't seen that one before either.  I'll see if it's happened before and keep an eye out for new ones.  20:10
jsalisburybjf, think I should request testing of and or mainline in bug 1269917 ?20:26
ubot2Launchpad bug 1269917 in linux (Ubuntu) "Kernel GPF" [High,Incomplete] https://launchpad.net/bugs/126991720:26
bjfjsalisbury, no, i want them to test this new saucy kernel once it gets built20:26
jsalisburybjf, got it, thanks.20:26
bjfjsalisbury, with 700+ commits in it we might get lucky20:26
jsalisburybjf, yeah20:26
jsalisburybjf, looks like saucy-proposed will be at anyway.20:27
bjfjsalisbury, yes20:27
phillwjsalisbury: i mentioned an issue earlier, but as the machine is in flux, I cannot fully raise a bug21:03
phillw(16:19:56) rtg: phillw, you upgraded from 12.04 ?21:03
phillw(16:20:50) phillw: indeed, my best guess is that the server kernel was not allowed to update.... server kernels are funny things!21:03
phillw(16:21:26) phillw: server was 12.04.321:03
phillw(16:22:05) rtg: phillw, hmm, I may know what happened. guess I'd better go fix that.21:03
phillwjsalisbury: I most likely have the log on the VM but cannor send them to you good people :(21:04
bjfphillw, you can use: https://bugs.launchpad.net/ubuntu/+source/linux/+filebug to file a bug from a different system if that helps21:05
jsalisburyphillw, Would you be able to open a bug report manually at launchpad.net ?  You should be able to select Ubuntu as the distro and Linux as the package.21:06
jsalisburyheh, or just follow the link from bjf :-)21:06
phillwjsalisbury:  and bjf oh, i need to go password hunting :)21:07
phillwahh, wonderful... it requires GUI.... :(21:08
phillwali@amjjawad:~$ https://bugs.launchpad.net/ubuntu/+source/linux/+filebug21:09
phillw-bash: https://bugs.launchpad.net/ubuntu/+source/linux/+filebug: No such file or directory21:09
phillwali@amjjawad:~$ 21:09
jsalisburyphillw, You would need to enter that URL in a web browser, not from the command line.21:12
phillwjsalisbury: that is a server VM (KVM) is has no browser21:12
apwlynx ?21:13
phillwapw: the VM is a try to be 14.04, but the upgrade has messed up and it still have 12.04 kernel. 21:14
phillwjsalisbury: scroll back to (12:12:39) UTC and do feek free to join #phillw to tell me off :)21:23
phillwand, of course, being CLI... have no idea of the command to issue :)21:24
phillwjsalisbury: Linux amjjawad 3.8.0-29-generic #42~precise1-Ubuntu SMP Wed Aug 14 16:19:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux21:33
phillwthat does seem a bug when you issue dist-upgrade -d .... this does need resolving as it spends two hours doing things and leaves you with 21:39
phillwali@amjjawad:~$ uname -a21:39
phillwLinux amjjawad 3.8.0-29-generic #42~precise1-Ubuntu SMP Wed Aug 14 16:19:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux21:39
phillwand 21:39
phillwali@amjjawad:~$  cat /etc/lsb-release21:39
phillwDISTRIB_DESCRIPTION="Ubuntu Trusty Tahr (development branch)"21:39
phillwali@amjjawad:~$ 21:39
phillwjsalisbury:  ^^21:40
infinityphillw: apt-get install linux-generic22:13
infinityphillw: And the migration path for lts-backport kernels is known to be a bit sketchy right now, we need to solve that.22:14
hallynsforshee: sorry i've not had a chance to test that patch myself, but it looked good to me (and i assume you've tested it yourself)22:14
hallynwill install and test it tomorrow. 22:14
sforsheehallyn: I have, but I noticed something today that makes me think there's something else going on22:14
sforsheeupstart opens console with O_NOCTTY, which should prevent it owning the tty22:15
sforsheeso I still don't know how upstart ends up owning that tty22:15
phillwinfinity: thanks, I'll try that. 22:15
hallynsforshee: ah.  interesting.22:17
hallynpotentially a bug elsewhere then...22:18
sforsheeyeah, not sure where though22:18
sforsheeis there some way I could strace init when it starts in the container?22:18
phillwinfinity: no major errors, can I ask it to be a new kernel, or is it still too unstabe?22:23
infinityphillw: It'll default to being the current kernel, and we're all running it.22:23
phillwinfinity: when I go to http://bodhizazen.net/Tutorials/kernel#easy for my non-pae kernel build how do I tell it to use the the .config file I want them it to use,?22:27
infinityphillw: Read the paragraph you linked to me?22:30
phillwinfinity:  bohdi-zazen is on #phillw  -- much easier to chat there?22:31
infinityphillw: Dude, you just asked me how to do the thing that that paragraph tells you how to do.  Pretty sure more chatting won't clear that up.22:32
phillwinfinity: and I install kernel 3.13 on to that 12.04 VM?22:34
phillwthat is what I'm awaiting for,22:34
infinityphillw: What 12.04 VM?  You were talking about a 14.04 system above...22:37
infinityphillw: Or, so lsb_release claimed.22:37
phillwinfinity: That is why you say what you say, and the bug team go "we do not believe you".... But, I actually believe bohdi-zazen who is on #phillw.22:41

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