Messages in this thread | | | Subject | Re: AW: 2.4.20 CPU lockup - Now with OOPS message | From | GrandMasterLee <> | Date | 23 Jan 2003 19:40:33 -0600 |
| |
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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |