Welcome! Log In Create A New Profile

Advanced

goflexhome kernel panics

Posted by ia_nasir 
goflexhome kernel panics
December 23, 2021 01:57AM
Hi

I'm running the following debian release on my goflexhome

root@debian:~# uname -a
Linux debian 4.4.0-kirkwood-tld-1 #1 PREEMPT Mon Jan 25 20:35:24 PST 2016 armv5tel GNU/Linux
root@debian:~#

I routinely see kernel page faults like the one shown below.

I'm running the latest uboot (2017.07 U-Boot). Also tried with Debian-5.13.6-kirkwood-tld-1-rootfs-bodhi.tar.bz2 as well as other versions. Not much difference.

Do I have a settings problem or maybe a physical memory issue?
I'm booting off of the hard disk

root@debian:~# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00100000 00020000 "u-boot"
mtd1: 0ff00000 00020000 "rootfs"

root@debian:~#

This is my kernel console log showing the pagefault

[   18.688522] console [netcon0] enabled
[   18.692221] netconsole: network logging started
[   22.417350] EXT4-fs (sda3): mounting ext3 file system using the ext4 subsystem
[   22.435228] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
[   22.944074] random: nonblocking pool is initialized
[   24.038099] systemd-udevd[299]: starting version 215
[   24.516080] orion_wdt: Initial timeout 21 sec
[   24.561485] marvell-cesa: probe of f1030000.crypto failed with error -524
[   25.967223] EXT4-fs (sda3): re-mounted. Opts: (null)
[   26.453443] EXT4-fs (sda3): re-mounted. Opts: errors=remount-ro
[   28.290618] Adding 1048572k swap on /swapfile.  Priority:-1 extents:20 across:9301828k FS
[   29.760414] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
[   31.298527] NET: Registered protocol family 10
[77668.434468] Unable to handle kernel paging request at virtual address e0233002
[77668.441789] pgd = c5b24000
[77668.444836] [e0233002] *pgd=00000000
[77668.448494] Internal error: Oops: 1 [#1] PREEMPT ARM
[77668.453484] Modules linked in: ipv6 marvell_cesa orion_wdt des_generic uio_pdrv_genirq uio netconsole configfs sg sd_mod sata_mv libata fixed scsi_mod
[77668.467187] CPU: 0 PID: 4770 Comm: smbd Not tainted 4.4.0-kirkwood-tld-1 #1
[77668.474186] Hardware name: Marvell Kirkwood (Flattened Device Tree)
[77668.480484] task: c5848dc0 ti: c7098000 task.ti: c7098000
[77668.485922] PC is at anon_vma_clone+0x74/0x16c
[77668.490401] LR is at anon_vma_clone+0x3c/0x16c
[77668.494874] pc : [<c00f2f34>]    lr : [<c00f2efc>]    psr: a0000013
[77668.494874] sp : c7099ea0  ip : c090e974  fp : c33336e0
[77668.506407] r10: c08a3fa7  r9 : e0233002  r8 : c3d4d8a0
[77668.511657] r7 : c72557c0  r6 : c72457f4  r5 : c0906608  r4 : c3d4d8a0
[77668.518223] r3 : c08a4a5c  r2 : 00000000  r1 : c7ee9268  r0 : c33336e0
[77668.524781] Flags: NzCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment none
[77668.531957] Control: 0005397f  Table: 05b24000  DAC: 00000051
[77668.537728] Process smbd (pid: 4770, stack limit = 0xc7098190)
[77668.543593] Stack: (0xc7099ea0 to 0xc709a000)
[77668.547982] 9ea0: 00000000 c468e060 01200011 c0906608 00000002 c72557c0 c72557c0 c738e1e0
[77668.556204] 9ec0: c0906608 c00f3058 c468e060 01200011 c5882620 00000002 00000000 c001d108
[77668.564427] 9ee0: c010d714 00000000 c468e278 c7098000 c0906660 c0906670 c738e214 c738e330
[77668.572649] 9f00: c5882654 c6dc3844 c0906668 c0906674 b50d3068 00000000 00000000 00000000
[77668.580873] 9f20: 970ad06c 000046a3 c5611164 00000000 806b6540 00000000 becb4860 01200011
[77668.589094] 9f40: 00000078 00000000 c7098000 00000000 becb48a4 c001ddc4 00000000 00000000
[77668.597319] 9f60: 00000000 0000002a c000f1a8 becb48c0 becb48c0 00000000 00000001 b50d3068
[77668.605546] 9f80: becb4860 b50d3000 00000078 c000f1a8 c7098000 c001e1b4 b50d3068 00000000
[77668.613773] 9fa0: 00000000 c000efe0 b50d3068 becb4860 01200011 00000000 00000000 00000000
[77668.621997] 9fc0: b50d3068 becb4860 b50d3000 00000078 b6481000 806c251c 000012a2 becb48a4
[77668.630220] 9fe0: b50d34c0 becb4860 000012a2 b63df574 60000010 01200011 00000000 00000000
[77668.638451] [<c00f2f34>] (anon_vma_clone) from [<c00f3058>] (anon_vma_fork+0x2c/0x154)
[77668.646416] [<c00f3058>] (anon_vma_fork) from [<c001d108>] (copy_process+0xab4/0x1658)
[77668.654384] [<c001d108>] (copy_process) from [<c001ddc4>] (_do_fork+0x78/0x3a4)
[77668.661735] [<c001ddc4>] (_do_fork) from [<c001e1b4>] (SyS_clone+0x1c/0x24)
[77668.668747] [<c001e1b4>] (SyS_clone) from [<c000efe0>] (ret_fast_syscall+0x0/0x38)
[77668.676367] Code: e250b000 0a000035 e3a04000 e5969004 (e5998000)
[77668.683081] ---[ end trace c2b169f4dd8eeea9 ]---


This is my uboot env (ignore the bootubi stuff)

root@debian:~# fw_printenv
arcNumber=3338
bootargs=console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:1M(u-boot),-(rootfs)
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; run bootubi
bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fi; else if run load_dtb; then bootm $load_uimage_addr - $load_dtb_addr; else bootm $load_uimage_addr; fi; fi
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi; sleep 3
bootdelay=10
bootdev=usb
bootubi=echo Trying to boot from NAND ...;if run mountubi; then ubifsload ${loadaddr} /boot/zImage;ubifsload ${fdtaddr} /boot/dtbs/${fdtfile};ubifsumount; setenv bootargs console=${console} ubi.mtd=1 root=ubi0:rootfs ro rootfstype=ubifs  rootwait ${mtdparts};bootz ${loadaddr} - ${fdtaddr};fi
console=ttyS0,115200
device=0:1
device_type=mmc
devices=usb ide mmc
disk_number=3
disks=0 1 2 3
dtb_file=/boot/dts/kirkwood-goflexhome.dtb
ethact=egiga0
ethaddr=00:10:75:2D:39:62
fdtaddr=0x800000
fdtdir=/boot/dtbs
fdtfile=kirkwood-goflexhome.dtb
if_netconsole=ping $serverip
init_ide=ide reset
init_mmc=mmc rescan
init_usb=usb start
ipaddr=192.168.1.70
led_error=orange blinking
led_exit=green off
led_init=green blinking
load_dtb=echo loading DTB $dtb_file ...; load $bootdev $device $load_dtb_addr $dtb_file
load_dtb_addr=0x1c00000
load_initrd=echo loading uInitrd ...; load $bootdev $device $load_initrd_addr /boot/uInitrd
load_initrd_addr=0x1100000
load_uimage=echo loading uImage ...; load $bootdev $device $load_uimage_addr /boot/uImage
load_uimage_addr=0x800000
loadaddr=0x810000
mainlineLinux=yes
mtddevname=u-boot
mtddevnum=0
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),-(rootfs)
nc_ready=1
ncargs=ignore_loglevel netconsole=6665@192.168.1.70/eth0,6666@192.168.1.51/
ncip=192.168.1.50
ncipk=192.168.1.51
partition=nand0,0
partitions=1 3
preboot=run preboot_nc
preboot_nc=setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then run start_netconsole; fi
scan_disk=echo running scan_disk ...; scan_done=0; setenv scan_usb "usb start"; setenv scan_ide "ide reset"; setenv scan_mmc "mmc rescan"; for dev in $devices; do for part in $partitions; do if test $scan_done -eq 0; then echo Scan device $dev; run scan_$dev; for disknum in $disks; do if test $scan_done -eq 0; then echo device $dev $disknum:$part; if load $dev $disknum:$part $load_uimage_addr /boot/uImage 1; then scan_done=1; echo Found bootable drive on $dev $disknum; setenv device $disknum:$part; setenv bootdev $dev; fi; fi; done; fi; done; done
scan_ide=ide reset
scan_mmc=mmc rescan
scan_usb=usb start
serverip=192.168.1.50
set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts netconsole=6665@${ipaddr}/eth0,6666@${ncipk}/ $custom_params
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; setenv ncargs ignore_loglevel netconsole=6665@${ipaddr}/eth0,6666@${ncipk}/; version;
stderr=nc
stdin=nc
stdout=nc
uenv_addr=0x810000
uenv_import=echo importing envs ...; env import -t $uenv_addr $filesize
uenv_init_devices=echo Initializing devices...; setenv init_usb "usb start";  setenv init_ide "ide reset";  setenv init_mmc "mmc rescan"; for devtype in $devices; do run init_$devtype; done
uenv_load=run uenv_init_devices; setenv uenv_loaded 0; for devtype in $devices; do for disknum in $disks; do if test $uenv_loaded -eq 0; then setenv device_type $devtype; setenv disk_number $disknum; run uenv_read; fi; done; done;
uenv_loaded=0
uenv_read=echo Loading envs from $device_type $disk_number...; if load $device_type  $disk_number:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; echo ... envs loaded; fi
usb_ready_retry=15

