On Thu, Mar 13, 2003 at 07:55:27PM -0800, Gregory K. Ruiz-Ade wrote:
> I got an opportunity, so the contents of cpuinfo, slabinfo, and meminfo are
> at: http://castandcrew.com/~gregory/lkmlstuff/burpr/2.4.20
> Hopefully they're useful.
> Additionally, I managed to generate an Oops (processed with ksymoops, too)
> while trying to create an LVM snapshot. The oops and it's
> ksymoops-translated file are up there too. The oops traces back into the
> VM somewhere.
Hmm, neither slabinfo nor meminfo show the machine being under any stress.
Were they generated while the problem was happening?
The useful information would be to collect meminfo and slabinfo while
kswapd and updated are spinning. Also, cpuinfo doesn't ever change,
(at least while being run on the same box) so you can leave that out.
BTW, oopses tracing back into the VM doesn't help. It's usually someone
doing something wrong the VM checks for. In this case I'll bet someone
(i.e. LVM) called vmalloc() with interrupts off.
-- wli
-
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 : Sat Mar 15 2003 - 22:00:38 EST