From: "Pete Monroe" <pizzlemonrizzle@gmail.com>
To: "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>
Cc: Netdev <netdev@vger.kernel.org>,
netfilter-devel@lists.netfilter.org,
linux-kernel@vger.kernel.org
Subject: Re: Crash report 2.6.22.5
Date: Tue, 28 Aug 2007 17:06:58 -0700 [thread overview]
Message-ID: <24c800fb0708281706n6d92d9d9w7c8defc4a884296b@mail.gmail.com> (raw)
In-Reply-To: <6bffcb0e0708281651g29729d6au6b40c0f9af5beed2@mail.gmail.com>
On 8/28/07, Michal Piotrowski <michal.k.k.piotrowski@gmail.com> wrote:
> Hi Pete,
>
> On 28/08/07, Pete Monroe <pizzlemonrizzle@gmail.com> wrote:
> > 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),
>
> Could you capture the bug with serial/netconsole etc.?
The servers are remote, production servers and it's a PITA when they
crash. But I'll see what I can do. Thanks for the pointer.
--
Pete
>
> "Collecting kernel messages"
> http://www.stardust.webpages.pl/files/handbook/handbook-en-0.3-rc1.pdf
> for more info.
prev parent reply other threads:[~2007-08-29 0:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <24c800fb0708281140r2c46e364i77e041b6c746b60d@mail.gmail.com>
2007-08-28 23:51 ` Crash report 2.6.22.5 Michal Piotrowski
2007-08-29 0:06 ` Pete Monroe [this message]
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=24c800fb0708281706n6d92d9d9w7c8defc4a884296b@mail.gmail.com \
--to=pizzlemonrizzle@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@lists.netfilter.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;
as well as URLs for NNTP newsgroup(s).