T-SeriesのトピックRe: kernel Bug at qman\bman _config.c

kernel Bug at qman\bman _config.c

mohsenhaghighat — Wed, 12 Jul 2017 06:57:37 GMT

We design a T1022 custom board. In this design we load U-boot on NOR-Flash and now we try to boot a OS on it.
We make a kernel (UIMAGE dtb and rootfs) with SDK, we use its default config in Menuconfig. Then we boot these files on my board and see this error:
" kernel BUG at /home/me/SDK/QorIQ-SDK-V2.0-20160527-yocto/build_t1042d4rdb/tmp/work-shared/t1042d4rdb/kernel-source/drivers/staging/fsl_qbman/qman_config.c
Oops: Exception in kernel mode, sig: 5 [#1]"

I attach the console logs.

I understand that this error happend because of qman and bman, So in menuconifg I deselect it. I do not use USB on my board so I deselect the USB Support. Then I load the file on my board and OS boot seccesfully. I attach my.config file and linux dmesg logs.

bootm 1000000 3000000 1fc0000

What can i do for qman bman error?
thanks,

Original Attachment has been moved to: config.zip

Original Attachment has been moved to: logs_qman_error.txt.zip

Re: kernel Bug at qman\bman _config.c

yipingwang — Wed, 19 Jul 2017 10:11:18 GMT

Hello mohsen haghighat,

It seems that you didn't configure BMAN in your Kernel configuration, please refer to the attached Kernel configuration.

You could run the following commands in Kernel source folder to generate .config automatically.

$ cp arch/powerpc/configs/corenet32_fmanv3l_smp_defconfig .config

$ make ARCH=powerpc menuconfig

Then save the configuration as .config file.

Have a great day,
TIC

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

Re: kernel Bug at qman\bman _config.c

mohsenhaghighat — Wed, 19 Jul 2017 11:08:39 GMT

Dear yiping thanks for answer, i can not find a attach kernel configuration.

I copy the corenet32_fmanv3l_smp_defconfig file to .config but it make error.

  Using /home/me/SDK/QorIQ-SDK-V2.0-20160527-yocto/build_t1042d4rdb/tmp/work-shared/t1042d4rdb/kernel-source as source for kernel |  |   Using /home/me/SDK/QorIQ-SDK-V2.0-20160527-yocto/build_t1042d4rdb/tmp/work-shared/t1042d4rdb/kernel-source as source for kernel |   /home/me/SDK/QorIQ-SDK-V2.0-20160527-yocto/build_t1042d4rdb/tmp/work-shared/t1042d4rdb/kernel-source is not clean, please run 'make mrproper' |  |   /home/me/SDK/QorIQ-SDK-V2.0-20160527-yocto/build_t1042d4rdb/tmp/work-shared/t1042d4rdb/kernel-source is not clean, please run 'make mrproper' |   in the '/home/me/SDK/QorIQ-SDK-V2.0-20160527-yocto/build_t1042d4rdb/tmp/work-shared/t1042d4rdb/kernel-source' directory. |  |   in the '/home/me/SDK/QorIQ-SDK-V2.0-20160527-yocto/build_t1042d4rdb/tmp/work-shared/t1042d4rdb/kernel-source' directory. | /home/me/SDK/QorIQ-SDK-V2.0-20160527-yocto/build_t1042d4rdb/tmp/work-shared/t1042d4rdb/kernel-source/Makefile:972: recipe for target 'prepare3' failed | make[2]: *** [prepare3] Error 1 |  | /home/me/SDK/QorIQ-SDK-V2.0-20160527-yocto/build_t1042d4rdb/tmp/work-shared/t1042d4rdb/kernel-source/Makefile:972: recipe for target 'prepare3' failed | make[2]: *** [prepare3] Error 1 | ERROR: oe_runmake failed | ERROR: Function failed: do_compile (log file is located at /home/me/SDK/QorIQ-SDK-V2.0-20160527-yocto/build_t1042d4rdb/tmp/work/t1042d4rdb-fsl-linux/linux-qoriq/4.1-r0/temp/log.do_compile.65107)

Re: kernel Bug at qman\bman _config.c

yipingwang — Thu, 20 Jul 2017 07:22:30 GMT

Hello mohsen haghighat,

If you use Linux SDK 2.0 Yocto build environment, please go to the build folder QorIQ-SDK-V2.0-20160527-yocto/build_t1042d4rdb/tmp/work/t1042d4rdb-fsl-linux/linux-qoriq/4.1-r0/build,

$ cp source/arch/powerpc/configs/corenet32_fmanv3l_smp_defconfig .config

$ make ARCH=powerpc menuconfig

You also could use the following commands to rebuild Linux Kernel.

1.$ bitbake virtual/kernel -c cleansstate

2. $ bitbake virtual/kernel -c configure

3. Go to the folder

build_t1042d4rdb/tmp/work/t1042d4rdb-fsl-linux/linux-qoriq/4.1-r0/build

$ make ARCH=powerpc menuconfig

4. After reconfigure Kernel according to your requirement.

$ bitbake virtual/kernel -c compile -f

$bitbake virtual/kernel

5. Got to step 3 to modify Kernel configuration and rebuild again.

Have a great day,
TIC

Re: kernel Bug at qman\bman _config.c

mohsenhaghighat — Sun, 23 Jul 2017 04:16:59 GMT

Dear Yiping, thanks for your reply

I resolved the problem by setting

fqd_a

(qman_fqd in dts) address in file Path_To_SDK/QorIQ-SDK-V2.0-20160527-yocto/build_t1042d4rdb/tmp/work-shared/t1042d4rdb/kernel-source/drivers/staging/fsl_qbman/qman_config.c to 0xff6000000 according to QorIQ-SDK2.0 document page 267:

and now qbman and ethernet drivers are initialized and fm1-gb0..4 interfaces can be seen by ifconfig -a (I attached boot and ifconfig log). however I have some problems when I set IP or ping and I asked my problem in another question, thank you for your help :smileyhappy:.

My questions now:

1) is that address the correct one? and should I also set bman_fbpr ,qman_pfdr ,pme_pdsr and pme_sre addresses to some locations in above address map or their must be the default value in dts?

2) I changed address of qman_fqd by setting it in the parser function in qman_config.c driver file, How can I change it through reserved-memory in dts? I change alloc-ranges property to some other value e.g.:

alloc-ranges = <0 0 0x2200000 0x55D4A80>;

but the address does not change.

reserved-memory {
#address-cells = <2>;
#size-cells = <2>;
ranges;
bman_fbpr: bman-fbpr {
compatible = "fsl,bman-fbpr";
alloc-ranges = <0 0 0x10000 0>;
size = <0 0x1000000>;
alignment = <0 0x1000000>;
};
qman_fqd: qman-fqd {
compatible = "fsl,qman-fqd";
alloc-ranges = <0 0 0x10000 0>;
size = <0 0x800000>;
alignment = <0 0x800000>;
};
qman_pfdr: qman-pfdr {
compatible = "fsl,qman-pfdr";
alloc-ranges = <0 0 0x10000 0>;
size = <0 0x2000000>;
alignment = <0 0x2000000>;
};
pme_pdsr: pme-pdsr {
compatible = "fsl,pme-pdsr";
alloc-ranges = <0 0 0x10000 0>;
size = <0 0x1000000>;
alignment = <0 0x1000000>;
};
pme_sre: pme-sre {
compatible = "fsl,pme-sre";
alloc-ranges = <0 0 0x10000 0>;
size = <0 0xa00000>;
alignment = <0 0xa00000>;
};
};

Please accept my apology for text prolongation :smileyhappy:.