/srv/irclogs.ubuntu.com/2015/03/27/#ubuntu-kernel.txt

AceLanapw: got it, thanks. BTW, I always use lts-backport-xxx branch on precise and trusty tree :p00:28
=== gerald is now known as Guest75447
Odd_BlokeHello kernel friends; I have a task for adding PTS/smoke testing in to the CPC image testing.  Is this something I can run with the kernel-testing/autotest stuff, or is this a different beast?10:21
Odd_Blokeapw, bjf: ^ ?10:24
apwOdd_Bloke, not quite sure what you are asking there, are you asking if running the kernle tests would be a good smoke test ?10:25
apwand remind me what PTS means10:25
Odd_Blokeapw: That makes two of us. ;)10:25
Odd_Blokeapw: I _think_ PTS==Phoronix Test Suite.10:26
Odd_BlokeBut if it's not obvious to you, then I should probably check what utlemming meant by it.10:27
apwOdd_Bloke, could be, not a phrase i use most days for sure10:38
apwOdd_Bloke, smoke testing is mormally "basic does it boot and give me a prompt" style testing10:39
Odd_BlokeYeah; I think this is a bit of a confused task.10:41
Odd_BlokeI'll check with Ben when he's back in on Monday.10:41
Odd_Blokeapw: Sorry for the noise! :)10:41
apwOdd_Bloke, np and good luck with that10:42
bguthroGreetings - A question about packaging, that I'm hoping someone can help with: Is there a way to do an iterative kernel build, without doing a clean? I'm debugging something that is part of the kernel proper (i.e., not a module) - and have been trying to avoid doing a full clean / build cycle...but so far have been unsuccessful. Despite placing a #error in a .c file as a test, my compile happily packages everything up, seemingly without recompiling12:17
bguthro this file. I'm using "AUTOBUILD=1 NOEXTRAS=1 skipabi=true skipconfig=true skipmodule=true fakeroot debian/rules binary" as a compile line, if it matters.12:17
bguthroI suspect there's a wiki page out there somewhere, but I've been unable to find it.12:19
apwbguthro, you need to remove the build stamp, and then you can rerun the command, stamps are in debian/stamps12:43
bguthroapw, fantastic - thank you much!12:44
=== JanC_ is now known as JanC
Odd_Blokeapw: Turns out http://bazaar.launchpad.net/~server-workload-testing-team/server-workload-testing/trunk/files/head:/pts/ is what we were talking about. :)15:29
apwOdd_Bloke, so it is phoronix, just a local copy15:31
Odd_BlokeIt's a wrapper around the Ubuntu package.15:33
Odd_Bloke(TIL there's an Ubuntu package for Phoronix)15:33
flexiondotorgI been discussing https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1368784/ with cjwatson in #ubuntu-devel16:04
ubot5Ubuntu bug 1368784 in virtualbox (Ubuntu) "Vivid and Utopic Virtualbox guest gets only up to resolution of 640x480" [High,Confirmed]16:04
flexiondotorgI've got the following work around - https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1368784/comments/1716:04
flexiondotorgcjwatson is prepare to update grub-gfxpayload-lists if someone here can confirm "fixing" this issue at a kernel level is hopeless.16:05
flexiondotorgSo, thoughts?16:05
flexiondotorgogasawara, Can you direct me to someone I can discuss the above with please?16:09
=== chuck_ is now known as zul
apwflexiondotorg, "fixing" at the kernel level, do we know what the issue is ?16:24
apwflexiondotorg, the implication of the (admittedly older) comments is that you need virtualbox-guest-x1116:24
apwflexiondotorg, and indeed i can confirm that installing the said package does sort things out, who knows what i has in it mind16:31
apwseems it has a vbox specific video drivers16:38
apwi wonder if they should be being installed by jockey16:48
flexiondotorgapw, So the issue is the default resolution when virtualbox-guest-x11 is not installed.16:49
apwthe default resolution is that offered by the vesa settings i assume ?16:50
flexiondotorgapw, The vmware video devices are already blacklisted by  grub-gfxpayload-lists16:50
apwok, so then it sounds like whatever this is using now is a candidate for blacklisting ?16:50
flexiondotorgapw, Must be. vesa is used by vbox when the guestadditions-x11 is absent.16:50
apwso that is a vbox issue really, offering stupid resolutions by default16:51
flexiondotorgapw, Since 14.04. Yes.16:51
flexiondotorgapw, The 640x480 thing started sometime during 14.10.16:51
apwand presumably it does that because they don't care about you if you don't install their video driver16:51
flexiondotorgapw, I couldn't possibly comment ;)16:52
apwi wonder why i makes a difference to blacklist it in grub though, vesa must be very broken16:52
apwand so i would think rather than being a fallback option to blacklist more things in grub, it might16:52
apwbe the appropriate option instead16:52
flexiondotorgapw, It is odd because when booting from the live media, resolution is 1024x768.16:53
flexiondotorgBut on first install, resolution is 640x480.16:53
apwright, that doesn't use grub, nor initialise the display16:53
apwit uses syslinux16:53
flexiondotorgapw, Indeed.16:53
apwgrub initialises the display, because you know the vesa modes offered should be the preferred size of your display, so setting it up early makes sense and makes things prettier16:53
apwunless your vesa config is spam16:53
apwand has "1 1024x768 2 640x480 (default)" in it ... or equiv16:54
flexiondotorgSo, possibly a regression in what Virtualbox provides.16:54
apwbut if we are blacklisting for vbox video anyhow, it may well make sense to blacklist everything when vbox is found16:55
apwwhich is what i assume the wildcard you added does16:55
flexiondotorgapw, Yes.16:55
flexiondotorgAlthough, AKAIK, vbox have only ever used one device ID for video.16:55
apwflexiondotorg, not that i really know why one would use vbox if you had any other choice16:56
flexiondotorgThe other "work around" is to configure grub to use 'console' for all video output.16:56
flexiondotorgapw, It is very popular with people who just want to test. Low barrier of entry.16:56
apwflexiondotorg, i don't find virtmgr any more complex to drive, and it idoesn't have these issue at least16:57
flexiondotorgapw, Agreed.16:57
apwand i don't need 30k lines of random out of tree junk loaded into my kernle to make it work either16:57
flexiondotorgBut, people do use vbox. Clearly the Ubuntu GNOME team do who reported this issue.16:57
flexiondotorgapw, So the question is. Is this fixable by the kernel team? Seems like a big fat "No" based on what we've discussed?16:58
apwwell they had much more ufn, they were just exploding in the host when they tried16:58
apwflexiondotorg, i am not sure what we would fix, grub handed us a configured terminal, and we continued to use it as instructed16:59
apwflexiondotorg, and presumably because vesa, it was at a stupid resolution16:59
flexiondotorgapw, That is a good answer.16:59
apwi'll try your workaround on that same gnome image in vbox and see how it looks16:59
flexiondotorgapw, So I think that blacklisting the vbox video device in grub is the way forward.17:00
flexiondotorgapw, OK. Thanks for testing.17:00
flexiondotorgapw, I am the maintainer of Ubuntu MATE BTW. This issue was flagged up in Beta 2 QA and I decided to take a peek.17:01
apwflexiondotorg, and i think the behaviour with the blacklist seems more useful, and i assume if i install the -guest-x11 i'll get go faster stripes17:04
flexiondotorgapw, Yes with guest-x11 install you get dynamic resizing and such.17:05
apwflexiondotorg, but yes, i htink my prefrered option is this blacklist, and if it fixes the issues you have with locked disks that sounds liek a win17:05
flexiondotorgapw, Agreed. Although the inability to enter encryption pass phrases affects actual hardware too. By blacklisting vbox for grub you get a text mode plymouth which always works.17:07
apwflexiondotorg, yeah, i assume we have a lot of issues there now we have systemd fun to play with17:07
apwi guess i ought to reinstall some of my kit with that to find out17:08
flexiondotorgapw, systemd isn't to blame for passphrase entry. That was present in 14.10 also.17:11
flexiondotorgapw, My "solution" was not to ship a graphical plymouth theme in 14.10. That way only test mode available and pass phrase entry worked.17:11
flexiondotorgapw, Are you still testing this on an Ubuntu GNOME image or have we concluded that blacklisting is the solution?17:21
apwi think we concur blacklisting is the way forward for the size issue17:29
apwthe plymouth not working is separate17:29
flexiondotorgapw, Thanks for your time.17:38
apwflexiondotorg, thanks for paying attention to it :)17:38
flexiondotorgapw, I'll report back to cjwatson and he can make the blacklist change.17:38
flexiondotorgapw, Most welcome :)17:39
apwack, thanks17:39
=== megabrutal is now known as MegaBrutal
bubba2I'd like to test a recent mainline bugfix that was "queued for 4.0".  Someone on the launchpad bug page said "no longer affects: linux-lts-vivid".  Can someone explain what that means?22:13
bubba2The lts and vivid part confuses me.  I'm on 14.04.2 - can I install that kernel build?  Or do I go to 15.04 vivid and install it (why the lts)?22:14
bubba2This is the issue: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1414930?comments=all22:15
ubot5Ubuntu bug 1414930 in HWE Next "[Lenovo ThinkPad X1 Carbon 20BT] Buttons of Synaptics trackpad doesn't work" [Medium,In progress]22:15
bubba2Is this more of a dev chat?22:58
bubba2squirrel23:37

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