Kernel Panic 10.4.8. with MacPro 3.0 and VMWARE Fusion Beta

[Henri]

Hello,

got I couple of crashes, I opened a new topic in the MACOS discussion forum, seams to me that this is more Macos related.

http://discussions.apple.com/message.jspa?messageID=3894096#3894096

Sun Jan 14 00:12:29 2007

panic(cpu 0 caller 0x0035BEAC): m_freem_list: m_nextpkt of m_next != NULL

Backtrace, Format - Frame : Return Address (4 potential args on stack)

0x2504b6e8 : 0x128d1f (0x3c9540 0x2504b70c 0x131df4 0x0)

0x2504b728 : 0x35beac (0x3e9cbc 0x202 0x2504b798 0x1416a6)

0x2504b768 : 0x3c0f74e2 (0x37e6f800 0x37f9f200 0x558c161c 0x20)

0x2504b788 : 0x3c12ae5b (0x397a800 0x37e6f800 0x1 0x12767a)

0x2504b7c8 : 0x3c12d539 (0x397a800 0x0 0x2504b7f8 0x34afd5)

0x2504b898 : 0x3c0ff37e (0x397a800 0x37ec7f00 0x0 0x37ec5500)

0x2504b8c8 : 0x3c0ff154 (0x3c8a0c0 0x3c59170 0x2504b8ec 0x19d23a)

0x2504b908 : 0x3c0ff2b9 (0x3c8a0c0 0x5b7a0 0x36cee80 0x21aead)

0x2504b938 : 0x3c0fab77 (0x3c8a0c0 0x37ec7f00 0x0 0x0)

0x2504b978 : 0x2025fe (0x3e50804 0x37ec7f00 0x2 0x2504b9e8)

0x2504b9d8 : 0x232a47 (0x3e50804 0x2 0x37ec7f00 0x3ffab04)

0x2504bb18 : 0x239d75 (0x37ec7f00 0x0 0x0 0x44441c8)

0x2504bc28 : 0x23833b (0x4444228 0x0 0x8000 0x6f0114ac)

0x2504be08 : 0x22d05e (0x37e42b00 0x14 0x37e42b00 0x0)

0x2504be48 : 0x22eabf (0x37e42b00 0x14 0x6 0x0)

0x2504bf58 : 0x21c23b (0x37e42b00 0x37e42b00 0x44307c 0x1a1ec0) Backtrace continues...

Kernel loadable modules in backtrace (with dependencies):

com.apple.driver.AppleIntel8254XEthernet(1.1.4a5)@0x3c122000

dependency: com.apple.iokit.IONetworkingFamily(1.5.1)@0x3c0f0000

dependency: com.apple.iokit.IOPCIFamily(2.1)@0x35014000

com.apple.iokit.IONetworkingFamily(1.5.1)@0x3c0f0000

Sun Jan 14 00:12:29 2007

panic(cpu 0 caller 0x0035BEAC): m_freem_list: m_nextpkt of m_next != NULL

Backtrace, Format - Frame : Return Address (4 potential args on stack)

0x2504b6e8 : 0x128d1f (0x3c9540 0x2504b70c 0x131df4 0x0)

0x2504b728 : 0x35beac (0x3e9cbc 0x202 0x2504b798 0x1416a6)

0x2504b768 : 0x3c0f74e2 (0x37e6f800 0x37f9f200 0x558c161c 0x20)

0x2504b788 : 0x3c12ae5b (0x397a800 0x37e6f800 0x1 0x12767a)

0x2504b7c8 : 0x3c12d539 (0x397a800 0x0 0x2504b7f8 0x34afd5)

0x2504b898 : 0x3c0ff37e (0x397a800 0x37ec7f00 0x0 0x37ec5500)

0x2504b8c8 : 0x3c0ff154 (0x3c8a0c0 0x3c59170 0x2504b8ec 0x19d23a)

0x2504b908 : 0x3c0ff2b9 (0x3c8a0c0 0x5b7a0 0x36cee80 0x21aead)

0x2504b938 : 0x3c0fab77 (0x3c8a0c0 0x37ec7f00 0x0 0x0)

