Wednesday, August 23, 2006

Panic Error - The Commercials were WRONG!!!

For all those that think that A MAC won’t crash.. Try this on for size…

I have this PowerPC G4 “Boat Anchor” in my cube, just for support of Macs Clients that are using Entourage and for OWA Issues.. Okay, so here we are, I am working away, I have Safari and Entourage open and then all of a sudden (Poof!) I get this “Panic Error”…

panic(cpu 0 caller 0x0003FEA8): zalloc: "kalloc.16" (22241 elements) retry
fail 3
Latest stack backtrace for cpu 0:
Backtrace:
0x00095718 0x00095C30 0x0002683C 0x0003FEA8 0x0002BB0C 0x00097D44
0x00140434 0x00162040
0x00160C14 0x0028FB84 0x002A3970 0x1AAB7700 0x1AAB9084 0x1AAB5754
0x000A9914
Kernel loadable modules in backtrace (with dependencies):
com.thursby.kext.NetBIOS(3.0)@0x1aaa2000
Proceeding back via exception chain:
Exception state (sv=0x1638D500)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000;
LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 8.7.0: Fri May 26 15:20:53 PDT 2006;
root:xnu-792.6.76.obj~1/RELEASE_PPCModel: PowerMac3,1, BootROM 3.2.2f1, 1
processors, PowerPC G4 (2.8), 400 MHz, 320 MB
Graphics: ATY,Rage128Pro, ATY,Rage128Pro, AGP, 16 MB
Memory Module: DIMM0/J21, 64 MB, SDRAM, PC100-222S
Memory Module: DIMM1/J22, 64 MB, SDRAM, PC100-222S
Memory Module: DIMM2/J23, 64 MB, SDRAM, PC100-222S
Memory Module: DIMM3/J24, 128 MB, SDRAM, PC100-222S
Modem: Spring, , V.90, , APPLE VERSION 0001, 4/7/1999
Network Service: Built-in Ethernet, Ethernet, en0
Parallel ATA Device: WDC WD102BA, 9.55 GB
Parallel ATA Device: MATSHITADVD-ROM SR-8585,
USB Device: Hub, , Up to 12 Mb/sec, 500 mA
USB Device: Apple USB Mouse, Mitsumi, Up to 1.5 Mb/sec, 100 mA
USB Device: M2452, Alps Electric, Up to 1.5 Mb/sec, 100 mA


This happens every F*N DAY!!! It does not seem to matter what I have open, running or if it is just sitting there.. CRASH! Every Day!


Why Mac’s SUCK!!!
http://video.google.com/videoplay?docid=-6553260189868317794&q=why+macs+suck&hl=en


I hate Macs.

Now, being the person that I am, I did try to troubleshoot the problem. At first I thought it was RAM, so I did a test will all of the sticks. NOPE! Hard-Drive…NOPE!

I hate Macs.

1 comment:

Anonymous said...

Looks like something to do with a Thursby kernel extension. Have you tried disabling any Thursby stuff and seeing if that resolves the issue? Might be worth asking the folks at Thursby.