From: GrandMasterLee <masterlee@digitalroadkill.net>
To: dk@webcluster.at
Cc: linux-kernel@vger.kernel.org
Subject: Re: AW: 2.4.20 CPU lockup - Now with OOPS message
Date: 23 Jan 2003 19:40:33 -0600 [thread overview]
Message-ID: <1043372432.12857.3.camel@localhost> (raw)
In-Reply-To: <DIEGIJEABDDLMLKJFCKJCEFLCEAA.dk@webcluster.at>
On Thu, 2003-01-23 at 18:11, Daniel Khan wrote:
> Hi,
>
> > > I reported frequently system lockups today.
> > > Now after some playing around (cause I don't know anything about kernel
> > > debugging - Thanks to Mark Hahn for the tipps)
> > > I found a way to reproduce the lock and to get the OOPS.
> [..]
>
> > Can I ask how you reproduced this? I've got several systems with TG3's
> > and they only get lockups during network backups.
>
> httpd session on the host which has big logfiles to get them changed.
> Starting rsync to sync the logfiles and other stuff to the backup host.
>
> Sometimes I have to retry 2-3 times but it crashes very reliable.
> It's quite the same as the network backups you mentioning.
We use rsync to do our backups. I've been getting lines in my backup
server kernel and dmesg like this:
TCP: Treason uncloaked! Peer 10.1.1.40:37859/873 shrinks window
2430745930:2430747378. Repaired.
TCP: Treason uncloaked! Peer 10.1.1.40:37859/873 shrinks window
2430745930:2430747378. Repaired.
I was able to successfully reproduce this error in a test setup, but not
the crashes. I'm curious if maybe I just start up too many instances of
rsync and see what happens.
Any particular method or size of files, etc, in reproducing this would
be greatly beneficial. TIA
> Daniel Khan
next prev parent reply other threads:[~2003-01-24 1:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-23 23:30 2.4.20 CPU lockup - Now with OOPS message Daniel Khan
2003-01-24 0:05 ` GrandMasterLee
2003-01-24 0:11 ` AW: " Daniel Khan
2003-01-24 1:40 ` GrandMasterLee [this message]
2003-01-24 2:33 ` AW: " Daniel Khan
2003-01-24 6:10 ` GrandMasterLee
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=1043372432.12857.3.camel@localhost \
--to=masterlee@digitalroadkill.net \
--cc=dk@webcluster.at \
--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