While bringing up a demo using crownbay, a WARNING was noted, which however didn't seem to affect system operation. The problem can be fixed with a patch from Fedora (Add patch to fix 32bit EFI service mapping (rhbz 726701)): http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-2.6.37-contrib/commit/?h=tzanussi/ioremap-fix Filing this as a low priority bug, mainly to keep track of the info until such time as we officially support bldk2. WARNING: at /usr/local/dev/yocto/crownbay-efi/build/tmp/work/crownbay-poky-linux/linux-yocto-3.2.1 1+git1+514847185c78c07f52e02750fbe0a03ca3a31d8f_1+211fc7f4d10ec2b82b424286aabbaff9254b7cbd-r1/linu x/arch/x86/mm/ioremap.c:102 __ioremap_caller+0x2d3/0x2e0() Hardware name: Crown Bay Modules linked in: Pid: 0, comm: swapper/0 Not tainted 3.2.11-yocto-standard #1 Call Trace: [<c14edc0e>] ? printk+0x1e/0x20 [<c103c603>] warn_slowpath_common+0x73/0xa0 [<c101ec03>] ? __ioremap_caller+0x2d3/0x2e0 [<c101ec03>] ? __ioremap_caller+0x2d3/0x2e0 [<c103c653>] warn_slowpath_null+0x23/0x30 [<c101ec03>] __ioremap_caller+0x2d3/0x2e0 [<c10cd1dd>] ? krealloc+0x1d/0x60 [<c10e75df>] ? kfree+0xf/0x150 [<c101ec59>] ioremap_cache+0x19/0x20 [<c1754c7d>] ? efi_enter_virtual_mode+0x14a/0x394 [<c1754c7d>] efi_enter_virtual_mode+0x14a/0x394 [<c17426c8>] start_kernel+0x294/0x309 [<c17421c1>] ? loglevel+0x2c/0x2c [<c17420aa>] i386_start_kernel+0xaa/0xb1 ---[ end trace 4eaa2a86a8e2da22 ]---
Waiting to hear back from Redhat on this.
Bruce, can you pull this in as is for now? Should be safe in yocto/base. Since Tom already has the patch in the branch, I thought I'd just send the request here :-)
I've moved this to base, and merged it to all BSPs.
This is in master (has been for a while) :-)