linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: CaT <cat@zip.com.au>
To: Pavel Machek <pavel@suse.cz>
Cc: swsusp@lister.fornax.hu, linux-kernel@vger.kernel.org
Subject: Re: [FIX, please test] Re: 2.5.70-bk16 - nfs interferes with s4bios suspend
Date: Wed, 18 Jun 2003 20:26:02 +1000	[thread overview]
Message-ID: <20030618102602.GA593@zip.com.au> (raw)
In-Reply-To: <20030618101728.GA203@elf.ucw.cz>

On Wed, Jun 18, 2003 at 12:17:28PM +0200, Pavel Machek wrote:
> > > Turn it off. You don't want to debug preempt and nfs at the same time.
> > 
> > And this is with preempt off:
> > 
> > Stopping tasks: XFree86 entered refrigerator
> > =pdflush entered refrigerator
> ...
> > =init entered refrigerator
> > =procmail entered refrigerator
> > =|
> > Freeing memory: .........................|
> > Syncing disks before copy
> > Suspending devices
> > Suspending device c052c48c
> > Suspending devices
> > Suspending device c052c48c
> > suspending: hda ------------[ cut here ]------------
> > kernel BUG at drivers/ide/ide-disk.c:1110!
> 
> Okay, you hit some ide problems, but freezing NFS worked okay. Did you
> have active NFS mounts at this point?

Yup. I upgraded to .72 and tried again (using the new taskfile stuff) and
this time it suspended. On resume though, the framebuffer console wasn't
really functioning. I had to switch to X and then switch back again before
it was all groovy.

Ponderance: Why did it do a full s/w suspend when I asked for the bios
to handle it? I have s4bios showing up in /proc/acpi/sleep and the bios
is set to suspend to disk. I've even got an a0 partition fully formatted
and it still ignored it all.

I was using the following line to activate it:

echo 4b >/proc/acpi/sleep

-- 
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

  reply	other threads:[~2003-06-18 10:11 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     ` [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 [this message]
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=20030618102602.GA593@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;
as well as URLs for NNTP newsgroup(s).