**** BEGIN LOGGING AT Fri Aug 13 02:59:57 2010 **** ENDING LOGGING AT Fri Aug 13 04:13:39 2010 **** BEGIN LOGGING AT Fri Aug 13 04:14:14 2010 Aug 13 08:47:10 cooloney: Morning Aug 13 09:26:28 ogra: Hi! I started testing your Aug 13 09:26:35 http://cdimage.ubuntu.com/ubuntu-netbook/ports/daily-preinstalled/20100812/maverick-preinstalled-netbook-armel+omap4.img.gz image Aug 13 09:28:13 on my PandaBoard ES 1.0. Aug 13 09:28:24 I get the below error message after the reboot: Aug 13 09:28:25 http://cdimage.ubuntu.com/ubuntu-netbook/ports/daily-preinstalled/20100812/maverick-preinstalled-netbook-armel+omap4.img.gz Aug 13 09:28:48 Oops, here's the error: http://pastebin.com/iKWD7Umg Aug 13 09:35:01 lag: morning man Aug 13 09:35:41 cooloney: Hey Bryan Aug 13 09:36:00 cooloney: How are you getting on with your packaging work? Aug 13 09:36:48 lag: yeah, just rebased to our 2.6.35 master tree Aug 13 09:37:04 and sent out an email to discuss the maintanenc method Aug 13 09:37:31 lag: how about your review? Aug 13 09:38:01 i think ndec is still working on the integration tree, since there L24.9 branch is increasing Aug 13 09:39:39 ogra: I wonder what's responsible for the "Exec format error" message. Aug 13 09:43:33 cooloney: Yes, I saw your email Aug 13 09:44:33 cooloney: I was chatting with apw and tgardner yesterday about the maintenance issues Aug 13 09:44:55 cooloney: It's quite a complex one Aug 13 09:45:50 cooloney: It would be easier if TI's tree was based solely on Linus' 2.6.35 tree Aug 13 09:46:40 lag: right, i also asked that question in the email to ndec Aug 13 09:47:25 lag: but that's TI's internal process. i hope we can get such ti patch stack on Linux 2.6.35 release Aug 13 09:47:46 lag: currently, it is not easy for them to change. Aug 13 10:09:54 cooloney: How did you do the last one? Aug 13 10:12:28 lag: sorry, what's the last one? Aug 13 10:12:41 The last release Aug 13 10:13:33 oh, the last release is simpler, since we just rebased TI's 230+ patches on top of our tip tree. Aug 13 10:18:19 So what makes this any different? Aug 13 10:21:37 lag: actually no big difference to me, just 1300+ patches vs 230+ patches. Aug 13 10:21:57 and it is 2.5.35 based release Aug 13 10:22:19 we cannot simple rebase on our -ti-omap4 branch, but need to rebase on our master Aug 13 10:22:31 since our master is also 2.6.35 based Aug 13 10:22:46 When I do a git merge onto master, I only receive one (easily correctable) issue Aug 13 10:22:56 yeah, that's it. Aug 13 10:22:59 i got 2, Aug 13 10:23:03 today. Aug 13 10:23:14 but 2 of them are omap3 related Aug 13 10:23:39 so it won't be much difficult. Aug 13 10:24:47 apw's method is not necessary this time Aug 13 10:27:28 You have to revert ce8bd5fb89ad58d345a5eaef52e7fa6f5683f5a9 Aug 13 10:27:35 Then you only get one Aug 13 10:28:35 cooloney: -^ Aug 13 10:29:34 lag: thx, man, you fixed 50% rebasing issues Aug 13 10:30:06 lag: and as ndec said in his latest email, we still need to wait for their integration release Aug 13 10:30:25 that's our upstream, L24.9 is just their monthly release tree. Aug 13 10:35:38 Well, why don't we wait then? Aug 13 10:35:56 I'm guessing sebjan will ensure their tree _fits_ on ours Aug 13 10:36:19 cooloney: The other conflict should be easy too Aug 13 10:36:39 cooloney: The one in HEAD looks far more correct than the other Aug 13 10:37:04 Just delete Aug 13 10:37:06 ======= Aug 13 10:37:06 dss_clk_enable(); Aug 13 10:37:06 r = dsi_pll_init(dssdev, 0, 1); Aug 13 10:37:06 >>>>>>> L24.9 Aug 13 10:37:19 and obviously <<<<<<< HEAD Aug 13 10:37:59 The result of the successful merge can be found here: http://kernel.ubuntu.com/git?p=lag/ubuntu-maverick.git;a=shortlog;h=refs/heads/ti-omap4-35 Aug 13 10:38:18 Now I just need your packaging work to test Aug 13 10:50:19 lag: how did you do that? git merge? Aug 13 10:50:35 cooloney: Yeah Aug 13 10:50:50 lag: i found you missed some patches from L24.9 branch Aug 13 10:50:58 Oh? Aug 13 10:51:09 When were they released? Aug 13 10:51:24 Give me the commit ids Aug 13 10:51:54 lag http://dev.omapzoom.org/?p=integration/kernel-omap4.git;a=shortlog;h=refs/heads/L24.9 Aug 13 10:52:09 they updated their tree yesterday, i think Aug 13 10:52:24 the release for us is supposed to be next week. Aug 13 10:52:33 ndec and sebjan will work on it. Aug 13 10:52:48 please find my rebase result here Aug 13 10:53:03 http://kernel.ubuntu.com/git?p=roc/ubuntu-maverick.git;a=shortlog;h=refs/heads/ti-release-rebasing-testing Aug 13 10:53:25 cooloney: I didn't miss anything - they weren't in the tree then Aug 13 10:53:40 I thought it was for Friday? Aug 13 10:54:04 cooloney: It's pointless merging now, they are going to be updating it daily Aug 13 10:54:15 We should wait until our proper release date Aug 13 10:54:27 lag: right, we have to wait Aug 13 10:54:47 ndec: Are you there? Aug 13 10:54:47 so i just test rebasing is simple for this release Aug 13 10:54:56 lag: hi!@ Aug 13 10:54:56 cooloney: Me too Aug 13 10:55:05 ndec: Hello :) Aug 13 10:55:35 We've been discussing how best to handle your tree Aug 13 10:56:00 lag: oh i see... i saw the emails but was not watching irc... Aug 13 10:56:08 When it our release date? Aug 13 10:56:11 is* Aug 13 10:56:34 lag: cooloney: the current l24.9 branch is quite broken, especially on panda, we are trying to fix this. Aug 13 10:57:01 ndec: Do you have people working on the checkpatch errors too? Aug 13 10:57:18 lag: unfortunately, I will be on vacation next ;-)... but sebjan will come back mid of next week. Aug 13 10:57:48 lag: for checkpatch, this is a bit more complicated... Aug 13 10:58:49 lag: our dev process implies that our dev teams are moving to .36, so very likely they will not addess them in a .35 release. Aug 13 10:59:11 ndec: after a quick review of the checkpatch result file, i think just several patches cause most of errors Aug 13 10:59:22 lag: i will need to see what we can do with sebjan for the most critical one Aug 13 10:59:34 ndec: if we pointed them out, they can help to fix that in .36 Aug 13 11:00:09 cooloney: well .36 won't help since we will stay in .35. but since you have the list already, you can send that to me and sebjan and we can address them Aug 13 11:00:50 ndec: yeah, i know that. but i don't think we can fix those 2800++ coding style errors in this release. Aug 13 11:01:00 ndec: Would it be possible to insure your developers run checkpatch before applying their work in future Aug 13 11:01:02 just wanna let them know this. Aug 13 11:01:22 cooloney: lag: we are working on this... Aug 13 11:01:23 mopdenacker, i wish too i would know that, we're hunting this bug since monday Aug 13 11:01:31 cooloney: lag: they know. Aug 13 11:01:35 ndec: If you every want to upstream your code, it will have to become a common operating procedure Aug 13 11:02:02 mopdenacker, if you want a working install, use the alpha3 milestone image Aug 13 11:02:08 ogra_cmpc: thanks. That's good to know that I'm not the only one... Aug 13 11:02:29 ndec: actually, i think for TI git server we can add some git post-commit script which will call checkpatch.pl to check every commit Aug 13 11:02:31 ogra_cmpc: OK, I will do that. Thanks! Aug 13 11:02:31 lag: it's part of the procedure. the main problem is time pressure and h/w problems that we need to work with Aug 13 11:02:45 ndec: Don't we all :) Aug 13 11:03:12 ndec: technically it will drop those commit having coding issues Aug 13 11:03:23 cooloney: we know all of this... Aug 13 11:03:35 ndec: :D Aug 13 11:03:40 lag: yes we do. then it's a matter of prioritization ;-) Aug 13 11:03:53 ndec: right, i understood Aug 13 11:03:58 ndec: Indeed Aug 13 11:04:10 ndec: When is your release date? Aug 13 11:04:18 lag: at the end of the day we make h/w... and this is much less soft than software ;-) Aug 13 11:04:30 ndec: i agree the first thing we need is working stable 2.6.35 based release for both panda and blaze Aug 13 11:04:52 lag: on 17th we should get an updated BSP Aug 13 11:05:22 So we'll pull your tree then? Aug 13 11:06:11 cooloney: they have been some updates this night in L24.9 branch. I still haven't had a chance to build, but they are supposed to have fix the panda boot problem. Aug 13 11:06:22 rcn-ee: ping (when you're up) Aug 13 11:06:54 ndec: cooloney: We should wait until the release date Aug 13 11:06:59 ndec: got it, awesome. need any help, please let use know Aug 13 11:07:04 ndec: cooloney: It's pointless merging until it's finished Aug 13 11:07:10 lag: for this specific release where our dev team release is on .35, yes, you can pull from L24.9 branch. then we will create a stable branch on http://dev.omapzoom.org/?p=integration/kernel-ubuntu.git;a=summary for the updates Aug 13 11:07:12 lag: yeah, Aug 13 11:07:42 ndec: And when's that due? Aug 13 11:07:53 ndec: indeed. that's way we worked for several monthes Aug 13 11:07:59 cooloney: When will your packaging be finished? Aug 13 11:08:05 lag: agreed. it's pointless untill I or sebjan tells you that it's booting on panda and blaze, let us do the dirty stuff first ;-) Aug 13 11:08:18 lag: i have to wait for that release Aug 13 11:08:25 lag: final L24.9 branch from dev team due on 17th Aug 13 11:08:29 ndec: I have every intention :) Aug 13 11:08:32 * ogra_cmpc hands ndec some gloves Aug 13 11:08:46 ndec: Noted Aug 13 11:09:02 lag: need to sync config files with the latest release. Aug 13 11:09:08 ogra_cmpc: for this specific item I will be on vacation ;-), so I am passing the gloves to sebjan Aug 13 11:09:10 ogra_cmpc: Why? Do you have something stuck up there which you'd like removing? Aug 13 11:09:18 ndec, haha Aug 13 11:09:39 lag, no, for not getting his hands so dirty Aug 13 11:09:52 ogra_cmpc: ;) Aug 13 11:10:02 heh Aug 13 11:10:31 lag, i'm well able to remove stuck things myself :P Aug 13 11:13:14 ogra_cmpc: Comes with practise I suppose :) Aug 13 11:13:27 ogra_cmpc: Where should the jasper.log file be? Aug 13 11:17:33 lag, after the install run in /var/log, during initramfs in /dev/.initramfs/ Aug 13 11:18:14 (jasper copies it over as the last step before the reboot) Aug 13 11:18:56 It's not in /var/log Aug 13 11:19:20 then check /dev/.initramfs/ Aug 13 11:19:29 (if it still exists) Aug 13 11:20:35 ogra_cmpc: http://paste.ubuntu.com/477403/ Aug 13 11:20:39 Does that look okay to you? Aug 13 11:21:44 ogra_cmpc: My Panda comes to a crashing halt when the purple screen appears Aug 13 11:22:10 The cursor and the background is visible but nothing else Aug 13 11:22:22 hit enter after waiting a few mins Aug 13 11:22:32 And my USB mouse and keyboard no longer work Aug 13 11:22:35 i suppose you are using a newer image than A3 ? Aug 13 11:22:51 I am using the latest daily build Aug 13 11:22:54 oem-config dies for no apparent reason since monday Aug 13 11:23:10 Okay Aug 13 11:23:24 What's the link to the most stable version? Aug 13 11:23:35 take A3 Aug 13 11:24:07 http://cdimage.ubuntu.com/ubuntu-netbook/ports/releases/maverick/ Aug 13 11:24:16 I have it Aug 13 11:33:40 lag pong. ;) Aug 13 11:33:56 Good morning Robert Aug 13 11:34:07 Hi Lee, how's it going. Aug 13 11:34:09 Are you well? Aug 13 11:34:13 Very good thanks Aug 13 11:34:40 Have you heard anything regarding your ro patch? Aug 13 11:35:52 i'm good, it's friday.. ;) I need to quickly verify on my C2/C4 before i post version 3... (it'll be this afternoon as i get off at noon) Aug 13 11:36:07 Are you going to shift all the code to board-omap3beagle.c on v3? Aug 13 11:36:13 yeap i did.. Aug 13 11:36:20 Good stuff Aug 13 11:36:28 Hopefully they're leave you alone on this one Aug 13 11:36:49 What happens once it's been approved on linux-omap? Aug 13 11:36:58 Do you have to submit it upstream? Aug 13 11:37:05 nah i'm not woried. ;) they are here for reference.. http://bazaar.launchpad.net/~beagleboard-kernel/%2Bjunk/2.6.35-devel/files/head:/patches/gpio/ Aug 13 11:38:27 after linux-omap, tony will probally push them for 2.6.37... (in for-next) (the 2.6.36 merge can't last for maybe another day or two..) Aug 13 11:40:03 ndec, can you include asac in the invite for the friday call ? Aug 13 11:41:54 rcn-ee: Is Tony the linux-omap maintainer? Aug 13 11:42:37 lag: he is Aug 13 11:42:54 lag: want to meet him? Aug 13 11:43:01 Sure, why not! Aug 13 11:43:17 lag: come to Helsinki on Tuesday, I'm having lunch with him Aug 13 11:43:17 amitk: Not that I have anything to say :) Aug 13 11:43:28 amitk: I'll just nip over :) Aug 13 11:43:29 Yeap Tony is the linux-omap maintainer.. Aug 13 11:44:32 rcn-ee: how are your stocks of XMs? :) Aug 13 11:45:19 rumor up the grape vine... possibly next week.. but i'll probally say that again next week.. ;) Aug 13 11:46:20 rcn-ee: You can have mine when amitk sends me the new version :) Aug 13 11:47:10 i'll trade you my 256 xMA P7 for your 512. ;) Aug 13 11:47:34 even thou the 512's have memory problems, they stay up longer then my 256. ;) Aug 13 11:48:04 rcn-ee: I'll think about it Aug 13 11:48:08 rcn-ee: nah Aug 13 12:04:50 lag, you are not seeing Bug 605488 because we dont use swap currently, create a swapfile and add it to fstab, then see if you get the errors Aug 13 12:04:51 Launchpad bug 605488 in linux-ti-omap4 (Ubuntu Maverick) (and 1 other project) "BUG: scheduling while atomic: mmcqd/46/0x00000002 (affects: 1) (heat: 132)" [High,In progress] https://launchpad.net/bugs/605488 Aug 13 12:54:11 rcn-ee: Not having much luck there are we? :) Aug 13 13:07:40 rcn-ee but nice you're working on this issue, things will be much easier to merge when we get your patches at least linux-omap upstream :-) Aug 13 13:08:59 rcn-ee: some other questions I have, related with xM Aug 13 13:09:03 lag, getting closer. ;) one little tweak at a time.. ;) Aug 13 13:09:09 maybe lag and ogra can tell more about it Aug 13 13:09:21 I wanted to understand the known issues we got with the hardware Aug 13 13:09:29 I have a p8 board Aug 13 13:10:16 lag: what rev is your xm? Aug 13 13:10:18 that has the bad 512Mb Micron, some work, some don't... Production boards are using Neomonix.. well until Micron figures out why they corrupt randomly. Aug 13 13:10:29 i have a P7, it's 256Mb Micron.. Aug 13 13:10:46 rcn-ee: oh, got it, thanks for the info Aug 13 13:10:47 * ogra has micron too, but rev. A Aug 13 13:10:50 it has other issues, like crashing into a ball of fire when your run "sudo aptitude update" Aug 13 13:10:56 my former one was P7 as well Aug 13 13:11:13 but with 512M Aug 13 13:11:21 random issues doesn't seems good hehe Aug 13 13:11:50 i think the rev. A ones are supposed to be more stable but i might be wrong Aug 13 13:11:51 that's weird.. according to my cheat sheet from gerald, the P8 was the first 512, but considering those are marked with a marker. ;) Aug 13 13:12:13 hmm, i might misremember and it might have been an 8 Aug 13 13:12:28 * lag has a Micron Aug 13 13:12:40 lag: but what rev? Aug 13 13:12:55 i think all out are micron right now.. the actuall production ones will be Nuemoinx.. Aug 13 13:13:37 let see "A" changed gpio related to mSecure, USB host1 (to a header), USB reset and Sysboot changes.. Aug 13 13:15:13 rcn-ee: cool, you have the logs :-) Aug 13 13:16:07 yeah the early one... hasn't been updated since May thou.. the current log is on the schematic of the "A2" on beagleboard.org (it doesn't have the old Px changes) Aug 13 13:16:29 * rcn-ee runs work back in a couple hours. Aug 13 13:19:21 I think the USB is broken on my Panda :( Aug 13 13:21:41 lag: why? Aug 13 13:24:31 It doesn't work Aug 13 13:25:02 usb 1-1: new high speed USB device using musb_hdrc and address 3 Aug 13 13:25:02 usb 1-1: device descriptor read/64, error -110 Aug 13 13:25:02 usb 1-1: device descriptor read/64, error -110 Aug 13 13:25:02 usb 1-1: new high speed USB device using musb_hdrc and address 4 Aug 13 13:25:02 usb 1-1: device not accepting address 4, error -110 Aug 13 13:25:02 usb 1-1: new high speed USB device using musb_hdrc and address 5 Aug 13 13:25:04 usb 1-1: device not accepting address 5, error -110 Aug 13 13:25:06 hub 1-0:1.0: unable to enumerate USB device on port 1 Aug 13 13:28:06 lag: es1.0 board:? Aug 13 13:28:56 How do I tell? Aug 13 13:29:03 black or not ? Aug 13 13:29:05 lag: is the pcb green or black? Aug 13 13:29:11 the only issue I saw regarding the usb is the dma problem Aug 13 13:29:11 es2.0 are painted black Aug 13 13:29:31 musb_hdrc.use_dma=0 could help, but not sure if you're getting the same issue Aug 13 13:29:37 lag, given that you didnt tell us about a new board you got this week i'd say es2 Aug 13 13:29:40 err Aug 13 13:29:42 es1 Aug 13 13:29:50 lag: es2 has the pandaboard logo Aug 13 13:30:11 because of some hardware issues related to the the TWL6030 configuration on ES1.0 boards, not all the time when the board boots with something plugged into the MUSB does it enumerate properly Aug 13 13:30:22 and apart from tobin the es2.0's should all still be in delivery Aug 13 13:30:27 try rebooting with the MUSB unplugged and plug it in after booting Aug 13 13:31:56 * ogra wonders how much the pandas differ within the es1.0 line Aug 13 13:32:10 i havent seen any issues regarding musb on my es1 Aug 13 13:32:32 ogra: it varies Aug 13 13:32:46 yeah, i was guessing so, like the XM Aug 13 13:33:13 Green Aug 13 13:33:28 now that was a prompt answer :P Aug 13 13:33:53 ogra: shh Aug 13 13:34:01 ogra: I'm doing more than one thing at once Aug 13 13:34:08 really ? Aug 13 13:34:12 you can ? Aug 13 13:34:15 lol Aug 13 13:34:19 lag: you mutli-task? Aug 13 13:34:19 I think you misunderstand me - it used to work Aug 13 13:34:32 * ogra always secretly suspected female genes in lag Aug 13 13:34:44 lag: new kernel ? Aug 13 13:34:58 there was a new meta today so likely a new kernel too Aug 13 13:35:02 prpplague: Yeah Aug 13 13:35:26 prpplague: I'll test the kernel separately - wait one Aug 13 13:35:32 lag: np, Aug 13 13:35:48 hmm, the kernel is from the 5th though, i wonder why meta wasnt updated alongside Aug 13 13:35:54 I tested the newer kernel already, seems to be working fine Aug 13 13:36:08 lag: try a simple test, just boot the boot without anything plugged into the MUSB and then plug it in after booting Aug 13 13:36:10 ogra: cooloney forgot about it Aug 13 13:36:18 when he updated the main debs Aug 13 13:36:26 rsalveti, ah Aug 13 13:36:46 would have been nice to have it in the alpha release though :P Aug 13 13:37:02 ah well Aug 13 13:37:08 cant have everything Aug 13 13:37:53 * ogra glares at the maverick-changes ML Aug 13 13:38:06 coinor-flopc++ ... Aug 13 13:38:20 looks like someone just hit random keys to make up a package name Aug 13 13:39:20 * prpplague tries to decide what to do about panda audio Aug 13 13:39:46 prpplague, emmet (persia) will take care of it (at least he said so yesterday) Aug 13 13:39:58 ogra: ?? Aug 13 13:40:09 ogra: you mean about the audio? Aug 13 13:40:14 though i dont see him online today, seems he still has issues with his new appartment and internet Aug 13 13:40:20 prpplague, yep Aug 13 13:40:35 ogra: ahh, right, this is more for internal TI L24.x release Aug 13 13:40:51 the ASoC module needs to expose the right stuff to make pulse aware of the different devices i think Aug 13 13:40:55 it doesnt do that atm Aug 13 13:40:59 ogra: i'm trying to decide if panda should share the sdp4430 audio file, or split it off for it's own Aug 13 13:41:08 ah Aug 13 13:41:15 ogra: yea that is being done in the L24.9 release Aug 13 13:41:33 main target needs to be to not need an asound.conf Aug 13 13:42:11 hmm Aug 13 13:42:51 ogra: the thing is that the panda doesn't have a number of the channels that the sdp has Aug 13 13:43:03 ogra: none of the mic Aug 13 13:43:05 well, then the driver needs fixing Aug 13 13:43:51 asound.conf is a hack to override broken driver defaults, if the driver doesnt expose the right HW to userspace that needs fixing in the driver Aug 13 13:44:01 ogra: right, so the question is, do we share the sdp4430.c file and add a bunch of "machine_is_omap4_panda()" or do i create a seperate file Aug 13 13:44:29 heh, your choice i guess, whats working better for upstreamability later ? Aug 13 13:44:49 yea that's what i'm trying to think through now Aug 13 13:45:58 prpplague, you could probably ask lrg as ASoC upstream buy ;) Aug 13 13:46:03 s/buy/guy/ Aug 13 13:46:22 ogra: yea already have a ping out for him this morning Aug 13 13:46:29 ah Aug 13 13:46:31 ogra: he's burried with the L24.9 release as well Aug 13 13:46:38 heh Aug 13 13:46:42 all of TI is it seems Aug 13 13:47:35 * ogra is only sitting with a bucket on his knees waiting to catch the stuff that comes downstream :) Aug 13 13:47:42 hehe Aug 13 13:48:37 what a nice metaphor Aug 13 13:48:57 It could have been worse Aug 13 13:49:06 hehe Aug 13 13:52:37 lool, you mean it could be a cup ? Aug 13 13:54:09 it could be in another place than on your knees Aug 13 14:48:23 ogra: I've tried the alpha3 installer and it works fine so far... Aug 13 14:48:43 great Aug 13 14:49:55 ogra: The only bad thing is that the first boot phase is completely silent for a few minutes (while it extends the partition). I had to add "console=ttyO2,115200n8" to the bootargs to actually see something. Aug 13 14:50:50 This could confuse users, thinking that their system is frozen. And they could reset their board and corrupt their rootfs which is currently being resized. Aug 13 14:51:00 well, the image is designed in a way that you dont need to use serial Aug 13 14:51:40 you should attach a HDMI monitor Aug 13 14:51:48 ogra, I understand... Aug 13 14:52:01 how big is your SD ? Aug 13 14:52:10 8 GB Aug 13 14:52:23 the resizing shouldnt take more than a few mins (1-2) nowadays Aug 13 14:52:51 ogra, you're right. It took approximately 2 minutes. Aug 13 14:52:52 lag> It doesn't work Aug 13 14:52:52 usb 1-1: new high speed USB device using musb_hdrc and address 3 Aug 13 14:52:52 usb 1-1: device descriptor read/64, error -110 Aug 13 14:52:52 usb 1-1: device descriptor read/64, error -110 Aug 13 14:52:52 usb 1-1: new high speed USB device using musb_hdrc and address 4 Aug 13 14:52:53 usb 1-1: device not accepting address 4, error -110 Aug 13 14:52:55 usb 1-1: new high speed USB device using musb_hdrc and address 5 Aug 13 14:52:57 usb 1-1: device not accepting address 5, error -110 Aug 13 14:52:58 we fixed that right before the alpha release (i didnt remove the thxt that tells you "10min per 4G yet) Aug 13 14:52:59 hub 1-0:1.0: unable to enumerate USB device on port 1 Aug 13 14:53:13 *text Aug 13 14:53:23 I did attach an hdmi display, but nothing got displayed during the first boot phase (before the reboot to the installer) Aug 13 14:54:31 intresting, but it did work on second boot ? Aug 13 14:54:45 ogra: Yes, it did. Aug 13 14:54:51 hmm, weird Aug 13 14:55:16 robclark, ^^^ any idea why the first boot wouldnt work on HDMI but the second does ? Aug 13 14:55:30 (we dont change any graphics related boot options or anything) Aug 13 14:56:00 ogra: hmm.. is the first boot over too quickly before the monitor can sync? Aug 13 14:56:16 and is there any way you could get a bootlog w/ omapdss.debug=1? Aug 13 14:56:33 no, it takes a few mins Aug 13 14:56:45 Someone's USB broken also? Aug 13 14:56:48 hmm.. and same kernel? Aug 13 14:57:08 and it does an auto-reboot so capturing the dmesg is a bit of an effort Aug 13 14:57:29 oh, ok.. Aug 13 14:57:33 its the alpha3 release, works on my monitor for first and all subsequent boots Aug 13 14:58:18 well, I can't think of any particular reason why it would not work on first boot, but would work on subsequent boots.. but I guess I don't know enough about what changes between first boot and second boot.. Aug 13 14:58:25 same MLO/u-boot/uImage? Aug 13 14:58:39 yes, all the same Aug 13 14:58:49 any difference which could change timing and expose a potential race condition? Aug 13 14:59:05 first boot is console only, second is using plymouth Aug 13 14:59:15 and i think GrueMaster saw some similar issues in the past Aug 13 14:59:34 ndec: ping Aug 13 14:59:35 hmm.. but framebuffer should come up before you even get to userspace.. Aug 13 14:59:53 yeah Aug 13 15:01:40 jayabharath: ping Aug 13 15:03:43 lag: hi Aug 13 15:04:22 lag: did you try to plug in usb kybd after boot up.. Aug 13 15:04:48 lag: there was a problem that sometimes usb peripharl was not detected when you have it plugged in on cold boot Aug 13 15:06:36 jayabharath: I have Aug 13 15:07:18 lag: can you send you me your kernel image, i'll test here Aug 13 15:07:34 lag: and info on what kernel source you are using Aug 13 15:07:35 prpplague: Email address? Aug 13 15:07:44 lag: x0132446@ti.com Aug 13 15:09:11 prpplague: I remeber there was a TWL OTG VBUS issue.. was this a HW fix or kernel change Aug 13 15:09:25 jayabharath: kernel fix Aug 13 15:16:33 jayabharath: prpplague: I'm going to rebuild our latest kernel Aug 13 15:16:49 prpplague: When I've done so, I'll send you the .deb Aug 13 15:29:31 ogra: thanks for targeting the bugs for beta Aug 13 15:29:38 easier to track now Aug 13 15:30:05 rsalveti, well, i have to else i'll get grilled in the release meeting :) Aug 13 15:30:20 oh, true :-) Aug 13 15:40:02 ogra: I got disconnected from the Internet, sorry. I may have missed replies from you. Aug 13 15:41:23 mopdenacker, i didnt reply any further to you, i just know that someone in here (i think GrueMaster) had a similar prob before Aug 13 15:42:12 Sorry, what was the issue? Aug 13 15:42:21 ogra: All right... we can continue to investigate. Thanks! Aug 13 15:42:43 GrueMaster, black screen on first boot on the panda but working monitor after the first reboot Aug 13 15:42:46 GrueMaster: having no graphical output with the preinstalled images.... Aug 13 15:42:50 (after resizing) Aug 13 15:43:26 I was seeing that too yesterday, even with my additional parameters I have had to set. Not even seeing serial console output. Aug 13 15:43:33 Though in both cases, I had to add hdmi driver bootargs to get the display to work. Aug 13 15:44:20 Right, console serial output wouldn't hurt, even if a serial console is not a requirement. Aug 13 15:44:30 My panda first boot cmdline: Aug 13 15:44:30 setenv bootargs vram=32M mem=463M root=/dev/mmcblk0p2 fixrtc console=ttyO2,115200 console=tty0 omapdss.debug=1 omapdss.hdmimode=0 omapdss.hdmicode=35 Aug 13 15:44:34 it breaks the splash screen Aug 13 15:44:59 ogra: Ah, right. Aug 13 15:46:07 GrueMaster: Got the same bootargs as you do (without console=tty0, which is a good idea btw, and without omapdss.debug) Aug 13 15:47:01 ogra: Are you supposed to detect the monitor type, and then load the display drivers from the initramfs with the corresponding settings? Aug 13 16:05:50 mopdenacker, the kernel is supposed to detect the EDID from the monitor and set the right stuff Aug 13 16:06:14 (inside the driver) Aug 13 16:06:29 and its kind of a myth why it does that right on second boot but not on first Aug 13 16:06:58 ogra: I understand, thanks. Aug 13 16:08:00 I can investigate this within TI, reproduce it in a simple testcase and file a bug report. Thanks again! Aug 13 16:08:40 mopdenacker, robclark has worked out patches that we dont have on the images yet Aug 13 16:08:52 *could* be related Aug 13 16:09:02 though its still a myth why it works on second boot Aug 13 16:09:49 ogra: I will try with our own images too. Thanks! Aug 13 16:11:18 mopdenacker: what problem are you seeing? Aug 13 16:13:28 prpplague: no graphical output on the first boot phase (with pre-installed images), and then a correct display after rebooting. Same kernel, same bootargs (except a root= setting with UUID). Aug 13 16:14:01 mopdenacker: which platform? panda? Aug 13 16:14:19 prpplague, panda with the ubuntu image Aug 13 16:14:28