All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean-Pierre TOSONI <jp.tosoni@acksys.fr>
To: Adam Cottrel <adam.cottrel@veea.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: Large number of crda failures
Date: Wed, 17 Oct 2018 12:39:16 +0000	[thread overview]
Message-ID: <AM4PR0101MB2305F09BCC38C687899BFC16E4FF0@AM4PR0101MB2305.eurprd01.prod.exchangelabs.com> (raw)
In-Reply-To: <DM6PR04MB40596FE840A2426E81FB22A2F2FE0@DM6PR04MB4059.namprd04.prod.outlook.com>

Code 234 => exit(-EINVAL)
Could be that crda is started in a context where the COUNTRY environment variable is invalid, or started with an argument (crda must be run without argument).

> -----Message d'origine-----
> De : linux-wireless-owner@vger.kernel.org [mailto:linux-wireless-owner@vger.kernel.org] De la part de
> Adam Cottrel
> Envoyé : mardi 16 octobre 2018 18:51
> À : linux-wireless@vger.kernel.org
> Objet : Large number of crda failures
> 
> Hi,
> 
> On start up I am getting a large number of error faults reported with CRDA:-
> ➢ ies0600133 systemd-udevd[3949]: Process '/sbin/crda' failed with exit code 234
> Typically, over 50 lines are reported to the syslogs
> 
> However, once the system has fully started, I do not get any issues with running:-
> ➢ iw reg set XX
> 
> These errors are doubling the boot time for Linux. My kernel is 4.14.4 and I am running a Debian base.
> 
> Please can someone advise what is going wrong?
> 
> Best,
> Adam

  reply	other threads:[~2018-10-17 12:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <DM6PR04MB40597C0C909A0EA209361F75F2FE0@DM6PR04MB4059.namprd04.prod.outlook.com>
2018-10-16 16:50 ` Large number of crda failures Adam Cottrel
2018-10-17 12:39   ` Jean-Pierre TOSONI [this message]
2018-10-18 10:18     ` Adam Cottrel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AM4PR0101MB2305F09BCC38C687899BFC16E4FF0@AM4PR0101MB2305.eurprd01.prod.exchangelabs.com \
    --to=jp.tosoni@acksys.fr \
    --cc=adam.cottrel@veea.com \
    --cc=linux-wireless@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.