[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <24c800fb0708281140r2c46e364i77e041b6c746b60d@mail.gmail.com>
Date: Tue, 28 Aug 2007 11:40:14 -0700
From: "Pete Monroe" <pizzlemonrizzle@...il.com>
To: linux-kernel@...r.kernel.org
Subject: Crash report 2.6.22.5
Hi,
Sorry there's not more to go on here.
A 32-bit firewall running the kernel LVS virtual server to fan out to
a dozen webservers ran fine for a year using 2.6.17.13, but won't
last more than four hours or so with 2.6.22.5. Another server,
different hardware and vendor but same purpose, also crashed with
2.6.22.5 after a few hours. It had previously run 2.6.20.11. Nothing
on the screen, nothing in the logs.
I'm attaching zipped dmesg (both kernel versions), .config and lspci
-v output for one of the machines, a Dell Intel dual-Xeon box. The
other machine is a dual Athlon box. Both use SCSI drives (the
attached Dell uses MPT Fusion, the other one Adaptec.) Intel ethernet
on both.
I did enable the Slub allocator in 2.6.22.5, figuring that if it is
going to be the default in 2.6.23 that it's probably solid in .22.5.
PLMK if any more info would be useful.
Thanks,
Pete
Download attachment "c2-lspci.out.gz" of type "application/x-gzip" (1371 bytes)
Download attachment "c2-2.6.22.5.dmesg.out.gz" of type "application/x-gzip" (5543 bytes)
Download attachment "c2-2.6.22.5.config.gz" of type "application/x-gzip" (7279 bytes)
Download attachment "c2-2.6.17.13.dmesg.out.gz" of type "application/x-gzip" (5739 bytes)
Powered by blists - more mailing lists