iwm: unhandled firmware response

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

iwm: unhandled firmware response

Jake Champlin
Hello bugs@!

With 6.5-current, seeing a lot of unhandled firmware responses that are filling
up the kernel message buffer. I've only been able to reproduce these errors
_after_ the system comes back from a low power state. However, this could also
be a red herring, I'm not sure.
There haven't been any recent commits to if_iwm.c in-between the errors occuring
either.

Thanks!

dmesg is after the following error messages:

Apr 25 17:23:10 openx apmd: battery status: high. external power status: not connected. estimated battery life 70% (77 minutes)
Apr 25 17:34:10 openx apmd: battery status: high. external power status: not connected. estimated battery life 60% (65 minutes)
Apr 25 17:45:50 openx apmd: battery status: low. external power status: not connected. estimated battery life 50% (55 minutes)
Apr 25 17:58:30 openx apmd: battery status: low. external power status: not connected. estimated battery life 40% (46 minutes)
Apr 25 18:11:00 openx apmd: battery status: low. external power status: not connected. estimated battery life 30% (40 minutes)
Apr 25 18:17:00 openx apmd: battery status: CRITICAL. external power status: not connected. estimated battery life 25% (24 minutes)
Apr 25 18:19:12 openx apmd: battery status: CRITICAL. external power status: connected. estimated battery life 23%
Apr 25 18:31:30 openx apmd: battery status: low. external power status: connected. estimated battery life 26%
Apr 25 18:57:23 openx /bsd: iwm0: unhandled firmware response 0x6/0x22909826 rx ring 85[74]
Apr 25 18:57:23 openx /bsd: iwm0: unhandled firmware response 0xb4/0x2290fdd4 rx ring 85[75]
Apr 25 18:57:23 openx /bsd: iwm0: unhandled firmware response 0x4a/0x2290fe6a rx ring 85[75]
Apr 25 18:57:23 openx /bsd: iwm0: unhandled firmware response 0x7c/0x304288 rx ring 75[203]
Apr 25 18:57:23 openx /bsd: iwm0: unhandled firmware response 0x9d/0x22910fbd rx ring 85[75]
Apr 25 18:57:23 openx /bsd: iwm0: unhandled firmware response 0x55/0x1d510c9 rx ring 1[172]
Apr 25 18:57:23 openx /bsd: iwm0: unhandled firmware response 0x7/0x2294dd27 rx ring 85[79]
Apr 25 18:57:23 openx /bsd: iwm0: unhandled firmware response 0x7d/0x1d51112 rx ring 1[172]
Apr 25 18:57:23 openx /bsd: iwm0: unhandled firmware response 0xff/0x80 rx ring 127[255]
Apr 25 18:57:23 openx /bsd: iwm0: unhandled firmware response 0xf6/0x22980816 rx ring 85[82]
Apr 25 18:57:23 openx /bsd: iwm0: unhandled firmware response 0x33/0x6208 rx ring 0[0]
Apr 25 18:57:23 openx /bsd: iwm0: unhandled firmware response 0x8d/0x229819ad rx ring 85[82]
Apr 25 18:57:23 openx /bsd: iwm0: unhandled firmware response 0x9a/0x22981dba rx ring 85[82]
Apr 25 18:57:24 openx /bsd: iwm0: unhandled firmware response 0x64/0x229b1d84 rx ring 85[85]
Apr 25 18:57:24 openx /bsd: iwm0: unhandled firmware response 0xff/0x80 rx ring 127[255]
Apr 25 18:57:24 openx /bsd: iwm0: unhandled firmware response 0xa/0x229e3d29 rx ring 85[88]
Apr 25 18:57:24 openx /bsd: iwm0: unhandled firmware response 0xff/0x80 rx ring 127[255]
Apr 25 18:57:24 openx /bsd: iwm0: unhandled firmware response 0xfb/0x1d511dd rx ring 1[172]
Apr 25 18:57:24 openx /bsd: iwm0: unhandled firmware response 0xe4/0x229e4804 rx ring 85[88]
Apr 25 18:57:24 openx /bsd: iwm0: unhandled firmware response 0x33/0x6208 rx ring 0[0]
Apr 25 18:57:24 openx /bsd: iwm0: unhandled firmware response 0xd4/0x229e4cf4 rx ring 85[88]
Apr 25 18:57:24 openx /bsd: iwm0: unhandled firmware response 0x33/0x6208 rx ring 0[0]
Apr 25 18:57:24 openx /bsd: iwm0: unhandled firmware response 0xfc/0x229e521c rx ring 85[88]
Apr 25 18:57:24 openx /bsd: iwm0: unhandled firmware response 0x33/0x6208 rx ring 0[0]
Apr 25 18:57:24 openx /bsd: iwm0: unhandled firmware response 0x54/0x229e5774 rx ring 85[88]
Apr 25 18:57:24 openx /bsd: iwm0: unhandled firmware response 0x33/0x6208 rx ring 0[0]
Apr 25 18:57:24 openx /bsd: iwm0: unhandled firmware response 0xf1/0x229e5d11 rx ring 85[88]
Apr 25 18:57:24 openx /bsd: iwm0: unhandled firmware response 0x33/0x6208 rx ring 0[0]
Apr 25 18:57:24 openx /bsd: iwm0: unhandled firmware response 0xff/0x6208 rx ring 127[255]
Apr 25 18:57:24 openx /bsd: iwm0: unhandled firmware response 0x7b/0x229e6f9b rx ring 85[88]
Apr 25 18:57:24 openx /bsd: iwm0: unhandled firmware response 0x1f/0x229e743f rx ring 85[88]
Apr 25 18:57:24 openx /bsd: iwm0: unhandled firmware response 0xfc/0x229e781c rx ring 85[88]
Apr 25 18:57:24 openx /bsd: iwm0: unhandled firmware response 0x33/0x6208 rx ring 0[0]
Apr 25 18:57:24 openx /bsd: iwm0: unhandled firmware response 0xce/0x229e88ee rx ring 85[88]
Apr 25 18:57:24 openx /bsd: iwm0: unhandled firmware response 0x33/0x6208 rx ring 0[0]
Apr 25 18:57:24 openx /bsd: iwm0: unhandled firmware response 0xd5/0x229e91f5 rx ring 85[88]
Apr 25 18:57:24 openx /bsd: iwm0: unhandled firmware response 0xff/0x6208 rx ring 127[255]
Apr 25 18:57:24 openx /bsd: iwm0: unhandled firmware response 0x33/0x4208 rx ring 0[0]
Apr 25 18:57:24 openx /bsd: iwm0: unhandled firmware response 0x49/0x22a15d69 rx ring 85[91]
Apr 25 18:57:24 openx /bsd: iwm0: unhandled firmware response 0x51/0x1d51248 rx ring 1[172]
Apr 25 18:57:24 openx /bsd: iwm0: unhandled firmware response 0x41/0x22a47d61 rx ring 85[94]
Apr 25 18:57:24 openx /bsd: iwm0: unhandled firmware response 0x91/0x1d512b4 rx ring 1[172]
Apr 25 18:57:24 openx /bsd: iwm0: unhandled firmware response 0x33/0x6208 rx ring 0[0]
Apr 25 18:57:24 openx /bsd: iwm0: unhandled firmware response 0xe0/0x22a48cff rx ring 85[94]
Apr 25 18:57:24 openx /bsd: iwm0: unhandled firmware response 0xbb/0x22a490da rx ring 85[94]
Apr 25 18:57:24 openx /bsd: iwm0: unhandled firmware response 0x85/0x22a495a4 rx ring 85[94]
Apr 25 18:57:24 openx /bsd: iwm0: unhandled firmware response 0xff/0x6208 rx ring 127[255]
Apr 25 18:57:24 openx /bsd: iwm0: unhandled firmware response 0x33/0x6208 rx ring 0[0]
Apr 25 18:57:24 openx /bsd: iwm0: unhandled firmware response 0x10/0x22a4a22f rx ring 85[94]
Apr 25 18:57:24 openx /bsd: iwm0: unhandled firmware response 0xeb/0x22a4a60a rx ring 85[94]
Apr 25 18:57:24 openx /bsd: iwm0: unhandled firmware response 0x33/0x6208 rx ring 0[0]
Apr 25 18:57:24 openx last message repeated 3 times


