tags 548630 + moreinfo quit Hi,
Hans IJ wrote: > I cannot use the hardware to reproduce. It is currently my LAMP server, and > used 24/7. Sorry. I was able to fix at that time the bug by putting the two > DDR modules in 32 bit configuration, and not in 64 bit. > > I hope this helps a bit... No problem. If there won't be time in the next month or so I guess we should close the bug and reopen when someone else experiences it or it happens again. If you or anyone else experiencing this ends up in a position to reproduce it, in addition to trying a recent kernel it would be interesting to try the debugging patch from [1] (the surrounding thread is about a different bug that was introduced in a newer kernel, but the patch makes the kernel print the right information). Also, it's possible (though unlikely) that a description of the problem (plus hardware information they ask about in follow-up) could be enough to ring a bell for the Linux memory management subsystem maintainers; feel free to ask them at linux...@kvack.org (no subscription required and the convention is always to reply-to-all there), cc-ing this bug. Sorry I have no better insights. Jonathan [1] http://thread.gmane.org/gmane.linux.kernel.mm/66536 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110912211551.gb2...@elie.gateway.2wire.net
