Q: G5 kernel problem, Ram OK

Hello again Aqua!  You've helped me before.   However, you may be giving me too much credit. . . no clue what Wake on Lan is. . . guessing the network has something pinging this mac trying to wake it? also, the Bonjour thingie. . . huh?@!  sorry no clue.  Tonight after done I will pull the Ethernet cord and let you know how console response changes.  thanks, so far.

OK.  I have to redefine the problem.   After this happened again I am better equipped to define problem. 

This looks like a failure to come out of sleep mode, not kernel related.  I was off on this because I simply saw the word kernel in the log. . .ha!  Anyway, here is the deal:   The Mac will come out of sleep as long as I don't leave it in that mode long.  SO, if I force it to sleep using the command and few min elapse. . . it will come out of sleep seamlessly via pressing a key.  However, I suspect from a 2nd occurrance last night that when it goes to sleep on its own due to no activity. . . it may be more likely to rev the fans and go nuts-- ie NOT responsive to key input or mouse.  

answers to your questions:   I pullled the plug on E'net last night and it killed the Uninet message.  (I use a DSL MODEM, have a Mac Airport Time Capsule.)

It looks like the mDNS responder message is related to the E'net. . . Failing to find the Domain Name Server . . . continuously or something??

       "3/12/15 11:25:31 AM mDNSResponder[18] ERROR: getOptRdata - unknown opt 65002 "

and, No, I did NOT have Wake for E'net admin access enabled. SO, I enabled it to see if there is a change.  

Before enabling the "Wake" though I have a console script of a few hundred lines with my notes. . . let me know if I should dump it here or attach a file, please.  I'm sure with this new description you might take this in a new direction.   By the way, on my MacBook Air and iMac I use OPEN DNS.  In addition, a review of console logs on the Air shows no messages like this.   Thanks!

OK, tonight I will try to force the event and dump console records. thx.  By the way, I have a bluetooth dongle for my magic mouse. . .  Maybe I will try with bluetooth turned off and repeat with it ON, to see a difference. 

I tried to find evidence of the not waking from sleep "area" on the console records last night and could not find it. . . maybe YOU will be able to see it with more trained eyes!  I notice you are asking for system log; I was monitoring "all messages"-- that may be the reason.

Hello again. . . I tried both with Bluetooth "ON" and Off and could not get it to fail and allowed it to go to sleep.  It has been asleep all afternoon and woke up with no problem.  Odd.  This may take a few days . . . anyway, for now, no problem.  If it arises again, I will ping you on this thread!  thanks!

Hey there BDAqua,

I was able to recreate the problem.  NOW, I at least know the source.   I accidentally touched the USB mouse and it failed to bring the G5 out of sleep but rev the engine to an idle-- about 600 RPM!(kidding).  Then, I figured it out.  I knew if I touched the keyboard, it would do nothing, sure enough.  I went out and returned in 2 hrs and founding the G5 wide open throttle(WOT) on all engines.  Only way to kill it was to push the Start / OFF button down for a few seconds.  SO, it appears to be a problem with the USB mouse pushing the wake up call but the Mac can only respond by go to idle and no-wakey.  Got some ideas?!

. . . forgot to say.  I also use a Magic Mouse, mainly, in fact.   The wired USB mouse is only in case the Magic mouse can't make a Bluetooth connection and I get tired of playing around to get it going.  I go to Bluetooth prefs and tell it to go find it. . .   It is set as discoverable but sometimes it fails to accomplish that big task.

Hello BD. . . OK, new things I've learned:

-- I have had both the wired & wireless mice connected in the past.  I figured there may be a "problem" with that and so, disconnected the wired cheese eater.  Even though it makes things easier when the wireless feller fails to connect after being dormant.  I found that NO problems occur with coming out of sleep for four days.  I have also left the wireless guy "hot"-- normally I turn his belly switch off when done with the computer for a while.  The G5 has been coming out of sleep just fine and no raging fan runs.

-- maybe this solves the problem, just get used to plugging in the wired mouse if I loose connection. . .

-- Regarding your input: well, not sure about the name.  I checked and it showed its normal name in the dialog box but without the .local extension, so I pressed Edit and up popped the .local in gray and I left it that way.

-- as to a new location, not sure why or what the purpose is you are aiming at but I did as you suggested and the following images show present state of network.   Don't forget I signed up for OPEN DNS since we started the conversation. . .

Let me know more background on why the location change and whether to leave it as is please.  thanks!