All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Horms <horms@verge.net.au>,
	Kexec Mailing List <kexec@lists.infradead.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Vivek Goyal <vgoyal@redhat.com>
Subject: Re: why kexec insists on syncing with recent kernels?
Date: Fri, 08 Feb 2008 18:19:48 +0100	[thread overview]
Message-ID: <47AC8F34.3020705@wpkg.org> (raw)
In-Reply-To: <20080208090407.4ab240f1.randy.dunlap@oracle.com>

Randy Dunlap schrieb:

(...)

>> Even if you did -f, it must have shutdown the network. I think somehow
>> in latest kernels there is some dependency on network and that's why
>> not shutting down network in this case is helping you.
> 
> I'm seeing NFS mounts take forever to unmount (at shutdown/reboot).
> (forever => 1 hour ... or never completes)
> 
> Is this similar to the problem that the OP is asking about?

Is it a diskless station?

Even in not, just make sure you don't shut the network down before NFS 
is actually unmounted...?


-- 
Tomasz Chmielewski
http://wpkg.org

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

WARNING: multiple messages have this Message-ID (diff)
From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Vivek Goyal <vgoyal@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Kexec Mailing List <kexec@lists.infradead.org>,
	Horms <horms@verge.net.au>
Subject: Re: why kexec insists on syncing with recent kernels?
Date: Fri, 08 Feb 2008 18:19:48 +0100	[thread overview]
Message-ID: <47AC8F34.3020705@wpkg.org> (raw)
In-Reply-To: <20080208090407.4ab240f1.randy.dunlap@oracle.com>

Randy Dunlap schrieb:

(...)

>> Even if you did -f, it must have shutdown the network. I think somehow
>> in latest kernels there is some dependency on network and that's why
>> not shutting down network in this case is helping you.
> 
> I'm seeing NFS mounts take forever to unmount (at shutdown/reboot).
> (forever => 1 hour ... or never completes)
> 
> Is this similar to the problem that the OP is asking about?

Is it a diskless station?

Even in not, just make sure you don't shut the network down before NFS 
is actually unmounted...?


-- 
Tomasz Chmielewski
http://wpkg.org

  reply	other threads:[~2008-02-08 17:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-07 14:13 why kexec insists on syncing with recent kernels? Tomasz Chmielewski
2008-02-07 16:37 ` Vivek Goyal
2008-02-07 16:37   ` Vivek Goyal
2008-02-07 16:59   ` Tomasz Chmielewski
2008-02-07 16:59     ` Tomasz Chmielewski
2008-02-08 16:04     ` Vivek Goyal
2008-02-08 16:04       ` Vivek Goyal
2008-02-08 17:04       ` Randy Dunlap
2008-02-08 17:04         ` Randy Dunlap
2008-02-08 17:19         ` Tomasz Chmielewski [this message]
2008-02-08 17:19           ` Tomasz Chmielewski
2008-02-08 17:26           ` Vivek Goyal
2008-02-08 17:26             ` Vivek Goyal
2008-02-11 12:36           ` Geert Uytterhoeven
2008-02-11 12:36             ` Geert Uytterhoeven
2008-02-08  8:53 ` Geert Uytterhoeven

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=47AC8F34.3020705@wpkg.org \
    --to=mangoo@wpkg.org \
    --cc=horms@verge.net.au \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=vgoyal@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.