Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 9 replies
  • Subscribers 3 subscribers
  • Views 3670 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

APX120 errors in log

Amodin

I have two APX120s set up as a MESH network around 100ft apart from each other.

I have some items from my wireless log that I cannot seem to track down the cause:

2022:06:08-09:15:34 P310062TCCHQB8C kernel: [191778.565642] [wifi0] FWLOG: [2347069] VDEV_MGR_BCN_IN_SYNC ( 0x2 )
2022:06:08-09:15:39 P310062TCCHQB8C kernel: [191783.563368] [wifi0] FWLOG: [2352081] VDEV_MGR_FIRST_BMISS_DETECTED ( 0x1, 0x23e3d1, 0x23e3ce, 0x3e8 )
2022:06:08-09:15:39 P310062TCCHQB8C kernel: [191783.563425] [wifi0] FWLOG: [2352104] VDEV_MGR_BCN_IN_SYNC ( 0x2 )
2022:06:08-09:15:42 P310062TCCHQB8C kernel: [191786.561729] [wifi0] FWLOG: [2355647] VDEV_MGR_FIRST_BMISS_DETECTED ( 0x1, 0x23f1bf, 0x23f1bb, 0x3e8 )
2022:06:08-09:15:42 P310062TCCHQB8C kernel: [191786.561796] [wifi0] FWLOG: [2355672] VDEV_MGR_BCN_IN_SYNC ( 0x2 )
2022:06:08-09:15:52 P310062TCCHQB8C kernel: [191796.557333] [wifi0] FWLOG: [2365299] VDEV_MGR_FIRST_BMISS_DETECTED ( 0x1, 0x241773, 0x241771, 0x3e8 )
2022:06:08-09:15:52 P310062TCCHQB8C kernel: [191796.557396] [wifi0] FWLOG: [2365324] VDEV_MGR_BCN_IN_SYNC ( 0x2 )
2022:06:08-09:16:06 P310062TCCHQB8C kernel: [191810.551170] [wifi0] FWLOG: [2380409] VDEV_MGR_FIRST_BMISS_DETECTED ( 0x1, 0x245279,

Also this:

2022:06:08-09:25:03 P31004JD36BQQ82 kernel: [1001003.162517] rfs_wxt_get_cpu_by_irq[131]:INFO:IRQ is bound to more than one CPU
2022:06:08-09:25:04 P31004JD36BQQ82 kernel: [1001003.866967] rfs_wxt_get_cpu_by_irq[131]:INFO:IRQ is bound to more than one CPU
2022:06:08-09:25:05 P31004JD36BQQ82 kernel: [1001005.489651] rfs_wxt_get_cpu_by_irq[131]:INFO:IRQ is bound to more than one CPU
2022:06:08-09:25:08 P31004JD36BQQ82 kernel: [1001007.697846] rfs_wxt_get_cpu_by_irq[131]:INFO:IRQ is bound to more than one CPU
2022:06:08-09:25:12 P31004JD36BQQ82 kernel: [1001012.406476] rfs_wxt_get_cpu_by_irq[131]:INFO:IRQ is bound to more than one CPU
2022:06:08-09:25:14 P31004JD36BQQ82 kernel: [1001013.968334] rfs_wxt_get_cpu_by_irq[131]:INFO:IRQ is bound to more than one CPU
2022:06:08-09:25:14 P31004JD36BQQ82 kernel: [1001014.486113] rfs_wxt_get_cpu_by_irq[131]:INFO:IRQ is bound to more than one CPU
2022:06:08-09:25:33 P31004JD36BQQ82 kernel: [1001033.170542] rfs_wxt_get_cpu_by_irq[131]:INFO:IRQ is bound to more than one CPU

And this:

2022:06:08-09:36:22 P31004JD36BQQ82 kernel: [1001681.848669] Switching to Tx Mode-1 Threshold 0
2022:06:08-09:36:24 P31004JD36BQQ82 kernel: [1001684.615935] Switching to Tx Mode-1 Threshold 34
2022:06:08-09:36:28 P31004JD36BQQ82 kernel: [1001688.021838] Switching to Tx Mode-1 Threshold 0
2022:06:08-09:36:30 P31004JD36BQQ82 kernel: [1001690.612645] Switching to Tx Mode-1 Threshold 34
2022:06:08-09:36:40 P31004JD36BQQ82 kernel: [1001699.839384] Switching to Tx Mode-1 Threshold 0
2022:06:08-09:36:42 P31004JD36BQQ82 kernel: [1001702.605751] Switching to Tx Mode-1 Threshold 34
2022:06:08-09:36:50 P31004JD36BQQ82 kernel: [1001710.757298] Switching to Tx Mode-1 Threshold 0
2022:06:08-09:36:51 P31004JD36BQQ82 kernel: [1001711.600671] Switching to Tx Mode-1 Threshold 34
2022:06:08-09:37:06 P31004JD36BQQ82 kernel: [1001725.798647] Switching to Tx Mode-1 Threshold 0
2022:06:08-09:37:06 P31004JD36BQQ82 kernel: [1001726.592158] Switching to Tx Mode-1 Threshold 34

Any ideas how to get rid of these?

Thanks for any help.



This thread was automatically locked due to age.
Parents
  • 0

    What do you observe when you get these lines in the Kernel log?

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson

    Nothing today in the Kernel log, and the only thing it shows is my NIC down and NIC up messages when I disconnected my cable modem related to my other post with wireless dropping when I lose ISP connectivity.

    And, these messages are still showing in the log today, several times, same messages.

    All of these messages here are from the new AP I got from you, at the remote end of my MESH. ;)  I do remember the IRQ error also showing when it was originally setup to configure the MESH on the wired network prior to moving it to the remote location.

    OPNSense 64-bit | Intel Xeon 4-core v3 1225 3.20Ghz
    16GB Memory | 500GB SSD HDD | ATT Fiber 1GB
    (Former Sophos UTM Veteran, Former XG Rookie)

  • 0 in reply to Amodin

    What's in the Wireless log when these lines appear in the Kernel log?

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson

    Zero information in Kernel.

    This is the entirety of my log today, after all of these same entries from today:

    2022:06:09-13:31:10 amodin kernel: [1789724.986617] e1000e: eth1 NIC Link is Down