0x2504b978 : 0x2025fe (0x3e50804 0x37ec7f00 0x2 0x2504b9e8)

0x2504b9d8 : 0x232a47 (0x3e50804 0x2 0x37ec7f00 0x3ffab04)

0x2504bb18 : 0x239d75 (0x37ec7f00 0x0 0x0 0x44441c8)

0x2504bc28 : 0x23833b (0x4444228 0x0 0x8000 0x6f0114ac)

0x2504be08 : 0x22d05e (0x37e42b00 0x14 0x37e42b00 0x0)

0x2504be48 : 0x22eabf (0x37e42b00 0x14 0x6 0x0)

0x2504bf58 : 0x21c23b (0x37e42b00 0x37e42b00 0x44307c 0x1a1ec0) Backtrace continues...

Kernel loadable modules in backtrace (with dependencies):

com.apple.driver.AppleIntel8254XEthernet(1.1.4a5)@0x3c122000

dependency: com.apple.iokit.IONetworkingFamily(1.5.1)@0x3c0f0000

dependency: com.apple.iokit.IOPCIFamily(2.1)@0x35014000

com.apple.iokit.IONetworkingFamily(1.5.1)@0x3c0f0000

[rcardona2k]

Can you provide more details and describe what you were doing in the VMware guest VM or on the network to possibly trigger these crashes?

[axelklatt]

I had similar crashes twice (same backtrace .. in com.apple.driver.AppleIntel8254XEthernet(1.1.4a5)@0x3c122000 .. blabla..)

I was running both Parallels and VMware on my MacPro 2.66.

I deinstalled Parallels now to see wether the crashes go away because I saw Parallels kernel modules activity in the system.log without actually using Parallels. This was now one day ago and I had no panic yesterday. I will wait and see wether I still see my MP crashing...

One thing I changed since I saw the panics was the NAT configuration of vmware. I forwarded some ports to my virtual machines to be able to ssh to them..

I have almost the same setup on my MBP but it did not crash (yet).

axel

[rickross]

I just saw a bunch of kernel panics in a row that appear similar to this. My colleague was simply trying to tranfer files from my computer to his, and Fusion had never been run since rebooting. Every time he tried to copy some files it hard crashed my Mac Pro within a minute or two. Here are the panic logs. You can see that "com.vmware.kext.vmnet" is almost always involved.

I uninstalled the Fusion beta, and I was able to copy without problems after that.

Rick Ross

---

*********

Mon Jan 15 12:23:09 2007

panic(cpu 2 caller 0x001A3135): Unresolved kernel trap (CPU 2, Type 14=page fault), registers:

CR0: 0x80010033, CR2: 0xdb1b7771, CR3: 0x01708000, CR4: 0x000006e0

EAX: 0xff7ffd4e, EBX: 0x5bceed00, ECX: 0x00000002, EDX: 0x7f484f72

CR2: 0xdb1b7771, EBP: 0x48f4ba88, ESI: 0x7ec84cbf, EDI: 0xdb1b7771

EFL: 0x00010602, EIP: 0x00195ef2, CS: 0x00000008, DS: 0x004d0010

Backtrace, Format - Frame : Return Address (4 potential args on stack)

0x48f4b838 : 0x128d1f (0x3c9540 0x48f4b85c 0x131df4 0x0)

0x48f4b878 : 0x1a3135 (0x3cf1f4 0x2 0xe 0x3cea24)

0x48f4b988 : 0x19a8d4 (0x48f4b9a0 0x48 0x48f40010 0x190010)

0x48f4ba88 : 0x349f3b (0x5bf3e200 0x1 0x9da3780 0x5bf3e236)

0x48f4baa8 : 0x6190a00c (0x5bf3e200 0x1 0x48f4bacc 0x0)

0x48f4bad8 : 0x2025cd (0x8131a00 0x804c404 0x2 0x48f4bb48)

0x48f4bb38 : 0x232a47 (0x804c404 0x2 0x5bf3e200 0x9263e04)

0x48f4bc78 : 0x239d75 (0x5bf3e200 0x0 0x0 0xec286b0)

0x48f4bd88 : 0x23d8f2 (0xec28710 0x5c075b00 0x10 0x1000)

0x48f4bdc8 : 0x35f5cc (0xec284e8 0x0 0x5c075b00 0x0)

0x48f4be68 : 0x363e7e (0xec284e8 0x0 0xe619200 0x5c075b00)

0x48f4bec8 : 0x36411a (0xe619200 0x0 0x918e7c4 0x0)

0x48f4bf68 : 0x378337 (0x83fe5dc 0x918e780 0x918e7c4 0x0)

0x48f4bfc8 : 0x19acae (0xa5ff900 0x0 0x19d0b5 0x85b67a0) No mapping exists for frame pointer

Backtrace terminated-invalid frame pointer 0xb03059c8

Kernel loadable modules in backtrace (with dependencies):

com.vmware.kext.vmnet(1.0.0d1)@0x61907000

Kernel version:

Darwin Kernel Version 8.8.1: Mon Sep 25 19:42:00 PDT 2006; root:xnu-792.13.8.obj~1/RELEASE_I386

*********

Mon Jan 15 12:29:14 2007

panic(cpu 1 caller 0x0035A8A3): mbuf address out of range 0xa3ff7f74

Backtrace, Format - Frame : Return Address (4 potential args on stack)

0x48f1b9e8 : 0x128d1f (0x3c9540 0x48f1ba0c 0x131df4 0x0)

0x48f1ba28 : 0x35a8a3 (0x3e9c5c 0xa3ff7f74 0x5be3fd00 0x35b1e9)

0x48f1ba48 : 0x35ac43 (0x5be44c00 0x9b101 0x48f1ba98 0x5be4bd00)

0x48f1ba68 : 0x61225dc2 (0x5be44c00 0x807e83c 0x48f1baa8 0x48f1bb48)

0x48f1baa8 : 0x61227045 (0x81f9838 0x5be44c00 0x48f1bacc 0x0)

0x48f1bad8 : 0x2025cd (0x80d7800 0x8170c04 0x2 0x48f1bb48)

0x48f1bb38 : 0x232a47 (0x8170c04 0x2 0x5be41000 0x874f104)

0x48f1bc78 : 0x239d75 (0x5be41000 0x0 0x0 0x8729da8)

0x48f1bd88 : 0x23d8f2 (0x8729e08 0x5be4ba00 0x10 0x1000)

0x48f1bdc8 : 0x35f5cc (0x8729be0 0x0 0x5be4ba00 0x0)

0x48f1be68 : 0x363e7e (0x8729be0 0x0 0x98ec100 0x5be4ba00)

0x48f1bec8 : 0x36411a (0x98ec100 0x0 0x85ce8bc 0x0)

0x48f1bf68 : 0x378337 (0x8657000 0x85ce878 0x85ce8bc 0x0)

0x48f1bfc8 : 0x19acae (0x84dee00 0x0 0x19d0b5 0x83ecf78) No mapping exists for frame pointer

Backtrace terminated-invalid frame pointer 0xb02849c8

Kernel loadable modules in backtrace (with dependencies):

com.vmware.kext.vmnet(1.0.0d1)@0x61224000

Kernel version:

Darwin Kernel Version 8.8.1: Mon Sep 25 19:42:00 PDT 2006; root:xnu-792.13.8.obj~1/RELEASE_I386

*********

Mon Jan 15 12:42:51 2007

panic(cpu 2 caller 0x0035BEAC): m_freem_list: m_nextpkt of m_next != NULL

Backtrace, Format - Frame : Return Address (4 potential args on stack)

0x48693808 : 0x128d1f (0x3c9540 0x4869382c 0x131df4 0x0)

0x48693848 : 0x35beac (0x3e9cbc 0x1000 0x0 0x6)

0x48693888 : 0x7194e2 (0x5b2d3d00 0x5b44f000 0x1 0x2)

0x486938a8 : 0x83ae5b (0x6e40000 0x5b2d3d00 0x1 0x6)

