Processed: Re: Bug#1013330: linux-image-5.18.0-0.bpo.1-arm64: kernel panic in dpaa2_eth_free_tx_fd

2022-12-05 Thread Debian Bug Tracking System 
Processing control commands:

> tag -1 moreinfo
Bug #1013330 [src:linux] linux-image-5.18.0-0.bpo.1-arm64: kernel panic in 
dpaa2_eth_free_tx_fd
Added tag(s) moreinfo.

-- 
1013330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013330
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1013330: linux-image-5.18.0-0.bpo.1-arm64: kernel panic in dpaa2_eth_free_tx_fd

2022-12-05 Thread Diederik de Haas 
Control: tag -1 moreinfo

On woensdag 22 juni 2022 00:20:22 CET you wrote:
> Kernel 5.18.3 contains (at least) 2 patches related to dpaa2-eth.
> Kernel 5.18.5-1 (currently in Sid) does contain quite a few fixes vs 5.18.2,
> so it would be useful to verify if that fixes your issue. I don't know when
> or what version becomes available next in Stable Backports though.

Have you been able to test a more recent bpo kernel? If so, what was the 
result? If not, could you (and inform the bug about it)?

signature.asc
Description: This is a digitally signed message part.

Bug#1013330: linux-image-5.18.0-0.bpo.1-arm64: kernel panic in dpaa2_eth_free_tx_fd

2022-06-21 Thread Diederik de Haas 
Control: reassign src:linux 5.18.2-1

