[00:50] <kuyanatan> can someone help me? have a computer that freezes when waking from sleep, does not respond. only does this when i close laptop lid, not choose suspend from the menu.
[00:54] <kuyanatan> someone from ubuntu-beginners said i should come here. is this the wrong place for this problem?
[00:56] <kuyanatan> ...
[02:03] <paultag> cnd: poke :)
[02:06] <johanbr> kuyanatan, see https://wiki.ubuntu.com/DebuggingKernelSuspend for instructions on debugging suspend/resume bugs
[02:07] <kuyanatan> johanbr: thanks!
[02:07] <johanbr> you're welcome
[02:08] <johanbr> when you're done with those steps, you can either ask here or file a bug by doing "ubuntu-bug linux" (or both)
[02:09] <kuyanatan> ok
[02:09] <kuyanatan> thank you!
[02:11] <johanbr> no problem :)
[02:45] <cnd> paultag, hey, what's up?
[02:46] <paultag> cnd: mind if I throw a PM your way?
[02:48] <cnd> paultag, sure
[08:55] <lag> apw: http://kernel.ubuntu.com/git?p=lag/ubuntu-maverick.git;a=commitdiff;h=652d0096e4cc7361db47b6efbebac28f7663bfc0
[09:30] <kraut> moin
[09:31] <apw> moin
[09:33] <csurbhi> apw, morning!
[09:33] <apw> morning
[09:33] <cooloney> apw: csurbhi morning
[09:34] <cooloney> csurbhi: long time no see
[09:34] <csurbhi> hie cooloney :)
[09:34]  * apw waves manically
[09:34] <csurbhi> cooloney, how are you doing?
[09:35] <cooloney> csurbhi: good, we will meet in Prague, right?
[09:35] <csurbhi> cooloney, yes, we will
[09:36] <kermiac> I just noticed bug 606139 from a member of the VMware QA Team. I re-assigned to the "linux" package but thought I would mention it here too as it seemed important
[09:36] <ubot2> Launchpad bug 606139 in linux (Ubuntu) "Request to disable vmwgfx driver in default config (affects: 1) (heat: 8)" [Undecided,New] https://launchpad.net/bugs/606139
[09:45] <ademmer> kamal: greetings! I stumbled upon your patch, fixing the broken ACPI backlight control for i915
[09:46] <ademmer> kamal: do you know, when you could submit your patch to the upstream kernel?
[10:06] <apw> ademmer, kamal is normally awake much later in the day
[10:10] <ademmer> apw: which timezone is he in? thx for the info! :)
[10:13] <cooloney> ademmer: i think kamal is based in CA, US
[10:14] <ademmer> cooloney: thx!
[10:27] <Daviey> Hi.. Has the flurry of e1000e patches from upstream landed in maverick yet?
[10:51] <apw> Daviey, maverick is at v2.6.35-r5 if that helps
[10:51] <apw> rc
[10:51] <Daviey> ah, ha - perhaps! 
[10:59] <cooloney> apw: one quick question, when will our M kernel be freezed?
[11:00] <cooloney> we might got some big patches for ti-omap4 in Sep
[11:00] <apw> *might* ?
[11:00] <cooloney> yeah, their montly release
[11:01] <cooloney> apw: September 16th, right? for kernel freeze
[11:02] <apw> cooloney, yes 16th is the cut-off, though our freeze date will likely be 9th or 10th as we have to prepare them
[11:03] <cooloney> apw: thx, i got it. so if we got about 200 patches before Sep 9th and we prepared the new ti-omap4 branch
[11:03] <apw> upload them, wait for them to build, fix them, repeat
[11:03] <cooloney> it is ok for mergeing right?
[11:05] <apw> is what ok for merging where?
[11:06] <apw> cooloney, ^^ ?
[11:08] <cooloney> oh, merging into Maverick ti-omap4 tree. 
[11:09] <cooloney> i am afraid that they will get us a big volumn patches just at our kernel freeze time.
[11:09] <apw> as long as its tested before then i guess its ok, but its the mobile team who have to test them
[11:09] <cooloney> or close to
[11:09] <cooloney> yeah, thx. we will work on that. 
[11:10] <apw> it would be better to get stuff much earler as you are making all the testing done at A3 and Beta pointless
[11:10] <cooloney> apw: yeah, i am trying to push that. 
[11:11] <cooloney> but bascially, their relese at the first half part of every month
[11:11] <apw> so how many patches did we get this month
[11:12] <cooloney> i was told there will be 200 at least for our .34 kernel
[11:12] <apw> we need to get buy in from mobile that they are ok with it changing things that late i guess
[11:12] <cooloney> but just one month later, we will move to .35 ti-omap4 kernel
[11:13] <cooloney> so i don't wanna merge too many things,
[11:13] <apw> have we had the july patches yet?
[11:13] <cooloney> no
[11:13] <apw> so we're not likely to get them in time are we
[11:13] <cooloney> we got 200 more patches in July
[11:13] <apw> we 'have got' or 'will get'
[11:14] <cooloney> we are discussing these. 
[11:14] <cooloney> actually they have 900 patches in July relese
[11:14] <apw> but have they released the july release to us yet ?
[11:14] <cooloney> and sebjan is helping to pick up some for our Ubuntu usage
[11:15] <cooloney> apw: no, they released internally 
[11:15] <cooloney> but sebjan is helping to pick up some and release for us
[11:15] <apw> so the likelyhood is that the august from is not going to arrive in time then
[11:16] <apw> august patch drop
[11:16] <cooloney> i was told it will be 200
[11:16] <cooloney> next month, August they will release a new branch based on .35
[11:16] <cooloney> we have to redo lots of work 
[11:16] <apw> right ... and then the september drop is the one you care about
[11:16] <cooloney> and replace our current .34 branch
[11:17] <cooloney> yeah, 
[11:17] <cooloney> correct
[11:17] <apw> and that isn't likely to be done in time 
[11:17] <cooloney> because september drop is similar to this month
[11:17] <cooloney> i think so
[11:17] <apw> as they haven't got the july one out before the 16th
[11:17] <cooloney> right.
[11:17] <apw> if it doesn't make the 10th they'll have to wait till after release i suspect
[11:18] <cooloney> exactly,
[11:18] <apw> and you can fight the sru team to get it through :)
[11:18] <cooloney> lol,
[11:19] <cooloney> just wanna let them know the tight schedule
[11:19] <apw> yep tell them the 9th
[11:19] <cooloney> yeah, already told sebjan about that. 
[11:19] <apw> that gives us a week to integrate and build them before we can no longer upload
[11:19] <cooloney> but he is not sure about that
[11:20] <cooloney> yeah, that will be perfect.
[11:20] <apw> then they miss the release
[11:20] <apw> time waits for no man
[11:21] <cooloney> don't miss the perfect 10/10!!
[11:21] <cooloney> apw: are you all set for the trip?
[11:21] <apw> cooloney, 10/10>  yeah something like that
[11:22] <apw> trip> heh not really, i've got my computers mostly ready to go, but nothing to wear at the moment
[11:23] <apw> cooloney, how about you? 
[11:23] <cooloney> apw: just exchanged some euros today.
[11:23] <apw> cooloney, do they use euro in prahah ?
[11:24] <apw> i thought it was crowns
[11:24] <cking_> check crowns
[11:24] <apw> czech crowns
[11:24] <cking_> doh, yep
[11:24] <cooloney> apw: yeah, we cannot exchange for that CZ currency in China
[11:24] <cooloney> so euros is ok, 
[11:24] <apw> oh what a pain that is for you
[11:24] <cooloney> then we exchange euros to CZ there
[11:25] <apw> mad .. not going to cost you a fortune no way
[11:25] <cooloney> in their airport, maybe
[11:25] <cooloney> but i was told, they also accept euros
[11:25] <cooloney> as well as their own currency
[11:25] <cooloney> how long is your flight then?
[11:26] <apw> 1.5 hours or something
[11:26] <apw> yours?  20 ?
[11:27] <cooloney> 15 maybe, from shanghai to moscow
[11:27] <cooloney> then moscow to there
[11:27] <cooloney> but backwards it will be faster.
[11:28] <apw> moscow ... wow
[11:28] <cooloney> apw: hehe, why so exciting?
[11:29] <cooloney> we were comrades before
[11:29] <cooloney> RU and CN
[11:29] <apw> dunno, one of those dangerous and exciting sounding places, one that i've yet to go to
[11:30] <cooloney> yeah, transfer there is faster than transfer in westen europe hub
[11:31] <apw> speak any russian ?
[11:31] <cooloney> a little, my father and mother studied that when they are in high school.
[11:31] <apw> handy if you get lost in the airport
[11:32] <cooloney> Товарищ
[11:34] <cooloney> ok, apw and cking_ i gonna head out for dinner
[11:34] <apw> see ya
[11:34] <cooloney> see you this Sunday
[11:34] <apw> yarg
[11:58]  * apw lunches
[13:23]  * apw_ works on the agenda for next week ...
[13:24] <cking_> apw_, perhaps I should do a firmware test suite spot
[13:27] <apw_> Sure why not. I am working on the page offline, so will add it here
[13:46] <tseliot> mjg59: is it ok to set usbcore.autosuspend=1 when using recent kernels?
[13:53] <apw_> TSELIOT isn't that something powertop recommends?
[13:54] <tseliot> apw_: powertop says to enable autosuspend but it doesn't say how
[13:55] <apw_> TSELIOT doesn't it print the command if you wait..  thought it did
[13:56] <tseliot> apw_: it does that with other suggestions not with autospend though
[13:56] <tseliot> autosuspend
[14:01] <apw_> Hrmm ok... that's annoying
[14:06] <tseliot> indeed
[14:22] <cking1> hrm, laptop overheated :-(
[14:31] <penguin42> if Apparmor loads a profile in Complain mode (apparmor_parser -Cr) should it change the behaviour of the application at all?
[14:31]  * penguin42 has a chromium profile that breaks it even in complain
[14:38] <apw_> Jjohansen ^^
[14:39] <jdstrand> penguin42: it should not affect it, but the '-r' reloads it and that is not always what you want. I suggest doing 'apparmor_parser -R...' followed by 'apparmor_parser -Ca'
[14:40] <jdstrand> penguin42: that is a full remove followed by add. you will have to restart chromium though
[14:41] <penguin42> jdstrand: Hmm, closer but not quite - I don't get any fonts with it like that
[14:42] <penguin42> but they reappear with -R
[14:42] <jdstrand> that should not be happening
[14:42] <jdstrand> penguin42: what does aa-status show?
[14:44] <penguin42> jdstrand: Let me paste bin it
[14:45] <penguin42> jdstrand: http://paste.ubuntu.com/464540/
[14:46] <penguin42> jdstrand: I get the feeling chromium has an odd way of doing its sandboxes which is where the null-numbers come from
[14:51] <jdstrand> penguin42: the null profiles do result from the sandboxes, but they are in complain mode anyway, so it shouldn't matter
[14:52] <jdstrand> penguin42: does dmesg provide any output?
[14:52] <jdstrand> (on the denial)
[14:55] <penguin42> it gives a few moans; I'll pastebin them
[14:58] <penguin42> jdstrand: http://paste.ubuntu.com/464546/
[14:58] <penguin42> jdstrand: This is on 2.6.35-8, on Lucid I used to get a lot more moaning in complain mode, but it worked
[14:59] <penguin42> mind you, there were some moans that I never got to the bottom why they were there
[15:00] <penguin42> jdstrand: http://www.treblig.org/debug/usr.lib.chromium-browser.chromium-browser   is the profile
[15:02] <jdstrand> penguin42: well, profiling with complain mode is different than profiling in enforcing. eg, in enforcing an actual denial will cause a different code path than a complain which didn't deny
[15:02] <jdstrand> penguin42: anyhoo, I think we need jj to take a look. I don't see anything that should make chromium not work in complain mode
[15:03] <penguin42> jdstrand: OK, thanks
[15:58] <apw> bdmurray,you about ?
[16:00] <komputes> Can someone please have a look at the following bug and suggest the next step to take. https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/605465
[16:00] <ubot2> komputes: Error: Bug #605465 is private.
[16:01] <komputes> ^ that is incorrect
[16:02] <smb> Maybe just bug 605465
[16:02] <ubot2> Launchpad bug 605465 in linux (Ubuntu) "Dell XPS M1330 CPU scales down to 800 MHz (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/605465
[16:02] <komputes> that works
[16:03] <apw> thats a common machine to be having issues ...
[16:03] <smb> Generally the answer to force a certain frequency limit is no. Not automatically
[16:04] <smb> Second it would be interesting to check what the current freq scaling parameters are when this happens
[16:05] <smb> grep . /sys/devices/system/cpu/cpu?/cpufreq/*
[16:06] <smb> Actually the above command done with sudo
[16:08] <smb> Oh, I see this is in mycpuinfo
[16:10] <smb> komputes, but from that file I cannot see the described problem.
[16:17] <smb> komputes, We need some real indication on that problem. If you ask the reporter to run and collect the output of "sudo powertop -d -t30" while doing a tight loop like "while true; do false; done" in another terminal when he thinks he has the problem?
[16:22] <komputes> smb: I will suggest this, thank you
[17:08] <apw> cking1, about ?
[17:09] <cking1> yep
[17:15] <hyperair> what rc is 2.6.35-7 based off?
[17:16] <apw> hyperair, thts a faq question :)
[17:17] <hyperair> apw: hmm? and where's this faq?
[17:17] <apw> https://wiki.ubuntu.com/Kernel/FAQ
[17:17] <hyperair> ah cool thanks
[17:17] <apw> http://kernel.ubuntu.com/~kernel-ppa/info/kernel-version-map.html
[17:17] <apw> leads you to that link
[17:19] <apw> hyperair, you can also tell from /proc/version_signature if it is booted
[17:20] <hyperair> apw: yeah i just saw on the faq. thanks.
[17:20] <apw> hyperair, heh the faq has been developed a lot recently to actually have some of the frequently asked questions in it :)
[17:20] <apw> !faq
[17:20] <ubot2> A list of common questions and answers about Ubuntu: http://help.ubuntu.com/community/CommonQuestions - Official documentation: http://help.ubuntu.com
[17:21] <apw> hrm
[17:21] <apw> !help
[17:21] <ubot2> Please don't ask to ask a question, simply ask the question (all on ONE line and in the channel, so that others can read and follow it easily). If anyone knows the answer they will most likely reply. :-)
[17:21] <hyperair> lol
[17:21] <hyperair> i think it's !faq is blah blah
[17:21] <hyperair> but i'm not sure if it will change faq on other channels as well.
[17:21] <apw> !kernel-faq is Common Kernel questions can be found here: https://wiki.ubuntu.com/Kernel/FAQ
[17:22] <apw> it reported in on me to #ubuntu-irc for trying to talk to it ... sigh
[17:23] <apw> !kernel-faq is Common Kernel questions can be found here: https://wiki.ubuntu.com/Kernel/FAQ
[17:32] <komputes> smb: are you sure the command is powertop?
[17:32] <smb> komputes, yes, why
[17:33] <komputes> smb: I am unable to find that executable
[17:33] <smb> komputes, Maybe install it?
[17:33] <komputes> smb: package name?
[17:33] <smb> powertop
[17:33] <komputes> done, thx, wonder why it didn't propose it ;)
[17:34] <apw> cause you used sudo ?
[17:37] <komputes> apw: that would be it
[17:51] <komputes> apw: smb: Could you guys suggest a kernel option to increase the delay Ubuntu waits to see the drives? 
[17:51] <bryce2> jfo, bjf: if lp #567007 sounds like a useful launchpad feature, mind clicking 'Affects me too'?  The more people marked as it affects them, the more likely it'll be to get on the Launchpad team's planning list when work starts on search improvements
[17:51] <ubot2> Launchpad bug 567007 in malone "User-specific default tag search parameters (affects: 1) (heat: 3)" [Low,Triaged] https://launchpad.net/bugs/567007
[17:52] <smb> Hm, wasn't that root_delay= ? All other mount are being waited infinitely by mountall
[18:02] <kees> komputes: kernel command-line for that (it's the initramfs scripts that parse it) is "rootdelay".  i.e. rootdelay=30 will wait 30 seconds for the root filesystem to become available.
[18:06]  * ogasawara bails, back in a few hrs
[18:23] <dupondje> [   34.007768] BUG: unable to handle kernel NULL pointer dereference at 00000000000003c0 => already reported ?
[18:24] <jjohansen> dupondje: maybe, but that isn't enough information to know
[18:25] <manjo> dupondje, could you paste bin dmesg ?
[18:25] <akgraner> apw, ping
[18:26] <dupondje> http://paste.ubuntu.com/464629/
[18:27] <manjo> dupondje, is that a maverick kernel ? 
[18:27] <dupondje> yea
[18:27] <sconklin> ls
[18:28] <sconklin> doh
[18:28] <manjo> dupondje, might be a good idea to open a bug on that one 
[18:28] <apw> akgraner, pong
[18:28] <manjo> dupondje, ubuntu-bug -p linux 
[18:29] <dupondje> https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/606244 => this seem to be related. As whith the kernel error, I get that issue also
[18:29] <ubot2> Launchpad bug 606244 in libdrm (Ubuntu) "X doesn't find a screen and is not starting due a race condition (affects: 2) (heat: 12)" [Undecided,New]
[18:29] <dupondje> without, everything works great
[18:30] <akgraner> apw - remember when you said - "Don't worry if you don't write code - if you see the instructions are wrong - don't be afraid to fix it!"  - I wanted to say thank you for your encouragement!   - check out http://www.amazon.com/Official-Ubuntu-Book-Benjamin-Mako/dp/0137081308 (the acknowledgements page :D)
[18:31] <akgraner> you all are the coolest kernel team ever  - well minus pgraner that is :-P
[18:31] <apw> akgraner, see was i wrong ?
[18:32] <akgraner> no you weren't - if you hadn't said just keep writing about stuff - I don't think I would have been asked to be a technical editor on this edition - so Thanks ya'll :-)
[18:33] <penguin42> dupondje: Do you have a backtrace below it?
[18:33] <dupondje> penguin42: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/606393
[18:33] <ubot2> Launchpad bug 606393 in linux (Ubuntu) "BUG: unable to handle kernel NULL pointer dereference at 00000000000003c0 (affects: 1) (heat: 6)" [Undecided,New]
[18:34]  * akgraner leaves on that note  - thanks again!
[21:08] <virtuald> Aha
[21:09] <virtuald> wrong channel
[21:37]  * manjo signing out early... 
[22:19] <chazn85> hey all, could someone enlighten me to the kj-triage tag?
[22:21] <bjf[afk]> chazn85, it's used by the kernel team, just ignore it
[22:25] <chazn85> ok will do, as an aspiring member currently being tutored by JFo was just curious to what it was
[22:25] <jjohansen> chazn85: kj is kernel janitor
[22:26] <jjohansen> basically its a tag used by the arsenal kernel janitor scripts
[22:26] <jjohansen> its not even documented in the tags for people to add
[22:27] <jjohansen> https://wiki.ubuntu.com/Kernel/Tagging
[22:27] <jjohansen> you can find it mentioned in here
[22:27] <jjohansen> https://wiki.ubuntu.com/specs/KernelKarmicBugHandling
[22:28] <chazn85> i thought it was automated as i hadnt seen that one as yet 
[22:28] <jjohansen> yep, to really know what it does you need to look in the arsenal scripts
[22:29] <bjf[afk]> chazn85, the scripts add it and then check for it so the same bug isn't processed multiple times for the same reasons
[22:33] <chazn85> thanks guys, all part of the learning curve, ill ignore them for the time being 
[22:34] <bjf[afk]> chazn85, it's not a bad idea to take a look at the scripts, there's a lot going on in them
[22:39] <chazn85> bjf[afk, i might just do that
[22:40] <bjf> chazn85, if you have questions, feel free to ask, i've been through most of them quite a bit
[22:41] <bjf> chazn85, i recommend you *don't* try to run them without talking to jfo first though
[22:43] <chazn85> im cautious at the moment, so no chance of that!