From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Matt Mackall <mpm@selenic.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org
Subject: Re: Using netconsole for debugging suspend/resume
Date: Fri, 9 Jun 2006 12:34:50 +0200 [thread overview]
Message-ID: <200606091234.50874.rjw@sisk.pl> (raw)
In-Reply-To: <4488D565.2020103@goop.org>
On Friday 09 June 2006 03:56, Jeremy Fitzhardinge wrote:
> Rafael J. Wysocki wrote:
> > Please try doing "echo 8 > /proc/sys/kernel/printk" before suspend.
> >
> Um, why? That would increase the amount of log output, but I don't see
> how it would help with netconsole preventing suspend, or not being able
> to see console messages on a blank screen after resume.
Ah, that's after resume. Sorry for the noise. :-)
Rafael
next prev parent reply other threads:[~2006-06-09 10:34 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-08 17:50 Using netconsole for debugging suspend/resume Jeremy Fitzhardinge
2006-06-08 20:35 ` Auke Kok
2006-06-08 20:40 ` Rafael J. Wysocki
2006-06-09 1:56 ` Jeremy Fitzhardinge
2006-06-09 10:34 ` Rafael J. Wysocki [this message]
2006-06-08 21:07 ` Matt Mackall
2006-06-09 1:54 ` Jeremy Fitzhardinge
2006-06-09 5:13 ` Auke Kok
2006-06-09 5:23 ` David Miller
2006-06-09 5:50 ` Andi Kleen
2006-06-09 17:14 ` Matt Mackall
2006-06-09 5:45 ` Jeremy Fitzhardinge
2006-06-09 2:15 ` [PATCH RFC] netpoll: don't spin forever sending to stopped queues Jeremy Fitzhardinge
2006-06-11 20:04 ` Matt Mackall
2006-06-12 20:57 ` Jeremy Fitzhardinge
2006-06-12 20:53 ` Matt Mackall
2006-06-12 21:20 ` Jeremy Fitzhardinge
2006-06-09 3:46 ` Using netconsole for debugging suspend/resume Andi Kleen
2006-06-09 15:24 ` Mark Lord
2006-06-12 11:21 ` Andi Kleen
2006-06-12 15:38 ` Mark Lord
2006-06-12 15:46 ` Andi Kleen
2006-06-12 21:25 ` Jeremy Fitzhardinge
2006-06-13 3:47 ` Andi Kleen
2006-06-13 4:49 ` David Miller
2006-06-13 4:54 ` Andi Kleen
2006-06-13 5:03 ` David Miller
2006-06-13 7:18 ` Christoph Hellwig
2006-06-13 7:31 ` David Miller
2006-06-09 8:34 ` Pavel Machek
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=200606091234.50874.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).