plugout.net

by **fvdw** » Thu Sep 17, 2020 8:31 pm

I check some archives a kernel of 2044704 bytes should be no problem, we have run slightly bigger kernels.
I will try to compile a smaller one but please do the test as jocko proposed

ps after uploading the kernel you must see also a line starting kernel in cmd window, did you see that ?

ps 2 if you have time please run also test as described in next post

by **fvdw** » Thu Sep 17, 2020 8:54 pm

another test you could do is manually perform a external kernel boot
To do this use the action "u-boot console" of the fvdw-sl console
This enables you to connect to uboot of the 5big1
Follow the instruction as described in fvdw-sl console for this action.

I assume the new kernel is in tftp folder of fvdw-sl console
Switch off the nas, start fvdw-sl console and choose as action, start tftp server, after that choose as action u-boot console

Start the nas and wait until u-boot console interrupts the boot and the marvell>> prompt appears

On this prompt give these commands, do not change anything type them as given below,
PS the u-boot console window has a paste option (right click on title bar)

Code: Select all: setenv bootargs console=ttyS0,115200 netconsole=6666@${ipaddr}/,6666@${serverip}/ root=/dev/sda7

check if now bootargs parameter is set to this string

Code: Select all: printenv bootargs

if oke, proceed

Code: Select all: ide reset tftpboot 0x800000 UIMAGE-3142-5BIG1-12

You should see in the u-boot window that the kernel is uploaded and loaded in RAM
something like this (example)

Code: Select all: tftpboot 0x800000 UIMAGE-26394-NWSP2CL-59 Using egiga0 device TFTP from server 192.168.1.147; our IP address is 192.168.1.197 Filename 'UIMAGE-26394-NWSP2CL-59'. Load address: 0x800000 Loading: ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ########################## done Bytes transferred = 3123520 (2fa940 hex)

If kernel is uploaded give command

Code: Select all: bootm

you should see something like this (example)

Code: Select all: Marvell>> bootm 0x800000 bootm 0x800000 ## Booting image at 00800000 ... Image Name: Linux-2.6.39.4 Created: 2012-12-23 21:59:32 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 3123456 Bytes = 3 MB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK OK Starting kernel ...

If the kernel loads it should show you after mention starting kernel detailed output of kernel laoding in the u-boot console window.
something like this (example)

Code: Select all: Linux version 2.6.39.4 (root@fvdwsl-nwsp2.local) (gcc version 4.5.4 (GCC) ) #88 PREEMPT Tue Feb 19 22:14:37 GMT+1 2013 CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053177 CPU: VIVT data cache, VIVT instruction cache Machine: LaCie Network Space v2 Ignoring unrecognised tag 0x41000403 Memory policy: ECC disabled, Data cache writeback Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024 Kernel command line: console=ttyS0,115200 netconsole=6666@192.168.1.252/,6666@1 2.168.1.44/ PID hash table entries: 1024 (order: 0, 4096 bytes) Linux version 2.6.39.4 (root@fvdwsl-nwsp2.local) (gcc version 4.5.4 (GCC) ) #88 PREEMPT Tue Feb 19 22:14:37 GMT+1 2013 ...etc

If the kernel fails before netconsole is activated in the kernel then there will be no output
Hopefully it fails after netconsole in that case we can hopefully see why kernel fails

by **mattenwright** » Sat Sep 19, 2020 8:47 pm

My apologies for the delay, I wanted to make sure that I could replicate everything correctly and that there were no other possible computer related issues (I did not find any).

In normal cases I have the front LED turned off in the settings. Here are the steps that I have performed below:

- Set Front LED to ON in settings on installed kernel
- Shutdown the NAS.

Attempt to load via console - external firmware, load and run
LED Behavior:
Front LED: Not lit (OFF) after "Starting kernel ..."
Back LEDs: Solid Blue (instead of blinking or red)

End results: NAS not available on the network

Attempt to connect to U-Boot via console - U-Boot Console
LED Behavior:
Front LED: Not lit (OFF) after "Starting kernel ..."
Back LEDs: Solid Blue (instead of blinking or red)

Command outputs:

