There are some differences in Robert's setup...he's using a .37
kernel(from kernel.org?) and a A1 board, while Laurent has an EA1. I
don't think the board revision has something to do, but the kernel may.
--
You received this bug notification because you are a member of TI OMAP
Developers, which
Hi Laurent,
Yeah, i didn't have any '-j' parameters in those builds (also had 'nice'
enabled)...
I just updated my script to use "-j2" and disabled "nice" so we shall
see what it does..
No, I'm not using NFS, (i really should), I'm using a locally mounted
usb sata drive (160G/7200rpm), also cont
Hi Robert,
Interesting. From the logs it looks like you're not using "-j 2", am I
right? I managed to get the freeze without -j and C only bootstrap but
it took a few iterations. Also are you using NFS for the build?
I've relaunched a build without NFS.
Ricardo, any news on this?
Sincerely,
--
Hey Laurent,
Finally setup my panda to do the same thing, so far i haven't been seeing this
issue.. (I'm not using the mem=768M boot arg)
(MMC contains uImage/uInitrd rootfs on external usb sata drive)
My own kernel: (http://rcn-ee.net/deb/squeeze/v2.6.37-x0/)
voo...@panda-a1-1gb:~$ cat /proc/
This config file is based on Ubuntu Natty TI OMAP4 config file
** Attachment added: "mainline_config"
https://bugs.launchpad.net/ubuntu/+source/linux-ti-omap4/+bug/633227/+attachment/1791242/+files/mainline_config
--
You received this bug notification because you are a member of TI OMAP
Deve
I tried build 2.6.37 mainline kernel which was just released with the
Ubuntu Natty ti-omap4 kernel config. 2.6.37 kernel boots fine with our
Ubuntu Natty minimal root file system. But I can still reproduce this
issue.
I will post this issue to upstream mail list for more attention.
==
[0.
6 matches
Mail list logo
