Hello, linaro-dev,
I am using the instructions in the "adjust kernel config" section at this link:
https://wiki.linaro.org/KenWerner/Sandbox/CreateCustomKernelDeb
When I run
# fakeroot debian/rules editconfigs
I get the the following errors:
Running config-check for all configurations ...
check-config: /tmp/tmp.Sv8FblIPLa/CONFIGS/armel-config.flavour.linaro-lt-omap: loading config check-config: /home/work/linux-linaro-lt-omap-3.4-3.4.0/debian.linaro/config/enforce: loading checks check-config: FAIL: value CONFIG_INIT_PASS_ALL_PARAMS y check-config: 43/44 checks passed -- exit 1 check-config: /tmp/tmp.Sv8FblIPLa/CONFIGS/armhf-config.flavour.linaro-lt-omap: loading config check-config: /home/work/linux-linaro-lt-omap-3.4-3.4.0/debian.linaro/config/enforce: loading checks check-config: FAIL: value CONFIG_INIT_PASS_ALL_PARAMS y check-config: 43/44 checks passed -- exit 1
*** ERROR: 2 config-check failures detected
I am using config-3.4.0-1-linaro-lt-omap as my initial .config. A search for INIT_PASS_ALL_PARAMS in the Kconfig files produces no results:
find . -name Kconfig -exec grep -H INIT_PASS_ALL_PARAMS '{}' ';'
When I extract the source to a temporary directory and search the "kernel_build" subdirectory (that John Rigby told me to delete), I find it in
./init/Kconfig:config INIT_PASS_ALL_PARAMS
So, now I am really confused. Is the real source in the "kernel_build" subdirectory?
David,
I thnk we need to start at the beginning. Where did you get the source you are working with. In your original post I assumed that this was source extracted with dpkg-source from a linaro kernel source pkg.
--john
On Tue, Jul 10, 2012 at 10:19 AM, David Cullen David.Cullen@koe-americas.com wrote:
Hello, linaro-dev,
I am using the instructions in the "adjust kernel config" section at this link:
https://wiki.linaro.org/KenWerner/Sandbox/CreateCustomKernelDeb
When I run
# fakeroot debian/rules editconfigsI get the the following errors:
Running config-check for all configurations ...
check-config: /tmp/tmp.Sv8FblIPLa/CONFIGS/armel-config.flavour.linaro-lt-omap: loading config check-config: /home/work/linux-linaro-lt-omap-3.4-3.4.0/debian.linaro/config/enforce: loading checks check-config: FAIL: value CONFIG_INIT_PASS_ALL_PARAMS y check-config: 43/44 checks passed -- exit 1 check-config: /tmp/tmp.Sv8FblIPLa/CONFIGS/armhf-config.flavour.linaro-lt-omap: loading config check-config: /home/work/linux-linaro-lt-omap-3.4-3.4.0/debian.linaro/config/enforce: loading checks check-config: FAIL: value CONFIG_INIT_PASS_ALL_PARAMS y check-config: 43/44 checks passed -- exit 1
*** ERROR: 2 config-check failures detected
I am using config-3.4.0-1-linaro-lt-omap as my initial .config. A search for INIT_PASS_ALL_PARAMS in the Kconfig files produces no results:
find . -name Kconfig -exec grep -H INIT_PASS_ALL_PARAMS '{}' ';'When I extract the source to a temporary directory and search the "kernel_build" subdirectory (that John Rigby told me to delete), I find it in
./init/Kconfig:config INIT_PASS_ALL_PARAMSSo, now I am really confused. Is the real source in the "kernel_build" subdirectory?
-- Thank you, David Cullen
Hello, John,
On 7/10/2012 12:52 PM, John Rigby wrote:
I thnk we need to start at the beginning. Where did you get the source you are working with. In your original post I assumed that this was source extracted with dpkg-source from a linaro kernel source pkg.
I used
apt-get source linux-image-3.4.0-1-linaro-lt-omap
Then I extracted the tarball. The tarball comes from the Linaro repository:
Get:1 http://ppa.launchpad.net/linaro-maintainers/kernel/ubuntu/ precise/main linux-linaro-lt-omap-3.4 3.4.0-1.1~120627131801 (tar) [204 MB]
So Linaro appears to have a defect in the kernel source package in their repository. This goes along with a defect I found in the linux-headers package for the same kernel.
On Tue, Jul 10, 2012 at 10:19 AM, David Cullen David.Cullen@koe-americas.com wrote:
Hello, linaro-dev,
I am using the instructions in the "adjust kernel config" section at this link:
https://wiki.linaro.org/KenWerner/Sandbox/CreateCustomKernelDeb
When I run
# fakeroot debian/rules editconfigsI get the the following errors:
Running config-check for all configurations ...
check-config: /tmp/tmp.Sv8FblIPLa/CONFIGS/armel-config.flavour.linaro-lt-omap: loading config check-config: /home/work/linux-linaro-lt-omap-3.4-3.4.0/debian.linaro/config/enforce: loading checks check-config: FAIL: value CONFIG_INIT_PASS_ALL_PARAMS y check-config: 43/44 checks passed -- exit 1 check-config: /tmp/tmp.Sv8FblIPLa/CONFIGS/armhf-config.flavour.linaro-lt-omap: loading config check-config: /home/work/linux-linaro-lt-omap-3.4-3.4.0/debian.linaro/config/enforce: loading checks check-config: FAIL: value CONFIG_INIT_PASS_ALL_PARAMS y check-config: 43/44 checks passed -- exit 1
*** ERROR: 2 config-check failures detected
I am using config-3.4.0-1-linaro-lt-omap as my initial .config. A search for INIT_PASS_ALL_PARAMS in the Kconfig files produces no results:
find . -name Kconfig -exec grep -H INIT_PASS_ALL_PARAMS '{}' ';'When I extract the source to a temporary directory and search the "kernel_build" subdirectory (that John Rigby told me to delete), I find it in
./init/Kconfig:config INIT_PASS_ALL_PARAMSSo, now I am really confused. Is the real source in the "kernel_build" subdirectory?
-- Thank you, David Cullen
There will shortly be a new kernel linux-linaro-lt-omap-3.4_3.4.0-1.1~120710203036 in the kernel ppa: https://code.launchpad.net/~linaro-maintainers/+archive/kernel with the kernel_build issue fixed.
Now we can get back to the original issue.
--john
On Tue, Jul 10, 2012 at 11:47 AM, David Cullen David.Cullen@koe-americas.com wrote:
Hello, John,
On 7/10/2012 12:52 PM, John Rigby wrote:
I thnk we need to start at the beginning. Where did you get the source you are working with. In your original post I assumed that this was source extracted with dpkg-source from a linaro kernel source pkg.
I used
apt-get source linux-image-3.4.0-1-linaro-lt-omapThen I extracted the tarball. The tarball comes from the Linaro repository:
Get:1 http://ppa.launchpad.net/linaro-maintainers/kernel/ubuntu/ precise/main linux-linaro-lt-omap-3.4 3.4.0-1.1~120627131801 (tar) [204 MB]
So Linaro appears to have a defect in the kernel source package in their repository. This goes along with a defect I found in the linux-headers package for the same kernel.
On Tue, Jul 10, 2012 at 10:19 AM, David Cullen David.Cullen@koe-americas.com wrote:
Hello, linaro-dev,
I am using the instructions in the "adjust kernel config" section at this link:
https://wiki.linaro.org/KenWerner/Sandbox/CreateCustomKernelDeb
When I run
# fakeroot debian/rules editconfigsI get the the following errors:
Running config-check for all configurations ...
check-config: /tmp/tmp.Sv8FblIPLa/CONFIGS/armel-config.flavour.linaro-lt-omap: loading config check-config: /home/work/linux-linaro-lt-omap-3.4-3.4.0/debian.linaro/config/enforce: loading checks check-config: FAIL: value CONFIG_INIT_PASS_ALL_PARAMS y check-config: 43/44 checks passed -- exit 1 check-config: /tmp/tmp.Sv8FblIPLa/CONFIGS/armhf-config.flavour.linaro-lt-omap: loading config check-config: /home/work/linux-linaro-lt-omap-3.4-3.4.0/debian.linaro/config/enforce: loading checks check-config: FAIL: value CONFIG_INIT_PASS_ALL_PARAMS y check-config: 43/44 checks passed -- exit 1
*** ERROR: 2 config-check failures detected
I am using config-3.4.0-1-linaro-lt-omap as my initial .config. A search for INIT_PASS_ALL_PARAMS in the Kconfig files produces no results:
find . -name Kconfig -exec grep -H INIT_PASS_ALL_PARAMS '{}' ';'When I extract the source to a temporary directory and search the "kernel_build" subdirectory (that John Rigby told me to delete), I find it in
./init/Kconfig:config INIT_PASS_ALL_PARAMSSo, now I am really confused. Is the real source in the "kernel_build" subdirectory?
-- Thank you, David Cullen
-- Thank you, David Cullen
Hello, John,
On 7/10/2012 5:39 PM, John Rigby wrote:
There will shortly be a new kernel linux-linaro-lt-omap-3.4_3.4.0-1.1~120710203036 in the kernel ppa: https://code.launchpad.net/~linaro-maintainers/+archive/kernel with the kernel_build issue fixed.
Now we can get back to the original issue.
That did fix the "kernel_build" problem, but I still see this
Running config-check for all configurations ...
check-config: /tmp/tmp.nh0bAR6k1r/CONFIGS/armel-config.flavour.linaro-lt-omap: loading config check-config: /home/work/linux-linaro-lt-omap-3.4-3.4.0/debian.linaro/config/enforce: loading checks check-config: FAIL: value CONFIG_INIT_PASS_ALL_PARAMS y check-config: 43/44 checks passed -- exit 1 check-config: /tmp/tmp.nh0bAR6k1r/CONFIGS/armhf-config.flavour.linaro-lt-omap: loading config check-config: /home/work/linux-linaro-lt-omap-3.4-3.4.0/debian.linaro/config/enforce: loading checks check-config: FAIL: value CONFIG_INIT_PASS_ALL_PARAMS y check-config: 43/44 checks passed -- exit 1
*** ERROR: 2 config-check failures detected
when I run
# fakeroot debian/rules editconfigs
A search for the configuration item produces no results:
find . -name Kconfig -exec grep -H INIT_PASS_ALL_PARAMS '{}' ';'
On Wed, Jul 11, 2012 at 10:35 AM, David Cullen David.Cullen@koe-americas.com wrote:
Hello, John,
On 7/10/2012 5:39 PM, John Rigby wrote:
There will shortly be a new kernel linux-linaro-lt-omap-3.4_3.4.0-1.1~120710203036 in the kernel ppa: https://code.launchpad.net/~linaro-maintainers/+archive/kernel with the kernel_build issue fixed.
Now we can get back to the original issue.
That did fix the "kernel_build" problem, but I still see this
Running config-check for all configurations ...
check-config: /tmp/tmp.nh0bAR6k1r/CONFIGS/armel-config.flavour.linaro-lt-omap: loading config check-config: /home/work/linux-linaro-lt-omap-3.4-3.4.0/debian.linaro/config/enforce: loading checks check-config: FAIL: value CONFIG_INIT_PASS_ALL_PARAMS y check-config: 43/44 checks passed -- exit 1 check-config: /tmp/tmp.nh0bAR6k1r/CONFIGS/armhf-config.flavour.linaro-lt-omap: loading config check-config: /home/work/linux-linaro-lt-omap-3.4-3.4.0/debian.linaro/config/enforce: loading checks check-config: FAIL: value CONFIG_INIT_PASS_ALL_PARAMS y check-config: 43/44 checks passed -- exit 1
*** ERROR: 2 config-check failures detected
when I run
# fakeroot debian/rules editconfigsA search for the configuration item produces no results:
find . -name Kconfig -exec grep -H INIT_PASS_ALL_PARAMS '{}' ';'
Yes this is expected because that config option is introduced by a ubuntu patch that is not in this tree. I changed some of the scripts to make this error non-fatal but the output gives no indication of that. I will change that so it is clear that this is a warning or I will make a change to the config checker to only require the option if it exists.
thanks john
Hello, John,
On 7/11/2012 2:05 PM, John Rigby wrote:
On Wed, Jul 11, 2012 at 10:35 AM, David Cullen wrote:
Running config-check for all configurations ...
check-config: /tmp/tmp.nh0bAR6k1r/CONFIGS/armel-config.flavour.linaro-lt-omap: loading config check-config: /home/work/linux-linaro-lt-omap-3.4-3.4.0/debian.linaro/config/enforce: loading checks check-config: FAIL: value CONFIG_INIT_PASS_ALL_PARAMS y check-config: 43/44 checks passed -- exit 1 check-config: /tmp/tmp.nh0bAR6k1r/CONFIGS/armhf-config.flavour.linaro-lt-omap: loading config check-config: /home/work/linux-linaro-lt-omap-3.4-3.4.0/debian.linaro/config/enforce: loading checks check-config: FAIL: value CONFIG_INIT_PASS_ALL_PARAMS y check-config: 43/44 checks passed -- exit 1
*** ERROR: 2 config-check failures detected
Yes this is expected because that config option is introduced by a ubuntu patch that is not in this tree. I changed some of the scripts to make this error non-fatal but the output gives no indication of that. I will change that so it is clear that this is a warning or I will make a change to the config checker to only require the option if it exists.
My concern here is that this configuration item was introduced in 2010 to fix a problem with starting a getty on OMAP processors:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/586386
Since I am using the Ubuntu image to work around problems with the Linaro-Ubuntu image, I am concerned that this will break my console getty.
Can you offer any reassurance, e.g. by pointing out how more modern kernels solve the problem differently?
-
David Cullen -
John Rigby