FileWave Alliance

The Official Community Forum
  • Page:
  • 1

TOPIC: Kernel Panic on a 10.5.2 client, caused by fwcld ?

Kernel Panic on a 10.5.2 client, caused by fwcld ? 16 Jun 2008 15:40 #78

  • jean-philippe.sakael
  • jean-philippe.sakael's Avatar Topic Author
  • Offline
  • 2nd Level - Yellow Belt
  • 2nd Level - Yellow Belt
  • Posts: 43
  • Karma: 1
  • Thank you received: 4
Hi,

one client here (iMac, Mac OS X 10.5.2) has panicked after grabbing a Acrobat Pro 8 fileset (created from the Adobe Installers using the Fileset X Magic assistant). This fileset has worked OK on a few other clients (not widely used yet since it's being validated).

This is what I got from the panic log :

Mon Jun 16 16:19:59 2008
panic(cpu 0 caller 0x001A8C8A): Kernel trap at 0x00449cff, type 14=page fault, registers:
CR0: 0x80010033, CR2: 0x00000027, CR3: 0x01117000, CR4: 0x00000660
EAX: 0x00000000, EBX: 0x00000027, ECX: 0x045a44f0, EDX: 0x6e700000
CR2: 0x00000027, EBP: 0x403df5d8, ESI: 0x00000001, EDI: 0x00000027
EFL: 0x00010206, EIP: 0x00449cff, CS: 0x00000008, DS: 0x00000010
Error code: 0x00000000

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x403df3e8 : 0x12b0e1 (0x457024 0x403df41c 0x13321a 0x0)
0x403df438 : 0x1a8c8a (0x460550 0x449cff 0xe 0x45fd00)
0x403df518 : 0x19eb67 (0x403df530 0x1 0x403df5d8 0x449cff)
0x403df528 : 0x449cff (0xe 0x48 0x4590070 0x4590010)
0x403df5d8 : 0x44b5ee (0x27 0x3019a6b0 0x403df5f8 0x479dc04)
0x403df608 : 0x2069a7 (0x44c0f84 0x3a 0x14 0x410c004)
0x403df628 : 0x208717 (0x44c0f84 0x212 0x403df688 0x1c8535)
0x403df648 : 0x1f2eb1 (0x403df664 0x212 0x403df66c 0x4f3f40)
0x403df688 : 0x1da45f (0x4621f30 0x3f6ec64 0x0 0x0)
0x403df6d8 : 0x1da67b (0x4621f30 0x1 0x403df708 0x19d311)
0x403df728 : 0x1dc2e6 (0x0 0x4f33c0 0x485637a0 0x485637a0)
0x403df7a8 : 0x31d704 (0x0 0x34 0x403df7fc 0x483c12c)
0x403df848 : 0x325772 (0x410c004 0x4b5e250 0x403dff08 0x403df978)
0x403df9a8 : 0x1f1b5f (0x403df9c8 0x2 0x403df9f8 0x44dc07)
0x403df9f8 : 0x1d36f9 (0x4b5e250 0x403dfdf4 0x403dff08 0x3f6ec64)
0x403dfa88 : 0x1d447e (0x403dfddc 0x414000b 0x12 0x400)
Backtrace continues...

BSD process name corresponding to current thread: fwcld

Mac OS version:
9C31

Kernel version:
Darwin Kernel Version 9.2.0: Tue Feb 5 16:13:22 PST 2008; root:xnu-1228.3.13~1/RELEASE_I386
System model name: iMac7,1 (Mac-F4238CC8)

As it's the first "fwcld" KP I've experienced I'm not sure there will be a serious pattern on our clients, just to make sure there is no known issue here.

Regards,
Jean-Philippe

Kernel Panic on a 10.5.2 client, caused by fwcld ? 16 Jun 2008 20:02 #480

  • FileWave
  • FileWave's Avatar
  • Offline
  • User is blocked
  • User is blocked
  • Posts: 218
  • Thank you received: 0
We have never had a report of a Kernel Panic caused by FileWave.



It is possible that the Adobe Software being installed causes a Kernel Panic but also quite unlikely.



Was it a one time issue or does it happen at every restart attempt?

Kernel Panic on a 10.5.2 client, caused by fwcld ? 17 Jun 2008 09:08 #481

  • jean-philippe.sakael
  • jean-philippe.sakael's Avatar Topic Author
  • Offline
  • 2nd Level - Yellow Belt
  • 2nd Level - Yellow Belt
  • Posts: 43
  • Karma: 1
  • Thank you received: 4
It was a one time issue.

here is the full context:

1. The client machine had Acrobat 6 (Pro+Distiller) installed using a .pkg file we had before the FileWave switch.
2. I imported this .pkg file into FileWave and made an association between the client and this fileset.
3. I programmed the fileset deletion on this client at 11.50 AM, then I added an association with the Acrobat 8 fileset to be enabled at 11.55 AM. The Acrobat 8 fileset is based on the "Fileset reboot" template.
4. I updated the server model at around 11.30 AM. There were some tests running on that client, I waited for the tests to complete prior to close all applications.
5. The test ended a few hours later, the end user closed all applications. It allowed the Acrobat8 fileset to install.

I assume the KP occurred while trying to restart, as the Acrobat 6 fileset should have been deleted on time and the Acrobat 8 activation has been delayed a few hours but finally happened.

Kernel Panic on a 10.5.2 client, caused by fwcld ? 05 Aug 2008 11:04 #482

  • jean-philippe.sakael
  • jean-philippe.sakael's Avatar Topic Author
  • Offline
  • 2nd Level - Yellow Belt
  • 2nd Level - Yellow Belt
  • Posts: 43
  • Karma: 1
  • Thank you received: 4
Hi again,

more occurences :

Quote:

Fri Aug 1 13:55:12 2008
panic(cpu 1 caller 0x001A8C8A): Kernel trap at 0x0019c26b, type 14=page fault, registers:
CR0: 0x80010033, CR2: 0x00000000, CR3: 0x00fdc000, CR4: 0x00000660
EAX: 0x00000019, EBX: 0x3cc8f5cc, ECX: 0x00000000, EDX: 0x3cc8f5cc
CR2: 0x00000000, EBP: 0x3cc8f4e8, ESI: 0x00000019, EDI: 0x000000aa
EFL: 0x00010202, EIP: 0x0019c26b, CS: 0x00000008, DS: 0xf0000010
Error code: 0x00000000

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x3cc8f308 : 0x12b0e1 (0x457024 0x3cc8f33c 0x13321a 0x0)
0x3cc8f358 : 0x1a8c8a (0x460550 0x19c26b 0xe 0x45fd00)
0x3cc8f438 : 0x19eb67 (0x3cc8f450 0x0 0x3cc8f4e8 0x19c26b)
0x3cc8f448 : 0x19c26b (0xe 0x4a70048 0x70 0x10)
0x3cc8f4e8 : 0x1c9b7a (0x0 0x3cc8f5cc 0x19 0x0)
0x3cc8f558 : 0x1cb21c (0x0 0x1 0x3cc8f668 0x4c)
0x3cc8f578 : 0x317b30 (0x3cc8f5cc 0x19 0x0 0x0)
0x3cc8f668 : 0x31a64b (0x0 0x0 0x3cc8f978 0x3cc8f7be)
0x3cc8f7d8 : 0x31bd97 (0x4b5f 0x0 0x3cc8f978 0x3cc8f8b0)
0x3cc8f848 : 0x325469 (0x3f95804 0x3cc8f964 0x0 0x3cc8f978)
0x3cc8f9a8 : 0x1f1b5f (0x3cc8f9c8 0x2 0x3cc8f9f8 0x44dc07)
0x3cc8f9f8 : 0x1d36f9 (0x4a551c0 0x3cc8fdf4 0x3cc8ff08 0x43b8844)
0x3cc8fa88 : 0x1d447e (0x3cc8fddc 0x100 0x3cc8fdfc 0x0)
0x3cc8fb48 : 0x1e2ff0 (0x3cc8fddc 0x3d47910 0x800000 0x0)
0x3cc8fd88 : 0x1e35e4 (0xbffffa30 0x0 0x0 0x0)
0x3cc8ff48 : 0x1e367d (0xbffffa30 0x0 0x0 0x0)
Backtrace continues...

BSD process name corresponding to current thread: fwcld

Mac OS version:
9C31

Kernel version:
Darwin Kernel Version 9.2.0: Tue Feb 5 16:13:22 PST 2008; root:xnu-1228.3.13~1/RELEASE_I386
System model name: iMac7,1 (Mac-F4238CC8)

Quote:Fri Aug 1 13:55:12 2008
panic(cpu 1 caller 0x001A8C8A): Kernel trap at 0x0019c26b, type 14=page fault, registers:
CR0: 0x80010033, CR2: 0x00000000, CR3: 0x00fdc000, CR4: 0x00000660
EAX: 0x00000019, EBX: 0x3cc8f5cc, ECX: 0x00000000, EDX: 0x3cc8f5cc
CR2: 0x00000000, EBP: 0x3cc8f4e8, ESI: 0x00000019, EDI: 0x000000aa
EFL: 0x00010202, EIP: 0x0019c26b, CS: 0x00000008, DS: 0xf0000010
Error code: 0x00000000

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x3cc8f308 : 0x12b0e1 (0x457024 0x3cc8f33c 0x13321a 0x0)
0x3cc8f358 : 0x1a8c8a (0x460550 0x19c26b 0xe 0x45fd00)
0x3cc8f438 : 0x19eb67 (0x3cc8f450 0x0 0x3cc8f4e8 0x19c26b)
0x3cc8f448 : 0x19c26b (0xe 0x4a70048 0x70 0x10)
0x3cc8f4e8 : 0x1c9b7a (0x0 0x3cc8f5cc 0x19 0x0)
0x3cc8f558 : 0x1cb21c (0x0 0x1 0x3cc8f668 0x4c)
0x3cc8f578 : 0x317b30 (0x3cc8f5cc 0x19 0x0 0x0)
0x3cc8f668 : 0x31a64b (0x0 0x0 0x3cc8f978 0x3cc8f7be)
0x3cc8f7d8 : 0x31bd97 (0x4b5f 0x0 0x3cc8f978 0x3cc8f8b0)
0x3cc8f848 : 0x325469 (0x3f95804 0x3cc8f964 0x0 0x3cc8f978)
0x3cc8f9a8 : 0x1f1b5f (0x3cc8f9c8 0x2 0x3cc8f9f8 0x44dc07)
0x3cc8f9f8 : 0x1d36f9 (0x4a551c0 0x3cc8fdf4 0x3cc8ff08 0x43b8844)
0x3cc8fa88 : 0x1d447e (0x3cc8fddc 0x100 0x3cc8fdfc 0x0)
0x3cc8fb48 : 0x1e2ff0 (0x3cc8fddc 0x3d47910 0x800000 0x0)
0x3cc8fd88 : 0x1e35e4 (0xbffffa30 0x0 0x0 0x0)
0x3cc8ff48 : 0x1e367d (0xbffffa30 0x0 0x0 0x0)
Backtrace continues...

BSD process name corresponding to current thread: fwcld

Mac OS version:
9C31

Kernel version:
Darwin Kernel Version 9.2.0: Tue Feb 5 16:13:22 PST 2008; root:xnu-1228.3.13~1/RELEASE_I386
System model name: iMac7,1 (Mac-F4238CC8)


I don't have much details on the circumstances it happened.

Kernel Panic on a 10.5.2 client, caused by fwcld ? 05 Aug 2008 15:54 #483

  • FileWave
  • FileWave's Avatar
  • Offline
  • User is blocked
  • User is blocked
  • Posts: 218
  • Thank you received: 0
Please have a look in /Library/Logs/CrashReporter and see if there is a file named fwcld.crash.log, if you do see this file, then please send it to eval(unescape('%64%6f%63%75%6d%65%6e%74%2e%77%72%69%74%65%28%27%3c%61%20%68%72%65%66%3d%22%6d%61%69%6c%74%6f%3a%73%75%70%70%6f%72%74%40%66%69%6c%65%77%61%76%65%2e%63%6f%6d%22%3e%73%75%70%70%6f%72%74%40%66%69%6c%65%77%61%76%65%2e%63%6f%6d%3c%2f%61%3e%27%29%3b')). If this file doesn't exist, then the FileWave Client process is not crashing and the Kernel Panic is most likely caused by something hardware related.

Kernel Panic on a 10.5.2 client, caused by fwcld ? 04 Dec 2008 14:40 #484

  • jean-philippe.sakael
  • jean-philippe.sakael's Avatar Topic Author
  • Offline
  • 2nd Level - Yellow Belt
  • 2nd Level - Yellow Belt
  • Posts: 43
  • Karma: 1
  • Thank you received: 4
I 'm not if it's the 10.5.4 update or me stopping fooling around with too many system extensions, but our test units are very stable now



Please close this topic. 8)

