[07:36]  * apw struggles on with crap internet, go bt go
[07:38]  * jk- read that as "crab internet"
[07:39] <smb> Its probably going as much sideways as that...
[07:40] <smb> apw, Any estimate whether or when they fix the wiring madness?
[07:40] <apw> jk-, you are upside down, so that is not supprising
[07:41] <jk-> :D
[07:41] <apw> smb, in theory the people to fix the broken draw arrived 40 minutes ago, fail
[07:41] <smb> apw, professionals...
[07:41] <apw> smb, and bt have magnanimously decided they can come back on the 13th to finish the job assuming the wire is in place
[07:41] <apw> so no internet until then at least
[07:42]  * apw burns some giffgaff data he has
[07:42] <smb> doh! what a fail
[07:51] <amitk> apw: I think this behaviour is part of charter of the Telecom Union of the World. I have yet to see a good Telecom company (though my Finnish one came close)
[07:52] <apw> in this day and age i find it incredible the lead times one has on service.  virgin for instance i am waiting now 4 weeks for someone to come and see if we have a wire at the house, which btw we do i can see it sticking out of the ground and the one next to it goes to our neibour who has service
[07:53] <apw> but till some minion comes to see if the cable they laid exists, they can't even tell me how long it would take to get someone to come and connect it
[07:53] <apw> oh and they won't call me for 7-14 days
[07:53] <apw> even call me, to tell me when they might be able to come
[07:53] <apw> i feel a ranting blog post coming on
[09:02] <ppisati> git fsck FTW! :)
[10:43] <dholbach> hey
[10:44] <dholbach> does anyone know if an Atheros AR9000 card (in a HP Probook 4545s) is somehow supported in Ubuntu? I'm looking at a friends laptop with 12.04 right now
[12:21] <ovidiu-florin> hello world :d
[12:21] <ovidiu-florin> when is the next kernel update planned for Precice?
[12:54] <brendand> ovidiu-florin, by the end of this week
[12:55] <ovidiu-florin> brendand: to what version?
[13:07] <sforshee> ogra_, ppisati: do either of you know whether anyone's looked at using the sensors on the nexus 4 yet?
[13:07] <ogra_> nope no idea
[13:08] <sforshee> hmm. It looks like android is using a proprietary library
[13:09] <psino> smb: do you know whether the patch mentioned in https://lkml.org/lkml/2013/3/21/518 will be applied to the planned precise kernel upgrade this week?
[13:10] <smb> psino, yes no, as they still have not succeeded in pushing it upstream
[13:11] <psino> ok, I've been on easter vacation so I haven't been able to pay attention to the progress
[13:12] <smb> psino, There was another ping for it but since it has to go via x86 maintainers it seems to be a bit sluggish
[13:15] <psino> what's the chance for having ubuntu include the patches before it's fixed upstream like fedora decided to do? :)
[13:23] <smb> psino, if the problem is bad enough, there is a bug report and someone willing to do testing. Of course things upstream can happen relatively quickly and the effort might be in vain in the end.
[13:26] <psino> do you know any of the x86 maintainers or a thread where there's some more information about the current state of the patches, so I can see how it is progressing / possibly have a little chat/email with the people who's going to merge it upstream?
[13:27] <ogra_> sforshee, talk to tvoss ... i think he looked into it but not on  a kernel level
[13:27] <ogra_> (not sure that was specifically on n4 though)
[13:28] <sforshee> ogra_, thanks. I'm really just looking for where the knobs for powering various device on/off are, but in the n4 they don't seem to be in the kernel
[13:28] <ogra_> right tvoss might know more ... i know he researched the general android sensor handling ... 
[13:30] <smb> psino, Think this (http://lists.xen.org/archives/html/xen-devel/2013-03/msg01976.html) are the latest messages
[13:33] <smb> psino, and hpa is one of them maintainers
[13:35] <psino> smb: thanks, I'll possibly give him a small prod to check the status of the patches :)
[13:36] <smb> psino, Well Boris did just yesterday. But one can always try. :)
[13:37] <psino> probably doesn't hurt to let him know there's more people being affected by it :)
[13:40] <psino> why would boris not want the patches to go into 3.9?
[13:42] <smb> I think that does not mean he does not want them there. Its more that he fear they wont make it. Or maybe implying that they have not appeared because 3.9 needs to be finalized first
[13:43] <ogasawara> rtg_, bjf, apw: just to confirm we're all in agreement, we're not going to provide an LBM package for Raring at this time.  correct?
[13:44] <rtg_> ogasawara, I don't think we shold be providing LBM for any release other then LTS
[13:44] <ogasawara> rtg_: I'm good with that
[13:44] <rtg_> given the shorter life span of the interim releases and the amount of work required to maintain an LBM
[13:47] <rtg_> ogasawara, you could drop in a cw-3.[78] into the precise LBM if you're tired of managing :)
[13:47] <ogasawara> rtg_: I am, I'll put it on my todo list
[13:51] <apw> ogasawara, works for me
[13:55] <rtg_> apw, I'm down to about 40 SAUCE patches to review, so you can expect more carnage in raring master-next.
[13:55] <rtg_> more, and frequent
[13:57] <apw> rtg_, great
[13:58] <rtg_> apw, just wanna be sure I don't push over something you've just pushed 'cause I'm not really checking very closely
[13:58] <apw> rtg_, nope, i have been helping the builders cut my house to bits
[14:00] <rtg_> apw, ugh, sounds painful
[14:50] <apw> rtg_, bah you beat me to applying those patches
[14:50] <rtg_> apw, email overlap
[14:54] <amitk> rtg_: do you moonlight as the host of Radioparadise? :)
[14:55] <rtg_> amitk, I havern't been a DJ in a long, long time.
[14:55] <amitk> rtg_: damn, he sounds just like you
[14:56] <rtg_> yeah, but they play all this mushy crap.
[14:56] <rtg_> I'm a rock 'n roll dude
[14:57] <amitk> rtg_: yeah, I tuned into them after ages while testing a new install for sound. I'm sure I'll grow up in a day or so.
[14:58] <psivaa> bjf: reported bug 1164553 for the test failure on panda
[14:58] <ubot2`> Launchpad bug 1164553 in linux (Ubuntu) "ubuntu_ecryptfs.lp-872905.sh.btrfs test fails to complete on panda ES with linux-ti-omap4: 3.5.0-222.33" [Undecided,New] https://launchpad.net/bugs/1164553
[14:59] <bjf> ppisati, cking, ^
[14:59] <cking> oh goody
[14:59] <apw> rtg_, i don't think i can visualise you as a DJ
[14:59] <rtg_> apw, I guess I was a different guy then :)
[15:00] <ppisati> cking: is it the same one you made me test some weeks ago?
[15:00] <cking> ppisati, I'm not sure (yet)
[15:20] <apw> rtg_, i am struggling with that image :)
[15:20] <rtg_> apw, we all evolve.
[15:22] <apw> rtg_, even us dinosaurs ?
[15:22] <rtg_> it happens slowly....
[15:34]  * ppisati wanders away for a bit
[15:37] <psivaa> cking: linux-lts-quantal-3.5.0 also has the same issue, 'WARNING: at /build/buildd/linux-lts-quantal-3.5.0/fs/btrfs/super.c:221 __btrfs_abort_transaction+0x99/0xb0 [btrfs]()'
[15:37] <psivaa> cking: do you need a separate bug for that?
[15:42] <bjf> psivaa, no, same issue there. see the comment cking added to the bug
[15:50] <psivaa> bjf: ok, i see that now, thanks. I'm rerunning the tests again. But if it happens again, i'm not sure how to proceed, since the rest of the tests wont be run after this.
[15:51] <cking> bjf, I suggest disabling this test for the moment, it is a corner case
[15:59] <apw> rtg_, how is raring, i have a patch to push ... let me know when she is static enough for me to push
[15:59] <apw> (rebase and push obviously)
[15:59] <rtg_> apw, another hour ?
[15:59] <apw> np
[16:00] <rtg_> 18 patches left to review
[16:02] <rtg_> apw, while you're waiting, perhaps you could take a stab at upstreaming 'UBUNTU: SAUCE: rds_ib_send() -- prevent local pings
[16:02] <rtg_>  triggering BUG_ON()' ?
[16:12] <bjf> psivaa, i'm sort of confused right now since it looks like that test is blacklisted
[16:12] <bjf> psivaa, i'm still looking at it
[16:13] <psivaa> bjf: ack, thanks
[16:17] <psivaa> bjf: just to confirm that the test was running and was passing in the past, the latest good one being on 19/03
[16:22] <rtg_> sforshee, did you ever try to upstream 'UBUNTU: SAUCE: dell-wmi: Demote unknown WMI event message to pr_debug' ?
[16:23] <sforshee> rtg_, I did, but mjg59 didn't merge it or even respond
[16:23] <rtg_> ack
[16:25] <rtg_> sforshee, how did you remember that so quick? that was over a year ago
[16:25] <sforshee> rtg_, I tried again within the past several months
[16:26] <sforshee> the first time he was going to merge it but someone from dell said they'd post patches to handle the events soon
[16:26] <sforshee> that never happened
[16:26] <rtg_> sforshee, oh well, its a simple enough patch.
[16:26] <rtg_> cking, do you think we still need 'UBUNTU: SAUCE: S3 early resume debug via keyboard LEDs' ?
[16:26] <sforshee> rtg_, yeah. The problem was we kept getting bug reports from folks who saw the message in dmesg.
[16:27] <cking> rtg_, I think we can bin that
[16:27] <rtg_> cking, ack
[16:27] <sforshee> rtg_, the more recent attempt was in December: http://thread.gmane.org/gmane.linux.drivers.platform.x86.devel/4065
[16:39] <sconklin> sforshee: some patches of yours that we got from stable for 3.2 are triggering a build fail due to config changes. Do we need these in precise? It looks like it adds nothing unless we make a config change, which we're not likely to do:
[16:39] <sconklin> 0156-efivars-Allow-disabling-use-as-a-pstore-backend.patch
[16:39] <sconklin> 0157-efivars-Add-module-parameter-to-disable-use-as-a-pst.patch
[16:39] <sconklin> 0158-efivars-Fix-check-for-CONFIG_EFI_VARS_PSTORE_DEFAULT.patch
[16:40] <sforshee> sconklin, looking
[16:40] <sconklin> thanks
[16:44] <sforshee> sconklin, I'm curious what the build failures are, but I think we'll want to set CONFIG_EFI_VARS_PSTORE=n as we've done for raring
[16:45] <sforshee> this was done in response to stgraber's lenovo getting bricked twice when pstore tried to write crash dumps to efivars
[16:45] <sconklin> EFI Variable Support via sysfs (EFI_VARS) [Y/n/m/?] y
[16:45] <sconklin>   Register efivars backend for pstore (EFI_VARS_PSTORE) [Y/n/?] (NEW) aborted!
[16:45] <sconklin> Console input/output is redirected. Run 'make oldconfig' to update configuration.
[16:45] <sconklin> sforshee: ^^
[16:45] <sforshee> sconklin, so it fails simply because there's a new config option
[16:46] <sconklin> What confused me was that the patch says it sets it, but it clearly didn't
[16:47] <sconklin> I'll updateconfigs
[16:47] <sforshee> sconklin, the other option is to enable that one and set the other option to make it disabled by default, then it can be enabled via the command line
[16:48] <sforshee> but I think we should keep it off by default until upstream has figured out how to work around all the firmware bugs that cause machines to get bricked
[16:48] <sconklin> sforshee: ack
[16:56] <rtg_> ogasawara, which blueprint has the SAUCE patch review work item? LP is timing out so I'm having trouble searching.
[16:56] <jsalisbury> rtg_, apw Is there a technical reason why the number of cpus is limited to 8 for the 32 bit arch?  I see CONFIG_NR_CPUS=8 in the config file.  A bug was opened for this: bug 1164122
[16:56] <ubot2`> Launchpad bug 1164122 in linux (Ubuntu) "Ubuntu 12.10 32-bit only shows a maximum of 8 cores" [Medium,Incomplete] https://launchpad.net/bugs/1164122
[16:56] <rtg_> jsalisbury, IIRC there was a memory cliff for 32 bit if you defined more then 8
[16:56] <ogasawara> rtg_: https://blueprints.launchpad.net/ubuntu/+spec/hardware-r-kernel-delta-review
[16:57] <ogasawara> rtg_: but really, you want the spec -> https://wiki.ubuntu.com/KernelTeam/Specs/RaringKernelDeltaReview
[16:57] <jsalisbury> rtg_, ok thanks.  I'll see if I can find some details to post to the bug.
[16:57] <rtg_> ogasawara, ok, I have looked at _every_ SAUCE patch over the last 2 days.
[16:58] <ogasawara> rtg_: ah, so you really do just want the bp to close that sucker out then
[16:58] <ogasawara> rtg_: I can do it for you, I've got it open here
[16:58] <rtg_> ogasawara, what I really want is my name clear of all responsibilities :)
[16:58] <ogasawara> rtg_: I'll make it so
[16:58] <rtg_> ogasawara, :)
[17:02] <rtg_> apw, raring master-next pushed. I'll return to my usual policy of _carefully_ checking before push +
[17:02] <rtg_> now to rebuild unstable-3.9
[17:14] <apw> rtg_, fix pushed to raring master-next, thanks
[17:18] <rtg_> apw, ack
[17:28] <jsalisbury> sforshee, I'm looking at bug 1155731, which appears to be related to a SAUCE patch or config file change.  Do you happen to have a  MacBook3,1 and a Apple bluetooth keyboard to see if you see this as well?
[17:28] <ubot2`> Launchpad bug 1155731 in linux (Ubuntu) "Recurring kernel panic with khidp after resume from S3 on a MacBook3,1 with a connected bluetooth keyboard" [High,Incomplete] https://launchpad.net/bugs/1155731
[17:31] <sforshee> jsalisbury, nope, I have neither
[17:31] <jsalisbury> sforshee, ok, thanks
[17:32]  * rtg_ -> lunch
[20:08]  * rtg_ -> EOD
[23:37] <dobey> anyone know how i can disable a specific PCI address from being used, rather than just blacklisting a module?