troy@holstein.com wrote...
> kernel BUG at vmscan.c:102!
I hit the same bug() an hour ago.
It was preceeded by a complete system lock up (not even sysrq worked)
and then fsck oopsed after triggering the above bug.
The lockup happened whilst I was diffing two kernel trees.
Seems large amounts of disk IO trigger this bug() easily.
regards,
d.
-- | Dave Jones <davej@suse.de> http://www.suse.de/~davej | SuSE Labs- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Oct 23 2000 - 21:00:17 EST