Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #90966 > unrolled thread

Bug#1126410: linux-image-6.18.5+deb14-arm64: null pointer dereference on arm64 during boot

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#1126410: linux-image-6.18.5+deb14-arm64: null pointer dereference on arm64 during boot Uwe Kleine-König <u.kleine-koenig@baylibre.com> - 2026-01-26 00:00 +0100
    Bug#1126410: linux-image-6.18.5+deb14-arm64: null pointer dereference on arm64 during boot mc36 <csmate@nop.hu> - 2026-01-26 00:10 +0100
      Bug#1126410: linux-image-6.18.5+deb14-arm64: null pointer dereference on arm64 during boot Uwe Kleine-König <u.kleine-koenig@baylibre.com> - 2026-01-26 07:40 +0100
        Bug#1126410: linux-image-6.18.5+deb14-arm64: null pointer dereference on arm64 during boot mc36 <csmate@nop.hu> - 2026-01-26 11:30 +0100

#90966 — Bug#1126410: linux-image-6.18.5+deb14-arm64: null pointer dereference on arm64 during boot

[Multipart message — attachments visible in raw view] — view raw

Hello,

On Sun, Jan 25, 2026 at 02:31:09PM +0100, mc36 wrote:
> Package: src:linux
> Version: 6.18.5-1
> Severity: normal
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where appropriate ***
> 
>    * What led up to the situation?
> upgrade to linux-image-arm64 which is 6.18.5 at the time of writing

Did you update from 6.18.3-1? Or something earlier?

>    * What exactly did you do (or not do) that was effective (or
>      ineffective)?
> sudo apt-get update ; sudo apt-get dist-upgrade ; sudo reboot
> 
>    * What was the outcome of this action?
> console hang, see log below
> 
>    * What outcome did you expect instead?
> boot up as usual, like on 6.17....
> [    4.557694] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000080
> [    4.557699] Mem abort info:
> [    4.557701]   ESR = 0x0000000096000004
> [    4.557704]   EC = 0x25: DABT (current EL), IL = 32 bits
> [    4.557707]   SET = 0, FnV = 0
> [    4.557710]   EA = 0, S1PTW = 0
> [    4.557713]   FSC = 0x04: level 0 translation fault
> [    4.557716] Data abort info:
> [    4.557718]   ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000
> [    4.557721]   CM = 0, WnR = 0, TnD = 0, TagAccess = 0
> [    4.557725]   GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0
> [    4.557728] [0000000000000080] user address but active_mm is swapper
> [    4.557732] Internal error: Oops: 0000000096000004 [#1]  SMP
> [    4.559914] Modules linked in:
> [    6.257097] CPU: 2 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.18.5+deb14-arm64 #1 PREEMPTLAZY  Debian 6.18.5-1
> [    6.267271] Hardware name: Marvell OcteonTX CN96XX board (DT)
> [    6.273013] pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
> [    6.279972] pc : of_pci_add_properties+0x2a8/0x5c0
> [    6.284765] lr : of_pci_add_properties+0x28c/0x5c0
> [    6.289554] sp : ffff800082b0b9e0
> [    6.292864] x29: ffff800082b0ba50 x28: 0000000000000000 x27: 0000000000000007
> [    6.300004] x26: ffff0001070ca000 x25: ffff800081a629d0 x24: 0000000000000000
> [    6.307144] x23: 0000000000000000 x22: ffff000bf1b50990 x21: ffff0001087eb448
> [    6.314284] x20: ffff000102ba7100 x19: ffff0001087e9680 x18: 00000000fffffffc
> [    6.321423] x17: 00000000dcdffe27 x16: 00000000988f8d04 x15: 0000000000000010
> [    6.328562] x14: 0000000000000000 x13: 0000000000000001 x12: 0000000000000020
> [    6.335701] x11: 00000000ffffffff x10: ffff0001087eb44e x9 : ffff800080dfeab4
> [    6.342841] x8 : ffff0001087eda80 x7 : 0000000000000000 x6 : 0000000000000000
> [    6.349980] x5 : 00000000ffffffff x4 : 0000000000000002 x3 : ffff800082b0ba30
> [    6.357119] x2 : ffff800081969fc8 x1 : ffff000100c99400 x0 : 0000000000000000
> [    6.364258] Call trace:
> [    6.366699]  of_pci_add_properties+0x2a8/0x5c0 (P)
> [    6.371490]  of_pci_make_dev_node+0xd8/0x168
> [    6.375759]  pci_bus_add_device+0x130/0x180
> [    6.379941]  pci_bus_add_devices+0x48/0xa0
> [    6.384035]  pci_host_probe+0x94/0x100
> [    6.387781]  pci_host_common_init+0x88/0xb0
> [    6.391962]  pci_host_common_probe+0x34/0x60
> [    6.396230]  platform_probe+0x64/0xc0
> [    6.399892]  really_probe+0xc8/0x3a0
> [    6.403465]  __driver_probe_device+0x84/0x160
> [    6.407820]  driver_probe_device+0x48/0x130
> [    6.412000]  __driver_attach+0xd0/0x1f8
> [    6.415834]  bus_for_each_dev+0x84/0x100
> [    6.419755]  driver_attach+0x2c/0x40
> [    6.423327]  bus_add_driver+0x118/0x240
> [    6.427160]  driver_register+0x70/0x138
> [    6.430994]  __platform_driver_register+0x28/0x40
> [    6.435696]  gen_pci_driver_init+0x24/0x38
> [    6.439791]  do_one_initcall+0x5c/0x2e0
> [    6.443626]  kernel_init_freeable+0x2c0/0x340
> [    6.447980]  kernel_init+0x28/0x160
> [    6.451467]  ret_from_fork+0x10/0x20
> [    6.455043] Code: 910143e3 d2800044 f0007cc2 913f2042 (f9404001)
> [    6.461133] ---[ end trace 0000000000000000 ]---
> [    6.465828] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
> [    6.473483] SMP: stopping secondary CPUs
> [    6.477411] Kernel Offset: disabled
> [    6.480894] CPU features: 0x000080,00026800,48046201,04017203
> [    6.486636] Memory Limit: none
> [    6.489687] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b ]---

