Messages in this thread | | | From | "Alexander Y. Fomichev" <> | 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 |
| |
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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |