macOS Sequoia – Kernel Panic: fq_codel / classq assertion on AMD (Realtek + Intel Wi-Fi + even without network kexts)

rezenderaul

New member
AMD OS X Member
Nov 30, 2025
2
1
3
CPU:
5600g

Hardware


  • CPU: Ryzen 5 5600g
  • GPU: APU Vega 7
  • Motherboard: Asus As520m-e
  • RAM: 32gb
  • Storage: SSD 500gb
  • Ethernet: Realtek RTL8111 (onboard)
  • Wi-Fi: Intel AC 7260 using itlwm


System Information


  • OpenCore: 1.0.6
  • macOS: Sequoia 15.1 (Build 25B78)
  • SMBIOS: MacPro7,1


Problem Description


I am getting repeated kernel panics on macOS Sequoia related to the network packet scheduler fq_codel:


At first I thought it was caused by RealtekRTL8111, so I removed it — but the panic still occurs, now referencing itlwm.
If I disable both network drivers, the panic still eventually happens, but references IONetworkingFamily only.


This strongly suggests a deeper incompatibility between:


  • AMD kernel patches
  • IONetworkingFamily 3.4 (Sequoia)
  • fq_codel queue discipline
  • Possibly timing/TSC issues unique to AMD

The problem happens even when no network traffic is occurring.




Kernel Panic Logs


Here is one example affecting RealtekRTL8111:
panic(cpu 6 caller 0xffffff800e5961cc): assertion failed: now >= *pkt_enq_time
...
Kernel Extensions in backtrace:
com.insanelymac.RealtekRTL8111 (2.4.2)
dependency: com.apple.iokit.IONetworkingFamily (3.4)

And here is another affecting itlwm:
panic(cpu 2 caller 0xffffff800df961cc): assertion failed: now >= *pkt_enq_time
...
Kernel Extensions in backtrace:
com.zxystd.itlwm (2.3)
dependency: com.apple.iokit.IONetworkingFamily (3.4)



Even with both drivers removed, a similar panic occurs referencing only:


IONetworkingFamily -> fq_codel -> panic


What I Have Tried So Far


Network


✔ RealtekRTL8111 v2.5.0 → panic
✔ RealtekRTL8111 v2.4.2 → panic
✔ itlwm 2.3 → panic
✔ Booting without Ethernet cable → panic
✔ Booting without Wi-Fi card connected → panic
✔ Removing all network kexts entirely → still panic




OpenCore / Kernel


✔ DisableIoMapper = true → no change
✔ DisableIoMapperMapping = true → no change
✔ Different boot-args (debug=0x100 -v keepsyms=1, tried without them)
✔ Checked all AMD patches (all from OC 1.0.6 sample)
✔ Rebuilt entire EFI




Observations


  • Panic always comes from fq_codel inside XNU networking stack.
  • This started only on Sequoia (Sonoma did not have this issue).
  • AMD timers or TSC synchronization may be interacting poorly with new networking scheduler.
  • Seems related to packet timestamps going backwards, which triggers the assertion.



EFI and Logs


Here is my full EFI (serials removed):


Full panic logs (multiple examples):
panic(cpu 0 caller 0xffffff801e3961cc): assertion failed: now >= *pkt_enq_time, file: /AppleInternal/Library/BuildRoots/4~CAeTugBviNP9M9Rx6fkigsQdAzLeEabN7n9UjXU/Library/Caches/com.apple.xbs/Sources/xnu/bsd/net/classq/classq_fq_codel.c, line: 1130 @uipc_socket.c:8238

Panicked task 0xffffff8b9c3aed38: 248 threads: pid 0: kernel_task

Backtrace (CPU 0), panicked thread: 0xffffff9a0255fb30, Frame : Return Address

0xffffffb2da4b3220 : 0xffffff801db574d1 mach_kernel : _handle_debugger_trap + 0x431

0xffffffb2da4b3270 : 0xffffff801dcd3ac6 mach_kernel : _kdp_i386_trap + 0x126