0x486938e8 : 0x83c929 (0x6e40000 0x0 0x48693938 0x12767a)

0x48693928 : 0x83d4ef (0x6e40000 0x5b457e44 0x48693958 0x34afd5)

0x486939f8 : 0x72137e (0x6e40000 0x5b457e00 0x0 0x5b450d00)

0x48693a28 : 0x721154 (0x6e530c0 0x6d74830 0x48693a4c 0x19d23a)

0x48693a68 : 0x7212b9 (0x6e530c0 0x5cb40 0x6e1dec0 0x21aead)

0x48693a98 : 0x71cb77 (0x6e530c0 0x5b457e00 0x0 0x0)

0x48693ad8 : 0x2025fe (0x7595004 0x5b457e00 0x2 0x48693b48)

0x48693b38 : 0x232a47 (0x7595004 0x2 0x5b457e00 0x859ba04)

0x48693c78 : 0x239d75 (0x5b457e00 0x0 0x0 0x833c544)

0x48693d88 : 0x23d8f2 (0x833c5a4 0x5b44db00 0x10 0x1000)

0x48693dc8 : 0x35f5cc (0x833c37c 0x0 0x5b44db00 0x0)

0x48693e68 : 0x363e7e (0x833c37c 0x0 0x8543780 0x5b44db00) Backtrace continues...

Kernel loadable modules in backtrace (with dependencies):

com.apple.driver.AppleIntel8254XEthernet(1.1.4a5)@0x832000

dependency: com.apple.iokit.IONetworkingFamily(1.5.1)@0x712000

dependency: com.apple.iokit.IOPCIFamily(2.1)@0x57c000

com.apple.iokit.IONetworkingFamily(1.5.1)@0x712000

Kernel version:

Darwin Kernel Version 8.8.1: Mon Sep 25 19:42:00 PDT 2006; root:xnu-792.13.8.obj~1/RELEASE_I386

*********

Mon Jan 15 12:44:23 2007

panic(cpu 1 caller 0x0035A8A3): mbuf address out of range 0xe1d73b41

Backtrace, Format - Frame : Return Address (4 potential args on stack)

0x4862b9e8 : 0x128d1f (0x3c9540 0x4862ba0c 0x131df4 0x0)

0x4862ba28 : 0x35a8a3 (0x3e9c5c 0xe1d73b41 0x5b44c800 0x35b1e9)

0x4862ba48 : 0x35ac43 (0x5b44fc00 0xe2b54 0x4862ba98 0x5b44fb00)

0x4862ba68 : 0x8a29cdc2 (0x5b44fc00 0x731d3bc 0x4862baa8 0x4862bb48)

0x4862baa8 : 0x8a29e045 (0x7467038 0x5b44fc00 0x4862bacc 0x0)

0x4862bad8 : 0x2025cd (0x74dbe00 0x7484e04 0x2 0x4862bb48)

0x4862bb38 : 0x232a47 (0x7484e04 0x2 0x5b44e200 0x7385104)

0x4862bc78 : 0x239d75 (0x5b44e200 0x0 0x0 0x7b7a6b0)

0x4862bd88 : 0x23d8f2 (0x7b7a710 0x5b44d200 0x10 0x1000)

0x4862bdc8 : 0x35f5cc (0x7b7a4e8 0x0 0x5b44d200 0x0)

0x4862be68 : 0x363e7e (0x7b7a4e8 0x0 0x7b25d80 0x5b44d200)

0x4862bec8 : 0x36411a (0x7b25d80 0x0 0x7a034e4 0x0)

0x4862bf68 : 0x378337 (0x7a723e8 0x7a034a0 0x7a034e4 0x0)

0x4862bfc8 : 0x19acae (0x78fc2e0 0x0 0x19d0b5 0x7b0b2c0) No mapping exists for frame pointer

Backtrace terminated-invalid frame pointer 0xb02039c8

Kernel loadable modules in backtrace (with dependencies):

com.vmware.kext.vmnet(1.0.0d1)@0x8a29b000

Kernel version:

