Wifi constantly crashing since upgrade

Question

Level 1

0 points

Wifi constantly crashing since upgrade

OK this is getting unusable ... every 10 maybe 15 minutes at the most i get the spinning wheel and my whole system freezes for 15 / 20 seconds and then it comes back to life but the wifi is hunting.

This has only happened since upgrading tonight.. Tips anyone ?

Macbook Pro, Mac OS X (10.6)

Posted on Sep 2, 2009 2:22 PM

Reply

Answer 1

Sep 2, 2009 2:24 PM in response to LCaller

What does you crash log say?

Reply

Answer 2

LCaller Author

Level 1

0 points

Sep 2, 2009 2:40 PM in response to Donald Palmer

Not a lot, there now seems to be some Vodafone program trying to constantly start which i don't have installed , which i've never noticed before

02/09/2009 22:39:45 com.apple.launchd.peruser.501[206] (cn.com.zte.usbswapper.plist[1731]) posix_spawn("/Applications/Vodafone Mobile Connect/Vodafone Mobile Connect.app/Contents/Resources/Specific/Mac SwapperDemon.app/Contents/MacOS/MacSwapperDemon", ...): No such file or directory

Reply

Answer 3

Dogcow-Moof

Level 8

36,557 points

Sep 2, 2009 2:44 PM in response to LCaller

So are you connecting using AirPort or some Vodafone device to connect?

If the latter, you may need to contact Vodafone to see if they have an update.

Reply

Answer 4

LCaller Author

Level 1

0 points

Sep 2, 2009 2:48 PM in response to Dogcow-Moof

No it's all airport i don't have an never had a Vodafone card on this machine. I'm wondering if that's come over from a time machine backup of my last machine..

It's just happened again and there is nothing in the logs, it's all messages about the Vodafone software in the console log, looks like every 10 seconds.

Reply

Answer 5

Dogcow-Moof

Level 8

36,557 points

Sep 2, 2009 3:10 PM in response to LCaller

You may want to try uninstalling the Vodafone software in case it's interfering with AirPort somehow.

Reply

Answer 6

LCaller Author

Level 1

0 points

Sep 2, 2009 3:13 PM in response to Dogcow-Moof

It's not installed , that's my point. It isn't on here and even the console log says it can't find it .

Reply

Answer 7

LCaller Author

Level 1

0 points

Sep 2, 2009 3:26 PM in response to LCaller

OK i just managed to watch the log as it happened

02/09/2009 23:24:14 kernel AirPort: Link Down on en1. Reason 4 (Disassociated due to inactivity).
02/09/2009 23:24:14 kernel vmnet: bridge-en1: interface en is going DOWN
02/09/2009 23:24:15 configd[13] network configuration changed.
02/09/2009 23:24:15 vmnet-bridge[164] Examining network configuration.
02/09/2009 23:24:15 vmnet-bridge[164] Intf: en2
02/09/2009 23:24:15 vmnet-bridge[164] Turning off bridge for: en1
02/09/2009 23:24:15 vmnet-bridge[164] Turning on bridge for: en2
02/09/2009 23:24:15 configd[13] setting hostname to "Lee-MBP.local"
02/09/2009 23:24:15 kernel vmnet: VMNetDisconnect called for port 0x133f0b00
02/09/2009 23:24:15 kernel vmnet: bridge-en1: filter detached
02/09/2009 23:24:15 kernel vmnet: bridge-en1: down
02/09/2009 23:24:15 kernel vmnet: bridge-en1: detached
02/09/2009 23:24:15 kernel vmnet: Freeing hub at 0x8d13000.
02/09/2009 23:24:15 kernel vmnet: VNetUserIf_Create: created userIf at 0x133c6e00.
02/09/2009 23:24:15 kernel vmnet: VMNetConnect: returning port 0x133c6e00
02/09/2009 23:24:15 kernel vmnet: Hub 0 does not exist, allocating memory.
02/09/2009 23:24:15 kernel vmnet: Allocated hub 0x8d13000 for hubNum 0.
02/09/2009 23:24:15 kernel vmnet: VMNET SOBINDTOHUB: port: paddr 00:50:56:f1:02:e3
02/09/2009 23:24:15 kernel vmnet: Hub 0
02/09/2009 23:24:15 kernel vmnet: Port 0
02/09/2009 23:24:15 kernel vmnet: bridge-en2: got dev 0x8d98c04
02/09/2009 23:24:15 kernel vmnet: bridge-en2: up
02/09/2009 23:24:15 kernel vmnet: bridge-en2: attached
02/09/2009 23:24:15 kernel vmnet: VNetUserIfFree: freeing userIf at 0x133c6e00.

