Bug 3986 - [Test Case 312] User could use yocto-kernel to set kernel config
Summary: [Test Case 312] User could use yocto-kernel to set kernel config
Status: VERIFIED WORKSFORME
Alias: None
Product: Meta-yocto
Classification: Build System, Metadata & Runtime
Component: meta-yocto (show other bugs)
Version: 1.3
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.3.2
Assignee: Tom Zanussi
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2013-03-05 15:44 UTC by Stoicescu Cornel
Modified: 2013-03-12 16:20 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stoicescu Cornel 2013-03-05 15:44:40 UTC
STATUS: FAILED
BUILD: danny:98292d1ef1cb44cf96f0a28fbca6439eda55ce1b
ENVIRONMENT: user-preference (any supported environment)
STEPS TO REPRODUCE: 1. Follow the case "yocto-kernel add patch" apply a patch to your kernel
2. Follow the instruments in https://wiki.yoctoproject.org/wiki/Transcript:_Using_the_Yocto_BSP_tools_to_manage_kernel_patches_and_config_items, to enable some kernel options for your kernel.
3. For example, run "yocto-kernel config add myqemuarm 
CONFIG_MISC_DEVICES=y" and "yocto-kernel config add myqemuarm 
CONFIG_YOCTO_TESTMOD=y" will make CONFIG_MISC_DEVICES and 
CONFIG_YOCTO_TESTMOD set for kernel
4. Rebuild the kernel and boot from the kernel, check if there is a line with 'Kilroy was here! __m_(OuO)_m__' in command dmesg

EXPECTED OUTCOME: User could use yocto-kernel to set kernel config .
Comment 1 Stoicescu Cornel 2013-03-05 15:45:53 UTC
ACTUAL OUTCOME:' dmesg | grep "was here" ' gives no output
Comment 2 Tom Zanussi 2013-03-07 14:17:50 UTC
Is this the same problem as seen here?:

https://bugzilla.yoctoproject.org/show_bug.cgi?id=2589

and here?:

https://bugzilla.yoctoproject.org/show_bug.cgi?id=3524
Comment 3 Darren Hart 2013-03-07 15:39:03 UTC
.
Comment 4 Stoicescu Cornel 2013-03-07 15:52:18 UTC
There is no fail during the build.

When the image bots up, after issuing the command `dmesg | grep "was here"`, there is no output.
Comment 5 Stoicescu Cornel 2013-03-07 15:54:24 UTC
I used https://wiki.yoctoproject.org/wiki/images/c/c9/Yocto-testmod.patch to patch the kernel, not copy-paste from the wiki page.
Comment 6 Tom Zanussi 2013-03-07 21:11:12 UTC
I'm not seeing any problem here.  Did you perhaps forget to apply the patch?  (I don't see that step in the STEPS to reproduce below).

I did the below using myqemuarm BSP and saw the module output in the dmesg.

[trz@empanada build]$ yocto-kernel patch add myqemuarm /home/trz/bsp-tools-tests/test/d\
anny/yocto-testmod.patch
Added patches:
      yocto-testmod.patch
[trz@empanada build]$ yocto-kernel config add myqemuarm CONFIG_MISC_DEVICES=y
Added items:
      CONFIG_MISC_DEVICES=y
[trz@empanada build]$ yocto-kernel config add myqemuarm CONFIG_YOCTO_TESTMOD=y
Added items:
      CONFIG_YOCTO_TESTMOD=y
[trz@empanada build]$ yocto-kernel config list myqemuarm
The current set of machine-specific kernel config items for myqemuarm is:
    1) CONFIG_MISC_DEVICES=y
    2) CONFIG_YOCTO_TESTMOD=y

[trz@empanada build]$ yocto-kernel patch list myqemuarm
The current set of machine-specific patches for myqemuarm is:
    1) yocto-testmod.patch
[trz@empanada build]$ bitbake core-image-sato
Comment 7 Stoicescu Cornel 2013-03-12 16:20:33 UTC
Even though the patch was applied before, it did not work.

I tried again with a newer danny commit and it works.

Verified on danny:955827af15f611189c66850fd077de344e1285c3