Kernel panic after Cisco AnyConnect establishes connection

Same problem here with AnyConnect and my MBA Late 2010. Can't use it anymore.

I had the same problem. This happened after I updated to 10.6.7. After trying many things I uninstalled vmware fusion and now everything works. If you have parralels or someonther vm software installed you may want to uninstall.

No VM software installed here.

I have the exact same problem. Mine happens ~30 seconds after I connect, and if I'm using ssh it happens right after I make a connection.

panic(cpu 6 caller 0xffffff80002d1208): Kernel trap at 0xffffff8000355ec0, type 14=page fault, registers:

CR0: 0x0000000080010033, CR2: 0x00000000000000ae, CR3: 0x0000000071402000, CR4: 0x0000000000040660

.

.

.

BSD process name corresponding to current thread: ssh

Hardware:

Early 2011 MacBook Pro 15"

Intel Core i7 @ 2 GHz

4GB RAM

Software:

Cisco AnyConnect 3.0.2052

Mac OS X 10.6.7

Lastest patches

No VM software (e.g. VirtualBox, VMWare Fusion, etc.)

No Bootcamp

This still happens in 10.6.8. This time it happened while Dropbox was uploading some files. It seems to be around that 30-second-after-connect mark.

Thu Jun 23 20:24:39 2011

panic(cpu 0 caller 0xffffff800035790c): "-- unknown opcode 97\n"@/SourceCache/xnu/xnu-1504.15.3/bsd/netinet/ip_fw2.c:2651

Backtrace (CPU 0), Frame : Return Address

0xffffff80b0993560 : 0xffffff8000204d15

0xffffff80b0993660 : 0xffffff800035790c

0xffffff80b0993870 : 0xffffff8000360754

0xffffff80b0993ac0 : 0xffffff8000367c04

0xffffff80b0993b80 : 0xffffff8000369628

0xffffff80b0993ce0 : 0xffffff80004adbed

0xffffff80b0993e00 : 0xffffff80004978b7

0xffffff80b0993e30 : 0xffffff80004956ba

0xffffff80b0993ed0 : 0xffffff8000495804

0xffffff80b0993f40 : 0xffffff80004e7e63

0xffffff80b0993fa0 : 0xffffff80002e4441

BSD process name corresponding to current thread: Dropbox

Mac OS version:

10K540

.

.

.

I kernel paniced with Lion yesterday, as well. Cisco did just come out with version 3.0.3050, but I'm not sure if it fixes anything related to this.

http://www.cisco.com/en/US/docs/security/vpn_client/anyconnect/anyconnect30/rele ase/notes/anyconnect30rn.html

Doesnt work with 3.0.3050 either.

After a fresh Lion install, the latest version of the client works for me - 3.0.3054.

I also had several problems with this , using the 3.03054 version of the client. Both on Snow Leopard and Lion.

It worked for me on occasions, but then started doing kernel panic again.

A solution for me that seems to work ( i have done it several times now with it working )

If your machine kernel panics, reboot it.

- close all apps

- shutdown macbook from menu.

- Make sure the powercord is in

- Reset the SMC by pressing Shift+Crtrl+Alt + Power button for at least 5 seconds

- Startup the macbook

- Connect using AnyConnect.

This has worked for me so far. It's not optimal, Cisco should fix client, but this is a way to at least be able to connect.

I use stock RAM from apple.

I have a MBP 13 and an MacPro both experiencing kernel panics with Anyconnect 2.5.3054 and 3.0.3054. These were previously working on the same hardware with no recent major changes. I did recently update both Parallels and VMWare Fusion so those are suspect.

Removed VMWare 3 and Parallels 7

Turned off LogMe In, Back to My Mac, and DropBox

Unistalled and reinstalled Anyconnect client

Reset SMC...

Still no joy.

Tested on the MBP 13" 10.7.1 with 3.0.3054 and 3.0.4235

Also have same problem on MacPRo with 2.5.3054 and 3.0.3054 but haven't uninstalled software there.