[07:16] <hyperair> hi. has anyone seen the 3.18 kernel hang bug?
[07:16] <hyperair> the one that wedges everything and disables everything except alt+sysrq+b
[07:16]  * hyperair thinks it's the same as the hpet bug
[09:08] <apw> hyperair, not seen any particular mention of that no
[09:08] <hyperair> damn
[09:08] <hyperair> it keeps hitting me, and for some reason nobody else sees it
[09:08]  * hyperair sighs
[09:08] <apw> hyperair, does it happen with the v3.19 in the CKT PPA?  as that will be our kernel shortly anyhow
[09:09] <hyperair> apw: dunno, i just compiled my 3.19 kernel. haven't rebooted yet
[09:09] <cristian_c> hello
[09:09] <cristian_c> apw, Have you read the paste?
[09:36] <apw> cristian_c, i have no indication in my backscroll that you told me where it was after you said you'd do it; but i have been travelling
[09:37] <cristian_c> apw, http://pastebin.com/TVmxXzUZ
[09:39] <apw> cristian_c, that looks comprehensive to me
[09:39] <cristian_c> ok
[10:00] <cristian_c> apw, ok, also, I've to open an upstream report for a regression
[10:00] <cristian_c> related to this bug
[10:01] <cristian_c> in total, two reports
[11:01] <cristian_c> I must collect info in kernel format for an upstream bug report
[11:02] <cristian_c> the upstream bug report should be about a regression
[11:02] <cristian_c> How can I locate the specific commit, exactly?
[11:02] <cristian_c> Any ideas?
[11:18] <apw> cristian_c, the specific commit which introduced the regression ?
[11:20] <cristian_c> apw, yes
[11:20] <cristian_c> correct
[11:20] <cristian_c> I think they request the exact kernel version
[11:23] <apw> the exact kernel version is easier, you would use the mainline builds to narrow in on it, in a bisection style
[11:24] <cristian_c> apw, ok, so have I to try many kernel until I find the nearest previous version and the nearest next version?
[11:25] <cristian_c> to the kernel version has introduced the regression
[11:26] <apw> cristian_c, right exactly that, but you do it in divide-and-conquor manner, so
[11:26] <cristian_c> ok
[11:26] <apw> say you know it worked in 3.2 and not 3.16 you'd pick like 3.9 first and then you have gotten rid of half either result
[11:27] <apw> cristian_c, i would use the prebuilt test kernels in the ubuntu mainline archive, so you don't have to make any
[11:27] <cristian_c> 3.8.0 is not affected by the regresssion
[11:28] <cristian_c> apw, can I use the prebuilt kernels even if I've to report in the upstrem?
[11:28] <cristian_c> *to the
[11:28] <cristian_c> to locate the regression version
[11:29] <cristian_c> apw, usually I download the kernel version from mainline kernel archive
[11:29] <cristian_c> http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D
[11:30] <cristian_c> and I always install three packages: headers, headers-generic, linux-image
[11:50] <apw> cristian_c, yes, those kernels are mainline code exactly, there is no ubuntu patches on those
[11:52] <cristian_c> ok, usually I install the mainline .deb packages
[11:52] <cristian_c> for the prebuilt is the same , I think
[11:52] <cristian_c> *prebuilt kernels
[11:52] <apw> i believe we are talking about the same ones yes, those are suitible for a bisect, and for reporting exact versions to upstream
[11:52] <apw> as they are unmodified upstream code, built on ubuntu for debugging
[12:08] <cristian_c> apw, anyway, I've to identifying the mantainer
[12:09] <cristian_c> If the bug is not in USB, the first step in reporting a bug upstream is to find the maintainer of the driver for the bug from the MAINTAINERS list. Here are some typical scenarios and suggested mailing list and procedures: 
[12:09] <cristian_c> in the first case
[12:09] <cristian_c> If this is a regression, CC the submitter of the regression commit. 
[12:09] <cristian_c> in the second case
[12:10] <cristian_c> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/MAINTAINERS
[12:10] <apw> if you can find the before and after mainline commit, we can ask joe to do a proper bisect for you to get the actual commit for it
[12:12] <cristian_c> I'll try
[14:44] <sarnex> hi guys, i noticed the automatic DEB build of the 3.19 kernel on kernel.ubuntu.org failed, is this a known issue?
[14:47] <apw> sarnex, failed how so ?
[14:47] <sarnex> apw: 	BUILD.LOG.amd64 and BUILD.LOG.i386 say "Access not authroized" and there are no debs in the filder
[14:48] <sarnex> apw:  see here http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19-vivid/
[14:54] <apw> sarnex, thanks, sorting
[14:54] <sarnex> apw: awesome thanks