Darwin Kernel Version 8.8.1: Mon Sep 25 19:42:00 PDT 2006; root:xnu-792.13.8.obj~1/RELEASE_I386

*********

Mon Jan 15 13:38:00 2007

panic(cpu 1 caller 0x0035A556): mbuf address out of range 0xabb6ddb3

Backtrace, Format - Frame : Return Address (4 potential args on stack)

0x47aeb9d8 : 0x128d1f (0x3c9540 0x47aeb9fc 0x131df4 0x0)

0x47aeba18 : 0x35a556 (0x3e9c5c 0xabb6ddb3 0x1 0x1b)

0x47aeba38 : 0x35b163 (0x1 0x1 0x1000 0x1b)

0x47aeba88 : 0x349f3b (0x5a6d3f00 0x1 0x2000 0x5a6d3f36)

0x47aebaa8 : 0x896c600c (0x5a6d3f00 0x1 0x47aebacc 0x0)

0x47aebad8 : 0x2025cd (0x6980e00 0x68dfe04 0x2 0x47aebb48)

0x47aebb38 : 0x232a47 (0x68dfe04 0x2 0x5a6d3f00 0x7528e04)

0x47aebc78 : 0x239d75 (0x5a6d3f00 0x0 0x0 0x7296fb8)

0x47aebd88 : 0x23d8f2 (0x7297018 0x5a851f00 0x2 0x10)

0x47aebdc8 : 0x35f5cc (0x7296df0 0x0 0x5a851f00 0x0)

0x47aebe68 : 0x363e7e (0x7296df0 0x0 0x7307a80 0x5a851f00)

0x47aebec8 : 0x36411a (0x7307a80 0x0 0x6e267c4 0x0)

0x47aebf68 : 0x378337 (0x6ea01f4 0x6e26780 0x6e267c4 0x0)

0x47aebfc8 : 0x19acae (0x6d0d960 0x0 0x19d0b5 0x6752a2c) No mapping exists for frame pointer

Backtrace terminated-invalid frame pointer 0xb01829c8

Kernel loadable modules in backtrace (with dependencies):

com.vmware.kext.vmnet(1.0.0d1)@0x896c3000

Kernel version:

Darwin Kernel Version 8.8.1: Mon Sep 25 19:42:00 PDT 2006; root:xnu-792.13.8.obj~1/RELEASE_I386

*********

Mon Jan 15 13:40:01 2007

panic(cpu 2 caller 0x0035A556): mbuf address out of range 0x18902c54

Backtrace, Format - Frame : Return Address (4 potential args on stack)

0x47b3b9d8 : 0x128d1f (0x3c9540 0x47b3b9fc 0x131df4 0x0)

0x47b3ba18 : 0x35a556 (0x3e9c5c 0x18902c54 0x1 0x1b)

0x47b3ba38 : 0x35b163 (0x1 0x1 0x1000 0x1b)

0x47b3ba88 : 0x349f3b (0x5a849b00 0x1 0x10000 0x5a849b36)

0x47b3baa8 : 0x896ee00c (0x5a849b00 0x1 0x47b3bacc 0x0)

0x47b3bad8 : 0x2025cd (0x690ce00 0x68c7c04 0x2 0x47b3bb48)

0x47b3bb38 : 0x232a47 (0x68c7c04 0x2 0x5a849b00 0x678e904)

0x47b3bc78 : 0x239d75 (0x5a849b00 0x0 0x0 0x7228334)

0x47b3bd88 : 0x23d8f2 (0x7228394 0x5a6e9e00 0x10 0x1000)

0x47b3bdc8 : 0x35f5cc (0x722816c 0x0 0x5a6e9e00 0x0)

0x47b3be68 : 0x363e7e (0x722816c 0x0 0x7556580 0x5a6e9e00)

0x47b3bec8 : 0x36411a (0x7556580 0x0 0x6e1bbd4 0x0)

0x47b3bf68 : 0x378337 (0x6ea25dc 0x6e1bb90 0x6e1bbd4 0x0)

0x47b3bfc8 : 0x19acae (0x6d1a820 0x0 0x19d0b5 0x6755c14) No mapping exists for frame pointer