0xffffffb2da4b32b0 : 0xffffff801dcc2ccc mach_kernel : _kernel_trap + 0x75c

0xffffffb2da4b3370 : 0xffffff801daeb971 mach_kernel : _return_from_trap + 0xc1

0xffffffb2da4b3390 : 0xffffff801db578a7 mach_kernel : _DebuggerTrapWithState + 0x67

0xffffffb2da4b3490 : 0xffffff801db56f19 mach_kernel : _panic_trap_to_debugger + 0x269

0xffffffb2da4b3600 : 0xffffff801e38b47d mach_kernel : _panic + 0x81

0xffffffb2da4b36f0 : 0xffffff801e3961cc mach_kernel : _panic_machine_check64 + 0xc78

0xffffffb2da4b3700 : 0xffffff801def9ff7 mach_kernel : _fq_codel_dq + 0x987

0xffffffb2da4b3720 : 0xffffff801def985a mach_kernel : _fq_codel_dq + 0x1ea

0xffffffb2da4b3790 : 0xffffff801deff2c4 mach_kernel : _fq_if_flow_feedback + 0x16e4

0xffffffb2da4b3820 : 0xffffff801defeb70 mach_kernel : _fq_if_flow_feedback + 0xf90

0xffffffb2da4b3910 : 0xffffff801defe2b0 mach_kernel : _fq_if_flow_feedback + 0x6d0

0xffffffb2da4b3a60 : 0xffffff801defb6da mach_kernel : _fq_if_dequeue + 0x2a

0xffffffb2da4b3a90 : 0xffffff801def6ffd mach_kernel : _ifclassq_dequeue + 0x38d

0xffffffb2da4b3b20 : 0xffffff801def6cea mach_kernel : _ifclassq_dequeue + 0x7a

0xffffffb2da4b3b90 : 0xffffff801ddd2de5 mach_kernel : _ifnet_dequeue + 0x105

0xffffffb2da4b3bf0 : 0xffffff801fe4583e com.apple.iokit.IONetworkingFamily : __ZN18IONetworkInterface20dequeueOutputPacketsEjPP6__mbufS2_PjPy + 0x7c

0xffffffb2da4b3c30 : 0xffffff8023621d0a com.insanelymac.RealtekRTL8111 : __ZN7RTL811111outputStartEP18IONetworkInterfacej + 0x9c

0xffffffb2da4b3f30 : 0xffffff801fe451f7 com.apple.iokit.IONetworkingFamily : __ZN18IONetworkInterface16drainOutputQueueEP7__ifnetP19IONetworkController + 0x5f

0xffffffb2da4b3f70 : 0xffffff801ddd7630 mach_kernel : _ifnet_attach + 0x2420

0xffffffb2da4b3fa0 : 0xffffff801daeb19e mach_kernel : _call_continuation + 0x2e

Kernel Extensions in backtrace:

com.apple.iokit.IONetworkingFamily(3.4)[3927A1C1-FAF2-3622-A5AD-E60D64F4FC66]@0xffffff801fe37000->0xffffff801fe4cfff

com.insanelymac.RealtekRTL8111(2.4.2)[7A4AD8D5-E6C5-3337-BF24-B570982B5D22]@0xffffff80235af000->0xffffff802362ffff

dependency: com.apple.iokit.IONetworkingFamily(3.4)[3927A1C1-FAF2-3622-A5AD-E60D64F4FC66]@0xffffff801fe37000->0xffffff801fe4cfff

dependency: com.apple.iokit.IOPCIFamily(2.9)[14BB2FB5-CB12-3113-803E-F14CEF7565DC]@0xffffff80200e7000->0xffffff8020139fff



Process name corresponding to current thread (0xffffff9a0255fb30): kernel_task

Boot args: -v keepsyms=1 debug=0x100



Mac OS version:

25B78



Kernel version:

Darwin Kernel Version 25.1.0: Mon Oct 20 19:26:51 PDT 2025; root:xnu-12377.41.6~2/RELEASE_X86_64

Kernel UUID: 375EF211-CCBA-3A63-9670-924A3BF74221

roots installed: 0

KernelCache slide: 0x000000001d800000

KernelCache base:    0xffffff801da00000

Kernel slide:            0x000000001d8e8000

Kernel text base:    0xffffff801dae8000

__HIB    text base: 0xffffff801d900000

System model name: MacPro7,1 (Mac-27AD2F918AE68F61)

System shutdown begun: NO

Panic diags file available: YES (0x0)

Hibernation exit count: 0



System uptime in nanoseconds: 237487404180

Last Sleep:                      absolute                      base_tsc                    base_nano

Uptime    : 0x000000374b5a375b

Sleep      : 0x0000000000000000 0x0000000000000000 0x0000000000000000

Wake        : 0x0000000000000000 0x0000001363c00860 0x0000000000000000

Compressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space

Zone info:

Zone map: 0xffffff80690db000 - 0xffffffa0690db000

. VM        : 0xffffff80690db000 - 0xffffff8535da7000

. RO        : 0xffffff8535da7000 - 0xffffff86cf74b000

. GEN0    : 0xffffff86cf74b000 - 0xffffff8b9c417000

. GEN1    : 0xffffff8b9c417000 - 0xffffff90690e3000

. GEN2    : 0xffffff90690e3000 - 0xffffff9535daf000

. GEN3    : 0xffffff9535daf000 - 0xffffff9a02a7b000

. DATA    : 0xffffff9a02a7b000 - 0xffffffa0690db000

Metadata: 0xffffffa06b8a3000 - 0xffffffa08b8a3000

Bitmaps : 0xffffffa08b8a3000 - 0xffffffa0918a3000

Extra      : 0 - 0




panic(cpu 2 caller 0xffffff800df961cc): assertion failed: now >= *pkt_enq_time, file: /AppleInternal/Library/BuildRoots/4~CAeTugBviNP9M9Rx6fkigsQdAzLeEabN7n9UjXU/Library/Caches/com.apple.xbs/Sources/xnu/bsd/net/classq/classq_fq_codel.c, line: 1130 @uipc_socket.c:8238

Panicked task 0xffffff8b6c02e7e8: 243 threads: pid 0: kernel_task

Backtrace (CPU 2), panicked thread: 0xffffff8b6cbad598, Frame : Return Address

0xffffffe9c102f4c0 : 0xffffff800d7574d1 mach_kernel : _handle_debugger_trap + 0x431

0xffffffe9c102f510 : 0xffffff800d8d3ac6 mach_kernel : _kdp_i386_trap + 0x126

0xffffffe9c102f550 : 0xffffff800d8c2ccc mach_kernel : _kernel_trap + 0x75c

0xffffffe9c102f610 : 0xffffff800d6eb971 mach_kernel : _return_from_trap + 0xc1

0xffffffe9c102f630 : 0xffffff800d7578a7 mach_kernel : _DebuggerTrapWithState + 0x67

0xffffffe9c102f730 : 0xffffff800d756f19 mach_kernel : _panic_trap_to_debugger + 0x269

0xffffffe9c102f8a0 : 0xffffff800df8b47d mach_kernel : _panic + 0x81

0xffffffe9c102f990 : 0xffffff800df961cc mach_kernel : _panic_machine_check64 + 0xc78

0xffffffe9c102f9a0 : 0xffffff800daf9ff7 mach_kernel : _fq_codel_dq + 0x987

0xffffffe9c102f9c0 : 0xffffff800daf985a mach_kernel : _fq_codel_dq + 0x1ea

0xffffffe9c102fa30 : 0xffffff800daff2c4 mach_kernel : _fq_if_flow_feedback + 0x16e4

0xffffffe9c102fac0 : 0xffffff800dafed26 mach_kernel : _fq_if_flow_feedback + 0x1146

0xffffffe9c102fbb0 : 0xffffff800dafe2b0 mach_kernel : _fq_if_flow_feedback + 0x6d0

0xffffffe9c102fd00 : 0xffffff800dafb6da mach_kernel : _fq_if_dequeue + 0x2a

0xffffffe9c102fd30 : 0xffffff800daf6ffd mach_kernel : _ifclassq_dequeue + 0x38d

0xffffffe9c102fdc0 : 0xffffff800daf6cea mach_kernel : _ifclassq_dequeue + 0x7a

0xffffffe9c102fe30 : 0xffffff800d9d2de5 mach_kernel : _ifnet_dequeue + 0x105

0xffffffe9c102fe90 : 0xffffff800fa4583e com.apple.iokit.IONetworkingFamily : __ZN18IONetworkInterface20dequeueOutputPacketsEjPP6__mbufS2_PjPy + 0x7c

0xffffffe9c102fed0 : 0xffffff8011fd4caa com.zxystd.itlwm : __ZN5itlwm11outputStartEP18IONetworkInterfacej + 0x9a

0xffffffe9c102ff30 : 0xffffff800fa451f7 com.apple.iokit.IONetworkingFamily : __ZN18IONetworkInterface16drainOutputQueueEP7__ifnetP19IONetworkController + 0x5f

0xffffffe9c102ff70 : 0xffffff800d9d7630 mach_kernel : _ifnet_attach + 0x2420

0xffffffe9c102ffa0 : 0xffffff800d6eb19e mach_kernel : _call_continuation + 0x2e

Kernel Extensions in backtrace:

com.apple.iokit.IONetworkingFamily(3.4)[3927A1C1-FAF2-3622-A5AD-E60D64F4FC66]@0xffffff800fa37000->0xffffff800fa4cfff

com.zxystd.itlwm(2.3)[681F902C-67C5-3C40-965D-E4553C6A962B]@0xffffff8011f80000->0xffffff8012efbfff

dependency: com.apple.iokit.IONetworkingFamily(3.4)[3927A1C1-FAF2-3622-A5AD-E60D64F4FC66]@0xffffff800fa37000->0xffffff800fa4cfff

dependency: com.apple.iokit.IOPCIFamily(2.9)[14BB2FB5-CB12-3113-803E-F14CEF7565DC]@0xffffff800fce7000->0xffffff800fd39fff



Process name corresponding to current thread (0xffffff8b6cbad598): kernel_task

Boot args: -v keepsyms=1 debug=0x100



Mac OS version:

25B78



Kernel version:

Darwin Kernel Version 25.1.0: Mon Oct 20 19:26:51 PDT 2025; root:xnu-12377.41.6~2/RELEASE_X86_64

Kernel UUID: 375EF211-CCBA-3A63-9670-924A3BF74221

roots installed: 0

KernelCache slide: 0x000000000d400000

KernelCache base:    0xffffff800d600000

Kernel slide:            0x000000000d4e8000

Kernel text base:    0xffffff800d6e8000

__HIB    text base: 0xffffff800d500000

System model name: MacPro7,1 (Mac-27AD2F918AE68F61)

System shutdown begun: NO

Panic diags file available: YES (0x0)

Hibernation exit count: 0



System uptime in nanoseconds: 242612493226

Last Sleep:                      absolute                      base_tsc                    base_nano

Uptime    : 0x000000387cd4de8f

Sleep      : 0x0000000000000000 0x0000000000000000 0x0000000000000000

Wake        : 0x0000000000000000 0x0000000dbd6b185d 0x0000000000000000

Compressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space

Zone info:

Zone map: 0xffffff8038d44000 - 0xffffffa038d44000

. VM        : 0xffffff8038d44000 - 0xffffff8505a10000

. RO        : 0xffffff8505a10000 - 0xffffff869f3b4000

. GEN0    : 0xffffff869f3b4000 - 0xffffff8b6c080000

. GEN1    : 0xffffff8b6c080000 - 0xffffff9038d4c000

. GEN2    : 0xffffff9038d4c000 - 0xffffff9505a18000

. GEN3    : 0xffffff9505a18000 - 0xffffff99d26e4000

. DATA    : 0xffffff99d26e4000 - 0xffffffa038d44000

Metadata: 0xffffffedc0325000 - 0xffffffede0325000

Bitmaps : 0xffffffede0325000 - 0xffffffede6325000

Extra      : 0 - 0


Questions for the community / AMD devs


  1. Is this a known issue with AMD on macOS Sequoia’s new networking stack?
  2. Is there any updated AMD patchset needed for XNU 25.x (Sequoia)?
  3. Is fq_codel incompatible with AMD timing/TSC on this macOS version?
  4. Should I downgrade to macOS Sonoma for now?
  5. Is there any workaround (boot-args, disabling fq_codel, IONetworkingFamily rollback, TSC adjustments, etc.)?



Additional Information


  • BIOS settings: Above 4G Disabled/Enabled tested, CSM disabled, VT-d off, IOMMU off
  • All ACPI tables extracted with SSDTTime
  • No overclock, PBO disabled
  • System is otherwise stable (GPU/CPU load) — panics only relate to network scheduling



Conclusion


The issue appears to be a Sequoia + AMD + networking regression, since ALL network drivers (Realtek, Intel, even none) eventually hit the same assertion in fq_codel.


Any help, patch guidance, or known workarounds would be greatly appreciated.


Thank you!
 

Attachments

  • Captura de Tela 2025-11-30 às 12.43.55.png
    Captura de Tela 2025-11-30 às 12.43.55.png
    79.1 KB · Views: 6
Solution
  1. Is this a known issue with AMD on macOS Sequoia’s new networking stack?
  2. Is there any updated AMD patchset needed for XNU 25.x (Sequoia)?
  3. Is fq_codel incompatible with AMD timing/TSC on this macOS version?
  4. Should I downgrade to macOS Sonoma for now?
  5. Is there any workaround (boot-args, disabling fq_codel, IONetworkingFamily rollback, TSC adjustments, etc.)?
  1. No, this is not a known or widely reported issue. Sequoia is fairly mature as far as AMD Hacks go.
  2. There is an updated set of AMD Kernel Patches for Tahoe.
    1. The patches for Sequoia have not been updated or changed since the end of 2024.
  3. Sequoia is not known to be incompatible with AMD TSC sync...
  1. Is this a known issue with AMD on macOS Sequoia’s new networking stack?
  2. Is there any updated AMD patchset needed for XNU 25.x (Sequoia)?
  3. Is fq_codel incompatible with AMD timing/TSC on this macOS version?
  4. Should I downgrade to macOS Sonoma for now?
  5. Is there any workaround (boot-args, disabling fq_codel, IONetworkingFamily rollback, TSC adjustments, etc.)?
  1. No, this is not a known or widely reported issue. Sequoia is fairly mature as far as AMD Hacks go.
  2. There is an updated set of AMD Kernel Patches for Tahoe.
    1. The patches for Sequoia have not been updated or changed since the end of 2024.
  3. Sequoia is not known to be incompatible with AMD TSC sync. Have you tried using ForgedInvariant.kext?
    1. https://github.com/ChefKissInc/ForgedInvariant
  4. Yes, installing Sonoma seems to be the logical option given your issues with Sequoia.
  5. Not that I have seen or read about.
I am not on a computer at the moment so can’t download your EFI folder, I will do so tomorrow (Monday) and report back if anything jumps out as being a problem with your OC setup.
 
Solution
Just wanted to give some feedback — the kext seems to be working perfectly on my system. I’ve been running a continuous streaming test for over an hour now and haven’t had a single kernel panic. Everything is stable so far.

Thanks again for the work on this!
 
  • Like
Reactions: Edhawk
  AdBlock Detected
Sure, ad-blocking software does a great job at blocking ads, but it also blocks some useful and important features of our website. For the best possible site experience please take a moment to disable your AdBlocker.