Kernel Panic on a 10.5.2 client, caused by fwcld ? 05 Nov 2016 08:23 #2407

  • john Smith
  • john Smith's Avatar
  • Offline
  • 1st level - White Belt
  • 1st level - White Belt
  • Posts: 2
  • Thank you received: 0
I am Having BAD POOL HEADER Problem in MY PC.

Kernel Panic on a 10.5.2 client, caused by fwcld ? 07 Nov 2016 14:25 #2408

  • john Smith
  • john Smith's Avatar
  • Offline
  • 1st level - White Belt
  • 1st level - White Belt
  • Posts: 2
  • Thank you received: 0
here's the thing now
i does as this website said
http://www.deskdecode.com/bad-pool-header/
and now my system wont able to start
what to do now does anybody knows something

Kernel Panic on a 10.5.2 client, caused by fwcld ? 22 Nov 2016 12:37 #2413

  • Derek Deckard
  • Derek Deckard's Avatar
  • Offline
  • FileWave Staff
  • FileWave Staff
  • Posts: 33
  • Thank you received: 6
Hi kinjo23,

I don't believe your post is related to the original issue but I'll see if I can offer some advise. The problem with a "Bad Pool Header" error is tracking down the cause of it. As the article you linked said, you're best bet would be to boot into Safe Mode and undo any software/hardware changes you made to the computer recently.

If your system is no longer able to start, even in Safe Mode, your only option may be to reinstall the OS. I found the following on Microsoft's website regarding Bad Pool Header.

http://answers.microsoft.com/en-us/windows/forum/all/what-is-a-bad-pool-header-and-how-do-i-fix-it/dd7bc035-48a8-4505-a5e0-5cdefb28077b

Regards,
Derek
Last Edit: by Derek Deckard.
  • Page:
  • 1