/srv/irclogs.ubuntu.com/2013/01/29/#ubuntu-kernel.txt

=== chiluk_away is now known as chiluk
ppisatimoin07:04
smbagain... :-P08:16
smbapw, one way fail08:50
smbapw, meaning we hear you but not other way round :)08:50
apwsmb, situation normal, thank you pulse08:54
smbAs normal as any situation involving PA can be08:54
caribousmb: morning09:18
caribousmb: have you tried to use crash 6.1.0 on a Raring kernel ?09:18
caribousmb: I get "(no debugging symbols found)" on the 3.8.0.2 ddebs09:19
smbcaribou, morning. maybe not. I honestly cannot remember...09:19
caribousmb: ok, just wanted to check; I'll investigate09:19
smbThough potentially I did with 3.7 based kernels. 09:20
smbcaribou, I would try to see how the last 3.7 we had works09:20
caribousmb: well, the ddebs are not available for 3.7 kernels in the archive09:22
smbcaribou, Doh! Seems we would rely on whatever copy you or arges have. Since we cannot keep ours from vanishing.09:23
caribousmb: I'll check what I have09:23
smbOr re-build a kernel from git based on a tag09:23
diwicIf we have bugs in 12.04 that are fixed by using the -lts-quantal kernel, would it be appropriate just to advice people to move to that kernel or should one spend time trying to backport fixes to 3.2?09:25
infinitydiwic: Depends on the bug.09:30
infinitydiwic: If it's flat-out hardware enablement, asking them to switch to our HWE stack is reasonable.  If it's rather something broken in 3.2, finding the commit that fixes it and pulling it into 3.2 is the right thing, IMO.09:31
infinitydiwic: Keep in mind, also, that we don't have lts-backport on !x86.  So, if it's a bug that's not specific to some x86 hardware, not fixing it in 3.2 doesn't help, say, ARM users.09:32
infinityThat was a lot of negatives.09:32
diwicinfinity, hmm, ok09:33
caribousmb: ok, I found the ddebs, I just no longer have the original 3.7 kernel package09:33
smbcaribou, Those should be on LP09:34
caribousmb: I have the 3.7.0.4 ddeb09:34
caribousmb: ok, got it09:35
smbcaribou, https://launchpad.net/ubuntu/raring/+source/linux/3.7.0-7.1509:35
caribousmb: ok, got everything I need, I'll let you know what I find09:45
smbcaribou, cool. thanks09:46
=== lantizia is now known as Lantizia
apwogra_, about ?  i have a kernel i'd like you to test if you have a chance10:13
ogra_now i am (i got a sick cat and need to spend 1-2h at the vet every day this week)10:23
ogra_apw, ^^10:23
apwogra_, what fun10:24
ogra_yeah10:24
janimoapw, ogra_  said he'll land the userspace the orientation changes as soon as the kernel input side is changed for the nexus10:29
apwogra_, ok ... so ...10:29
janimoI am fine with either chicken or egg first though, but users will need to be fully upgraded to have it working10:29
apwogra_, ok ... once you have tested that one, i'll spin you another with janimos orientation change10:31
apwogra_, so you can test your orientation fixes :)10:31
apwand when you are happy we can upload together10:31
ogra_given that the arm livefs builder is dead since days, i dont think we need to worry to much about ahlf a day delay between the uploads10:31
ogra_ok10:31
ogra_apw, perfect !10:33
ogra_i wonder why i still saw the wifi messages in my build10:33
apwogra_, ok good.  i'll get your new one built in a minute10:33
ogra_totally silent with yours10:33
ogra_janimo, do you have the acceld changes handy ?10:33
janimoogra_, yes, I'll paste them again, a moment10:34
apwogra_, and note that the login screen doesn't have rotate10:34
janimoogra_, http://paste.ubuntu.com/1585333/10:34
apwog10:35
apwogra_, that fixes things once you are logged in, but at the password prompt ?10:35
ogra_apw, it will, as soon as i dropped the forced rotate from xorg.conf ;)10:35
janimoI think we have an xrotate call somewhere there, which needs to be dropped10:35
apwheh great10:35
ogra_janimo, line 6 is wrong :P10:37
janimowhich is line 6? I think I only shuffled the matrix orders10:38
janimoah, DIR='right'10:38
janimois that the default orientation? Indeed that right is wrong10:38
ogra_right 10:39
ogra_*grin*10:39
janimothat's why first tilt did not work I guess :)10:39
ogra_doesnt od any harm, but you need to rotate once to actually activate the rotation if thats wrong10:39
ogra_right, its one more tilt you need... i had the same issue in my foirst upload10:40
ogra_grrr10:54
ogra_i cant get the xorg.conf right :/10:54
apwogra_, seemed to work for me11:32
ogra_great, uploaded the changes11:32
ppisatihas it ever happened to you that, during a bisect with, with  commit X being good, and commit X +  Y being bad14:45
ppisatigit bisect goes _behind_ commit X instead of picking one in between X and X+Y?14:46
einonmppisati:  could be due to branching between X & Y?14:55
rtgppisati, yeah, make sure its a linear range14:56
apwogra_, ok all of those changes are in the -release pocket now15:16
ogra_yay15:18
* ogasawara back in 2015:39
tseliotapw: what's the source package for linux-image-3.1.10-9-nexus7 ?15:39
apwlinux-nexus715:40
apwtseliot, ^^15:40
tseliotapw: ok, thanks15:40
apwtseliot, need something ?15:40
tseliotapw: no, I just needed to know the name as I'm adding kernel names in my test suite for ubuntu-drivers-common so that I can tests for problems with my code and these name schemes15:42
ogra_tseliot, there is also linux-ac100 (tegra2)15:46
tseliotapw, ogra_: ok and do you know if linux-ti-omap4 has linux-headers-ti-omap4 etc.? (With this name scheme)?15:47
ogra_it should, yes15:48
apwit should be linux-headers-omap415:48
apwand linux-image-omap415:48
ogra_oh, right, the -ti is only in the source 15:48
apwti-omap4 is the source package name15:48
apw-omap4 is the flavour name15:48
tseliotok, thanks15:49
smbarges, Out of interest, is the xen package again flagged broken in raring +1? Right now it won't compile in my sbuild chroots (even the version you uploaded). And as a second thing, can I prevent others from fixing it while I look? ;)16:18
jsalisbury##16:39
jsalisbury## Kernel team meeting today @ 17:00 UTC16:39
jsalisbury##16:39
zequenceapw: Am I expected to set the bug reports for regression-testing and/or Verification-testing to "fix released"?16:59
=== bjf[afk] is now known as bjf
argesrtg: was the bug you were seeing, you could suspend with pm-suspend, but there was no way to do it via the menu, or Fn-F7 (on mythinkpad)17:02
apwinfinity, i forget already what lowlatency testing was ... can you remind17:02
apwie when we do the regression testing what we are meant to set to what17:02
rtgarges, I was just closing the lid. haven't really explored much further, but am uploading a bug report17:03
argesrtg: ok. i might be hitting the same thing17:03
infinityapw: If no lowlatency-specific bugs, mark verification-testing Fix Released if the parent kernel is done.17:04
infinityapw: If specific bugs, verify, then do above.17:04
infinityapw: For smoke testing, mark regressing-testing Fix Released, and tag the bug "qa-testing-passed" to appease the bot.17:05
apwzequence, ^^ :)17:05
infinityarges: If pm-suspend works, but various buttons and UI triggers don't, gnome-settings-daemon is probably wedged.17:06
argeshmm17:06
zequenceapw: Thanks. I'll ask infinity some more, if I didn't get it yet :)17:06
apwzequence, so this has no specific patches for lowlatency it is a pure rebase17:06
apwzequence, so that means vefication-testing is not needed, so it can go Fix Released for no actions17:07
rtginfinity, pm-suspends works even after upowerd augers in17:07
zequenceapw: Ok. Good17:07
zequenceapw: But, I still add the tag?17:07
zequenceDo I add it in a comment?17:08
infinityrtg: pm-suspend should always work, barring kernel bugs or massive userspace sadness.17:08
infinityrtg: But most of the higher level plumbing for this relies on gnome-settings-daemon being alive and willing to talk pleasantly to you.17:08
rtginfinity, right, 'cause I think about all it does these days is blat something into sysfs17:08
infinityrtg: Which doesn't sound like your sort of date.17:08
apwzequence, the otehr testing one once they are boot tested, mark regression-testing fix-released and add a tag in the tags field at the top as above17:09
zequenceapw: So, this should be right then17:12
zequencehttps://bugs.launchpad.net/kernel-sru-workflow/regression-testing/+bug/110514617:12
ubot2Ubuntu bug 1105146 in Kernel SRU Workflow verification-testing "linux-lowlatency: 3.5.0-23.22 -proposed tracker" [Undecided,In progress]17:12
apwzequence, well verification-testing is done as there is none,17:12
* herton -> back in 1.5h17:13
caribousmb: FYI, the debug symbols were fine in he 3.7 kernel in Raring17:13
smbcaribou, Ok. Thanks. Sounds like yet another thing moved around17:14
=== jsalisbury changed the topic of #ubuntu-kernel to: Home: https://wiki.ubuntu.com/Kernel/ || Ubuntu Kernel Team Meeting - Tues February 5th, 2013 - 17:00 UTC || If you have a question just ask, and do wait around for an answer!
apwrtg, could you add me and cjw to the bug please, so we can see it17:22
rtgapw, ack17:22
rtgapw, done17:23
jsalisburyrtg, is there a public bug?  Just wondering in case we get a bunch of duplicate reports.  Else, I can see if I can reproduce it and create a public report.17:34
rtgjsalisbury, it'll be public as soon as the apport retracer runs17:34
jsalisburyrtg, ack17:34
* ppisati goes out to find some food, before the food finds me17:36
smbapw, arges, So the xen build fail was actually two parts. One (for which I found reference on xen-devel) is that the check for needing librt was using clock_gettime but that is not requiring it anymore. The other (for which I could not yet be bothered to search) is some part using ulong wihtout including sys/types.h (which probably something else used to do).18:00
smbarges, I will include that in the stuff I am working on, so you won't have to worry about that ftbs :)18:01
argessmb: ok great! let me know if there is anything i can do to help18:01
smbarges, Just the usual grinding work for youknowwhat issues for the youknowho team... ;-P18:02
arges: )18:02
* rtg -> lunch18:02
apwrtg, bjf, there will be a new upowerd in the archive 'immently' which should fix things up18:21
bjfapw, ack, i see there have been quite a few bugs filed against it18:21
apwbjf, well it at least fixes my 32bit systems18:45
* smb -> donefortheday18:47
apwsmb, done in by the day18:48
smbapw, Or so I guess :)18:48
=== arges is now known as arges_
zequenceAh, I can be really slow sometimes19:41
zequenceAnyway, I think I got the bug handling for next time19:41
apwrtg, you pushed just before me dammit, but you forgot the acks for the second one20:05
rtghmm, I thought I got both.20:05
apwrtg, and both are missing the bug numbers20:06
rtgapw, drat. why don't you push yours then since I'm clearly incompetent right now :)20:06
rtgI didn't tag yet20:07
apw:) ack20:07
apwrtg, yeah i'll wrapit and upload it20:07
rtgapw, ok20:07
rtgapw, I'm about done for the day anyways20:07
apwrtg np20:08
* rtg is outta here. back on Feb 5.20:09
=== arges_ is now known as arges
infinitysmb: If the only reason it links librt is for clock_gettime, it doesn't need librt.20:34
infinitysmb: (Though, --as-needed linking will sort that out anyway)20:34
argescomputer suspends properly again! thanks21:24
=== yofel_ is now known as yofel
infinityjjohansen: You have a few pending security-signoff tasks for the current SRU round still, FYI.22:54
jjohanseninfinity: yep thanks for the poke, I'll get them done22:55
infinityjjohansen: All good.  I'm sure you'll get them done before cert finishes. :)22:56

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!