[03:29] <FNStaffa> yo
[03:29] <FNStaffa> !ops
[03:29] <ubot2> Help! lamont, zul, T-Bone, mdz, or jdub
[03:30] <FNStaffa> !ops
[03:30] <FNStaffa> !ops
[03:30] <ubot2> Help! lamont, zul, T-Bone, mdz, or jdub
[07:11] <tjaalton> anyone know if stable@vger is moderated?
[07:20] <smb> morning
[07:21] <smb> tjaalton, Not as far as I know. But it may do some delaying when one is not registered and such...
[07:23] <smb> tjaalton, And I see some mails from you posted recently
[07:32] <tjaalton> smb: oh cool, I'll just wait then :)
[07:37] <ppisati> moin
[07:42] <cking> smb, my tests are still running - HDD is getting rather over-worked :-/
[07:43] <smb> cking, Saw your email. Rather than worrying about your hdd, how are you doing?
[07:44] <cking> smb, I'm OK - crashed out a late afternoon, got a raging temperature and head was all fuzzy, lots of sleep seems to have helped, but woke up at 6am, so I kicked off some tests again
[07:45] <smb> cking, Sounds a bit like dragging something along. 
[07:45] <cking> yep
[07:45] <smb> Anyway, yeah. It seems that something really is not cool with cfq...
[07:46] <cking> so, for the multi-bonnie + dd reader + dd writer, deadline finishes in a few minutes, but cfq is saturated by the dd I/O and bonnie is taking forever to complete
[07:47] <smb> So in the present state it really is not well suited for server and I wonder how well it is for desktop...
[07:47] <cking> bit rubbish for both methinks
[07:48] <cking> let's face it, a dd seems to suck up all the I/O for some strange reason, so it seems totally unfair
[07:49] <smb> right. What you could try (when things ever finish) is to disable autogroup (just wondering about it since trying to find something else around it)
[07:50] <smb> /proc/sys/kernel/sched_autogroup_enabled
[07:51] <cking> yep, I will give this test one more hour to complete and try that
[07:51] <smb> cking, It might be time for breakfast. Isn't it?
[07:51]  * cking munching it right now 
[07:53] <smb> cking, There are rumors about doing that at the breakfast table and non-sticky keys... ;-P
[07:53]  * cking nods
[07:53] <cking> munchy munchy munch
[07:55]  * apw yawns slowly
[08:00] <smb> apw, Morning. Overstretched jaw?
[08:01] <cking> is he still yawning?
[08:03] <smb> cking, ultra slow motion...
[08:04] <cking> just the thought of the yawn is making me yawn too
[08:05] <bambee> morning
[08:28] <xnox> If I'm trying to see which releases an upstream commit went into, is it save to use commitid, e.g. git branch -a --contains commitid
[08:29] <xnox> on the ubuntu git kernels
[08:29] <xnox> ?
[08:29] <xnox> as in, do you ever rewrite upstream history? or do you only ever rebase on top of it?
[08:33] <infinity> apw: Is the linux-image-hwe-generic stuff in precise-* meant to be in main?
[08:34] <infinity> apw: (And linux-image-current-generic, which depends on it)
[08:35] <infinity> You know what, I'm going to assume yes, and we can punt it back to universe if I'm wrong. :P
[08:50]  * henrix will be away for a while
[08:54] <xnox> infinity: you are awake :/
[08:54] <xnox> anyway I think we are sorted with bug 1014883
[08:54] <ubot2> Launchpad bug 1014883 in linux "Check that the nasty md/raid bug is not currently shipped across all releases" [High,Fix released] https://launchpad.net/bugs/1014883
[09:07] <infinity> xnox: Not for long.
[09:08] <xnox> infinity: =))))
[09:08]  * xnox taps infinity, and he crashes
[11:02] <ppisati> brb
[12:30] <cking> smb, so my first round of bonnie++ tests are complete, - you want me to re-run with  /proc/sys/kernel/sched_autogroup_enabled set to zero?
[12:31] <smb> cking, Yes, you don't have to wait eternity for completion. Just to quickly check whther it makes a difference
[12:31] <cking> smb, hrm, let's see how it works out on the faster of the two tests...
[12:32] <smb> cking, Thinking is that maybe having processes isolated counters the goal cfq tries to archive ...
[12:33] <smb> Though sounds completely opposite to what we thought to have seen...
[12:33]  * cking needs to check this tweakable
[12:33] <smb> cking, Basically it turns off the feature that a task with its own session id gets into its own taskgroup
[12:34] <cking> ok, lets see if it does any better
[12:43] <cking> smb, looks like I'm getting a more even share of time to each reader + writer, but let me see what the final data says
[12:44] <smb> cking, Interesting... yeah
[12:45]  * cking is surprised at how long multiple bonnie tests take, sigh
[12:47] <ppisati> cking: i should try them on any arm board, you would be shocked how fast they run on your x86 box :)
[12:47] <ppisati> s/i/you/
[12:47]  * cking chuckes, yep,  you' would see them complete just at the point that the sun turns super-nova
[12:49] <ppisati> probably later
[12:49] <cking> oh, when time comes to a halt then
[13:38]  * cking reboots his AP once more
[13:50] <brendand> jsalisbury, ping
[13:51] <jsalisbury> brendand, pong
[13:51] <brendand> jsalisbury, i'm trying to get back to confirming https://bugs.launchpad.net/bugs/960311
[13:51] <ubot2> Ubuntu bug 960311 in linux "Networking on Dell PowerEdge R300 with Broadcom Corporation NetXtreme BCM5722 Gigabit Ethernet PCI Express is not functional" [High,Confirmed]
[13:52] <brendand> jsalisbury, i can't seem to find the binary packages for the old kernel
[13:52] <brendand> jsalisbury, you wanted me to try : https://launchpad.net/ubuntu/+source/linux/3.2.0-17.27
[13:53] <brendand> jsalisbury, in case you don't remember, this bug appeared about alpha2 and then i got the lab engineer to upgrade the bios and it seemed to disappear. then it returned again at release
[13:53] <jsalisbury> brendand, The .debs you can install are under "Builds".  You just need to click on your specific arch.  Let me look at the bug, it might be beetter to try a newer kernel.
[13:54] <jsalisbury> brendand, It might be best to test the latest Precise kernel, then go from there.
[13:54] <jsalisbury> brendand, https://launchpad.net/ubuntu/+source/linux/3.2.0-25.40
[13:55] <brendand> jsalisbury, i can even test it with the -proposed one (that would actually be easier for me)
[13:55] <brendand> jsalisbury, i'll try and update asap
[13:56] <jsalisbury> brendand, sure that would be great
[14:37] <Yankees52> !ops
[14:37] <ubot2> Help! lamont, zul, T-Bone, mdz, or jdub
[14:37] <Yankees52> !staff
[14:37] <ubot2> hey Christel, Dave2, Gary, KB1JWQ, Levia, Martinp23, SportsChick, VorTechS, jayne, jenda, marienz, nalioth, niko, nhandler, rob, dax, stew, or tomaw, I could use a bit of your time :)
[14:38] <Yankees52> yay =)
[14:38] <Yankees52> [14:38] <Yankees52> [14:38] <Yankees52> [14:38] <Yankees52> [03:28] <bazhang> hfsplus again
[14:38] <Yankees52> [03:28] <Jordan_U> I didn't know I had ops powers in #ubuntu-irc.
[14:38] <Yankees52> [03:29] <Unit193> You do?
[14:38] <Yankees52> [03:29] <Jordan_U> Well, I'm in the !ops factoid there. Let me check if I actually do.
[14:38] <Yankees52> [14:38] <Yankees52> [03:30] <bazhang> I don't but the emergency ! o p s call is the same as in #ubuntu
[14:38] <Yankees52> [03:30] <Jordan_U> Maybe that should be changed :)
[14:38] <Yankees52> [03:30] <Unit193> Appears my fancy cloak allows me.
[14:38] <Yankees52> [05:11] <sistematico> Any help is welcome on #ubuntu-br
[14:38] <Yankees52> [05:11] <sistematico> JavaNunes is using bad words and insulting others users.
[14:38] <Yankees52> [05:43] <bkerensa> IdleOne: you around?
[14:38] <Yankees52> [06:07] <bkerensa> What do we suggest to users reporting abuse in a loco channel if they have no ops available?
[14:38] <Yankees52> [06:07] <bkerensa> Brazil's loco channel has a guy in there that has been using vulgar profanity in there and trolling it it would appear nobody with ops is around.
[14:38] <Yankees52> [06:13] <Flannel> bkerensa: LoCo channels are -irc, but in case of emergency, that channel has ubuntu/member as operators, so... if it's an emergency, it seems you have the ability to handle it yourself.
[14:38] <Yankees52> [06:13] <bkerensa> kk
[14:48]  * ogasawara back in 20
[15:05] <arges> apw, rtg https://bugs.launchpad.net/ubuntu/+source/linux/+bug/905219
[15:05] <ubot2> Ubuntu bug 905219 in linux "Linux Kernel crash in Netfilter both in Natty (2.6.38-8-server) and oneiric(3.0.0-13-server/3.0.0-14-server) kernels" [Medium,Confirmed]
[15:24] <rtg> henrix, has the patch for drivers/media/rc/ene_ir.c been accepted upstream ?
[15:24] <henrix> rtg: no, i haven't submitted it yet
[15:24] <henrix> rtg: will do in a minute, i was just waiting for you guys to take a look just in case... :)
[15:25] <rtg> henrix, ack
[16:55] <janimo> apw, ogasawara when does ubuntu switch to a new upstream major release kernel? I did not see in the wiki when master-next with a new kernel based on upstream rcX replaces the stable one on master
[16:56] <ogasawara> janimo: well I uploaded our first v3.5-rc3 based kernel for Quantal today
[16:56] <ogasawara> janimo: can you point me to the wiki you are looking at?
[16:57] <ogasawara> janimo: I don't have it as a step in my upload process to update the wiki, but will do so in the future if that's what people are monitoring
[16:57] <janimo> ogasawara, thanks I just saw 3.5 is on master too (it was not yet a few hours ago when I last looked)
[16:58] <janimo> I meant the various kernel wiki pages in general
[16:58] <ogasawara> janimo: yep, I only pushed it this morning
[16:58] <janimo> the mentions of master-next I saw only related to SRUs where it is clearer when they are folded into master
[16:58]  * janimo goes on to rebase armadaxp on 3.5
[16:59] <ogasawara> janimo: indeed our master-next branches are for staging purposes only, nothing is official until it lands in master.  I'll try and get our wiki's cleaned up if they are misleading.
[17:00] <janimo> ogasawara, the SRU part of it is clear, just being in a -devel series I was not sure if there are hard rules as to when to go with Linus' next besides 'when it feels right' :)
[17:10] <cking> smb, I'm still waiting for one more set of results to pop out of my test box - I will get them to you tomorrow
[17:11] <smb> cking, Sure. By then I might have a brain again to understand... ;)
[17:11] <cking> hopefully I won't be vomiting up so much tomorrow either :-/
[17:12] <smb> cking, Lucky for me that does not transfer that well via email... But yeah, hope you get better
[17:12]  * cking heads for some rest
[18:27] <janimo> smb`, any reason why a canonical email address is enforced in maint-tools? Non-Canonical lemployees could find them useful, or even canonicalers with an @ubuntu.com address
[18:28] <janimo> smb`,  and by maint tools I mean the maintscripts in kteam-tools :)
[21:26] <dupondje> Somebody alive here that can help me with some usb power issue ?