From: Ian Kent <ikent@redhat.com>
To: Ondrej Valousek <webserv@s3group.cz>
Cc: "autofs@linux.kernel.org" <autofs@linux.kernel.org>
Subject: Re: Automouter crashed, I have the core
Date: Wed, 08 Dec 2010 00:24:10 +0800 [thread overview]
Message-ID: <1291739050.16875.14.camel@perseus> (raw)
In-Reply-To: <4CFE4D4C.9020008@s3group.cz>
On Tue, 2010-12-07 at 16:05 +0100, Ondrej Valousek wrote:
> On 07.12.2010 13:21, Ian Kent wrote:
> > Unfortunately not but there certainly is a mistake in this area
> > somewhere.
> >
> > I have another report of a hang with very similar symptoms but a thread
> > that should have existed in the back trace had simply disappeared. That
> > thread should have been an expire callback just like the one you have
> > here. So this is really useful to know but I haven't worked it out yet.
> Hi Ian,
>
> Ok, so how can I help now? Submit a bugzilla request/Redhat support
> case/forget about it?
My problem is working out what is going wrong.
There are two things we need to do. First, any information about what is
happening at the time this occurs might give us a clue of where to look.
Second, a debug log might tell us what is happening, especially if we
can spot the time of the problem and relate it back to the time in the
log, although turning debugging on might stop the bug from occurring.
If that happens then we need to go over what we do have and guess, then
put some selective logging in to try and nail down what is happening.
There's no question this process is difficult for us both and will
require a fair amount of effort but that's the way it goes.
Ian
next prev parent reply other threads:[~2010-12-07 16:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 10:06 Automouter crashed, I have the core Ondrej Valousek
2010-12-07 12:21 ` Ian Kent
2010-12-07 15:05 ` Ondrej Valousek
2010-12-07 16:24 ` Ian Kent [this message]
2010-12-07 16:30 ` Ondrej Valousek
-- strict thread matches above, loose matches on Subject: below --
2010-12-03 13:44 Ondrej Valousek
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=1291739050.16875.14.camel@perseus \
--to=ikent@redhat.com \
--cc=autofs@linux.kernel.org \
--cc=webserv@s3group.cz \
/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.