"Calling CRDA to update world regulatory domain" - WTH??
 

For some 7 months now I've had a Raspberry Pi running Raspbian acting as an embedded controller for a time release lock. The system is contained on a 4Gb SD card which has the little tab in the 'locked' position so it can't get written to or corrupted (in theory at any rate). Everything was running sweet as a nut until about a week ago when I couldn't get the lock to open.
This system relies on getting the time/date from the network via a wi-fi connection, but on examination of the problem, it seems some sort of subroutine has unaccountably started interfering with the bash script I wrote to perform the timing function and is constantly interrupting it. Here's an example of what I'm seeing on a screen when this happens:

...and so on. It actually goes on for page after page.

So anyway, I re-imaged the SD card from a backup and the same problem is happening, so it's obviously something extraneous that's changed rather than any corruption or virus on the card.
Anyone know what this problem is caused by and how I can get rid of it?
TIA,
CC

It's not a problem but messages of the informational level. AFAIK the cfg80211 doesn't have any modprobe switches to quieten it down so you'll have to bit bucket them via a Rsyslogd or Syslog-NG filter. Else maybe you shouldn't use a script but NTP instead or refine it.

I don't know how you can say "it's not a problem" when it is continually interfering with the running of this script right from the moment the thing boots up! How did it get there in the first place? For 7 months the thing was running like a Swiss watch, then all of a sudden out of nowhere these infernal interruptions crop up which render the whole system useless.

I get this as the last message at shutdown. I don't run your script so maybe that was why
you are having a problem. I pulled this out of /var/log/kernel.log

I THINK that is why Unspawn means it is no problem. I get the CDRA message on all my AntiX
laptops and Desktop computers. It is the last message before shutdown.

...additionally
what script exactly? Who created it? What does it do? Or else what's the contents (as in 'grep -v ^# script|grep .;').

This one:

I wrote it. It enables an electronic lock to be opened on Tuesdays and Fridays only (as is evident from the comments).

Interesting. If it did this on mine only at shutdown it wouldn't be a problem. Perhaps if I moved the instruction calling the script to a different file it might fix the problem. Maybe I'm calling it too soon before the system has settled down. Anyway as I say, it never used to matter, though. :-/

So the script itself isn't the problem (can't see how, looks clean) but apparently how and when you call it. Elaborate?

I was just trying to find the file and folder from which it is called but it's taking longer than I thought. If I don't post the answer again within 10 mins, it'll have to be tomorrow as it's late here already...

Right, found it. The script is called by a line in the file /etc/rc.local but there is also an rc.local file in /etc/init.d so perhaps I should transfer the call over to the other one (although I can't see it making much difference).
Right, got brain-ache now so off to bed!

In the House now on my

I checked AGAIN so you will see CDRA is a normal thing

You'll see in my inxi report I am running a 3.12.1 64bit kernel and above was also pulled from /var/log/kern.log.
My other post was from my 32bit i486 3.12.1 kernel on my Atom Netbook running the same distro but in 32bit.

OK, accepting what you say that it's "normal" behaviour, that still leaves me with a system that this "normal, not-a-problem" thing has rendered inoperative.
My original questions remain unanswered, however. What is this thing, how come it suddenly began interfering with my script after 7 months of trouble-free operation and how do I get rid of it - or at least work around it?

Gee, I don't know. Might help. might not.

http://wireless.kernel.org/en/developers/Regulatory

Thanks, I shall take a look later (after a few triple expressos to improve my concentration).

Anyway, searches of the web have revealed that many other users have experienced similar problems with this particular interference, though nowhere have I read anything which explains what precisely it is, where it came from, or how it mysteriously appears (in my case on an SD card which is mounted read-only in /etc/fstab AND has the 'lock' tab in the locked position to prevent alteration/corruption by anyone other than myself (since I alone have physical access).
Perhaps I should have posted this query in the 'security' forum?

Could it be what you are seeing in the logs actually is a side effect of Something Completely Different? Like the device constantly trying to re-establish a connection with the AP? does your AP send a country code? As in 'iw set reg ES'?


That's where the link rokytnji posted comes in.


No, this isn't a Linux security question.