/srv/irclogs.ubuntu.com/2016/03/04/#ubuntu-kernel.txt

DalekSecapw: Any luck looking at the new cryptsetup?  If it helps, I did a merge for myself end of last month.07:32
DalekSechttps://sigma.unit193.net/source/cryptsetup_1.7.1-0ubuntu1.dsc07:33
=== dgadomski_ is now known as dgadomski
tjaaltonapw: do you have initramfs-tools in git somewhere? bug 1500751 needs fixing08:59
ubot5bug 1500751 in initramfs-tools (Ubuntu) "Cryptsetup Keyboard not working on Xubuntu 3.19.0-30" [High,In progress] https://launchpad.net/bugs/150075108:59
tjaaltonthen again it's not out of proposed yet09:08
tjaaltonshould it still be blocked by https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1548120 ?09:12
ubot5Launchpad bug 1548120 in initramfs-tools (Ubuntu) "[xenial][initramfs-tools] support uppercase and lowercase uuids" [High,New]09:12
apwtjaalton, almost cirtainly not be blocked ... checking09:17
tjaaltonit broke something for ntfs mounts09:17
tjaaltonbut that was not the reason for the tag09:18
apwtjaalton, oh poo ... ok ... so that needs fixing too09:18
apwtjaalton, do you have a fix in hand for your problem, if so if you email it to me now09:18
tjaaltonI do09:18
apwtjaalton, i'll fix this uuid thing again, and apply yours at the same itme09:18
tjaaltonhttps://launchpadlibrarian.net/223637474/debdiff-vivid09:19
apw(as yes it is in git)09:19
apwtjaalton, thanks ...09:19
apwgrrr09:19
tjaaltonthis still works, sans changelog09:19
tjaaltonyeah this fell through the cracks, and now vivid is eol. trusty would need this too, but it's also still in proposed waiting for testing09:20
apwack09:20
xnoxah, i'm not the only one11:14
xnoxbug 1500751 =)11:14
ubot5bug 1500751 in initramfs-tools (Ubuntu) "Cryptsetup Keyboard not working on Xubuntu 3.19.0-30" [High,In progress] https://launchpad.net/bugs/150075111:14
xnoxi have this optimus things, with nvidia & intel graphics. Is there a known good way to force intel graphics only, in plymouth and elsewhere?11:16
xnoxmy input is all weird with latest kernel -> plymouth is shown, yet i "type" at top left corner, and not into "plymouth" as if plymouth doesn't have focus.11:16
apwtjaalton, ok ... i've applied your fix and what i hope is the fix for the other issue, and uploaded to ppa:apw/ubuntu/initramfs-tools-test11:37
apwxnox, plymouth not having focus iirc is often when plymouth has rejected all the graphics displays as non-primary11:38
apwso it doesn't open the terminal, so the underlying vt reads and echos11:38
xnoxack.11:38
xnoxapw, i'm suspecting the kernel/plymouth might have started to either use noveau instead of intel graphics, or noveaue graphics (with plymouth) got broken11:39
apwmanjo, it seems your UUID fix is blowing up NTFS installs, i've uploaded a "only apply this to rfc4122 format uuids" fix to ppa:apw/ubuntu/initramfs-tools-test, could you verify that still fixes youpls.11:40
xnoxi've blacklisted noveaue, purged noveaue xserver packages, booted without splash (to unlock the drive) and have desktop now (previously lightdm would work, unity/gnome-shell/plymouth crash/not-work)11:40
apwsounds like you are having fun, i don't know what wally thought switchable graphics was ever a good idea architecturally11:41
tjaaltonxnox: is this a skylake laptop?11:43
xnoxyes.11:43
tjaaltonso you need that new initramfs-tools11:43
apwxnox, ahh that should be in ppa:apw/ubuntu/initramfs-tools-test11:44
tjaaltonbecause otherwise initrd doesn't come with i915_bpo11:44
apwubuntu2~rc111:44
tjaaltonoh I missed the backlog11:44
tjaaltonso yeah11:44
apwtjaalton, oh i wasn't asking him to test it :)  i was just asking you and manjo :)11:44
apwif he can test too ... yay11:45
apwxnox, make sure you have an old kernel and initramfs :)11:45
xnoxapw, i'm using a spare machine =) that seems to work.11:45
apwthe initramfs-tools fixes you ?11:46
xnoxapw, did i hear that right, that i shall dist-upgrade and everything will work.11:46
xnoxapw, i've booted the laptop by hand, without splash and not shutting it down now =)11:46
apwwithout any risk of explosion, yes i definatly said that :)11:46
tjaaltonit might also unbreak your nouveau11:46
xnoxwheere can i get the magical ubuntu2~rc1?11:46
apwxnox, ahh that should be in ppa:apw/ubuntu/initramfs-tools-test11:46
apwubuntu6~rc111:46
xnoxi ponder to just cowboy in the hooks/framebuffer thing11:48
xnoxcause i don't want to enable that ppa, will forget about it.11:48
xnoxapw, the copy_modules_dir of ubuntu/i915 is kosher.11:53
apwxnox, as long as it fixes you :)12:05
apwxnox, i tend to enable the ppa, instlal the pckage, and then remove it immediatly12:05
apwi always version before the archive in there12:05
manjoapw, sure will do today12:57
apwmanjo, thanks ... hopefully that one will work for everyone and can actually go out12:57
manjoapw, thanks a ton .. will test do you have a bug number I can report back to ? 12:57
apwbug: #155310713:04
ubot5bug 1553107 in initramfs-tools (Ubuntu) "initramfs-tools: UUID checks now fail for NTFS which has upper cases UUIDS" [Critical,In progress] https://launchpad.net/bugs/155310713:04
apwmanjo, ^13:04
manjoapw, awesome .. we are in a critsit with one of our friends today.. but I will definitely find time to test that for you and report back in that bug 13:05
lamontapw: (or anyone) in trusty and later, which, if any, filesystems still report 1-second granularity timestamps?14:00
apwlamont, hmmm, fat perhaps14:03
apwthose kinds of places, not sure you'd keep dns things one one of those14:03
apwi'dbe slightly suspicious of samba mounts, and would suggest checking nfs14:03
lamontapw: let me reprhase that - places where even the most insane user/admin might put /etc14:03
apwbut ... they should all just return 0 in that14:03
apwthey should still return valid times in the calls which support ns numbers though right ?14:04
apwso ... do you care ?14:04
lamontfat is so broken in so many ways for that, making it not a consideration14:04
lamonthttps://bugs.launchpad.net/ubuntu/+source/bind9/+bug/155317614:05
ubot5Launchpad bug 1553176 in bind9 (Ubuntu) "BIND ignores nanoseconds field in timestamps, fails to load newer versions of zones on reload" [High,Confirmed]14:05
apwlamont, right but if you take them into account (the ns) tey should be valid and always 0 or something on older broken filesystems14:05
lamontand a related "maas does crazy things trying to work around 1-sec granularity" issue - I'm looking at "do I push to fix this in trusty, or not.14:05
lamontapw: true, making them either "still broken" or "fixed?"14:06
lamonts/?//14:06
lamontnewly-broken being the one I really want to avoid14:06
apwwell i think your contention that all sane underlying things would support <1s granularity14:06
apwi beleive if they are using something without, they already are broken, so makign it take ns into account won't make them any worse i odn't think14:07
lamontand no architecture where the patch in that bug would be bad?  (given that bind9 made it into xenial with that fix, it at least compiles, so nevermind that question14:07
lamontcogent argument.  thanks for the clarifying conversation14:07
apwdo bear in mind just because the FS reports ns timestamps in its stat info14:08
apwthat does not make the granulatity ns, it may well jump in multiple ms14:08
apwso i am not sure you can be confident of avoiding your issue if you keep updating the file at line speed14:08
apwlamont, ^14:09
smbline or light...14:09
apwall of the above :)  "very quickly" might be less than the fs granulairity regardless of the stat result maximum granularity14:09
apwthough it would be easy enough for maas to stat the file, update it, stat it again, if the timestamps match, touch it again until its not14:10
smbyeah, true indeed14:10
lamontoh, that's fine14:10
lamontwe take lots longer than that to acutally write the file14:10
apwand guarentee we never hit that issue14:10
apwor ... you could fix bind so when you ask it to reload, it does regardless of the timestamps14:10
apwbecause you know you asked it to14:11
lamonthttp://paste.ubuntu.com/15276110/ <-- from the headscratching yesterday finding the bug14:11
apwand it seems rude for it to say, naaa you are a tool the file is the same date i hate you14:11
apwall of the above :)  "very quickly" might be less than the fs granulairity regardless of the stat result maximum granularity14:11
apwdamn you paste14:11
smbapw, nah you cannot make "tools" useful... :-P14:11
apwlamont, it is actually unreasonable for bind9 to be sent an _explicit_ reload and for it to say "nope i know better"14:12
apwwhy would you send it a reload if you didn't want it to like actually reload14:12
lamontif you send it a bunch of reloads for 1 zone, there's no reason it can't combine them into one load14:13
lamontit's specifically code that was added to help named installs with thousands of zones survive the admin saying "rndc reload"14:14
lamontthe process goes: update zone file (atomically...), run rndc reload $ZONE, bind9 wakes up, processes zonefile, remembers when that happened14:16
lamontso there's definitely some lag between the zone getting written and bind9 serving new data14:16
lamontand yeah, milliseconds is fine14:17
apwlamont, so why is it not checking the inode and device numbers as well as the time14:18
lamontalso, I'm fine with adding code down the road that says "while (timestamp hasn't changed) {write the *(^)*&*& file;}"14:18
apwas to make an atomic update you necesarily need to change the file, ie the inode number on the device14:19
lamontbecause we hate veryone14:19
apwif bind9 did that, we'd avoid this completely14:19
lamonttrue.  that will go in the bug report to upstream14:19
lamontbut it's invasive enough of a change that I'd rather just go lalalalaalalala and ignore it for now14:20
apwsurely the bit which adds ns check is the identicle bit we'd want to keep the inode number, but hey14:22
smbapw, though then bind9 has bigger issues right now than to worry about timestamps14:23
smbor rather not bind9 but poor tools trying to use its libraries... :-P14:24
apwheh14:30
lamontsmb: adding back in the -export libs is inplan for this weekend (mgilbert is working on that, and worst case, I'll work on it early next week)15:00
* lamont has a flight to kill time on monday evening15:00
smblamont, Yeah, I know. And thanks for that.15:00
smblamont, Just seriously felt like needing a shower after having been up to my throat in user-space code... ;)15:03
apwsmb, :)15:14
lamontsmb: heh15:26
manjoapw, initramfs tools is in your test PPA correct ? 16:52
manjoapw, https://launchpad.net/~apw/+archive/ubuntu/initramfs-tools16:53
manjoapw, $ apt-cache policy initramfs-tools16:58
manjoinitramfs-tools:16:58
manjo  Installed: 0.122ubuntu5~rc216:58
manjo  Candidate: 0.122ubuntu5~rc216:58
manjo  Version table:16:58
manjo *** 0.122ubuntu5~rc2 10016:58
manjo        100 /var/lib/dpkg/status16:58
manjo     0.122ubuntu3 50016:58
manjo        500 http://ports.ubuntu.com/ubuntu-ports xenial/main arm64 Packages16:58
manjo     0.122ubuntu1~rc4 50016:58
manjo        500 http://ppa.launchpad.net/apw/initramfs-tools/ubuntu xenial/main arm64 Packages16:58
manjoapw, are you missing arm64 ? 16:58
cristian_c!paste16:59
ubot5For posting multi-line texts into the channel, please use http://paste.ubuntu.com | To post !screenshots use http://imgur.com/ !pastebinit to paste directly from command line | Make sure you give us the URL for your paste - see also the channel topic.16:59
manjoapw, or is it the version in proposed ? 0.122ubuntu5 50017:03
manjo        500 http://ports.ubuntu.com/ubuntu-ports xenial-proposed/main arm64 Packages17:03
manjoapw, it is no clear to me that proposed have any changes for NTFS .. can you please tell me which PPA / archive the new initramfs tools is in ?17:09
apwmanjo: i thpught i turned arm64 on on that ppa17:22
apwmanjo: oh initramfs-tool-test, note the -test17:22
manjoapw, it is working .. I will update the bug 17:31
manjoapw, testing upper case now 17:33
apwmanjo, great thanks17:37
manjoapw, wait .. upper case does not wrok17:37
apwhrm, what format is the thing, can you paste it for me17:39
manjoyes17:39
manjoI was going to update that bug ... but I can paste here17:40
apwta17:40
apwdo update the bug too pls17:40
* apw drumbs his fingers17:43
manjoroot=PARTUUID=7c5978e5-a56f-4c4c-a3f1-de1467d0b602 (lower case) works17:43
manjoroot=PARTUUID=7C5978E5-A56F-4C4C-A3F1-DE1467D0B602 (upper case) does not work.17:43
* manjo is sorry .. did not realize this would turn into such a cluster 17:44
apwmanjo, meh, we'll get there, i was over zelous applying it to everything, and underzelous applying it to anything now it seems :)17:45
apwmanjo, oh blech ... i see whats going on ... boo17:48
manjothing do with the 5 digits / 17:48
manjo? 17:48
apwmanjo, no just not thinking when writing the code, i was losing the DEV when checking it ... so i've just uploaded a ~rc2 ... should be built in about 20m17:54
manjook sure I can test that 17:54
manjoapw, drinking and typing on Friday evening ... s**t happens 17:56
apwmanjo, heh i did that this morning, so no excuses17:57
manjoapw, ☺ beer fixes sober coding errors .. works either way ..  17:58
apwheh i wish i was drinking, but i am not17:58
manjoapw, heh I hear ya .. I could use a strong drink right now ... s**t blowing up on my face all day17:59
=== decoder_ is now known as decoder

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