Tue Feb 18, 2014 10:51 am
Feed the mystery message into Google that will often reveal the reason.
Else pull the source code for the device driver and see if it tells you why it might be issued.
Else if you don't notice any odd effects assume it's just noise or "informational" and can be ignored.
If I write programs that generate messages I use IBM's scheme. Each message gets a three char prefix (so you know where it came from), a four digit number (each message is unique) and a one char severity code (I == informational, W == warning, E == error, S == severe & T == terminating). That should become a world wide standard because it doesn't half make it easier to sort the signal from the noise.
Languages using left-hand whitespace for syntax are ridiculous
DMs sent on https://twitter.com/DougieLawson or LinkedIn will be answered next month.
Fake doctors - are all on my foes list.
The use of crystal balls and mind reading is prohibited.