From: Pavel Machek <pavel@ucw.cz>
To: Nigel Cunningham <ncunningham@linuxmail.org>
Cc: swsusp-devel@lists.sourceforge.net,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [Swsusp-devel] suspend2 problems on SMP machine, incorrect tainting
Date: Sat, 29 May 2004 13:34:10 +0200 [thread overview]
Message-ID: <20040529113410.GA25121@elf.ucw.cz> (raw)
In-Reply-To: <40B83F15.9070701@linuxmail.org>
Hi!
> I should mention that the code is not perfectly stable at the moment. As
> soon as it is I'll get stuck into last cleanups and then the merge. Crashes
> I'm seeing involve an oops shortly after resuming, occuring in slab
> code.
The oops I saw with "nosmp noapic" was after resuming... it might be
related.
Pavel
--
934a471f20d6580d5aad759bf0d97ddc
prev parent reply other threads:[~2004-05-29 11:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-28 10:35 suspend2 problems on SMP machine, incorrect tainting Pavel Machek
2004-05-29 7:34 ` Nigel Cunningham
2004-05-29 8:47 ` [Swsusp-devel] " Nigel Cunningham
2004-05-29 7:43 ` [Swsusp-devel] " Nigel Cunningham
2004-05-29 11:34 ` Pavel Machek [this message]
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=20040529113410.GA25121@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@linuxmail.org \
--cc=swsusp-devel@lists.sourceforge.net \
/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