From: "Haar János" <djani22@netcenter.hu>
To: "Jim Crilly" <jim@why.dont.jablowme.net>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: How to send a break? - dump from frozen 64bit linux
Date: Sun, 28 May 2006 09:04:27 +0200 [thread overview]
Message-ID: <004501c68225$00add170$1800a8c0@dcccs> (raw)
In-Reply-To: 20060527234350.GA13881@voodoo.jdc.home
----- Original Message -----
From: "Jim Crilly" <jim@why.dont.jablowme.net>
To: "Haar János" <djani22@netcenter.hu>
Cc: <linux-kernel@vger.kernel.org>
Sent: Sunday, May 28, 2006 1:43 AM
Subject: Re: How to send a break?
> On 05/27/06 02:58:44PM +0200, Haar János wrote:
> > Hello, list,
> >
> > I wish to know, how to send a "BREAK" to trigger the sysreq functions on
the
> > serial line, using echo.
> >
> > I mean like this:
> >
> > #!/bin/bash
> > echo "?BREAK?" >/dev/ttyS0
> > sleep 2
> > echo "m" >/dev/ttyS0
> >
>
> Is there a reason you can't use "echo -n m > /proc/sysrq-trigger"?
Yes, i want to dump my frequently frozen remote server, automatically, if it
is possible. (using null-modem cable, and another server.)
Anyway, i made it this time by hand.
Here is the dump:
http://download.netcenter.hu/bughunt/20060528/log.txt (400KB!)
Can somebody tell me, what is wrong exactly?
Anyway, i interested about, how can i -a single user- interpret these dump
to made error reporting more useful?
The problem:
I used one stable system on 32bit, but i need to switch to X86_64, because
the nbd cannot use >2TB devices on 32bit.
I have reinstall the RH 9.0 to FC 5.0, and recompiled everything what i used
to serving. (the OS is only for external tasks.)
But on 64bit, my system becomes unstable.
Sometimes it is frozen, but no error message at all!
I can see, the crond-jobs is hangs too, but syslog can post messages, but no
valuable at all.
(I cannot login with ssh.)
Thats why i need to dump with serial console.
Can somebody help me? :-)
Here is the "normal" dmesg message:
http://download.netcenter.hu/bughunt/20060528/dmesg.txt (21KB)
Thanks,
Janos
>
> Jim.
> -
> 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/
next prev parent reply other threads:[~2006-05-28 7:05 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 ` Haar János [this message]
2006-05-28 16:17 ` How to send a break? - dump from frozen 64bit linux Jesper Juhl
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='004501c68225$00add170$1800a8c0@dcccs' \
--to=djani22@netcenter.hu \
--cc=jim@why.dont.jablowme.net \
--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