| 2014-03-27 03:39:09 |
Botao |
bug |
|
|
added bug |
| 2014-03-27 03:39:09 |
Botao |
attachment added |
|
file_structure_in_proc.txt https://bugs.launchpad.net/bugs/1298176/+attachment/4045906/+files/file_structure_in_proc.txt |
|
| 2014-03-28 05:20:36 |
vishal |
linaro-android: importance |
Undecided |
Medium |
|
| 2014-03-28 05:20:43 |
vishal |
linaro-android: assignee |
|
HariGopal (harigopal-gollamudi) |
|
| 2014-04-14 12:07:57 |
Soumya Basak |
description |
On Samsung Arndale board with Linaro Android image:
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.03-release/#build=1
"device-tree" directory doesn't exist under the path "/proc", please refer to attachment to get all directories list:
root@arndale:/ # find /proc -name device-tree
root@arndale:/ #
By comparison, this directory exists with all device tree related files inside on ARM Versatile Express A9 Android.
However, from boot log, the blob had been loaded to Kernel:
reading board.dtb
21192 bytes read
## Flattened Device Tree blob at 41f00000
Booting using the fdt blob at 0x41f00000
Loading Kernel Image ... OK
OK
Using Device Tree in place at 41f00000, end 41f082c7
Starting kernel ...
#################################
This issue is observed on following images:
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=386
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.03-release/#build=1 |
On Samsung Arndale board with Linaro Android image:
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.03-release/#build=1
"device-tree" directory doesn't exist under the path "/proc", please refer to attachment to get all directories list:
root@arndale:/ # find /proc -name device-tree
root@arndale:/ #
By comparison, this directory exists with all device tree related files inside on ARM Versatile Express A9 Android.
However, from boot log, the blob had been loaded to Kernel:
reading board.dtb
21192 bytes read
## Flattened Device Tree blob at 41f00000
Booting using the fdt blob at 0x41f00000
Loading Kernel Image ... OK
OK
Using Device Tree in place at 41f00000, end 41f082c7
Starting kernel ...
#################################
This issue is observed on following images:
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=386
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.03-release/#build=1
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=415 |
|
| 2014-04-22 17:44:22 |
Soumya Basak |
description |
On Samsung Arndale board with Linaro Android image:
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.03-release/#build=1
"device-tree" directory doesn't exist under the path "/proc", please refer to attachment to get all directories list:
root@arndale:/ # find /proc -name device-tree
root@arndale:/ #
By comparison, this directory exists with all device tree related files inside on ARM Versatile Express A9 Android.
However, from boot log, the blob had been loaded to Kernel:
reading board.dtb
21192 bytes read
## Flattened Device Tree blob at 41f00000
Booting using the fdt blob at 0x41f00000
Loading Kernel Image ... OK
OK
Using Device Tree in place at 41f00000, end 41f082c7
Starting kernel ...
#################################
This issue is observed on following images:
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=386
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.03-release/#build=1
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=415 |
On Samsung Arndale board with Linaro Android image:
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.03-release/#build=1
"device-tree" directory doesn't exist under the path "/proc", please refer to attachment to get all directories list:
root@arndale:/ # find /proc -name device-tree
root@arndale:/ #
By comparison, this directory exists with all device tree related files inside on ARM Versatile Express A9 Android.
However, from boot log, the blob had been loaded to Kernel:
reading board.dtb
21192 bytes read
## Flattened Device Tree blob at 41f00000
Booting using the fdt blob at 0x41f00000
Loading Kernel Image ... OK
OK
Using Device Tree in place at 41f00000, end 41f082c7
Starting kernel ...
#################################
This issue is observed on following images:
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=386
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.03-release/#build=1
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=415
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.04-release/#build=1 |
|
| 2014-05-22 08:26:42 |
Botao |
description |
On Samsung Arndale board with Linaro Android image:
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.03-release/#build=1
"device-tree" directory doesn't exist under the path "/proc", please refer to attachment to get all directories list:
root@arndale:/ # find /proc -name device-tree
root@arndale:/ #
By comparison, this directory exists with all device tree related files inside on ARM Versatile Express A9 Android.
However, from boot log, the blob had been loaded to Kernel:
reading board.dtb
21192 bytes read
## Flattened Device Tree blob at 41f00000
Booting using the fdt blob at 0x41f00000
Loading Kernel Image ... OK
OK
Using Device Tree in place at 41f00000, end 41f082c7
Starting kernel ...
#################################
This issue is observed on following images:
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=386
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.03-release/#build=1
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=415
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.04-release/#build=1 |
On Samsung Arndale board with Linaro Android image:
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.03-release/#build=1
"device-tree" directory doesn't exist under the path "/proc", please refer to attachment to get all directories list:
root@arndale:/ # find /proc -name device-tree
root@arndale:/ #
By comparison, this directory exists with all device tree related files inside on ARM Versatile Express A9 Android.
However, from boot log, the blob had been loaded to Kernel:
reading board.dtb
21192 bytes read
## Flattened Device Tree blob at 41f00000
Booting using the fdt blob at 0x41f00000
Loading Kernel Image ... OK
OK
Using Device Tree in place at 41f00000, end 41f082c7
Starting kernel ...
#################################
This issue is observed on following images:
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=386
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.03-release/#build=1
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=415
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.04-release/#build=1
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=447 |
|
| 2014-05-27 05:52:53 |
Botao |
description |
On Samsung Arndale board with Linaro Android image:
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.03-release/#build=1
"device-tree" directory doesn't exist under the path "/proc", please refer to attachment to get all directories list:
root@arndale:/ # find /proc -name device-tree
root@arndale:/ #
By comparison, this directory exists with all device tree related files inside on ARM Versatile Express A9 Android.
However, from boot log, the blob had been loaded to Kernel:
reading board.dtb
21192 bytes read
## Flattened Device Tree blob at 41f00000
Booting using the fdt blob at 0x41f00000
Loading Kernel Image ... OK
OK
Using Device Tree in place at 41f00000, end 41f082c7
Starting kernel ...
#################################
This issue is observed on following images:
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=386
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.03-release/#build=1
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=415
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.04-release/#build=1
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=447 |
On Samsung Arndale board with Linaro Android image:
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.03-release/#build=1
"device-tree" directory doesn't exist under the path "/proc", please refer to attachment to get all directories list:
root@arndale:/ # find /proc -name device-tree
root@arndale:/ #
By comparison, this directory exists with all device tree related files inside on ARM Versatile Express A9 Android.
However, from boot log, the blob had been loaded to Kernel:
reading board.dtb
21192 bytes read
## Flattened Device Tree blob at 41f00000
Booting using the fdt blob at 0x41f00000
Loading Kernel Image ... OK
OK
Using Device Tree in place at 41f00000, end 41f082c7
Starting kernel ...
#################################
This issue is observed on following images:
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=386
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.03-release/#build=1
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=415
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.04-release/#build=1
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=447
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.05-release/#build=1 |
|
| 2014-06-19 10:13:12 |
Botao |
description |
On Samsung Arndale board with Linaro Android image:
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.03-release/#build=1
"device-tree" directory doesn't exist under the path "/proc", please refer to attachment to get all directories list:
root@arndale:/ # find /proc -name device-tree
root@arndale:/ #
By comparison, this directory exists with all device tree related files inside on ARM Versatile Express A9 Android.
However, from boot log, the blob had been loaded to Kernel:
reading board.dtb
21192 bytes read
## Flattened Device Tree blob at 41f00000
Booting using the fdt blob at 0x41f00000
Loading Kernel Image ... OK
OK
Using Device Tree in place at 41f00000, end 41f082c7
Starting kernel ...
#################################
This issue is observed on following images:
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=386
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.03-release/#build=1
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=415
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.04-release/#build=1
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=447
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.05-release/#build=1 |
On Samsung Arndale board with Linaro Android image:
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.03-release/#build=1
"device-tree" directory doesn't exist under the path "/proc", please refer to attachment to get all directories list:
root@arndale:/ # find /proc -name device-tree
root@arndale:/ #
By comparison, this directory exists with all device tree related files inside on ARM Versatile Express A9 Android.
However, from boot log, the blob had been loaded to Kernel:
reading board.dtb
21192 bytes read
## Flattened Device Tree blob at 41f00000
Booting using the fdt blob at 0x41f00000
Loading Kernel Image ... OK
OK
Using Device Tree in place at 41f00000, end 41f082c7
Starting kernel ...
###########################################
This issue is observed on following images:
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=386
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.03-release/#build=1
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=415
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.04-release/#build=1
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=447
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.05-release/#build=1
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=473 |
|
| 2014-06-24 11:05:16 |
Botao |
description |
On Samsung Arndale board with Linaro Android image:
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.03-release/#build=1
"device-tree" directory doesn't exist under the path "/proc", please refer to attachment to get all directories list:
root@arndale:/ # find /proc -name device-tree
root@arndale:/ #
By comparison, this directory exists with all device tree related files inside on ARM Versatile Express A9 Android.
However, from boot log, the blob had been loaded to Kernel:
reading board.dtb
21192 bytes read
## Flattened Device Tree blob at 41f00000
Booting using the fdt blob at 0x41f00000
Loading Kernel Image ... OK
OK
Using Device Tree in place at 41f00000, end 41f082c7
Starting kernel ...
###########################################
This issue is observed on following images:
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=386
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.03-release/#build=1
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=415
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.04-release/#build=1
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=447
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.05-release/#build=1
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=473 |
On Samsung Arndale board with Linaro Android image:
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.03-release/#build=1
"device-tree" directory doesn't exist under the path "/proc", please refer to attachment to get all directories list:
root@arndale:/ # find /proc -name device-tree
root@arndale:/ #
By comparison, this directory exists with all device tree related files inside on ARM Versatile Express A9 Android.
However, from boot log, the blob had been loaded to Kernel:
reading board.dtb
21192 bytes read
## Flattened Device Tree blob at 41f00000
Booting using the fdt blob at 0x41f00000
Loading Kernel Image ... OK
OK
Using Device Tree in place at 41f00000, end 41f082c7
Starting kernel ...
###########################################
This issue is observed on following images:
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=386
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.03-release/#build=1
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=415
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.04-release/#build=1
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=447
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.05-release/#build=1
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=473
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.06-release/#build=1 |
|
| 2014-07-23 02:12:09 |
Botao |
description |
On Samsung Arndale board with Linaro Android image:
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.03-release/#build=1
"device-tree" directory doesn't exist under the path "/proc", please refer to attachment to get all directories list:
root@arndale:/ # find /proc -name device-tree
root@arndale:/ #
By comparison, this directory exists with all device tree related files inside on ARM Versatile Express A9 Android.
However, from boot log, the blob had been loaded to Kernel:
reading board.dtb
21192 bytes read
## Flattened Device Tree blob at 41f00000
Booting using the fdt blob at 0x41f00000
Loading Kernel Image ... OK
OK
Using Device Tree in place at 41f00000, end 41f082c7
Starting kernel ...
###########################################
This issue is observed on following images:
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=386
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.03-release/#build=1
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=415
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.04-release/#build=1
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=447
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.05-release/#build=1
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=473
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.06-release/#build=1 |
On Samsung Arndale board with Linaro Android image:
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.03-release/#build=1
"device-tree" directory doesn't exist under the path "/proc", please refer to attachment to get all directories list:
root@arndale:/ # find /proc -name device-tree
root@arndale:/ #
By comparison, this directory exists with all device tree related files inside on ARM Versatile Express A9 Android.
However, from boot log, the blob had been loaded to Kernel:
reading board.dtb
21192 bytes read
## Flattened Device Tree blob at 41f00000
Booting using the fdt blob at 0x41f00000
Loading Kernel Image ... OK
OK
Using Device Tree in place at 41f00000, end 41f082c7
Starting kernel ...
###########################################
This issue is observed on following images:
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=386
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.03-release/#build=1
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=415
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.04-release/#build=1
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=447
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.05-release/#build=1
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=473
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.06-release/#build=1
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=502 |
|
| 2014-07-30 00:06:03 |
Botao |
description |
On Samsung Arndale board with Linaro Android image:
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.03-release/#build=1
"device-tree" directory doesn't exist under the path "/proc", please refer to attachment to get all directories list:
root@arndale:/ # find /proc -name device-tree
root@arndale:/ #
By comparison, this directory exists with all device tree related files inside on ARM Versatile Express A9 Android.
However, from boot log, the blob had been loaded to Kernel:
reading board.dtb
21192 bytes read
## Flattened Device Tree blob at 41f00000
Booting using the fdt blob at 0x41f00000
Loading Kernel Image ... OK
OK
Using Device Tree in place at 41f00000, end 41f082c7
Starting kernel ...
###########################################
This issue is observed on following images:
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=386
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.03-release/#build=1
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=415
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.04-release/#build=1
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=447
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.05-release/#build=1
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=473
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.06-release/#build=1
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=502 |
On Samsung Arndale board with Linaro Android image:
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.03-release/#build=1
"device-tree" directory doesn't exist under the path "/proc", please refer to attachment to get all directories list:
root@arndale:/ # find /proc -name device-tree
root@arndale:/ #
By comparison, this directory exists with all device tree related files inside on ARM Versatile Express A9 Android.
However, from boot log, the blob had been loaded to Kernel:
reading board.dtb
21192 bytes read
## Flattened Device Tree blob at 41f00000
Booting using the fdt blob at 0x41f00000
Loading Kernel Image ... OK
OK
Using Device Tree in place at 41f00000, end 41f082c7
Starting kernel ...
###########################################
This issue is observed on following images:
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=386
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.03-release/#build=1
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=415
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.04-release/#build=1
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=447
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.05-release/#build=1
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=473
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.06-release/#build=1
https://android-build.linaro.org/builds/~linaro-android/linux-linaro-arndale/#build=502
https://android-build.linaro.org/builds/~linaro-android/arndale-linaro-14.07-release/#build=1 |
|
| 2014-08-15 12:59:33 |
Milosz Wasilewski |
linaro-android: status |
New |
Won't Fix |
|
