[01:55] <ohsix> hm where do i ask to get the debootsrtap backport for natty bumped again
[08:51]  * apw yawns
[08:51] <smb> morning
[08:52] <apw> morning
[08:53]  * apw notes that all the slowness he was seeing was nm-applet, which was 1.7g and growing
[08:53] <smb> o_O
[08:54] <apw> yeah major memory leak and no mistake
[08:55] <apw> oh and that was 1.7g resident, about 8gb virtual before i zappd it
[08:55] <smb> Awesome. That must help to get rid off those older machines.. :-P
[08:56] <smb> Had a kvm install yesterday and that felt much more unstable than real hw (or xen the last time I looked). Lots of those sorry compiz just shit itself
[08:57] <smb> (not only compiz but nautilus, flippy and whatnot)
[08:58]  * smb cannot remember all the names
[09:00] <cooloney> apw and smb, morning, long time no talk, men
[09:00] <apw> smb, who is this cooloney fellow anyhow
[09:01] <smb> apw, Dunno, feels somehow it rings a bell
[09:01] <cooloney> come on, 
[09:01] <smb> cooloney, It's foggy, like looking through a lot of glass bottoms... :-P
[09:02]  * cooloney waves at apw and smb with splendid smile
[09:07]  * smb waves back at cooloney 
[09:08] <cooloney> smb: how's going, man
[09:15] <smb> cooloney, Same as always, just different. :) Had a bit of a cold lately but now its getting warmer. 
[09:15] <smb> Err
[09:15] <smb> I mean cold as in outside cold not me being ill
[09:15]  * smb needs to wake his brain
[09:17] <apw> heh yeah, now apw has the other cold to confuse matters
[09:25] <cos^> hi, i submitted a small patch to kernel yesterday to lkml+other lists. how long it normally takes for a patch to be added to git repo and should i just wait for it?
[09:26]  * cooloney feels cold
[10:32] <ppisati> apw: when you have time, can you bump linux-ti-omap4-meta? thanks
[10:39] <bkerensa> Are any Kernel Team folks awake? :)
[10:40] <bkerensa> I'm hoping to improve the description for linux-tools and resolve #593107 and was wondering if the Kernel had some feedback as to a better description... The only tool I know of in that is perf 
[10:42] <infinity> ppisati: I think he may have done it a minute or two before you asked. ;)
[10:48] <apw> ppisati, already done
[10:48] <apw> bug #593107b
[10:48] <ubot2`> Launchpad bug 593107 in linux "Package description for linux-tools-* needs improvement" [Medium,In progress] https://launchpad.net/bugs/593107
[10:48] <apw> bug #593107
[10:48] <smb> bkerensa, At least for precise it is also x86_energy_perf_policy and turbostat
[10:49] <apw> bkerensa, the intent is that it will get more tools as we go
[10:49] <apw> as smb points out we already have some more
[10:49] <bkerensa> apw: Would it be ok to improve upon the description?
[10:50] <apw> bkerensa, yes, its not very good indeed.  erm, we do need to keep its generic nature
[10:51] <apw> bkerensa, the intent is for it to contain those tools which are shipped with the upstream kernel and where more than version is installed at once
[10:52] <apw> bkerensa, "Kernel specific tools such as perf which are tied closly to the kernel version for version NNNN on ARCH" perhaps
[10:52] <apw> the DESC not being updated is also wrong
[10:55] <bkerensa> apw: Indeed
[10:55] <bkerensa> updating it now and will submit a patch
[10:55] <apw> bkerensa, sounds good, let us know when thats done
[10:57] <bkerensa> apw: How do I add reference for Arch and Versions in control desc?
[10:57] <apw> bkerensa, well i am confused, i would expect DESC to be the right thing and to be filled in
[10:57] <apw> bkerensa, so leave that bit and i'll figure that out separatly now
[10:58] <bkerensa> apw: k
[10:58] <apw> bkerensa, from the bug it looks like any description update should be mirrored into the meta package which is in a different git repo
[11:05] <bkerensa> apw: Kernel specific tools such as perf, turbostat and 
[11:05] <bkerensa> x86_energy_perf_policy which are tied closely to the kernel version 3.2.0 
[11:05] <bkerensa> on x86/x86_64.
[11:06] <bkerensa> how does that sound?
[11:06] <apw> bkerensa, thats fine, though leave the on part as on DESC as that should get put in
[11:07] <bkerensa> k
[11:07] <apw> bkerensa, am looking at why that doesn't work
[11:07] <cos^> is there a generic kernel channel on freenode?
[11:08] <apw> cos^, as in non-ubuntu kernel stuff?  i don't think i know of one, they tend to be more specific to a subsystem like intel graphics or whatever
[11:08] <ppisati> brb
[11:10] <cos^> apw: ok, thanks. i'll try to find something
[11:10] <apw> cos^, so patches to lkml take between 0 and 7 days to be noticed normally, after that it depend on whether they liked it etc
[11:11] <apw> cos^, then they will be likely merged into a maintainers tree, and more than likely merged up in the next merge window if they represent new functionality or a low priority fix.  if they are urgent they may go in immediatly
[11:11] <cos^> what would be the best way to get my patch to next ubuntu kernel? attach patch to bug report?
[11:12] <apw> cos^, well if its a clear bug fix, then you would mark it for stable, or submit it to stable (upstream stable) and we would then get it it from there in the natural course of taking stalbe
[11:12] <apw> cos^, if its urgent or affecting a wide range of people then you could also send it to kernel-team@lists.ubuntu.com making sure it has a reference to the bug which it fixes and we can review it
[11:13] <apw> cos^, though don't be offended if someone on the team then tells you that we would prefer to wait for it to come from stable
[11:13] <cos^> apw: it's this http://www.spinics.net/lists/linux-input/msg19380.html
[11:13] <apw> cos^, cirtainly we prefer to have a commit upstream in linus' tree so we know its not going to be rejected before we take things
[11:13] <cos^> not urgent, but shouldn't break anything
[11:14] <apw> cos^, that is cirtainly low impact and a device enablement only so ... you have more chance than average of getting it applied earlier
[11:14] <cos^> vs https://bugs.launchpad.net/ubuntu/+source/linux/+bug/500834
[11:14] <ubot2`> Launchpad bug 500834 in linux "CH joysticks not working" [Undecided,Confirmed]
[11:38] <bkerensa> apw: I passed the patch for review 
[11:38] <apw> bkerensa, are you submitting your patch to the bug or to the mailing list ?
[11:39] <bkerensa> apw: I submitted it to the bug but pinged mailing list so kernel team can review as necessary 
[11:39] <Ezim> hi now I have tried everything but it seems this issue is kernel related. it gives me kernel panic. when I use my bluetooth usb for transfering files between laptop-phone.
[11:41] <apw> Ezim, if you get a kernel panic, then there is a kernel bug almost cirtainly, some instances of bad config can legitimatly cause a panic, but not commonly
[11:41] <apw> Ezim, so get the panic filed as a bug
[11:42] <Ezim> apw, how?
[11:42] <apw> how do you know you are getting kernel panic?
[11:42] <apw> either its in a log, or on your screen
[11:42] <Ezim> apw, putting my blueotooth usb to laptop and try transfering files
[11:42] <apw> so either file a bug and add the log snippet that has the panic, or a photo of the panic screen
[11:43] <Ezim> apw, were can I find the log?
[11:43] <apw> you may see the panic in /var/log/syslog
[11:43] <apw> but you are saying you see a panic, so you must be seeeing it somewhere
[11:45] <Ezim> apw, my laptop screen got freezed and turn to black with white error message
[11:45] <Ezim> that most be kernel panic?
[11:45] <bkerensa> Ezim: What was the specific error message?
[11:45] <apw> depends what the error message says
[11:46] <apw> and if its a panic, then an image of that screen is what you want to attach
[11:46] <Ezim> bkerensa, sorry I do not remenber to be honest a lot of text
[11:46] <Ezim> I can pastebin the things I have in /var/log/syslog
[11:46] <Ezim> would that help anything?
[11:47] <Ezim> all the kernel in (k)ubuntu 11.10 have this issue.
[11:47] <apw> if there is a panic in there likely yes
[11:47] <Ezim> the older (k)ubuntu release I did not have this problem
[11:48] <Ezim> apw, there is nothing in syslog about kernel panic
[11:49] <apw> then the information only appears on that black and white screen you mentioned
[11:50] <Ezim> but there is bluez error in syslog
[11:51] <Ezim> apw, I can give information about my bluetooth usb
[11:51] <apw> if you are getting a kernel panic on the screen when the freeze occurs, that is the information we would need to see to have a hope of finding the issue.  bluez is userspace
[11:51] <Ezim> which kernel I am running
[11:51] <Ezim> if that is for any help
[11:52] <apw> if you have tested the latest official kernel and its still broken, then the panic is the only thing we are likely to be able to use to help
[11:52] <Ezim> apw, :( my phone camera is really bad but if I get kernel panic again I will take screenshot.
[11:52] <apw> and you need to get a bug filed, ubuntu-bug linux
[11:52] <Ezim> no I am to scare to try
[11:53] <Ezim> apw, so I do not need to filed a bug report to launchpad
[11:53] <bkerensa> Ezim: I assure you ubuntu-bug will not bite :)
[11:53] <Ezim> #ubuntu-bug works also?
[11:53] <bkerensa> Ezim: It will gather info and open a bug report in launchpad
[11:53]  * apw is hoping we have language barrier issues here
[11:54] <apw> are you too scared to try filing a bug, or to try reproducing the issue, or trying the latest official kernel
[11:54] <bkerensa> Ezim: No you would need to run the command from terminal it is not a channel
[11:54] <Ezim> bkerensa, doing it now
[11:55] <Ezim> what should I pick?
[11:55] <apw> Description-en: Linux kernel image for version 3.2.0 on x86/x86_64
[11:55] <apw>  This package contains the Linux kernel image for version 3.2.0 on
[11:55] <apw>  x86/x86_64.
[11:56] <Ezim> should I pick External or internal storage device
[11:57] <Ezim> or other problem?
[11:57]  * ppisati -> out for lunch
[11:57] <bkerensa> apw: hmm?
[11:57] <apw> bkerensa, that is for smb, talking about the arch name and how its dumb
[11:58] <bkerensa> oh :D
[11:59] <Ezim> what should I pick? :)
[12:00] <apw> debian.master/control.d/vars.generic:desc="x86/x86_64"
[12:00] <apw> debian.master/control.d/vars.generic-pae:desc="x86"
[12:00] <apw> debian.master/control.d/vars.omap:desc="TI OMAP3-based systems"
[12:00] <apw> debian.master/control.d/vars.powerpc:desc="32-bit PowerPC"
[12:00] <apw> debian.master/control.d/vars.powerpc-smp:desc="32-bit PowerPC SMP"
[12:00] <apw> debian.master/control.d/vars.powerpc64-smp:desc="64-bit PowerPC SMP"
[12:00] <apw> debian.master/control.d/vars.virtual:desc="x86/x86_64"
[12:04] <Ezim> :) okey that does not help me at all
[12:04] <apw> Ezim, i am having more than one conversation, this one is with sm
[12:04] <apw> smb
[12:11] <Ezim> apw, np.
[12:11] <Ezim> I think its best if I file a bug report for it in launchpad or compile myself new kernel:)
[12:21] <apw> smb, vv
[12:21] <smb> apw, ^^
[12:21] <apw> Description: Linux kernel tools for version 3.2.0-16
[12:21] <apw>  This package provides the architecture dependant parts for kernel
[12:21] <apw>  version locked tools for version 3.2.0-16 on 64 bit x86.
[12:21] <apw> ...
[12:22] <smb> apw, Looks much better to me
[12:23] <smb> apw, Is it rather too much or would "kernel version" instead of just version make sense?
[12:23] <apw> Description: Linux kernel image for version 3.2.0 on 64 bit x86 SMP
[12:23] <apw>  This package contains the Linux kernel image for version 3.2.0 on
[12:23] <apw>  64 bit x86 SMP.
[12:23] <apw> smb, that one is the linux-image one
[12:24] <apw> the tools i notice are not using the same version either
[12:25] <smb> Hm, yep one with abi reference and one without
[12:25] <smb> maybe removing the "for" makes sense?
[12:27] <smb> So "Linux kernel image version 3.2.0-16 on 64 bit x86"... Not sure about smp either
[12:27] <smb> cause it is the same for UP or SMP and just toggles
[12:49] <k-rAd-> i would like to install 
[12:49] <k-rAd-> !info linux-image precise
[12:49] <k-rAd-> the latest pangolin kernel on oneiric
[12:50] <k-rAd-> linux-image (source: linux-meta): Generic Linux kernel image.. In component main, is optional. Version 3.2.0.16.16 (precise), package size 1 kB, installed size 30 kB (Only available for i386 amd64 all armel armhf powerpc)
[12:50] <k-rAd-> i have a usb 3.0 drive that is off/on.  
[12:50] <k-rAd-> turns off then on
[12:50] <k-rAd-> on crontab
[12:50] <smb> bryceh, tjaalton Not sure whom to ask specifically, just wondering whether you have a feeling about gui stablility on kvm/cirrus 3D (surprised that is possible actually). 2D displays better but seems generally to have more applications (nautilus/bamfd or so) crashing
[12:54] <tjaalton> smb: unity should not run on it
[12:54] <tjaalton> there's a bug open aboutit
[12:55] <smb> tjaalton, Ok, well it does run... sort of. Just not very displayative...
[12:55] <tjaalton> the new swrast driver has a different identifier string, so the current blacklist doesn't work
[12:56] <tjaalton> well, it's just buggy :)
[12:56] <tjaalton> but not that useful yet anyway
[12:56] <smb> Heh, I "see" :)
[12:57] <smb> Ah, so at least people are aware. Unfortunately it is the default gfx for kvm and you are just taken into 3d if you are not careful
[12:59] <tjaalton> i don't know why it's not fixed yet
[12:59] <tjaalton> filed two weeks ago
[13:00] <smb> Probably depends on the right people actually noticing it and not having worse problems to look after... 
[13:11] <apw> !info udev-common
[13:11] <apw> !info libudev0
[13:12] <apw> bot not useful error
[13:15]  * tgardner reboots tangerine for kernel update
[13:19] <apw> bkerensa, to take this patch i need to commit it to our git tree, and for that it needs to be signed off, can i take it you are happy for it to be 'Signed-off-by: ' the email address in the changelog ?
[13:19] <bkerensa> apw: Surely :)
[13:20] <apw> bkerensa, this is a linux-meta update, is are you doing the linux update as well ?
[13:20] <bkerensa> apw: I can do that as well yes :)
[13:20] <apw> bkerensa, ok let me know when its on the bug, and i'll poke it
[13:20] <bkerensa> I will ping you when I have that one complete but there is not a open bug for it
[13:21] <apw> i am fixing the DESC issue as well
[13:21] <apw> bkerensa, actually there is no bug for the linux-meta issue, or this one is miss targetted, but ... i'll add a task for linux-meta to the same bug
[13:22] <apw> bkerensa, ok done, i've assigned both to you
[13:22] <bkerensa> apw: Ok whats the package for the one that still needs work so I can get the right source?
[13:23] <apw> linux
[13:25] <bkerensa> k
[13:44] <bkerensa> apw: Ok I have updated #593107 with the second patch for "linux" so now you have both :)
[13:48] <apw> bkerensa, ok thanks
[13:49] <apw> bkerensa, thanks will look at them now
[13:49] <apw> bkerensa, thanks for contributing
[13:50] <bkerensa> apw: No problem... Hopefully bigger things in the future :P
[13:55] <apw> bkerensa,  we typically take patches after review on the mailing list, the description of the formatting rules etc for patches are here: https://wiki.ubuntu.com/Kernel/Dev/KernelPatches
[13:55] <apw> bkerensa, though in this case i've got these ones covered
[13:55] <bkerensa> apw: excellent
[13:56] <bkerensa> apw: and the signed off byline just means you take over the changes in changelog?
[13:57] <apw> Signed-off-by: means that you are saying the work is yours, and is yours to give to the project, that it is compatible with the licence of the project too
[13:58] <apw> if that makes sense
[14:00] <apw> ppisati, the el in armel is that "emulated float"
[14:02] <bkerensa> apw: Ahh surely thats fine :)
[14:11] <ppisati> apw: ARM E(ABI) L(ittle)
[14:11] <ppisati> apw: ad EABI stands for Embedded Abstract Binary Interface
[14:13] <apw> ppisati, oh ok, from a consumers point of view that is mostly useless, is it the soft float option if hf is hard ?
[14:13] <ppisati> yep
[14:39] <soren> Hey. Since yesterday's kernel update, my laptop (Thinkpad X220) fails to suspend properly. I was hoping I could use git bisect to my way to the culprit, but I'm having a bit of trouble.
[14:39] <scott-work> is there any chance of someone review the lowlatency kernel in REVU?  http://revu.ubuntuwire.com/p/linux-lowlatency
[14:40] <scott-work> we need just one more advocate before tomorrow (i believe)
[14:41] <soren> I wanted to build the kernel with "debian/rules binary-generic", but since the build system gets rebased on top, i can't really do that.
[14:47] <soren> What's the trick to using git-bisect to track down a bug?
[14:54] <tgardner> apw, git://kernel.ubuntu.com/rtg/ubuntu-precise.git hv
[14:59] <ogasawara> soren: so I'm assuming this is precise that you're running?  and that the latest 3.2.0-16.25 kernel is giving you suspend issues, and 3.2.0-15.24 is working as expected?
[14:59] <soren> ogasawara: That's exactly right.
[15:00] <soren> ogasawara: I can't git bisect my way to find the culprit, because for most of the points in between the two commits, there build system isn't there.
[15:01] <ogasawara> soren: ack.  so give this a quick test if you can -> http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2.6-precise/
[15:01] <soren> ogasawara: Cool. Onit.
[15:01] <soren> On it, even.
[15:01] <ogasawara> soren: the mainline builds will at least help a little here
[15:02] <soren> ogasawara: I'm on hotel internet, so it'll be a little bit before I'm done downloading. :-/
[15:02] <ogasawara> soren: ack
[15:03] <ogasawara> soren: about the bisect, jj gave an dev week talk a while ago and touched on the issues you mention doing a bisect -> https://wiki.ubuntu.com/MeetingLogs/devweek1107/KernelDebugging
[15:03] <soren> ogasawara: Cool. Thanks.
[15:04] <apw> /bin/sh: 1: arm-linux-gnueabi-objdump: not found
[15:07]  * ogasawara back in 20
[15:26] <tgardner> apw, looks like my hv branch build correctly now
[15:30] <apw> tgardner, ok cool thakns
[15:38] <vanhoof> soren: x220 here w/ 3.2.0-16, s3 working quite well
[15:41] <soren> vanhoof: Fascinating.
[15:42] <soren> vanhoof: For a whlie I suspected it to be a userspace problem, but reverting to -15 seemed to solve it, so I ruled that out. Perhaps that was premature.
[15:43] <soren> vanhoof: I suspected userspace because it would fail to suspend, but when I did a "shutdown -h now" afterwards, it'd suspend. When I resumed it, it shut down.
[15:43] <soren> ...so it was like some process was preventing it from suspending, but shutdown caused that to be killed, so it could proceed with the suspend... and when it resumed from suspend, it continued with the shutdown.
[15:44] <vanhoof> soren: yeah quite odd
[15:44] <soren> ...but again: Reverting to a -15 kernel, the problem seemed to disappear.
[15:44] <vanhoof> soren: fwiw I did a dist-upgrade last evening as soon as i saw -16 hit the archive
[15:44] <vanhoof> been using the x220 all morning
[15:44] <vanhoof> I am running with no swap, and just /boot, /rootfs, /tmpfs, no swap fwiw
[15:45] <vanhoof> and ssd
[15:45] <vanhoof> but other than that it's an i7 x220
[15:45] <soren> This is an i5 one.
[15:46] <soren> Sandybridge.
[15:46] <vanhoof> soren: what bios are you on?
[15:46] <vanhoof> soren: i'm still on 1.17
[15:47] <vanhoof> i believe 1.24 is the latest
[15:47] <soren> vanhoof: BIOS Revision: 1.26
[15:47] <soren> Firmware Revision: 1.19
[15:49] <vanhoof> soren: yeah really sounds like $some_process is wedged and stoping the s3, you attached to any remote mounts? ... i had similar issues when my NAS went offline once
[15:50] <soren> vanhoof: Nope.
[16:02] <apw> -do_common_headers_indep = false
[16:14] <apw> tgardner, this hv branch seems to have an ndiswrapper update at the bottom
[16:14] <apw> as in unmerged with ogasawara's tree
[16:15] <ogasawara> apw: I've yanked ndiswrapper
[16:15] <apw> ogasawara, ahh bad ?
[16:15] <ogasawara> apw: I saw no need to carry it since there is a dkms package for it
[16:15] <apw> oh as in gone, great
[16:16] <tgardner> apw, yeah, I rebased against master-next before I started on hv
[16:16] <tgardner> apw, whoops, maybe I didn't
[16:16]  * apw re-drops it from his copy
[16:16] <ogasawara> apw: yah, just drop it from what you have
[16:17] <apw> pick 5756c31 NLS: improve UTF8 -> UTF16 string conversion routine
[16:17] <apw> tgardner, i assume thats foundational ?
[16:18] <tgardner> apw, looks like it. its alos reasonably well isolated
[16:19] <tgardner> apw, well, not really. that should have been 2 patches.
[16:19] <apw> 68 patches and counting, deep joy
[16:28] <tgardner> scott-work, I updated the comments at http://revu.ubuntuwire.com/p/linux-lowlatency
[16:32] <scott-work> thank you tgardner :)
[16:34] <tgardner> apw, dpkg -S objdump
[16:34] <tgardner> binutils-arm-linux-gnueabi: /usr/arm-linux-gnueabi/bin/objdump
[16:45] <apw> tgardner, ok i am being a tard, and trying to cross the wrong way round ... tool failure
[16:46] <tgardner> apw, there is an easy solution to that. gahab
[17:20] <tkamppeter> Any chance that anyone could fix bug 900802 for Precise, that we would have USB tethering support for the iPhone in the LTS. The fix (patch attached) is trivial, only add the ID of the iPhone 4S.
[17:20] <ubot2`> Launchpad bug 900802 in ipheth "PATCH: Got the USB tethering of the iPhone 4S working" [Undecided,Fix released] https://launchpad.net/bugs/900802
[17:22] <mjg59> tkamppeter: Has that been sent upstream?
[17:24] <apw> bkerensa, ok i've looked at your patches, unfortuanatly the first line is a separate short description and cannot be wrapped the way you have.  i have spun an alternative patch to improve these and will push those out shortly
[17:27] <tgardner> tkamppeter, was just going to ask the same question. your patch looks fine.
[17:28] <tkamppeter> mjg59, tgardner, I did not send it upstream by myself, but this is absolutely trivial, only one line with the phone's ID added.
[17:28] <mjg59> tkamppeter: If you don't send it upstream then anyone running an upstream kernel doesn't get the feature and the patch has to be maintained until someone else does it
[17:30] <tgardner> tkamppeter, mjg59 - I'll take care of it
[17:31] <tkamppeter> tgardner, any chance that Precise will ship with USB tethering support for the iPhone 4S?
[17:32] <tgardner> tkamppeter, yes
[17:32] <mjg59> tgardner: Thanks!
[17:34] <tkamppeter> tgardner, thanks, looking forward to have my iPhone 4S USB-tethering out of the box with Precise.
[17:37] <tgardner> tkamppeter, which email address would you prefer for the Signed-off-by ?
[17:41] <tkamppeter> tgardner, till dot kamppeter at gmail dot com
[17:41] <tgardner> tkamppeter, can do
[17:41] <albrigha> tkamppeter, hey Till!
[17:42] <tkamppeter> albrigha, hi
[17:42] <albrigha> tkamppeter, long time no talk to!
[17:42] <albrigha> tkamppeter, I was on HPLIP for years and years :)
[17:42] <tkamppeter> hi, I remember you, and what are you doing now.
[17:43] <albrigha> tkamppeter, just started on the Ubuntu QA team!
[17:44] <tkamppeter> albrigha, yes in QA you test and report bugs, if it's HPLIP you can directly attach the patches to fix the bugs.
[17:45] <albrigha> tkamppeter, nah i don't do hplip any more I'm afraid. :) working on ubuntu overall. but i'm sure some hplip at some point. anyway, I just wanted to say hi there :)
[17:46] <tkamppeter> albrigha, then welcome in the club and have great work with us. Will we meet on the UDSes?
[17:46] <albrigha> tkamppeter, yep! looking forward to it
[17:51] <tkamppeter> albrigha, and if you want to meet me on IRC, I am usually not in the #ubuntu-kernel channel but in #ubuntu-desktop and #ubuntu-devel.
[18:32]  * apw shifts to another machine ... and a more comfortable location
[18:37]  * tgardner -> must have food
[19:35] <tgardner> apw, looks like your hv bits are working.
[21:17]  * tgardner -> EOD
[23:30] <bjf> ogasawara: still around ?