Eternal Media - Latest Comments

Re: Pirating internet access

Vincent — Sun, 20 Feb 2011 00:38:38 -0000

If you're using Mac OSX 10.6 you should to set net.inet.ip.scopedroute=0:
$ sudo sysctl -w net.inet.ip.scopedroute=0

Re: Cisco VPN causes kernel panic on Mac OS X

MacBookPro User — Tue, 07 Sep 2010 15:01:42 -0000

I am having the same issue, but there is no VMware (Parallels or Fusion) on the MacBook Pro [MacBookPro6,2 (Mac-F22586C8)] that I am using. I just turned off the IPv6, and I will see if that makes a difference.

Re: Cisco VPN causes kernel panic on Mac OS X

valerio1974to — Sat, 13 Mar 2010 04:47:51 -0000

Sorry, what IT staff did you a developer release?
Do you mean Cisco staff?
What release is it? Cisco VPN Client 4.X ?

Re: Cisco VPN causes kernel panic on Mac OS X

Helmut — Wed, 10 Mar 2010 23:31:13 -0000

problem resolved: IT support had given me a developer beta release which was unstable. after installing the full 10.6 all works.

Re: Cisco VPN causes kernel panic on Mac OS X

Helmut — Wed, 17 Feb 2010 18:55:57 -0000

disabled ipv6, have no wmware, configured Cisco VPN via apple (i.e., no cisco client installed). when i type in the password i obtain a kernel panic. note that there used to be a cisco client installed (now uninstalled) before i went from 10.5 to 10.6. maybe i did not uninstall the VPN client well enough. but i figured that running the uninstall.sh script would do the trick. ideas?

Re: Cisco VPN causes kernel panic on Mac OS X

mfisch@mfisch.com — Fri, 18 Dec 2009 09:43:16 -0000

I'm running
Cisco VPN Client 4.9.1.0180
Mac OS X 10.6.2
VMware Fusion 3.0.1

I get the same crash, it only happens when I'm connected to a VPN peer. Sometimes I can work on the vpn for days or even weeks at a time, sometimes I'll get the crash 4x in 48 hours. I can't use the built-in cisco vpn client because it only supports TCP tunnels.

I tried turning IPv6 off on both my Airport and Ethernet interfaces, this seemed to have no effect.

There doesn't seem to be any workarounds yet other than uninstalling VMware or Cisco VPN Client, but good bug reports may lead to something down the road.

Interval Since Last Panic Report: 699530 sec
Panics Since Last Report: 3
Anonymous UUID: 89F40876-109C-4140-B07A-C58B352DAA6B

Fri Dec 18 09:31:35 2009
panic(cpu 0 caller 0x34b465): "ip_output: mix of packet in packetlist is wrong=0x587a3c00"@/SourceCache/xnu/xnu-1486.2.11/bsd/netinet/ip_output.c:1606
Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
0x56713728 : 0x21b2bd (0x5cf868 0x5671375c 0x223719 0x0)
0x56713778 : 0x34b465 (0x5a6638 0x587a3c00 0x90 0x1)
0x567138f8 : 0x352140 (0x587a3c00 0x3 0x0 0x56713944)
0x56713978 : 0x353a46 (0x3 0x0 0x0 0x0)
0x56713a98 : 0x34fd2d (0x7d886b0 0x58827400 0x1 0x921cd14a)
0x56713c68 : 0x34550f (0x58827400 0x14 0x4 0x0)
0x56713ca8 : 0x346c22 (0x58827400 0x14 0x6 0x0)
0x56713dd8 : 0x346d49 (0x58827400 0x0 0x6 0x0)
0x56713df8 : 0x32d695 (0x2 0x58827400 0x56713e28 0x0)
0x56713e38 : 0x319f0c (0x2 0x58827400 0x56713e68 0x11c2b74)
0x56713ec8 : 0x31619c (0x823aa04 0x2 0x58827400 0x4fb2b0)
0x56713ef8 : 0x3188ff (0x87b7a4 0x878fb48 0x2 0x56713f74)
0x56713f68 : 0x318b6d (0x0 0x58827400 0x0 0x81d28ac)
0x56713fc8 : 0x29d68c (0x81d2884 0x0 0x29d69b 0x7e652a4)

BSD process name corresponding to current thread: kernel_task

Mac OS version:
10C540

Kernel version:
Darwin Kernel Version 10.2.0: Tue Nov 3 10:37:10 PST 2009; root:xnu-1486.2.11~1/RELEASE_I386
System model name: MacBook4,1 (Mac-F22788A9)

