cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
210 Views
Registered: ‎12-13-2019

Migrating from 2018.1 to 2019.1 pl353 nand driver crashing

I am migrating from xilinx branch 2018.1 to 2019.1

Nand driver is crashing 

WARNING: CPU: 1 PID: 1 at drivers/mtd/nand/raw/nand_base.c:2773 nand_subop_get_data_len+0x80/0x8c
Modules linked in:
Hardware name: Xilinx Zynq Platform
[<c010e1d0>] (unwind_backtrace) from [<c010b0d4>] (show_stack+0x10/0x14)
[<c010b0d4>] (show_stack) from [<c047217c>] (dump_stack+0x7c/0x9c)
[<c047217c>] (dump_stack) from [<c0119d20>] (__warn+0xd0/0xec)
[<c0119d20>] (__warn) from [<c0119d74>] (warn_slowpath_null+0x38/0x44)
[<c0119d74>] (warn_slowpath_null) from [<c033872c>] (nand_subop_get_data_len+0x80/0x8c)
[<c033872c>] (nand_subop_get_data_len) from [<c033f510>] (pl353_nand_exec_op_cmd+0x12c/0x2f4)
[<c033f510>] (pl353_nand_exec_op_cmd) from [<c0334ce4>] (nand_op_parser_exec_op+0x364/0x40c)
[<c0334ce4>] (nand_op_parser_exec_op) from [<c0335ee8>] (nand_reset_op+0x100/0x150)
[<c0335ee8>] (nand_reset_op) from [<c03389d8>] (nand_reset+0x50/0xa8)
[<c03389d8>] (nand_reset) from [<c0339020>] (nand_scan_with_ids+0x2e8/0x1ab4)
[<c0339020>] (nand_scan_with_ids) from [<c033ead8>] (pl353_nand_probe+0x168/0x1f8)
[<c033ead8>] (pl353_nand_probe) from [<c030fcb0>] (platform_drv_probe+0x38/0x6c)
[<c030fcb0>] (platform_drv_probe) from [<c030e168>] (really_probe+0x284/0x3b4)
[<c030e168>] (really_probe) from [<c030c574>] (bus_for_each_drv+0xa0/0xb4)
[<c030c574>] (bus_for_each_drv) from [<c030e330>] (__device_attach+0x98/0x114)
[<c030e330>] (__device_attach) from [<c030d284>] (bus_probe_device+0x28/0x80)
[<c030d284>] (bus_probe_device) from [<c030b390>] (device_add+0x480/0x594)
[<c030b390>] (device_add) from [<c03a914c>] (of_platform_device_create_pdata+0x98/0xbc)
[<c03a914c>] (of_platform_device_create_pdata) from [<c03ae64c>] (pl353_smc_probe+0x174/0x214)
[<c03ae64c>] (pl353_smc_probe) from [<c02d5898>] (amba_probe+0x50/0x68)
[<c02d5898>] (amba_probe) from [<c030e168>] (really_probe+0x284/0x3b4)
[<c030e168>] (really_probe) from [<c030e620>] (__driver_attach+0xb0/0x124)
[<c030e620>] (__driver_attach) from [<c030c484>] (bus_for_each_dev+0x64/0xa0)
[<c030c484>] (bus_for_each_dev) from [<c030d5a8>] (bus_add_driver+0x1b4/0x22c)
[<c030d5a8>] (bus_add_driver) from [<c030ed74>] (driver_register+0xac/0xf0)
[<c030ed74>] (driver_register) from [<c01025e8>] (do_one_initcall+0x70/0x170)
[<c01025e8>] (do_one_initcall) from [<c0700dfc>] (kernel_init_freeable+0x18c/0x1d0)
[<c0700dfc>] (kernel_init_freeable) from [<c0483e48>] (kernel_init+0x8/0x10c)
[<c0483e48>] (kernel_init) from [<c01010d8>] (ret_from_fork+0x14/0x3c)
Exception stack(0xdf441fb0 to 0xdf441ff8)
1fa0: 00000000 00000000 00000000 00000000
1fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
1fe0: 00000000 00000000 00000000 00000000 00000013 00000000
---[ end trace 5377d337ee813d8f ]---

 

This exception keeps on coming

Please help

0 Kudos
2 Replies
Moderator
Moderator
188 Views
Registered: ‎09-12-2007

Re: Migrating from 2018.1 to 2019.1 pl353 nand driver crashing

When you migrated, did you create every thing for scratch again?

0 Kudos
Highlighted
178 Views
Registered: ‎12-13-2019

Re: Migrating from 2018.1 to 2019.1 pl353 nand driver crashing

Before Migration we were on the branch https://github.com/Xilinx/linux-xlnx/tree/xilinx-v2018.1 , 

A week before we start migrating. Everything was from scratch.

1: Upgraded to latest yocto version thud(20.0.3)

2: Migrated the meta-xilinx layer to comapatiable thud release (https://github.com/Xilinx/meta-xilinx/tree/rel-v2019.1 )

3: Start to migrate with the Linux kernel with compatiable meta-xilinx layer to branch ( https://github.com/Xilinx/linux-xlnx/tree/xilinx-v2019.1 )

0 Kudos