=== smb` is now known as smb [07:21] apw, Yup it was me. [07:23] apw, you still have broken sound, right? Or did it resolve itself? [08:12] smb, heh ... ok [08:13] diwic, i think that the condition my system is in now it is not happening [08:13] diwic, i am suspicious it is power related, being on battery or some such, but not being able [08:13] diwic, to get fully updated easily is hampering my efforts to exclude cause [08:17] apw, anyway, I saw two more bugs related to hdmi audio this morning. One was an oops and I'm about to write a patch for it [08:20] sounds good, i'll assume my issue is unreproducible till it isn't [08:59] diwic, get the patches out, they can go in the first SRU [08:59] apw, I just posted it to the list [09:00] diwic, always ahead of me, heh [09:00] apw, but sigh, maybe I need to do the the SRU essay too [09:01] diwic, yep after kernel freeze one needs that anyhow basically [09:02] * ppisati hates pollen [09:05] ppisati, pollen already? [09:06] apw: yes, pollen f***ing pollen! [09:06] apw: i'm sneezing like there's no tomorrow [09:06] sounds lovely [09:06] more drugs for you [09:06] nope [09:07] i don't like to mess pills :) [09:07] ppisati, http://www.snopes.com/science/stats/sneeze.asp [09:07] heh i think if i was alergic to the world around me i'd be popping them [09:09] "it's the time for the sneezin' of love" [09:09] oh my... [09:09] a histamine reaction isn't fun, you don't have to mess with many pills to get it back to normal :p [09:11] ohsix: i was kidding dude... [10:23] ogra_: weren't you talking about modules on N4? [10:26] was i ? [10:26] what do you want to know ? [10:27] why don' we use the new N4 kernel in the phablet img? [10:28] i think that still needs some changes to the android build system ... [10:28] i know rsalveti committed something already, but i'm not sure thats enough yet [10:29] also there is work going on to flip the containers which means we'll use an ubuntu initrd, i guess that needs to be done as well before we can change === ara_ is now known as ara [10:31] ogra_: i'm reading irc logs [10:33] oh, and there needs to be some way of ugrading the kernel ... we'll need to research if flash-kernel really makes sense (if we dont flip the containers it will be better to use abootimg directly) [10:34] no containers flip? doesn't sound good to me [10:34] well, we dont know if it will work yet [10:34] ChickenCutLass is still exploring [12:09] * henrix -> food [12:26] ogra_, what are we using from android other than the kernel anyhow [12:26] apw, HAL, binary drivers, the input and media layers ... [12:27] pretty mich everything that talks to HW directly [12:34] ogra: which would dictate more or less an Android API for app developers? [12:36] amitk, nope, there is libhybris in android and the ubuntu platform-api sitting on top of it [12:36] so devs need to use the api [12:37] s/api/ubuntu api/ [13:48] ogra_: ppisati: I sent a patch yesterday to allow reusing the kernel available in ubuntu [13:48] and also enabling that for nexus 4, waiting sergio to review & apply it [14:02] rtg: apw ^ [14:02] ppisati, yep, saw that. [14:24] ppisati, good news indeed [14:30] sconklin: do you think its worth starting bisecting the Q bug in parallel? [14:31] henrix: I think we need to find an in-house reproducer machine [14:32] I can't see any commonality in the hardware in the various bugs [14:32] except that they are all filed against the 64 bit kernel [14:33] sconklin, henrix i think some of the people in bug 1140716 are having the same problem [14:33] Launchpad bug 1140716 in linux-lts-quantal (Ubuntu Precise) "[regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge" [Critical,Confirmed] https://launchpad.net/bugs/1140716 [14:33] whats the bug [14:33] apw: bug #1167114 and bug #1169380 [14:33] Launchpad bug 1167114 in linux (Ubuntu) "Ubuntu Kernel 3.5.0-27 does not boot" [High,Confirmed] https://launchpad.net/bugs/1167114 [14:33] Launchpad bug 1169380 in linux (Ubuntu) "Alienware M11x fails to boot with 3.2.40 upgrade" [High,Confirmed] https://launchpad.net/bugs/1169380 [14:34] henrix, sconklin, actually i won't be surprised if we are looking at multiple issues here [14:34] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1169304 [14:34] Launchpad bug 1169304 in linux (Ubuntu) "3.2.0-40-generic hanging Lenovo T420 on boot" [High,Confirmed] [14:34] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1168961 [14:34] Launchpad bug 1168961 in linux (Ubuntu) "Linux kernel 3.2.0-40-generic update causes regression, does not boot anymore" [High,Incomplete] [14:34] bjf: yep, i'm almost sure we are due to different feedback from different users [14:35] 1168961 has only one graphics card [14:40] kamal, oooh, congrats for the new job ... ! [14:48] apw, is there any reason to try and keep our enforcer rules in sync between the phablet kernels and the others? [14:54] sforshee, it is less sensible where the base versions do not match [14:54] where they do we should be trying to make a set of rules representing what we intend [14:54] sconklin, henrix, i note that at least one has a call trace starting right after a failure to initialise the GART [14:55] apw, thanks. The base versions don't match, so now I can take the easy route and just delete the rule I don't want :-) [14:56] apw: that helps, let me dig through the pile of graphics patches in the last stable update [14:57] sforshee, do you know anything about what bumblebee actually changes [14:57] as peple on the same bug are saying that installing that is sorting them out, and there is a definate theme of sandybridge (integrated intel graphics) + a-n-other card in these machines (first bug at least) [14:57] apw, not a clue, sorry [14:57] apw, I suppose it's likely to power on the secondary graphics device at least [15:10] anyone happen to know where the fix for 957298 is supposed to be? it doesn't appear to be in 13.04 (3.8.0-18) [15:10] and the workaround stopped working after 12.10 [15:11] calc, looking [15:11] it mentions that 3.9 should help resolve the issue, but the bug was closed out as fixed already [15:32] calc, 3.8.0-19.29 has the latest upstream stable commits in it. that's in -proposed you could try that to see if it fixes your issue. you will want to just grab the .debs for the kernel and not enable -proposed for raring as that may pull in other packages that are not ready [15:37] bjf: ok thanks i'll that now, when losing interrupts like a few seconds ago i can't even type, heh [15:37] er i'll try that now [15:45] * calc brb rebooting [15:48] sconklin: i give up trying to reproduce the bug. tried *every* x86 box i have around with both 3.2.0-40.64 and 3.5.0-27.46. no luck [15:49] I just posted another bisection to the one bug that had a reported failure from the first bisection, and I'm looking at some patches in that first bisection result range [15:49] henrix: thanks for trying [15:49] np [15:50] incidentall, that is bug #1169380 [15:50] Launchpad bug 1169380 in linux (Ubuntu) "Alienware M11x fails to boot with 3.2.40 upgrade" [High,Confirmed] https://launchpad.net/bugs/1169380 [15:51] sconklin: yep, seen it. lets wait and see... [15:51] bjf: working atm, will watch it and see if it starts eating cpu again [15:52] calc, ack, good luck :-) [15:54] bjf: thanks for the help :) [15:54] henrix: there are two patches having to do with graphics transition from grub2 to kernel. One clears all buffer attributes, and I wonder if it's perhaps breaking the dual display case. But that's speculation [15:55] * calc leaving going to do suspend/resume testing, etc, bbl [15:56] sconklin: also, there are a few regression fixes in the -proposed kernels (both P and Q). [15:56] I found a suspicious patch [15:57] http://kernel.opensuse.org/cgit/kernel/commit/?id=e93a9a868792ad71cdd09d75e5a02d8067473c4e [15:57] that's the upstream one [15:58] henrix: but there are several others, which touch fb driver, or have to do with grub2->kernel graphics transition [15:58] sconklin: ah, interesting. and that commit is on both kernels [15:59] any patch with "band-aid" in the description is suspect immediately [15:59] heh, true :) [16:01] the patches I found are pretty spread out through the commits between known good and bad, so I don;t think we can do much better than just letting the bisection run its course right now. After one or two more we may be able to tell. [16:01] sconklin: fortunately, the bug reporters seem to be quite responsive [16:02] small miracles [16:16] bjf: seems that doesn't fix the issue :-\ [16:16] calc, sorry to hear that [16:17] bjf: is there an ppa for testing newer kernels? i could try one of those to see if it helps [16:18] calc, the -proposed is the newest [16:19] henrix: I'm going to start bisecting for quantal bug #1167114 also [16:19] Launchpad bug 1167114 in linux (Ubuntu) "Ubuntu Kernel 3.5.0-27 does not boot" [High,Confirmed] https://launchpad.net/bugs/1167114 [16:19] sconklin: ack [16:19] bjf: ok [17:16] hello.. I joined to inquire whether you guys have considered enabling config_chromeos_laptop in your 3.9.0 builds? [17:17] Jope, CONFIG_CHROMEOS_LAPTOP=m is in our git repo, but apw's mainline build may not have it turned on. [17:18] ok, that's nice.. so just that I don't misunderstand, does this mean it will eventually make it to the mainline too? [17:18] 3.9 is built against raring, so if the config is in master-next it would likely get turned on in a mainline build; unless they moved it or somethig dumb [17:19] rtg, when did it get turned on in raring ? [17:19] apw, not asure if it exists in raring [17:19] apw, in fact it didn't appear until 3.9 [17:19] rtg, "CONFIG_CHROMEOS_LAPTOP=m is in our git repo," ... which one [17:20] oh unstable-3.9 ? [17:20] apw, unstable-3.9 [17:20] so yeah when you cut SS repo we would start building using that, and it would be on in later mainline builds [17:20] yep [17:20] i wonder when we will know what it is goibng to be called [17:26] ok, cheers :-) [17:26] hopefully I don't have to build too many kernels of my own then [17:27] where has the morning gone ? /me -> lunch [17:27] where has my broadband gone, oh, i know that [18:31] bjf: it appears to be fixed in 3.9rc7 and I updated the bug report noting that. I'm willing to test any kernels in the effort to get it fixed properly for 13.04 as well, otherwise the bug report probably should stay open until 13.10. [20:13] sforshee, uploaded the N4 kernel with your FTRACE config changes. [20:24] * rtg -> EOD === kentb is now known as kentb-out === hggdh_ is now known as hggdh