Reply

Answer 8

Dogcow-Moof

Level 8

36,557 points

Sep 2, 2009 4:12 PM in response to LCaller

What's your Wi-Fi router? AirPort? Something else?

The suspicious bit in the log is this:

<pre>AirPort: Link Down on en1. Reason 4 (Disassociated due to inactivity).</pre>

Some routers will disassociate clients once they have been idle for a prescribed amount of time (some as few as two to three minutes.)

This disassociation and the need to reassociate is likely what you're seeing.

Reply

Answer 9

LCaller Author

Level 1

0 points

Sep 2, 2009 4:13 PM in response to Dogcow-Moof

It's the same O2 Thompson it's always been... As i said it was all just working fine until 7pm this evening when i stuck in the upgrade disk *SIGH* and it's still working fine on the Leopard Mac.

Now connected to ethernet to stop the constant crashing, as it gets worse the more data you put over it.

Reply

Answer 10

Dogcow-Moof

Level 8

36,557 points

Sep 2, 2009 4:16 PM in response to LCaller

I suspect the Thompson has always been sending out the disassociation packets and the newer AirPort drivers are simply honoring them. Just a guess.

Do you see the connection pauses if you're actively using the Internet, say streaming a radio station in the background?

Reply

Answer 11

badair

Level 1

0 points

Sep 7, 2009 10:52 AM in response to Dogcow-Moof

Gents,

I am having the same "disassociation" issue but mine is a definite driver/OS issue with 10.6 SL. I receive this message every 5 to 15 minutes:
9/7/09 1:24:16 PM kernel AirPort: Link Down on en1. Reason 4 (Disassociated due to inactivity).

I have a macbook that has been on my home network for years, I have not changed anything there. The Macbook stays online fine but is running Leopard. Of my 5 Wi-Fi devices, this new MBP with SL is the only one dropping connection so I am sure it is not my router.

I am considering installing Leopard to prove my point.

Apple Support....Please fix this Airport driver issue in 10.6.

Reply

Answer 12

LCaller Author

Level 1

0 points

Sep 7, 2009 11:13 AM in response to badair

The only way way i resolved this was a full reinstall of Snow Leopard, the upgrade process for me was a total failure.

Reply

Answer 13

Dogcow-Moof

Level 8

36,557 points

Sep 7, 2009 11:43 AM in response to badair

badair wrote:
I am having the same "disassociation" issue but mine is a definite driver/OS issue with 10.6 SL. I receive this message every 5 to 15 minutes:
9/7/09 1:24:16 PM kernel AirPort: Link Down on en1. Reason 4 (Disassociated due to inactivity).

I have a macbook that has been on my home network for years, I have not changed anything there. The Macbook stays online fine but is running Leopard. Of my 5 Wi-Fi devices, this new MBP with SL is the only one dropping connection so I am sure it is not my router.

I am considering installing Leopard to prove my point.

Reinstalling Leopard proves nothing.

I'll ask you the same question - does the inactivity timeout still occur if you are actively using the interface, say streaming an Internet radio station in the background? Or just when you're doing nothing say using an application that doesn't use the Internet?

Reply

Answer 14

Sep 8, 2009 5:37 AM in response to LCaller

My airport also keeps disconnecting every 10 - 15 minutes. I am also using an O2 router, and it's only started happening since I installed 10.6.

Reply

Answer 15

LCaller Author

Level 1

0 points

Sep 8, 2009 5:51 AM in response to Nicolanicolanicola

Did you do a clean install or an upgrade ?

Reply