Code: Select all: provided by fvdw waiting for u-boot.. starting u-boot net console click on window and press enter Marvell>> setenv bootargs console=ttyS0,115200 netconsole=6666@${ipaddr}/,6666@${serverip}/ root=/dev/sda7 setenv bootargs console=ttyS0,115200 netconsole=6666@${ipaddr}/,6666@${serverip}/ root=/dev/sda7 Marvell>> printenv bootargs printenv bootargs bootargs=console=ttyS0,115200 netconsole=6666@192.168.2.222/,6666@192.168.2.135/ root=/dev/sda7 Marvell>> ide reset ide reset Reset IDE: Marvell Serial ATA Adapter Found adapter at bus 1, device 7 ... Scanning channels Device 1: OK Model: ST31500341AS Firm: CC4H Ser#: 9VS1ZRAP Type: Hard Disk Supports 48-bit addressing Capacity: 1430799.3 MB = 1397.2 GB (-1364690128 x 512) Device 2: OK Model: ST31500341AS Firm: CC1H Ser#: 9VS1S102 Type: Hard Disk Supports 48-bit addressing Capacity: 1430799.3 MB = 1397.2 GB (-1364690128 x 512) Device 3: OK Model: ST31500341AS Firm: CC4H Ser#: 9VS21Y8B Type: Hard Disk Supports 48-bit addressing Capacity: 1430799.3 MB = 1397.2 GB (-1364690128 x 512) Device 4: OK Model: ST2000DM001-1CH164 Firm: CC47 Ser#: Z1E7W9VC Type: Hard Disk Supports 48-bit addressing Capacity: 1907729.0 MB = 1863.0 GB (-387938128 x 512) Marvell>> tftpboot 0x800000 UIMAGE-3142-5BIG1-12 tftpboot 0x800000 UIMAGE-3142-5BIG1-12 Using egiga0 device TFTP from server 192.168.2.135; our IP address is 192.168.2.222 Filename 'UIMAGE-3142-5BIG1-12'. Load address: 0x800000 Loading: ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ########## done Bytes transferred = 2044704 (1f3320 hex) Marvell>> bootm bootm ## Booting image at 00800000 ... Image Name: linux-3.14.2-5big1-fvdw Created: 2020-09-12 22:12:31 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2044640 Bytes = 1.9 MB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK OK Starting kernel ... r6:c03dd5d4 r5:c7bc8280 [ 27.524840] r4:c0229e64 [ 27.527428] [<c00469c0>] (request_threaded_irq) from [<c0046b58>] (request_any_context_irq+0x74/0x7c) [ 27.536650] r10:c03d7f00 r9:c03d7f1c r8:c03627ef r7:c7049b74 r6:00000029 r5:c0229e64 [ 27.544734] r4:00000083 r3:00000083 [ 27.548398] [<c0046ae4>] (request_any_context_irq) from [<c0229cb8>] (gpio_keys_probe+0x2d4/0x480) [ 27.557359] r8:c7049b60 r7:c03d7d50 r6:c7052400 r5:00000083 r4:c7049b74 [ 27.564291] [<c02299e4>] (gpio_keys_probe) from [<c01c2b00>] (platform_drv_probe+0x20/0x54) [ 27.572643] r10:00000000 r9:00000000 r8:c03f30a0 r7:c03eccb0 r6:c041f3fc r5:c03eccb0 [ 27.580750] r4:c03d7d50 [ 27.583343] [<c01c2ae0>] (platform_drv_probe) from [<c01c1548>] (driver_probe_device+0xa8/0x1e4) [ 27.592126] r5:c03d7d84 r4:c03d7d50 [ 27.595807] [<c01c14a0>] (driver_probe_device) from [<c01c1740>] (__driver_attach+0x70/0x94) [ 27.604248] r7:c03ea230 r6:c03eccb0 r5:c03d7d84 r4:c03d7d50 [ 27.610088] [<c01c16d0>] (__driver_attach) from [<c01bfd10>] (bus_for_each_dev+0x74/0x98) [ 27.618270] r6:c01c16d0 r5:c03eccb0 r4:00000000 r3:00000001 [ 27.624102] [<c01bfc9c>] (bus_for_each_dev) from [<c01c10b0>] (driver_attach+0x20/0x28) [ 27.632120] r6:c703c6a0 r5:00000000 r4:c03eccb0 [ 27.636872] [<c01c1090>] (driver_attach) from [<c01c0d2c>] (bus_add_driver+0xe8/0x1d4) [ 27.644792] [<c01c0c44>] (bus_add_driver) from [<c01c1b80>] (driver_register+0xa4/0xe8) [ 27.652795] r7:c03ca3a8 r6:c03c5210 r5:c7828028 r4:c03eccb0 [ 27.658638] [<c01c1adc>] (driver_register) from [<c01c2acc>] (__platform_driver_register+0x50/0x64) [ 27.667683] r5:c7828028 r4:c03c0a90 [ 27.671381] [<c01c2a7c>] (__platform_driver_register) from [<c03c0aa8>] (gpio_keys_init+0x18/0x20) [ 27.680337] [<c03c0a90>] (gpio_keys_init) from [<c0008598>] (do_one_initcall+0x9c/0x140) [ 27.688436] [<c00084fc>] (do_one_initcall) from [<c03acb7c>] (kernel_init_freeable+0x100/0x1c4) [ 27.697138] r9:c03f30a0 r8:c03f30a0 r7:c03ca3a8 r6:c03c5210 r5:00000070 r4:00000007 [ 27.705117] [<c03aca7c>] (kernel_init_freeable) from [<c02d5710>] (kernel_init+0x10/0xec) [ 27.713276] r9:00000000 r8:00000000 r7:00000000 r6:00000000 r5:c02d5700 r4:00000000 [ 27.721229] [<c02d5700>] (kernel_init) from [<c000d9f0>] (ret_from_fork+0x14/0x24) [ 27.728786] r4:00000000 r3:00000000 [ 27.732434] handlers: [ 27.734725] [<c01fd258>] mv_interrupt [ 27.738408] Disabling IRQ #52

End results: NAS not available on the network, not responding after last line in kernel loading progress.

Thanks again!

by **fvdw** » Sun Sep 20, 2020 10:06 am

thx :thumbup
well the good news is, it is not the kernel size that is the problem, indeed loading the gpio_keys driver seems to cause a kernel crash.
See text in the kernel output like this

(gpio_keys_probe)

I will recompile a new kernel with slightly different initialization of the gpio keys driver

by **fvdw** » Sun Sep 20, 2020 11:04 am

it is done, a new trial kernel for testing #14 , same procedure as you did for #12

by **mattenwright** » Tue Sep 22, 2020 5:15 pm

Still no joy...

Code: Select all: provided by fvdw waiting for u-boot.. starting u-boot net console click on window and press enter Marvell>> setenv bootargs console=ttyS0,115200 netconsole=6666@${ipaddr}/,6666@${serverip}/ root=/dev/sda7 setenv bootargs console=ttyS0,115200 netconsole=6666@${ipaddr}/,6666@${serverip}/ root=/dev/sda7 Marvell>> printenv bootargs printenv bootargs bootargs=console=ttyS0,115200 netconsole=6666@192.168.2.222/,6666@192.168.2.135/ root=/dev/sda7 Marvell>> ide reset ide reset Reset IDE: Marvell Serial ATA Adapter Found adapter at bus 1, device 7 ... Scanning channels Device 1: OK Model: ST31500341AS Firm: CC4H Ser#: 9VS1ZRAP Type: Hard Disk Supports 48-bit addressing Capacity: 1430799.3 MB = 1397.2 GB (-1364690128 x 512) Device 2: OK Model: ST31500341AS Firm: CC1H Ser#: 9VS1S102 Type: Hard Disk Supports 48-bit addressing Capacity: 1430799.3 MB = 1397.2 GB (-1364690128 x 512) Device 3: OK Model: ST31500341AS Firm: CC4H Ser#: 9VS21Y8B Type: Hard Disk Supports 48-bit addressing Capacity: 1430799.3 MB = 1397.2 GB (-1364690128 x 512) Error - Failed initializing(SRST) drive on channel 4 Failed initializing storage deivce connected to SATA channel 4 Marvell>> ide reset ide reset Reset IDE: Marvell Serial ATA Adapter Found adapter at bus 1, device 7 ... Scanning channels Device 1: OK Model: ST31500341AS Firm: CC4H Ser#: 9VS1ZRAP Type: Hard Disk Supports 48-bit addressing Capacity: 1430799.3 MB = 1397.2 GB (-1364690128 x 512) Device 2: OK Model: ST31500341AS Firm: CC1H Ser#: 9VS1S102 Type: Hard Disk Supports 48-bit addressing Capacity: 1430799.3 MB = 1397.2 GB (-1364690128 x 512) Device 3: OK Model: ST31500341AS Firm: CC4H Ser#: 9VS21Y8B Type: Hard Disk Supports 48-bit addressing Capacity: 1430799.3 MB = 1397.2 GB (-1364690128 x 512) Device 4: OK Model: ST2000DM001-1CH164 Firm: CC47 Ser#: Z1E7W9VC Type: Hard Disk Supports 48-bit addressing Capacity: 1907729.0 MB = 1863.0 GB (-387938128 x 512) Marvell>> tftpboot 0x800000 UIMAGE-3142-5BIG1-14 tftpboot 0x800000 UIMAGE-3142-5BIG1-14 Using egiga0 device TFTP from server 192.168.2.135; our IP address is 192.168.2.222 Filename 'UIMAGE-3142-5BIG1-14'. Load address: 0x800000 Loading: ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ########## done Bytes transferred = 2044704 (1f3320 hex) Marvell>> bootm bootm ## Booting image at 00800000 ... Image Name: linux-3.14.2-5big1-fvdw Created: 2020-09-20 11:01:49 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2044640 Bytes = 1.9 MB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK OK Starting kernel ... [ 9.530377] [<c0008160>] (asm_do_IRQ) from [<c0011a74>] (__irq_svc+0x34/0x64) [ 9.537504] Exception stack(0xc7829cc0 to 0xc7829d08) [ 9.542561] 9cc0: 00000000 00000028 00000000 00000083 c03dd55c c7bc8580 00000000 00000000 [ 9.550737] 9ce0: 00000028 60000013 c03dd590 c7829d3c c7829ce8 c7829d08 c0047a44 c0046840 [ 9.558904] 9d00: 60000013 ffffffff [ 9.562410] [<c00464d0>] (__setup_irq) from [<c0046a90>] (request_threaded_irq+0xd0/0x124) [ 9.570664] r10:00000028 r9:c7049d74 r8:00000083 r7:00000000 r6:c03dd55c r5:c7bc8580 [ 9.578740] r4:c0229e64 [ 9.581326] [<c00469c0>] (request_threaded_irq) from [<c0046b58>] (request_any_context_irq+0x74/0x7c) [ 9.590549] r10:c03d7f00 r9:c03d7f1c r8:c03627ef r7:c7049d74 r6:00000028 r5:c0229e64 [ 9.598633] r4:00000083 r3:00000083 [ 9.602297] [<c0046ae4>] (request_any_context_irq) from [<c0229cb8>] (gpio_keys_probe+0x2d4/0x480) [ 9.611267] r8:c7049d60 r7:c03d7d50 r6:c7052800 r5:00000083 r4:c7049d74 [ 9.618192] [<c02299e4>] (gpio_keys_probe) from [<c01c2b00>] (platform_drv_probe+0x20/0x54) [ 9.626538] r10:00000000 r9:00000000 r8:c03f30a0 r7:c03eccb0 r6:c041f3fc r5:c03eccb0 [ 9.634621] r4:c03d7d50 [ 9.637228] [<c01c2ae0>] (platform_drv_probe) from [<c01c1548>] (driver_probe_device+0xa8/0x1e4) [ 9.646017] r5:c03d7d84 r4:c03d7d50 [ 9.649697] [<c01c14a0>] (driver_probe_device) from [<c01c1740>] (__driver_attach+0x70/0x94) [ 9.658137] r7:c03ea230 r6:c03eccb0 r5:c03d7d84 r4:c03d7d50 [ 9.663996] [<c01c16d0>] (__driver_attach) from [<c01bfd10>] (bus_for_each_dev+0x74/0x98) [ 9.672177] r6:c01c16d0 r5:c03eccb0 r4:00000000 r3:00000001 [ 9.678008] [<c01bfc9c>] (bus_for_each_dev) from [<c01c10b0>] (driver_attach+0x20/0x28) [ 9.686019] r6:c703cd00 r5:00000000 r4:c03eccb0 [ 9.690771] [<c01c1090>] (driver_attach) from [<c01c0d2c>] (bus_add_driver+0xe8/0x1d4) [ 9.698690] [<c01c0c44>] (bus_add_driver) from [<c01c1b80>] (driver_register+0xa4/0xe8) [ 9.706695] r7:c03ca3a8 r6:c03c5210 r5:c7828028 r4:c03eccb0 [ 9.712564] [<c01c1adc>] (driver_register) from [<c01c2acc>] (__platform_driver_register+0x50/0x64) [ 9.721617] r5:c7828028 r4:c03c0a90 [ 9.725314] [<c01c2a7c>] (__platform_driver_register) from [<c03c0aa8>] (gpio_keys_init+0x18/0x20) [ 9.734271] [<c03c0a90>] (gpio_keys_init) from [<c0008598>] (do_one_initcall+0x9c/0x140) [ 9.742358] [<c00084fc>] (do_one_initcall) from [<c03acb7c>] (kernel_init_freeable+0x100/0x1c4) [ 9.751055] r9:c03f30a0 r8:c03f30a0 r7:c03ca3a8 r6:c03c5210 r5:00000070 r4:00000007 [ 9.759024] [<c03aca7c>] (kernel_init_freeable) from [<c02d5710>] (kernel_init+0x10/0xec) [ 9.767185] r9:00000000 r8:00000000 r7:00000000 r6:00000000 r5:c02d5700 r4:00000000 [ 9.775119] [<c02d5700>] (kernel_init) from [<c000d9f0>] (ret_from_fork+0x14/0x24) [ 9.782686] r4:00000000 r3:00000000 [ 9.786350] handlers: [ 9.788642] [<c01fd258>] mv_interrupt [ 9.792316] Disabling IRQ #52

