Re: 10.2.5 problem
Re: 10.2.5 problem
- Subject: Re: 10.2.5 problem
- From: Phill Kelley <email@hidden>
- Date: Sun, 13 Apr 2003 11:37:28 +1000
At 12:54 AM +0200 13/4/03, Gerriet M. Denkmann wrote:
>
I know that this is very much off topic - but I am quite desperate.
>
>
I have just upgraded to 10.2.5 and now always 7 - 12 minutes after
>
start of the computer the screen gets overlaid with a transparent gray
>
rectangle, which has a small white rectangle in the middle, telling me
>
in four languages that I have to restart the computer.
>
>
This even happens, if no one is logged in.
>
>
Maybe some kind soul could advice me what to do.
I've been down this path on a tiBook. My problem was that login, logout,
login, logout would panic on a 10.1.x system and, like you, nothing was
being written to the panic log.
Can I direct your attention to the following file:
/Developer/Documentation/Darwin/howto/
kext_tutorials/hello_debugger/hello_debugger.html
There's a lot to wade through but one of the key points is to change what
your machine does when it panics. Back in the good old days, a panic would
drop your machine into a whole-screen terminal session. It was the sort of
thing to make you sit back and say, "whoa!" but at least you got *some*
useful information.
Someone inside Apple decided that behaviour wasn't user-friendly and the
upshot of that decision is the singularly useless display you're seeing now.
About a third of the way into the above document, you'll find a section
entitled, "On Target Machine, Enable Kernel Debugging" with the key step:
sudo nvram boot-args="debug=0xe"
Doing that (or the alternative below it if you have an older machine) will
take you back to the older style of display where the traceback may give
you some clue as to what the machine was doing when it panicked.
If you have two machines, you can set up the other one following the steps
in the above document.
If you don't have it already, you will also need to obtain the gdbinit file
from the Darwin open-source server. Among other things, that gets you a
command called "paniclog".
Then, when your target panics, your monitoring machine will gain control
and you will be able to issue "paniclog".
In my case, the "terminal mode" crash display produced the backtrace
information which appeared to indicate that com.apple.driver.AppleADBMouse
was the culprit, and "paniclog" produced "Argument to arithmetic operation
not a number or boolean". So, my guess was a bad parameter being passed to
that driver.
Of course, the fact that my tiBook doesn't have ADB ports and couldn't
possibly have had an ADB mouse caused me to wonder about my sanity...
Fortunately (for me), a new system update fixed the problem before I had to
take an axe to my tiBook.
Anyway, I hope this helps you track down the cause.
Regards, Phill
--
----------------------------------------------
Phill Kelley
PO Box 661 Jamison Centre ACT Australia 2614
Voice: +61-2-6253-1015
Fax: +61-2-6253-4500
Mobile: +61-411-477-705
I am at UTC+10 (UTC+11 November through March)
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
| References: | |
| | >10.2.5 problem (From: "Gerriet M. Denkmann" <email@hidden>) |