For the past few months I get a kernel panic every Sunday at 7PM. I have no idea why.
This is on a G4 Sawtooth machine. The HD was previously in a G3 B&W and did the same thing
from time to time, not every Sun. at 7PM though. I'm fairly sure this happens when it
runs the weekly maintenance scripts. Any ideas what is going on? And yes I've run
repair permissions fairly frequently. I'm running 10.3.9 also,and it even happens when running
10.3.9 from a different HD(fresh install,not a copy of the problem drive). From the console,under
the panic log I get this....

Sun Mar 26 19:03:29 2006


panic(cpu 0): lockmgr: locking against myself
Latest stack backtrace for cpu 0:
Backtrace:
0x00083498 0x0008397C 0x0001EDA4 0x002139D8 0x000CF268 0x000C18F8 0x001D5030 0x001D58D4
0x001DBB94 0x001DC288 0x000BEC44 0x000BE68C 0x000C83E4 0x00246D84 0x000941C0 0xFFFFFFFF
Proceeding back via exception chain:
Exception state (sv=0x2AB2EC80)
PC=0x9001478C; MSR=0x0000F030; DAR=0x2AACAF3C; DSISR=0x40000000; LR=0x90029430; R1=0xBFFFFAE0; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 7.9.0:
Wed Mar 30 20:11:17 PST 2005; root:xnu/xnu-517.12.7.obj~

Thanks for any insight.
BG

graham1352 Wrote:
-------------------------------------------------------
> For the past few months I get a kernel panic every
> Sunday at 7PM. I have no idea why.

When in fact, the rest of your post clearly suggests that you do.

> I'm fairly sure this happens when it
> runs the weekly maintenance scripts.

I believe this would be called "an idea" of why this is happening.

As it happens the maint scripts aren't supposed to run at that time -- did you ever install anything to alter that?

> Any ideas
> what is going on? And yes I've run
> repair permissions fairly frequently.

(Separate from your problem) There's no need to run permissions "frequently," particularly if you can plainly see that it's not solving the problem. Once a month maybe.

> I'm running
> 10.3.9 also,and it even happens when running
> 10.3.9 from a different HD(fresh install,not a
> copy of the problem drive).

This establishes that this is a hardware problem

From the
> console,under
> the panic log I get this....
>
>
> panic(cpu 0): lockmgr: locking against myself

I don't think you have to be a geek to decipher this. One of your CPUs is having an issue. This is most likely caused by some corrupted EPROM instructions that are set to execute on Sundays at 7pm. Even if I'm wrong about that, it's clearly a hardware problem. Time to take it into the shop.

---

chas_m




[crawlingfromtheusa.blogspot.com] <-- Moving to Canada blog

What hardware is connected?
(All USB/Firewire peripherals)
Modem connected to a phone line?
Is it on a UPS? Checked the batteries recently?

Are you usually there when it happens, or do you return to find it like that?

It happens whether I have any usb/firewire peripherals connected. I haven't
disconnected the ethernet for the cable modem yet. No UPS,and haven't checked
the PRAM battery. It's quite an odd problem.

> > panic(cpu 0): lockmgr: locking against
> myself
>
> I don't think you have to be a geek to decipher
> this. One of your CPUs is having an issue. This is
> most likely caused by some corrupted EPROM
> instructions that are set to execute on Sundays at
> 7pm. Even if I'm wrong about that, it's clearly a
> hardware problem. Time to take it into the shop.

It's a single processer Sawtooth. The thing that's odd is that it happened in my
B&W G3 as well(same HD). I suppose it would make sense that it's something with
the HD causing problems,or the HD controller. Ahhhh maybe the PCI ATA card perhaps.
Time to try some testing,
Thanks for the input.
BG