[lkml]   [2003]   [Jan]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: AW: 2.4.20 CPU lockup - Now with OOPS message
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 shrinks window
2430745930:2430747378. Repaired.
TCP: Treason uncloaked! Peer 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
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:32    [W:0.040 / U:2.392 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site