"device-tree" test failed on vexpress A9 ubuntu.

Bug #1058013 reported by Botao
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Linaro Linux Baseline
Fix Released
Low
Tixy (Jon Medhurst)
Linaro UEFI
Fix Released
Low
Ryan Harkin
Linaro Ubuntu
Fix Released
Low
Unassigned

Bug Description

On vexpress A9 board with Linaro ubuntu pre-built image:

http://snapshots.linaro.org/precise/pre-built/vexpress/316/vexpress-precise_ubuntu-desktop_20120923-316.img.gz

"device-tree" test failed. Please refer to this link to get details:

http://validation.linaro.org/lava-server/dashboard/streams/private/team/linaro/pre-built-vexpress/bundles/8bf98ee7d20c5525101203c7975cf95127c959d9/200a294c-0725-11e2-8dd2-0002f7003cc2/

has_proc_device_tree: FAIL - Unable to find /proc/device-tree
device_tree_model_not_empty: FAIL - Unable to find /proc/device-tree/model

Revision history for this message
Fathi Boudra (fboudra) wrote :

in linaro/configs/ubuntu.conf: CONFIG_PROC_DEVICETREE=y

The support for device tree in /proc doesn't seems to work on Vexpress.

Ryan/Tixy, opinion?

Changed in linaro-ubuntu:
status: New → Triaged
importance: Undecided → Low
Revision history for this message
Tixy (Jon Medhurst) (tixy) wrote :

It this test worth bothering with? Only the A9 CoreTile is capable of booting without device-tree and that ability is probably going away in the Linux 3.9.

As to why the test fails, that is because the vexpress kernels are built with the ubuntu-minimal.conf config fragment, not ubuntu.conf. I.e. with the 25 config options needed to boot Ubuntu, not the 2130 'kitchen sink' config options that upstream Ubuntu ships with to support every X86 PC, server and peripheral on the planet. ;-)

And there doesn't seem much point in adding CONFIG_PROC_DEVICETREE to ubuntu-minimal.conf if it's sole purpose is to check that you've configured your bootloader to boot with device-tree.

Revision history for this message
Fathi Boudra (fboudra) wrote : Re: [Bug 1058013] Re: "device-tree" test failed on vexpress A9 ubuntu.

On 7 December 2012 12:45, Tixy (Jon Medhurst)
<email address hidden> wrote:
> It this test worth bothering with? Only the A9 CoreTile is capable of
> booting without device-tree and that ability is probably going away in
> the Linux 3.9.
>
> As to why the test fails, that is because the vexpress kernels are built
> with the ubuntu-minimal.conf config fragment, not ubuntu.conf. I.e. with
> the 25 config options needed to boot Ubuntu, not the 2130 'kitchen sink'
> config options that upstream Ubuntu ships with to support every X86 PC,
> server and peripheral on the planet. ;-)
>
> And there doesn't seem much point in adding CONFIG_PROC_DEVICETREE to
> ubuntu-minimal.conf if it's sole purpose is to check that you've
> configured your bootloader to boot with device-tree.

device-tree test is part of the basic requirements tests. I'll prefer
to have a single test to cover all the boards than treat vexpress as
an exception. +1 for CONFIG_PROC_DEVICETREE in ubuntu-minimal.conf.

Revision history for this message
Tixy (Jon Medhurst) (tixy) wrote :

On Fri, 2012-12-07 at 11:27 +0000, Fathi Boudra wrote:
> device-tree test is part of the basic requirements tests. I'll prefer
> to have a single test to cover all the boards than treat vexpress as
> an exception. +1 for CONFIG_PROC_DEVICETREE in ubuntu-minimal.conf.

Android has similar test case and it would probably be part of any
platform's testing, so I think the proper place is to put the config is
in linaro-base.conf...

http://lists.linaro.org/pipermail/linaro-dev/2012-December/014708.html

Revision history for this message
Fathi Boudra (fboudra) wrote :

