|
Replies
:
52
-
Last Post
:
Jun 10, 2009 7:39 AM
by: Guypwill
|
|
|
Posts:
17
Registered:
Jan 8, 2007
|
|
|
AppleYukon2
Posted:
May 14, 2009 4:14 PM
|
|
|
hello.
After recently updating my OS to 10.5.7, I began seeing this in my system log:
May 14 17:41:01 Q kernel[0]: AppleYukon2: 00000001,00000000 sk98nif - deadmanCheck - nothing received, resetting chip
May 14 17:41:05 Q kernel[0]: Ethernet AppleYukon2: Link up on en0, 100-Megabit, Full-duplex, Symmetric flow-control, Debug 796d,6f08,0de1,0200,45e1,4000
May 14 17:44:05 Q kernel[0]: AppleYukon2: 00000001,00000000 sk98nif - deadmanCheck - nothing received, resetting chip
May 14 17:44:09 Q kernel[0]: Ethernet AppleYukon2: Link up on en0, 100-Megabit, Full-duplex, Symmetric flow-control, Debug 796d,6f08,0de1,0200,45e1,4000
May 14 17:47:09 Q kernel[0]: AppleYukon2: 00000001,00000000 sk98nif - deadmanCheck - nothing received, resetting chip
May 14 17:47:13 Q kernel[0]: Ethernet AppleYukon2: Link up on en0, 100-Megabit, Full-duplex, Symmetric flow-control, Debug 796d,6f08,0de1,0200,45e1,4000
May 14 17:50:12 Q kernel[0]: AppleYukon2: 00000001,00000000 sk98nif - deadmanCheck - nothing received, resetting chip
May 14 17:50:16 Q kernel[0]: Ethernet AppleYukon2: Link up on en0, 100-Megabit, Full-duplex, Symmetric flow-control, Debug 796d,6f08,0de1,0200,45e1,4000
May 14 17:53:16 Q kernel[0]: AppleYukon2: 00000001,00000000 sk98nif - deadmanCheck - nothing received, resetting chip
May 14 17:53:20 Q kernel[0]: Ethernet AppleYukon2: Link up on en0, 100-Megabit, Full-duplex, Symmetric flow-control, Debug 796d,6f08,0de1,0200,45e1,4000
Before turning to this forum I did a little troubleshooting and this is what I discovered:
- this happens only when connected to a network
- this happens every 3 minutes only when the network is idle
- using Little Snitch, configd is connecting to ff02::2 everytime, and DirectoryService is hitting my nameservers
- watching the Activity Monitor shows 35 bytes being transmitted 5 times at the beginning of this 3 minute cycle
I have repaired all permissions.
I have rebooted several times.
My system is setup as dual boot using rEFIt.
What can I do to stop this?
Please help, thanks!
MacBookPro 2.4 GHz Intel Core 2 Duo
Mac OS X (10.5.7)
2 GB 667 Mhz DDR2 SDRAM
|
|
|
Posts:
3,823
From:
UK
Registered:
Oct 31, 2005
|
|
|
Re: AppleYukon2
Posted:
May 14, 2009 4:31 PM
in response to: m1k3l0w
|
|
|
Hi
Set the Configure IPv6 option to off. Apply the changes and restart.
Tony
|
|
|
|
Posts:
17
Registered:
Jan 8, 2007
|
|
|
Re: AppleYukon2
Posted:
May 14, 2009 9:53 PM
in response to: Antonio Rocco
|
|
|
ok.
I tried what you suggested.
I am still receiving the same system log at the same intervals.
How can I troubleshoot this further?
Mac OS X (10.5.7)
|
|
|
|
Posts:
3,823
From:
UK
Registered:
Oct 31, 2005
|
|
|
Re: AppleYukon2
Posted:
May 15, 2009 10:26 AM
in response to: m1k3l0w
|
|
|
Hi
System Preferences > Network > Ethernet > Advanced > Ethernet. Are the settings set to Automatic?
Tony
|
|
|
|
Posts:
3,823
From:
UK
Registered:
Oct 31, 2005
|
|
|
Re: AppleYukon2
Posted:
May 15, 2009 3:31 PM
in response to: m1k3l0w
|
|
|
Hello Mike
Your OP listed:
". . . configd is connecting to ff02::2 everytime . . ."
As I understand it the ff bit is an example of a Multicast IPv6 address. The log only appears when connected to the network. Perhaps the update has added an ability to log this activity? I can't find anything referring to this for the update itself:
http://support.apple.com/kb/HT3397
Although it could be part of the security fix? Perhaps it's a problem with Little Snitch or possibly Growl? If you have it installed? What if you were to uninstall any 3rd-Party stuff just to see if anything changes?
Beyond what's already been offered I've not got much left. I've done the update myself and don't see what you see. Apart from what's in the logs is there actually a problem?
Tony
|
|
|
|
Posts:
17
Registered:
Jan 8, 2007
|
|
|
Re: AppleYukon2
Posted:
May 15, 2009 4:03 PM
in response to: Antonio Rocco
|
|
|
Thanks for your help Antonio.
The major problem is that if I leave my computer on all night the system log fills with these annoying entries. Plus, seeing network activity every 3 minutes can get annoying and frustrating.
I installed Little Snitch just to troubleshoot this problem. Otherwise I have no other 3rd party software running at that level.
The other interesting thing is, when I take the Ethernet setting off automatic, it will not connect, and says the cable is unplugged.
The way I see it is thus:
The network interface card in my laptop is resetting itself every 3 minutes when the network is idle.
How can I find out more about this AppleYukon2?
Is there a service I can turn off?
Is it time to call Apple?
Thanks again for your help.
|
|
|
|
Posts:
3,823
From:
UK
Registered:
Oct 31, 2005
|
|
|
Re: AppleYukon2
Posted:
May 15, 2009 4:18 PM
in response to: m1k3l0w
|
|
|
Hello Mike
Perhaps a hardware fault has developed that just happened to coincide with the recent update? Perhaps the update itself has caused the problem?
I suppose to eliminate the possibility of an intermittent hardware fault you could manually download the 10.5.7 combo update and run it again? If the log entries persist boot from the Installer Disk and archive and install. If the log entries go away then you can could be fairly certain it's not a hardware fault although it would make sense to monitor it for a short while. When you're confident you could download and run the 10.5.6 update. Test again. When you're ready manually download the 10.5.7 update and test again.
Tony
|
|
|
|
Posts:
17
Registered:
Jan 8, 2007
|
|
|
Re: AppleYukon2
Posted:
May 15, 2009 4:55 PM
in response to: Antonio Rocco
|
|
|
Will do.
I'll report my progress.
|
|
|
|
Posts:
17
Registered:
Jan 8, 2007
|
|
|
Re: AppleYukon2
Posted:
May 16, 2009 9:09 AM
in response to: m1k3l0w
|
|
|
I have re-installed the stand alone update, and no go on solving my problem.
|
|
|
|
Posts:
8
Registered:
Mar 2, 2009
|
|
|
Re: AppleYukon2
Posted:
May 15, 2009 10:20 AM
in response to: m1k3l0w
|
|
|
I am seeing the same thing as m1k3l0w:
09/05/15 07:16:12 kernel Ethernet AppleYukon2: Link up on en0, 100-Megabit, Full-duplex, No flow-control, Debug 796d,6c08,0de1,0200,41e1,4000
09/05/15 07:16:14 mDNSResponder15 Note: Frequent transitions for interface en0 (192.168.0.101); network traffic reduction measures in effect
09/05/15 07:19:13 kernel AppleYukon2: 00000001,00000000 sk98nif - deadmanCheck - nothing received, resetting chip
I can confirm that this started after the upgrade to 10.5.7.
Curiously, this is not happening on my wife’s iMac, even though we both have 2.4 GHz 24" Intel iMacs.
2.4 GHz 24" Intel iMac
Mac OS X (10.5.7)
|
|
|
|
Posts:
2
Registered:
May 16, 2009
|
|
|
Re: AppleYukon2
Posted:
May 16, 2009 2:04 AM
in response to: PeterSchoenrank
|
|
|
Hello All,
I also confirm that the AppleYukon2 error log appeared after 10.5.7 update.
My main log system errors are :
kernel[0]: AppleYukon2: error - FATAL: SkGeStopPort() does not terminate (Rx)
kernel[0]: AppleYukon2: error - Event queued in Init Level 0
kernel[0]: Ethernet AppleYukon2: Link up on en0, 100-Megabit, Full-duplex, No flow-control
AppleYukon2: 00000001,00000000 sk98nif - deadmanCheck - nothing received, resetting chip
My Ethernet driver connection seems to work as before.
The only thing I could find out until now is that this may be related
to the extension software in :
/System/Library/Extensions/IONetworkingFamily.kext/Contents/PlugIns/AppleYukon2.kext
Related to Apple Yukon Ethernet 3.1.12b14, Copyright 2007 Apple Inc., and Marvell
I aslo have regular system.log errors, each time that there is an input / output network connection.
I am exploring if :
-> I have to consider the messages seriously.
-> How can I fix the problem, even if I don't have network processes failures.
Best Regards.
iMac, MacMini, MacBook Pro
Mac OS X (10.5.7)
Intel Based
|
|
|
|
Posts:
3
From:
Canada
Registered:
Mar 22, 2009
|
|
|
Re: AppleYukon2
Posted:
May 16, 2009 3:10 AM
in response to: AntonyMac
|
|
|
Me too on log messages...Mac Mini as OS X Server 10.5.7. Also getting this in the log...
mDNSResponder30: Note: Frequent transitions for interface en0 (xxx.xxx.xxx.xxx); network traffic reduction measures in effect
I doubt it could be hardware for all of us at once.
Mac Mini
Mac OS X (10.5.7)
Server
|
|
|
|
Posts:
7
From:
Poland
Registered:
May 16, 2009
|
|
|
Re: AppleYukon2
Posted:
May 16, 2009 4:18 AM
in response to: T Highmoor
|
|
|
the same me. I have two comps connected together WinXP and Leo 10.5.7 on macbook. Everything have worked great but after update I've network reset every 3-5 minutes if it's idle. When I transfer large files over this network it seems to work great.
maybe it's possible to turn off these Ethernet resetting?
MacBook pro
Mac OS X (10.5.7)
|
|
|
|
Posts:
2
Registered:
May 16, 2009
|
|
|
Re: AppleYukon2
Posted:
May 16, 2009 6:19 AM
in response to: pabloscotty
|
|
|
In addition to my previous :
I think that the most important thing above all
is to understand what AppleYukon2 actually is and its main purpose.
iMac, MacMini, MacBook Pro
Mac OS X (10.5.7)
Intel Based
|
|
|
|
Posts:
7
From:
Poland
Registered:
May 16, 2009
|
|
|
Re: AppleYukon2
Posted:
May 16, 2009 7:41 AM
in response to: pabloscotty
|
|
|
It's strange because I've transferred 30gb over that LAN and know there is no message logs and no connection lost. I'll try to restart and see what happen.
Message was edited by: pabloscotty
MacBook pro
Mac OS X (10.5.7)
|
|
|
|
Posts:
7
From:
Poland
Registered:
May 16, 2009
|
|
|
Re: AppleYukon2
Posted:
May 16, 2009 7:47 AM
in response to: pabloscotty
|
|
|
...it's back
MacBook pro
Mac OS X (10.5.7)
|
|
|
|
Posts:
7
From:
Poland
Registered:
May 16, 2009
|
|
|
Re: AppleYukon2
Posted:
May 18, 2009 12:41 AM
in response to: pabloscotty
|
|
|
anyone?
MacBook pro
Mac OS X (10.5.7)
|
|
|
|
Posts:
89
Registered:
Nov 7, 2007
|
|
|
Re: AppleYukon2
Posted:
May 24, 2009 8:11 PM
in response to: PeterSchoenrank
|
|
|
Yea here too:
May 24 20:40:49 ns1 kernel[0]: AppleYukon2: 00000001,00000000 sk98nif - deadmanCheck - nothing received, resetting chip
May 24 20:40:51 ns1 kernel[0]: AppleYukon2: error - Event scheduler called in Init Level 0 or 1
May 24 20:40:51: --- last message repeated 9 times ---
May 24 20:40:51 ns1 kernel[0]: AppleYukon2: error - FATAL: SkGeStopPort() does not terminate (Rx)
May 24 20:40:51 ns1 kernel[0]: AppleYukon2: error - Event queued in Init Level 0
May 24 20:40:54 ns1 kernel[0]: Ethernet AppleYukon2: Link up on en0, 1-Gigabit, Full-duplex, Symmetric flow-control, Debug 796d,ac0c,0de1,0200,c5e1,7c00
Started after 10.5.7 according to the logs. Most annoying...running OS X Server on a Mac Mini.
|
|
|
|
Posts:
10
Registered:
Jul 19, 2004
|
|
|
Re: AppleYukon2
Posted:
May 18, 2009 2:17 AM
in response to: m1k3l0w
|
|
|
I've also noticed this problem. Happens every 45 minutes to an hour, and certainly seems to be linked to the 10.5.7 update. I'm currently running my connection from an Airport Extreme connected with an ethernet cable. What are you running your connection through?
iMac 2007
Mac OS X (10.5.7)
|
|
|
|
Posts:
7
From:
Poland
Registered:
May 16, 2009
|
|
|
Re: AppleYukon2
Posted:
May 18, 2009 3:40 AM
in response to: Carolyn Samit
|
|
|
I've noticed then I open any of my shared MAC folders from Windows XP side to establish connection with my macbook pro. Then problem is gone. So that means Leo 10.5.7 is resetting periodically ethernet chip only if there is no connection active, or lan is in IDLE.
So try to open one of yours shared folders from the other side of lan, leave it open and you see that connection is now stable.
Unfortunately I don't know what to do if you are connecting to any router... airport
MacBook pro
Mac OS X (10.5.7)
|
|
|
|
Posts:
129
From:
Troy, AL
Registered:
Oct 24, 2001
|
|
|
Re: AppleYukon2
Posted:
May 18, 2009 10:48 AM
in response to: pabloscotty
|
|
|
I'm pretty sure whatever this 'problem' is it was introduced in the latest 10.5.7 update. I actually only updated a day or so ago and started seeing this in my logs this morning.
I doubt that Little Snitch is causing this since I don't have it installed.
Aside from spamming up the log file, is this causing any problems for anyone? I didn't notice anything wrong while using my Macbook this morning. Everything connected fine. Perhaps it is a power-saving feature or something got messed up in the latest update.
MacBook (Early 2008) 2.1GHz ( OCZ Vertex SSD)
Mac OS X (10.5.7)
Powermac G3 1.2GHz / 1GB / 2x80GB / Radeon 9200 ME / USB 2.0 ; iPod Touch 8GB
|
|
|
|
Posts:
129
From:
Troy, AL
Registered:
Oct 24, 2001
|
|
|
Re: AppleYukon2
Posted:
May 19, 2009 1:17 PM
in response to: Thomas M
|
|
|
I've switched over to using my wireless network for now. I was wondering if anyone had any more info on this, as of yet.
MacBook (Early 2008) 2.1GHz ( OCZ Vertex SSD)
Mac OS X (10.5.7)
Powermac G3 1.2GHz / 1GB / 2x80GB / Radeon 9200 ME / USB 2.0 ; iPod Touch 8GB
|
|
|
|
Posts:
9
Registered:
Mar 18, 2005
|
|
|
Re: AppleYukon2
Posted:
May 18, 2009 4:05 AM
in response to: m1k3l0w
|
|
|
Hi, I have same issue, even under fresh install!!
MyPost = http://discussions.apple.com/thread.jspa?threadID=2008912
I have confirmed this ethernet issue is occured under my iMac Early 2006 and MacBookPro 2.4GHz.
Both seems to use AppleYukon2 chip and System.log shows:
- "deadmanCheck - nothing received, resetting chip"
I am sure this is not hardware fault, because if I boot them in second Tiger partition, they work well.
Also No thirdparty issue because it is reproducible under fresh install environment from DVD + 10.5.7 Combo updater.
Apple folks,
- It causes intermittent link down on ethernet connection... server connection could gone... big impact! Please make updater soon.
iMac Early 2006
Mac OS X (10.5.7)
|
|
|
|
Posts:
8
Registered:
Mar 2, 2009
|
|
|
Re: AppleYukon2
Posted:
May 19, 2009 3:55 PM
in response to: m1k3l0w
|
|
|
I believe the AppleYukon2 "deadmanCheck" issue only concerns laptops using the "Marvell Yukon Gigabit Adapter 88E8055 Singleport Copper SA".
In my post of 15 May you can see that I am using a 24" Intel iMac. In MyCometG3’s post of 18 May, s/he says s/he is using an early 2006 iMac. So no, I don’t think the problem is limited to laptops. It may be limited to the Marvell Yukon Gigabit Adapter, but I don’t have any way to check that.
|
|
|
|
Posts:
8
Registered:
Mar 2, 2009
|
|
|
Re: AppleYukon2
Posted:
May 19, 2009 7:20 PM
in response to: m1k3l0w
|
|
|
m1k3l0w wrote:
... kernel[0]: AppleYukon2: Marvell Yukon Gigabit Adapter 88E8055 Singleport Copper SA
... kernel[0]: AppleYukon2: RxRingSize <= 1024, TxRingSize 256, RX_MAX_LE 1024, TX_MAX_LE 768, ST_MAX_LE 3328
Yes, that is in the system.log shortly after rebooting.
|
|
|
|
Posts:
1
From:
Normal IL
Registered:
May 21, 2009
|
|
|
Re: AppleYukon2
Posted:
May 21, 2009 11:10 AM
in response to: m1k3l0w
|
|
|
I can confirm that this also happens on my iMac 20", dating to 2006, and occurred only after 10.5.7 was installed last week. The messages in my system log are:
AppleYukon2: 00000001,00000000 sk98nif - deadmanCheck - nothing received, resetting chip
AppleYukon2: error - Event scheduler called in Init Level 0 or 1
--- last message repeated 9 times ---
AppleYukon2: error - FATAL: SkGeStopPort() does not terminate (Rx)
AppleYukon2: error - Event queued in Init Level 0
Ethernet AppleYukon2: Link up on en0, 100-Megabit, Full-duplex, No flow-control, Debug 796d,6d00,0de1,0200,41e1,4000
and repeat every 3 to 10 minutes. The iMac is connected by ethernet to an Airport which is connected to a cable modem. The iMac also has internal Airport, but I've shut it off for now and the messages still appear. My network connection doesn't appear to be suffering, but I don't do anything that requires high bandwidth; web response is good.
iMac 20"
Mac OS X (10.5.7)
MacBook, iMac snowdome
|
|
|
|
Posts:
4
Registered:
Jul 25, 2008
|
|
|
Re: AppleYukon2
Posted:
May 21, 2009 2:43 PM
in response to: spjk
|
|
|
In my case (early 2006 20" iMac), the ethernet port is used to connect using AppleTalk through an AsanteTalk adapter to my old trusty Apple LaserWriter 4/600 PS printer. The connection gets a self-assigned IP address. At boot time, there is a system log entry "kernel[0]: AppleYukon2: Marvell Yukon Gigabit Adapter 88E8053 Singleport Copper SA".
I connect to the internet through an airport connection and a Netgear DG834v2 modem/router. Parallels Shared Networking Adapter and Parallels Host-Only Networking Adapter connections are on.
This network arrangement worked perfectly under 10.5.6. After the 10.5.7 Combo update, every 1m34s when the printer is idle the ethernet (en0) connection disconnects, then reconnects by itself and the system log gets flooded with the following messages:
May 20 23:57:16 dbms-imac kernel[0]: AppleYukon2: 00000001,00000000 sk98nif - deadmanCheck - nothing received, resetting chip
May 20 23:57:16 dbms-imac configd34: AppleTalk shutdown
May 20 23:57:18 dbms-imac kernel[0]: AppleYukon2: error - Event scheduler called in Init Level 0 or 1
May 20 23:57:18 dbms-imac kernel[0]: AppleYukon2: error - Event scheduler called in Init Level 0 or 1
May 20 23:57:18: --- last message repeated 8 times ---
May 20 23:57:18 dbms-imac kernel[0]: AppleYukon2: error - FATAL: SkGeStopPort() does not terminate (Rx)
May 20 23:57:18 dbms-imac kernel[0]: AppleYukon2: error - Event queued in Init Level 0
May 20 23:57:18 dbms-imac configd34: AppleTalk shutdown complete
May 20 23:57:20 dbms-imac kernel[0]: AppleYukon2: error - Link Partner not Auto-Neg. able
May 20 23:57:20 dbms-imac configd34: AppleTalk startup
May 20 23:57:20 dbms-imac kernel[0]: AppleYukon2: 00000000,00000000 skgehw - cppSkDrvEvent - SK_DRV_LIPA_NOT_AN_ABLE: link partner not auto-negotiate capable, port, phy r6
May 20 23:57:20 dbms-imac kernel[0]: Ethernet AppleYukon2: Link up on en0, 10-Megabit, Half-duplex, No flow-control, Debug 796d,0d40,0de1,0200,0021,0000
May 20 23:57:26 dbms-imac configd34: AppleTalk startup complete
The airport and Parallels adapter connections are stable and work normally whether idle or in use, but apparently, 10.5.7 does not allow an idle ethernet connection ("deadmanCheck") for more than 1m34s. It makes no difference which method I choose to configure IPv4 or whether IPv6 configuration is set to Automatic, manual or off. Despite the cyclic ethernet malfunction, I can use the printer normally. The disorder continues with AppleTalk off, but the message floods no longer contain AppleTalk entries (and I can't use the printer).
My current workaround is to turn off the ethernet connection when not using the printer - the system log message flood then stops. It's annoying to have to manually turn on the ethernet connection to print, but equally annoying to have the error message flood if I leave it on. It would be even more annoying to have to manually turn on ethernet to access the internet if the port were used for that purpose.
iMac core duo 20"
Mac OS X (10.5.7)
|
|
|
|
Posts:
1,078
From:
Midwest
Registered:
Sep 15, 2000
|
|
|
Re: AppleYukon2
Posted:
May 21, 2009 5:00 PM
in response to: spjk
|
|
|
I see the same thing on my Intel iMac running 10.5.7. It's some sort of daemon apparently. It has NOT affected my connection in any way that I can discern and I am ignoring it as of now. Logs rotate daily, weekly, monthly so it not an issue really. Some immensely intelligent genius will figure out what it all means eventually or it will be gone in some future update. I don't really care.
Aluminum 24" iMac (2.8Ghz Intel Penryn)
Mac OS X (10.5.7)
Apple TV 2.3.1 / Sharp Aquos 46" HDTV
|
|
|
|
Posts:
5
Registered:
Sep 15, 2006
|
|
|
Re: AppleYukon2
Posted:
May 23, 2009 3:43 PM
in response to: m1k3l0w
|
|
|
I have the same issue on my macbook. Ethernet resets or seems to "go dead" to the point I am forced to use my slower wireless connection. I'm getting the same exact errors in my system.log.
May 23 15:35:30 macbook kernel[0]: AppleYukon2: 00000001,00000000 sk98nif - deadmanCheck - nothing received, resetting chip
May 23 15:35:32 macbook kernel[0]: AppleYukon2: error - Event scheduler called in Init Level 0 or 1
May 23 15:35:32: --- last message repeated 9 times ---
May 23 15:35:32 macbook kernel[0]: AppleYukon2: error - FATAL: SkGeStopPort() does not terminate (Rx)
May 23 15:35:32 macbook kernel[0]: AppleYukon2: error - Event queued in Init Level 0
May 23 15:35:35 macbook kernel[0]: Ethernet AppleYukon2: Link up on en0, 100-Megabit, Full-duplex, Symmetric flow-control, Debug 796d,6d4c,0de1,0200,45e1,4000
May 23 15:36:05 macbook kernel[0]: AppleYukon2: 00000000,00000000 skgehw - cppSkDrvEvent - SK_DRV_RX_OVERFLOW: rcv fifo overflow
May 23 15:37:05 macbook kernel[0]: AppleYukon2: 00000001,00000000 sk98nif - deadmanCheck - nothing received, resetting chip
May 23 15:37:07 macbook kernel[0]: AppleYukon2: error - Event scheduler called in Init Level 0 or 1
May 23 15:37:07: --- last message repeated 9 times ---
May 23 15:37:07 macbook kernel[0]: AppleYukon2: error - FATAL: SkGeStopPort() does not terminate (Rx)
May 23 15:37:07 macbook kernel[0]: AppleYukon2: error - Event queued in Init Level 0
May 23 15:37:10 macbook kernel[0]: Ethernet AppleYukon2: Link up on en0, 100-Megabit, Full-duplex, Symmetric flow-control, Debug 796d,6d4c,0de1,0200,45e1,4000
May 23 15:37:40 macbook kernel[0]: AppleYukon2: 00000000,00000000 skgehw - cppSkDrvEvent - SK_DRV_RX_OVERFLOW: rcv fifo overflow
Message was edited by: ne0shell
macbook
Mac OS X (10.5.7)
|
|
|
|
Posts:
7
From:
Poland
Registered:
May 16, 2009
|
|
|
|
|
Posts:
17
Registered:
Jan 8, 2007
|
|
|
Re: AppleYukon2
Posted:
May 24, 2009 11:06 AM
in response to: pabloscotty
|
|
|
Hey Pablo,
I am sorry to say that what you suggested did not work for me.
MacBookPro 2.4 GHz Intel Core 2 Duo
Mac OS X (10.5.7)
2 GB 667 MHz DDR2 SDRAM
|
|
|
|
Posts:
4
Registered:
Jul 25, 2008
|
|
|
Re: AppleYukon2
Posted:
May 24, 2009 9:44 PM
in response to: pabloscotty
|
|
|
I followed Pablo's solution carefully twice, but it does not work for me either. I still have to turn off Ethernet (en0) to stop the message flood, otherwise it cyclically resets itself and gives the error messages.
Regards
iMac core duo 20"
Mac OS X (10.5.4)
|
|
|
|
Posts:
129
From:
Troy, AL
Registered:
Oct 24, 2001
|
|
|
Re: AppleYukon2
Posted:
May 25, 2009 8:00 AM
in response to: pabloscotty
|
|
|
I was so happy to learn about a solution that I immediately gave it a try. Sadly, it does not work for me either. I still get the deadmancheck messages in the log as usual. Nothing really changed, as far as I can tell.
Thanks for pointing that potential solution out, though.
MacBook (Early 2008) 2.1GHz ( OCZ Vertex SSD)
Mac OS X (10.5.7)
Powermac G3 1.2GHz / 1GB / 2x80GB / Radeon 9200 ME / USB 2.0 ; iPod Touch 8GB
|
|
|
|
Posts:
11
From:
La-La-Land
Registered:
Jun 7, 2002
|
|
|
Re: AppleYukon2
Posted:
Jun 2, 2009 9:19 AM
in response to: m1k3l0w
|
|
|
Hi guys. Sorry to hear you are having problems, but I'm glad I'm not alone. I finally had to turn of Hardware Growler this morning because of the constant stream of alerts on my screen. It just got to be too much.
I too tried the potential fix and it didn't help.
iMac
Mac OS X (10.5.6)
3.06 Ghz Intel Core 2 Duo 4GB RAM
|
|
|
|
Posts:
2
Registered:
Feb 6, 2009
|
|
|
Re: AppleYukon2
Posted:
Jun 2, 2009 10:48 AM
in response to: Mr. Bob Dobolina
|
|
|
I also noticed this problem only because of the hardware growler which fills the screens with messages. And the solutions above also didn't help for me.
My "solution" is to keep the connection up, i.e. ping my home router from the terminal:
$ ping -i 89 <router address>
This is a crude solution (more of a workaround), but it works for me.
iMac
Mac OS X (10.5.7)
|
|
|
|
Posts:
11
From:
La-La-Land
Registered:
Jun 7, 2002
|
|
|
Re: AppleYukon2
Posted:
Jun 2, 2009 10:51 AM
in response to: irush
|
|
|
I was thinking about doing something like that as well, but I just don't feel like it's a good use of resources.
iMac
Mac OS X (10.5.6)
3.06 Ghz Intel Core 2 Duo 4GB RAM
|
|
|
|
Posts:
10
Registered:
Jul 19, 2004
|
|
|
Re: AppleYukon2
Posted:
Jun 3, 2009 4:32 PM
in response to: Mr. Bob Dobolina
|
|
|
Has anyone noticed an improvement since the iTunes update? I don't want to jinx anything but my wireless connections have been rock solid since then (as opposed to going every 30-60 minutes) and there is no evidence of disconnect in console. Any change (+/-) since then for anyone else?
iMac 2007
Mac OS X (10.5.7)
|
|
|
|
Posts:
17
Registered:
Jan 8, 2007
|
|
|
Re: AppleYukon2
Posted:
Jun 3, 2009 5:16 PM
in response to: Jed Johnson
|
|
|
Hello Jed,
I originally started this thread and I am still receiving the same entry in my system log every 3 minutes when my network is idle.
This has absolutely nothing to do with iTunes and is not a wireless problem.
MacBookPro 2.4 GHz Intel Core 2 Duo
Mac OS X (10.5.7)
2 GB 667 MHz DDR2 SDRAM
|
|
|
|
Posts:
1
From:
Pennsylvania, USA
Registered:
Jun 4, 2009
|
|
|
Re: AppleYukon2
Posted:
Jun 4, 2009 5:52 AM
in response to: m1k3l0w
|
|
|
I'm having the same problem, but mine has more side affects than a log being filled up.
When a client of mine dials up to my internet connection and the ethernet is active (for network print functionality) the system.log will show a yukon2 deadman check, setting up hostname macintosh.local and then I'm disconnected from the internet, approximately after 3 minutes of being connected. If I disable my ethernet adapter, I can stay connected indefinitely.
Apple support was not able to provide a solution and said by design you can only use one network interface at a time. This worked fine prior to 10.5.7
Macbook
Mac OS X (10.5.7)
|
|
|
|
Posts:
16
Registered:
Jun 27, 2006
|
|
|
Re: AppleYukon2
Posted:
Jun 4, 2009 6:06 AM
in response to: trevorprokop
|
|
|
I'm trying the following fix:
- Downloaded Pacifist utility.
- Downloaded Mac OS X 10.5.6 Combo Updater from Apple.
- Opened the updater package with Pacifist, located the AppleYukon2.kext file inside /System/Library/Extensions/IONetworkingFamily.kext/Contents/PlugIns
- Right click on AppleYukon2.kext file and selected Extract to default.
- Confirmed some overwrite messages from Pacifist.
- Next... from Terminal: touch /System/Library/Extensions
- Next... Repair disk permissions.
- Next... Reboot.
Writing this post with this fix applied. Networking seems to have been fixed.
I'll post some news in a few hours of test.
20" 2.4 GHz. Intel Core 2 Duo iMac
Mac OS X (10.5.7)
|
|
|
|
Posts:
16
Registered:
Jun 27, 2006
|
|
|
Re: AppleYukon2
Posted:
Jun 4, 2009 12:09 PM
in response to: m1k3l0w
|
|
|
I can confirm that this fix is working for some hours.
Just for your information, what you are doing with this fix is to return using the previous AppleYukon2 driver present on Mac OS X 10.5.6
Steps to fix the issue:
- Download Pacifist utility from http://www.charlessoft.com
- Download Mac OS X 10.5.6 Combo Updater from Apple at http://www.apple.com/downloads/macosx/apple/macosx_updates/macosx1056comboupdate.html
- Run Pacifist, wait some seconds to run it if you are not a registered user.
- Mount the Mac OS X 10.5.6 Combo Updater downloaded from Apple.
- Open the updater package with Pacifist, located the AppleYukon2.kext file inside /System/Library/Extensions/IONetworkingFamily.kext/Contents/PlugIns
- Right click on AppleYukon2.kext file and select Install to Default Location option.
- Confirmed all overwrite messages from Pacifist.
- Open Terminal and run the following: sudo touch /System/Library/Extensions
- Open Disk Utility and Repair disk permissions.
- Reboot the computer.
Now you are using the AppleYukon2 driver present on the previous Mac OS X 10.5.6 system.
20" 2.4 GHz. Intel Core 2 Duo iMac
Mac OS X (10.5.7)
|
|
|
|
Posts:
16
Registered:
Jun 27, 2006
|
|
|
Re: AppleYukon2
Posted:
Jun 5, 2009 5:11 PM
in response to: tdttester
|
|
|
The fix that I explained in my last post is working right.
The issue, al least in my case, was originated on something new in the latest drivers of the Ethernet card (Marvell Yukon) present at Mac OS X 10.5.7 update.
So, in my case I have rolled back these drivers to the previous version present at Mac OS X 10.5.6 as I explained in the prodedure.
No problems for now.
Mac OS X (10.5.7)
|
|
|
|
Posts:
10
From:
NH
Registered:
Jun 4, 2009
|
|
|
Re: AppleYukon2
Posted:
Jun 10, 2009 7:39 AM
in response to: tdttester
|
|
|
The fix didn't work for me. Followed the instructions and all seemed well but here are my logs.
6/10/09 9:20:16 AM kernel AppleYukon2: 00000001,00000000 sk98nif - deadmanCheck - nothing received, resetting chip
6/10/09 9:20:20 AM kernel Ethernet AppleYukon2: Link up on en0, 100-Megabit, Full-duplex, Symmetric flow-control, Debug 796d,6f48,0de1,0200,45e1,4000
6/10/09 9:29:20 AM kernel AppleYukon2: 00000001,00000000 sk98nif - deadmanCheck - nothing received, resetting chip
6/10/09 9:29:24 AM kernel Ethernet AppleYukon2: Link up on en0, 100-Megabit, Full-duplex, Symmetric flow-control, Debug 796d,6f08,0de1,0200,45e1,4000
6/10/09 9:38:24 AM kernel AppleYukon2: 00000001,00000000 sk98nif - deadmanCheck - nothing received, resetting chip
6/10/09 9:38:28 AM kernel Ethernet AppleYukon2: Link up on en0, 100-Megabit, Full-duplex, Symmetric flow-control, Debug 796d,6f48,0de1,0200,45e1,4000
6/10/09 9:41:28 AM kernel AppleYukon2: 00000001,00000000 sk98nif - deadmanCheck - nothing received, resetting chip
6/10/09 9:41:31 AM kernel Ethernet AppleYukon2: Link up on en0, 100-Megabit, Full-duplex, Symmetric flow-control, Debug 796d,6f48,0de1,0200,45e1,4000
6/10/09 9:44:31 AM kernel AppleYukon2: 00000001,00000000 sk98nif - deadmanCheck - nothing received, resetting chip
6/10/09 9:44:35 AM kernel Ethernet AppleYukon2: Link up on en0, 100-Megabit, Full-duplex, Symmetric flow-control, Debug 796d,6f08,0de1,0200,45e1,4000
6/10/09 9:50:35 AM kernel AppleYukon2: 00000001,00000000 sk98nif - deadmanCheck - nothing received, resetting chip
6/10/09 9:50:39 AM kernel Ethernet AppleYukon2: Link up on en0, 100-Megabit, Full-duplex, Symmetric flow-control, Debug 796d,6f48,0de1,0200,45e1,4000
6/10/09 9:58:09 AM kernel AppleYukon2: 00000001,00000000 sk98nif - deadmanCheck - nothing received, resetting chip
6/10/09 9:58:13 AM kernel Ethernet AppleYukon2: Link up on en0, 100-Megabit, Full-duplex, Symmetric flow-control, Debug 796d,6f08,0de1,0200,45e1,4000
6/10/09 9:58:16 AM mDNSResponder23 Note: Frequent transitions for interface en0 (192.168.1.100); network traffic reduction measures in effect
6/10/09 10:04:13 AM kernel AppleYukon2: 00000001,00000000 sk98nif - deadmanCheck - nothing received, resetting chip
6/10/09 10:04:17 AM kernel Ethernet AppleYukon2: Link up on en0, 100-Megabit, Full-duplex, Symmetric flow-control, Debug 796d,6f08,0de1,0200,45e1,4000
Seems like the same thing you guys were seeing.
Imac
Mac OS X (10.5.7)
|
|
|
|
Posts:
17
Registered:
Jan 8, 2007
|
|
|
Re: AppleYukon2
Posted:
Jun 5, 2009 5:44 PM
in response to: tdttester
|
|
|
Hey tdt,
I will give your suggestion a try when I get some time.
Looks like it will solve my problem.
My only question is, if I have already updated my OS, will I have to downgrade to 10.5.6, then run the combo updater? Or with my current OS 10.5.7, will the procedure you suggested work?
Thanks!
MacBookPro 2.4 GHz Intel Core 2 Duo
Mac OS X (10.5.7)
2 GB 667 MHz DDR2 SDRAM
|
|
|
|
Posts:
16
Registered:
Jun 27, 2006
|
|
|
Re: AppleYukon2
Posted:
Jun 6, 2009 3:58 PM
in response to: m1k3l0w
|
|
|
Hey m1k3l0w,
You have to apply the procedure as it is with your current OS X 10.5.7
This procedure don't downgrade the OS X version, but only the AppleYukon2 drivers.
Good luck!
Mac OS X (10.5.7)
|
|
|
|
Posts:
17
Registered:
Jan 8, 2007
|
|
|
Re: AppleYukon2
Posted:
Jun 6, 2009 4:39 PM
in response to: tdttester
|
|
|
Thanks tdt, worked like a charm.
No more noisy log.
MacBookPro 2.4 GHz Intel Core 2 Duo
Mac OS X (10.5.7)
2 GB 667 MHz DDR2 SDRAM
|
|
|
|
Posts:
4
Registered:
Jul 25, 2008
|
|
|
Re: AppleYukon2
Posted:
Jun 5, 2009 11:09 PM
in response to: tdttester
|
|
|
Thanks tdttester, your brilliant procedure to rollback to the 10.5.6 AppleYukon2 driver SOLVED my problem with the 10.5.7 AppleYukon2 driver. I opened a 10.5.6 install DVD with Pacifist rather than downloading the 10.5.6ComboUpdate. My en0 ethernet connection is now stable. The cyclic disconnect/reconnect and deadmanCheck error message floods are gone. All other network components (airport, parallels) are working fine. So far, no adverse effects. I will post again if any show up...
Many regards
iMac core duo 20"
Mac OS X (10.5.4)
|
|
|
|
Posts:
10
Registered:
Jul 19, 2004
|
|
|
Re: AppleYukon2
Posted:
Jun 4, 2009 10:16 PM
in response to: m1k3l0w
|
|
|
My apologies for failing to be clear. I knew it was an ethernet issue at heart, but the what was causing me the most problems was the connection to my time capsule which is connected via ethernet to my imac, and which handles my wireless to the rest of the house kept failing. After updating iTunes the problem appears to be resolved. My wireless connections are not dropped, nor have I had any problems with the ethernet reseting, at least according to the console. I actually have not done anything different other than that, as I kept hoping that Apple would issue a fix. I am now really stumped because I was expecting other people to notice a change when I did.
iMac 2007
Mac OS X (10.5.7)
|
|
|
|
Posts:
10
Registered:
Jul 19, 2004
|
|
|
Re: AppleYukon2
Posted:
Jun 5, 2009 3:46 PM
in response to: Jed Johnson
|
|
|
Oh never mind. It's back again.
iMac 2007
Mac OS X (10.5.7)
|
|
|
|