One of my drives was being a bit weird, hence the 2nd reset.

by **fvdw** » Tue Sep 22, 2020 8:46 pm

thank you,
Although the output is limited
it still seems gpio_keys driver crashes the kernel when probing the platform device gpio-keys :scratch
The activation of netconsole takes some time therefor we loose some data in beginning of kernel start
I o, or is it because it fills the command window to quick to capture all of it

Anyhow I looked at previous kernel 2.6.39.4, there gpio_keys driver was included and working oke.
I modified the driver on 3.14.2 to match the code in 2.6.39.4 kernel and added some print calls in the probe function.
Hopefully they show us where the probe fails if the patches are not sufficient to solve the issue

Attached kernel #15, hopefully you can find time to test it

If it doesn't work we can try to incoperated the gpioKeys driver from Lacie GPL code

by **mattenwright** » Fri Sep 25, 2020 1:48 am

Sadly it looks to be about the same...
As a note, I capture the entire command window... so there must be a slight delay for the console that you were speaking about.

Code: Select all: provided by fvdw waiting for u-boot.. starting u-boot net console click on window and press enter Marvell>> setenv bootargs console=ttyS0,115200 netconsole=6666@${ipaddr}/,6666@${serverip}/ root=/dev/sda7 setenv bootargs console=ttyS0,115200 netconsole=6666@${ipaddr}/,6666@${serverip}/ root=/dev/sda7 Marvell>> printenv bootargs printenv bootargs bootargs=console=ttyS0,115200 netconsole=6666@192.168.2.222/,6666@192.168.2.135/ root=/dev/sda7 Marvell>> ide reset ide reset Reset IDE: Marvell Serial ATA Adapter Found adapter at bus 1, device 7 ... Scanning channels Device 1: OK Model: ST31500341AS Firm: CC4H Ser#: 9VS1ZRAP Type: Hard Disk Supports 48-bit addressing Capacity: 1430799.3 MB = 1397.2 GB (-1364690128 x 512) Device 2: OK Model: ST31500341AS Firm: CC1H Ser#: 9VS1S102 Type: Hard Disk Supports 48-bit addressing Capacity: 1430799.3 MB = 1397.2 GB (-1364690128 x 512) Device 3: OK Model: ST31500341AS Firm: CC4H Ser#: 9VS21Y8B Type: Hard Disk Supports 48-bit addressing Capacity: 1430799.3 MB = 1397.2 GB (-1364690128 x 512) Device 4: OK Model: ST2000DM001-1CH164 Firm: CC47 Ser#: Z1E7W9VC Type: Hard Disk Supports 48-bit addressing Capacity: 1907729.0 MB = 1863.0 GB (-387938128 x 512) Marvell>> tftpboot 0x800000 UIMAGE-3142-5BIG1-15 tftpboot 0x800000 UIMAGE-3142-5BIG1-15 Using egiga0 device TFTP from server 192.168.2.135; our IP address is 192.168.2.222 Filename 'UIMAGE-3142-5BIG1-15'. Load address: 0x800000 Loading: ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ########## done Bytes transferred = 2044752 (1f3350 hex) Marvell>> bootm bootm ## Booting image at 00800000 ... Image Name: linux-3.14.2-5big1-fvdw Created: 2020-09-22 20:40:58 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2044688 Bytes = 1.9 MB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK OK Starting kernel ... [ 14.317139] 9be0: 00000008 c03f3b40 00000028 60000013 c03dd590 c7829c6c c7829c10 c7829c10 [ 14.325308] 9c00: c001de2c c001ea6c 60000013 ffffffff [ 14.330374] [<c001e9e4>] (__do_softirq) from [<c001ee64>] (irq_exit+0x88/0xe8) [ 14.337604] r10:c03dd590 r9:60000013 r8:00000028 r7:c7829cec r6:00000000 r5:00000015 [ 14.345664] r4:c7828030 [ 14.348254] [<c001eddc>] (irq_exit) from [<c000e898>] (handle_IRQ+0x6c/0x88) [ 14.355322] r4:c03e2c60 r3:00000040 [ 14.358982] [<c000e82c>] (handle_IRQ) from [<c0008170>] (asm_do_IRQ+0x10/0x14) [ 14.366226] r6:fe020200 r5:60000013 r4:c0046840 r3:c0047a44 [ 14.372082] [<c0008160>] (asm_do_IRQ) from [<c0011a74>] (__irq_svc+0x34/0x64) [ 14.379208] Exception stack(0xc7829cb8 to 0xc7829d00) [ 14.384254] 9ca0: 00000000 00000028 [ 14.392421] 9cc0: 00000000 00000083 c03dd55c c7bc8280 00000000 00000000 00000028 60000013 [ 14.400598] 9ce0: c03dd590 c7829d34 c7829ce0 c7829d00 c0047a44 c0046840 60000013 ffffffff [ 14.408773] [<c00464d0>] (__setup_irq) from [<c0046a90>] (request_threaded_irq+0xd0/0x124) [ 14.417026] r10:00000028 r9:c7049b74 r8:00000083 r7:00000000 r6:c03dd55c r5:c7bc8280 [ 14.425118] r4:c0229f0c [ 14.427716] [<c00469c0>] (request_threaded_irq) from [<c0046b58>] (request_any_context_irq+0x74/0x7c) [ 14.436938] r10:c03d7f00 r9:c03d7f1c r8:c036279f r7:c7049b74 r6:00000028 r5:c0229f0c [ 14.445012] r4:00000083 r3:00000083 [ 14.448676] [<c0046ae4>] (request_any_context_irq) from [<c0229ccc>] (gpio_keys_probe+0x304/0x544) [ 14.457637] r8:c7049b60 r7:c03d7d50 r6:00000083 r5:c7052400 r4:c7049b7c [ 14.464580] [<c02299c8>] (gpio_keys_probe) from [<c01c2b00>] (platform_drv_probe+0x20/0x54) [ 14.472924] r10:00000000 r9:00000000 r8:c03f30a0 r7:c03eccb0 r6:c041f3fc r5:c03eccb0 [ 14.481027] r4:c03d7d50 [ 14.483621] [<c01c2ae0>] (platform_drv_probe) from [<c01c1548>] (driver_probe_device+0xa8/0x1e4) [ 14.492403] r5:c03d7d84 r4:c03d7d50 [ 14.496085] [<c01c14a0>] (driver_probe_device) from [<c01c1740>] (__driver_attach+0x70/0x94) [ 14.504526] r7:c03ea230 r6:c03eccb0 r5:c03d7d84 r4:c03d7d50 [ 14.510384] [<c01c16d0>] (__driver_attach) from [<c01bfd10>] (bus_for_each_dev+0x74/0x98) [ 14.518575] r6:c01c16d0 r5:c03eccb0 r4:00000000 r3:00000001 [ 14.524398] [<c01bfc9c>] (bus_for_each_dev) from [<c01c10b0>] (driver_attach+0x20/0x28) [ 14.532415] r6:c703c700 r5:00000000 r4:c03eccb0 [ 14.537186] [<c01c1090>] (driver_attach) from [<c01c0d2c>] (bus_add_driver+0xe8/0x1d4) [ 14.545104] [<c01c0c44>] (bus_add_driver) from [<c01c1b80>] (driver_register+0xa4/0xe8) [ 14.553108] r7:c03ca3a8 r6:c03c5210 r5:c7828028 r4:c03eccb0 [ 14.558969] [<c01c1adc>] (driver_register) from [<c01c2acc>] (__platform_driver_register+0x50/0x64) [ 14.568013] r5:c7828028 r4:c03c0a90 [ 14.571712] [<c01c2a7c>] (__platform_driver_register) from [<c03c0aa8>] (gpio_keys_init+0x18/0x20) [ 14.580668] [<c03c0a90>] (gpio_keys_init) from [<c0008598>] (do_one_initcall+0x9c/0x140) [ 14.588777] [<c00084fc>] (do_one_initcall) from [<c03acb7c>] (kernel_init_freeable+0x100/0x1c4) [ 14.597475] r9:c03f30a0 r8:c03f30a0 r7:c03ca3a8 r6:c03c5210 r5:00000070 r4:00000007 [ 14.605464] [<c03aca7c>] (kernel_init_freeable) from [<c02d57b8>] (kernel_init+0x10/0xec) [ 14.613635] r9:00000000 r8:00000000 r7:00000000 r6:00000000 r5:c02d57a8 r4:00000000 [ 14.621594] [<c02d57a8>] (kernel_init) from [<c000d9f0>] (ret_from_fork+0x14/0x24) [ 14.629151] r4:00000000 r3:00000000 [ 14.632808] handlers: [ 14.635099] [<c01fd258>] mv_interrupt [ 14.638792] Disabling IRQ #52