I didn't look into the details yet, but Salvatore found this to be
similar to
https://lore.kernel.org/all/wnrtofgggs5d7y42ps4ujp3h54nuiszfkmoor6hdz2vlpbvkys@d4nre55j6nam/#t.

Does this problem happen for you on each boot?

Best regards
Uwe

[toc] | [next] | [standalone]

#90968

hi,

On 1/25/26 23:50, Uwe Kleine-K  nig wrote:
>>     * What led up to the situation?
>> upgrade to linux-image-arm64 which is 6.18.5 at the time of writing
> 
> Did you update from 6.18.3-1? Or something earlier?
> 

i rarely turn that box on, the one before 6.18 was 6.17.9 and that 
worked....

>> [    6.486636] Memory Limit: none
>> [    6.489687] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b ]---
> 
> I didn't look into the details yet, but Salvatore found this to be
> similar to
> https://lore.kernel.org/all/wnrtofgggs5d7y42ps4ujp3h54nuiszfkmoor6hdz2vlpbvkys@d4nre55j6nam/#t.
> 
nice find, the trace seems almost identical...

> Does this problem happen for you on each boot?
> 
yess i can say 100% happens on both of my 2 machines with this soc....

have a nice day,

csaba

[toc] | [prev] | [next] | [standalone]

#90973

[Multipart message — attachments visible in raw view] — view raw

Hello,

On Sun, Jan 25, 2026 at 11:57:54PM +0100, mc36 wrote:
> On 1/25/26 23:50, Uwe Kleine-K  nig wrote:
> > >     * What led up to the situation?
> > > upgrade to linux-image-arm64 which is 6.18.5 at the time of writing
> > 
> > Did you update from 6.18.3-1? Or something earlier?
> > 
> 
> i rarely turn that box on, the one before 6.18 was 6.17.9 and that
> worked....

I intend to look into the detail here later this week, but if you come
around to test the earlier 6.18.y kernels and report back which is the
first broken one that would help me to know where to look for the
regression.

Thanks for your feedback,
Uwe

[toc] | [prev] | [next] | [standalone]

#90974

hi,

On 1/26/26 07:31, Uwe Kleine-K  nig wrote:

>> i rarely turn that box on, the one before 6.18 was 6.17.9 and that
>> worked....
> 
> I intend to look into the detail here later this week, but if you come
> around to test the earlier 6.18.y kernels and report back which is the
> first broken one that would help me to know where to look for the
> regression.
> 

i'll try my best to bisect this at debian kernel version level, but 
don't have high hopes to do so at commit level; the device i have 
(asterfusion x312p with 2 dpu-s, and those latter are the aarch64s) 
revolves around the intel tofino asic and the two arm64 socs are just 
sidecars, moreover its a development box, and as such, to power cycle 
them needs about 10 minutes manual process from my side bring up all the 
stuff to have the arm64s some networking again... it also adds to the 
mix that the 6.17 had about 50% chance of not booting up and getting to 
the (initramfs) because the kernel failed to bring up the emmc.... and 
if it even booted up, had tons of complains about the nics, which, 
later, i use with dpdk, thats the reason i did not bugged about this 
before....

tldr; i'll get back to you with the latest known working kernel version 
if i find some spare hours, or n/a if i've given up in the middle of the 
process...:)

all the best,

csaba

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web