[02:35] <tammy1230> ethanchang, do you see abnormal situation on Asahi while pressing F4?
[10:20] <brendand> is there a way to check if a system has been suspended?
[10:20] <apw> brendand, since boot ?
[10:21] <brendand> apw, yeah
[10:21] <brendand> apw, does dmesg just cover one boot? i could look in there
[10:21] <apw> brendand, yeah its just one boot in dmesg
[10:22] <apw> there are also logs in /var/log/pm-suspend
[10:22] <apw> [393718.228670] ACPI: Low-level resume complete
[10:22] <apw> that line is probabally pretty indicative
[10:23] <apw> brendand, though if i am honest for a proper check i would look at how suspend_test from firmware test suite does it
[10:25] <brendand> apw, it doesn't need to be too thorough, just a cursory check so i can validate that X event happened after suspend
[11:06]  * ppisati goes hunting for food..
[11:08]  * henrix follows ppisati
[11:09] <ogra_> henrix, dont eat ppisati !
[11:10] <henrix> ogra_: nah, not in the mood for italian food
[11:10] <ogra_> lol
[11:18]  * apw goes splash about
[12:11] <apw> wet
[12:11] <rtg> apw, one of you less secure passwords ?
[12:11] <apw> rtg, heh no a state of being right now :)
[12:12] <apw> rtg, and arn't you away today ?
[12:12] <rtg> apw, not until 11:30
[12:12] <FreddrH> Hi! I've just seen the latest kernel team meeting minutes, it has a note about testing kernel 3.5 in precise. Where are problems supposed to be reported? looked around on launchpad but couldnt find the right spot.
[12:12] <apw> FreddrH, file a bug against linux i'd say, the version number should clue is in
[12:14] <rtg> FreddrH, file it against linux-lts-quantal
[12:15] <FreddrH> ok thx!
[12:32] <tjaalton> apw: whee, the overlayfs patch looks good.. building mesa right now :)
[12:34] <tjaalton> but I'm not sure how long it took to fail, so let's see..
[12:40] <tjaalton> apw: yeah, it would fail right in the beginning, so.. success with the patch
[12:41] <apw> tjaalton, thanks, will clean it up for submission
[12:46] <tjaalton> apw: would it be ok for precise as well?
[13:10] <apw> tjaalton, dunno will see
[14:55]  * ogasawara back in 20
[15:07] <rtg> ogasawara, between calxeda and ecryptfs I think there are enough major function patches in the hopper that we should upload again.
[15:08] <ogasawara> rtg: ack, was thinking the same
[15:08] <apw> ogasawara, and that revert for aufs
[15:08] <ogasawara> apw: yep, I think I pushed that revert already
[15:08] <apw> ogasawara, cool
[15:38] <rtg_> ogasawara, smoke testing the ecryptfs patches on -9 seem to work OK
[15:39] <ogasawara> rtg: thanks, good to know
[15:39] <rtg_> though I haven't tested the boundary conditions. cking has some tests for that. he'll be busy when he returns.
[15:48] <apw> smb, hey, where is your .33 tree
[15:48] <smb> apw, where it has been before...
[15:49] <smb> http://git.kernel.org/?p=linux/kernel/git/smb/linux-2.6.32.y-drm33.z.git;a=shortlog;h=refs/heads/drm-next
[15:49] <smb> or
[15:49] <smb> http://kernel.ubuntu.com/git?p=smb/linux-2.6.32.y-drm33.z.git;a=shortlog;h=refs/heads/drm-next
[15:49] <smb> without drm-next 
[15:49] <smb> (was the first place I found for pasting)
[15:56]  * dileks thought drm-next was a backport GIT branch from airlieds development tree
[15:56] <rtg> bjf, that 17" Dell you were admiring in PDX is beginning to die. Major nVidia display corruption.
[15:57] <bjf> huh
[15:57] <dileks> smb: what about compat-drm? an option? tested?
[15:57] <bjf> that sucks
[15:57] <rtg> 4+ years of hard use though
[15:57] <rtg> bjf, yeah, I'm bummed. I may actually have to buy a laptop this time :)
[15:58] <bjf> rtg, of find one to "enable"
[15:58] <bjf> s/of/or/
[15:58] <rtg> bjf, I'll send it to sforshee first :)
[16:03] <smb> dileks, No option I would say. It just is the way the 2.6.32 relase was done (Ubuntu and Debian) as nobody liked the drm in 32
[16:03] <dileks> IIRC the same with drm in 3.2.y 
[16:03] <G__81> "Failed to create pty - disabling logging for job
[16:04] <G__81> can someone help me out ?
[16:04] <G__81> i am trying to boot an Ubuntu FS Image in qemu with just the kernel. Its a 64 bit Ubuntu image though it boots up i dont see the console and it does not get me to the prompt. Its a 12.04 FS image and the kernel is 3.4.7. I am  using an  Ubuntu kernel config 
[16:04] <G__81> the error that i get is Failed to create pty - disabling logging for job
[16:07] <apw> G__81, that error just tells you one of your upstart jobs failed to open a logging channel
[16:08] <apw> G__81, it should not prevent anything working thoough
[16:08] <G__81> i have the tty drivers stuff enabled too 
[16:08] <G__81> the devpts98 stuff is enabled along with the kernel 
[16:08] <apw> yep that error normally means there is a race being tickled, it still does not affect functionality
[16:08] <apw> if your functionality missing, its not likely to be related to that error
[16:09] <apw> what kernel command line are you supplying
[16:09] <G__81> it boots but i get the error and it stops and then it does not proceed 
[16:10] <apw> that error only means some logging is being dropped on the floor from upstart
[16:10] <apw> the jobs continued as normal, so if they were working they'd work with that error there
[16:10] <G__81> this is the command http://pastebin.com/qurG1uEd
[16:10] <apw> i would add --verbose to the end of the kernel command line and see what that says
[16:14] <dileks> hmm, xserver with releasename
[16:15] <apw> dileks, ?
[16:15] <dileks> http://cgit.freedesktop.org/xorg/xserver/commit/?id=c22c936b35cee60609041ccb7ee52c00b0634d7b
[16:16] <apw> heh must have got bored of being the only ones without a silly name for every release
[16:20] <apw> G__81, what did that sayb
[16:21] <apw> ogasawara, sforshee, go back to bed both ... i was using that machine :)
[16:21] <ogasawara> apw: :)
[16:21] <apw> ogasawara, you do kill her in the face
[16:24] <hallyn> hi - https://lkml.org/lkml/2012/8/7/442 seems noteworthy.  bug in the apparmor+selinux cooperation with netfilter
[16:24] <apw> jjohansen, ^^
[16:25] <G__81> apw, looks like its got to do with the lib/modules . That verbose option really helped :) Thanks a ton 
[16:25] <apw> np
[16:25] <jjohansen> apw: thanks, looking at it
[16:26] <apw> hallyn, how do we know its AA related ?
[16:27] <hallyn> apw: it's not strictly AA related, but AA is running (default precise systems) and selinux nf hooks are running
[16:28] <hallyn> so i think it's a bug in the initcalls stuff causing selinux's netfilter hook init to happen before selinux_disable() gets called
[16:28] <apw> perhaps just an ordering issue, don't some of them flop into the same buckets
[16:28] <hallyn> (i could dive deeper but thought i should mention it here first)
[16:29] <apw> as in there are more levels exposed than exist in initcalls
[16:29] <hallyn> right, it's possible that it working so far relied on luck in the ordering of the initcall() entries.  
[16:30] <hallyn> so to answer again, it don't think it's AA related, i think it's a bug in selinux, but not one selinux users will care about :)
[16:30] <apw> indeed
[16:30] <apw> and likely jjohansen will grok the interaction better than us
[16:30] <hallyn> yup.  thanks.
[16:35] <apw> jj
[16:35] <apw> bah
[16:36]  * smb -> gone
[16:46] <G__81> apw, ping
[16:46] <apw> pong
[16:47] <G__81> i corrected the modules problem in the FS but now again the same problem. it stops with the error which i pasted earlier , logging disabled
[16:47] <G__81> as you said i have the verbose option enabled 
[16:47] <apw> and what else does it say, the error is only a warning
[16:48] <G__81> it does not say anything it just stops :( i can probably upload the screenshot too if you want to look @ it
[16:48] <apw> --verbose will vomit all over the place so it must have said something
[16:50] <G__81> apw, i just created ./lib/modules/3.4.7 in my FS it does not have the drivers as such, thats ok right ?
[16:50] <jjohansen> hallyn, apw: the config in that bug report hash selinux as the only security module and enabled by default
[16:50] <apw> G__81, if you have no modules you have only half of your kernel installed
[16:50] <apw> jjohansen, oh, so its not an ubuntu config then
[16:51] <hallyn> jjohansen: eh what?  i thought he said he was running the ubuntu kernel!
[16:51] <jjohansen> hallyn: well he said running ubuntu, I double checked
[16:51] <G__81> apw, ok then i ll do the install_mod_path 
[16:51] <jjohansen> I think we assumed an ubuntu kernel
[16:52] <apw> yeah that looks to be a straight selinux issue, its enabled, its the only one, its on by default, and it explodes
[16:55] <hallyn> jjohansen: thanks, and sorry.  do you care to reply to the thread?
[16:55] <jjohansen> hallyn: sure
[16:56] <hallyn> jjohansen: great, thanks 
[17:15]  * rtg is officially on vacation 
[17:17] <apw> sconklin, ok sorted out that 0044 it is now back to needed like it should be (for lucid)
[17:18] <sconklin> apw: not following you
[17:18] <apw> sconklin, CVE-2012-0033
[17:18] <ubot2> apw: ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem.  When the candidate has been publicized, the details for this candidate will be provided. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-0033)
[17:19] <apw> sconklin, CVE-2012-0044
[17:19] <ubot2> apw: Integer overflow in the drm_mode_dirtyfb_ioctl function in drivers/gpu/drm/drm_crtc.c in the Direct Rendering Manager (DRM) subsystem in the Linux kernel before 3.1.5 allows local users to gain privileges or cause a denial of service (memory corruption) via a crafted ioctl call. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-0044)
[17:19] <sconklin> apw: ack
[17:19] <apw> sconklin, we should likely prioritise getting that fixed as it has been announced as not broken for lucid
[17:20] <sconklin> ok, I'll have at it
[17:23] <bjf> http://www.phoronix.com/scan.php?page=news_item&px=MTE1NTk
[17:24] <sconklin> what is the sound of one hand whacking?
[17:24] <sconklin> that will sort itself out
[17:27] <G__81> what should be the arch option in deboostrap that i should give if the system is 64 bit
[17:42]  * henrix -> EOD