[06:13] moin [07:13] morning [07:28] * smb enjoys non-charcoaled coffee... [07:31] moving up in the world, hey? [07:31] * ppisati actually likes the American coffee... [07:32] ppisati, pervert! ;) [07:33] yes i am :) [07:33] jk-, More "right" [07:35] next it'll be non-charcoaled charcoal [07:35] rsync after a travel takes forever... [07:37] jk-, Hm, I wonder whether that would work so well on the next barbecue... [07:37] ppisati, Was ok for me, just the full backup that followed still runs... [07:38] * smb wonders whether Bryan will make it back... [07:40] seems Bryan has *a lot* of luck with airplanes lately... :) [07:40] i know these words will condemn me to God knows what for *my* next travel anyway... [07:41] ppisati, Probably. :) But yeah, birds, sick people... He works hard to become the next Colin... ;) [07:52] "No space left on device" [07:52] ARGHHHHHHHHHHHHHHHHHHHHH [07:52] btrfs, or *actually* running out of space? :P [08:02] the second one [08:05] ppisati, You should not have downloaded so much p... err data... ;-P [08:05] is there a know issue with resume from suspend with kernel 3.5.0-5 ? [08:06] jibel, I think we heard the one or the other curse a bit about it recently... [08:07] smb, should I file a bug or it's on the team's radar already ? [08:09] jibel, A bug report in general would be good but maybe you can wait until apw gets conscious and ask him whether he already knows of one filed. [08:17] smb, ack, will do as soon as I can bring down my machine [08:44] jibel, i don't know of a specific bug report as yet. cirtainly its affecting my travel laptop as well [08:45] jibel, would "black screen on resume machine may be alive unsure" describe what you are seeing? [08:45] thats what i am seeing about 3-4 resumes on -5.5, -4.4 was ok [08:47] apw, yes, it describes what I'm seeing. [08:47] and no reaction from keyboard e.g caps lock led [09:10] jibel ok i have filed bug #1027828 [09:10] Launchpad bug 1027828 in linux "[Quantal] black screen on resume on 3.5.0-5.5 (regression from 3.5.0-4.4)" [Undecided,New] https://launchpad.net/bugs/1027828 [09:13] apw, confirmed, thanks [09:14] * apw seems to be able to hit it all the time, so hopefully we can find it pretty quick [09:15] net: dont use __netdev_alloc_skb for bounce buffer [09:15] smb, i see your net thing made it in for v3.5 [09:16] apw, yep [09:17] apw, Just the scheduler thing still not pulled for right now [09:34] * apw gets building some test kernels, why does resync home take soooo long [09:39] * smb found it to be relatively quick... starts wondering whether all went back... [09:39] * apw was more thining the mental sync back :) [09:40] ah [09:40] * smb probably is not back then [09:41] apw: I see those black screens on suspend too, with the latest from X-swat PPA [09:42] on precise [09:43] amitk, what kernel is in there? [09:44] my issue is definatly a regression -4.4 -> -5.5 [09:44] apw: 3.5.0-5 [09:44] amitk, ok thats fine (and likely expected) then [09:44] * apw has his suspicio [09:45] * apw has his suspicions about a s/r fix that went in there [09:45] apw: so the quantal kernel on precise isn't really the latest quantal kernel? (sorry not running quantal yet) [09:45] amitk, no it is the latest and thats where i am seeing this regression too [09:46] apw: the kernel makes resumes a _lot_ faster on macbook pro, when it does work [09:47] amitk, interesting [10:16] yawn [10:21] cking, morning [10:21] * cking notes that jet lag sucks [10:22] cking, indeed so [10:48] cking, the fwts cpu_scaling test tests all the frequency governors, right? [10:49] brendand, which specific test are you referring to? [10:50] cpufreq? [10:51] cking, yeah - cpufreq would be the name of the test in fwts [10:54] brendand, it basically figures out the set of CPU freqs available and steps through each one on each CPU. It does NOT test the different governors [10:56] cking, thanks [11:32] * henrix is out for ~30mins (errands...) [11:37] jibel, ok the latest 3.5 based kernel no longer reproduces the s/r hang for me, could you try the kernel at this url and see if it works for you too pls: http://people.canonical.com/~apw/lp1027828-quantal/ [11:37] (remember you need an -extra package too) === shadeslayer is now known as shadeslayer_ === shadeslayer_ is now known as shadeslayer === yofel_ is now known as yofel [12:59] apw: haven't tried your kernel yet, but I built a 3.5 vanilla end of last week, and it fixed the s/r hangs for /me [12:59] jjohansen, then i suspect mine will too [12:59] apw: yeah, I expect it will, I will test it in a bit [13:08] apw: sounds like we should squeeze in an upload for Alpha3 [13:08] please look at bug 1027524 - failure on QRT tests on omap-hf [13:08] Launchpad bug 1027524 in linux-ti-omap4 "QRT failed on test_072_config_debug_rodata and test_072_strict_devmem" [Undecided,New] https://launchpad.net/bugs/1027524 === shadeslayer is now known as shadeslayer_ === shadeslayer_ is now known as shadeslayer [13:36] ogasawara, yeah for me its a bit improvement over the -rc7 kernel [13:37] if we can persuade jjohansen to test soonest then we can get the show on the road [13:37] apw: I've kick off some build tests in the mean time [13:37] ogasawara, also i have pushed a 'tim did the rebase in on top' [13:37] apw: yep saw that, thanks [13:38] ogasawara, if this does fix it for jjohansen as well then we should add that bug number to the rebase commit [13:38] apw: ack [13:38] jibel, did you get to test that kernel at all? we would like to get some confirmations to justify an upload [13:39] apw: I am a little worried about the config vomit and firmware bits tim shoved in, so it would be good to get a little extra testing all around. [13:39] apw, oh, forgot to resume the mac, doing now [13:39] apw, it works [13:40] apw, any other verification you'd like me to do on this machine ? [13:40] ogasawara, yeah am somewhat concerned about it all but if you are doing a bunch of config you want people to have tested after it [13:40] jibel, well i found the issue was one in a few, so if you could do like 5 or so s/r's and just check [13:40] jibel, i did 10 and seemed ok for me [13:41] ack [13:41] jibel, other than that playing with it a little to see if its generally not pants [13:53] smb, cking, if you have spare machines getting some testing on the kernels in http://people.canonical.com/~apw/lp1027828-quantal/ which is basically what ogasawara would upload [13:54] apw, testing anything in particular? [13:55] apw: got any arm builds for ppisati? If not, mine should finish shortly. [13:55] apw, I can get it into the acer relatively quickly (though it would be quite the same as yours) [13:55] cking, I guess supend/resume [13:55] cking, just as wide a set of "touch tests" machines wide as we can [13:55] Not sure what is on the dell right now... lets see [13:55] cking, as this has our config review hackery on top of it [13:55] apw, ack [13:55] ogasawara, no not done arm builds [13:56] ogasawara: done this morning all arm builds [13:56] ogasawara: i'm testing omap4 and is ok [13:57] ogasawara: don't know about omap3 [13:57] ogasawara: asked ogra to give it a sping [13:57] sping [13:57] grr [13:57] sping [13:57] ARGH! [13:57] spin! [13:57] hehe [13:57] ppisati: thanks :) [13:57] * ogra_ spings [13:58] ogra_, maybe spring? :) [14:06] * cking thinks ppisati is suffering from jet lag [14:07] cking, its hard to imagine anyone not, other than ogasawara of course [14:07] though she will be kai-lagged [14:09] apw: heh indeed, I think I'll go refresh my cup of coffee [14:16] * apw will be offline for a couple of hours, watching the torch [14:23] apw, resume failed at 7th try, but differently. Screen is white instead of black and the machine is alive. Likely an issue with screenlock or compiz, it looks like a stacking issue. [14:45] apw, did 30 suspend/resumes OK on Lenovo x220i and a Ivybridge Intel SDP laptop, more results to come later [14:51] cking: on the new one? [14:51] cking: new sdp? :) [14:51] cking: if so, \o/ [14:52] ;) [15:06] * ogasawara back in 20 [15:47] ogasawara, apw - any ETA on when we'll get the suspend/resume kernel fix uploaded? Anything else on the horizon kernel wise for A3? [15:47] apw, any clue on this one? bug 1028004 [15:47] Launchpad bug 1028004 in linux "MMC Card Reader not working" [Undecided,New] https://launchpad.net/bugs/1028004 [15:47] skaet: just waiting on a powerpc test build and then I plan to upload [15:47] skaet: probably another 2-3hrs. === cmagina-lunch is now known as cmagina [15:52] apw, that kernel works on 30 s3 tests on a Dell 6400 and Atom based HP 210-1000 too [15:53] thanks ogasawara [15:54] skaet: just fyi, this upload will pull us up to v3.5 final as well [15:56] ogasawara, will we need a d-i update then as well? [16:03] skaet: yes, it is an ABI bump [16:03] skaet: I'm going to upload it to quantal-proposed, so you guys can ultimately make the call if you want to pull it in for A3 [16:15] ppisati: can you look at bug 1027524? [16:15] Launchpad bug 1027524 in linux-ti-omap4 "QRT failed on test_072_config_debug_rodata and test_072_strict_devmem" [Undecided,New] https://launchpad.net/bugs/1027524 [16:16] bjf: ack [16:29] * ppisati -> gym [16:32] apw: so it didn't work for /me. It fixed the odd time out pause at the boot screen but the machine never came back from suspend. I tested it twice but have to admit I only waited a few minutes [16:37] jjohansen, wait to see if it comes back after 300+ seconds (~5 + mins) [16:39] cking: I will give it another try in a minute, point being it didn't make the odd pause after resume go away for /me. Wanted to let apw know asap as they where considering it for and upload [16:39] ack [17:08] bjf: https://bugs.launchpad.net/ubuntu/+source/linux-ec2/+bug/1021084 has been stalled for a week. Is cert testing not something that actually happens for linux-ec2? [17:08] Ubuntu bug 1021084 in linux-ec2 "linux-ec2: 2.6.32-346.51 -proposed tracker" [Medium,In progress] [17:12] apw, 30 more S3 tests passed on an AMD based Dell laptop and a UEFI Intel SDK box [17:12] infinity: looking [17:13] infinity: i didn't think we did cert testing [17:13] infinity: of ec2 [17:13] infinity: marking it invalid [17:14] bjf: That would unstick it, yeah. Thanks. :) [17:15] * henrix wonders why i didn't realised the -ec2 was still stuck [17:16] cking, Hm, seems the aspire one stuck itself on some s3 cycle... Now that not necessarily means the kernel is bad... [17:16] henrix: i don't know if it is smart enought to detect that something is 'confirmed' for too long [17:16] smb, that just means fwts s3 is good [17:17] cking, And this netbook quite broken... :) [17:17] smb, I'm doing a 32 bit install on a HPMini210 to see how well 32 bit works [17:17] bjf: well, at least we could detect something failed the 3 weeks cycle and fire an alarm [17:18] henrix: agreed [17:19] henrix: Or, you could rely on third parties to tell you! ;) [17:19] infinity: heh, right :) [17:20] cking, Btw, I am sorry to report that fwts is not foolproof. It allowed the fool that is me to specify the --s3-multiple after the s3 argument without telling me that I am stupid... ;) [17:21] ah, yeah, that's a problem indeed [17:21] cking, apw: test kernel didn't come back from suspend even after 15min [17:21] cking, Oh well, one that sits in front of the screen. [17:22] apw: however the 3.5 vanilla that I tested earlier didn't either when I retested it [18:26] * henrix reboots [18:27] jjohansen, ok so i am going to call you an outlier, i think that is another issue [18:28] apw: yeah it seems so, I'll keep poking at it [18:33] apw, My Acer also seems to suffer of something else. It failed the fwts s3 tests after 7 and 12 repeats but with a black screen, the dell was ok [18:47] apw, my HPMini210 in amd64 and i386 can do S3 x 30 successfuly [18:58] apw: still want me to shove 1027828 in the changelog to get autoclosed? [19:57] cking: bug 1028111 [19:57] Launchpad bug 1028111 in linux "ecryptfs tests fail on Lucid" [Undecided,New] https://launchpad.net/bugs/1028111 [19:57] cking: bug 1028112 [19:57] Launchpad bug 1028112 in linux "kernel SRU: ecryptfs tests fail on Natty" [Undecided,New] https://launchpad.net/bugs/1028112 [19:58] bjf, ack, will look at that first thing tomorrow, probably a test failure rather than a kernel bug, but I will poke it tomorrow [19:58] cking: thanks [20:06] * smb -> eod [20:09] * cking -> eod too [20:43] ogasawara, i'd say yes. i say my problem is fixed [20:43] apw: cool, I'd had the same train of thought so I shoved it in and uploaded [20:44] ogasawara, excellent. clearly we have other issues, but those are bad === bjf is now known as bjf[afk]