[08:01]  * apw yawns
[09:01] <psivaa> apw: Updated bug #1195710 with some more information, not sure it will help. Have time to look into it?
[09:01] <ubot2`> Launchpad bug 1195710 in linux (Ubuntu Saucy) "'Kernel bug - invalid opcode: 0000 [#1] SMP' is reported at 'Preparing linux-image-extra-3.10.0-0-generic' stage of multi-lvm installations of amd64 saucy server " [High,Confirmed] https://launchpad.net/bugs/1195710
[09:03] <apw> psivaa, oh hmmm, increasing memory helped ...
[09:04] <apw> psivaa, as neither smb nor I could reproduce it, but 1G is my default size
[09:04]  * ppisati -> reboot
[09:05] <psivaa> apw: isn't 512 the minimum allowed for server?
[09:09] <apw> psivaa, oh quite probabally, i just mean the default in the box when i make new instances
[09:09] <smb> By default I use 1G but I probably have done 512 as well
[09:09] <smb> Cannot remember right now
[09:09] <apw> is 1G and that sems 'small' and therefore wasn't going to hit it ... doh
[09:17] <apw> /srv/images192.0.2.0/24(ro,sync,no_subtree_check)
[09:17] <apw> /srv/images 192.0.2.0/24(ro,sync,no_subtree_check)
[09:33] <apw> Error creating pool: Could not start storage pool: cannot open path '/var/lib/libvirt/images/iso': Permission denied
[09:39] <psivaa> apw: is this one of the utah errors in trying to reproduce the above bug?
[09:45] <apw> psivaa, oh no, this is me trying to export some images so i can start some new vms with less ram
[09:45] <apw> psivaa, i am chatting with smb about how retarded libvirt is and how much i would like to meet its mother
[09:46] <psivaa> apw: ack :)
[09:47] <apw> (with and axe)
[10:22] <apw> psivaa, do you have the whole preseed you are using for this install ?
[10:26] <psivaa> apw: it's here: http://bazaar.launchpad.net/~ubuntu-server-dev/ubuntu-test-cases/server-tests-raring/view/head:/preseeds/multi-lvm.preseed 
[10:27] <psivaa> attached to the bug as a file as well now
[10:27] <apw> psivaa, brilliant ..
[10:43] <apw> smb, ok so using the preseed manually is pretty easy, just change the kernel command line and remove the file=fooo.preseed and replace it with like url=http://192..../foo.preseed
[10:49] <apw> psivaa, ok with that i was able to repro this, i think ... thanks
[10:50] <psivaa> apw: ack, thank you
[10:51] <apw> psivaa, will see what i can find
[11:03] <apw> psivaa, ok yeah made it do it twice, seems to happen later without utah, utah must be consuming a chunk of memory i recon
[11:05] <psivaa> apw: that's probable. I always used utah. the client logs are saved in there before retrieving to the server
[12:09]  * ppisati -> out for lunch
[12:14]  * henrix follows ppisati
[13:16] <jjohansen> rtg: so I have a branch with the aa3 sync against pure upstream 3.11, so it doesn't have the ubuntu configs as part of it. Do you want a pull request using this or do you want to point me to your 3.11 rebase?
[13:19] <rtg> jjohansen, a pull request agsint the saucy unstable branch would be nice
[13:20] <jjohansen> rtg: ah, got it. I'll have that for you in a few minutes
[13:20] <rtg> jjohansen, no rush. we won't transition to 3.11 until about rc3 or 4
[13:21] <jjohansen> rtg: ack
[13:25] <jjohansen> rtg: okay, I've pushed it to my saucy tree on zinc, I'll do some build testing etc, before sending out the request
[13:25] <rtg> jjohansen, ack
[13:27] <FernandoMiguel> howdy
[13:27] <FernandoMiguel> ever since kernel  3.9.0-7, I haven't managed to get a proper CPU scheduler management 
[13:27] <FernandoMiguel> 3.10 only offers two states
[13:27] <FernandoMiguel> and seems to use much more battery
[13:41] <rtg> sforshee, re: bug #1190225. Is that in drivers/power/smb347-charger.c ?
[13:41] <ubot2`> Launchpad bug 1190225 in linux-grouper (Ubuntu) "opening /sys/devices/platform/tegra-i2c.4/i2c-4/4-006a/reg_status (as user) causes immediate reboot" [Undecided,New] https://launchpad.net/bugs/1190225
[13:49] <Sarvatt> FernandoMiguel: update again, i think that was fixed a few weeks ago?
[13:50] <FernandoMiguel> Sarvatt: every kernel I get, I boot into it, and all are the same
[13:50] <Sarvatt> or boot with intel_pstate=disable
[13:52] <sforshee> rtg: looking
[13:52] <rtg> sforshee, I'm pretty sure that it
[13:53] <rtg> root@ubuntu-phablet:/# dmesg|grep charger
[13:53] <rtg> [    2.096531] smb347_charger: [smb347_init] project_id=0, pcba_ver=3, dock_in_gpio=164
[13:53] <rtg> [    2.098920] [charger] Disable AICL, retval=93 setting=83
[13:53] <rtg> [    2.099397] [charger] set cahrger limmit, limit=900 retval =73 setting=73
[13:53] <rtg> [    2.099802] [charger] re-enable AICL, setting=93
[13:53] <rtg> [    2.627268] smb347_charger: [cable_type_detect] Reg39 : 0x10
[13:53] <rtg> [    2.627539] smb347_charger: [cable_type_detect] Reg3F : 0xc0
[13:53] <rtg> [    2.627681] smb347_charger: [cable_type_detect] USB_IN
[13:53] <rtg> [    2.627949] smb347_charger: [cable_type_detect] Reg3E : 0x0c
[13:53] <Sarvatt> apw: didn't you make that default to off? i'm not seeing it in the changelog
[13:53] <apw> Sarvatt, yeah that was disabled in the 3.9 kernel, the rumours were that 3.10 was 'better'
[13:54] <rtg> Sarvatt, also NO_HZ_FULL=n
[13:54] <apw> Sarvatt, so it wasn't switched there, on the assumption we would never ever test it there
[13:54] <apw> Sarvatt, unless it was on, ... are we seeing issues now we are in 3.10
[13:54] <Sarvatt> oh 3.10 made it start working on ivybridge too and it was bad here once that kicked in
[13:54] <apw> Sarvatt, so still shit in 3.10 yes
[13:54] <Sarvatt> yeah, 15C higher idle even in power save mode :(
[13:54] <apw> if so i can pull that change up to there, and leave it off in 3.11 which rtg is managing
[13:55] <apw> Sarvatt, well i call that tested in the negative ... 
[13:56] <FernandoMiguel> Sarvatt: what will that parameter do ?
[13:56] <sforshee> rtg: looks like it is smb347-charger
[13:56] <apw> Sarvatt, what the heck was the bug number
[13:56] <rtg> sforshee, yep
[13:56] <FernandoMiguel> apw: so it's a known bug/limitation ?
[13:56] <Sarvatt> i think they expect you to use that intel thermal management daemon to control fans if you use intel_pstate (https://01.org/linux-thermal-daemon)
[13:57] <FernandoMiguel> cause with 40ºc here, I can't just leave it in 3.10 Power Save ... it will kill kittens
[13:57] <apw> pstate_idle being pants, it is 'known of' in 3.9, and now 3.10 yeah
[13:57] <apw> FernandoMiguel, sounds fun indeed
[13:57] <FernandoMiguel> apw: it works fine in 3.9.0.7
[13:57] <apw> FernandoMiguel, and pstate_idle=off or whatever Sarvatt said it was, did the trick for you
[13:57] <FernandoMiguel> and all before that
[13:57] <apw> FernandoMiguel, well it was
[13:57] <FernandoMiguel> the few after and 3.10 broke 
[13:58] <apw> FernandoMiguel, well it was not enabled for some your kit at all in 3.9 
[13:58] <FernandoMiguel> there was a 3.10.1 that worked too. but broke again on .2
[13:59] <FernandoMiguel> so the advice is to pass a kernel option for 3.10 till this is improved, correct?
[13:59] <FernandoMiguel> any bug # I can track?
[13:59] <Sarvatt> hmm its not on https://bugs.launchpad.net/~adconrad/+reportedbugs so it must have been closed
[13:59] <Sarvatt> FernandoMiguel: still trying to find it..
[14:00] <FernandoMiguel> thanks
[14:00] <apw> Sarvatt, found it ... bug #1188647
[14:00] <ubot2`> Launchpad bug 1188647 in linux (Ubuntu) "Please change intel_pstate default to disable" [High,Fix released] https://launchpad.net/bugs/1188647
[14:00] <FernandoMiguel> GRUB_CMDLINE_LINUX="intel_pstate=disable"
[14:00] <FernandoMiguel> how will this affect 3.9.x kernels?
[14:01] <FernandoMiguel> thanks guys!
[14:02] <apw> FernandoMiguel, if you arn't using there they won't notice it
[14:02] <FernandoMiguel> apw: the bug is fix released, but it's not fixed in 3.10.x
[14:02] <apw> rtg, i have pulled that pstate_idle change up to master-next, but _not_ applied it to unstable as per discussion above
[14:02] <apw> FernandoMiguel, reload the bug
[14:03] <FernandoMiguel> ah :9
[14:03] <sforshee> rtg: the offending function is smb347_reg_show. One thing that is obvious is that it's reading more data than what its buffers are sized for.
[14:03] <FernandoMiguel> apw: need any info on my system to help triage it ?
[14:03] <apw> FernandoMiguel, the fix was deliberatly applied and releasd against the v3.9 kernel but not applied to unstable (v3.10 based) at the time
[14:04] <apw> FernandoMiguel, nope, i have turned it off, we suspected it was not ready for mainstream in v3.10 and your confirmation that is sucks is sufficient for me to just disable it pending it getting less crap
[14:04] <rtg> apw, so 3.11 should work better ? 
[14:04] <apw> rtg, i think the bigger question is "is v3.11 any better", for v3.10 we left it not applied in unstable so we would find out, i am proposing the same for v3.11
[14:04] <FernandoMiguel> apw: how many users actually even change schedulers, like I do ?
[14:05] <apw> rtg, as infinity as an avid user of affected kit we find out pretty smartly if it is utter crap
[14:05] <rtg> apw, ack.
[14:05] <apw> FernandoMiguel, heh dunno, but this is a default change so anyone with the kit is getting it by default
[14:05] <apw> it is new and shiney and meant to give you yet more performance for less power consumption
[14:05] <apw> which it clearly fails dismally to do
[14:06] <FernandoMiguel> on battery, it sure changes a lot 
[14:06] <FernandoMiguel> I've gonne from 5h+  to 2h
[14:06] <sforshee> rtg: that function has so many things wrong with it
[14:06] <FernandoMiguel> and that's ondemand
[14:06] <rtg> sforshee, off by one everywhere
[14:06] <FernandoMiguel> now I need to track down unity folks.... unity service is hogging a core.... :\
[14:06] <apw> FernandoMiguel, heh only one, you are lucky
[14:06] <FernandoMiguel> bye! if you need any update or testing, I'm subbed to the bug and can be found on #+1
[14:07] <rtg> sforshee, do you suppose it _ever_ worked ?
[14:07] <sforshee> rtg: I doubt it
[14:07] <FernandoMiguel> apw: $ killall -9 unity-panel-service 
[14:07] <FernandoMiguel> that's how I've been surviving 
[14:07] <FernandoMiguel> everytime I hear the fans go crazy
[14:07] <rtg> sforshee, well, I'm gonna hack on it to see if I can get it to stop faulting
[14:08] <sforshee> rtg: I added a comment to the bug, definitely looks like stack corruption
[14:08] <rtg> sforshee, agreed
[14:10] <apw> FernandoMiguel, hopefully the peeps on #ubuntu-unity have it covered
[14:10] <FernandoMiguel> thanks
[14:52] <jsalisbury> **
[14:52] <jsalisbury> ** Ubuntu Kernel Team Meeting - Today @ 17:00 UTC - #ubuntu-meeting
[14:52] <jsalisbury> **
[15:13] <Quintasan> Hi, I've recently discovered that my system stopped reading blanks DVDs. Since I didn't want to open up a new bug without any searching I did some digging around and last time anyone had a problem with it was Lucid. I did check the disk itself on another PC and it's blank for sure. I also did check it on Windows, blank there too. Output of `sudo /lib/udev/cdrom_id --debug /dev/sr0` is  http://paste.ubuntu.com/5858658/ and output of `sudo 
[15:13] <Quintasan> strace -vvfo /tmp/cdrom_id_new.trace -s 1024 /lib/udev/cdrom_id --debug /dev/sr0` is http://paste.ubuntu.com/5858660 . The bug I found was bug #561585
[15:13] <ubot2`> Launchpad bug 561585 in udev (Ubuntu Lucid) "Blank cd/dvd not recognized [LUCID] " [High,Fix released] https://launchpad.net/bugs/561585
[16:16] <rtg> jdstrand, I'll have a look
[16:16] <jdstrand> rtg: thanks! :)
[16:18] <rtg> jdstrand, hmm, I would have expected all netfilter options to have been enabled. I'll look closer.
[16:21] <jdstrand> yeah
[16:21] <rtg> its not like the LOG target is new
[16:22] <Sarvatt> apw: so I'm on 3.10.0-0 that has # CONFIG_NO_HZ_IDLE is not set CONFIG_NO_HZ_FULL=y, i'll verify intel_pstate is still crazy on -2 now
[16:23] <apw> rtg, grouper was missing a few last i looked, that was one of the patches i did, out of date now of course
[16:23] <Sarvatt> ah 3.10.0-2 still has that combo, someone responded on https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1188647/comments/6
[16:23] <ubot2`> Ubuntu bug 1188647 in linux (Ubuntu) "Please change intel_pstate default to disable" [High,Fix committed]
[16:25] <rtg> apw, I thought I normalized all netfilter config options. 'UBUNTU: [Config] Enable and modularize all netfilter matches'
[16:26] <rtg> jdstrand, CONFIG_NETFILTER_XT_TARGET_NFLOG=y for mako
[16:28] <apw> rtg, ahh so you did
[16:28] <jdstrand> rtg: [    0.000000] Linux version 3.4.0-3-mako (buildd@tritons) (gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-5ubuntu2) ) #13-Ubuntu SMP PREEMPT Tue Jun 25 17:07:54 UTC 2013
[16:28] <jdstrand> rtg: is that too old? ^
[16:29] <rtg> jdstrand, nope, thats current
[16:29] <rtg> jdstrand, maybe I'm looking at the wrong option. 'CONFIG_IP_NF_TARGET_ULOG is not set'
[16:30] <jdstrand> this isn't ulog
[16:30] <Sarvatt> i'm building a kernel with CONFIG_NO_HZ_IDLE=y CONFIG_NO_HZ_FULL=n CONFIG_NO_HZ_FULL_ALL=n to test that guys theory
[16:30] <jdstrand> ufw doesn't support ulog. I was going to, then no one did it for ipv6 and said it was bad or something, and so I said forget it
[16:31] <jdstrand> rtg: my desktop generic kernel has:
[16:31] <jdstrand> CONFIG_NETFILTER_NETLINK_LOG=m
[16:31] <jdstrand> CONFIG_NETFILTER_XT_TARGET_LOG=m
[16:31] <jdstrand> CONFIG_NETFILTER_XT_TARGET_NFLOG=m
[16:31] <rtg> jdstrand, yeah, looks like I missed some
[16:31] <jdstrand> CONFIG_NETFILTER_XT_TARGET_LOG is what we want I'm quite sure
[16:31] <jdstrand> NFLOG is the successor for ULOG
[16:31] <rtg> jdstrand, 'This option adds a `LOG' target, which allows you to create rules...'
[16:31] <jdstrand> ok, cool
[16:43] <ogasawara> apw, rtg: bug 1196597, I've a one line patch to shove in for Saucy, I'll submit the SRU for Raring
[16:43] <ubot2`> Launchpad bug 1196597 in linux (Ubuntu Raring) "nic-modules udeb does not contain the qlcnic driver for Qlogic" [Medium,In progress] https://launchpad.net/bugs/1196597
[16:44] <rtg> ogasawara, ack
[16:44] <rtg> ogasawara, get it in both master-next and unstable for saucy
[16:44] <ogasawara> rtg: just want to make sure I won't mess anyone up if I shove this up
[16:44] <ogasawara> rtg: ack
[16:46] <apw> ogasawara, not touching anything here, shove away
[16:55] <jsalisbury> ##
[16:55] <jsalisbury> ## Kernel team meeting in 5 minutes
[16:55] <jsalisbury> ##
[17:15]  * ppisati -> gym
[17:34]  * rtg -> lunch
[18:25]  * henrix -> EOD
[19:24] <rtg> bjf, is there a Raring bug for 'UBUNTU: [Config] CONFIG_ARM_ERRATA_643719=y' ? Shall I do the same for saucy ?
[19:25] <bjf> rtg, i didn't create a bug. it was a FTBS fix :-(
[19:26] <rtg> huh
[19:26] <rtg> because of a stable update ?
[19:26] <bjf> rtg, yes
[19:26] <bjf> rtg, i forgot to run updateconfigs before submitting
[19:27] <bjf> rtg, i'd have to go look at where it came it
[19:27] <rtg> bjf, no big deal. I just wanna be sure saucy is consistent
[19:27] <bjf> ack
[19:31] <bjf> rtg, it came in the 3.8.13.4 upstream stable release  bug 1199100  "ARM: 7752/1: errata: LoUIS bit field in CLIDR register is incorrect"
[19:31] <ubot2`> Launchpad bug 1199100 in linux (Ubuntu Raring) "Raring update to 3.8.13.4 stable release" [Undecided,New] https://launchpad.net/bugs/1199100
[19:31] <bjf> just fyi
[19:31] <rtg> bjf, I've got it set in both saucy branches
[20:10]  * rtg -> EOD
[20:46] <hallyn_> apw: just fyi, that sigchld delivery weirdness?  I can't reproduce it in 3.2, 3.5 or 3.7.  (mind you what we found before was a usage bug, but fixing that in lxc didn't help - so it looks like i ws facing one kernel and one userspace bug)
[20:46] <hallyn_> hopefully i don't offend when i say that bisecting ubuntu kernels is something i like to avoid
[20:46] <apw> hallyn_, it is something we all like to avoid
[20:47] <hallyn_> "Bisecting: a merge base must be tested"
[20:48] <hallyn_> so i'm just sort of manually bisecting by Ubuntu-3.7.0-7.15 versions, then i'll try and do upstream git commit (when i can nail down a reasonable ubuntu-ified config)
[20:50] <hallyn_> actually i guess i must be just about there.  3.7..3.8 shouldn't require too much config wrangling
[21:06] <apw> hallyn_, sounds sane
[22:35] <xnox> so grouper kernel is old, such that avahi doesn't work out of the box, and needs it's parameters tweaked for kernels << 3.9.4 or something like that.
[22:36] <ohsix> what.
[22:37] <ohsix> since when does avahi have 'parameters', and since when does it do anything but very basic network access