From: CaT <cat@zip.com.au>
To: swsusp@lister.fornax.hu
Cc: linux-kernel@vger.kernel.org, pavel@suse.cz
Subject: 2.5.70-bk16 - nfs interferes with s4bios suspend
Date: Fri, 13 Jun 2003 13:37:03 +1000 [thread overview]
Message-ID: <20030613033703.GA526@zip.com.au> (raw)
Not too sure which list to send this to exactly so here goes. I go
my laptop back from warranty repair and it was returned with an old
version of the bios that still had suspend-2-disk capability in it.
Having set everything up I hit the suspend button and all seemed to
go ok upto a point:
==mutt entered refrigerator
=mutt entered refrigerator
=mutt entered refrigerator
=mutt entered refrigerator
=mutt entered refrigerator
=mutt entered refrigerator
=mutt entered refrigerator
=tail entered refrigerator
=
stopping tasks failed (2 tasks remaining)
Suspend failed: Not all processes stopped!
Restarting tasks...<6> Strange, rpciod not stopped
Strange, lockd not stopped
XFree86 left refrigerator
init left refrigerator
khubd left refrigerator
then it kept unfreezing my tasks till the following debug stuff
came up:
tail left refrigerator
pdflush left refrigerator
done
Debug: sleeping function called from illegal context at include/linux/rwsem.h:43
Call Trace:
[<c011a2a3>] __might_sleep+0x5f/0x6c
[<c01179b6>] do_page_fault+0x76/0x40a
[<c0117940>] do_page_fault+0x0/0x40a
[<c0142d1f>] shmem_nopage+0x33/0x68
[<c01416a7>] pte_chain_alloc+0x1b/0x84
[<c01fcbc8>] __copy_from_user_ll+0x60/0x78
[<c010b0f0>] sys_vm86old+0xfc/0x10c
[<c0108fe9>] error_code+0x2d/0x38
[<c0108e3f>] syscall_call+0x7/0xb
Debug: sleeping function called from illegal context at include/linux/rwsem.h:43
Call Trace:
[<c011a2a3>] __might_sleep+0x5f/0x6c
[<c01179b6>] do_page_fault+0x76/0x40a
[<c0117940>] do_page_fault+0x0/0x40a
[<c0142d1f>] shmem_nopage+0x33/0x68
[<c01416a7>] pte_chain_alloc+0x1b/0x84
[<c01fcbc8>] __copy_from_user_ll+0x60/0x78
[<c010b0f0>] sys_vm86old+0xfc/0x10c
[<c0108fe9>] error_code+0x2d/0x38
[<c0108e3f>] syscall_call+0x7/0xb
Laptop seems to be working fine still. X and networking are going ok. The
nfs mounts still function (laptop is a client with 3 nfs mounts).
--
Martin's distress was in contrast to the bitter satisfaction of some
of his fellow marines as they surveyed the scene. "The Iraqis are sick
people and we are the chemotherapy," said Corporal Ryan Dupre. "I am
starting to hate this country. Wait till I get hold of a friggin' Iraqi.
No, I won't get hold of one. I'll just kill him."
- http://www.informationclearinghouse.info/article2479.htm
next reply other threads:[~2003-06-13 3:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-13 3:37 CaT [this message]
2003-06-13 6:30 ` 2.5.70-bk16 - nfs interferes with s4bios suspend 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 ` [Swsusp] " Michael Frank
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=20030613033703.GA526@zip.com.au \
--to=cat@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--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