From: "Alexander Y. Fomichev" <gluk@php4.ru>
To: Andrea Arcangeli <andrea@suse.de>
Cc: admin@list.net.ru, linux-kernel@vger.kernel.org
Subject: Similar behaviour without BUG() message(was: Re: 2.6.5-aa3: kernel BUG at mm/objrmap.c:137!)
Date: Mon, 19 Apr 2004 16:32:53 +0400 [thread overview]
Message-ID: <200404191632.53565.gluk@php4.ru> (raw)
In-Reply-To: <20040414114731.GJ2150@dualathlon.random>
On Wednesday 14 April 2004 15:47, Andrea Arcangeli wrote:
> ok so there are good chances that 2.6.5-aa5 will fix it, if not then
> please notify me again, thanks.
I've noticed a behaviour today very similar to mentioned in previous report
(on 14 Apr 2004) except for message from BUG() (kernel 2.6.5-aa5) i.e.
system remained accessible but procps(ps,pkill) appears to be locked and
Sysrq-T is similar to previous one - some of apache2 & all of procps
have been blocked.
Here is a traces:
http://sysadminday.org.ru/2.6.5-ps-lockup/sysrq-M
http://sysadminday.org.ru/2.6.5-ps-lockup/full_trace
--
Best regards.
Alexander Y. Fomichev <gluk@php4.ru>
Public PGP key: http://sysadminday.org.ru/gluk.asc
next prev parent reply other threads:[~2004-04-19 12:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-14 8:57 2.6.5-aa3: kernel BUG at mm/objrmap.c:137! Alexander Y. Fomichev
2004-04-14 9:54 ` Andrea Arcangeli
2004-04-14 11:39 ` Alexander Y. Fomichev
2004-04-14 11:47 ` Andrea Arcangeli
2004-04-19 12:32 ` Alexander Y. Fomichev [this message]
2004-04-23 2:27 ` Similar behaviour without BUG() message(was: Re: 2.6.5-aa3: kernel BUG at mm/objrmap.c:137!) Andrea Arcangeli
2004-04-23 9:24 ` Alexander Y. Fomichev
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=200404191632.53565.gluk@php4.ru \
--to=gluk@php4.ru \
--cc=admin@list.net.ru \
--cc=andrea@suse.de \
--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 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.