[03:15] <harryc> How can I set btrfs to make one copy of the data and metadata on three drives of the same size?
[08:00]  * apw yawns
[08:28] <ppisati> cking: we can hear you
[08:29] <cking> i can't hear you, /me retries
[08:55] <usr_> hello everybody 
[08:55] <usr_> I face a problem with Ubuntu 13.04 sudden kernal panic http://s1.directupload.net/images/130530/pqrvetxb.jpg
[08:56] <usr_> Help me please its very serious problem It happens regularly !
[09:04] <smb> usr_, The you should file a bug (and if doing screen pictures, disable the flash ;)) From what is readable it looks like being caused by the wl module (proprietary driver for Broadcom wireless) and at least the kernel never got updated since release. So update the system before reporting any bugs.
[09:04] <usr_> I did 
[09:07] <smb> The picture still shows kernel 3.8.0-19.29 running. So either the wrong kernel runs or the picture is outdated.
[09:07] <usr_> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1181392
[09:07] <ubot2> Ubuntu bug 1181392 in linux (Ubuntu) "[Solved for me]Kernel Panic not syncing fatal exception in interrupt-solved for me, firmware-b43-lpphy-installer instead of b43-firmware solves the panic" [High,Confirmed]
[09:07] <usr_> this pic not of my computer 
[09:10] <smb> Then even more reason to open your own bug report with your information. The bug you mentioned is about the b43 module an would not even match the stacktrace.
[09:14] <usr_> No I faced the same problem 
[09:14] <usr_> I think I  the problem is solved :-) 
[09:17] <usr_> Thank you very much indeed 
[09:18] <usr_> and sorry about being rude 
[09:18] <usr_> Cya :-)
[10:02]  * ppisati goes out for a bi
[10:02] <ppisati> y
[10:02] <ppisati> t
[10:02] <ppisati> *bit
[10:21] <apw> a biyt sounds good to me
[13:30] <apw> tseliot, hey hows the dkms packags going, i think you fixed nvidia ...
[13:31] <tseliot> apw: I'm about to test (as in compile) my patch for nvidia-173. So far I've patched 319 and 304. I need to transition 310 and 313 to 319 (since I don't intend to maintain them). Then I'll move on to fglrx and broadcom
[13:32] <tseliot> the patches are quite big for nvidia...
[13:33] <apw> tseliot, how long do we think this will take for the others?  we're obviously chomping at the bit to get 3.10 in the archive
[13:35] <tseliot> apw: I was hoping to finish my work by the end of this week
[13:50] <apw> tseliot, thanks
[13:51] <tseliot> yw
[13:56] <ppisati> looks like i'm back...
[13:57] <smb> ppisati, Seems like. If you are not 3G ppisati 
[13:57] <ppisati> smb: nope
[13:58] <ppisati> smb: and i even upgraded the haswell box, finally! :)
[14:54] <jsalisbury> **
[14:54] <jsalisbury> ** Ubuntu Kernel Team Meeting - Today @ 17:00 UTC - #ubuntu-meeting
[14:54] <jsalisbury> **
[15:03] <rtg_> apw, I assume 'UBUNTU: SAUCE: ubuntu: overlayfs -- ovl_path_open should not take path reference' should also be applied to unstable ?
[15:03] <apw> rtg_, yes it should in deed, have i not done so, bad andy
[15:03] <apw> rtg_, and i'll get that upstream today
[15:03] <rtg_> apw, I just pushed it
[15:03] <apw> great
[15:05] <rtg_> apw, aufs has still not been updated upstream since March
[15:05] <apw> rtg_, hmmm let me check my email archives, in case it moved
[15:07] <apw> rtg_, ok there have been releases since then, i'm on the case
[15:07] <rtg_> apw, cool. I'm working on lttng
[15:07] <apw> you have more pain me thinks
[15:10] <apw> rtg_, ok it has moved, i'll get teh new one and update our shit and see fi it works any better
[15:11] <rtg_> apw, ack
[15:11] <rtg_> apw, where has it moved to ?
[15:11] <rtg_> it was git://aufs.git.sourceforge.net/gitroot/aufs/aufs3-standalone.git
[15:13] <apw> git://git.code.sf.net/p/aufs/aufs3-standalone
[15:13] <apw> rtg_, i'll get master-next and unstable cleaned up and see if they work
[15:27] <apw> b #is
[15:57] <tseliot> apw: just to give you an idea, this is the kind of fun it is to fix drivers for linux 3.10: http://paste.ubuntu.com/5777380/ ;)
[16:02] <apw> tseliot, they really hate you don't they
[16:05] <tseliot> apw: I've always had my suspicions... :D
[16:05] <apw> tseliot, you seen any reports of wl being pants with 3.9 ?
[16:05] <apw> tseliot, though as we won't be on 3.9 for long i guess ignore that till we are on 3.10
[16:06] <rtg_> and then 3.11
[16:06] <tseliot> apw: yes but I haven't looked into it yet and the only device I have for testing doesn't really work with the latest driver...
[16:07] <tseliot> hopefully they won't break the procfs functions again...
[16:07] <smb> Actually there seemed to be some saying even 3.8 has some issues
[16:07] <smb> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1181392
[16:07] <ubot2> Ubuntu bug 1181392 in linux (Ubuntu) "[Solved for me]Kernel Panic not syncing fatal exception in interrupt-solved for me, firmware-b43-lpphy-installer instead of b43-firmware solves the panic" [High,Confirmed]
[16:08] <smb> Of course them saying the problem is "fixed" by using b43 does not help
[16:08] <tseliot> smb: that would be the open driver, right?
[16:08] <smb> tseliot, yeah
[16:09] <tseliot> I'm talking about the binary driver
[16:09] <smb> And on the hw I got wl seemed to be running ok
[16:09] <smb> Well the bug reports _start_ with a backtrace of wl
[16:09] <smb> Then they switched to b43 and that was the "solution"
[16:10] <tseliot> heh
[16:17] <apw> for me wl seems to not be working well, like it sees nothing at all
[16:17] <apw> rmmod wl; modprobe brcmsmac seem to work ok for me
[16:18] <apw> we shall see how 3.10 fares with brcmsmac shortly
[16:19] <smb> apw, Thats good as long as your are not unlucky like me and brcmsmac does not support your particular chipset
[16:20] <mjg59> Which, given it only supports one chipset...
[16:20] <mjg59> Eh, ok, three.
[16:24] <apw> mjg59, yeah the wonderful world of broadcom ... sigh
[16:27] <mjg59> apw: And then they decided not to add new support because b43 already had support. But we can't distribute the b43 firmware.
[16:29] <smb> and then there is not only one but the lpphy and the other...
[16:36] <tseliot> nice, it's even worse than I thought :D
[16:37] <apw> mjg59, oh how lovely indeed
[16:38] <mjg59> Yeah, pretty easy to get the impression that it was a driver written to meet a contractual obligation or something...
[16:49]  * smb remembers daily nag-time: infinity: crash? apw: xen?
[16:49]  * apw whines
[16:50] <apw> rtg_, ogasawara, aufs updated in unstable and seems to at least surviving touch testing
[16:50] <ogasawara> apw: good to know, thanks
[16:50] <rtg_> apw, cool. I'm about to push alx from linux-next as well
[16:52] <apw> rtg_, sweet, i have already pushed so you should be good whenever
[16:52] <rtg_> apw, ack
[16:53] <apw> smb, it is 4.2.1 we are looking at yes 
[16:54] <smb> apw, Yeah, the 4.2.1-2ubuntu1 iirc only
[16:54] <smb> Holding off with the 4.2.2 until maybe there is a Debian origin
[17:00] <jsalisbury> ##
[17:00] <jsalisbury> ## Meeting starting now
[17:00] <jsalisbury> ##
[17:09]  * ppisati -> gym
[17:37]  * rtg_ -> lunch
[17:43] <jsalisbury> sforshee, you mind taking a look at bug 1192259
[17:43] <ubot2> Launchpad bug 1192259 in linux (Ubuntu) "wireless access point won't connect- changed bandwidth in a way we can't support - disconnect" [High,Confirmed] https://launchpad.net/bugs/1192259
[18:26] <rtg_> ogasawara, do you  know how the Package information Maintainer URL is generated ? for example, on https://launchpad.net/ubuntu/+source/linux it _says_ 'Ubuntu Kernel team', but actually points to https://launchpad.net/~kernel-team (which is wrong).
[18:26] <ogasawara> rtg_: heh, I was looking at that very issue this morning and trying to figure it out
[18:26] <ogasawara> rtg_: but then I got distracted of course
[18:27] <ogasawara> rtg_: I wasn't able to determine where we could update it
[18:27] <ogasawara> rtg_: is it in our kernel source?
[18:27] <rtg_> ogasawara, Maintainer: Ubuntu Kernel Team <kernel-team@lists.ubuntu.com>
[18:27] <rtg_> thats from our control info
[18:28] <ogasawara> that must be it
[18:28] <rtg_> a launchpad algorithm that attempts to deduce the LP ID from that ?
[18:32] <ogasawara> it must, it's clearly wrong in the control file as it is
[18:33] <rtg_> well, the email address is correct.
[18:46] <ogasawara> ah right, that email address is correct, I keep thinking its ubuntu-kernel-team@
[19:11] <tjaalton> 3.5.0-35.56 is now in quantal-proposed?
[19:12] <tjaalton> oh pre-proposed..
[19:14] <tjaalton> I'll probably revert the abi-break in i915_hsw, because it'll make i915-dkms ftbfs. should've seen that coming..
[19:16] <tjaalton> so that drm_mm_* is again appended with _hsw, makes retiring the dkms smoother
[20:49] <rtg_> ppisati, http://permalink.gmane.org/gmane.linux.network/271538
[21:40]  * rtg_ -> EOD