linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Frank <mflt1@micrologica.com.hk>
To: swsusp@lister.fornax.hu, CaT <cat@zip.com.au>,
	Pavel Machek <pavel@suse.cz>
Cc: linux-kernel@vger.kernel.org, swsusp-devel@lists.sourceforge.net
Subject: Re: [Swsusp] Re: [FIX, please test] Re: 2.5.70-bk16 - nfs interferes with s4bios suspend
Date: Mon, 16 Jun 2003 09:41:46 +0800	[thread overview]
Message-ID: <200306160941.46575.mflt1@micrologica.com.hk> (raw)
In-Reply-To: <20030616001141.GA364@zip.com.au>

On Monday 16 June 2003 08:11, CaT wrote:
> On Sun, Jun 15, 2003 at 08:31:11PM +0200, Pavel Machek wrote:
> > >  stopping tasks failed (2 tasks remaining)
> > > Suspend failed: Not all processes stopped!
> > > Restarting tasks...<6> Strange, rpciod not stopped
> >
> > This should fix it... Someone please test it.
>
> I didn't have any actual nfs mounts at the time but I tried it
> with an otherwise similar system. It went through, got to freeing
> memory, showed me a bunch of fullstops being drawn and then went
> into an endless BUG loop. All I could pick out (after many a moment
> of staring) was 'schedule in atmoic'.
>
> I'll do a proper test with a console cable present in a few days. I
> can't atm cos I'm not on the same network and don't have a 2nd
> computer to hook up the null-modem cable to.
>
> Pre-empt is on btw.

I tested swsusp ex 2.5 BK tree - it is is broken. 

Looks something like: Writing data to swap (2273 pages): .<3>bad: scheduling while atomic!
and call traces.

Have a look at the thread on LKML around June 4: 
IDE Power Management (Was: software suspend in 2.5.70-mm3)

I'll wait for Nigel's 2.5 port

Regards
Michael
-- 
Powered by linux-2.5.70-mm3, compiled with gcc-2.95-3 because it's rock solid
                
My current linux related activities in rough order of priority:
- Testing of Swsusp for 2.4
- Learning 2.5 kernel debugging with kgdb - it's in the -mm tree
- Studying 2.5 serial and ide drivers, ACPI, S3

The 2.5 kernel could use your usage. More info on setting up 2.5 kernel at 
http://www.codemonkey.org.uk/post-halloween-2.5.txt



  reply	other threads:[~2003-06-16  3:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-13  3:37 2.5.70-bk16 - nfs interferes with s4bios suspend CaT
2003-06-13  6:30 ` Pavel Machek
2003-06-15 18:06 ` Pavel Machek
2003-06-15 23:00   ` CaT
2003-06-15 23:16     ` Pavel Machek
2003-06-15 18:31 ` [FIX, please test] " Pavel Machek
2003-06-16  0:11   ` CaT
2003-06-16  1:41     ` Michael Frank [this message]
2003-06-16 10:47     ` Pavel Machek
2003-06-18  8:16       ` CaT
2003-06-18 10:17         ` Pavel Machek
2003-06-18 10:26           ` CaT
2003-06-18 10:35             ` Pavel Machek
2003-06-21 14:24               ` can't get linux to perform a bios suspend (was: Re: [FIX, please test] Re: 2.5.70-bk16 - nfs interferes with s4bios suspend) CaT
2003-06-22 15:15                 ` Pavel Machek
2003-06-23  0:58                   ` CaT
2003-06-23  9:50                     ` Pavel Machek
2003-06-23  9:58                       ` CaT
2003-07-01  8:03                       ` CaT

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=200306160941.46575.mflt1@micrologica.com.hk \
    --to=mflt1@micrologica.com.hk \
    --cc=cat@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=swsusp-devel@lists.sourceforge.net \
    --cc=swsusp@lister.fornax.hu \
    /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).