root@debian:~#

==============

moderator edit: please use code tags (formatted code button) to post log



Edited 2 time(s). Last edit at 12/23/2021 02:04PM by bodhi.
Re: goflexhome kernel panics
December 23, 2021 02:16PM
ia_nasir,

> Linux debian 4.4.0-kirkwood-tld-1 #1 PREEMPT Mon
> Jan 25 20:35:24 PST 2016 armv5tel GNU/Linux

That's a quite old kernel.

> Also tried with
> Debian-5.13.6-kirkwood-tld-1-rootfs-bodhi.tar.bz2
> as well as other versions. Not much difference.

But you have also tried the new rootfs. I hope you have set up swap while running the rootfs Debian-5.13.6-kirkwood-tld-1?

This problem is hard to track down, because it could be caused by a lot of things.

Create a new rootfs Debian-5.13.6-kirkwood-tld-1 on a USB drive, set up swap, and then run it for a while. See if you still have this problem. And please post the entire log (not excerpts) when you see it again.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: goflexhome kernel panics
December 25, 2021 07:38AM
Thanks bodhi.

I had started off with Debian-5.13.6-kirkwood-tld-1 on a USB stick with swap at 512 MB. Saw the same kind of issues along with process crashes. Thinking it might have been because of my USB drive, I installed the same on the HDD and wasn't much different although the frequency of process crashes on USB was higher. I was also having issues with getting samba to work with my Windows 11 box.

