public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: CaT <cat@zip.com.au>
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 12:17:28 +0200	[thread overview]
Message-ID: <20030618101728.GA203@elf.ucw.cz> (raw)
In-Reply-To: <20030618081600.GA484@zip.com.au>

Hi!

> > > 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.
> 
> Was able to capture the output for this case (it's long). The result
> without preempt is below this one.

> I hit the power button here and shut the box down.
> 
> > 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?
								Pavel
-- 
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]

  reply	other threads:[~2003-06-18 10:03 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 [this message]
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=20030618101728.GA203@elf.ucw.cz \
    --to=pavel@suse.cz \
    --cc=cat@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --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