You are not logged in.

#1 2016-07-16 13:46:31

motivic
Member
From: Washington DC
Registered: 2016-02-28
Posts: 1

What to do with systemd error messages on brcmf and mei_wdt

First time poster, hoping to become more involved in the Arch Linux community.

I started using Arch Linux around March this year and it has been a relatively smooth and pleasant experience.

With that said, I have been for several months now trying to address the error messages that I get every time I start Arch Linux.

% dmesg -l err
[    2.651885] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Nov 10 2015 06:38:10 version 7.35.177.61 (r598657) FWID 01-ea662a8c
[    2.716872] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 0x30)
[    6.373367] psmouse serio1: synaptics: Unable to query device.
[   15.690262] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23
[   17.140347] mei_wdt mei::05b79a6f-4628-4d7f-899d-a91514cb32ab:02: Could not register event ret=-22

Based on my research, the brcmfmac errors have to do with my Broadcom controller:

 % lspci -k | grep Network                                                                        
02:00.0 Network controller: Broadcom Corporation BCM43602 802.11ac Wireless LAN SoC (rev 01)

and the mei_wdt error has to do with my Intel graphic card.

There is also the error with psmouse serio1: synaptics, and I suspect that's caused by a USB serial mouse which is not usually plugged into my laptop.

So far I haven't found any information on what to do with these error messages. They have not caused any real issues except for being a constant source of annoyance.

So my questions are:

  1. Is it advisable to just continue ignoring these error messages as they do not cause any usability issues?

  2. Can anyone suggest things I can try to resolve these errors?

P.S.: I'm on a Dell XPS 15 9550 (non-touchscreen).

Any feedback is much appreciated!

Last edited by motivic (2016-07-16 13:47:16)

Offline

#2 2016-08-11 17:37:22

wingsuit
Member
Registered: 2013-05-18
Posts: 12

Re: What to do with systemd error messages on brcmf and mei_wdt

Is there a way I can stop the boot from being interrupted due to this brcmfmac error?

Offline

#3 2016-08-16 13:53:21

initramfs
Member
Registered: 2016-02-26
Posts: 5

Re: What to do with systemd error messages on brcmf and mei_wdt

I too experience these errors, on a Dell XPS 15 9550 as well (with touchscreen).

Offline

#4 2016-10-15 08:08:45

patrick.bucher
Member
From: Switzerland
Registered: 2016-10-15
Posts: 13
Website

Re: What to do with systemd error messages on brcmf and mei_wdt

First poster, too :-)
I get exactly the same error, but not any other errors:

$ dmesg -l err
[   16.732820] mei_wdt mei::05b79a6f-4628-4d7f-899d-a91514cb32ab:02: Could not register event ret=-22

I'm running a Dell OptiPlex 7040. Everything else is working smoothely and perfectly (thanks arch team!).
Edit: Maybe some hints from the source: https://github.com/torvalds/linux/blob/ … /mei_wdt.c

/* on legacy devices notification is not supported
     * this doesn't fail the registration for RX event
     */
    if (ret && ret != -EOPNOTSUPP) {
        dev_err(&cldev->dev, "Could not register event ret=%d\n", ret);
        goto err_disable;
        }
// lines omitted
err_disable:
        mei_cldev_disable(cldev);

So could one just blacklist that module?

Last edited by patrick.bucher (2016-10-15 08:11:06)

Offline

#5 2017-06-27 04:17:27

nachopro
Member
Registered: 2013-08-23
Posts: 78

Re: What to do with systemd error messages on brcmf and mei_wdt

Sorry, but I'm experimenting the same issue (with the exactly identifier) on my new Latitude E7270

Offline

#6 2017-06-27 04:57:19

Docbroke
Member
From: India
Registered: 2015-06-13
Posts: 1,433

Re: What to do with systemd error messages on brcmf and mei_wdt

If there are no functional problems just add this to your kernel parameters

loglevel=3

for information

loglevel=       All Kernel Messages with a loglevel smaller than the
                    console loglevel will be printed to the console. It can
                    also be changed with klogd or other programs. The
                    loglevels are defined as follows:

                    0 (KERN_EMERG)          system is unusable
                    1 (KERN_ALERT)          action must be taken immediately
                    2 (KERN_CRIT)           critical conditions
                    3 (KERN_ERR)            error conditions
                    4 (KERN_WARNING)        warning conditions
                    5 (KERN_NOTICE)         normal but significant condition
                    6 (KERN_INFO)           informational
                    7 (KERN_DEBUG)          debug-level messages

Offline

#7 2017-06-27 07:17:02

seth
Member
Registered: 2012-09-03
Posts: 49,945

Re: What to do with systemd error messages on brcmf and mei_wdt

modinfo mei_wdt
modinfo wrote:

description:    Device driver for Intel MEI iAMT watchdog

ISO3166 is the region codes (uk, de, dk, us, ...) so something at some point tries to set an invalid regulatory domain for the chip (what reg. the rules is close to irrelevant, but you might be able to use wifi channels and transmission power considered illegal by your government)
This does not mean it's never set correctly, try

iw reg get

and ensure to correctly configure your system locale.

There might be not IP table *yet* - if wifi works, you can ignore that message

psmouse1/synaptics is your touchpad - you might be unable to use advanced features (two-finger or corner actions etcetc.) or this is just "the device has not yet initialized")

In general, I personally tend to look into dmesg and logs when sth. doesn't work; not like "omg, there's a message!!! what will it mean???" ;-)

Online

#8 2017-07-14 00:54:42

nachopro
Member
Registered: 2013-08-23
Posts: 78

Re: What to do with systemd error messages on brcmf and mei_wdt

So Sorry, my "new" E7270 comes with 1.6.3 BIOS version. After update to 1.16.4 the mei_wdt gone away! No more problem with i915 suspension nor   clicking/poping speakers noise!!!

Check if yours models have a BIOS update!

Offline

Board footer

Powered by FluxBB