How many system.log entries can you ID?

Discussion in 'Mac Apps and Mac App Store' started by Toe, Feb 9, 2005.

  1. Toe macrumors 65816

    Toe

    Joined:
    Mar 25, 2002
    #1
    If you're not familiar with your system.log file, open Console (in your /Applications/Utilities folder), click on the "Logs" button in the upper-left, then click on "system.log" in the resulting sidebar.

    Sure, I can kinda understand many of the entries in my system.log. But some are semi-confusing, and some are total mysteries.

    If you Google some key phrases, you can find answers to some of these. But for others, all you get is other people (not infrequently on macrumors forums) posting their system.log, asking for help.

    So if you can explain any of these, your exlanation (via this thread) will go into the annals of Googledom, and help people understand arcane mysteries previously known only unto you. :)

    Here are some I am not sure about. Feel free to explain any of these, or any other baffling-looking system.log entries...

    Code:
    Feb  5 21:41:52 localhost loginwindow[185]: sendQuitEventToApp (iTunes Helper): AESendWithMach returned error -609
    Feb  5 21:42:28 localhost kernel: CSRHIDTransitionDriver::start after command - e00002ed
    Feb  5 21:42:28 localhost last message repeated 5 times
    Feb  5 21:42:31 localhost kernel: Jettisoning kernel linker.
    Feb  5 21:42:51 localhost SystemStarter: The "HasShadow" window property is obsolete. Use CGSSetWindowShadowAndRimParameters(cid, wid, 0.0,0.0, 0,0, CGSNoShadowStyle) to turn off the window shadow instead. Set a break-point on CGSLogMessage to find out where this property is set. 
    Feb  5 21:43:14 localhost kernel: [AppleUSBHCIController][StopIsochPipeRead] - mInt1IsochInPipe = 0 - numReadsPending = 0
    Feb  5 22:52:02 localhost kernel: Sound assertion "0 != err" failed in "AppleLegacyAudio/AppleTexas2Audio/AppleTexas2Audio.cpp" at line 960 goto Exit
    Feb  5 22:52:02 localhost kernel: FWOHCI handleSelfIDInt - nodeID not valid (reset bus and retry 1)
    Feb  6 21:05:39 localhost mach_init[2]: Server 0 in bootstrap d03 uid 0: "/usr/libexec/fix_prebinding": exited with non-zero status 1 [pid 402]
    Feb  6 21:29:01 localhost /Applications/Firefox.app/Contents/MacOS/firefox-bin: *** Warning: ATSUSetFontFallbacks has been deprecated.  Use ATSUFontFallbacks objects instead. ***
    Feb  6 23:32:50 localhost /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder: kCGErrorInvalidConnection : CGSWindowAddRegionToDirtyShape: Invalid connection
    Feb  6 23:32:50 localhost /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder: kCGErrorInvalidConnection : CGSFlushWindowContentRegion: Invalid connection
    Feb  6 23:33:46 localhost kernel: [HCIController][RequestPowerStateChange] changePowerStateTo() returned 0x0
    Feb  6 23:33:46 localhost kernel: [HCIController][RequestPowerStateChange] changePowerStateTo(1) returned 0x0
    Feb  6 23:33:46 localhost kernel: [HCIController][PerformPowerStateChange] 0->1
    Feb  6 23:33:47 localhost syslogd: /dev/console: Input/output error
    Feb  9 11:46:18 localhost kernel: handleAirPortChangesChannelWL fails because POWER IS OFF (the mask is correcty set however)
    Feb  9 11:46:18 localhost kernel: AirPort:  Rx'd mesg P-3
    Feb  9 11:46:18 localhost kernel: AirPort:  New Group Key, Idx 1
    Feb  9 11:46:23 localhost mach_init[2]: Server 0 in bootstrap d03 uid 0: "/usr/sbin/lookupd": exited as a result of signal 1 [pid 575]
    Feb  9 11:53:20 localhost kernel: NVDA,Display-A: vram [a0000000:08000000]
    Feb  9 11:53:21 localhost kernel: NVDA,Display-B: vram [00000000:01000000]
    
     
  2. Toe thread starter macrumors 65816

    Toe

    Joined:
    Mar 25, 2002
  3. wrldwzrd89 macrumors G5

    wrldwzrd89

    Joined:
    Jun 6, 2003
    Location:
    Solon, OH
    #4
    Entries 5 and 10 are nothing to worry about. These messages indicate that whoever wrote the application generating these messages hasn't updated their software to conform to the current Apple guidelines.

    Entries 13, 14, and 15 appear completely normal - 0x0 means "exit normally, no errors".

    Entry 7 looks like a bug in Mac OS X. I have no idea what triggered the error message though.

    Entries 17, 18, and 19 appear to be related to AirPort initializing itself - I wouldn't worry about these.

    The rest I haven't a clue.
     
  4. Toe thread starter macrumors 65816

    Toe

    Joined:
    Mar 25, 2002
    #5
    Anybody else wanna take a shot at this?

    If we can actually describe most of these, future Google-searchers will find this a very handy resource...




    1 loginwindow[185]: sendQuitEventToApp (iTunes Helper): AESendWithMach returned error -609
    2 kernel: CSRHIDTransitionDriver::start after command - e00002ed
    3 last message repeated 5 times
    4 kernel: Jettisoning kernel linker.
    5 SystemStarter: The "HasShadow" window property is obsolete. Use CGSSetWindowShadowAndRimParameters(cid, wid, 0.0,0.0, 0,0, CGSNoShadowStyle) to turn off the window shadow instead. Set a break-point on CGSLogMessage to find out where this property is set.
    6 kernel: [AppleUSBHCIController][StopIsochPipeRead] - mInt1IsochInPipe = 0 - numReadsPending = 0
    7 kernel: Sound assertion "0 != err" failed in "AppleLegacyAudio/AppleTexas2Audio/AppleTexas2Audio.cpp" at line 960 goto Exit
    8 kernel: FWOHCI handleSelfIDInt - nodeID not valid (reset bus and retry 1)
    9 mach_init[2]: Server 0 in bootstrap d03 uid 0: "/usr/libexec/fix_prebinding": exited with non-zero status 1 [pid 402]
    10 /Applications/Firefox.app/Contents/MacOS/firefox-bin: *** Warning: ATSUSetFontFallbacks has been deprecated. Use ATSUFontFallbacks objects instead. ***
    11 /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder: kCGErrorInvalidConnection : CGSWindowAddRegionToDirtyShape: Invalid connection
    12 /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder: kCGErrorInvalidConnection : CGSFlushWindowContentRegion: Invalid connection
    13 kernel: [HCIController][RequestPowerStateChange] changePowerStateTo() returned 0x0
    14 kernel: [HCIController][RequestPowerStateChange] changePowerStateTo(1) returned 0x0
    15 kernel: [HCIController][PerformPowerStateChange] 0->1
    16 syslogd: /dev/console: Input/output error
    17 kernel: handleAirPortChangesChannelWL fails because POWER IS OFF (the mask is correcty set however)
    18 kernel: AirPort: Rx'd mesg P-3
    19 kernel: AirPort: New Group Key, Idx 1
    20 mach_init[2]: Server 0 in bootstrap d03 uid 0: "/usr/sbin/lookupd": exited as a result of signal 1 [pid 575]
    21 kernel: NVDA,Display-A: vram [a0000000:08000000]
    22 kernel: NVDA,Display-B: vram [00000000:01000000]
     
  5. wrldwzrd89 macrumors G5

    wrldwzrd89

    Joined:
    Jun 6, 2003
    Location:
    Solon, OH
    #6
    1. Most likely, this is an error report that was generated when you logged out or shut down. Mac OS X tried to quit iTunesHelper, but couldn't because error -609 (invalid connection) occurred.
    2-3. These look like initialization messages from a hardware driver.
    4. I don't know what this means. It appears in my system.log, and my Mac is working just fine.
    5 & 10. These messages are meant purely for the programmer that wrote the program generating them.
    6. Looks to me like finishing communication with a USB device of some sort.
    7. I think this is a bug in Mac OS X.
    8. FireWire device error of some sort, most likely.
    9. fix_prebinding encountered a fatal error, code 1. This might occur if Installer freezes during the Optimizing System Performance stage of software installation.
    11-12. These messages indicate a window refresh problem in the Finder.
    13-15. Some device is requesting a power state change, which occurred successfully.
    16. There was a problem writing data to the console log.
    17-19. Something tried to connect using AirPort, but couldn't because AirPort was turned off. AirPort turned on and configured itself.
    20. I get similar messages to this one all the time in my logs, and I have no idea what they mean.
    21-22. These messages are reporting the VRAM allocation of the graphics card to each display connected to your Mac.
     

Share This Page