mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "Haar János" <djani22@netcenter.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to send a break? - dump from frozen 64bit linux
Date: Sun, 28 May 2006 18:17:19 +0200	[thread overview]
Message-ID: <9a8748490605280917l73f5751cmf40674fc22726c43@mail.gmail.com> (raw)
In-Reply-To: <004501c68225$00add170$1800a8c0@dcccs>

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

  reply	other threads:[~2006-05-28 16:17 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-27 12:58 How to send a break? Haar János
2006-05-27 23:43 ` Jim Crilly
2006-05-28  7:04   ` How to send a break? - dump from frozen 64bit linux Haar János
2006-05-28 16:17     ` Jesper Juhl [this message]
2006-05-28 17:34       ` Haar János
2006-05-29  4:37         ` Jesper Juhl
2007-08-20  7:44           ` Andev Debi
2006-05-30 10:22         ` Janos Haar
2006-05-30 19:03           ` Valdis.Kletnieks
2006-05-30 21:44             ` Janos Haar
2006-05-31  1:20             ` Steven Rostedt
2006-05-31  4:38               ` XFS related hang (was Re: How to send a break? - dump from frozen 64bit linux) Nathan Scott
2006-05-31  8:00                 ` Janos Haar
2006-05-31 21:54                   ` Jan Engelhardt
2006-06-01  7:29                     ` Janos Haar
2006-06-01  9:44                       ` Jan Engelhardt
2006-06-01 22:04                         ` Nathan Scott
2006-06-02  5:11                           ` Jan Engelhardt
2006-06-01 21:58                   ` Nathan Scott
2006-06-01 22:14                     ` Janos Haar
2006-06-01 23:43                       ` Nathan Scott
2006-06-02  8:01                         ` Janos Haar
2006-05-28 23:06 ` How to send a break? H. Peter Anvin
2006-05-29 15:08 ` linux-os (Dick Johnson)
2006-05-29 15:35   ` Valdis.Kletnieks
2006-05-29 17:32     ` Haar János

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9a8748490605280917l73f5751cmf40674fc22726c43@mail.gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=djani22@netcenter.hu \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®