Backtrace terminated-invalid frame pointer 0xb01019c8

Kernel loadable modules in backtrace (with dependencies):

com.vmware.kext.vmnet(1.0.0d1)@0x896eb000

Kernel version:

Darwin Kernel Version 8.8.1: Mon Sep 25 19:42:00 PDT 2006; root:xnu-792.13.8.obj~1/RELEASE_I386

[rcardona2k]

>I uninstalled the Fusion beta, and I was able to copy without problems after that.

A simpler way to possibly avoid the crashes is to shutdown Fusion host networking and unload the VMware kernel extensions, you can do this by running:

sudo /Library/Application\ Support/VMware\ Fusion/boot.sh --stop

To re-enable Fusion networking, you can change --stop to --start above. BTW, do you have any customizations to nat.conf on your MacPro?

[Henri]

Got the crashes sometimes as I used Apple Remote Desktop (ARD 3) to copy files to the MACPro. This seams to be very simular. I got a post regarding Parallels. Same trouble. So maybe it's Apples mistake ....

Thanks you very much for the posts.

Best regrads

Henri

[kaolson]

Got the crashes sometimes as I used Apple Remote

Desktop (ARD 3) to copy files to the MACPro. This

seams to be very simular. I got a post regarding

Parallels. Same trouble. So maybe it's Apples mistake

....

Thanks you very much for the posts.

Best regrads

Henri

Henri, Sorry for the dual-posting! I posted to the os x forum by mistake (had both open at the time), but I think this is the best place.

Can you link to the parallels thread?

I can reliably reproduce a kernel panic in 10.4.8 by ejecting a volume mounted from a host system (default afp mount) that is either of two macintel systems (mini & mbp).

Problem started when I installed Fusion, went away when I de-installed. Both systems also have Parallels (latest build but one) installed.

The workaround of unloading the networking kexts makes me nervous -- sooner or later I'll forget, and then KABLOOEY!

[rcardona2k]

can reliably reproduce a kernel panic in 10.4.8 by ejecting a volume mounted from a host system (default afp mount) that is either of two macintel systems (mini & mbp).

Can you clarify this for me? I have been AFP mounting remote shares from my home network, over the Internet and to .Mac with no problems. Ejecting (unmounting) these AFP shares has worked flawlessly for me on an MBP. Are you sharing an AFP mount via Shared Folders or am I missing something? Please post exact steps to reproduce. Thanks in advance.

[kaolson]

can reliably reproduce a kernel panic in 10.4.8 by

ejecting a volume mounted from a host system (default

afp mount) that is either of two macintel systems

(mini & mbp).

Can you clarify this for me? I have been AFP

mounting remote shares from my home network, over the

Internet and to .Mac with no problems. Ejecting

(unmounting) these AFP shares has worked flawlessly

for me on an MBP. Are you sharing an AFP mount via

Shared Folders or am I missing something? Please

post exact steps to reproduce. Thanks in advance.

Well, from any of my systems (mini, mbp, g4 pb), I'd connect to the mini or mbp with a vanilla Finder Network connect and mount the user's home. So, note this is not a windows sharing thing, all done in the host. When I disconnected by ejecting the mounted volume with the Finder, the mini and mbp kernel panic'd immediately. Didnt matter whether I'd actually copied anything or not (after the first couple of times I tried connect and immediate disconnect, same results). Fusion was not running in all but one case. Ditto Parallels.

As it happened, Fusion was the last thing I'd installed on both the mini and mbp, so I ran the Fusion uninstaller script (which worked great, BTW, but could give a little more user feedback while prompting for admin password five or six times) and the problem went away.

Cant think of anything else to add. Oh, for both systems, the user I was connecting as is the system owner/admin. And both systems have Parallels installed. Both systems are at 10.4.8 with all current updates per Software Update.

I hope to get the time tomorrow to re-install Fusion on the mini and try it again, this time toggling networking (as recommended above) for the control instead of uninstalling.

HTH. Give a shout if more ?s.

[kaolson]

can reliably reproduce a kernel panic in 10.4.8