by **fvdw** » Fri Sep 25, 2020 6:41 pm

thax for testing much appreciated.
I will go now for another route. I must have lying around an lacie internetspace. This device is also an orion cpu based nas like 5big1. I will see if I can get a 3.14.2 kernel with gpio_kyes driver up and running on that device. It should have same issue with it as a 5big1 I expect. I can hook up th serial interface and that will make it easier for me to find where the problem is in the code. I will be back...hope you can wait a little

by **fvdw** » Fri Sep 25, 2020 9:43 pm

I did the test on internet space vs 1 and...no kernel crash. :thumbup
That would mean the problem is not the code of the gpio_keys driver but the gpio definition in the setup of the mainboard, I will need some time to see what is different compared to kernel 2.6.39.4
To be continued...

plugout.net

New Installtion on 5Big - Trouble adding disks

Re: New Installtion on 5Big - Trouble adding disks

Re: New Installtion on 5Big - Trouble adding disks

Re: New Installtion on 5Big - Trouble adding disks

Re: New Installtion on 5Big - Trouble adding disks

Re: New Installtion on 5Big - Trouble adding disks

Re: New Installtion on 5Big - Trouble adding disks

Re: New Installtion on 5Big - Trouble adding disks

Re: New Installtion on 5Big - Trouble adding disks

Re: New Installtion on 5Big - Trouble adding disks

Re: New Installtion on 5Big - Trouble adding disks

Who is online