website consistently kernel panicking my machine
This is quite worrying because of the fact it is doing it consistently and it is just a web page.
Basically what I did was go to www.autotrader.com and then choose the American site.
Then I clicked Find Your Car
I entered a code in the postcode section and picked used cars
Then I just hit submit
Then the browser hung up and the dock and soon afterwards kernel panic
My machine is an Intel Mac Mini solo running 10.4.6 and Safari 2.0.3
The logfile says:
*********
Mon Dec 4 13:47:51 2006
panic(cpu 0 caller 0x0014141D): zalloc: "ipc kmsgs" (226736 elements) retry fail 3
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0xb0f3ce8 : 0x128b5e (0x3bbeb8 0xb0f3d0c 0x131bbc 0x0)
0xb0f3d28 : 0x14141d (0x3bcbc4 0x3bba9c 0x375b0 0x3)
0xb0f3d88 : 0x141649 (0x13f2760 0x1 0xb0f3dd8 0x194f61)
0xb0f3da8 : 0x11c98d (0x13f2760 0x1ba7c80 0x13f2808 0x0)
0xb0f3dd8 : 0x12b307 (0x58 0x0 0x0 0x0)
0xb0f3e18 : 0x124902 (0x9666e00 0x0 0x28 0xb0f3efc)
0xb0f3f28 : 0x192efc (0xb0f3f54 0x0 0x0 0x0)
0xb0f3fd8 : 0x197fa6 (0x2538278 0x2538278 0x4a1000 0xb0f3eec) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xbfffca88
Kernel version:
Darwin Kernel Version 8.6.1: Tue Mar 7 16:55:45 PST 2006; root:xnu-792.9.22.obj~1/RELEASE_I386
*********
Mon Dec 4 14:01:12 2006
panic(cpu 0 caller 0x0014141D): zalloc: "mk_timer" (243955 elements) retry fail 3
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0xb35be38 : 0x128b5e (0x3bbeb8 0xb35be5c 0x131bbc 0x0)
0xb35be78 : 0x14141d (0x3bcbc4 0x3bc43c 0x3b8f3 0x3)
0xb35bed8 : 0x141649 (0x15b46c0 0x1 0x0 0x1301d7)
0xb35bef8 : 0x12ffea (0x15b46c0 0x9832000 0x282089c 0x98366e8)
0xb35bf28 : 0x192efc (0xb35bf54 0x3e3a00 0x48 0x0)
0xb35bfd8 : 0x197fa6 (0x2637ac8 0x2637ac8 0x4a1000 0xb35beec) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xbfffcb58
Kernel version:
Darwin Kernel Version 8.6.1: Tue Mar 7 16:55:45 PST 2006; root:xnu-792.9.22.obj~1/RELEASE_I386
Can anyone else run through the procedure to see if they get a kernel panic? Please only try this if you have saved your documents in case it gives you a kernel panic too.
Basically what I did was go to www.autotrader.com and then choose the American site.
Then I clicked Find Your Car
I entered a code in the postcode section and picked used cars
Then I just hit submit
Then the browser hung up and the dock and soon afterwards kernel panic
My machine is an Intel Mac Mini solo running 10.4.6 and Safari 2.0.3
The logfile says:
*********
Mon Dec 4 13:47:51 2006
panic(cpu 0 caller 0x0014141D): zalloc: "ipc kmsgs" (226736 elements) retry fail 3
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0xb0f3ce8 : 0x128b5e (0x3bbeb8 0xb0f3d0c 0x131bbc 0x0)
0xb0f3d28 : 0x14141d (0x3bcbc4 0x3bba9c 0x375b0 0x3)
0xb0f3d88 : 0x141649 (0x13f2760 0x1 0xb0f3dd8 0x194f61)
0xb0f3da8 : 0x11c98d (0x13f2760 0x1ba7c80 0x13f2808 0x0)
0xb0f3dd8 : 0x12b307 (0x58 0x0 0x0 0x0)
0xb0f3e18 : 0x124902 (0x9666e00 0x0 0x28 0xb0f3efc)
0xb0f3f28 : 0x192efc (0xb0f3f54 0x0 0x0 0x0)
0xb0f3fd8 : 0x197fa6 (0x2538278 0x2538278 0x4a1000 0xb0f3eec) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xbfffca88
Kernel version:
Darwin Kernel Version 8.6.1: Tue Mar 7 16:55:45 PST 2006; root:xnu-792.9.22.obj~1/RELEASE_I386
*********
Mon Dec 4 14:01:12 2006
panic(cpu 0 caller 0x0014141D): zalloc: "mk_timer" (243955 elements) retry fail 3
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0xb35be38 : 0x128b5e (0x3bbeb8 0xb35be5c 0x131bbc 0x0)
0xb35be78 : 0x14141d (0x3bcbc4 0x3bc43c 0x3b8f3 0x3)
0xb35bed8 : 0x141649 (0x15b46c0 0x1 0x0 0x1301d7)
0xb35bef8 : 0x12ffea (0x15b46c0 0x9832000 0x282089c 0x98366e8)
0xb35bf28 : 0x192efc (0xb35bf54 0x3e3a00 0x48 0x0)
0xb35bfd8 : 0x197fa6 (0x2637ac8 0x2637ac8 0x4a1000 0xb35beec) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xbfffcb58
Kernel version:
Darwin Kernel Version 8.6.1: Tue Mar 7 16:55:45 PST 2006; root:xnu-792.9.22.obj~1/RELEASE_I386
Can anyone else run through the procedure to see if they get a kernel panic? Please only try this if you have saved your documents in case it gives you a kernel panic too.
Comments
Had no problems seems like something is wrong with your os. Have you run first aid under disk utilities ...
Thanks for checking it out. I did it again just to see if the machine was being temperamental yesterday but it did it again with the same zalloc: "ipc kmsgs" error.
I might try upgrading to 10.4.8 and see if that fixes anything. I'm beginning to think there is something wrong with this machine because the internet chokes when other people's computers on the same network runs fine.
The disk and Ram check out fine but given that most of the trouble has happened with network stuff, it may be the Airport card.
edit: thanks Apple for making the 10.4.8 update 300MB, 'cos my network is crawling at 10k/sec now. I'll have to wait until I get home to download it.
The error also seems limited to Safari. I tried it in Firefox and it reports that there was an unresponding script and it puts the processor use to maximum but even hitting continue doesn't cause a kernel panic. BTW, you may have to enter an unrecognised zip code into the box - just type anything.
The site has what sounds like a Java script error or bug which is causing some issues. I tried on my trusty iMac G3 500MHz and it causes a kernal panic.
I guess I should submit a bug report to Apple. No website should ever cause a kernel panic. Thanks too for checking it out.
Ok so I just installed 10.4.8 and now the site doesn't kernel panic the machine. I wonder if they updated the site since yesterday or if the update fixed it.
I also now have upped to 10.4.8 with all updates and it doesn't any more. It may have either been something in the update or a temporary problems the site was having and has been fixed.
Glad to hear it's fixed for you too. I wonder if anyone can test it again on 10.4.6 or less. I have 10.4.7 at home and it didn't kernel panic there either. I'm a bit concerned that it was just the site getting updated because it means that such a thing might still be able to kernel panic a machine.