[03:42] <owlman> Hi, is there a git branch with only the packaging patches for the mainline kernels (e.g. http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.1-rc5-unstable/) publically available?
[03:53] <owlman> i.e. the 3 patch files 000?*
[07:47] <apw> owlman, no they are not in a public git tree, just in the directory
[10:11] <thoma> Someone knows a SIMPLE way to collect MCE information ?
[10:23] <genkgo> jsalisbury: unfortunately, the hyperv is still there. could we collect more information somehow? i am not very experienced with kernel. e.g. a backtrace. i now only use dmesg.
[12:26] <apw> genkgo, do you mean the "going offline on backup issue is still there" ?
[13:06] <genkgo> apw: yes
[13:06] <genkgo> apw: but it took a while to trigger
[13:07] <genkgo> apw: much longer than before
[13:08] <trippeh> Hm. wireless-regdb is still way out of date
[13:08] <apw> trippeh, yep we are working on that right now
[13:09] <trippeh> wohoo :)
[13:09] <trippeh> had to disable VHT80 on the network here, or else iwl keeps downgrading to 802.11n.
[13:23] <genkgo> apw: is there any method to do some sort of trace? e.g. to see where an error is coming, to exactly see why the system goes into read-only. i would like to add more information than just my dmesg, because that one is always the same.
[13:24] <apw> genkgo, i suspect that that contains the real info ... and thaat implies the fix just made the window smaller not removed it
[13:27] <genkgo> apw: i guess so
[13:28] <genkgo> apw: maybe it also proves why testing with a development machine is so hard with this problem. the io pattern of a testing machine does not match a production machine and therefore the window is too small on a testing machine. hence, it is likely the bug to manifest faster on a production.
[13:57] <owlman> apw: thanks.
[13:59] <owlman> I found the git://kernel.ubuntu.com/ubuntu/unstable.git repository. Where is the wily master-next repo?
[14:03] <apw> git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/wily
[14:03] <owlman> awesome, thanks
[14:29] <jsalisbury> genkgo, thanks for updated the bug.  We'll see what the response is from jrp and see if other commits are needed.
[14:30] <genkgo> jsalisbury: yes, let's see. i am also wondering how they have done their tests
[14:31] <genkgo> jsalisbury: we are pushing limits of course by creating snapshots every half an hour
[14:31] <jsalisbury> genkgo, right