Files
kfitz.info/content/blog/2005-02-11-kernel-panic.md
Kathleen Fitzpatrick 655ad0ded8 upgrade to 3.0
2024-10-14 19:27:15 -04:00

2.3 KiB
Raw Permalink Blame History

title, date, permalink, tags
title date permalink tags
Kernel Panic 2005-02-11T11:43:11-05:00 /kernel-panic/
computers

So, my first-generation flat-panel iMac at home crashed this morning, for the first time in at least a year. Id rebooted the machine about three weeks ago, but only because of the move; unless Im updating software, theres never any reason for me to restart. Needless to say, I was not expecting a kernel panic.

And, frankly, have never witnessed one like this. The old 10.2 kernel panics were terrifying to behold: the screen image would suddenly shatter and sort of melt, and there wasnt any real sense of what was going on. The 10.3 panics are eerily calm: the screen greys out, from top to bottom, as if a shade were being drawn, and a soothing message appears on-screen informing you that the operating system has become unstable and needs to be rebooted. Ive only gotten a couple of those since upgrading to 10.3, but while they lack the sheer terror of the old schizoid panics, their very calmness instills a different kind of fear, as if your secretary were to call you and announce, in a too-even tone of voice, that the Department of Homeland Security wished to have a word with you.

This mornings was something else entirely. Im still stuck with my dial-up connection, as Verizon hasnt gotten its DSL act together for me yet, and so I passed by the computer on my way out of the room, selected “connect” from the modem menu, and went off to take care of something else. When I returned, a minute or so later, my screen had turned into a PC, circa 1990 — pre GUI, black screen, white pixellated text scrolling up and up and up, as if DOS had gotten caught in some mid-boot loop. On the screen, the kernel panic info:

Exception state (sv=0x00337230)
PC=0x00337380; MSR=0x0001030; DAR=0x003373D8; DSISR=0x003373E0; LR=0x003373C8; R1=0x003372B8; XCP=0x003373E8 (Unknown code)

Backtrace: backtrace terminated — unaligned frame address: 0x003372B8

Yes, I wrote the whole thing down. Something about it seriously creeped me out: the thing I love about OS X is that I can see the machines command-line guts if I want to, but I dont have to. I felt weirdly like my computer had suddenly opened its raincoat to show me something I most distinctly did not want to see.