mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Pete Monroe" <pizzlemonrizzle@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Crash report 2.6.22.5
Date: Tue, 28 Aug 2007 11:40:14 -0700	[thread overview]
Message-ID: <24c800fb0708281140r2c46e364i77e041b6c746b60d@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 891 bytes --]

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 #2: c2-lspci.out.gz --]
[-- Type: application/x-gzip, Size: 1371 bytes --]

[-- Attachment #3: c2-2.6.22.5.dmesg.out.gz --]
[-- Type: application/x-gzip, Size: 5543 bytes --]

[-- Attachment #4: c2-2.6.22.5.config.gz --]
[-- Type: application/x-gzip, Size: 7279 bytes --]

[-- Attachment #5: c2-2.6.17.13.dmesg.out.gz --]
[-- Type: application/x-gzip, Size: 5739 bytes --]

             reply	other threads:[~2007-08-28 18:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-28 18:40 Pete Monroe [this message]
2007-08-28 23:51 ` Michal Piotrowski
2007-08-29  0:06   ` Pete Monroe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=24c800fb0708281140r2c46e364i77e041b6c746b60d@mail.gmail.com \
    --to=pizzlemonrizzle@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®