From: Mike Fedyk <mfedyk@matchmail.com>
To: linux-kernel@vger.kernel.org
Subject: Processes stuck in D state with autofs + smbfs
Date: Wed, 29 May 2002 10:26:16 -0700 [thread overview]
Message-ID: <20020529172616.GB1136@matchmail.com> (raw)
Hi,
I've been having a recurring problem ever since the 2.2 kernel days between
smbfs and autofs.
I'm currently running 2.4.19-pre6-vm33 on this 2x664Mhz P3 machine, but I've
also had the problem in the previous UP machine.
I'm not sure what information will be helpful in debugging this probem.
Would sysrq+t run through ksymoops be helpful?
I also have this in my kernel log:
May 26 06:33:16 fileserver kernel: Uhhuh. NMI received. Dazed and confused, but trying to continue
May 26 06:33:16 fileserver kernel: You probably have a hardware problem with your RAM chips
I did a quick search and it looks like this might be a memory parity error.
Right now this system runs the scripts that triggers the condition, but I
can do tests on a different machine.
Is there anyone interested in this problem?
Oh, I'm running debian and the samba packages are:
ii samba 2.2.3a-6 A LanManager like file and printer server for Unix.
ii smbfs 2.2.3a-6 mount and umount commands for the smbfs (for kernels >= than
Thanks,
Mike
next reply other threads:[~2002-05-29 17:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-29 17:26 Mike Fedyk [this message]
2002-05-30 12:36 ` Processes stuck in D state with autofs + smbfs Urban Widmark
2002-05-30 19:18 ` Denis Vlasenko
2002-05-30 19:56 ` Mike Fedyk
2002-05-30 20:03 ` Mike Fedyk
2002-05-30 21:41 ` Urban Widmark
2002-05-30 23:20 ` Mike Fedyk
2002-05-30 23:25 ` Urban Widmark
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=20020529172616.GB1136@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=linux-kernel@vger.kernel.org \
/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