From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Sylvain Pasche <sylvain_pasche@yahoo.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.41 Autofs4: bad: scheduling while atomic!
Date: 11 Oct 2002 17:13:51 -0700 [thread overview]
Message-ID: <1034381631.1319.2.camel@sherkaner.pao.digeo.com> (raw)
In-Reply-To: <15783.5936.803024.183802@yahoo.fr>
On Fri, 2002-10-11 at 11:23, Sylvain Pasche wrote:
Unfortunately, I did not keep the .config.
From what I remember, I had CONFIG_PREEMPT set and CONFIG_SMP not set.
I'm not under 2.5 now, but I can recompile and test again if you want
to be able to reproduce it and have more details..
I really can't see how it could get into a non-preemptable state along
that path. Did anything else bad happen in that session? Any oopses or
other funnies? Can you give more detail about what you were doing at
the time? Was it the first use of autofs, or had you been using it
heavily? How many autofs filesystems mounted?
Thanks,
J
prev parent reply other threads:[~2002-10-12 0:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-10 17:09 Sylvain Pasche
[not found] ` <1034322155.1568.14.camel@ezr>
[not found] ` <15783.5936.803024.183802@yahoo.fr>
2002-10-12 0:13 ` Jeremy Fitzhardinge [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=1034381631.1319.2.camel@sherkaner.pao.digeo.com \
--to=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sylvain_pasche@yahoo.fr \
/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®