Uh, yes, it *was* frozen solid. I was able to turn on the monitor and see
the last message on console (the kernel panic). Three-finger salute did
not work, and the server was completely unresponsive.

There is no record of an oops in any of the logfiles. Far as I could tell,
the kernel did not oops; it simply threw up the "Kernel panic: trying to
release non-existent task" message, and then hung.

I have not been able to figure out what happened, but I have since
upgraded to the 2.2.14 kernel, in the hopes that this won't happen again.

<-- .\\ -->
Matthew S. McCleary, Network Administrator          [EMAIL PROTECTED]
Los Alamos Community Network                        Work: (505) 662-6020
148 Central Park Square                             Home: (505) 672-3409
Los Alamos, NM 87544 USA                            Cell: (505) 670-3126
Web: http://www.los-alamos.net/~myrrh               ICQ: 52176494

On Wed, 12 Apr 2000, Richard Adams wrote:

> On Tue, 11 Apr 2000,  Matthew McCleary wrote about,  Kernel panic: non-existent task 
>?:
> > I got a kernel panic on our main server this afternoon. Everything just
> > froze solid--I had to go to console to figure out what was wrong. The
> > message was:
> 
> Everything froze "solid" but you could access a console, then everything
> did not freeze solid.
> 
> Did you manage to figure out what was wrong.?? you dont mention, there
> shuold be a copy of the oops in /var/log/messages / debug / syslog, in the
> message it will possably say which task it was causing the problem.
> There will be an EIP value, that value can be used with ksymoops a small
> program in the kernel source tree ./linux/scripts/ksymoops/* in the README
> in that dir, it tells you what to do.
> 
> > Kernel panic: trying to release non-existent task
> > 
> > The server is running 2.0.34. Is anyone aware what this message means, or
> > was it just a fluke? 
> 
> I would be concerned if it happend to me, however i am choosy. Nothing is
> a fluke, something hit the kernel hard and caused it to barf, in itself
> that is NOT a good thing.
> 
> > The server had an uptime of around 12 days and had
> > experienced no problems up to this point, and there was nothing
> > particularly stressful running at the time. Should I worry?
> 
> I have had machines running for more that 300 days and they have never
> missed a beat.
> 
> One thing to remember is you are running an old pre-distribution kernel, by
> that i mean, 2.0.38 {i belive} it was was the final edition in that kernel
> series and was considered to be the most stable.
> 
> Another thing to remember is, when one has such an out dated kernel and
> distribution and one keeps installing "new programs" then problems are
> going to arise.
>  
> > 
> > Thanks,
> > Matt
> > 
> > <-- .\\ -->
> > Matthew S. McCleary, Network Administrator          [EMAIL PROTECTED]
> > Los Alamos Community Network                        Work: (505) 662-6020
> > 148 Central Park Square                             Home: (505) 672-3409
> > Los Alamos, NM 87544 USA                            Cell: (505) 670-3126
> > Web: http://www.los-alamos.net/~myrrh               ICQ: 52176494
> 
> -- 
> Regards Richard
> [EMAIL PROTECTED]
> http://people.zeelandnet.nl/pa3gcu/
> 


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs

Reply via email to