by

ejecting a volume mounted from a host system

(default

afp mount) that is either of two macintel systems

(mini & mbp).

Can you clarify this for me? I have been AFP

mounting remote shares from my home network, over

the

Internet and to .Mac with no problems. Ejecting

(unmounting) these AFP shares has worked

flawlessly

for me on an MBP. Are you sharing an AFP mount

via

Shared Folders or am I missing something? Please

post exact steps to reproduce. Thanks in advance.

Well, from any of my systems (mini, mbp, g4 pb), I'd

connect to the mini or mbp with a vanilla Finder

Network connect and mount the user's home. So, note

this is not a windows sharing thing, all done in the

host. When I disconnected by ejecting the mounted

volume with the Finder, the mini and mbp kernel

panic'd immediately. Didnt matter whether I'd

actually copied anything or not (after the first

couple of times I tried connect and immediate

disconnect, same results). Fusion was not running in

all but one case. Ditto Parallels.

As it happened, Fusion was the last thing I'd

installed on both the mini and mbp, so I ran the

Fusion uninstaller script (which worked great, BTW,

but could give a little more user feedback while

prompting for admin password five or six times) and

the problem went away.

Cant think of anything else to add. Oh, for both

systems, the user I was connecting as is the system

owner/admin. And both systems have Parallels

installed. Both systems are at 10.4.8 with all

current updates per Software Update.

I hope to get the time tomorrow to re-install Fusion

on the mini and try it again, this time toggling

networking (as recommended above) for the control

instead of uninstalling.

HTH. Give a shout if more ?s.

Sorry, guess that wasnt quite exact steps. Here goes:

From one system connect to another with Fusion installed.

In the Finder, follow the Network path to the system with Fusion installed and connect, selecting the home directory of the user as whom you're connecting. Then disconnect by ejecting the mount point in the Finder window. System with Fusion installed panics.

-K

[rcardona2k]

>From one system connect to another with Fusion installed. In the Finder, follow the Network path to the system with Fusion installed and connect, selecting the home directory of the user as whom you're connecting. Then disconnect by ejecting the mount point in the Finder window. System with Fusion installed panics.

I have Fusion Build 36932 and Parallels 2.5.3120 installed on a MacBook Pro running OS X 10.4.8. From a G4 box (also running AFP sharing) on my home network, over wireless, I AFP remotely mount my home directory residing on the MacBook Pro. I copy a few files over, then on the G4 I unmount my home directory that lives on the MBP with Fusion. I am logged in as an admin and owner - I don't get a kernel panic. All VMware and Parallels kexts are loaded (and have been since startup).

[kaolson]

>From one system connect to another with Fusion

installed. In the Finder, follow the Network path to

the system with Fusion installed and connect,

selecting the home directory of the user as whom

you're connecting. Then disconnect by ejecting the

mount point in the Finder window. System with Fusion

installed panics.

I have Fusion Build 36932 and Parallels 2.5.3120

installed on a MacBook Pro running OS X 10.4.8. From

a G4 box (also running AFP sharing) on my home

network, over wireless, I AFP remotely mount my home

directory residing on the MacBook Pro. I copy a few

files over, then on the G4 I unmount my home

directory that lives on the MBP with Fusion. I am

logged in as an admin and owner - I don't get a

kernel panic. All VMware and Parallels kexts are

loaded (and have been since startup).

I figured everyone wasnt seeing it. Hmm... I have a slightly older version of Parallels. Only thing I can add is I use Bridged Networking.

Just re-installed and tried it again, same results. Rebooted and ran it to check the version under About VMWare Fusion -- panic'd again when the About sheet opened. Rebooted and was able to check the configuration & quite without problem.

So I'll test the workaround you mentioned above, but can you please clarify "shutdown Fusion host networking" -- does that mean uncheck all the network addapters in the host's Network system prefs before executing the boot.sh script?

Then I'll update Parallels and see if anything changes.

Any idea how many users are seeing this?

Thanks,

-K

[rcardona2k]

>Only thing I can add is I use Bridged Networking.

I can try this.

