From: Olaf Hering <olh@suse.de>
To: "H. Peter Anvin" <hpa@transmeta.com>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
autofs@linux.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: race in autofs / nfs
Date: Tue, 13 Feb 2001 16:58:31 +0100 [thread overview]
Message-ID: <20010213165831.A1289@suse.de> (raw)
In-Reply-To: <20010211211701.A7592@suse.de> <3A86F6AA.1416F479@transmeta.com> <shsbss8i8iq.fsf@charged.uio.no> <20010212111448.A28932@suse.de> <20010212125115.B30552@suse.de> <3A881FA7.2C5C8CBE@transmeta.com> <20010212184816.C3778@suse.de>
In-Reply-To: <20010212184816.C3778@suse.de>; from olh@suse.de on Mon, Feb 12, 2001 at 06:48:16PM +0100
On Mon, Feb 12, Olaf Hering wrote:
> On Mon, Feb 12, H. Peter Anvin wrote:
>
> > Olaf Hering wrote:
> > >
> > > The autofs4.o is the culprit, it works perfect with autofs.o.
> > >
> > > What would happen if I stick with autofs.o now?
> > > The docu recommends autofs4 in modules.conf.
> > >
> >
> > I don't know who came up with that idea. You should use the module that
> > matches your daemon, and not try to hack around so that there is a
> > module/daemon mismatch.
>
> cantaloupe:~ # /usr/sbin/automount -v
> Linux automount version 4.0.0
>
>
> We had 4.0pre7 in 7.0 and 4.0pre9 in 7.1.
> I would really like to know _where_ it hangs, Trond sent me a printk
> patch but this one was not called.
Any ideas where to start with the debugging?
> I will try to get a i386 SMP machine to see if its ppc specific.
I'm unable to reproduce it on a Piii 750 with SuSE 7.1.
guillory:/usr/src/OLAF/linux-2.4.2-pre3 # sh scripts/ver_linux
-- Versions installed: (if some fields are empty or look
-- unusual then possibly you have very old versions)
Linux guillory 2.4.2-pre3-SMP #3 SMP Tue Feb 13 14:50:47 CET 2001 i686
unknown
Kernel modules 2.4.1
Gnu C 2.95.2
Gnu Make 3.79.1
Binutils 2.10.0.33
Linux C Library x 1 root root 1382179 Jan 19 07:14
/lib/libc.so.6
Dynamic linker ldd (GNU libc) 2.2
Procps 2.0.7
Mount 2.10q
Net-tools 1.57
Kbd 1.02
Sh-utils 2.0
Modules Loaded nfsd ipv6 mousedev hid input usbcore eepro100
both 2.4.1ac10 and 2.4.2-pre3 boot fine.
This machine oops in the usb stack, but thats another issue.
Gruss Olaf
--
$ man clone
BUGS
Main feature not yet implemented...
prev parent reply other threads:[~2001-02-13 15:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-11 20:17 race in autofs / nfs Olaf Hering
2001-02-11 20:31 ` H. Peter Anvin
2001-02-12 8:57 ` Trond Myklebust
2001-02-12 9:35 ` Olaf Hering
2001-02-12 10:14 ` Olaf Hering
2001-02-12 11:51 ` Olaf Hering
2001-02-12 17:38 ` H. Peter Anvin
2001-02-12 17:48 ` Olaf Hering
2001-02-13 15:58 ` Olaf Hering [this message]
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=20010213165831.A1289@suse.de \
--to=olh@suse.de \
--cc=autofs@linux.kernel.org \
--cc=hpa@transmeta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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