[malique]

Hi I am on the search for the cause of my 1-KP-per day. This appears since 3 or 4 days, everytime when I run VLC or at least have it loaded.

I believe VLC doesn't install anything in the kernel area so I wonder how this would be possible.

Maybe it's the second gfx card, overheating (but this card is way too slow to be used by me for watching movies, it just shows my second screen desktop with iChat and such). The only thing I have changed was that terminalcommand to fasten the booting time again. No Haxies.

I really don't get it... is there a crashlog I could post that might help anywhere?

[Detrius]

look in /Library/Logs. Any kernel panics should show up in panic.log. There is also the subdirectory CrashReporter which may have some useful information in it.

[malique]

Originally posted by Detrius:
look in /Library/Logs.

wow thanks. I post the last 2 crashes here, it doesn't tell me a thing:

*********

Wed Dec 31 18:12:53 2003


panic(cpu 0): zalloc
Latest stack backtrace for cpu 0:
Backtrace:
0x000833B8 0x0008389C 0x0001ED8C 0x00038FE0 0x00024188 0x0020BACC 0x0022F880 0x0022E3E8
0x0022E6E8 0x31273C70 0x0023DD24 0x00093D20 0x05193191
Kernel loadable modules in backtrace (with dependencies):
at.obdev.KUC(1.1.1)@0x31271000
Proceeding back via exception chain:
Exception state (sv=0x251BC280)
PC=0x9001090C; MSR=0x0000F030; DAR=0x06D9B000; DSISR=0x0A000000; LR=0x00002EF8; R1=0xBFFFFBE0; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 7.2.0:
Thu Dec 11 16:20:23 PST 2003; root:xnu/xnu-517.3.7.obj~1/RELEASE_PPC


*********

Thu Jan 1 14:22:04 2004


panic(cpu 0): zalloc
Latest stack backtrace for cpu 0:
Backtrace:
0x000833B8 0x0008389C 0x0001ED8C 0x00038FE0 0x00024188 0x0020BACC 0x0022F880 0x0022E3E8
0x0022E6E8 0x2D409C70 0x0023DD24 0x00093D20 0x724A46F6
Kernel loadable modules in backtrace (with dependencies):
at.obdev.KUC(1.1.1)@0x2d407000
Proceeding back via exception chain:
Exception state (sv=0x25377A00)
PC=0x9001090C; MSR=0x0000F030; DAR=0xE028E000; DSISR=0x42000000; LR=0x00002EF8; R1=0xBFFFFBE0; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 7.2.0:
Thu Dec 11 16:20:23 PST 2003; root:xnu/xnu-517.3.7.obj~1/RELEASE_PPC


*********

Crash reporter doesn't contain any files.

[wadesworld]

Kernel loadable modules in backtrace (with dependencies):
at.obdev.KUC(1.1.1)@0x31271000

Aha. That clearly points to the LaunchBar folks. Do you have it installed? If so, uninstall it and your problems should go away. Report it to the LaunchBar folks.

You may have to manually remove the kernel extension.

Wade

[malique]

Originally posted by wadesworld:
Aha. That clearly points to the LaunchBar folks. Do you have it installed? If so, uninstall it and your problems should go away. Report it to the LaunchBar folks.

You may have to manually remove the kernel extension.

Wade

No, this is not it. AFAIK there IS no kext, Launchbar is just one app? I quit it, removed it from startobjects - and WHOOM! There is my kernel-panic-per day again, some hours later.

I don't get it.

[someone_else]

This panic does point to the LaunchBar folks, but it's not LB. They also make a product called "Little Snitch", which requires a kernel extension. I would guess this is the culprit.

Send your panic.log file to OBDev and check to make sure you have the lastest version of Little Snitch. In the meantime, uninstall Little Snitch.

For the tecnically curious:

zalloc() is the lowest level memory allocator in the kernel.

Here is the backtrace:
0x1ed8c <panic+472>: lwz r0,556(r29)
0x38fe0 <zalloc_canblock+348>: li r29,1
0x24188 <kalloc_canblock+212>: lwz r0,104(r1)
0x20bacc <_MALLOC+128>: cmpwi cr7,r3,0
0x22f880 <getsockaddr+68>: mr r5,r30
0x22e3e8 <socketpair+716>: mr. r31,r3
0x22e6e8 <sendto+136>: lwz r0,136(r1)
# little snitch patch is next
0x31273c70: Cannot access memory at address 0x31273c70
0x23dd24 <unix_syscall+580>: lwz r0,16412(r27)

Little Snitch patches the the kernel syscall dispatch table and intercepts network related syscalls (sendto in this case). It looks like Little Snitch is doing something to cause sendto to corrupt socket info or memory and then zalloc fails.

According to the 10.3.1 kernel source, zalloc() is panicing because kernel_memory_allocate() failed for some other reason than low memory. This shouldn't happen.

HTH.

[malique]

Originally posted by someone_else:
This panic does point to the LaunchBar folks, but it's not LB. They also make a product called "Little Snitch", which requires a kernel extension. I would guess this is the culprit.HTH.

It seems you DO live in the Promised Land. THANK YOU. I have LS and will RIGHT NOW uninstall it....