>So I'll test the workaround you mentioned above, but can you please clarify "shutdown Fusion host networking" -- does that mean uncheck all the network addapters in the host's Network system prefs before executing the boot.sh script?

No, it simply means, running "boot.sh --stop" that's all.

[kaolson]

>Only thing I can add is I use Bridged Networking.

I can try this.

>So I'll test the workaround you mentioned above, but

can you please clarify "shutdown Fusion host

networking" -- does that mean uncheck all the network

addapters in the host's Network system prefs before

executing the boot.sh script?

No, it simply means, running "boot.sh --stop" that's

all.

'boot.sh --stop' does the trick. Tomorrow I'll update Parallels, at least that'll make our environments a closer match. Odds bodkins! Long day. Thanks for your help.

-K

[rcardona2k]

>>Only thing I can add is I use Bridged Networking.

I can try this.

Did you mean, wired v. wireless networking? I wired my MacBook Pro, turned off Airport and repeated both mounting remote AFP volumes and having my MBP's drive shared (mounted remotely). When I unmounted in all cases, I received no kernel panics. Do you have AppleTalk active on any of your network interfaces? I tried both with AppleTalk active and not - same result - no panics.

[kaolson]

>>Only thing I can add is I use Bridged Networking.

I can try this.

Did you mean, wired v. wireless networking? I wired

my MacBook Pro, turned off Airport and repeated both

mounting remote AFP volumes and having my MBP's drive

shared (mounted remotely). When I unmounted in all

cases, I received no kernel panics. Do you have

AppleTalk active on any of your network interfaces?

I tried both with AppleTalk active and not - same

result - no panics.

Sorry, should have covered that. Typical small network, DLink wired/wireless router; the macintels have been wired throughout (connected on en0). DHCP. No AppleTalk. On both systems, Fusion Bridged Networking selected.

So what happens on the system being dismounted -- the dismount-ee as opposed to the dismount-er -- that clashes with those kernel extensions? Seems like the act of being dismounted should be focused enough, no?

[Henri]

To clearify, this thread is MacPro related. Please check:

MacPro:

-> kextstat | grep AppleIntel8254XEthernet

91 0 0x3c121000 0x1a000 0x19000 com.apple.driver.AppleIntel8254XEthernet (1.1.4a5) <88 16 5 4 3 2>

MacBook Pro:

kextstat | grep AppleIntel8254XEthernet

(null)

It seams to me, that the Gigabit Ethernet driver (AppleIntel8254XEthernet) of the MacPro tries sometimes to double free memory, which results in a kernel panic.

Best regards

Henri

[rcardona2k]

>To clarify, this thread is MacPro related.

The nature of this thread is that others will chime in with their network kernel panics. The original thread is clearly MacPro network driver-related.

kaolson introduced the possibillty of another network-related kernel panic with Apple File Protocol (AFP) on Mac Minis and a MacBook Pro

>I can reliably reproduce a kernel panic in 10.4.8 by ejecting a volume mounted from a host system (default afp mount) that is either of two macintel systems (mini & mbp).

The latter should probably have its own thread.

[kaolson]

>To clarify, this thread is MacPro related.

The nature of this thread is that others will chime

in with their network kernel panics. The original

thread is clearly MacPro network driver-related.

kaolson introduced the possibillty of another

network-related kernel panic with Apple File Protocol

(AFP) on Mac Minis and a MacBook Pro

>I can reliably reproduce a kernel panic in 10.4.8 by

ejecting a volume mounted from a host system (default

afp mount) that is either of two macintel systems

(mini & mbp).

The latter should probably have its own thread.

Shall I start a separate thread? Eg, "Kernel Panic with Fusion kexts loaded: mini & mbp" ?

Updated Parallels on the mini to Build 3120, got same kp. Want to see the Problem Report dump?

-K

[rcardona2k]

>Shall I start a separate thread? Eg, "Kernel Panic with Fusion kexts loaded: mini & mbp" ?

Want to see the Problem Report dump?

This is probably a good opportunity for both: creating your own thread and seeding it with the panic.log entry for your kernel panic. Thanks!