From: Michael Reinelt <reinelt@eunet.at>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: strange hangs with kernel 2.4.12 (and 13)
Date: Sun, 28 Oct 2001 18:32:30 +0100 [thread overview]
Message-ID: <3BDC412E.88A77A4A@eunet.at> (raw)
In-Reply-To: <3BDA8A5E.503EDD28@eunet.at> <slrn9tlq11.crb.j.kloos@gandalf.yadha.dnsalias.net>
Johannes Kloos wrote:
>
> Michael Reinelt <reinelt@eunet.at> wrote:
> > I've got seveal processes hanging in "D" state, especially devfsd. I
> > think something with devfs and/or devfsd is broken here. If I kill
> > devfsd before, the problem does not arise (but I need devfsd :-)
> I've had this problem as well - it seems there's a deadlock in devfs.
> I have sent a mail to Richard Gooch about this some days ago, but he
> hasn't responded yet.
> I will resend my bug report to the list then.
Mybe you could CC me the reports? I'm not a regular reader of lkml.
Thanks...
> > Now, It gets even more strange: The problem does only exist if I
> > deactivate ACPI! I tried with a ACPI enabled kernel with the command
> > line "acpi=off", I tried on a machine which is too old for ACPI, and I
> > even compiled a kernel without ACPI at all. Everywhere the same problem.
> > When I boot with activated ACPI, there's no problem.
> I don't know about this.
Well, I've just had the same problem with ACPI. So forget about the last
paragraph.
But I found another strange thing: If I deactivate nscd, the problem
does not occur when logging in and out.
bye, Michael
--
netWorks Vox: +43 316 698260
Michael Reinelt Fax: +43 316 692343
Geisslergasse 4 GSM: +43 676 3079941
A-8045 Graz, Austria e-mail: reinelt@eunet.at
prev parent reply other threads:[~2001-10-28 17:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-27 10:20 Michael Reinelt
2001-10-27 17:00 ` Johannes Kloos
2001-10-28 17:32 ` Michael Reinelt [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=3BDC412E.88A77A4A@eunet.at \
--to=reinelt@eunet.at \
--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
all inboxes | Powered by JetHome®