**** BEGIN LOGGING AT Thu May 05 02:59:57 2011
May 05 15:00:43 <ppisati> GrueMaster: lp758961
May 05 15:00:49 <ppisati> bug 758961
May 05 15:00:50 <ubot2> Launchpad bug 758961 in linux-ti-omap4 "WARNING: at /build/buildd/linux-ti-omap4-2.6.38/drivers/tty/tty_mutex.c:31 tty_lock 0x30/0x4c()" [Medium,New] https://launchpad.net/bugs/758961
May 05 15:01:04 <GrueMaster> Yes?
May 05 15:01:17 <ppisati> GrueMaster: did you do anything particular to get it?
May 05 15:01:23 <GrueMaster> I booted.
May 05 15:01:28 <ppisati> ah :)
May 05 15:02:13 <ogra_> that might be your problem then ... :)
May 05 15:02:19 <GrueMaster> Most of the bugs I file like this are because apport discovered them and autolaunched.  I allow it to confinue so that if I can reproduce the bug, I can add more info.
May 05 15:03:53 <wschaub> I'm looking into making some arm build slaves (on some Efika MX smarttops) does the arm port use launchpad-buildd? If so I have a couple of questions.
May 05 15:05:02 <ogra_> wschaub, i think NCommander has some experience setting up a local lp-buildd instance
May 05 15:06:54 <wschaub> the main thing I'm trying to figure out is where the "buildd-slave-chroot-tool" can be found that is mentioned in the readme in the launchpad-buildd source dir.
May 05 15:07:14 <wschaub> I dont see anything like that in the launchpad source tree.
May 05 15:08:45 <wschaub> I guess I could try using pbuilder to make a chroot but I don't know if thats a great idea or not.
May 05 15:09:53 <GrueMaster> wschaub: I use pbuilder to do individual builds.  For a more automated system, there are other tools in the pool.
May 05 15:11:59 <wschaub> I was basically told to set up a build farm that can be used with launchpad. so thats why I'm going in this direction. out of curiosity what other tools are you referring to?
May 05 15:13:19 <GrueMaster> I'd have to look at apt-cache.  Can't remember.  Question came up a few weeks ago.
May 05 15:15:15 <ogra_> wschaub, btw, already tried #launchpad and #soyuz ?
May 05 15:16:04 <wschaub> No, but I will.
May 05 15:47:49 <wschaub> #soyuz seems to not even be a channel on freenode.
May 05 15:51:23 <ogra_> probably its ##soyuz or ##Soyuz
May 05 15:51:43 <ogra_> ask the #launchpad guys, i guess they will know
May 05 16:44:43 <wschaub> ogra_ I got an answer its located at lp:~lamont/launchpad-buildd/chroot-scripts
May 05 16:45:02 <wschaub> thanks.
May 05 17:13:23 <ppisati> anyone with a panda: dmesg| grep -A 1 L310
May 05 17:13:37 <ppisati> it it says:
May 05 17:13:42 <ppisati> CACHE_ID 0x410000c4
May 05 17:13:47 <ppisati> according to this:
May 05 17:13:52 <ppisati> http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0246d/Beidiajg.html
May 05 17:14:12 <ppisati> we have a L310 (r3p0)
May 05 17:14:23 <ppisati> so, i think we need this:
May 05 17:14:32 <ppisati> http://permalink.gmane.org/gmane.linux.ports.arm.kernel/106676
May 05 17:14:54 <ppisati> but the option is off
May 05 17:15:03 <ppisati> i mean, we have this patch but it's off
May 05 17:18:47 <GrueMaster> So, try with it on and see if it explodes.  If it looks good initially, ping me with a kernel link for more testing (after UDS).  :P
May 05 17:19:29 <ppisati> since we pull from linaro, what if i shot an email in their mailing list?
May 05 17:19:38 <ppisati> anyway, testing it right now
May 05 17:19:42 <ppisati> and it works for me
May 05 17:20:40 <GrueMaster> Cool.  rsalveti, what is your take?
May 05 17:20:54 <ogra_> linaro might indeed be intrested to turn it on for their kernel too
May 05 17:21:05 <ppisati> just a small note
May 05 17:21:15 <ppisati> in the datahseet it says:
May 05 17:21:30 <ppisati> [a] This value is pin dependent, depending on how external CACHEID pins are tied.
May 05 17:21:47 <ppisati> near the CACHE_ID
May 05 17:22:17 <GrueMaster> So there is a chance that this is irrelevant to omap4?
May 05 17:22:24 <ppisati> no no
May 05 17:22:30 <ppisati> this is omap4 relevant
May 05 17:22:36 <rsalveti> yeah, makes sense to have it
May 05 17:22:43 <ppisati> at least if you have that msg in dmesg
May 05 17:22:49 <ppisati> it means we have a L310 ctrl
May 05 17:22:56 <ppisati> the point is, which revision do we have?
May 05 17:23:05 <ogra_> tnen linaro will probably only want to enable it in andys kernel
May 05 17:23:18 <ppisati> if it's r3p0, then the errata applits
May 05 17:23:20 <ppisati> applies
May 05 17:23:24 <ppisati> and at least my panda
May 05 17:23:25 <ogra_> since their official kernel is omap3 and 4
May 05 17:23:30 <ppisati> has that revision
May 05 17:24:37 <ppisati> anyway, i'll shot an email to the linato ml and see the reaction
May 05 17:24:50 <rsalveti> ppisati: cool, thanks
May 05 17:25:39 <rsalveti> CONFIG_ARM_ERRATA_753970 is also not set at linaro-omap
May 05 17:27:17 <ppisati> let me recompile a SMP kernel, and do some more testing...
May 05 18:21:08 <ppisati> if you want to try a kernel with that errata on: http://people.canonical.com/~ppisati/ERRATA_753970/linux-image-2.6.38-1209-omap4_2.6.38-1209.13_armel.deb
May 05 19:10:32 <Torfbolt> where do i get the latest sources for the gnuarm toolchain? gnuarm.org is dead and gnuarm.com is outdated.
May 05 19:25:20 <rsalveti> Torfbolt: try asking at #linaro
May 05 19:26:04 <Torfbolt> rsalveti, ok thx
May 06 00:40:06 <Neko> In file included from up-device-csr.c:36:
May 06 00:40:06 <Neko> /usr/include/libusb-1.0/libusb.h: In function 'libusb_fill_control_transfer':
May 06 00:40:06 <Neko> /usr/include/libusb-1.0/libusb.h:928: error: cast increases required alignment of target type
May 06 00:40:11 <Neko> anyone seen this compiling upower?
**** ENDING LOGGING AT Fri May 06 02:59:57 2011