So I purposefully installed an older one in the hopes that an older samba version would work and it did, but the crash issues are still there.

FWIW, prior to moving to debian, I had Arch linux installed and would see the kernel panics there too. That's' why I moved to debian, But not much improvement either :-)

Currently I have 1 G swap configured
Re: goflexhome kernel panics
December 26, 2021 03:08PM
ia_nasir,

> FWIW, prior to moving to debian, I had Arch linux
> installed and would see the kernel panics there
> too. That's' why I moved to debian, But not much
> improvement either :-)

That's an indicator of HW problems, when you run 2 different distro rootfs and see the same error. Unless you were not root (sudo does not work) when you created either rootfs.

I think you shoud check the power supply. Use a meter to measure the Volt and Amp at the power supply output. Or use a different power supply to see if the problem goes away.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: goflexhome kernel panics
December 29, 2021 02:15AM
bodhi

Yes I was root when I created the distros. It definitely seems to be a hardware issue. I installed openwrt on the box and even there the same issue. You think power supply might cause this? I was thinking that maybe my RAM might be the issue.

For the power supply test, I just need to check whether the output is in line with the PS specs?

Thanks for your help
Re: goflexhome kernel panics
December 29, 2021 02:56PM
ia_nasir,

> For the power supply test, I just need to check
> whether the output is in line with the PS specs?

Right! 12V 2A.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Author:

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: