[08:15] <smb> morning
[08:17] <cooloney> smb and cking morning
[08:17] <cking> yay
[08:19] <smb> Another Friday morning which hopefully turns into a Friday evening soon. :)
[08:19] <cking> poor smb
[08:19]  * apw yawns ... morning
[08:19] <smb> cking, Oh, there is nothing specific. Just the usual lamment. :)
[08:19] <smb> apw, Welcome :)
[08:20] <apw> heh yeah, roll on beer-o-clock
[08:21] <cking> we need a time machine that's for sure
[08:24] <TeTeT> smb: the public bug for the WWAN module in the x201 is https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/592046, I've put it in the private bug description
[08:24] <ubot2> Launchpad bug 592046 in linux (Ubuntu) "Lenovo x201 WWAN module in Lucid kernel (affects: 1) (heat: 732)" [Undecided,Incomplete]
[08:25] <smb> TeTeT, Ok works for me
[08:25] <smb> So I like will look at that next week
[08:25] <TeTeT> smb: great :)
[08:58] <kraut> moin
[09:00] <apw> moin
=== cking_ is now known as cking
[11:23] <amitk> apw: know why the omap kernel does not have any information generated from the variables in vars.omap? https://edge.launchpad.net/ubuntu/+source/linux/2.6.35-4.5
[11:24] <apw> amitk, sorry what information is missing??
[11:24] <amitk> "No description available for linux-image-2.6.35-4-omap in ubuntu maverick"
[11:24] <amitk> but if you click on the kernel, it shows the info
[11:24] <amitk> (on the link above)
[11:25] <apw> amitk, could it just be recent
[11:27] <apw> amitk, can you check now, as it seems to have a description on that page for me
[11:29] <apw> amitk, oh you are saying on that link it has info, so where you seeing 'no informaiton' ?
[11:29] <amitk> apw: yeah, it's there now, was this a recent upload that just get populated into LP?
[11:29] <apw> yeah probababally only got though recently
[11:30] <amitk> apw: no, there was no info on the link 5 minutes ago
[11:30] <apw> i note sparc is still new
[11:30] <amitk> I guess that page is not generated atomically
[11:31] <apw> or it cannot get the inforamtion till the kernel is published by the publisher run
[11:33] <amitk> apw: care to apply this patch which cleans up the description a bit? http://paste.ubuntu.com/451547/
[11:37] <apw> amitk, maverick right?
[11:38] <amitk> yeah
[12:12] <apw> amitk, sent it out to leann
[12:24] <amitk> apw: thanks
[12:26] <apw> np
[13:36] <tseliot> mjg59: are you around?
[14:16] <tgardner> apw, did we ever bottom out on the minim CPU support in the toolchain?
[14:17] <tgardner> minimum*
[14:17] <apw> tgardner, its on robbie's radar to get the recommendations and write up sorted out
[14:18] <apw> i have only heard 'i686' from doko and 'i686 and cmov' from keybuk, neither on official channels.  so i'd say its still up in the air for s
[14:18] <apw> us
[14:18] <tgardner> apw, ok. I was just reading some internal reports about thin clients.
=== kentb_out is now known as kentb
[14:20] <mjg59> Note that building glibc for i686 will generate i686 and cmov and i686 nopl
[14:20] <tgardner> apw, on a diff topic, can you have a look at the maverick ti-omap4 branch to see if I got your commonized debian bits right. There was a bit of confusion over the location of the enforce file.
[14:20] <mjg59> Which kills Geode
[14:20] <mjg59> (even though it has cmov)
[14:20] <tgardner> Geode is 586, right?
[14:20] <apw> tgardner, the enforce file should be in debian.master as it is series common
[14:21] <tgardner> apw, then I have it in the wrong spot.
[14:21] <apw> tgardner,i suspect you have two then
[14:21] <mjg59> tgardner: No, Geode LX is 686
[14:22] <tgardner> apw, no, just one.
[14:22] <mjg59> (depending on your precise definition of 686)
[14:22] <apw> tgardner, hrm, then i'd expect updateconfigs and any build to fail if its in the wrong place
[14:22] <tgardner> mjg59, some of those low enbd CPUs are kinda funky, like VIA
[14:22] <tgardner> end*
[14:22] <mjg59> tgardner: Yeah, some of the VIAs lack cmov
[14:23] <mjg59> But the 686 family isn't very well defined
[14:23] <apw> tgardner, i think such a move is going to kill off my bastion host, as that via and doesn't seem to have cmov in /proc/cpuinfo
[14:23] <mjg59> cmov is the main reason to go 686
[14:23] <tseliot> mjg59: using my patch (to use ATIF) + acpi_osi="!Windows 2009" = keycode 227, my patch without acpi_osi = keycodes 25 28. This happens without X. Furthermore, If I use the keymap tool, I can see that hotkey events (scan code 0x00 key code: switchvideomode) come from /dev/input/event4 while events from other keys come from event3. 
[14:24] <mjg59> But gcc and binutils will potentially generate other 686 instructions as well
[14:24] <mjg59> tseliot: Ok, so that sounds like it works
[14:24] <tseliot> mjg59: in X, however, using xev, I still get Return, Return, Super_L
[14:24] <mjg59> tseliot: X may be grabbing something or other
[14:24] <tgardner> apw, well, I've uploaded the ti-omap4, so now you should come along behind me and put some whoop-ass on that branch, i.e., recreate the debian bits in your own image.
[14:25] <apw> tgardner, heh ok ... will have a look :)
[14:25] <tgardner> apw, I don't think its too far off
[14:26] <tseliot> mjg59: that's what I thought. Killing the gnome-settings-daemon doesn't seem to help though
[14:26] <apw> tgardner, yeah can't tell
[14:26] <tseliot> mjg59: furthermore I still can't get an event using "acpi_listen"
[14:27] <tseliot> with or without X
[14:29] <mjg59> tseliot: You won't if it's sending windows+p
[14:30] <mjg59> However, if you're seeing switchvideomode come from somewhere other than the normal keyboard device, it's working
[14:30] <tseliot> mjg59: yes, I guess that's the device created by the dell wmi module
[14:31] <mjg59> More likely it's the ACPI device
[14:33] <smb> apw, tgardner The SRU team noted today that there is a big number of bug reports which have fix-committed for Maverick. From my feeling there should not be really much not being released. But I am usually not looking at Maverick that closely.
[14:34] <apw> smb, i would expect there to be some stuff outstanding but not a whole heap
[14:34] <JFo> cking, i seem to be unable to join your firmware team
[14:34] <apw> do you have a list we can look at, so i can see if there is an issue or just they are outstanding
[14:34] <smb> https://bugs.edge.launchpad.net/~ubuntu-sru/+subscribedbugs?field.assignee=&field.bug_reporter=&field.has_no_package=&field.has_patch=&field.omit_dupes=on&field.searchtext=linux&field.status%3Alist=CONFIRMED&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INPROGRESS&field.status%3Alist=NEW&field.status%3Alist=TRIAGED&orderby=targetname&search=Sear
[14:34] <smb> ch&start=150
[14:34] <smb> Oh how useful
[14:35] <smb> Quite a few are sound bugs which probably use committed differently than we do
[14:35] <apw> dammit launchpad searching is just stupid
[14:36] <smb> Like  https://bugs.edge.launchpad.net/ubuntu/lucid/+source/linux/+bug/567494 for example
[14:36] <ubot2> Launchpad bug 567494 in linux (Ubuntu Maverick) (and 2 other projects) "Problem sound on Fujitsu Siemens Amilo XI 1526 (affects: 1) (heat: 10)" [Low,Fix committed]
[14:36] <cking> JFo, lemme subscribe you
[14:36] <JFo> thanks cking 
[14:37]  * JFo gathers bits to test
[14:37] <tgardner> smb, anything thats fix committed for Maverick ought to be fix released
[14:38] <apw> smb, i suspect those are getting lost because pitti shoved it over to the kernel package, so dtchen cannot see it anymore and it was he who was tracking it
[14:38] <smb> Right, so I probably goe over all of them and change commited to released
[14:39] <apw> well we need to check the commits are in
[14:39] <apw> like the one there is in so i'll fix released it
[14:39] <smb> ok
[14:40] <apw> apw@dm$ git merge-base 3353541fe533350a22a03e2fb7dc085b35912575 origin/master
[14:40] <apw> 3353541fe533350a22a03e2fb7dc085b35912575
[14:40] <apw> so that one at least is in
[14:40] <tgardner> apw, whats the name of the 'misc' blueprint? I need to drop the maverick LBM and ti-omap4 work items in it.
[14:40] <apw> kernel-maverick-misc
[14:41] <apw> https://blueprints.edge.launchpad.net/ubuntu/+spec/kernel-maverick-misc
[14:41] <apw> tgardner, ^^
[14:41] <tgardner> apw, my feeble memory thanks you
[14:41] <apw> tgardner, you can find all of the blueprints for lucid now from the wiki.ubuntu.com/Kernel
[14:41] <apw> follow 'releases' and there is a link under Lucid thre
[14:42] <tgardner> apw, man, you are _way_ too organized
[14:43] <apw> tgardner, thats a bit of me and a bit of ogasawara  ... there is a reason you let us do things :)
[14:46] <cwillu_at_work> ooo, drama on the btrfs mailing list :)
[14:46] <JFo> well that was fun
[14:47] <JFo> brb
[14:48] <tseliot> mjg59: if I press any other hot key (e.g. brightness keys, wlan) I get this in kern.log: "dell-wmi: Unknown key 0 pressed"
[14:48] <mjg59> That seems to be a dell-wmi bug
[14:49] <tseliot> ah a separate bug then
[14:49] <mjg59> Yeah
[14:54] <tseliot> ok
[14:58] <smb> apw https://bugs.edge.launchpad.net/~ubuntu-sru/+subscribedbugs?field.searchtext=linux
[15:13] <tgardner> cnd, ogasawara, lag, bouncing emerald for new kernel
[15:14] <lag> tgardner: oka
[15:14] <lag> y
[15:15] <lag> tgardner: Can you let me know when it's back please?
[15:15] <tgardner> lag, why would I know any sooner then you?
[15:16] <lag> tgardner: Oh, it's not with you is it?
[15:16] <lag> Are you bouncing right away?
[15:16] <tgardner> lag, nope, its in Virgina (or somewhere where I can't hear it)
[15:17] <lag> :)
[15:17] <tgardner> lag, bouncing tyler.mills as well
[15:17] <lag> Rubbish! I'm being shot from all angles! 
[15:18] <lag> Back
[15:18] <lag> ty
=== bjf[afk] is now known as bjf
[15:46] <JFo> moin bjf 
[15:47] <bjf> moin
[15:58] <tgardner> kees, is procps the right place to dump 'sysctl net.netfilter.nf_conntrack_acct=1' ? CONFIG_NF_CT_ACCT is being deprecated.
[16:05] <cking> morning bjf - thanks for the 2nd load of logs
[16:06] <bjf> cking, welcome, wish it was more
[16:06] <apw> smb, ok i've gotten a script together to find these maverick noms which are Fix Committed and yet have BugLink:'s ...
[16:06] <cking> bjf, no chance of getting any more then?
[16:07] <bjf> cking, working on it, there's more just having "issues" :-)
[16:07] <cking> bjf, no sweat, it's not urgent
[16:07] <bjf> cking, running into unicode breakage in odd places
[16:07] <smb> apw, Very nice. This will give us a lot of bonus points with the SRU team. :)
[16:08] <apw> though i don;'t know quite how many its going to close as yet
[16:08]  * cking wonders where the day has gone
[16:08] <smb> cking, Towards B o'c :)
[16:08] <cking> glug glug
[16:09] <apw> bah an hour here
[16:09] <smb> apw, Could be a few. I have been looking at least at one page listing
[16:09] <apw> smb, i am thinking that this will find like 10, more accurate numbers in a sec
[16:10] <smb> cool
[16:11] <apw> smb, 15 by the looks of it ...
[16:12] <smb> apw, Better than nothing. I guess after we got rid of those, we need to check on the remaining manually
[16:13] <apw> i suspect that is a fair chunk
=== kentb is now known as kentb_lunch
[17:19] <ogasawara> apw: http://people.canonical.com/~ogasawara/mark-fix-commited.py
[17:43] <ogasawara> apw: http://pastebin.ubuntu.com/451674/
[17:43] <ogasawara> apw: not exactly what you want, but it will return the task, nomination, and milestone
[17:44] <apw> ogasawara, thanks anyhow, i'll hit it harder till it squeeks
[18:21] <kees> tgardner: I need slightly more background.
[18:22] <kees> tgardner: (for net.netfilter.nf_conntrack_acct)
[18:22] <kees> tgardner: you're saying the CONFIG_ is being dropped, but the sysctl is staying, but the sysctl defaults to the opposite of what we've had?
[18:23] <kees> tgardner: why is the CONFIG_ being dropped?  it might live in /etc/sysctl.d/10-network-security.conf, but maybe iptables should ship a new /etc/sysctl.d file?
[18:23] <tgardner> kees, CONFIG_NF_CT_ACCT is getting deprecated in favor of a sysctl to set that behavior at runtime. I'm sending the deprecation patch, but the default behavior should remain the same.
[18:23] <kees> tgardner: why is it being deprecated?
[18:24] <tgardner> kees, I'm going to send an email to ubuntu-devel about this issue 'cause its sort of a general problem, e.g., setting syctl's provided by a module
[18:25] <tgardner> kees, I'm deprecating  CONFIG_NF_CT_ACCT because it prints some noise in the dmesg log
[18:25] <kees> tgardner: it's not being deprecated upstream?
[18:26] <tgardner> kees, its been marked for deprecation sinece before 2.6.29
[18:26] <kees> hah
[18:26] <tgardner> I'm just doing the patch to finally implement it
[18:26] <kees> okay, well, /etc/sysctl.d is the place to ship sysctl settings.  procps is responsible for activating them.
[18:27] <kees> procps itself ships some system-wide defaults.
[18:27] <kees> things like wine, dosemu, kvm-qemu-static-extras, etc ship files in there.
[18:27] <apw> smb, i am sure you are off by now, but i have just run that update and closed off a bunch of bugs ... hope that'll make pitti et al happier
[18:27] <tgardner> kees, but what happens when the module is not installed until after sysctl does its thing at startup?
[18:27] <smb> apw, I am still hanging around. :) And thanks
[18:28] <kees> tgardner: ew
[18:29] <kees> tgardner: sounds like you need a hook in /etc/modprobe.d instead
[18:29] <tgardner> kees, yeah, thats what I'm thinking.
[18:31] <kees> tgardner: ship a file that contains:    install conntrack-acct /sbin/modprobe --ignore-install conntrack-acct; sysctl net.netfilter.nf_conntrack_acct=1
[18:31] <kees> kind of hacky, but it'll work
[18:32] <tgardner> kees, as part of modprobe.d ?
[18:33] <kees> tgardner: as a file in /etc/modprobe.d/ yeah.  like ship it as  /etc/modprobe.d/conntrack-acct.conf   or something.  probably should present the question and this idea to ubuntu-devel anyway.  perhaps I'm on crack.
[18:33] <kees> tgardner: you can see examples is the oss .conf file in there now
[18:35] <tgardner> kees, in lucid? All I see are blacklists
[18:36] <kees> hm.  my "alsa-base" package seems to claim it ships /etc/modprobe.d/alsa-base.conf
[18:37] <kees> examples like:
[18:37] <kees> install snd-via82xx /sbin/modprobe --ignore-install snd-via82xx $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-seq ; }
[18:37] <kees> (oh, I guess it should include $CMDLINE_OPTS
[18:37] <kees> )
=== kentb_lunch is now known as kentb
[20:29] <jjohansen> -> Lunch
[21:19]  * ogasawara lunch
[21:29] <MTecknology> apw: Keeping busy I see