Project

General

Profile

Actions

Bug #440

open

wifi/hostapd generates lots of log messages

Added by Hammel about 9 years ago. Updated about 1 year ago.

Status:
In Progress
Priority:
Urgent
Assignee:
Category:
04 - Root File System
Target version:
Start date:
21 May 2015
Due date:
% Done:

20%

Estimated time:
Severity:
04 - Low

Description

This will fill up /var/log/messages. I need a way to trim this down.

The messages look like this:

Jan 1 00:08:38 (none) user.warn kernel: [ 518.568892] ieee80211 phy0: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 2 in queue 2
Jan 1 00:08:38 (none) user.warn kernel: [ 518.568922] ieee80211 phy0: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 2 in queue 2

More examples attached.


Files

log.txt (2.99 KB) log.txt log messages from wifi via hostapd Hammel, 21 May 2015 20:13
Actions #1

Updated by Hammel almost 9 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 20

Might be able to use nohwcrypt=1 and disable power mgmt.

Also, check version of firmware

[84010.058440] ieee80211 phy13: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.29

after update it will say

[85241.009289] ieee80211 phy14: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.32

The bug doesn't seem to be a problem with nearby devices (the local lan in the trailer) so one option would be to disable the message from syslog. In /etc/syslog.conf (I think)

user.=warn /dev/null

But that will remove all warnings, which may not be what we want in the long term. It suffices for production, however.

Actions #2

Updated by Hammel almost 9 years ago

Busybox's syslogd already does logrotation and this feature is enabled in my config. So technically this issue is a non-issue. But I still want to filter those messages.

It also support a limited syslog.conf, which I already have enabled. Here is the docs/syslog.conf.txt file:

If syslogd applet compiled with FEATURE_SYSLOGD_CFG=y, then it supports restricted syslog.conf.
The config resembles rsyslog.conf in RULES part:

LINE = DELIM [RULE | COMMENT]
COMMENT = #.*
DELIM = SPACE TAB
RULE = SELECTOR [;SELECTOR]* DELIM* ACTION DELIM*
SELECTOR = FACILITY [,FACILITY]* .[[!]=] PRIORITY
FACILITY = * | kern | user ... (see syslog.h)
PRIORITY = * | emerg | alert ... (see syslog.h)
ACTION = FILE

"mark" facility is NOT supported.
"none" priority is supported.
In FACILITY and PRIORITY "*" stands for "any".
FILE is a regular file or tty device.

Here is an example:

#syslog.conf
kern,user.*                                 /var/log/messages   #all messages of kern and user facilities
kern.!err                                   /var/log/critical   #all messages of kern facility with priorities
lower tha
n err (warn, notice ...)
*.*;auth,authpriv.none                      /var/log/noauth #all messages except ones with auth and authpriv
facilities
kern,user.*;kern.!=notice;*.err;syslog.none /var/log/OMG    #some whicked rule just as an example =)
*.*                                         /dev/null       #this prevents from logging to default log file (-O
FILE or
/var/log/messages)

Even in the case of match with some rule another rules will be tried too.
If there was no match with any of the rules, logging to default log file or shared memory will be performed.

So I should be able to added a syslog.conf similar to what I have in the first comment.

Actions #3

Updated by Hammel almost 9 years ago

  • Priority changed from Immediate to Low
  • Severity changed from 01 - Critical to 04 - Low

I'm not seeing this much anymore. I'm not sure why it went away. Since it doesn't show up on a system that has been running for a long time I'm going to move this to a very low priority.

Actions #4

Updated by Hammel almost 9 years ago

  • Target version changed from 0.11.0 to 2.0 - Harkonnen
Actions #5

Updated by Hammel about 1 year ago

  • Priority changed from Low to Urgent
  • Target version changed from 2.0 - Harkonnen to 3.0 - Corrino

Retest for 3.0. If not reproducable then close issue.

Actions

Also available in: Atom PDF