dmesg:
Apr 26 09:19:26 openx /bsd: OpenBSD 6.5-current (GENERIC.MP) #23: Tue Apr 23 18:58:50 MDT 2019
Apr 26 09:19:26 openx /bsd:     [hidden email]:/usr/src/sys/arch/amd64/compile/GENERIC.MP
Apr 26 09:19:26 openx /bsd: real mem = 8302006272 (7917MB)
Apr 26 09:19:26 openx /bsd: avail mem = 8040357888 (7667MB)
Apr 26 09:19:26 openx /bsd: mpath0 at root
Apr 26 09:19:26 openx /bsd: scsibus0 at mpath0: 256 targets
Apr 26 09:19:26 openx /bsd: mainbus0 at root
Apr 26 09:19:26 openx /bsd: bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x7f114000 (64 entries)
Apr 26 09:19:26 openx /bsd: bios0: vendor HUAWEI version "1.03" date 05/19/2017
Apr 26 09:19:26 openx /bsd: bios0: HUAWEI HUAWEI MateBook X
Apr 26 09:19:26 openx /bsd: acpi0 at bios0: rev 2
Apr 26 09:19:26 openx /bsd: acpi0: sleep states S0 S3 S4 S5
Apr 26 09:19:26 openx /bsd: acpi0: tables DSDT FACP UEFI UEFI ECDT SSDT MSDM SSDT SSDT SSDT ASPT BOOT HPET APIC MCFG SSDT WSMT SSDT DBGP DBG2 SSDT SSDT DMAR NHLT FPDT BGRT
Apr 26 09:19:26 openx /bsd: acpi0: wakeup devices GLAN(S4) XHC_(S3) XDCI(S4) HDAS(S4) PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) RP05(S4) PXSX(S4) RP06(S4) [...]
Apr 26 09:19:26 openx /bsd: acpitimer0 at acpi0: 3579545 Hz, 24 bits
Apr 26 09:19:26 openx /bsd: acpiec0 at acpi0
Apr 26 09:19:26 openx /bsd: acpihpet0 at acpi0: 23999999 Hz
Apr 26 09:19:26 openx /bsd: acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat
Apr 26 09:19:26 openx /bsd: cpu0 at mainbus0: apid 0 (boot processor)
Apr 26 09:19:26 openx /bsd: cpu0: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz, 2395.41 MHz, 06-8e-09
Apr 26 09:19:26 openx /bsd: cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
Apr 26 09:19:26 openx /bsd: cpu0: 256KB 64b/line 8-way L2 cache
Apr 26 09:19:26 openx /bsd: cpu0: smt 0, core 0, package 0
Apr 26 09:19:26 openx /bsd: mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
Apr 26 09:19:26 openx /bsd: cpu0: apic clock running at 23MHz
Apr 26 09:19:26 openx /bsd: cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE
Apr 26 09:19:26 openx /bsd: cpu1 at mainbus0: apid 2 (application processor)
Apr 26 09:19:26 openx /bsd: cpu1: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz, 2394.40 MHz, 06-8e-09
Apr 26 09:19:26 openx /bsd: cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
Apr 26 09:19:26 openx /bsd: cpu1: 256KB 64b/line 8-way L2 cache
Apr 26 09:19:26 openx /bsd: cpu1: smt 0, core 1, package 0
Apr 26 09:19:26 openx /bsd: cpu2 at mainbus0: apid 1 (application processor)
Apr 26 09:19:26 openx /bsd: cpu2: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz, 2394.40 MHz, 06-8e-09
Apr 26 09:19:26 openx /bsd: cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
Apr 26 09:19:26 openx /bsd: cpu2: 256KB 64b/line 8-way L2 cache
Apr 26 09:19:26 openx /bsd: cpu2: smt 1, core 0, package 0
Apr 26 09:19:26 openx /bsd: cpu3 at mainbus0: apid 3 (application processor)
Apr 26 09:19:26 openx /bsd: cpu3: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz, 2394.40 MHz, 06-8e-09
Apr 26 09:19:26 openx /bsd: cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
Apr 26 09:19:26 openx /bsd: cpu3: 256KB 64b/line 8-way L2 cache
Apr 26 09:19:26 openx /bsd: cpu3: smt 1, core 1, package 0
Apr 26 09:19:26 openx /bsd: ioapic0 at mainbus0: apid 2 pa 0xfec00000, version 20, 120 pins
Apr 26 09:19:26 openx /bsd: acpimcfg0 at acpi0
Apr 26 09:19:26 openx /bsd: acpimcfg0: addr 0xe0000000, bus 0-255
Apr 26 09:19:26 openx /bsd: acpiprt0 at acpi0: bus 0 (PCI0)
Apr 26 09:19:26 openx /bsd: acpiprt1 at acpi0: bus -1 (RP01)
Apr 26 09:19:26 openx /bsd: acpiprt2 at acpi0: bus -1 (RP02)
Apr 26 09:19:26 openx /bsd: acpiprt3 at acpi0: bus -1 (RP03)
Apr 26 09:19:26 openx /bsd: acpiprt4 at acpi0: bus -1 (RP04)
Apr 26 09:19:26 openx /bsd: acpiprt5 at acpi0: bus -1 (RP05)
Apr 26 09:19:26 openx /bsd: acpiprt6 at acpi0: bus -1 (RP06)
Apr 26 09:19:26 openx /bsd: acpiprt7 at acpi0: bus 1 (RP07)
Apr 26 09:19:26 openx /bsd: acpiprt8 at acpi0: bus -1 (RP08)
Apr 26 09:19:26 openx /bsd: acpiprt9 at acpi0: bus 2 (RP09)
Apr 26 09:19:26 openx /bsd: acpiprt10 at acpi0: bus -1 (RP10)
Apr 26 09:19:26 openx /bsd: acpiprt11 at acpi0: bus -1 (RP11)
Apr 26 09:19:26 openx /bsd: acpiprt12 at acpi0: bus -1 (RP12)
Apr 26 09:19:26 openx /bsd: acpiprt13 at acpi0: bus -1 (RP13)
Apr 26 09:19:26 openx /bsd: acpiprt14 at acpi0: bus -1 (RP14)
Apr 26 09:19:26 openx /bsd: acpiprt15 at acpi0: bus -1 (RP15)
Apr 26 09:19:26 openx /bsd: acpiprt16 at acpi0: bus -1 (RP16)
Apr 26 09:19:26 openx /bsd: acpiprt17 at acpi0: bus -1 (RP17)
Apr 26 09:19:26 openx /bsd: acpiprt18 at acpi0: bus -1 (RP18)
Apr 26 09:19:26 openx /bsd: acpiprt19 at acpi0: bus -1 (RP19)
Apr 26 09:19:26 openx /bsd: acpiprt20 at acpi0: bus -1 (RP20)
Apr 26 09:19:26 openx /bsd: acpiprt21 at acpi0: bus -1 (RP21)
Apr 26 09:19:26 openx /bsd: acpiprt22 at acpi0: bus -1 (RP22)
Apr 26 09:19:26 openx /bsd: acpiprt23 at acpi0: bus -1 (RP23)
Apr 26 09:19:26 openx /bsd: acpiprt24 at acpi0: bus -1 (RP24)
Apr 26 09:19:26 openx /bsd: acpicpu0 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33), C1(1000@1 mwait.1), PSS
Apr 26 09:19:26 openx /bsd: acpicpu1 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33), C1(1000@1 mwait.1), PSS
Apr 26 09:19:26 openx /bsd: acpicpu2 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33), C1(1000@1 mwait.1), PSS
Apr 26 09:19:26 openx /bsd: acpicpu3 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33), C1(1000@1 mwait.1), PSS
Apr 26 09:19:26 openx /bsd: acpipwrres0 at acpi0: WRST
Apr 26 09:19:26 openx /bsd: acpipwrres1 at acpi0: WRST
Apr 26 09:19:26 openx /bsd: acpipwrres2 at acpi0: WRST
Apr 26 09:19:26 openx /bsd: acpipwrres3 at acpi0: WRST
Apr 26 09:19:26 openx /bsd: acpipwrres4 at acpi0: WRST
Apr 26 09:19:26 openx /bsd: acpipwrres5 at acpi0: WRST
Apr 26 09:19:26 openx /bsd: acpipwrres6 at acpi0: WRST
Apr 26 09:19:26 openx /bsd: acpipwrres7 at acpi0: WRST
Apr 26 09:19:26 openx /bsd: acpipwrres8 at acpi0: WRST
Apr 26 09:19:26 openx /bsd: acpipwrres9 at acpi0: WRST
Apr 26 09:19:26 openx /bsd: acpipwrres10 at acpi0: WRST
Apr 26 09:19:26 openx /bsd: acpipwrres11 at acpi0: WRST
Apr 26 09:19:26 openx /bsd: acpipwrres12 at acpi0: WRST
Apr 26 09:19:26 openx /bsd: acpipwrres13 at acpi0: WRST
Apr 26 09:19:26 openx /bsd: acpipwrres14 at acpi0: WRST
Apr 26 09:19:26 openx /bsd: acpipwrres15 at acpi0: WRST
Apr 26 09:19:26 openx /bsd: acpipwrres16 at acpi0: WRST
Apr 26 09:19:26 openx /bsd: acpipwrres17 at acpi0: WRST
Apr 26 09:19:26 openx /bsd: acpipwrres18 at acpi0: WRST
Apr 26 09:19:26 openx /bsd: acpipwrres19 at acpi0: WRST
Apr 26 09:19:26 openx /bsd: acpitz0 at acpi0: critical temperature is 98 degC
Apr 26 09:19:26 openx /bsd: acpipci0 at acpi0 PCI0: 0x00000000 0x00000011 0x00000001
Apr 26 09:19:26 openx /bsd: acpicmos0 at acpi0
Apr 26 09:19:26 openx /bsd: acpials0 at acpi0: ALSD
Apr 26 09:19:26 openx /bsd: "INT3403" at acpi0 not configured
Apr 26 09:19:26 openx last message repeated 4 times
Apr 26 09:19:26 openx /bsd: "INT344B" at acpi0 not configured
Apr 26 09:19:26 openx /bsd: "ELAN2201" at acpi0 not configured
Apr 26 09:19:26 openx /bsd: acpiac0 at acpi0: AC unit online
Apr 26 09:19:26 openx /bsd: acpibat0 at acpi0: BAT0 model "BASE-BAT" serial 123456789 type Li oem "Kollur"
Apr 26 09:19:26 openx /bsd: "INT0E0C" at acpi0 not configured
Apr 26 09:19:26 openx /bsd: "PNP0C14" at acpi0 not configured
Apr 26 09:19:26 openx /bsd: "INT33A1" at acpi0 not configured
Apr 26 09:19:26 openx /bsd: acpibtn0 at acpi0: LID_
Apr 26 09:19:26 openx /bsd: acpibtn1 at acpi0: PWRB
Apr 26 09:19:26 openx /bsd: "INT3400" at acpi0 not configured
Apr 26 09:19:26 openx /bsd: "PNP0C14" at acpi0 not configured
Apr 26 09:19:26 openx /bsd: "WDT0001" at acpi0 not configured
Apr 26 09:19:26 openx /bsd: "PNP0C14" at acpi0 not configured
Apr 26 09:19:26 openx /bsd: acpivideo0 at acpi0: GFX0
Apr 26 09:19:26 openx /bsd: acpivout0 at acpivideo0: DD1F
Apr 26 09:19:26 openx /bsd: cpu0: Enhanced SpeedStep 2395 MHz: speeds: 2601, 2600, 2500, 2400, 2200, 2000, 1900, 1700, 1500, 1400, 1200, 1100, 800, 700, 600, 400 MHz
Apr 26 09:19:26 openx /bsd: pci0 at mainbus0 bus 0
Apr 26 09:19:26 openx /bsd: pchb0 at pci0 dev 0 function 0 "Intel Core 7G Host" rev 0x02
Apr 26 09:19:26 openx /bsd: inteldrm0 at pci0 dev 2 function 0 "Intel HD Graphics 620" rev 0x02
Apr 26 09:19:26 openx /bsd: drm0 at inteldrm0
Apr 26 09:19:26 openx /bsd: inteldrm0: msi
Apr 26 09:19:26 openx /bsd: "Intel Core 6G Thermal" rev 0x02 at pci0 dev 4 function 0 not configured
Apr 26 09:19:26 openx /bsd: xhci0 at pci0 dev 20 function 0 "Intel 100 Series xHCI" rev 0x21: msi, xHCI 1.0
Apr 26 09:19:26 openx /bsd: usb0 at xhci0: USB revision 3.0
Apr 26 09:19:26 openx /bsd: uhub0 at usb0 configuration 1 interface 0 "Intel xHCI root hub" rev 3.00/1.00 addr 1
Apr 26 09:19:26 openx /bsd: pchtemp0 at pci0 dev 20 function 2 "Intel 100 Series Thermal" rev 0x21
Apr 26 09:19:26 openx /bsd: dwiic0 at pci0 dev 21 function 0 "Intel 100 Series I2C" rev 0x21: apic 2 int 16
Apr 26 09:19:26 openx /bsd: iic0 at dwiic0
Apr 26 09:19:26 openx /bsd: dwiic1 at pci0 dev 21 function 1 "Intel 100 Series I2C" rev 0x21: apic 2 int 17
Apr 26 09:19:26 openx /bsd: iic1 at dwiic1
Apr 26 09:19:26 openx /bsd: ihidev0 at iic1 addr 0x15 (polling), vendor 0x4f3 product 0x3056, ELAN2201
Apr 26 09:19:26 openx /bsd: ihidev0: 93 report ids
Apr 26 09:19:26 openx /bsd: imt0 at ihidev0: clickpad, 5 contacts
Apr 26 09:19:26 openx /bsd: wsmouse0 at imt0 mux 0
Apr 26 09:19:26 openx /bsd: "Intel 100 Series MEI" rev 0x21 at pci0 dev 22 function 0 not configured
Apr 26 09:19:26 openx /bsd: ppb0 at pci0 dev 28 function 0 "Intel 100 Series PCIE" rev 0xf1: msi
Apr 26 09:19:26 openx /bsd: pci1 at ppb0 bus 1
Apr 26 09:19:26 openx /bsd: nvme0 at pci1 dev 0 function 0 "Lite-On CB1 NVMe" rev 0x01: msi, NVMe 1.2
Apr 26 09:19:26 openx /bsd: nvme0: LITEON CB1-SD256, firmware C38640B, serial 002721101REP
Apr 26 09:19:26 openx /bsd: scsibus1 at nvme0: 1 targets
Apr 26 09:19:26 openx /bsd: sd0 at scsibus1 targ 0 lun 0: <NVMe, LITEON CB1-SD256, C386> SCSI4 0/direct fixed
Apr 26 09:19:26 openx /bsd: sd0: 244198MB, 512 bytes/sector, 500118192 sectors
Apr 26 09:19:26 openx /bsd: ppb1 at pci0 dev 29 function 0 "Intel 100 Series PCIE" rev 0xf1: msi
Apr 26 09:19:26 openx /bsd: pci2 at ppb1 bus 2
Apr 26 09:19:26 openx /bsd: iwm0 at pci2 dev 0 function 0 "Intel Dual Band Wireless-AC 8265" rev 0x78, msi
Apr 26 09:19:26 openx /bsd: "Intel 100 Series UART" rev 0x21 at pci0 dev 30 function 0 not configured
Apr 26 09:19:26 openx /bsd: "Intel 100 Series SPI" rev 0x21 at pci0 dev 30 function 3 not configured
Apr 26 09:19:26 openx /bsd: pcib0 at pci0 dev 31 function 0 "Intel 200 Series LPC" rev 0x21
Apr 26 09:19:26 openx /bsd: "Intel 100 Series PMC" rev 0x21 at pci0 dev 31 function 2 not configured
Apr 26 09:19:26 openx /bsd: azalia0 at pci0 dev 31 function 3 "Intel 200 Series HD Audio" rev 0x21: msi
Apr 26 09:19:26 openx /bsd: azalia0: codecs: Realtek ALC298, Intel/0x280b, using Realtek ALC298
Apr 26 09:19:26 openx /bsd: audio0 at azalia0
Apr 26 09:19:26 openx /bsd: ichiic0 at pci0 dev 31 function 4 "Intel 100 Series SMBus" rev 0x21: apic 2 int 16
Apr 26 09:19:26 openx /bsd: iic2 at ichiic0
Apr 26 09:19:26 openx /bsd: isa0 at pcib0
Apr 26 09:19:26 openx /bsd: isadma0 at isa0
Apr 26 09:19:26 openx /bsd: pckbc0 at isa0 port 0x60/5 irq 1 irq 12
Apr 26 09:19:26 openx /bsd: pckbd0 at pckbc0 (kbd slot)
Apr 26 09:19:26 openx /bsd: wskbd0 at pckbd0: console keyboard
Apr 26 09:19:26 openx /bsd: pcppi0 at isa0 port 0x61
Apr 26 09:19:26 openx /bsd: spkr0 at pcppi0
Apr 26 09:19:26 openx /bsd: vmm0 at mainbus0: VMX/EPT
Apr 26 09:19:26 openx /bsd: efifb at mainbus0 not configured
Apr 26 09:19:26 openx /bsd: vscsi0 at root
Apr 26 09:19:26 openx /bsd: scsibus2 at vscsi0: 256 targets
Apr 26 09:19:26 openx /bsd: softraid0 at root
Apr 26 09:19:26 openx /bsd: scsibus3 at softraid0: 256 targets
Apr 26 09:19:26 openx /bsd: root on sd0a (6510fc29d465de1e.a) swap on sd0b dump on sd0b
Apr 26 09:19:26 openx /bsd: WARNING: / was not properly unmounted
Apr 26 09:19:26 openx /bsd: inteldrm0: 2160x1440, 32bpp
Apr 26 09:19:26 openx /bsd: wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation), using wskbd0
Apr 26 09:19:26 openx /bsd: wsdisplay0: screen 1-5 added (std, vt100 emulation)
Apr 26 09:19:26 openx /bsd: iwm0: hw rev 0x230, fw ver 22.361476.0, address 7c:11:cb:4b:81:45
Apr 26 09:19:26 openx sendsyslog: dropped 2 messages, error 57, pid 83686
Apr 26 09:19:26 openx savecore: no core dump
Apr 26 09:19:27 openx apmd: battery status: high. external power status: connected. estimated battery life 100%
Apr 26 09:19:32 openx reorder_kernel: kernel relinking done

Reply | Threaded
Open this post in threaded view
|

Re: iwm: unhandled firmware response

Stefan Sperling-5
On Fri, Apr 26, 2019 at 09:47:49AM -0400, Jake Champlin wrote:

> Hello bugs@!
>
> With 6.5-current, seeing a lot of unhandled firmware responses that are filling
> up the kernel message buffer. I've only been able to reproduce these errors
> _after_ the system comes back from a low power state. However, this could also
> be a red herring, I'm not sure.
> There haven't been any recent commits to if_iwm.c in-between the errors occuring
> either.
>
> Thanks!

> Apr 25 18:57:23 openx /bsd: iwm0: unhandled firmware response 0x6/0x22909826 rx ring 85[74]

Please check if this still occurs after adding kern.bufcachepercent=20
to /etc/sysctl.conf and a reboot.

Reply | Threaded
Open this post in threaded view
|

Re: iwm: unhandled firmware response

Jake Champlin
On Fri, Apr 26, 2019 at 04:49:49PM +0200, Stefan Sperling wrote:

> On Fri, Apr 26, 2019 at 09:47:49AM -0400, Jake Champlin wrote:
> > Hello bugs@!
> >
> > With 6.5-current, seeing a lot of unhandled firmware responses that are filling
> > up the kernel message buffer. I've only been able to reproduce these errors
> > _after_ the system comes back from a low power state. However, this could also
> > be a red herring, I'm not sure.
> > There haven't been any recent commits to if_iwm.c in-between the errors occuring
> > either.
> >
> > Thanks!
>
> > Apr 25 18:57:23 openx /bsd: iwm0: unhandled firmware response 0x6/0x22909826 rx ring 85[74]
>
> Please check if this still occurs after adding kern.bufcachepercent=20
> to /etc/sysctl.conf and a reboot.

So far so good, will continue to monitor over the next couple of days.

Reply | Threaded
Open this post in threaded view
|

Re: iwm: unhandled firmware response

Krystian Lewandowski-2
I observed similar issues:

iwm0: hw rev 0x230, fw ver 22.361476.0, address e4:0e:ee:81:3d:a0
iwm0: unhandled firmware response 0x58/0xc10f rx ring 0[0]
iwm0: unhandled firmware response 0xc4/0xc10e rx ring 0[0]
iwm0: unhandled firmware response 0x5c/0xc10e rx ring 0[0]
iwm0: unhandled firmware response 0xce/0xa502028d rx ring 12[85]
iwm0: unhandled firmware response 0x42/0xa5020301 rx ring 12[85]
iwm0: unhandled firmware response 0x4f/0xa502040e rx ring 12[85]
iwm0: unhandled firmware response 0xe4/0x304288 rx ring 1[238]
[...]

With kern.bufcachepercent=20, so far so good. But didn't test much.

--
Krystian

Reply | Threaded
Open this post in threaded view
|

Re: iwm: unhandled firmware response

Stefan Sperling-5
On Sat, Apr 27, 2019 at 12:04:51PM +0200, Krystian Lewandowski wrote:

> I observed similar issues:
>
> iwm0: hw rev 0x230, fw ver 22.361476.0, address e4:0e:ee:81:3d:a0
> iwm0: unhandled firmware response 0x58/0xc10f rx ring 0[0]
> iwm0: unhandled firmware response 0xc4/0xc10e rx ring 0[0]
> iwm0: unhandled firmware response 0x5c/0xc10e rx ring 0[0]
> iwm0: unhandled firmware response 0xce/0xa502028d rx ring 12[85]
> iwm0: unhandled firmware response 0x42/0xa5020301 rx ring 12[85]
> iwm0: unhandled firmware response 0x4f/0xa502040e rx ring 12[85]
> iwm0: unhandled firmware response 0xe4/0x304288 rx ring 1[238]
> [...]
>
> With kern.bufcachepercent=20, so far so good. But didn't test much.

Thanks for confirming that the problem seems to be related to bufcachepercent.
I will need help from elder wizards to learn what could be done about this.

Reply | Threaded
Open this post in threaded view
|

Re: iwm: unhandled firmware response

Bryan Linton
On 2019-04-27 15:56:33, Stefan Sperling <[hidden email]> wrote:

> On Sat, Apr 27, 2019 at 12:04:51PM +0200, Krystian Lewandowski wrote:
> > I observed similar issues:
> >
> > iwm0: hw rev 0x230, fw ver 22.361476.0, address e4:0e:ee:81:3d:a0
> > iwm0: unhandled firmware response 0x58/0xc10f rx ring 0[0]
> > iwm0: unhandled firmware response 0xc4/0xc10e rx ring 0[0]
> > iwm0: unhandled firmware response 0x5c/0xc10e rx ring 0[0]
> > iwm0: unhandled firmware response 0xce/0xa502028d rx ring 12[85]
> > iwm0: unhandled firmware response 0x42/0xa5020301 rx ring 12[85]
> > iwm0: unhandled firmware response 0x4f/0xa502040e rx ring 12[85]
> > iwm0: unhandled firmware response 0xe4/0x304288 rx ring 1[238]
> > [...]
> >
> > With kern.bufcachepercent=20, so far so good. But didn't test much.
>
> Thanks for confirming that the problem seems to be related to bufcachepercent.
> I will need help from elder wizards to learn what could be done about this.
>

