Wireless Access

last person joined: 20 hours ago 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Expand all | Collapse all

system log kernel error

This thread has been viewed 26 times
  • 1.  system log kernel error

    Posted Dec 27, 2018 04:04 AM

    Hi,

     

    on ap-315 and AP-314  with mobility controler ( 6.5.4.10 ) :

     

    show log system 100
    
    ....
    
    Dec 27 07:38:24 KERNEL(DYDDD1AP04@172.29.123.211): [14161.395595] === Reducing pace for error prints ====
    Dec 27 07:38:24 KERNEL(DYDDD1AP04@172.29.123.211): [14161.395626] Start seq_num 0 End seq_num 0 tid 16 failed seq 0 - error occured 2000 times
    Dec 27 07:45:50 KERNEL(DYDDD1AP04@172.29.123.211): [14607.126054] === Reducing pace for error prints ====
    Dec 27 07:45:50 KERNEL(DYDDD1AP04@172.29.123.211): [14607.126054] Start seq_num 0 End seq_num 0 tid 16 failed seq 0 - error occured 2100 times
    Dec 27 07:53:36 KERNEL(DYDDD1AP04@172.29.123.211): [15072.993096] === Reducing pace for error prints ====
    Dec 27 07:53:36 KERNEL(DYDDD1AP04@172.29.123.211): [15072.993096] Start seq_num 0 End seq_num 0 tid 16 failed seq 0 - error occured 2200 times
    Dec 27 07:57:36 KERNEL(DYDDD2AP04@172.29.123.215): [2146636.818840] === Reducing pace for error prints ====
    Dec 27 07:57:36 KERNEL(DYDDD2AP04@172.29.123.215): [2146636.818840] Start seq_num 0 End seq_num 0 tid 16 failed seq 0 - error occured 19500 times
    Dec 27 08:00:19 KERNEL(DYDDD1AP04@172.29.123.211): [15476.715776] === Reducing pace for error prints ====
    Dec 27 08:00:19 KERNEL(DYDDD1AP04@172.29.123.211): [15476.715808] Start seq_num 0 End seq_num 0 tid 16 failed seq 0 - error occured 2300 times
    Dec 27 08:00:28 KERNEL(DYDD15AP02@172.29.123.199): [2805921.925015] === Reducing pace for error prints ====
    Dec 27 08:00:28 KERNEL(DYDD15AP02@172.29.123.199): [2805921.925046] Start seq_num 0 End seq_num 0 tid 16 failed seq 0 - error occured 2500 times
    Dec 27 08:01:03 KERNEL(FECCC1AP02@172.29.147.180): [514459.719384] Start seq_num 0 End seq_num 0 tid 16 failed seq 0 - error occured 8300 times
    Dec 27 08:01:03 KERNEL(FECCC1AP02@172.29.147.180): [514459.719353] === Reducing pace for error prints ====
    Dec 27 08:07:23 KERNEL(DYDDD1AP04@172.29.123.211): [15900.491659] === Reducing pace for error prints ====
    Dec 27 08:07:23 KERNEL(DYDDD1AP04@172.29.123.211): [15900.491690] Start seq_num 0 End seq_num 0 tid 16 failed seq 0 - error occured 2400 times
    Dec 27 08:14:35 KERNEL(FECCC1AP02@172.29.147.180): [515271.803014] === Reducing pace for error prints ====
    Dec 27 08:14:35 KERNEL(FECCC1AP02@172.29.147.180): [515271.803014] Start seq_num 0 End seq_num 0 tid 16 failed seq 0 - error occured 8400 times
    Dec 27 08:15:35 KERNEL(DYDDD1AP04@172.29.123.211): [16392.300437] === Reducing pace for error prints ====
    Dec 27 08:15:35 KERNEL(DYDDD1AP04@172.29.123.211): [16392.300469] Start seq_num 0 End seq_num 0 tid 16 failed seq 0 - error occured 2500 times
    Dec 27 08:23:37 KERNEL(DYDDD1AP04@172.29.123.211): [16874.106810] === Reducing pace for error prints ====
    Dec 27 08:23:37 KERNEL(DYDDD1AP04@172.29.123.211): [16874.106842] Start seq_num 0 End seq_num 0 tid 16 failed seq 0 - error occured 2600 times
    Dec 27 08:27:52 KERNEL(FECCC1AP02@172.29.147.180): [516068.862933] === Reducing pace for error prints ====
    Dec 27 08:27:52 KERNEL(FECCC1AP02@172.29.147.180): [516068.862964] Start seq_num 0 End seq_num 0 tid 16 failed seq 0 - error occured 8500 times
    Dec 27 08:31:05 KERNEL(DYDDD1AP04@172.29.123.211): [17322.847017] === Reducing pace for error prints ====
    Dec 27 08:31:05 KERNEL(DYDDD1AP04@172.29.123.211): [17322.847017] Start seq_num 0 End seq_num 0 tid 16 failed seq 0 - error occured 2700 times
    Dec 27 08:38:10 KERNEL(DYDDD1AP04@172.29.123.211): [17747.698344] === Reducing pace for error prints ====
    Dec 27 08:38:10 KERNEL(DYDDD1AP04@172.29.123.211): [17747.698376] Start seq_num 0 End seq_num 0 tid 16 failed seq 0 - error occured 2800 times
    Dec 27 08:39:32 KERNEL(FECCC1AP02@172.29.147.180): [516768.820634] === Reducing pace for error prints ====
    Dec 27 08:39:32 KERNEL(FECCC1AP02@172.29.147.180): [516768.820634] Start seq_num 0 End seq_num 0 tid 16 failed seq 0 - error occured 8600 times
    
    ..... 

     

    We search without sucess on the Internet for the meaning of this error logs.

     

    Can someone explain the problem ? ( if it is a problem ).

     

    Regards.



  • 2.  RE: system log kernel error

    EMPLOYEE
    Posted Jan 03, 2019 01:04 AM

    hi

     

    are there any users on the APs when these messages are occurring ?

    do the messages stop when there are no users ?

    if you reboot one AP that has the logs, do they come back within (say) 1 day ?

    what are the client types ? (macs, windows, mixed, what chipset?)

     

    it's possible there is some user impact, it may also be unnoticed by the users - need to get some more information.

     

     

     

     



  • 3.  RE: system log kernel error

    Posted Jan 18, 2019 09:05 AM

     Hi,

     

    soory for delay :

     

    are there any users on the APs when these messages are occurring ?

    yes there's users on the APs   ( 5 to 14 on 2.4Ghz ssid )

     

    do the messages stop when there are no users ?

    We will check on night but most of the AP that make the log are on place where there is WiFi connected printers.

     

    if you reboot one AP that has the logs, do they come back within (say) 1 day ?

    We try to reboot 2 AP that have the logs , they comme back in less than 10 minutes (6 users ). 

     

    what are the client types ? (macs, windows, mixed, what chipset?)

    Windows PC , printers , and one or two Windows CE barcode readers (Zebra) . 

    don't know the chipset. 

     

    no users impact for now.

     

    controler are 7210 on 6.5.4.10. most of the log 90-95%  comme from AP-315. and most of log from 6 AP-315 (we have 20+ AP-315 )

    before that with 6.5.4.8 we also have lot of this logs with AP-314 , now with 6.5.4.10 we have 2 log per day ( from 2 AP on 400+ AP314).

     

    Thank for help.

     

    Regards

     

     



  • 4.  RE: system log kernel error

    Posted Jan 22, 2019 09:42 AM

    Hi ,

    one of the AP that have the log message (the one that have most of this log)  just do that :

     

    Jan 22 14:21:39  KERNEL(DYDDD2AP03@172.29.123.214): [344103.513225] === Reducing pace for error prints ==== 
    Jan 22 14:21:39  KERNEL(DYDDD2AP03@172.29.123.214): [344103.513225] Start seq_num 0 End seq_num 0 tid 16 failed seq 0 - error occured 10700 times
    Jan 22 14:25:20  KERNEL(DYDDD1AP04@172.29.123.211): [12112.805654] === Reducing pace for error prints ==== 
    Jan 22 14:25:20  KERNEL(DYDDD1AP04@172.29.123.211): [12112.805654] Start seq_num 0 End seq_num 0 tid 16 failed seq 0 - error occured 1800 times
    Jan 22 14:28:50  KERNEL(DYDDD2AP03@172.29.123.214): [344534.558398] === Reducing pace for error prints ==== 
    Jan 22 14:28:50  KERNEL(DYDDD2AP03@172.29.123.214): [344534.558429] Start seq_num 0 End seq_num 0 tid 16 failed seq 0 - error occured 10800 times
    Jan 22 14:30:14  KERNEL(FECCC1AP02@172.29.147.180): [505996.868244] === Reducing pace for error prints ==== 
    Jan 22 14:30:14  KERNEL(FECCC1AP02@172.29.147.180): [505996.868244] Start seq_num 0 End seq_num 0 tid 16 failed seq 0 - error occured 4000 times
    Jan 22 14:30:31  KERNEL(DYDDD2AP03@172.29.123.214): [344635.831906] Start seq_num 0 End seq_num 0 tid 16 real failed seq -1 win_mask 0 vdev (80:8d:b7:e4:20:42) peer d863e000 (e4:b3:18:3c:18:60)
    Jan 22 14:30:31  KERNEL(DYDDD2AP03@172.29.123.214): [344635.831906] ol_rx_reorder_release 271 RX reorder error occured total 10823 times 10000 times within 337025438ms. ASSERTING the Target to collect FW core dump!!!
    Jan 22 14:30:32  KERNEL(DYDDD2AP03@172.29.123.214): [344635.833062] [wifi1]: XXX TARGET ASSERTED XXX
    Jan 22 14:30:32  KERNEL(DYDDD2AP03@172.29.123.214): [344635.834093] Target Register Dump Location 0x004066AC
    Jan 22 14:30:32  KERNEL(DYDDD2AP03@172.29.123.214): [344635.835093] Target Register Dump
    Jan 22 14:30:32  KERNEL(DYDDD2AP03@172.29.123.214): [344635.835124] [00]   :  0x00000009
    Jan 22 14:30:32  KERNEL(DYDDD2AP03@172.29.123.214): [344635.835124] [01]   :  0x000015B3
    Jan 22 14:30:32  KERNEL(DYDDD2AP03@172.29.123.214): [344635.835124] [02]   :  0x009A8523
    Jan 22 14:30:32  KERNEL(DYDDD2AP03@172.29.123.214): [344635.835124] [03]   :  0x00955B31
    Jan 22 14:30:32  KERNEL(DYDDD2AP03@172.29.123.214): [344635.835124] [04]   :  0x009A8523
    Jan 22 14:30:32  KERNEL(DYDDD2AP03@172.29.123.214): [344635.835124] [05]   :  0x00060530
    Jan 22 14:30:32  KERNEL(DYDDD2AP03@172.29.123.214): [344635.835124] Resetting  wifi1 radio
    Jan 22 14:30:32  KERNEL(DYDDD2AP03@172.29.123.214): [344635.840029] dbglog_hdr.dbuf=0041b018 dbglog_data=db58f000 dbglog_buf.buffer=000e6e4c dbglog_buf.length=760

    reboot maybe related to the problem.

     

    any idea ?

     

    Regards.



  • 5.  RE: system log kernel error

    EMPLOYEE
    Posted Jan 24, 2019 10:31 AM

    hi, sorry for the delay. there are two issues evident:

     

    a) log flooding of this message where "seq 0" is seen

    Jan 22 14:25:20  KERNEL(DYDDD1AP04@172.29.123.211): [12112.805654] === Reducing pace for error prints ==== 
    Jan 22 14:25:20  KERNEL(DYDDD1AP04@172.29.123.211): [12112.805654] Start seq_num 0 End seq_num 0 tid 16 failed seq 0 - error occured 1800 times

    b) a self initiated crash that comes when this message is seen, where "seq -1" is seen

    Jan 22 14:30:31  KERNEL(DYDDD2AP03@172.29.123.214): [344635.831906] Start seq_num 0 End seq_num 0 tid 16 real failed seq -1 win_mask 0 vdev (80:8d:b7:e4:20:42) peer d863e000 (e4:b3:18:3c:18:60)
    Jan 22 14:30:31  KERNEL(DYDDD2AP03@172.29.123.214): [344635.831906] ol_rx_reorder_release 271 RX reorder error occured total 10823 times 10000 times within 337025438ms. ASSERTING the Target to collect FW core dump!!!
    Jan 22 14:30:32  KERNEL(DYDDD2AP03@172.29.123.214): [344635.833062] [wifi1]: XXX TARGET ASSERTED XXX

    For b), it's resolved in bug id 191696 which is fixed in 8.x software but not yet 6.5.x , it's pending patch - check back in a few weeks

     

    For a), it's not fixed - R&D needs more info (bug 180612), if you're able and willing to do some further data collection, send me a private message and we can discuss it via email rather than the forum

     

    regards

    -jeff

     

     



  • 6.  RE: system log kernel error

    Posted Jan 30, 2019 08:38 AM

    Hi,

     

    thanks for answers !

     

    I send i private message with informations.

     

    for all , We will make update if bug is resolved.

     

    Regards.

     



  • 7.  RE: system log kernel error

    Posted Feb 23, 2022 02:21 AM
    Hi OPENevents,

    Could you please update this case? Is this bug resolved?
    I have the same problem right now.

    Thank you so much.

    ------------------------------
    Jasmine Phan
    ------------------------------