From: Nigel Cunningham <ncunningham@users.sourceforge.net>
To: "Udo A. Steinberg" <us15@os.inf.tu-dresden.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [OOPS] Linux-2.6.1 suspend/resume
Date: Mon, 26 Jan 2004 14:48:21 +1300 [thread overview]
Message-ID: <1075081701.10885.18.camel@laptop-linux> (raw)
In-Reply-To: <20040126022540.315c4f8c@argon.inf.tu-dresden.de>
[-- Attachment #1: Type: text/plain, Size: 289 bytes --]
Hi.
Those don't look like oopses. Rather, they're call traces resulting from
scheduling while atomic. You should have a working system at the
conclusion of what you're recorded.
Regards,
Nigel
--
My work on Software Suspend is graciously brought to you by
LinuxFund.org.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-01-26 1:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-26 1:25 [OOPS] Linux-2.6.1 suspend/resume Udo A. Steinberg
2004-01-26 1:48 ` Nigel Cunningham [this message]
2004-01-26 4:16 ` Hugang
2004-01-26 8:35 ` Udo A. Steinberg
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=1075081701.10885.18.camel@laptop-linux \
--to=ncunningham@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=us15@os.inf.tu-dresden.de \
/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.