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
Attachment:
c2-lspci.out.gz
Description: GNU Zip compressed data
Attachment:
c2-2.6.22.5.dmesg.out.gz
Description: GNU Zip compressed data
Attachment:
c2-2.6.22.5.config.gz
Description: GNU Zip compressed data
Attachment:
c2-2.6.17.13.dmesg.out.gz
Description: GNU Zip compressed data
- Follow-Ups:
- Re: Crash report 2.6.22.5
- From: "Michal Piotrowski" <[email protected]>
- Re: Crash report 2.6.22.5
- Prev by Date: Re: nmi_watchdog=2 regression in 2.6.21
- Next by Date: Re: [PATCH 1/2] sysctl: Properly register the irda binary sysctl numbers.
- Previous by thread: NFSv4 client OOPS on 2.6.22-rc3
- Next by thread: Re: Crash report 2.6.22.5
- Index(es):
 |