From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?iso-8859-2?B?R+Fib3IgTOlu4XJ0?= Subject: Re: kernel panic Date: Thu, 24 Jul 2003 09:29:06 +0200 Sender: linux-8086-owner@vger.kernel.org Message-ID: <20030724072906.GC18217@vega.digitel2002.hu> References: <20030724044745.71119.qmail@web8206.mail.in.yahoo.com> Reply-To: lgb@lgb.hu Mime-Version: 1.0 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Content-Disposition: inline In-Reply-To: <20030724044745.71119.qmail@web8206.mail.in.yahoo.com> List-Id: Content-Type: text/plain; charset="iso-8859-1" To: mount me Cc: Linux-8086@Vger.Kernel.Org On Thu, Jul 24, 2003 at 05:47:45AM +0100, mount me wrote: > Hi all, > what does "kernel panic" actually mean ? In general it indicates a major problem which should not occured and be= cause kernel does not know what it should do in case of this problem, or even the problem should not be occured, it reports kernel panic. A good example is the example where the root filesystem cannot be mount= ed. Since booting the OS _REQUIRES_ to mount the filesystem it's perfectly = clear that kernel can't continue the boot procedure (since eg running init sh= ould be done from filesystem) so it stops there and indicates the problem wi= th a message like kernel panic. This message itself is not too meaningful, you should see another messa= ge as well describes the problem caused the kernel panic. - G=E1bor (larta'H) - To unsubscribe from this list: send the line "unsubscribe linux-8086" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html