Hello Deepak/Andrey,
Building the omap2 defconfig kernel for armhf instead of armel seemed to fix the omap2 defconfig boot issues previously mentioned in bug 972191.
The omap2_defconfig builds boot fine on panda boards, but the kernel
built is now failing to boot on beagle boards because of Kernel panic.
The
Kernel trace can be found in the log http://validation.linaro.org/lava-server/scheduler/job/21290/log_file#entry6.
Here is the job which was https://ci.linaro.org/jenkins/job/linux-linaro-tracking_beagle-omap2plus/84/consoleFull.
Is this a known issue ?
That still doesn't quite give me enough information. Both this and theOn 11 May 2012 08:03, Andy Doan <andy.doan@linaro.org> wrote:
> +1 the LAVA team
>
>
> On 05/11/2012 06:56 AM, Deepti Kalakeri wrote:
>>
>> On Fri, May 11, 2012 at 4:19 PM, Venkatraman S <venkat@linaro.org
>> <mailto:venkat@linaro.org>> wrote:
>>
>> Checked that log. The boot log seems to be okay from the kernel. The
>> rootfs was mounted and fsck also succeeded.
>>
>> 2 interesting sections:-
>>
>> 1) mount: mounting udev on /dev failed: No such device
>> W: devtmpfs not available, falling back to tmpfs for /dev
>>
>> Do your scripts depend on udev ?
>>
>>
>> Not my scripts, but I guess the linaro-media-create used on LAVA does.
>
>
> Here's is a link to the scheduler's view of this, which is a little easier
> to read and has details like the job time out.
>
> http://validation.linaro.org/lava-server/scheduler/job/18287
other log are confusing b/c as Venkat pointed out, it appears that the
kernel booted OK and mounted the rootfs. Is there a log of what
commands are actually run on the target with their respective outputs?
~Deepak