**** BEGIN LOGGING AT Wed Dec 14 02:59:57 2011 Dec 14 03:04:04 FWIW, keyboard repeat on tty is fine on an external USB keyboard Dec 14 03:04:14 So it must be something in the kb controller Dec 14 03:05:38 Feels weird to have a full-width keyboard for the first time in years Dec 14 03:05:54 heh I'd believe it Dec 14 03:06:01 the EC driver is hacky as shit Dec 14 03:06:11 EC? Dec 14 03:06:40 event controller Dec 14 03:07:06 controlls the keyboard and mouse Dec 14 03:08:17 So like evdev Dec 14 03:09:07 no Dec 14 03:09:07 cause it is hardware Dec 14 03:09:25 Righto Dec 14 03:10:08 the asusec is the controller for the keyboard and mouse Dec 14 03:10:15 Ah, that fucker Dec 14 03:10:30 and a few other little things Dec 14 03:10:37 Quite often in the previous install it would spew printks so fast I couldn't do anything but hard-reboot Dec 14 03:12:53 I was wondering what asusec was for. Dec 14 03:12:58 Nice to know. Dec 14 03:13:31 the asusec does a little more Dec 14 03:13:40 but that is the main thing Dec 14 03:19:39 yup Dec 14 03:20:43 Does tf101 have a hardware AES module? And if so, does ubuntu leverage it? Dec 14 03:21:03 Some of my programs (e.g. mutt) seem to be hanging a lot, and my first guess is they're churning TLS Dec 14 03:21:55 Hm, or it could just be that python is really crap Dec 14 03:21:59 10602 twb 20 0 8800 3568 1680 R 2 0.5 0:00.09 python -c import netrc; print netrc.netrc().authenticators('imap.cyber.com.au')[0] Dec 14 03:22:46 yes, and not really at this point I guess Dec 14 03:22:50 never tried Dec 14 03:23:06 but there is hardware aes Dec 14 03:24:57 Since bt isn't working atm I'm doing this: update-rc.d bsp-tf101 disable Dec 14 03:25:03 So at least I can halt reliably for now Dec 14 03:25:17 heh Dec 14 03:25:24 fair enough Dec 14 03:25:35 the other stuff in the bsp is for CrOS kernel so it wont affect you Dec 14 03:25:42 So next week when I come in yelling that it isn't starting, that is why ;-) Dec 14 03:26:12 haha ok Dec 14 04:20:54 lilstevie: is there a way to detect (programmatically) if the dock is attached? Dec 14 04:24:40 I'd assume the extra devices show up in /sys somewhere? Dec 14 04:24:56 http://paste.ubuntu.com/769703/ little /etc/cron.hourly/battery job I wrote to get a feel for battery consumption rate Dec 14 04:25:14 infinity: unfortunately no, they still appear and if you cat them it complains to all the login ttys Dec 14 04:25:33 infinity: so right now I think that cron job will print gank all over my screen occasionally Dec 14 04:26:18 (I also have a battery monitor in .screenrc, but that's not logging, so I can't look at the rate-of-change.) Dec 14 04:29:06 tegra-i2c tegra-i2c.3: no acknowledge; tps6586x 4-0034: failed reading at 0x20; Failed to set dvfs regulator vdd_cpu; Failed to set regulator vdd_cpu for clock cpu to 1000 mV; cpu-tegra: Failed to set cpu frequency to 1000000 kHz Dec 14 04:29:19 ^^ any idea whart those dmesg's are about? It sounds like it's failing to save my battery Dec 14 04:34:39 lilstevie: btw why was apmd installed instead of acpid? Dec 14 04:34:49 lilstevie: is apmd an OMAPism? Dec 14 04:35:08 And more importantly, is suspend-to-RAM working yet? Dec 14 04:48:19 there is no acpi on arm Dec 14 04:48:30 and no suspend functions do not work Dec 14 04:48:52 well more correctly waking up from suspend functions does not work properly Dec 14 04:57:12 lilstevie: well, acpi_listen can see hardware keys being pressed Dec 14 04:57:20 That's how I'm triggering shutdowns right now Dec 14 04:57:46 (re suspend -- OK, thanks.) Dec 14 04:58:51 lilstevie: Hrm, suspend is working on the ac100. Perhaps some bits need merging between trees? Dec 14 04:59:07 twb: my point is acpi is not really all there for arm Dec 14 04:59:11 infinity: no Dec 14 04:59:24 infinity: already spoke to ogra et al. with that Dec 14 04:59:32 the ac100 used some nvec stuff for it Dec 14 04:59:37 we don't use nvec Dec 14 04:59:44 Ah. Dec 14 04:59:48 lilstevie: OK, hardware-wise I see your point. From a practical perspective, should I uninstall acpid and install something "better"? Dec 14 05:00:12 and, the issue with suspend is the framebuffer Dec 14 05:00:13 (The goal being to respond to power/volup/voldn and kb media buttons like brightup/brightdn) Dec 14 05:00:29 twb: evdev does that :p Dec 14 05:00:55 I mean without resorting to gnome-power-manager or kpowerwhatever Dec 14 05:01:13 oh i see Dec 14 05:01:17 In the x86 world you just install acpid and acpi-support, but for some reason oneiric doesn't even seem to *have* an acpi-support package Dec 14 05:01:19 well that is a bit more difficult Dec 14 05:01:35 and yes, that is because we don't have acpi tables Dec 14 05:01:39 lilstevie: right now acpid is WORKING, which is partly why I'm confused. Dec 14 05:01:43 as in, not at all Dec 14 05:01:59 we have a kernel maintained device tree Dec 14 05:02:05 which will fill in a few of the blanks Dec 14 05:02:09 but not enough Dec 14 05:02:38 twb@elba[Desktop]$ config.guess ==> armv7l-unknown-linux-gnu Dec 14 05:02:38 twb@elba[Desktop]$ acpi_listen ==> video/brightnessup BRTUP 00000086 00000000 Dec 14 05:02:43 infinity: anyway, after suspend, the framebuffer keeps getting suspended Dec 14 05:03:46 infinity: under CrOS_2.6.38 it is worse :p it doesn't even wake up Dec 14 05:04:52 and twb right, there are some standard features which will Dec 14 05:05:21 Ah, OK Dec 14 05:05:23 Does android actually suspend the tf though when you leave it or press the power button? Dec 14 05:05:26 So the kernel is basically faking it Dec 14 05:05:35 TheMuso: yes Dec 14 05:05:48 Ah ok. Dec 14 05:05:54 Very responsive in coming back then. Dec 14 05:06:15 TheMuso: the difference is minimal Dec 14 05:06:33 sometimes when you wake it up it is instant, that did not go all the way to LP0 Dec 14 05:06:51 when there is about 1-1.5sec lag, that is waking up from WB0/LP0 Dec 14 05:08:13 ah ok. Dec 14 05:09:03 Are they registers or what? Dec 14 05:09:42 Hmm, http://www.faqs.org/patents/app/20090204837 ? Dec 14 05:10:37 kinda Dec 14 05:10:42 PMIC Dec 14 05:10:57 which has control registers Dec 14 05:12:47 btw, can I use any old mains<-->usb power brick? Dec 14 05:12:53 no Dec 14 05:12:59 Bugger Dec 14 05:13:28 I want a second one to leave in the office rather than carrying it with me every day Dec 14 05:14:28 how typical Dec 14 05:14:34 trying to debug the suspend issue Dec 14 05:14:44 cant trig the damn bug Dec 14 05:15:00 actually Dec 14 05:15:04 thats a good thing Dec 14 05:15:08 lol Dec 14 05:15:16 this is the first time I have done it dockless Dec 14 05:15:27 maybe the bug is in the dock resume :p Dec 14 05:15:28 THat means something. Dec 14 05:15:38 Or something USB. Dec 14 05:15:42 WHich doesn't surprise me. Dec 14 05:15:50 hah Dec 14 05:16:07 What interconnect does the dock use anyway? I just kinda assumed it was power + usb Dec 14 05:16:21 a very complex interconnect Dec 14 05:16:23 plus a few other random pins, of course Dec 14 05:16:38 lilstevie: custom asus one, or custom tegra one? Dec 14 05:16:47 usb+gpio+power+i2c+i2s Dec 14 05:16:58 (As if USB isn't complex enough interconnect on its own :P) Dec 14 05:17:31 the keyboard runs off a combination of GPU+i2c Dec 14 05:17:58 er Dec 14 05:18:00 GPIO Dec 14 05:18:04 heh Dec 14 05:18:37 Oh wow, I thought the keyboard would be USB. Dec 14 05:19:22 the mouse is i2c and i2s Dec 14 05:19:48 Even more weird. Dec 14 05:20:02 well not really Dec 14 05:20:12 mouse as in touchpad? Dec 14 05:20:15 it implements a ps/2 like interface over that Dec 14 05:20:20 yes Dec 14 05:20:20 I guess they wanted to keep the USB free for the USB ports. Dec 14 05:20:36 well technically the USB controller is in the dock ;) Dec 14 05:20:46 Yeah, another UBhub... Dec 14 05:20:49 if I was doing it, I'd have just run the keyboard and touchpad as USB off a UHCI controller in the dock Dec 14 05:20:51 usb hub... Dec 14 05:21:30 the keyboard is based of nvex Dec 14 05:21:33 nvec* Dec 14 05:21:33 How many ports can your typical UHCI controller have soldered onto it? Four? Eight? Dec 14 05:21:52 gpio is the primary interface Dec 14 05:21:56 If it was four you could just have two ports on the dock, plus one for the kb and one for the tp Dec 14 05:23:13 TheMuso: can you tack on to that blueprint that I need to reverse the off state for the lid switch Dec 14 05:23:15 :p Dec 14 05:23:35 and also, right on queue Dec 14 05:23:42 lilstevie: What does it have to do with that daemon Dec 14 05:23:45 dock+suspend == bad times Dec 14 05:23:52 TheMuso: nothing, just it is dock related :p Dec 14 05:24:10 lilstevie: Fair enough. You hsould have write access to the whiteboard of the blueprint... Dec 14 05:24:14 But I can add it. Dec 14 05:24:21 yeah I just CBF :p Dec 14 05:24:32 I really should do a kernel blueprint Dec 14 05:25:02 Yeah that would be good, I would like to know what you have planned. Dec 14 05:25:13 heh :) Dec 14 05:26:00 that kinterruptive stuff also is interconnected with the dock :( Dec 14 05:26:17 no trace of it in my dmesg, connect dock, bam Dec 14 05:26:25 lilstevie: added. Dec 14 05:26:30 ta Dec 14 05:27:07 ok, so will not suspend with the usb cord plugged in :p Dec 14 05:29:14 lol I love it when one gets side tracked from something else because the point of discussion is interesting enough to dig deeper into a problem. :) Dec 14 05:30:41 heh :p Dec 14 05:30:56 well I have been meaning to dig deeper into suspend Dec 14 05:31:13 cause man will that push batt life to extreme levels Dec 14 05:31:21 Yep. Dec 14 05:34:15 f*** it Dec 14 05:34:21 I cant trigger the damn bug again Dec 14 05:34:48 this is annoying, it is what happens every time Dec 14 05:35:13 heh Dec 14 05:35:19 and when i do trigger it, I am nowhere near a computer that will allow me to remote access it and get detailed logs rather than a 500ms flash Dec 14 05:36:32 holy crap Dec 14 05:36:37 I don't believe it Dec 14 05:36:43 I want to run sleepd Dec 14 05:36:58 plugging in the usb cable, hooked to the computer stops the bug Dec 14 05:37:01 Which basically just does pm-suspend if it hasn't seen keyboard input for ten minutes Dec 14 05:37:05 unplug, bang it is back Dec 14 05:37:28 Actually I should install it now and just configure it to turn off the backlight Dec 14 05:37:40 Since that's like 30% of the power drain Dec 14 05:38:23 lilstevie: weird. Dec 14 05:38:28 Anyway, gotta run. Dec 14 05:38:59 TheMuso: weird is right, plug usb cable in, resume bug goes away Dec 14 05:39:25 unplug it, within 30s bug starts back Dec 14 05:39:30 later TheMuso Dec 14 05:46:41 got it Dec 14 05:47:17 TheMuso: when you are around; figured out why it locks when the usb plug is in Dec 14 05:48:12 TheMuso: when the usb plug is in it prevents suspend. when unplugged it gets into a suspend/wake loop Dec 14 05:48:48 now just need to figure out why wake from suspend goes into a suspend/wake loop **** ENDING LOGGING AT Wed Dec 14 06:20:29 2011 **** BEGIN LOGGING AT Wed Dec 14 06:22:15 2011 Dec 14 06:33:39 mplayer says: mplayer: Symbol `ff_codec_bmp_tags' has different size in shared object, consider re-linking Dec 14 06:34:50 sudo mplayer http://radio1.internode.on.net:8000/117 ==> mplayer: relocation error: mplayer: symbol __aeabi_f2ulz, version LIBAVCODEC_53 not defined in file libavcodec.so.53 with link time reference Dec 14 06:35:04 >sad face< Dec 14 06:40:04 Hmm, that's mplayer1 Dec 14 06:40:09 * twb tries mplayer2 Dec 14 06:43:39 Same issue with mplayer2 Dec 14 06:47:27 ok I am kinda getting a little confused Dec 14 06:47:32 twb: which releasE? Dec 14 06:47:42 also mplayer would be terrible on unaccelerated hw Dec 14 06:47:56 there was a compiler issues which had libav emitting extra symbols on oneiric IIRC Dec 14 06:48:00 I only want audio Dec 14 06:48:07 It's just my scripts are set up to assume mplayer atm Dec 14 06:48:08 micahg: this is on oneiric Dec 14 06:48:30 ah, mplayer might need a rebuild if it's failing Dec 14 06:48:38 I could probably learn xmms2 or something but today ICBF Dec 14 06:48:43 ok, so this is what is happening Dec 14 06:49:27 lilstevie: won't *all* video be sucky without hw accel -- not just mplayer? Dec 14 06:49:29 as soon as the wake lock is removed (by unplugging the usb cable) suspend: sys_sync; suspend: enter suspend Dec 14 06:49:38 twb: actually Dec 14 06:49:49 all video will be sucky even with acceleration Dec 14 06:50:06 Why? Dec 14 06:50:09 until you start doing processing on the AVP Dec 14 06:50:16 cause tegra sucks ass Dec 14 06:50:20 k Dec 14 06:50:46 My simple-minded brain reduces that down to "hardware acceleration" Dec 14 06:51:16 ok, so basically as soon as every last piece of hw has come back from suspend; it calls back to suspend 0.o Dec 14 06:51:18 no idea why Dec 14 06:51:39 twb: it is a little more complex than that, the GPU is weak Dec 14 06:51:40 to save power duh :P Dec 14 06:52:06 twb: yeah but it resumes from the recalled suspend after 0.310sec Dec 14 06:52:09 eh I am coming from matrox and intel Dec 14 06:52:15 ^^measured by the kernel timer Dec 14 06:52:27 twb: no what i mean is the tegra GPU is really weak Dec 14 06:52:36 even weaker than an i915? Dec 14 06:52:37 unless video gets preprocessed by the AVP Dec 14 06:52:37 Wow Dec 14 06:53:05 hum, ok Dec 14 06:53:08 for mpeg vid Dec 14 06:53:31 thats what all those .axf files are in /lib on android Dec 14 06:53:43 they are programs for the avp to aid decoding Dec 14 06:54:08 presumably that's only useful if you're watching video, tho Dec 14 06:54:16 not e.g. playing doom Dec 14 06:55:03 yes Dec 14 06:55:06 correct Dec 14 06:55:26 Righto Dec 14 07:02:01 btw for some reason when I rebooted out of android, the caps lock light was on, and it won't turn off Dec 14 07:02:13 (Which is a surprise to me; I didn't even know there WAS a light.) Dec 14 07:02:29 lol Dec 14 07:16:10 micahg: there's this libavcodec-extra-53 that Provides libavcodec53, is it also likely to be buggered? Dec 14 07:16:28 twb: idk Dec 14 07:16:39 * twb tries Dec 14 07:18:22 answer: it does Dec 14 07:18:37 Er, "libavcodec-extra-53 is also buggered" Dec 14 07:21:51 hm Dec 14 07:22:10 http://pastie.org/3014429 Dec 14 07:23:04 lilstevie: how do you get that out? netconsole? Dec 14 07:23:18 (assume you're still banging against suspend issues.) Dec 14 07:23:48 because once you plug in the USB it triggers wake lock Dec 14 07:24:08 Ah Dec 14 07:24:16 it seems to fully wake up Dec 14 07:24:26 then bam out of nowhere suspends again Dec 14 07:25:01 Does the suspend key have a down and an up event? Dec 14 07:25:01 which is what that portion of the dmesg is Dec 14 07:25:12 it isn't that :p Dec 14 07:25:14 Maybe it suspends before the up even arrives, so it thinks you're still holding it down Dec 14 07:25:16 OK Dec 14 07:25:23 I called suspend from the power menu :) Dec 14 07:25:44 What happens if you throw away the GUI and call it from /sys ? ;-P Dec 14 07:26:10 no idea really :p Dec 14 07:26:34 the only way I know to suspend from /sys isn't in the kernel Dec 14 07:27:48 Might be /proc I forget Dec 14 07:30:32 Something like echo mem > /sys/power/state Dec 14 07:31:12 yeah Dec 14 07:31:14 And if you cat it it tells you someting like "swap mem" to mean it supports suspend to both disk and ram Dec 14 07:31:41 Of course that's JUST suspending, and pm-utils and friends do all sorts of crazy shit in addition to that to work around failtastic hw Dec 14 07:31:48 only supports mem Dec 14 07:32:01 like halting bt and turning all the LEDs off and rmmoding things Dec 14 07:32:39 It wouldn't surprise me in the slightest if one of those things was actually CAUSING the resume problems Dec 14 07:33:06 lol Dec 14 07:33:19 I will try it Dec 14 07:33:20 :) Dec 14 07:33:27 just need to call reboot Dec 14 07:33:35 I bet you get new and excitingly different problems Dec 14 07:33:44 something has to be calling suspend Dec 14 07:33:48 Just remember to turn off the GUI and esp. gnome-power-manager first Dec 14 07:33:55 heh Dec 14 07:34:09 service lightdm stop Dec 14 07:34:12 problem solved Dec 14 07:34:39 You could just "stop lightdm" Dec 14 07:37:09 fwiw identical result Dec 14 07:37:17 well surface is identical Dec 14 07:37:34 will check out the dmesg in 2 secs Dec 14 07:38:21 k Dec 14 07:43:43 yep same result Dec 14 07:44:13 Aw Dec 14 07:44:35 Well at least we know it's not any of the helper code now Dec 14 07:44:43 yeah Dec 14 07:44:51 which I already figured anyway :) Dec 14 07:45:27 the most I can see at the moment is a kernel owned task is calling the suspend Dec 14 07:45:36 as part of the end of waking up from suspend Dec 14 07:45:50 So-rry Dec 14 07:45:56 :p Dec 14 07:46:02 You can just tell me to STFU if I'm not helping Dec 14 07:46:03 worth a try though to confirm Dec 14 07:47:10 STFU every little idea helps Dec 14 07:48:20 maybe... it only happens when you hold the tablet upside down! Dec 14 07:48:40 lol Dec 14 07:49:27 well I may have been misinterpreting the log Dec 14 08:02:30 WTF Dec 14 08:02:43 festival --tts book, half a sentence in it goes "=== PAUSE ===" Dec 14 08:02:48 That has never happened before Dec 14 08:06:39 Goddammit, no bedtime stories for me tonight Dec 14 08:06:56 The actual thing pausing is aplay AFAICT Dec 14 08:09:10 Hmm, why does free -m say I only have 728MB of RAM? Dec 14 08:09:44 Surely it doesn't need >256MB reserved for the GPU or something? :-/ Dec 14 08:09:56 Anyway, home time. Dec 14 10:43:29 <_Thomas> Hmm, I have this usb wifi stick that works with open access points, but when I try to connect to encrypted ones, it fails to connect Dec 14 10:43:46 <_Thomas> (I'm trying to connect using the network wizzard) Dec 14 10:43:56 <_Thomas> erh, Network Manager Dec 14 10:46:48 is that with one of the official ubuntu images from cdimage ? Dec 14 10:48:41 <_Thomas> ogra_: No it's linaro's ubuntu-based image, but it's using most of it's packages from the ubuntu pool Dec 14 10:49:27 that doesnt matter, they are built differently (using metapackages instaed of tasks which can result in different package/dependency selection) Dec 14 10:49:45 so you might miss something Dec 14 10:49:58 do you see any messages in dmesg ? Dec 14 11:00:05 <_Thomas> ogra_: yes, I got some messages in dmesg Dec 14 11:00:17 pastebin them Dec 14 11:00:41 it could also be a missing kernel config option or so Dec 14 11:00:49 or missing firmware etc Dec 14 11:01:06 btw, what HW is that ? Dec 14 11:03:34 <_Thomas> ogra_: http://pastebin.com/Qwrs3a3e Dec 14 11:03:47 <_Thomas> rtl8187 Dec 14 11:04:44 do you see it loading the right firmware (thats not in your dmesg, a full copy would have been better than a snippet) Dec 14 11:04:57 and do you have linux-firmware installed ? Dec 14 11:05:31 <_Thomas> I can yank out the stick, and put it back in again Dec 14 11:05:56 yeah, check if you see anything about firmware and also check if you have that package installed Dec 14 11:06:14 and again, what hardware is that ? Dec 14 11:07:46 <_Thomas> RTL8187, as I said above :) Dec 14 11:08:32 _Thomas: which board are you using? Dec 14 11:08:46 kernel source tree etc Dec 14 11:09:06 right Dec 14 11:09:22 <_Thomas> my own board, kernel source tree is linux-samsung tree Dec 14 11:10:01 ah right. you make the libEGL for that not yet released samsung board? Dec 14 11:10:06 <_Thomas> :) Dec 14 11:11:22 it is the Origen board? Dec 14 11:12:26 <_Thomas> xranby: No, but it's the same AP Dec 14 11:13:09 _Thomas: can you check if the same bug exist on the Origen boarD? Dec 14 11:13:39 * ogra_ would guess its either a missing kernel option or some package missing Dec 14 11:14:25 <_Thomas> xranby: Kind of hard, since I don't have any origen boards Dec 14 11:15:33 <_Thomas> ogra_: Maybe, but I don't see what could be missing from the kernel Dec 14 11:16:42 i dont either since i dont know your kernel ... the ubuntu kernels have a good bunch of common options they all share and that specifically is true for external devices like USB ... Dec 14 11:17:41 (and independent of arch etc) Dec 14 11:18:23 <_Thomas> But could this be USB related, given that the device is detected, and works with open APs? Dec 14 11:18:41 unlikely ... but it could for example be driver related Dec 14 11:18:54 <_Thomas> And with the regards to cfg80211, I've enabled almost everything (only debugging parts not enabled) Dec 14 11:19:07 probably you should :) Dec 14 11:19:26 might get you some more insight (even though it seriously spams dmesg) Dec 14 11:20:22 <_Thomas> with regards to the driver itself, there was no options to choose from Dec 14 11:20:28 <_Thomas> other than mode / integrated / none Dec 14 11:20:32 <_Thomas> mode=module Dec 14 11:20:39 <_Thomas> and I chose to compile as module Dec 14 11:20:40 no, but there might be patches we have in ubuntu and you are missing Dec 14 11:20:52 <_Thomas> that is true Dec 14 11:20:59 <_Thomas> I'm running 3.2-rc1 Dec 14 11:21:00 what kernel version is that ? Dec 14 11:21:08 <_Thomas> fairly recent Dec 14 11:21:12 ah, same we have for panda and omap3 Dec 14 11:21:20 that should do Dec 14 11:21:41 not sure about possible patches though, #ubuntu-kernel might be able to talk about these Dec 14 11:22:15 <_Thomas> I tested the same USB-stick on regular ubuntu 11.04 (x86, that is) Dec 14 11:22:21 <_Thomas> with same issue Dec 14 11:22:31 aha Dec 14 11:22:41 <_Thomas> I had forgot about that until now :D Dec 14 11:25:45 <_Thomas> Should all sticks download firmware? Dec 14 11:25:52 <_Thomas> because there's nothing about firmware in the loggs Dec 14 11:26:01 <_Thomas> not even about failed download/upload or anything Dec 14 11:26:05 it might not report it if its successfull Dec 14 11:26:34 <_Thomas> ok, so it's safe to rule out firmware, then Dec 14 11:26:51 ogra@horus:~$ ls /lib/firmware/rtlwifi/ Dec 14 11:26:51 rtl8192cfw.bin rtl8192cufw.bin rtl8192defw.bin rtl8192sefw.bin rtl8712u.bin Dec 14 11:27:02 thats what i have on my machine in oneiric Dec 14 11:27:22 <_Thomas> no 8187 there Dec 14 11:27:38 no, but often firmware files apply to multiple devices Dec 14 11:28:56 if you actually have the same prob on other HW with the same device i would go to #ubuntu-kernel and ask there Dec 14 11:30:08 oh, and there is bug 802902 Dec 14 11:30:09 Launchpad bug 802902 in linux "Realtek rtl8187b wireless chipset slow speed" [Undecided,Confirmed] https://launchpad.net/bugs/802902 Dec 14 11:30:22 the last comment is intresting Dec 14 11:35:30 <_Thomas> I don't have the b-version of the chipset, it seems Dec 14 12:22:04 doko, just playing with the ac100 you gave me .... as i thought, the kbd cable was only half plugged in Dec 14 12:22:30 armhf feels quite a bit snappier on the desktop i must say Dec 14 12:27:14 ogra_: heh yeah hf is amazing Dec 14 12:27:30 is libreoffice working on hf yet? Dec 14 12:27:37 nope, didnt build yet Dec 14 12:27:43 patches accepted Dec 14 12:27:43 ah ok Dec 14 12:27:46 ;) Dec 14 12:28:01 ogra_, including the mmap fix? Dec 14 12:29:16 doko, no idea if janimo included that in the precise upload from yesterday Dec 14 12:29:32 i'll upgrade to the 3.0 kernel soon Dec 14 12:29:44 janimo, ^^^ ? Dec 14 12:29:47 for now i want to see how much rendering improves by using hf Dec 14 12:30:07 firefox seems to scroll a lot smoother Dec 14 12:39:26 lool, could you care about the flash-installer merge? Dec 14 12:39:55 doko, we are still discussiong it Dec 14 12:40:06 its not clear yet if we will switch at all Dec 14 12:40:08 ahh, ok, so not mine Dec 14 12:40:24 oh, wait you mean adobe flash? Dec 14 12:40:27 or flash-kernel Dec 14 12:42:18 (flash-installer is adobe, no ?) Dec 14 13:34:35 infinity, are you around today or still ill ? Dec 14 13:35:14 * ogra_ is about to roll an nvidia-tegra driver for precise restricted/multiverse and could need a package review in NEW then Dec 14 13:45:29 ogra_: have you obtained a armhf version? Dec 14 13:45:34 no Dec 14 13:45:45 up to nvidia to provide one Dec 14 13:46:04 i dont see aaronp in #ac100 anymore, else i would have asked him Dec 14 14:14:23 armhf rocks :) Dec 14 14:16:00 heh Dec 14 14:16:22 ogra: yes yes i find it nifty Dec 14 14:16:47 now a binary driver would really be lovely Dec 14 14:17:36 ogra: right now im also using 256kb default stack by setting * soft stack 256 in /etc/security/limits.conf Dec 14 14:17:56 and my armhf system ticks on fine without any zram swap tricks Dec 14 14:18:33 just that line ? Dec 14 14:18:36 * soft stack 256 Dec 14 14:18:38 ? Dec 14 14:18:40 yes Dec 14 14:18:46 * ogra adds it Dec 14 14:18:56 anything i need ot restart for it to take effect ? Dec 14 14:19:04 it makes pthread's use 256kb stack by default instead of 8Mb for each thread Dec 14 14:19:21 well, i guess i'll reboot Dec 14 14:24:04 in my humble optinion: since a ubuntu unity2d system + browser open runs around 321 running threads the default pthread stack size do matter Dec 14 14:24:19 ogra: how does things look on your side? Dec 14 14:24:40 what should be the difference with thet security conf setting Dec 14 14:24:51 there is no feelable difference it seems Dec 14 14:25:08 newly started programs threads should use less memory fore each thread by default Dec 14 14:25:37 programs can still opt in for more stack for each thread.. as i have understood it Dec 14 14:25:47 hm. k Dec 14 14:25:57 we'll see over time i guess Dec 14 14:26:47 hmm, actually seems to eat less ram Dec 14 14:26:54 ogra: now ulimit -a should report stack size 256kb Dec 14 14:27:00 yes, thats the idea Dec 14 14:27:09 programs start to use less ram automagically Dec 14 14:27:10 it does indeed Dec 14 14:27:32 i wonder what the implications would be if we set it by default Dec 14 14:29:33 dont set it too low. if the default are 64kb then unity will not work around 128kb jsome woud have trouble unzipping stuff 256 looks fine for most applications that i have tested Dec 14 14:30:05 k Dec 14 14:30:23 well, what i mean is ... there doesnt seem to be any default value in the file Dec 14 14:30:37 and i wonder if there is a reason for this Dec 14 14:31:00 the default have increased during the last years, i think the default are set in eglibc source Dec 14 14:31:30 ah, not a kernel thing then Dec 14 14:31:31 some years ago the default thread size on x86 was 2Mb now its 8Mb for most architectures Dec 14 14:31:36 ogra, xranby: does changing the stack limit make much of a difference in practice? I though the memory wasn't really allocated in advance... this just controls how much VMA space is reserved for stack growth Dec 14 14:31:41 doko, any thoughts on the above Dec 14 14:32:02 dmart, well, htop shows a *lot* less ram used Dec 14 14:32:25 with the stuff i have open atm i would usually hit 400M or so Dec 14 14:32:34 and it only reports about 280 Dec 14 14:33:08 Interesting. What is that actually measuring, though? Dec 14 14:33:24 htop ... i think it sums up RES Dec 14 14:33:47 not sure though Dec 14 14:34:47 Interesting if so Dec 14 14:48:08 I just got LP0 suspend working on tf101 Dec 14 14:48:10 :D Dec 14 14:48:19 awesome ! Dec 14 14:48:23 ogra: try http://pastebin.ubuntu.com/770100/ Dec 14 14:48:40 This should help to give an idea of just the thread overhead Dec 14 14:49:32 With 8M stacksize, I get an overhead of about 8.4K per thread Dec 14 14:49:49 (measuring PSS with smem)( Dec 14 14:50:19 ogra: it was something basic too Dec 14 14:50:35 ogra: wakelocks were interfering; damn android Dec 14 14:50:39 dmart, ok, i get 768 with my current setup Dec 14 14:51:04 i bet i cant change the value without a reboot Dec 14 14:51:28 768 what? Dec 14 14:51:34 ogra: ulimit -s 4096 Dec 14 14:51:35 etc Dec 14 14:51:49 dmart, it prints 768 threads created. Dec 14 14:52:07 Just increase THREAD_COUNT ... the choice of value was totally arbitrary Dec 14 14:52:17 ogra: ulimit -s 8192 Dec 14 14:52:20 oddly though, on an ARM board it only creates 157 thread Dec 14 14:52:21 thats the ubuntu default Dec 14 14:52:31 dmart: why is that odd? Dec 14 14:52:39 with 4096 i get only 451 threads Dec 14 14:52:41 dmart: if you use 8Mb for each thread Dec 14 14:53:26 8192 gets me an error Dec 14 14:53:34 seems i'm exceeding the limit Dec 14 14:53:36 Ah, OK, the kernel may require 8MB of backing per thread Dec 14 14:53:38 dmart: it simply means that you have exausted the process adress space quickly by consuming 1.2gb of ram Dec 14 14:53:50 dmart: run ulimit -s 256 Dec 14 14:53:54 and then rerun the test Dec 14 14:54:13 xranby: ah, yes of course Dec 14 14:54:16 bah, and now i cant set anything else but 256 anymore Dec 14 14:54:33 xranby: this shouldn't affect the memory load on the system overall Dec 14 14:54:37 afaik Dec 14 14:54:51 thats not really consistent Dec 14 14:55:02 it does.. if one application consume all ram on the system + all swap as your 768threads*8Mb Dec 14 14:55:04 would do Dec 14 14:55:12 then no program can fork Dec 14 14:55:35 and leave your system in a locked up state Dec 14 14:55:40 xranby: right, with ulimit -s 256 I get 768 threads. But we're not consuming RAM here, just virtual address space in that particular process. Dec 14 14:56:27 xranby: that only happens if overcommit is enabled, and if all those threads actually use 8MB of stack Dec 14 14:56:31 well, running the same stuff on my oneiric armel installed device it starts swapping already Dec 14 14:56:49 99% of threads don't use anything like 8MB of stack Dec 14 14:56:54 (which is just as well) Dec 14 14:56:56 on this armhf install and with the ulimit set to 256 it only uses 00M Dec 14 14:57:05 300M Dec 14 14:57:54 I guess my question is: why does changing the default stack size actually make a difference? Dec 14 15:00:02 dmart: do pthread zero the stack? Dec 14 15:00:14 i have to check Dec 14 15:01:01 xranby: normally, zeroing the stack would be unnecessary. Maybe there are some specific processes allocting their threads' memory explicitly via another mechanism Dec 14 15:01:31 If so, then changing the default stack size system-wide might make a big difference to the memory consumption of some processes but not others Dec 14 15:03:35 xranby: I can't see anything in the pthread_create manpage about pre-zeroing of stacks, and it obviously doesn't happen for my silly test Dec 14 15:06:00 dmart: freebsd have for a long time used a default of 64Kb pthread stack size Dec 14 15:06:57 dmart: i think your question are all valid.. i really dont know why the memory gets consumed Dec 14 15:07:56 ogra: maybe you could run smem with the two stacksize defaults, and see where the memory consumption changes Dec 14 15:08:00 in linux where we allow all programs to overcommit we usually like solutions that allow programs to grab a large block of memory and rely on the linux OOM kilelr to kill the most suitable overcommiter Dec 14 15:08:56 indeed... Dec 14 15:16:20 geez Dec 14 15:16:26 i have a load of 18 Dec 14 15:16:39 and there goes firefox Dec 14 15:17:09 seems it didnt like the 25th tab i opened Dec 14 15:21:52 * ogra wonders why janimo's ac100 3.0 upload doesnt show up yet ... it should be published by now Dec 14 15:22:52 apt only offers me linux-image-2.6.38-1002-ac100 Dec 14 15:25:47 ogra: interesting indeed they are seen here https://launchpad.net/ubuntu/+source/linux-ac100/3.0.8-1.1/+build/3007924 Dec 14 15:26:27 probably stuck in the NEW queue Dec 14 15:59:10 janimo: https://bugs.launchpad.net/ubuntu/+source/linux-ac100/+bug/904313 any possible config issue? Dec 14 15:59:11 Launchpad bug 904313 in linux-ac100 "boot failure using linux-image-3.0.8-1-ac100_3.0.8-1.1 armhf precise" [Undecided,New] Dec 14 16:00:56 ogra: I'm around today. Dec 14 16:01:15 k Dec 14 16:01:19 ogra: Still feeling ill, but I only have two days left at work, I figure I'll tough it out. :P Dec 14 16:01:26 i was a bit distracted from the driver Dec 14 16:01:37 so i didnt do much about it yet, but will Dec 14 16:01:50 playing with armhf on the ac100 is exciting := Dec 14 16:01:51 :) Dec 14 16:02:57 * ogra installs the 3.0.8 kernel from janimo Dec 14 16:03:36 i have got my system bootable again by reverting back to the 2.6.38-1002-ac100 kernel Dec 14 16:03:43 WOAH ! Dec 14 16:03:54 update-initramfs: Generating /boot/initrd.img-3.0.8-1-ac100 Dec 14 16:03:54 *** stack smashing detected ***: /bin/sh terminated Dec 14 16:03:54 Aborted (core dumped) Dec 14 16:04:10 E: /usr/share/initramfs-tools/hooks/udev failed with return 134. Dec 14 16:04:16 geez, that looks bad Dec 14 16:04:32 xranby, might not be the kernel at all Dec 14 16:04:38 hmm i see Dec 14 16:04:42 You see weird things on your ac100 that no one else does. I'm convinced you have bad RAM. Dec 14 16:05:19 infinity: me or ogra? Dec 14 16:05:47 well, i poked around in /etc/security/limits.conf, might be related :) Dec 14 16:05:58 ogra@amun:~/Downloads$ sudo update-initramfs -u -k 3.0.8-1-ac100 Dec 14 16:05:58 update-initramfs: Generating /boot/initrd.img-3.0.8-1-ac100 Dec 14 16:05:58 Writing boot image to /dev/mmcblk0p4 ... done. Dec 14 16:06:03 a manual run works fine Dec 14 16:06:11 lets see if it comes back up again Dec 14 16:06:14 * ogra reboots Dec 14 16:07:00 xranby: ogra. Dec 14 16:07:53 nope, same issue here Dec 14 16:07:59 hangs at the toshiba logo Dec 14 16:08:11 janimo, did you actually test that kernel before uploading it ? Dec 14 16:09:10 * ogra_ curses ... i just prodded pitti to let it out of NEW, now the images wont boot :( Dec 14 16:09:23 Oops. Dec 14 16:09:32 meta's been updated too? :/ Dec 14 16:09:40 indeed assuming janimo at least booted it once Dec 14 16:09:46 no, neta isnt yet Dec 14 16:09:47 luckily Dec 14 16:09:55 Okay, so not world-ending yet. Dec 14 16:10:02 indeed Dec 14 16:10:02 Cause only people who know it's there will upgrad. Dec 14 16:10:03 e Dec 14 16:10:17 yep Dec 14 16:11:08 Compare configs from 2.6.38 and 3.0.8 and see if there are any obvious differences? Dec 14 16:11:25 there will surely be Dec 14 16:11:45 let me boot back into .38 first Dec 14 16:14:53 * ogra twiddles thumbs waiting for man-db Dec 14 16:17:47 infinity, http://paste.ubuntu.com/770198/ Dec 14 16:19:19 bah, sigh ... DM is gone again Dec 14 16:19:38 -CONFIG_BLK_DEV_DM=m Dec 14 16:19:38 +# CONFIG_BLK_DEV_DM is not set Dec 14 16:20:03 half of bluetooth too Dec 14 16:20:28 Yeah, but nothing in there jumps out as an obvious reason for it not booting either. :/ Dec 14 16:21:01 what is +CONFIG_CPU_RMAP=y ? Dec 14 16:21:23 Not sure, but it looks gone completely. Dec 14 16:21:30 Since it's not replaced in the diff with a # not set Dec 14 16:21:42 yep Dec 14 16:50:59 ogra: maybe +CONFIG_CMDLINE_FROM_BOOTLOADER=y Dec 14 16:51:13 well, we get it from there Dec 14 16:51:22 at least we did in the past Dec 14 16:51:25 if it get the memory wrong, it will crash at logo (or shortly after) Dec 14 16:51:32 ah Dec 14 16:51:34 k Dec 14 16:51:56 i'll let a package build run over night Dec 14 16:52:05 * ogra_ isnt near any cross build machine atm Dec 14 16:52:24 wait until I checked it myself (I'm back home in an hour) Dec 14 16:52:36 k Dec 14 16:56:22 ogra: "Overnight"? linux-ac100 should build in a couple of hours on a Panda or ac100, tops. Dec 14 16:56:38 yeah, but i wont start a build right now Dec 14 16:56:38 (Assuming you export DEB_BUILD_OPTIONS="parallel=2") Dec 14 18:33:27 I'm having trouble getting a bluetooth USB dongle to pair with devices on the Pandaboard. I'm running Ubuntu 11.10 and can scan for devices successfully but cannot pair with them. With the onboard bluetooth, I am not even able to turn bt on, which is why i've resorted to the bt USB dongle. Looking for some help getting the pairing working with the dongle, but am happy to revert back to the onboard bt if someone has any sugges Dec 14 18:34:13 i think there is a daemon missing thats not in the ubuntu archive ... search on launchpad there is a bug about bluetooth on panda Dec 14 18:34:31 it points to the upstream sourfce for that daemon iirc Dec 14 18:35:25 Yes, I've read that but don't fully understand it. Does this mean that there is no way to get bluetooth working period? Dec 14 18:36:48 you have to build that daemon from source until it is packages Dec 14 18:36:52 *packaged Dec 14 18:38:17 hmm...do you know of any resources that describe how to do that? Dec 14 18:39:26 there should be info about this in the upstream source Dec 14 18:39:33 a README or INSTALL doc Dec 14 18:47:00 I'm very inexperienced in compiling this type of thing. Do you think I can find a package that someone's already fixed? Dec 14 18:49:59 i dubt that Dec 14 18:58:33 bummer. Well thank you for your help Dec 14 20:26:54 chroot /root dpkg --purge ac100-tarball-installer Dec 14 20:26:59 cp /root/usr/share/ac100-tarball-installer/zram.conf /root/etc/init/ || true Dec 14 20:27:07 ogra_: What's wrong with this picture? :P Dec 14 20:36:29 infinity, what's wrong whit it besides it being shell script :P ? Dec 14 20:42:28 janimo: The part where he tries to copy a file after he deletes it. :) Dec 14 20:43:07 Which, I guess, it why it needs the || true... Dec 14 20:43:10 *cough* Dec 14 20:47:52 Looks like a perfect example of working code to me (of course I have spent a lot of time reviewing jasper). Dec 14 22:24:09 infinity, whats wrong ? it checks the error handling of cp just fine :P Dec 14 22:25:31 ogra_: You're kidding, I hope? ;) Dec 14 22:25:41 indeed :) Dec 14 22:25:50 Phew. I'm sick. Don't toy with me. Dec 14 22:26:04 go back to your eglibc ... Dec 14 22:26:09 Yeah, yeah. Dec 14 22:26:21 I uploaded a fix for ac100. Dec 14 22:26:28 saw that, thanks Dec 14 22:26:32 (noticed the cp failure flash by while I was reinstalling with armhf) Dec 14 22:26:45 was on my list, i hadnt bothered to look at the code yet Dec 14 22:27:08 yeah, i saw it too today and i know about it since release day Dec 14 22:27:24 Heh. Dec 14 22:27:32 (that it doesnt get installed i knew) Dec 14 22:27:46 That's okay. I have another bug that's going to drive me nuts now (and I suspect I'll find it and fix it on my holidays because I'm OCD). Dec 14 22:28:04 My ARM machines all get several copies of udevd running until I restart udev. Dec 14 22:28:13 Don't have the same behaviour on x86. Dec 14 22:28:41 And those multiple udevs are doing angry things to CPU time. Dec 14 22:28:53 yeah, i noticed in my ac100 install today that it installed to mmcblk0p14 ... Dec 14 22:29:10 while the installed system sees only up to p7 Dec 14 22:29:19 (which actually is the rootfs) Dec 14 22:29:33 That's normal, isn't it? Dec 14 22:29:38 i would blame the udev in initrd to not being carried over properly or some such Dec 14 22:29:59 that the initrd sees twice as many block devices ? Dec 14 22:30:04 i doubt thats normal Dec 14 22:30:30 Either way. udev madness is on my TODO for "later". Dec 14 22:30:49 I noticed it a long time ago on my mx53, but I was running the ancient Freescale kernel and blamed it on that. :/ Dec 14 22:30:58 Just noticed it more recently on other machines with distro kernels. Dec 14 22:31:03 I guess I should have looked into it back then. Dec 14 22:31:31 hmm, i never noticed any udev weirdness until now Dec 14 22:31:43 It's been happening on my quickstart forever. Dec 14 22:31:54 Always have to restart udev after boot to kill off all the extra ones. Dec 14 22:31:54 ah, so pre-precice Dec 14 22:32:08 Yeah, my QS is running oneiric. Dec 14 22:32:13 Panda and ac100 are precise. Dec 14 22:32:19 All show the problem. Dec 14 22:32:24 yeah, that sounds like a stick signalfd or some other weird stuff Dec 14 22:32:37 *stuck Dec 14 22:33:35 Something weird indeed. Dec 14 22:34:48 hmm, checking my fresh install i see 3 instances of udevd Dec 14 22:35:24 the latter two with a four digit pid ... the first one with 236 Dec 14 22:36:06 seems the magic that scott did to carry over the running udevd from the initrd is broken Dec 14 22:38:58 yup and restarting gets me a single process Dec 14 22:44:25 Might not be arm-specific, but perhaps just a weird race that slow hardware exposes. Dec 14 22:44:28 I'll poke it "later". Dec 14 22:44:47 But tonight, I need to finish this eglibc merge and get it in, so I can deal with possible fallout tomorrow. Dec 14 22:50:07 I'll make sure to test it once it lands so you will have plenty of fallout to keep you semi-active. :P Dec 14 22:52:01 GrueMaster: Heh. Well, it's a pretty big merge, I'm more worried about x86 fallout, to be honest. But I'll get some time tonight to test before I upload. Dec 14 22:57:32 * GrueMaster wishes maverick on omap4 would just go away. Getting automated installs working with the same ip address everytime is a pita. Dec 14 22:57:45 When dealing with a panda pool that is. Dec 14 23:08:52 holy crap Dec 14 23:09:53 TheMuso: battery life with LP0 is stupedious, was in LP0 for 7 hours without dropping a single percent Dec 14 23:10:09 tablet battery 100% dock at 73% Dec 14 23:14:19 GrueMaster: Can't you just cheat with a backported uBoot? Dec 14 23:15:16 No, the kernel driver freaks out. I'm already using uboot from oneiric so I can test on newer pandas (maverick only supported A1 due to lookup tables in uboot). Dec 14 23:16:07 And it is the kernel smsc95xx driver that needs to be fixed. Natty+ uses the cpu die-id to generate a unique mac. Dec 14 23:16:52 (although that is only on panda, same driver on beagleXM but patch for die-id isn't upstream). Dec 14 23:21:20 Maverick was 10.10? So, you get to drop support when 12.04 ships? Dec 14 23:21:33 Almost there! Dec 14 23:21:49 Yep. Dec 14 23:26:16 lilstevie: Wow so you fixed the bug? Dec 14 23:27:37 yep Dec 15 01:03:40 lilstevie: have you seen this? http://paste.ubuntu.com/770683/ Dec 15 01:03:48 "fakeroot, while creating message channels: Function not implemented This may be due to a lack of SYSV IPC support." Dec 15 01:04:30 that I have not Dec 15 01:04:38 twb: also, LP0 fixed Dec 15 01:04:52 coo Dec 15 01:04:55 ...l Dec 15 01:05:37 lilstevie: does "fakeroot pwd" work for you? Dec 15 01:06:07 I would hope so... Dec 15 01:06:39 WTF have I done Dec 15 01:06:48 * lilstevie doesn't even have fakeroot installed Dec 15 01:07:02 lilstevie: it's mainly used when building packages Dec 15 01:07:08 yeah I know Dec 15 01:07:12 I have it on the trim Dec 15 01:07:17 where I build my packages Dec 15 01:07:30 Who's sending me a trim for Christmas? Dec 15 01:07:32 Anyone? :) Dec 15 01:07:40 * infinity hears crickets. Dec 15 01:07:56 lol Dec 15 01:09:39 lilstevie: it works if I update-alternatives and change it to use fakeroot-tcp instead Dec 15 01:10:01 lol Dec 15 01:10:24 Which is Bad Juju because IIRC that breaks something else Dec 15 01:10:36 I currentlly have no wifi on my tf101 so I cant install fakeroot to tell you my result Dec 15 01:10:58 k Dec 15 02:02:34 lilstevie: FYI, guy next to me can reproduce fakeroot-sysv issue on his tf101 Dec 15 02:04:08 ok Dec 15 02:06:38 twb: Kernel built without sysvipc? Dec 15 02:06:57 CONFIG_SYSVIPC=y Dec 15 02:06:57 CONFIG_SYSVIPC_SYSCTL=y Dec 15 02:07:09 CONFIG_SYSVIPC_COMPAT=y Dec 15 02:07:19 Probably want all of those for fakeroot to not be a sad panda. Dec 15 02:08:33 infinity: I didn't build the kernel Dec 15 02:08:46 * twb points at lilstevie! Dec 15 02:08:54 scary monkey style Dec 15 02:09:07 There's no /boot/config either :-( Dec 15 02:09:07 \o/ it's done: https://launchpad.net/builders: armhf 11 empty Dec 15 02:09:18 Aha, /proc/config.gz tho Dec 15 02:09:28 Yep, sysvipc is off. FAIL. Dec 15 02:09:48 not set Dec 15 02:09:52 will fix later Dec 15 02:10:00 No rush, fakeroot-tcp works for now Dec 15 02:10:03 I really don't give an f right now :) Dec 15 02:10:11 doko: \o/ Dec 15 02:10:29 I will have to ring up your girlfriend and tell her bad things about you so she leaves you and you have more time for work Dec 15 02:10:36 doko: I'll see if there are any obvious things I can unsnag tomorrow. And keep an eye on stuff here and there while I'm on VAC. Dec 15 02:11:29 twb: lol. I don't give an f because I am working on something else on the project right now so that would acomplish nothing Dec 15 02:12:41 Okey dokey Dec 15 02:12:45 * twb puts down the phone Dec 15 02:13:26 No more underground boxing matches with baby seal pups for you **** ENDING LOGGING AT Thu Dec 15 02:59:57 2011