/srv/irclogs.ubuntu.com/2012/12/04/#ubuntu-kernel.txt

infinityherton: Oh, you could do it too, sure. :)00:15
infinityherton: How often does shankbot poll the PPA?01:35
bjfinfinity, once an hr.02:16
infinitybjf: Thanks.02:18
infinitybjf: Hrm, I'm missing some subtle nuance then, cause linux/hardy has been built and published for well over an hour, but the bug has no promote-to-proposed confirmed.  Weird.02:49
infinitybjf: And it finally got around to it.  Maybe I'm just impatient.03:02
tyfif I am using the linux-generic-lts-quantal kernel in Precise, am I able to use any of the lbm-cw packages in the repository? are the kernel modules compiled specifically only for other kernel versions?03:17
Sarvatttyr: no you can't, are you using linux-backports-modules-cw-3.6-precise-generic? that's the only one newer than the lts backports kernel03:38
Sarvattthe lbm-cw packages are compiled against 3.2 kernel updates each time03:38
tyfso there's none that are compiled against kernel 3.5?03:51
* apw yawns08:50
=== henrix_ is now known as henrix
apwsmb, there is no good reason to not build the DM delay and flakey personalities is there?11:24
smbapw, Hm, don't think really. They become modules I suspect and then will only be used if someone actually builds a target with them. Which pretty much is another painful and manual process.11:27
apwsmb, that fits my thinking too, thanks11:27
smbtjaalton, Not sure how/where/what exactly to report but I noticed on my sdp that using the quantal X stack and kernel on Precise running from a SSD is booting pretty fast and comes up ok but when rebooting or shutting down I see a dialogue telling me the system would only run in low-graphics mode (and it definitely was not doing that)11:38
apwsmb, so you see a new X server with "you are in low graphics mode", doe that have to be acknowledged or does the reboot/shutdown complete11:39
tjaaltonsmb: I guess it's plymouth's fault11:39
smbapw, It does go on but if you are quick you could confirm the first screen11:39
apwsmb, and do you get the 'dots' if you confirm it ?11:40
tjaaltonit has some hardcoded checks for 'i915'..11:40
smbapw, No, I get the second dialogue asking me what "other" config to use. And I was not quick enough to click before that was shot down11:40
apwsmb, ok :)11:41
smbtjaalton, We had been wondering whether X may go away too quickly because other people with that combo but slower disks do not see that11:42
smbtjaalton, Or I did something wrong when pulling the new stacks...11:42
apwsmb, i think file a bug against plymouth and see what happens11:43
apwsmb, and mention it to slangasek11:43
* smb thinks what happens will be a response saying "you are running crack"11:43
smbBut anyway, I will try11:44
apwsmb, it is going to be a supported combination ...11:44
tjaaltonright, and I haven't seen that bug with quantal11:45
tjaaltonthough I sometimes get the same dialog when it boots up11:45
apwsmb, any idea whether it makes sense to have CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES turned on11:48
smbapw, Err, not really have an idea what that would be...11:49
smbapw, Sounds very useful for crashing your system when unaware but interesting create unusual setups...11:53
apwsmb, yeah, i think as it is on i will leave it alone ... even if it is a bit scarey11:58
smbapw, True and probably there are more evil things that you can do when you can modify the kernel command-line...12:00
=== psivaa is now known as psivaa_lunch
smbslangasek, tjaalton I filed bug 1086345 for the x-lts-quantal oddity I see. If there is more I should do, please let me know12:07
ubot2Launchpad bug 1086345 in plymouth (Ubuntu) "Quantal-LTS-stack: Showing low-resolution screen on shutdown/reboot" [Undecided,New] https://launchpad.net/bugs/108634512:07
apwcking, i assume we have SLUB_DEBUG turned on for a reason ... 12:19
ckingapw, hrm, can't recall exactly when we enabled that12:20
rtgapw, ogasawara: pushed -rc8. build testing.12:21
ckingapw I would be more concerned if SLUB_DEBUG_ON was enabled, that turns it on by default12:23
apwcking, SLUB_DEBUG on, i believe _ON is off12:24
ckingapw, if we are concerned about the performance penalty of SLUB_DEBUG I can look at that12:25
apwcking, i was more interested to know it was a concious decision12:25
ckingapw, it wasn't a conscious decision that I can recall12:26
apwthen ... low low on your list, perhaps test it12:26
ckingapw, if it's not on for previous releases we should disable it for the moment I reckon12:27
hertoncking, apw, I believe it has been always enabled on our config (SLUB_DEBUG), it's helpful to debug some memory corruption cases passing slub_debug on commandline, like double frees, I recall it being useful once to me12:32
hertonbut not sure about the performance impact, if it has some then probably should be disabled12:32
ckingin which case, let me assess the overhead, if its is unnoticeable then it's a useful to have feature12:32
apwcking, herton, works for me12:33
xnoxwhat is the procedure to get an account on kernel.ubuntu.com ?12:34
rtgxnox, beg #is via an RT ticket.12:38
xnoxrtg: sounds like a good plan =)12:39
xnoxthanks.12:39
hertonrtg, that commit you mentioned yesterday (bc78c57), do you saw a problem it fixes? I can forward to stable12:50
rtgherton, no specific problem. I was looking at backporting TRIM support for md arrays and noticed that its likely a good bug fix.12:53
hertonrtg, ok, will ask for inclusion12:53
=== psivaa_lunch is now known as psivaa
* henrix -> lunch13:06
* apw wanders out to get some fresh air13:14
Konstigtis there any ppa with 3.7 for 12.10? or are rarings kernels OK on 12.10 perhaps?13:24
tjaaltonsmb: thanks, subscribed13:25
=== yofel_ is now known as yofel
rtgKonstigt, there are raring kernels for 12.04 at https://launchpad.net/~ubuntu-x-swat/+archive/r-lts-backport13:36
ogasawarartg: I was thinking we should upload today.  lemme know if your test build was successful and I can test on some kit here and then prep the upload.13:37
rtgogasawara, I've got x86en built on tangerine. lemme stash it on zinc in a sec and I'll give you an URL13:41
henrixkees: i'm getting a build error on arm platforms for precise regarding your "seccomp: forcing auditing of kill condition" commit13:42
henrixkees: https://pastebin.canonical.com/79684/13:42
henrixkees: any suggestion?13:42
rtghenrix, you might be a bit early in the day for him13:43
henrixrtg: ah, right :)13:43
rtgogasawara, cking, apw: http://kernel.ubuntu.com/~rtg/3.7-rc8.1/13:44
ogasawarartg: ack13:44
ckingrtg, want me to exercise this on a bunch of machines?13:44
rtgcking, please13:45
* cking rummages around for some H/W13:45
henrixdoes anyone know the rational for not having CONFIG_AUDITSYSCALL on arm configs?13:57
henrixi believe this is what is causing the build failure13:57
rtgppisati, ^^13:57
ppisatihenrix: hold on13:58
henrixppisati: thanks13:58
ppisatihenrix: config AUDITSYSCALL bool "Enable system-call auditing support" depends on AUDIT && (X86 || PPC || S390 || IA64 || UML || SPARC64 || SUPERH)14:01
ppisatihenrix: ARM was not supported back then14:02
henrixppisati: heh, ok. i should have checked that myself :)14:02
henrixppisati: thanks.14:02
ckingrtg, kernel seems good on atom n450, ivybridge + sandybridge H/W, will exercise it on some AMD kit now14:24
rtgcking, ack. thanks14:26
rtgogasawara, cking,apw: I'm gonna have to respin Raring with arges ticket_spinlock (fsnotify) patches.15:02
ckingrtg, tested on a bunch of older kit too (AMD, etc) works fine, boots, S3, S4, audio, network15:02
ckingah, more to test :-)15:02
ogasawarartg: ack15:02
ogasawarartg: previous build tested fine on my kit here15:02
apwrtg ack15:03
rtgcking, yeah, the ticket_spinlock tests might require more manula USB plugging, etc15:03
ckingack15:03
argesrtg, there is a script that reproduces the issue easily. I've tested this set of patches with that but would like to do more testing15:03
argesrtg,  cking : in addition do some performance tests if we can.15:04
ckingarges, such as?15:04
argescking, not really sure : ) have to think of something fs notify related15:04
janimortg, I am removing the ubuntu nexus tree from its former location in hwe/ , no objections right?15:05
* janimo goes to update the wiki as well15:05
rtgjanimo, go ahead15:07
apwarges, the point is that fsnotify is in the way of _all_ operations if its enabled15:13
apwarges, so if you ask for "read/write" notification for instance15:13
apwwhich isn't common but is possible15:13
argesapw, yea I think I can look at the test case, and try to write something15:15
argesapw, start time, inotify_add_watch , access file/directory, inotify_rm_watch15:15
apwyeah15:18
apwarges, with multiple read/writers in there15:18
rtgogasawara, cking, arges, apw: http://kernel.ubuntu.com/~rtg/3.7-rc8.2/ for the fanotify version15:32
argesrtg, downloading15:32
ogasawarartg: ack15:32
ppisatibrb15:34
* rtg relocates...15:36
Konstigtrtg: thanks but I have 12.10/Quantal15:42
rtgKonstigt, you can still install the kernel debs from either archive, but you won't get automagic updates via meta packages.15:43
* ogasawara back in 2015:48
Konstigtrtg: aha, so the kernel isn't really bound to the release and vice versa. so then just downloading the needed files from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7-rc8-raring/ should work.15:49
rtgKonstigt, yep15:49
rtgthe 'raring' part simply means that it was built using the raring config. I think all mainline are built using the Precise toolchain.15:50
apwthey are built using the previous LTS' tool chain15:50
rtgso, either Lucid or precise15:50
apwyes15:50
Konstigtthanks15:51
apw(in theory it would also use hardy, but ... i don't think we every make things that old)15:51
jsalisbury**15:52
jsalisbury** Ubuntu Kernel Team Meeting - Today @ 17:00 UTC - #ubuntu-meeting15:52
jsalisbury**15:52
apwits tuesday _again_ ?15:52
jsalisburyheh15:53
smbapw, Its _that_ late again, too15:53
apwseemingly indeed15:53
jsalisburybjf, smb, it looks like bug 1034099 is due to commit ffaf6a1e73719e0250fce7b52015187180a77fe9 15:55
ubot2Launchpad bug 1034099 in linux (Ubuntu Quantal) "Kernel panic with ulatencyd on kernel 3.2.0-29-generic" [High,In progress] https://launchpad.net/bugs/103409915:55
smbjsalisbury, Yeah, somehow I stopped worrying when I saw that...15:55
jsalisburysmb, is that commit something we can revert ?  If so, I can submit an SRU request.15:57
smbjsalisbury, Gosh I should read better (commit != comment)...15:58
jsalisburysmb, its this SAUCE:15:58
jsalisburycommit ffaf6a1e73719e0250fce7b52015187180a77fe915:58
jsalisburyAuthor: Stefan Bader <stefan.bader@canonical.com>15:58
jsalisburyDate:   Tue Jul 3 15:01:58 2012 +020015:58
jsalisbury    UBUNTU: SAUCE: sched: Fix race in task_group()15:58
smbOh f**k, I would not want that reverted but there was something messed up by it and I really cannot say right now what exactly it was16:00
ckingrtg, that kernel works OK on a bunch of laptops, atom, sandybridge, ivybridge, amd64.  however my sharkbay desktop gets video corruption and seems to lock up (tried it now 4 times)16:00
rtgcking, does the kernel in .1 have teh same issue ?16:01
ckingrtg, yep16:01
rtgcking, ok, so at least it wasn't introduced by the fanotify patches16:01
ckingI didn't get around to test it until just now 'cos I was exercising it on a bunch of other tests16:01
bjfcking, sharkbay is haswell?16:02
rtgcking, does the sharkbay work with ogasawara's Oneiric haswell pile ?16:02
bjfcking, i don't think all of ogasawara's haswell patches are in raring16:02
jsalisburysmb, the bug affects precise and quantal.  I'll find out if it also affects raring.16:02
ogasawarartg: all the haswell patches I pulled won't land until 3.8 opens16:02
ckingbjf yes, rtg no, but it used to work on earlier raring kernels16:03
bjfhuh16:03
rtgindeed, huh.16:03
rtgI'm gonna ignore it for now16:03
ckingsorry, that was not clear16:03
ckingno, as in I never sucessfully tested this box last week, so no, I am not sure, but it was booting fine on earlier 3.7 kernels16:04
smbjsalisbury, I thought I had someone with a boot oops because of that and thought at that point some additional upstream change was found... 16:04
* cking wonders if this is going to be the last -rc for 3.716:05
rtgcking, mebbe16:06
smbjsalisbury, Do we have this one pulled: commit fd8ef11730f1d03d5d6555aa53126e9e34f52f1216:06
smbAuthor: Mike Galbraith <efault@gmx.de>16:06
smbDate:   Mon Dec 3 06:25:25 2012 +010016:06
smb    Revert "sched, autogroup: Stop going ahead if autogroup is disabled"16:06
smb... stupid question as that was in the precise tree..16:07
bjfsmb, nope16:07
smbHm, ok seems something from 3.7-rc8...16:12
smbjsalisbury, So can we instead try the other revert which should be queued for stable afaics16:14
* smb curses and rushes over to the other irc meeting16:15
jsalisburysmb, so put your patch back and then apply fd8ef11730f1d03d5d6555aa53126e9e34f52f1216:17
smbjsalisbury, Yeah, which reverts the other thing actually16:17
jsalisburysmb, got it.  thanks16:17
jsalisburysmb, I ran into an issue when cherry-picking commit: fd8ef11730f1d03d5d6555aa53126e9e34f52f1216:24
jsalisburysmb, git diff says:16:24
jsalisbury* Unmerged path kernel/sched/auto_group.c16:24
jsalisbury* Unmerged path kernel/sched/auto_group.h16:24
jsalisburysmb, I can manually revert commit 800d4d3 without an issue16:25
rtgjsalisbury, clean your tree first ?16:25
jsalisburyrtg, I did a fresh clone16:25
jsalisburyof the precise tree on tangerine16:25
smbjsalisbury, Oh well, could be because Peter was bored and renamed most of the files about 3.516:25
smbso things moved from kernel into kernel/sched16:26
jsalisburysmb, ahh.  Can I just do the revert of commit 800d4d3 myself, and have that tested?16:27
jsalisburysmb, Or I can just fix things up after the cherry pick16:27
smbwonder whether the lazy fixup of git format-patch <revert>, git am <upstream> -> fail , patch < <export> works16:27
smbjsalisbury, just reverting the change would work as well for testing. Mainly its to have the upstream changelog (but that could be done later)16:29
jsalisburysmb, ack16:29
apwrtg, remind me the nature of the USB_OTG badness when enabled on x8616:34
rtgapw, I think its because there _isn't_ an OTG on x86 platforms.16:39
infinityOh hey, do I get to drop my UAPI hacks from glibc after the next linux upload?  Did that land?16:41
rtgapw, this must be for you? ^^16:42
infinityEither of you. :P16:42
infinityrtg: I expect you to know every line of the every kernel rc.  Sheesh.16:42
apwUAPI: strip the _UAPI prefix from header guards during header installation16:45
apwinfinity, thats what you are hoping for i believe 16:45
apwv3.7-rc8~27^2~616:46
apwwhich is in ^^ .... ie in -rc8 and our next upload16:46
infinityapw: That'd be the one.16:46
smbbjf, sconklin <arosales> smb: is kernel team going to be using UTAH in their testing?  (perhaps smb can provide some more context)16:47
ogasawarartg: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/108464016:48
ubot2Launchpad bug 1084640 in linux (Ubuntu Raring) "linux: 3.7.0-5.13 -proposed tracker" [Medium,In progress]16:48
ogasawarartg: in the future, you'd just run create-tracking-bug or whatever it's called and it'll shove the changelog entry for you16:48
sconklinsmb: not in our team testing environment for the foreseeable future. the QA team does theirs differently, and may use it for their kernel tests16:50
apwsconklin, i thought we had like a shim between utah and our tests so we use the same tests in both environments; right?16:50
apw(but not using it indeed)16:51
sconklinapw: the same tests can be run in both environments, all the kernel tests are under autotest client. Different ways of calling them are used in QU and out team16:52
bjfsmb, in a word, no16:52
smbbjf, Ok, I can pass this on next week. :)16:53
smbOr... hggdh ^16:53
bjfsmb, is there some feature of utah that would make me want to do so ?16:53
smbbjf, I am merely the messenger here. No personal interest really in doing one or the other16:53
bjfsmb, should i talkto arosales directly?16:53
smbbjf, Actually it was hggdh asking through arosales16:54
smbbjf, Or I ping you before the next server-team meeting to join the fun on irc. :)16:55
bjfwell, that's just damn odd16:55
bjfsmb, not sure i can handle that much fun .. but sure16:56
smbbjf, Maybe it brings a bit of the scary happy face back. :)16:57
bjflol16:57
rtgapw, both raring branches pushed. I'm just gonna wait to upload until my armhf test build is done.16:57
rtgabout 30 minutes I expect16:58
apwrtg, ack16:58
=== jsalisbury changed the topic of #ubuntu-kernel to: Home: https://wiki.ubuntu.com/Kernel/ || Ubuntu Kernel Team Meeting - Tues December 11th, 2012 - 17:00 UTC || If you have a question just ask, and do wait around for an answer!
* ppisati goes out for a bit17:18
hallynrtg: is raring master-next supposed to build right now?17:24
hallyn(from last night actually) 17:24
rtghallyn, yep. are you having issues ?17:24
rtghallyn, just pushed -rc8 this AM17:25
hallynyeah seemed to complain about a missing file,17:25
hallynok i'll merge that, thanks17:25
hallynfar prefereable anyway17:25
rtghallyn, hmm, I've been building it pretty regular17:25
hallynrtg: I got gcc: error: lib/oid_registry.c: No such file or directory17:26
rtghallyn, in a PPA, right ?17:26
rtgapw and I have encountered that same error. restarting the build makes it go away.17:27
hallynrtg: yeah ppa..  huh.  ok thanks :)17:28
apwhallyn, has to be a missing dep in the kernel makefiles somewhere17:36
rtgapw, the PPA's are -j1 aren't they ?17:37
* apw would have thought not, we check the number of CPUs don't we in the packaging17:38
rtgapw, ifeq ($(wildcard /CurrentlyBuilding),)....17:39
rtgoh, that has changed17:39
rtgapw, indeed, you are correct.17:40
apwrtg, am pretty sure you did that :)17:43
rtgapw, you're prolly right.17:43
apwrtg, actually that /CurrentlyBuilding is about whether we make udebs and the like, and i added that to speend up normal builds17:57
apwrtg, but its years old17:57
rtgapw, we _used_ to use it to determine parallelsim. it likely is still that way in hardy17:57
apwahh ... :)17:58
rtgapw, Iv'e been playing with parallel builds in lib, but can't get it to break.17:58
apwwierd17:58
apwi wonder if it is also used from outside of lib without deps17:58
apwthey do that kind of thing sometimes ... #include ../xxx/foo.c17:58
apwand the like17:58
rtgapw, perhaps during the headers install phase ?17:59
apwseems odd, but ...17:59
rtgapw, you'd think it would complain about not being able to find oid_registry_data.c (which is generated)18:00
apwi need to see a full log which has this in18:05
apwrtg/hallyn if you get one again do download the log before restarting it18:06
rtgapw, there isn't a lot of info in it18:06
apwi want to see the order things occured18:06
apwif you have one18:06
hallynapw: i haven't restarted the one so you can get the log from this morning,18:13
hallynapw: https://launchpadlibrarian.net/124867223/buildlog_ubuntu-raring-amd64.linux_3.7.0-5.13ubuntu1userns2_FAILEDTOBUILD.txt.gz18:14
apw$(obj)/oid_registry.c: $(obj)/oid_registry_data.c18:23
apwrtg, that is wrong isn't it ?18:23
apwnote the $(obj)/oid_registry.c ... that file is in $(src)/18:24
rtgapw, I was just trying to figure that out. gonna build with V=118:24
apwso i think that apparent dependancy is non-effective18:24
rtgapw, seems reasonable. why would it _ever_ work ?18:24
apwthey are likely started in the right order by luck18:25
apwso as long as we are doing things in the stack which take a while it will finish18:25
apwas the execution engine in make is limiting self to 10 builds or whatever18:25
apwyeah i think that line should be:18:26
apw$(src)/oid_registry.c: $(obj)/oid_registry_data.c18:26
apwand i think that should fix it, if you can reproduce it18:26
rtgyeah, just changed it. gonne give it awhirl18:26
rtgapw, well, it didn't break 'make M=lib -j'18:27
apwheh18:28
apwrtg, though i am slightly unsure if it should be $(obj)/oid_registry.o: in reality18:29
rtgthat actually makes more sense rule wise18:30
apwas you do not remake the oid_registry.c, it is the same, but you do remake the .o18:30
apwrtg, no18:31
apwrtg, the .c does depend on it, cause you need it made before the other .c is usable18:31
apwrtg, so .c is right18:31
rtgapw, I think either is correct18:32
* apw gets a headache18:32
apwyeah cause you write18:32
apwfoo.o: foo.c bar.h18:33
apwand that is what we are trying to write here18:33
apwyou don't write18:33
apwfoo.o: foo.c18:33
apwfoo.c: foo.h18:33
rtgapw, '$(obj)/oid_registry.o: $(obj)/oid_registry_data.c $(src)/oid_registry.c' ?18:34
apwthere is an implicit rule for the first oid_registry.c18:34
apwso you don't need that i don't believe18:34
apw$(obj)/oid_registry.o: $(obj)/oid_registry_data.c18:34
rtgapw, on;y if the rule is '::'. right ?18:34
apwthat sounds reasonable18:35
rtg$(obj)/oid_registry.o:: $(obj)/oid_registry_data.c18:35
rtgthat seems to work.18:36
apwrtg, there are no examples of :: in the kernel Makefiles, so i susspect they are avoiding them18:36
apwso if your '$(obj)/oid_registry.o: $(obj)/oid_registry_data.c $(src)/oid_registry.c' works i would use that18:36
hggdhbjf, smb: I have no problems with the kernel tests being out of UTAH. This was a question arosales asked me and smb18:36
rtgapw, maybe I'll have lunch first and then send something upstream.18:36
apwrtg ack18:36
* rtg -> lunch18:37
hallynrtg: apw: weird, I just fetched raring master-next, but it does not have 3.8...18:53
hallynrtg: the dev_change_net_namespace patch was just applied by dmiller to the netdev tree, fwiw18:56
apwhallyn, 3.8 ?  v3.7-rc8 you mean ?18:56
apwbjf, w18:59
apwbjf, am i reading this right that this week is prep week for SRUs ?18:59
bjfapw, saved18:59
bjfapw, yup!18:59
apwbjf, is slightly confusing because it is listed as the 'week of the 6th' ... thanks19:00
bjfapw, where do you see it? on the interlock schedule?19:00
apwyeah on the interlock schedule RR/ReleaseInterlock on the wiki19:01
hallynapw: oh, i misread then.  i was thinking it was going to be 3.819:01
hallynthanks19:01
hallynsilly me :)19:01
bjfapw, yes, that's because releases happen on thursdays so the calendar goes from thursday to thursday19:01
bjfapw, it was/is a release manager thing19:01
apwbjf, my head is made to hurt by it ... thanks19:03
apwbjf, is henrix on the hook for kernel prep this week ?19:09
henrixapw: i am19:09
bjfapw, yes, something in particular you are interested in?19:09
apwi may have something urgent for precise19:09
apwcan we spin that one last ?19:10
henrixapw: well, too late now :) but we can respin it if required19:10
henrixapw: do you have any idea about when you may have something? i can ping you on thursday about this19:13
apwhenrix, i hope to have it out for review in the AM, and should know the testing is confirmed (we have tested but waiting on the reporter) by EOD tommorrow i hope19:13
henrixapw: ok, cool. let me know about it.19:14
apwhenrix, will do, and thanks19:15
henrixnp19:15
apwhenrix, and do remember to ping me :/19:15
henrixapw: heh, i will19:15
apwogasawara, rtg, ok i have just pushed the first slab of 3.7 config review updates to raring19:22
rtgapw, ack19:22
apwit builds to udebs for me on x86 and armhf, ymmv19:22
ogasawaraapw: ack, thanks19:26
=== henrix is now known as henrix_
rtgapw, 'PATCH 3.7-rc8] lib/Makefile: Fix oid_registry build dependency' fired upstream19:56
apwrtg nice20:28
rtgapw, the double colon rule was wrong by the way.20:29
apwrtg, heh good to know20:34
apwwhat did you go with in the end20:35
rtgapw, just the simplest change, e.g., .o20:35
rtgpushed it to raring master-next20:35
apwahh great20:35
rtgapw, Howell introduced it in -rc1 with the signed modules patch set (I think)20:36
apwrtg hence it feels like a new issue20:36
rtgyep20:37
* rtg bugs out for the day20:41
* apw wanders off too20:47
apwBenC, i am doing some config cleanup work on master, i also have the equivalent in the works for PPC for once you are rebased to -5.  i'll get a pull request to you, so feel free to ignore the config fixes on master i'll do them22:46
BenCapw: rebased and uploaded on -5 already22:48
apwBenC, sweet, then i'll get the config fixes done tommorrow and out to you22:52
BenCapw: thanks23:08

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