On Wednesday 19 March 2008, Jon Elson wrote:
>John Thornton wrote:
>> John,
>>
>> No one could possibly guess or assume that the message only prints once.
>> The message needs to be changed to state that it will only appear once.
>
>The version of the message that is written in the system log
>DOES say that.
>
>Jon
>
Humm, for all the messages I have seen on screen, there is only one such 
message in the logs:

Mar 18 17:41:05 localhost kernel: [ 3248.821765] kobject_register failed for 
parport_pc (-17)
Mar 18 17:41:05 localhost kernel: [ 3248.821798]  [kobject_register+69/80] 
kobject_register+0x45/0x50
Mar 18 17:41:05 localhost kernel: [ 3248.821838]  [bus_add_driver+78/160] 
bus_add_driver+0x4e/0xa0
Mar 18 17:41:05 localhost kernel: [ 3248.821854]  [pnp_register_driver+47/96] 
pnp_register_driver+0x2f/0x60
Mar 18 17:41:05 localhost kernel: [ 3248.821869]  [pg0+546189486/1069859840] 
init_module+0x1e/0x80 
[probe_parport]
Mar 18 17:41:05 localhost kernel: [ 3248.821878]  [sys_init_module+158/384] 
sys_init_module+0x9e/0x180
Mar 18 17:41:05 localhost kernel: [ 3248.821889]  [sysenter_past_esp+99/103] 
sysenter_past_esp+0x63/0x67
Mar 18 17:41:05 localhost kernel: [ 3248.831012] config string '0x378'

Mar 18 17:41:07 localhost kernel: [ 3250.686350] RTAPI: ERROR: Unexpected 
realtime delay on task 1
Mar 18 17:41:07 localhost kernel: [ 3250.691958] 1631: ERROR: Unexpected 
realtime delay: check dmesg for 
details.
Mar 18 17:41:07 localhost kernel: [ 3250.691970]
Mar 18 17:41:07 localhost kernel: [ 3250.691971] In recent history there were
Mar 18 17:41:07 localhost kernel: [ 3250.691973] 1600992, 1395691, 1401153, 
1400095, and 1405671
Mar 18 17:41:07 localhost kernel: [ 3250.691975] elapsed clocks between calls 
to the motion controller.
Mar 18 17:41:07 localhost kernel: [ 3250.691979] This time, there were 1682846 
which is so anomalously
Mar 18 17:41:07 localhost kernel: [ 3250.691981] large that it probably 
signifies a problem with your
Mar 18 17:41:07 localhost kernel: [ 3250.691991] realtime configuration.  For 
the rest of this run of
Mar 18 17:41:07 localhost kernel: [ 3250.691993] EMC, this message will be 
suppressed.
Mar 18 17:41:07 localhost kernel: [ 3250.691994]

I do not know what I had the base_thread set at when that single instance
occured.  I believe that was the one time when I actually had 2 popups to
clear before I could enable emc at startup time.  Normally there is only one.

FWIW, I always see the fail line I started this log clip with, nominally
1.8 seconds before the RTAPI message.  Possible clue?  Damnifiknow...

I also wonder why the log was rotated this morning, its not Sunday.
Does kubuntu do that differently? ntpd is running and the time is correct.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
heavy, adj.:
        Seduced by the chocolate side of the force.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users

Reply via email to