Kernel Panics

2»

Comments

  • Reply 21 of 28
    [quote]Originally posted by Mac The Fork:

    <strong>It would be impossible to implement basic mouse control within the kernel?.</strong><hr></blockquote>*shrug*



    No, it's not impossible, but that doesn't mean it's a good idea. The more you move into the kernel, the more instable it may become. As rare as a KP occurs, it's not worth the effort (and it would take some crazy effort) and possible new errors for something as frivalous as this.
  • Reply 22 of 28
    I've had maybe three kernel panics during my usage of OS X. The first was on second day of usage, which almost made me shy away completely from the OS. A week later I felt it was time to give it a chance again, and I like it a lot, all aspects of it. I wouldn't be able to do serious DTP-work in it, and I still need to boot into OS 9 if I were to do any serious illustrating but other than that it works like a charm. I have a factory-installed cube with no extra perapharelia (sp??) installed and did nothing out of the ordinary for any of my kernel panics. I'm pretty sure Classic was running during all cases though. *shrugs*
  • Reply 23 of 28
    stimulistimuli Posts: 564member
    Actually, it is pretty unrealistic to have a restart dialogue. First, that dialogue box would have to exist in the kernel, along with the fonts/pixmaps for it. Second, and more importantly, if you have a kernel panic, it means the core of your OS is ****ed, so it will 99.99999% of the time be too ****ed to throw up the dialogue box.



    Third, if the window manager is ****ed, the mouse and keyboard will not work.



    Fourth, if the window manager is fuxXored, you won't have the lovely transparency effects and aqua buttons, and the crash dialogue won't be 'lickable'.



    Fifth, for diagnostics purposes, kernel panic output is far handier than "you have crashed. Restart"
  • Reply 24 of 28
    [quote]Fifth, for diagnostics purposes, kernel panic output is far handier than "you have crashed. Restart" <hr></blockquote>



    I can understand if there are overwhelming technical issues preventing the display of a black and white box with mouse control, but I don't totally buy that diagnostic line.



    You have to think about how much of the Mac OS X market would simply be scared (and thus punished for using their computer) by a standard kernel panic, versus the *n*x pros and gung-ho Comp. Sci. majors. who would find the information at all useful.



    If nothing polished can be done when the panic occurs, Apple should at least change the wording and layout of the error message to reflect that Mac OS X is a professionally-made, consumer OS, with elegance as a defining factor against its competitors.
  • Reply 25 of 28
    newnew Posts: 3,244member
    [quote] (It also gets slower during use. upto a point where a restart is required. The Cube doesn't do this.)

    ---------------------------------------------------------------

    It sounds like you've got low memory and OSX is paging to the disk. How much RAM do you have?

    <hr></blockquote>



    384?!? <img src="graemlins/hmmm.gif" border="0" alt="[Hmmm]" />
  • Reply 26 of 28
    stimulistimuli Posts: 564member
    type:

    free -m

    to see how much free ram you have (hope it works on OSX)



    If you leave your system on for ages, eventually all the system stuff and apps, at one point in time or another, get loaded into ram. Restarting is like wiping the slate clean.
  • Reply 27 of 28
    emaneman Posts: 7,204member
    [quote]Originally posted by stimuli:

    <strong>type:

    free -m

    to see how much free ram you have (hope it works on OSX)

    </strong><hr></blockquote>



    Just tried that... doesn't work in X.
  • Reply 28 of 28
    serranoserrano Posts: 1,806member
    [quote]Originally posted by New:

    <strong>



    384?!? <img src="graemlins/hmmm.gif" border="0" alt="[Hmmm]" /> </strong><hr></blockquote>



    i'm guessing you're running classic and the true blue environment is getting ram hungry on you, open up proccess viewer (you don't seem terminal friendly) and kill it.
Sign In or Register to comment.