On Tuesday, 21 June 2022 23:31:29 CEST Harald Welte wrote:
> Package: linux-image-5.18.0-0.bpo.1-arm64
> Version: 5.18.2-1~bpo11+1
> 
> today I briefly tried the backport 5.18 kernel on bullseye. It boots fine,
> but as soon as some network traffic happens, it panics with a backtrace
> indicating  some kind of problem in the dpaa2_eth netwokr driver.
> 
> [   46.451190] Unable to handle kernel paging request at virtual address
> fcf7fe08 [   46.459126] Mem abort info:
> [   46.461937]   ESR = 0x9605
> [   46.464983]   EC = 0x25: DABT (current EL), IL = 32 bits
> [   46.470301]   SET = 0, FnV = 0
> [   46.473347]   EA = 0, S1PTW = 0
> [   46.476491]   FSC = 0x05: level 1 translation fault
> [   46.481373] Data abort info:
> [   46.484257]   ISV = 0, ISS = 0x0005
> [   46.488095]   CM = 0, WnR = 0
> [   46.491067] swapper pgtable: 4k pages, 48-bit VAs, pgdp=8258f000
> [   46.497786] [fcf7fe08] pgd=102f78387003,
> p4d=102f78387003, pud= [   46.506496] Internal error:
> Oops: 9605 [#1] SMP

Kernel 5.18.3 contains (at least) 2 patches related to dpaa2-eth.
Kernel 5.18.5-1 (currently in Sid) does contain quite a few fixes vs 5.18.2, so 
it would be useful to verify if that fixes your issue. I don't know when or 
what version becomes available next in Stable Backports though.

signature.asc
Description: This is a digitally signed message part.

Bug#1013330: linux-image-5.18.0-0.bpo.1-arm64: kernel panic in dpaa2_eth_free_tx_fd

2022-06-21 Thread Harald Welte 
Package: linux-image-5.18.0-0.bpo.1-arm64
Version: 5.18.2-1~bpo11+1
Severity: normal

Dear Maintainer,

today I briefly tried the backport 5.18 kernel on bullseye. It boots fine,
but as soon as some network traffic happens, it panics with a backtrace
indicating  some kind of problem in the dpaa2_eth netwokr driver.

The problem can be reproduced 100% within very few seconds after system boot. 
One can
usually still ssh into the machine, but then the first shell command producing
more than a single-line output (like ls -l /etc) makes the kernel panic like 
below.

As soon as I downgraded back to linux-image-5.10.0-15-arm64 = 5.10.120-1 the 
problem
disappeared.  On 5.10.120-1 the network runs very stable.

[   46.451190] Unable to handle kernel paging request at virtual address 
fcf7fe08
[   46.459126] Mem abort info:
[   46.461937]   ESR = 0x9605
[   46.464983]   EC = 0x25: DABT (current EL), IL = 32 bits
[   46.470301]   SET = 0, FnV = 0
[   46.473347]   EA = 0, S1PTW = 0
[   46.476491]   FSC = 0x05: level 1 translation fault
[   46.481373] Data abort info:
[   46.484257]   ISV = 0, ISS = 0x0005
[   46.488095]   CM = 0, WnR = 0
[   46.491067] swapper pgtable: 4k pages, 48-bit VAs, pgdp=8258f000
[   46.497786] [fcf7fe08] pgd=102f78387003, p4d=102f78387003, 
pud=
[   46.506496] Internal error: Oops: 9605 [#1] SMP
[   46.511364] Modules linked in: caam_jr crypto_engine rng_core aes_ce_blk 
aes_ce_cipher ghash_ce dpaa2_caam gf128mul caamhash_desc sha2_ce caamalg_desc 
sha256_arm64 authenc libdes sha1_ce dpaa2_console caam ofpart error lm90 
spi_nor at24 mtd sbsa_gwdt qoriq_thermal evdev layerscape_edac_mod 
qoriq_cpufreq drm fuse configfs ip_tables x_tables autofs4 ext4 crc16 mbcache 
jbd2 crc32c_generic dm_mod dax fsl_dpaa2_ptp fsl_dpaa2_eth xhci_plat_hcd 
xhci_hcd usbcore nvme nvme_core ahci_qoriq t10_pi libahci_platform libahci 
at803x libata fsl_mc_dpio crc64_rocksoft ptp_qoriq crc64 xgmac_mdio pcs_lynx 
acpi_mdio phylink crc_t10dif mdio_devres rtc_pcf2127 ptp of_mdio 
i2c_mux_pca954x crct10dif_generic regmap_spi i2c_mux dwc3 fixed_phy pps_core 
fwnode_mdio scsi_mod udc_core sfp crct10dif_ce sdhci_of_esdhc crct10dif_common 
mdio_i2c roles sdhci_pltfm ulpi scsi_common usb_common libphy sdhci 
spi_nxp_fspi i2c_imx fixed gpio_keys
[   46.591702] CPU: 7 PID: 822 Comm: sshd Not tainted 5.18.0-0.bpo.1-arm64 #1  
Debian 5.18.2-1~bpo11+1
[   46.600736] Hardware name: SolidRun LX2160A Clearfog CX (DT)
[   46.606383] pstate: a005 (NzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[   46.613332] pc : kfree+0x78/0x290
[   46.616644] lr : dpaa2_eth_free_tx_fd.isra.0+0x308/0x3b4 [fsl_dpaa2_eth]
[   46.623341] sp : 8aa3b2d0
[   46.626643] x29: 8aa3b2d0 x28: 3e200d37a800 x27: 3e2005045d00
[   46.633769] x26: 0001 x25: 0001 x24: 0002
[   46.640895] x23: b76243dab000 x22: b76239b320e8 x21: faee1740
[   46.648020] x20: 3dff8000 x19: fcf7fe00 x18: 
[   46.655145] x17: 86cc769fc000 x16: b762425450d0 x15: 4000
[   46.662270] x14:  x13: c2008000 x12: 0001
[   46.669395] x11: 0004 x10: 0008 x9 : b76239b320e8
[   46.676520] x8 :  x7 : 000faee2 x6 : 3e2000ce4a00
[   46.683645] x5 : b76243196000 x4 : 0003 x3 : 0009
[   46.690769] x2 :  x1 : 0030 x0 : fc00
[   46.697894] Call trace:
[   46.700328]  kfree+0x78/0x290
[   46.703286]  dpaa2_eth_free_tx_fd.isra.0+0x308/0x3b4 [fsl_dpaa2_eth]
[   46.709631]  dpaa2_eth_tx_conf+0xb0/0x19c [fsl_dpaa2_eth]
[   46.715020]  dpaa2_eth_poll+0xf4/0x3b0 [fsl_dpaa2_eth]
[   46.720149]  __napi_poll+0x40/0x1dc
[   46.723628]  net_rx_action+0x2fc/0x390
[   46.727366]  __do_softirq+0x120/0x348
[   46.731017]  __irq_exit_rcu+0x10c/0x140
[   46.734842]  irq_exit_rcu+0x1c/0x30
[   46.738320]  el1_interrupt+0x38/0x54
[   46.741885]  el1h_64_irq_handler+0x18/0x24
[   46.745970]  el1h_64_irq+0x64/0x68
[   46.749360]  n_tty_poll+0x98/0x1e0
[   46.752752]  tty_poll+0x7c/0x114
[   46.755968]  do_select+0x28c/0x64c
[   46.759361]  core_sys_select+0x238/0x3a0
[   46.763273]  __arm64_sys_pselect6+0x17c/0x280
[   46.767619]  invoke_syscall+0x50/0x120
[   46.771357]  el0_svc_common.constprop.0+0x4c/0xf4
[   46.776051]  do_el0_svc+0x30/0x90
[   46.779354]  el0_svc+0x34/0xd0
[   46.782397]  el0t_64_sync_handler+0x1a4/0x1b0
[   46.786743]  el0t_64_sync+0x18c/0x190
[   46.790396] Code: 8b130293 b25657e0 d34cfe73 8b131813 (f9400660) 
[   46.796478] ---[ end trace  ]---
[   46.801083] Kernel panic - not syncing: Oops: Fatal exception in interrupt
[   46.807945] SMP: stopping secondary CPUs
[   46.811867] Kernel Offset: 0x37623a20 from 0x8800
[   46.817947] PHYS_OFFSET: 0xc2008000
[   46.822116] CPU features: 0x100,4b09,1086
[