Hello,

Just in case it might be useful, I thought mentioning a similar
issue I had encountered in the past might help.

In my case, I had issues with the em(4) driver disconnecting from
the system while mbuf usage increased, so this may ultimately
prove be a separate issue.

        https://marc.info/?l=openbsd-bugs&m=152413838210478&w=2

Nevertheless, I figured mentioning it might possibly be of help,
since I ultimately figured out that the issues were caused by
me setting kern.bufcachepercent=90.

Setting it back to kern.bufcachepercent=20 fixed all my issues.
Through trial and error, I found that I could crank it up to 60%
without issues, which is where it's been since.

Again, my issue may be completely separate from the OPs issue, but
since both of them involved networking and the bufcache, I thought
I might at least mention it just in case it helps to reveal some
more information somehow.

--
Bryan

Reply | Threaded
Open this post in threaded view
|

Re: iwm: unhandled firmware response

Krystian Lewandowski-2
I did use kern.bufcachepercent=90 before. I think I copied it blindly
from some blog post about OpenBSD on a laptop. No problems observed
for now with "iwm" since 20% value in use.

--
Krystian

Reply | Threaded
Open this post in threaded view
|

Re: iwm: unhandled firmware response

Stefan Sperling-5
On Mon, Apr 29, 2019 at 02:10:26AM +0200, Krystian Lewandowski wrote:
> I did use kern.bufcachepercent=90 before. I think I copied it blindly
> from some blog post about OpenBSD on a laptop. No problems observed
> for now with "iwm" since 20% value in use.

The problem does not affect all machines.
As far as I understand, it is related to how much physical memory can
be used for DMA, and this varies between machines.