System uptime in nanoseconds: 8827910318100
unloaded kexts:
com.apple.driver.AppleUSBHIDKeyboard 1.2.0a3 (addr 0x1058000, size 0x8192) - last unloaded 4760269023333
loaded kexts:
com.cisco.nke.ipsec 2.0.1
com.vmware.kext.vmnet 3.0.0
com.vmware.kext.vmioplug 3.0.0
com.vmware.kext.vmci 3.0.0
com.vmware.kext.vmx86 3.0.0
com.Logitech.Control Center.HID Driver 2.6.0
com.apple.filesystems.afpfs 9.6
com.apple.nke.asp_tcp 5.0
com.apple.driver.AppleHDA 1.7.9a4
com.apple.driver.AppleHWSensor 1.9.2d0
com.apple.filesystems.autofs 2.1.0
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.AudioIPCDriver 1.1.2
com.apple.driver.SMCMotionSensor 3.0.0d4
com.apple.driver.AppleUpstreamUserClient 3.1.0
com.apple.driver.AppleLPC 1.4.9
com.apple.driver.AppleIntelPenrynProfile 17
com.apple.driver.ACPI_SMC_PlatformPlugin 4.0.1d0
com.apple.driver.AppleBacklight 170.0.14
com.apple.driver.AppleIntelGMAX3100 6.0.6
com.apple.driver.AppleIntelGMAX3100FB 6.0.6
com.apple.driver.AppleUSBTrackpad 1.8.0b4
com.apple.driver.AppleUSBTCKeyEventDriver 1.8.0b4
com.apple.driver.AppleUSBTCKeyboard 1.8.0b4
com.apple.driver.AppleIRController 251.1.4
com.apple.iokit.SCSITaskUserClient 2.6.0
com.apple.iokit.AppleYukon2 3.1.14b1
com.apple.driver.AppleHPET 1.4
com.apple.driver.AppleFWOHCI 4.4.0
com.apple.driver.AirPortBrcm43xx 411.91.20
com.apple.BootCache 31
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.iokit.IOAHCIBlockStorage 1.6.0
com.apple.driver.AppleUSBHub 3.8.4
com.apple.driver.AppleAHCIPort 2.0.1
com.apple.driver.AppleIntelPIIXATA 2.5.0
com.apple.driver.AppleUSBEHCI 3.7.5
com.apple.driver.AppleUSBUHCI 3.7.5
com.apple.driver.AppleSmartBatteryManager 160.0.0
com.apple.driver.AppleEFINVRAM 1.3.0
com.apple.driver.AppleRTC 1.3
com.apple.driver.AppleACPIButtons 1.3
com.apple.driver.AppleSMBIOS 1.4
com.apple.driver.AppleACPIEC 1.3
com.apple.driver.AppleAPIC 1.4
com.apple.driver.AppleIntelCPUPowerManagementClient 96.0.0
com.apple.security.sandbox 0
com.apple.security.quarantine 0
com.apple.nke.applicationfirewall 2.1.11
com.apple.driver.AppleIntelCPUPowerManagement 96.0.0
com.apple.driver.AppleUSBHIDKeyboard 1.2.0a3 - last loaded 8381743479945
com.apple.driver.DspFuncLib 1.7.9a4
com.apple.driver.AppleProfileReadCounterAction 17
com.apple.driver.AppleProfileTimestampAction 10
com.apple.driver.AppleProfileThreadInfoAction 14
com.apple.driver.AppleProfileRegisterStateAction 10
com.apple.driver.AppleProfileKEventAction 10
com.apple.driver.AppleProfileCallstackAction 20
com.apple.iokit.IOSurface 73.0
com.apple.iokit.IOBluetoothSerialManager 2.2.4f3
com.apple.iokit.IOSerialFamily 10.0.3
com.apple.iokit.IOAudioFamily 1.7.2fc1
com.apple.kext.OSvKernDSPLib 1.3
com.apple.iokit.IOFireWireIP 2.0.3
com.apple.driver.AppleHDAController 1.7.9a4
com.apple.iokit.IOHDAFamily 1.7.9a4
com.apple.iokit.AppleProfileFamily 41
com.apple.driver.IOPlatformPluginFamily 4.0.1d0
com.apple.iokit.IONDRVSupport 2.0
com.apple.driver.AppleSMC 3.0.1d2
com.apple.iokit.IOGraphicsFamily 2.0
com.apple.driver.CSRUSBBluetoothHCIController 2.2.4f3
com.apple.driver.AppleUSBBluetoothHCIController 2.2.4f3
com.apple.iokit.IOBluetoothFamily 2.2.4f3
com.apple.driver.AppleHIDKeyboard 1.2.0a3
com.apple.iokit.IOUSBHIDDriver 3.8.4
com.apple.driver.AppleUSBMergeNub 3.8.5
com.apple.driver.AppleUSBComposite 3.7.5
com.apple.iokit.IOSCSIMultimediaCommandsDevice 2.6.0
com.apple.iokit.IOBDStorageFamily 1.6
com.apple.iokit.IODVDStorageFamily 1.6
com.apple.iokit.IOCDStorageFamily 1.6
com.apple.driver.XsanFilter 402.1
com.apple.iokit.IOFireWireFamily 4.1.7
com.apple.iokit.IOATAPIProtocolTransport 2.5.0
com.apple.iokit.IOSCSIArchitectureModelFamily 2.6.0
com.apple.iokit.IO80211Family 310.6
com.apple.iokit.IONetworkingFamily 1.9
com.apple.iokit.IOUSBUserClient 3.8.5
com.apple.iokit.IOAHCIFamily 2.0.2
com.apple.iokit.IOATAFamily 2.5.0
com.apple.iokit.IOUSBFamily 3.8.5
com.apple.driver.AppleEFIRuntime 1.3.0
com.apple.iokit.IOHIDFamily 1.6.1
com.apple.iokit.IOSMBusFamily 1.1
com.apple.kext.AppleMatch 1.0.0d1
com.apple.security.TMSafetyNet 6
com.apple.driver.DiskImages 281
com.apple.iokit.IOStorageFamily 1.6
com.apple.driver.AppleACPIPlatform 1.3
com.apple.iokit.IOPCIFamily 2.6
com.apple.iokit.IOACPIFamily 1.3.0
Model: MacBook4,1, BootROM MB41.00C1.B00, 2 processors, Intel Core 2 Duo, 2.4 GHz, 4 GB, SMC 1.31f0
Graphics: Intel GMA X3100, GMA X3100, Built-In, 144 MB
Memory Module: global_name
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x88), Broadcom BCM43xx 1.0 (5.10.91.19)
Bluetooth: Version 2.2.4f3, 2 service, 0 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
Serial ATA Device: ST9320423AS, 298.09 GB
Parallel ATA Device: HL-DT-ST DVDRW GSA-S10N
USB Device: Keyboard Hub, 0x05ac (Apple Inc.), 0x1006, 0xfa200000
USB Device: USB Trackball, 0x046d (Logitech Inc.), 0xc408, 0xfa230000
USB Device: Apple Keyboard, 0x05ac (Apple Inc.), 0x0220, 0xfa220000
USB Device: Bluetooth USB Host Controller, 0x05ac (Apple Inc.), 0x8205, 0x1a100000
USB Device: Built-in iSight, 0x05ac (Apple Inc.), 0x8501, 0xfd400000
USB Device: Apple Internal Keyboard / Trackpad, 0x05ac (Apple Inc.), 0x0229, 0x5d200000
USB Device: IR Receiver, 0x05ac (Apple Inc.), 0x8242, 0x5d100000

Re: Cisco VPN causes kernel panic on Mac OS X

Wm. Cerniuk — Thu, 24 Sep 2009 21:04:28 -0000

This is much more simple. Have the Cisco VPN software running, then let TimeMachine take off against the Timecapsule. It uses IPv6 and it causes a kernel panic every time.

And I turned TimeMachine off and the problem goes away. It comes back if I use the Apple Airport utility which also uses IPv6.

Regardless, the KPs always show that the crash occurred in the Cisco driver. This has been occurring in Cisco VPNClient 4.9.1.0100 and 0180.

Unfortunately the built in VPN will not work with our Cisco VPN concentrator for some reason. The login fails every time. Perhaps there is only partial support in the OS via Raccoon?

Re: Cisco VPN causes kernel panic on Mac OS X

Jackson — Sun, 20 Sep 2009 10:20:34 -0000

Yeah I'm pretty sure I disabled it in both interfaces. Too bad it didn't fix the problem. :( I'm always connected via ethernet when the crash happens.

Re: Cisco VPN causes kernel panic on Mac OS X

noah — Tue, 15 Sep 2009 16:41:51 -0000

@Jackson: Did you disable IPv6 on both the wired ethernet and the Airport?

@Beth: And neither CodeWeaver's CrossOver, as mentioned in the report? FWIW, both my early 2008 MBP and late 2007 iMac 24", both with 4GB memory, crashes whenever I'm connected with Cisco VPN, if VMware is installed AND IPv6 is active on the interfaces. (I'm always connected to networks where IPv6 is spoken)

Either turning off IPv6 on all interfaces or uninstalling VMware has fixed the issue for me and others. I haven't had a single crash since I uninstalled VMware (14 months ago) and I don't get crashes when having VMware installed and remembering to turn off IPv6 before connecting to VPN.
Those times when I forget to turn off IPv6 beforehand always end crashing the kernel, with Cisco's kext being pointed out as the responsible party.

IPv6 and/or virtualization/emulation software might of course not be the only reason why Cisco's kernel extension crashes the computer. But pulling either of them out of the picture have "permanently fixed" the sudden crash issues for me and others. That being said, YMMV.

Re: Cisco VPN causes kernel panic on Mac OS X

Beth — Tue, 15 Sep 2009 14:57:03 -0000

I am following this crash issue with interest. My MacBook Pro crashed twice yesterday with this exact kernel panic. I have Cisco's VPN client installed on my machine, but it wasn't running either time I got the kernel panic. I also don't have VMWare or Parallels installed on this machine. I've never had this type of kernel panic before, and I've been using this machine with this VPN software for probably 2 years now.

Someone suggested to me that it may have been related to a recent upgrade of our company's wireless. Yesterday, my wireless seemed to be flaking out, so I turned it off (I always have ethernet plugged in as well). Haven't gotten a crash since.

Just another data point to add to the puzzle.

Re: Cisco VPN causes kernel panic on Mac OS X

Jackson — Mon, 14 Sep 2009 11:05:27 -0000

I was having this same crash issue. I disabled IPV6 for ethernet last week and I just had another kernel panic that I traced to Cisco. So I don't think disabling IPV6 is a reliable fix or this issue. Maybe uninstalling VMWare Fusion would solve it, but I need VMWare. Any other ideas?

Re: Cisco VPN causes kernel panic on Mac OS X

noah — Fri, 04 Sep 2009 07:49:21 -0000

Good point. Now those details are in the comments already (thanks!) but I've also updated the post in an attempt to make that more clear.

Re: Cisco VPN causes kernel panic on Mac OS X

Santino — Wed, 02 Sep 2009 21:27:01 -0000

I see. The way I read your description, it seemed to say unless you set IPv6 to "Off" you will have problems.

Re: Cisco VPN causes kernel panic on Mac OS X

noah — Wed, 02 Sep 2009 08:51:26 -0000

Do you really run IPv6 in your network? I.e, do you have IPv6 routers and actively use IPv6?
Just having a link local IPv6 address (as you'll get with IPv6 set to automatic) but not using IPv6 for transport doesn't seem to be enough to trigger the bug in my experience.

When IPv6 is set to be automatically configured, Mac OS X will periodically query the network for neighbouring IPv6 routers by sending IPv6 Router Solicitation messages. It will also listen for Router Advertisement messages from IPv6 routers, which can be sent either in response to a previous Router Solicitation message or by a router who simply want to announce its presence on the network.

The RA messages from routers contain, among other things, parameters needed for hosts to do automatic address configuration. I guess you could think of it like a mix of ARP and DHCP, although it's different; see RFC 2461 for more information.

So, unless you have IPv6 routers in the network, you computer wont be assigned a public, routable IPv6 address and hence won't be able to talk to the IPv6 internet. Which in turn severely limits the amount of IPv6 traffic your computer exchanges on the network. This could be one reason why you're not experiencing the issue.

Re: Cisco VPN causes kernel panic on Mac OS X

Santino — Wed, 02 Sep 2009 08:11:11 -0000

There must be another variable because I can know of at least 5 and as many as 20 Mac users at my organization (myself included) who use Fusion (NAT), the IPSec client, and leave IPv6 set to automatic, and have absolutely no problems using their VPN connections all day.

Re: Spotify could provide useful content over IPv6

Alex Smith — Sun, 23 Aug 2009 12:36:10 -0000

It's the old chicken and egg problem with IPv6, the unwillingness of content providers to IPv6 enable their services and then ISP's using that as an excuse not to IPv6 their networks....

It would be nice to see Spotify take a nice stance on IPv6, it's a project that would put IPv6 very much in the public eye. I think the other major company that has IPv6'd their network that will have an impact was Limelight Networks who IPv6 enabled their CDN platform back in June.

The more people doing things like that the more pressure people can put on their ISP's :)