Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
well, any kernel errors should be in the log files somewhere, sometimes this is an issue because the disks aren't mounted when the kernel panic occurs, hence no writing to the log files! Take a look at this: http://rhcelinuxguide.wordpress.com/...ardiac-arrest/
How to fin a 'kernel panic' error in a running a system. (It was an Interview question).
Thanks.
if you are using kdump it will create a dump file of any kernel information. However I am not sure where the log if located. But there are occasions where the kernel will panic when mounting the filesystem in which case no log will be created.
well, any kernel errors should be in the log files somewhere, sometimes this is an issue because the disks aren't mounted when the kernel panic occurs, hence no writing to the log files! Take a look at this: http://rhcelinuxguide.wordpress.com/...ardiac-arrest/
But there are occasions where the kernel will panic when mounting the filesystem in which case no log will be created.
If the kernel is totally confused, it can be unable to write logs or be unwilling to take the chance because it is so confused.
That's why a dump to swap is so valuable - assuming that you have the tools and the skill to evaluate the dump, of course. That article referenced above gives good examples of tracing.
You should realize that a panic is almost always going to be from a bad driver or bad hardware. If you've been running along for months with no changes and your system starts to panic regularly, it's probably hardware.
If it is hardware, the most common guilty party is RAM. Bad RAM can send the kernel off into the flowers, trampling all over everything until it trips and realizes "Hey, I can't go THERE!" and panics.
Above all, remember Don't panic. That's the kernel's job - Jeff Liebermann
Just a simple scenario regarding kernel panic, consider i have deleted the vmlinuz file while the sys is running. what will happen immediately(will the system continue to run) and where can i find that the vmlinuz files was deleted(I mean thr logs).
Just a simple scenario regarding kernel panic, consider i have deleted the vmlinuz file while the sys is running. what will happen immediately(will the system continue to run) and where can i find that the vmlinuz files was deleted(I mean thr logs).
Thanks.
Why dont you try out this scenario on a test system and let us know how it goes
AFAIK, when you delete a file it doesn't get logged anywhere. If its been done by some user, you need to analyse the bash_history for that user (s)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.