The Linux Foundation servers were compromised this weekend, and as a result http://yoctoproject.org is unavailable. Apologies for any inconvenience. We hope to be back up as soon as possible. -- Jeff

Bruce, Even though I haven't test utrace, I just tested my newly built sato-sdk with the same tree for arm and didn't run into kernel panic. So seems not related to utrace and more specific to

As would I! I just audited the kernel changes, and there's nothing that should cause anything so severe. My build and boot of course worked as well. The grand total of changes since the 3.0.4 update

Don't know whether these data will help but seems the issue hit several people, Lianhao reported the same failure with his local build as well. I first noticed the failure happened with my local

To be clear, I updated master to 98c2da694ca4c72b3e222a593b8baddea102bde5 and rebuilt my image (yesterday). This image now crashes as reported. What can I look at to help? --

I've just tested qemux86 and qemuarm images and both of these were fine (apart from pango issues which I locally reverted the change in question for). I'm a little puzzled why things are therefore

Actually, I forgot that qemux86 also uses i586 packages, so there were quite a few other packages changed since Aug 31. You can see the lists at http://www.mlbassoc.com/poky/qemux86-rpms --

Verified - fails for me here as well. A Bruce said, a build from just a few days ago did work. Note: I only tried core-image-sato As far as I can tell, the only packages that were rebuilt since my

Since I've been at Linux plumbers since Wednesday, I can confirm that nothing has changed in the kernel itself. And I just booted an older userspace with a brand new kernel a few minutes ago. That

Hi, Has anybody ran into kernel panic when boot up core-image-sato-sdk for qemux86. I’ve been having this issue with several clean build for two days. And my latest build tree is a freshly

This suffers a similar problem: git am ../meta-intel-contrib/0001-Remove-10-100-LAN-support.-10-100-LAN-will-be-config.patch Patch format detection failed. If it's easier for you, just git

* Opens collection - 5 min (Song) * Yocto 1.1 M4 status review and issues - 10 min (team) https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.1_Release_Criteria#Milestone_ - Status summary for bug

Hi Bruce, I have pushed the pacthes to meta-intel-contrib, link given below: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel-contrib/tree/?h=10-100-patch Let me know if this

This is a concern, iirc we needed GRUB 2 for x86_64. I was considering dropping grub entirely and using syslinux in the 1.2 timeframe. I asked on list if there were any non-x86 grub users and didn't

Hi Nitin, Having a config fragment for btrfs available in linux-yocto is appropriate and makes btrfs easily added to any BSP from recipe space or from the linux-yocto meta repository. However, we do

The license version specified in the recipe is wrong - it should be v3 rather than 2+. Signed-off-by: Tom Zanussi <tom.zanussi@...> --- common/recipes-bsp/grub/grub_1.98.bb | 2 +- 1 files

And I just pushed a fix to update the recipe as well... Tom

Yeah, thanks for pointing that out. Will keep the legacy version around in any case... Thanks, Tom

We need to keep the older grub 0.97 as well. grub2 is GPLv3 and a lot of people will refuse to use it based on that. --Mark

I haven't tried the 32-bit BSPs with grub2 - been focused on other things until this incomplete fix for 1428 seems to have forced the issue, but can try it over the weekend and see what