From: Oleg Nesterov <oleg@redhat.com>
To: archer@sourceware.org, utrace-devel@redhat.com
Subject: Re: gdbstub initial code, v5
Date: Tue, 24 Aug 2010 17:10:00 -0000 [thread overview]
Message-ID: <20100824170718.GA8966@redhat.com> (raw)
In-Reply-To: <20100823185223.GA31912@redhat.com>
On 08/23, Oleg Nesterov wrote:
>
> However. I spent all Monday trying to resolve the new bug, and
> so far I do not understand what happens. Extremely hard to reproduce,
> and the kernel just hangs silently, without any message.
> So far I suspect the proble in utrace.c, but this time I am not sure.
Solved. This was scheduler bug fixed in 2.6.35, but I used 2.6.34.
This is really funny. This bug (PF_STARTING lockup) was found and
fixed by me & Peter.
Oh. But I hit yet another problem, BUG_ON() in __utrace_engine_release().
Again, it is not reproducible, I saw it only once in dmesg and I do
not even know for sure what I was doing.
I'll contiue tomorrow, but if I won't be able to quickly resolve
this problem I am going to ignore it for now. This time I think
ugdb is wrong.
Oleg.
next prev parent reply other threads:[~2010-08-24 17:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-20 17:41 Oleg Nesterov
2010-08-23 18:55 ` Oleg Nesterov
2010-08-24 17:10 ` Oleg Nesterov [this message]
2010-08-24 23:36 ` Roland McGrath
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=20100824170718.GA8966@redhat.com \
--to=oleg@redhat.com \
--cc=archer@sourceware.org \
--cc=utrace-devel@redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).