From: Auke Kok <auke-jan.h.kok@intel.com>
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: Thu, 08 Jun 2006 13:35:28 -0700 [thread overview]
Message-ID: <44888A10.4010207@intel.com> (raw)
In-Reply-To: <44886381.9050506@goop.org>
Jeremy Fitzhardinge wrote:
> I've been trying to get suspend/resume working well on my new laptop.
> In general, netconsole has been pretty useful for extracting oopses and
> other messages, but it is of more limited help in debugging the actual
> suspend/resume cycle. The problem looks like the e1000 driver won't
> suspend while netconsole is using it, so I have to rmmod/modprobe
> netconsole around the actual suspend/resume.
>
> This is a big problem during resume because the screen is also blank, so
> I get no useful clue as to what went wrong when things go wrong. I'm
> wondering if there's some way to keep netconsole alive to the last
> possible moment during suspend, and re-woken as soon as possible during
> resume. It would be nice to have a clean solution, but I'm willing to
> use a bletcherous hack if that's what it takes.
>
> Any ideas?
Have you tried using different cards/drivers? This might or might not be
either a netconsole problem (generic) or driver related (which could impact
other drivers too).
From the top of my head I don't see any reason why the e1000 shouldn't handle
the suspend event - but mind you that a fix for e1000/WoL impacting shutdown
handlers was only recently added. Which kernels does this impact?
Auke
next prev parent reply other threads:[~2006-06-08 20:35 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 [this message]
2006-06-08 20:40 ` Rafael J. Wysocki
2006-06-09 1:56 ` Jeremy Fitzhardinge
2006-06-09 10:34 ` Rafael J. Wysocki
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=44888A10.4010207@intel.com \
--to=auke-jan.h.kok@intel.com \
--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).