On 7 December 2012 15:50, Tixy (Jon Medhurst)
<email address hidden> wrote:
> On Fri, 2012-12-07 at 11:27 +0000, Fathi Boudra wrote:
>> device-tree test is part of the basic requirements tests. I'll prefer
>> to have a single test to cover all the boards than treat vexpress as
>> an exception. +1 for CONFIG_PROC_DEVICETREE in ubuntu-minimal.conf.
>
> Android has similar test case and it would probably be part of any
> platform's testing, so I think the proper place is to put the config is
> in linaro-base.conf...
>
> http://lists.linaro.org/pipermail/linaro-dev/2012-December/014708.html

Make sense. Thanks Tixy!

no longer affects: linaro-landing-team-arm
Changed in linaro-linux-baseline:
importance: Undecided → Low
milestone: none → 12.12
Changed in linaro-ubuntu:
milestone: none → 12.12
Changed in linaro-linux-baseline:
assignee: nobody → Tixy (Jon Medhurst) (tixy)
status: New → In Progress
Changed in linaro-ubuntu:
assignee: nobody → Fathi Boudra (fboudra)
Revision history for this message
Fathi Boudra (fboudra) wrote :
Changed in linaro-linux-baseline:
status: In Progress → Fix Committed
Revision history for this message
Fathi Boudra (fboudra) wrote :

latest test result: http://validation.linaro.org/lava-server/dashboard/attachment/209460/view

has_proc_device_tree: PASS
device_tree_model_not_empty: FAIL - Unable to find /proc/device-tree/model

@Tixy, is it expected to have the device tree model empty?

Revision history for this message
Tixy (Jon Medhurst) (tixy) wrote : Re: [Bug 1058013] Re: "device-tree" test failed on vexpress A9 ubuntu.

On Sat, 2012-12-15 at 10:43 +0000, Fathi Boudra wrote:
> latest test result: http://validation.linaro.org/lava-
> server/dashboard/attachment/209460/view
>
> has_proc_device_tree: PASS
> device_tree_model_not_empty: FAIL - Unable to find /proc/device-tree/model
>
> @Tixy, is it expected to have the device tree model empty?

Probably not, but if this is from an automated testing in Lava then I
believe that doesn't boot with device-tree as UEFI still has bugs with
device-tree on A9.

On Android (what I have handy) then cat /proc/device-tree/model
gives V2P-CA9 on A9 and V2P-CA15_CA7 on TC2.

Revision history for this message
Ryan Harkin (ryanharkin) wrote :

I can confirm that there is still an outstanding bug in UEFI the prevents us from booting with device tree:

https://bugs.launchpad.net/linaro-landing-team-arm/+bug/1067784

Fathi Boudra (fboudra)
Changed in linaro-ubuntu:
milestone: 12.12 → 13.01
Changed in linaro-linux-baseline:
status: Fix Committed → Fix Released
Changed in linaro-uefi:
status: New → Confirmed
Changed in linaro-ubuntu:
status: Triaged → Confirmed
assignee: Fathi Boudra (fboudra) → nobody
Fathi Boudra (fboudra)
Changed in linaro-ubuntu:
milestone: 13.01 → 13.02
Changed in linaro-uefi:
milestone: none → 13.02
Fathi Boudra (fboudra)
Changed in linaro-uefi:
milestone: 13.02 → 13.03
Changed in linaro-ubuntu:
milestone: 13.02 → 13.03
Fathi Boudra (fboudra)
Changed in linaro-uefi:
milestone: 13.03 → 13.04
Changed in linaro-ubuntu:
milestone: 13.03 → 13.04
Ryan Harkin (ryanharkin)
Changed in linaro-uefi:
assignee: nobody → Ryan Harkin (ryanharkin)
Ryan Harkin (ryanharkin)
Changed in linaro-uefi:
status: Confirmed → Fix Released
Changed in linaro-ubuntu:
status: Confirmed → Fix Released
Changed in linaro-uefi:
importance: Undecided → Low
Ryan Harkin (ryanharkin)
Changed in linaro-landing-team-arm:
milestone: none → 2013.04
assignee: nobody → Ryan Harkin (ryanharkin)
importance: Undecided → Low
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.