All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesper Juhl <jesper.juhl@gmail.com>
To: Bret Towe <magnade@gmail.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: nfs4 client bug
Date: Mon, 5 Sep 2005 22:48:32 +0200	[thread overview]
Message-ID: <9a87484905090513481118e67b@mail.gmail.com> (raw)
In-Reply-To: <dda83e78050905134420f06fbf@mail.gmail.com>

On 9/5/05, Bret Towe <magnade@gmail.com> wrote:
> On 9/4/05, J. Bruce Fields <bfields@fieldses.org> wrote:
> > On Sun, Sep 04, 2005 at 08:08:22PM -0700, Bret Towe wrote:
> > > On 9/4/05, J. Bruce Fields <bfields@fieldses.org> wrote:
> > > > Do you get anything from alt-sysrq-T?
> > >
> > > no i havent used that im usally in x when its freezing
> > > x wont even switch to console would it still give me anything then?
> >
> > Well, you can try something like:
> >         alt-sysrq-T
> > wait a couple seconds, then
> >         alt-sysrq-S
> >         alt-sysrq-U
> >         alt-sysrq-B
> > with maybe a second between each to give stuff a chance to get to disk.
> >
> > Then if you're lucky you may find the stack dumps in your log after you
> > reboot.
> 
> tried it and so far no luck ill keep trying a few more times and see
> if i can get it
> to spit somethin out to disk but i dont think ill be that lucky as that would
> prob make life to easy wouldnt it?

How about 

serial console over a cross-over cable to a second box.
netconsole will let you put the console on a different box over the network.
console on line printer will let you have a permanent record of the
console output on paper.

See
 Documentation/serial-console.txt
 Documentation/networking/netconsole.txt
 the help entry for "config LP_CONSOLE" (in drivers/char/Kconfig)

Would any of those perhaps help you in capturing anything ?

-- 
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:[~2005-09-05 20:48 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-04  0:15 nfs4 client bug Bret Towe
2005-09-04  3:05 ` Bret Towe
2005-09-04 10:35   ` Francois Romieu
2005-09-04 19:44     ` Bret Towe
2005-09-04 20:51       ` Bret Towe
2005-09-04 21:52         ` J. Bruce Fields
2005-09-05  3:08           ` Bret Towe
2005-09-05  3:18             ` J. Bruce Fields
2005-09-05 20:44               ` Bret Towe
2005-09-05 20:48                 ` Jesper Juhl [this message]
2005-09-06  3:40                   ` Bret Towe
2005-09-06 18:13                     ` J. Bruce Fields
2005-09-06 18:21                       ` Randy.Dunlap
2005-09-06 18:30                         ` J. Bruce Fields
2005-09-06 18:40                           ` Randy.Dunlap
2005-09-06 18:53                           ` Valdis.Kletnieks
2005-09-09  4:56                           ` [PATCH] Doc: update oops-tracing.txt (Tainted flags) Randy.Dunlap
2005-09-09  6:55                       ` nfs4 client bug Bret Towe
2005-09-12 18:27                         ` Bret Towe
2005-09-12 18:29                           ` J. Bruce Fields
  -- strict thread matches above, loose matches on Subject: below --
2005-09-05 16:24 Andreas Sundstrom
2005-09-06  5:10 Andreas Sundstrom

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=9a87484905090513481118e67b@mail.gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=bfields@fieldses.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=magnade@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.