2022:06:09-13:32:51 amodin kernel: [1789826.507073] e1000e: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None

    This entry was generated only because of me unplugging my cable modem. There was 0 entries from yesterday as well.  As in, absolutely nothing in Kernel.

    OPNSense 64-bit | Intel Xeon 4-core v3 1225 3.20Ghz
    16GB Memory | 500GB SSD HDD | ATT Fiber 1GB
    (Former Sophos UTM Veteran, Former XG Rookie)

  • 0 in reply to Amodin

    ROFL - that's the Kernel log, not the Wireless log!

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson
    BAlfson said:

    What's in the Wireless log when these lines appear in the Kernel log?

    LOL that threw me off.  All of my log postings are the Wireless log, except that actual Kernel log I posted.  Slight smile

    All three log entries in the original post are from Wireless log.  

    OPNSense 64-bit | Intel Xeon 4-core v3 1225 3.20Ghz
    16GB Memory | 500GB SSD HDD | ATT Fiber 1GB
    (Former Sophos UTM Veteran, Former XG Rookie)

  • 0 in reply to Amodin

    "kernel:" is in all of the log lines here.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson

    Yeah, I know.  I swear that is all in Wireless.

    OPNSense 64-bit | Intel Xeon 4-core v3 1225 3.20Ghz
    16GB Memory | 500GB SSD HDD | ATT Fiber 1GB
    (Former Sophos UTM Veteran, Former XG Rookie)

  • 0 in reply to Amodin

    Yeah, I got no idea on this anymore.  This has to be some kind of problem with MESH and it drops my connectivity all the time, or some firmware issue with the AP being used with MESH.

    OPNSense 64-bit | Intel Xeon 4-core v3 1225 3.20Ghz
    16GB Memory | 500GB SSD HDD | ATT Fiber 1GB
    (Former Sophos UTM Veteran, Former XG Rookie)

Reply
  • 0 in reply to Amodin

    Yeah, I got no idea on this anymore.  This has to be some kind of problem with MESH and it drops my connectivity all the time, or some firmware issue with the AP being used with MESH.

    OPNSense 64-bit | Intel Xeon 4-core v3 1225 3.20Ghz
    16GB Memory | 500GB SSD HDD | ATT Fiber 1GB
    (Former Sophos UTM Veteran, Former XG Rookie)

Children
No Data
Unfiltered HTML