Messages in this thread | | | Date | Sun, 28 May 2006 18:17:19 +0200 | From | "Jesper Juhl" <> | Subject | Re: How to send a break? - dump from frozen 64bit linux |
| |
On 28/05/06, Haar János <djani22@netcenter.hu> wrote: > > Can somebody tell me, what is wrong exactly? > I can't tell you exactely what's wrong unfortunately, but after looking at your dump & dmesg I notice two things that might be worth trying to change :
1) You seem to be running without any swap space at all. I't usually a good idea always to have some swap configured - try adding a swap file. (note: I don't think this will help with your current problem, it's just a good thing to do generally).
2) You should try the latest stable kernel. Currently that's 2.6.16.18 (http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.16.18.tar.bz2). There have been lots of fixes added since 2.6.15.x and perhaps you are lucky that whatever is giving you trouble has already been fixed in that kernel.
> Anyway, i interested about, how can i -a single user- interpret these dump > to made error reporting more useful? > You can find some info in Documentation/sysrq.txt & Documentation/oops-tracing.txt . As for posting good error/bug reports, please read the REPORTING-BUGS file in the root of the kernel source dir.
-- Jesper Juhl <jesper.juhl@gmail.com> Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html Plain text mails only, please http://www.expita.com/nomime.html - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |