On Thu, Oct 17, 2002 at 01:22:46AM -0400, Doug Ledford wrote:
> Sure, coming under separate cover.
Actually, this isn't needed now I assume ;-)
> > err. ramdisk? initrd? If so, does this fix?
>
> initrd. Will try booting without initrd and see if memcounts go back to
> normal. On the current setup, when the thing locks up, Shift-ScrollLock
> dumps the meminfo. Of interest here is the line right after the
> Zone:HighMem line which reads:
>
> ( Active:1634 inactive:1603 dirty:4294966795 writeback:0 free:59222 )
>
> Booting without initrd solves the lockup issue. It also clears up the
> dirty count. So, initrd is what's corrupting things. I'll try the patch
> and let you know if it solves the initrd corruption here in a sec.
Patch solves the problem. Writes don't hang and Shift-ScrollLock shows a
reasonable number for dirty now.
--
Doug Ledford <dledford@redhat.com> 919-754-3700 x44233
Red Hat, Inc.
1801 Varsity Dr.
Raleigh, NC 27606
-
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/
This archive was generated by hypermail 2b29 : Wed Oct 23 2002 - 22:00:32 EST