[00:38] <johanbr> hi... on the first suspend after a cold boot, my laptop suspends immediately after the hard drive is parked
[00:39] <johanbr> but on subsequent suspends, there's about a five-second delay after the hard drive is parked... does anyone know why this might happen?
[00:43]  * manjo out 
[07:48] <amitk> morning
[07:48] <smb> morning
[07:49] <amitk> hey smb 
[07:56] <ikepanhc> good morning .eu :)
[07:56] <cooloney> morning guys
[07:57] <cooloney> amitk: one short question for you, need i use external powered usb hub for beagleboard, right?
[07:57] <amitk> cooloney: yes
[07:57] <amitk> hi ikepanhc 
[07:58] <cooloney> i got an external powered usb hub to my BB's usb host port.
[07:58] <cooloney> amitk: but doesn't work. so weird.
[08:00] <amitk> cooloney: which port did you connect it to? the ehci (standard) port or the OTG port?
[08:01] <cooloney> amitk: the standard EHCI port
[08:01] <amitk> cooloney: nothing is detected?
[08:02] <cooloney> amitk: i am trying to install the system from SD card, so no chance to get the dmesg
[08:02] <cooloney> amitk: but i can change the bootargs to see from serial maybe
[08:03] <amitk> cooloney: ohh, you have C3 right?
[08:03]  * ikepanhc updating maverick and praying
[08:03] <cooloney> amitk: yeah C3
[08:04] <amitk> cooloney: Hardware issue on rev C3 - the EHCI port on some rev C3 boards is unstable and will disconnect hubs/devices. Symptoms are: devices are disconnected from the port and cannot be reconnected without a reboot. It appears the shared 1.8V rail between the OMAP3530 and the power chip was getting noisy. Suggested solution (works on many boards) is adding a 22 uF 0805 package SMT capacitor atop the existing cap on C97. If SMT parts 
[08:05] <amitk> cooloney: http://elinux.org/BeagleBoard#EHCI
[08:05] <amitk> cooloney: time to get out the soldering iron ;)
[08:05] <jk-> heh
[08:08] <cooloney> amitk: oh yeah. i need 22uF 0805
[08:14]  * ikepanhc updated, looks great :)
[08:15] <amitk> ikepanhc: you updated yourself?
[08:16] <ikepanhc> amitk: ahah, update my machine, not my brain :)
[13:00]  * apw has to shift locations
[14:08] <tgardner> apw, have you run into 'Cannot make directory '/var/run/screen': Permission denied' ? Seems that the /var/run/screen directory isn't correctly created at boot time.
[14:09] <apw> tgardner, no ... is that something to do with you using screen as your default on login ?
[14:09] <tgardner> apw, nope, just running jobs on remote servers. I rebooted tangerine this AM and found screen no longer worked.
[14:10] <tgardner> there must be a service startup rule somewhere.
[14:10] <apw> ahh ... not a bit screen user so i'd probabally not hit it
[14:10] <tgardner> apw, really? I thought everyone was seduced by the wonders of screen
[14:10] <apw> tgardner, i am a little supprised it uses /var/run/ ...
[14:11] <apw> tgardner, i use it on zinc, thats about it
[14:11] <apw> /etc/init/screen-cleanup.conf <-- tgardner 
[14:12] <JFo> I <3 screen
[14:12] <apw> JFo, yeah its great other than not being able to access scrollback, so i use it for things where i have to, otherwise i tend to run and log locally to a file and tail the file remotely style
[14:13] <JFo> same here
[14:13] <JFo> I tail from a non-screened term
[14:13] <apw> don't get me wrong it rocks for those where you need it
[14:13] <JFo> oh yes
[14:13] <apw> tgardner, so thats an upstart job ... so ask upstart if its started
[14:13] <tgardner> All of my build scripts log locally so I don't have to deal with the lack of scroll back
[14:13] <JFo> especially for things that run forever and would suffer from unexpected failure
[14:14] <tgardner> apw, I just ran it by hand. I'd actually already tries it with 'restart', but its not well coded and did nothing
[14:14] <apw> tgardner, hrm ... sounds like a bug ... cirtianlyu it exists on my maverick boxes ok
[14:14] <tgardner> now I can't remember what the hell I started out to do
[14:15] <apw> tgardner, now that i can relate to
[14:15] <tgardner> oh, updating maverick schroots
[14:19] <tgardner> apw, ok grubmaster, tell me why emerald boots 2.6.32-21.32-server ? /boot/grub/grub.cfg looks right. nothing in /etc/default/grub, etc
[14:20] <apw> tgardner, looking#
[14:21] <smb> saved_entry?
[14:21] <tgardner> apw, I think it should be booting linux-image-2.6.35-14-server
[14:21] <apw> tgardner, the config does say 'default = 10' and if i count from 0 that is the 32-21 kernel
[14:22] <apw> so i think its doing what the config says ... now why thats not default=0 i am not sure
[14:22] <tgardner> huh
[14:22] <apw> on my other machines the default = 0
[14:22] <tgardner> apw, well then, I shall set the default to 0
[14:23] <apw> tgardner, it seems that the default is set in /etc/default/grub and to 10
[14:23] <apw> which to my mind is oddness indeed
[14:24] <smb> apw, Maybe someone tried to set a timeout and hit the wrong line...
[14:26] <apw> smb, or maybe they wanted to move to an older one, and it tracks it somehow
[14:26] <tgardner> apw, I'm betting smb is right, someone (perhaps pgraner) wanted a grub menu timeout
[14:26] <smb> Could be, too. I am also not sure how the save default feature would work
[14:28] <apw> yeah something mad
[14:28] <pgraner> tgardner, yea that way me, when emerald was wedged I wanted to throw up grub for 10 sec
[14:28] <pgraner> tgardner, looks like I got the wrong entry
[14:28] <pgraner> tgardner, just flip it back
[14:28] <tgardner> pgraner, you used the wrong option
[14:29] <apw> and until you get to 10 in the menu it suddenly means something
[14:29] <pgraner> tgardner, no duh
[14:29] <tgardner> pgraner, well, she's bouncing.
[14:29] <pgraner> tgardner, thanks
[14:31] <tgardner> pgraner, ah, much better
[14:33] <apw> lag its as likely my end
[14:33] <tgardner> apw, you're_rally_ quiet
[14:33] <tgardner> really*
[14:34] <apw> tgardner, thanks
[14:52] <lag> apw: Connection failed. Error: (336151568) error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure
[14:53] <apw> lag, lovely helpful error message
[14:53] <lag> Quite
[14:54] <lag> apw: If I disable SSL I get "Connected. Now logging in..." then nothing
[14:54] <lag> How does bip know which channels to save logs for?
[14:54] <apw> heh proper handy
[14:54] <apw> lag, all open ones i think
[14:55] <apw> it tracks where you open in your client
[14:55] <lag> Arh okay
[14:55] <lag> So you don't need to tell it
[14:55] <lag> That's good at least
[14:56] <apw> lag, i think you can give it a list to open by default when it reconnects, otherwise it tracks (or in addition) it tracks places your clients ask for
[14:56] <apw> note that more than one client can be connected
[14:57] <lag> apw: I can't even get one to connect :(
[15:03] <apw> lag, there must be a simpletons quide out there somwhere
[15:04] <lag> Seemingly not
[15:05] <lag> apw: http://www.mindforge.org/index.php?option=com_content&task=view&id=70&Itemid=45
[15:05] <lag> I've done all this
[15:13] <lag> apw: Sorted!
[15:26] <ikepanhc> JFo: I am interested in bug 612454, shall I change the status myself or you perfer you triage first?
[15:26] <ubot2> Launchpad bug 612454 in linux (Ubuntu) "[Packard-Bell EasyNote] asus_laptop problem: wifi (affects: 1) (heat: 3411)" [Undecided,New] https://launchpad.net/bugs/612454
[15:27] <JFo> ikepanhc, I am fine with you changing it as you see fit
[15:27] <JFo> :)
[15:27] <ikepanhc> JFo: thanks :)
[15:27] <JFo> no problem. you guys are the only ones I don't second guess if I can help it :)
[15:32] <ikepanhc> JFo: change done, just want to make sure I wont let you hard to track those bugs
[15:32] <JFo> no, it isn't a problem
[15:32] <ikepanhc> :)
[16:20] <manjo> drm-intel-next kernels (2.6.35-997 and 999) also give me a blank screen on boot under lucid,
[16:21] <manjo> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/561802
[16:21] <ubot2> Ubuntu bug 561802 in linux (Ubuntu Lucid) (and 1 other project) "[lucid] [i915] blank screen on Latitude E6410 (affects: 27) (heat: 166)" [Medium,In progress]
[16:32] <smb> bjf, git://git.kernel.org/pub/scm/linux/kernel/git/smb/linux-2.6.32.y-drm33.z.git
[16:32] <bjf> smb ack
[16:33] <ogasawara> apw: bug 589439 is linked to our config blueprint and I've reviewed it and commented on the config options we have changed as requested.  There is no way I'm going to change the whole lot of them without proper justification.
[16:33] <ubot2> Launchpad bug 589439 in linux (Ubuntu) "configuration gotchas with Maverick 2.6.35 kernel... (affects: 1) (heat: 63)" [Medium,Triaged] https://launchpad.net/bugs/589439
[16:33] <ogasawara> apw: is there a way for the bug to remain open and linked to the blueprint but not show up as an open action item on our release page?
[16:34] <ogasawara> apw: maybe if I set the milestone to ubuntu-later?
[16:37] <apw> ogasawara, i don't think there is right now, if you put it ubuntu-later i think it'll just show up
[16:37] <ogasawara> apw: maybe I'll unlink it from the blueprint and then write it down as an actual work item that I can mark DONE
[16:38] <apw> ogasawara, yeah i've been known to do that too ... its not ideal
[16:38]  * apw waves to balbir 
[16:40] <apw> ogasawara, essentially you are saying that the work item is smaller than the bug open life, so actually a manual work item is appropriate in that context
[16:40]  * balbir waves back
[16:40] <manjo> apw, is this correct ? git checkout lucid debian 
[16:41] <manjo> apw, is this correct ? git checkout lucid debian.master 
[16:41] <apw> ogasawara, and on the original point ... you are sane to not change the ones which you don't need
[16:41] <apw> manjo, if lucid is your remote then likely its
[16:41] <manjo> apw, yes.. thanks
[16:41] <apw> git checkout lucid/master debian debian.master
[16:43] <bjf> smn, when reviewing your new combined tree we are reviewing everything after 2.6.32.16.6, correct?
[16:43] <manjo> git remote add lucid1 git://kernel.ubuntu.com/ubuntu/ubuntu-lucid.git
[16:43] <manjo> manjo@tangerine:~/linux-2.6.34.y.561802$ git checkout lucid1/master debian debian.master
[16:43] <manjo> error: pathspec 'lucid1/master' did not match any file(s) known to git.
[16:43] <manjo> error: pathspec 'debian' did not match any file(s) known to git.
[16:43] <manjo> error: pathspec 'debian.master' did not match any file(s) known to git.
[16:43] <manjo> manjo@tangerine:~/linux-2.6.34.y.561802$ 
[16:44] <manjo> apw, ^^
[16:44] <bjf> smb, when reviewing your new combined tree we are reviewing everything after 2.6.32.16.6, correct?
[16:44] <apw> manjo, did you fetch your remote ?
[16:44] <smb> bjf, yes correct
[16:45] <manjo> no :)
[16:45] <apw> spanner
[16:48]  * manjo is wondering if stefan is building on tangerine :) 
[16:50] <apw> manjo, he has a tendancy to make the load hit about 90 ... most annoying
[16:51] <manjo> apw, absolutely!
[16:51] <tgardner> manjo,  16:51:39 up  3:01,  6 users,  load average: 0.58, 0.58, 1.51
[16:52] <manjo> tgardner, hmm... so my connection has a lag possibly ... should have done top before blaming smb :)
[16:53] <smb> I am innocent this time
[17:03] <manjo> apw, do I have to do something special for FAIL: value CONFIG_DEFAULT_SECURITY_APPARMOR Y ?? 
[17:03] <apw> manjo, zap the enforce configuration
[17:15] <JFo> I really wish chromium would quit crapping its pants
[17:15] <vanhoof> JFo: seems to be worse lately
[17:15] <JFo> it does indeed
[17:15] <JFo> nigh unusable on my netbook
[17:15] <JFo> I just opened it and it was up all of 10 seconds
[17:16] <JFo> segfaulting it seems
[17:16] <JFo> chromium-browse[29554]: segfault at 0 ip 08619d0f sp bfde07a0 error 4 in chromium-browser[8048000+2214000]
[17:16] <JFo> looks like it has been reported to google though
[17:17] <JFo> did you and I ever come to some satisfactory decision on the QA bugs vanhoof?
[17:17] <JFo> my brain is still fuzzy from sickness
[17:17] <pgraner> JFo: is that what they are calling hangovers these days?
[17:17] <JFo> heh
[17:17] <JFo> nope, but I wonder if that would help at all
[17:18] <JFo> not the hangover, more the drinking
[17:18] <JFo> :-)
[17:18] <JFo> pgraner, someone has requested we re-enact the dogs playing poker next time we do photos
[17:18] <JFo> I'm up for it
[17:18] <lag_> Any ideas: http://paste.ubuntu.com/473148/
[17:19] <lag_> apw: --^
[17:19] <apw> lag_, nope
[17:19] <lag_> apw: :(
[17:20] <vanhoof> JFo: we did, do you have some?
[17:20] <vanhoof> JFo: from you -> project
[17:20] <lag_> apw: It's weird how the complicated one works and the "just works", "open" one doesn't!
[17:20] <JFo> no, just trying to follow up on our chat and my notes
[17:20] <JFo> ah yes, I remember that now
[17:20] <vanhoof> ultimately, if QA can make that call, then from QA -> project
[17:20] <apw> lag_, perhaps some config options are leaking over
[17:20] <JFo> sweet
[17:20] <vanhoof> JFo: getting my bits in place, should have it setup soon
[17:20] <JFo> just wanted to make sure my notes were complete
[17:20] <JFo> ok cool
[17:21] <JFo> I'll do some quick and dirty write up for my notes then
[17:21] <JFo> since I remember now
[17:21] <JFo> thanks for the reminder vanhoof :)
[17:21] <lag_> apw: What's to leak?
[17:21] <lag_> network {
[17:21] <lag_>         name = "freenode";
[17:21] <lag_>         server { host = "irc.freenode.net"; port = 8001; };
[17:21] <lag_> };
[17:22] <vanhoof> JFo: cool
[17:24] <apw> 8001 ?
[17:25] <apw> lag_, ^^
[17:25] <manjo> lag_, server { host = "irc.freenode.net"; port = 8001; };
[17:25] <lag_> yep
[17:25] <manjo> that is what I have too
[17:25] <lag_> It' what I've always used
[17:25] <lag_> So shouldn't be an issue
[17:25] <lag_> It's so annoying!
[17:25] <manjo> lag_, you are setting up bip ?
[17:26] <lag_> I've been through the conf 100 times
[17:26] <lag_> manjo: Yes
[17:26] <apw> lag_, so i have 6667 in mine
[17:26] <lag_> I've tried that too
[17:27] <manjo> lag_, I can send you mine try to compate ? 
[17:27] <lag_> pgraner is email me his
[17:27] <JFo> sconklin, I just blew soda all over my laptop
[17:27] <JFo> thx
[17:27] <JFo> :)
[17:28] <vanhoof> lag_: try irc.us.freenode.net
[17:28] <apw> lag_, perhaps you could put your config as is somewhere
[17:29] <vanhoof> lag_: see if its a problem where you're being sent to
[17:29] <lag_> vanhoof: Sure - 1 mo
[17:30] <manjo> apw, zapping enfore causes other errors ... 
[17:31] <manjo> apw check-config: /home/manjo/linux-2.6.34.y.561802/debian.master/config/enforce: open failed -- No such file or directory -- aborting
[17:31] <apw> zap the contents not the file
[17:31] <manjo> fuck!
[17:31] <apw> ie make the file empty
[17:31] <manjo> :)
[17:32] <JFo> heh
[17:43] <manjo> apw, finally getting it to build 
[17:43] <manjo> apw, thanks beer++
[17:43] <smb> error overflow
[17:51] <apw> smb, no asuch thing, its a 256 bit integer
[17:53] <smb> apw, That is, if he gives you enough beer tokens you end up to give him beers
[17:53] <smb> Thats bad
[17:55] <JFo> oh no, I took the beer++ as multiple beers rather than coding addition
[17:55] <JFo> :)
[17:58] <cking> is beer a unsigned int or signed int? I'd hate it to wrap to -ve
[17:58] <JFo> cking, it is a Long
[17:58] <cking> unsigned or signed long?
[17:58] <JFo> either way, it is big ;)
[17:59] <cking> a big negative is bad for the beer gut
[17:59] <JFo> probably unsigned
[17:59] <JFo> given memory during its use
[18:01] <cking> struct lame_beer { unsigned int beer:1; };  knowing my luck
[18:11] <apw> cking, thats all you can take anyhow
[18:11] <cking> yep
[18:25] <manjo> apw, processor LNXCPU:00: registered as cooling_device0
[18:26] <JFo> cking, http://www.youtube.com/watch?v=WESUiQ07ibY
[18:27] <cking> JFo, that's an old TV ad
[18:27] <JFo> indeed
[18:37] <rsalveti> guys, I have some patches I got from TI in my tree and I wanted to publish it somewhere, and kernel.ubuntu.com seems to be the best place to go
[18:38] <rsalveti> is there an easy way to get access to it?
[18:38] <rsalveti> otherwise I can just push it elsewhere
[18:51] <JFo> <-lunch
[18:57] <manjo> rsalveti, you could send a request pull to the mailing list
[18:58]  * tgardner lunches
[18:58]  * manjo getting lunch will be back soon 
[18:58] <rsalveti> manjo: I know, but is not only the kernel team would take use from it, it's useful to send to the TI guys also, and our team if anybody wants to test them
[18:59] <rsalveti> it's just a working branch, before sending to review and etc
[19:02] <manjo> rsalveti, you could also try asking in #linaro
[19:02] <manjo> I assume they might be the right people to deal with it
[19:05] <rsalveti> well, it's just a bunch of patches for arm
[19:06] <ogasawara> rsalveti: I believe tgardner (who just went to lunch) is the gatekeeper for adding accounts to kernel.ubuntu.com/git
[19:09] <rsalveti>  ogasawara: thanks, will try to ping him later then :-)
[19:28] <vanhoof> apw: ping
[19:28] <apw> pong
[19:28] <apw> vanhoof, ^^
[19:31] <vanhoof> apw: did that bug match what you were after?
[19:32] <apw> vanhoof, yeah i think so
[19:34] <vanhoof> apw: what grapevine did this come through :)
[20:03]  * apw calls it a day
[20:07] <cking> it's a wrap
[20:19] <JFo> pgraner, http://failblog.files.wordpress.com/2010/08/098d342c-a365-44f7-a35f-aa398398404f.jpg
[20:19] <JFo> :)
[20:22] <jjohansen> hehe
[20:41] <pgraner> JFo, rofl
[20:42] <JFo> :-)
[20:53]  * jjohansen lunch
[22:15] <vanhoof> JFo: http://sfbay.craigslist.org/eby/cto/1879395238.html
[23:24]  * manjo out for the moment