From: GrandMasterLee <masterlee@digitalroadkill.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Two on the kernel. - Please Respond.
Date: 17 Jan 2003 16:32:49 -0600 [thread overview]
Message-ID: <1042842769.1291.20.camel@UberGeek> (raw)
In-Reply-To: <1042836639.1292.16.camel@UberGeek>
If you have any information to share, questions, etc, I'd appreciate
anything which may help shed light on what I'm seeing here. I'm planning
on testing a custom patch set internally so I know it will fix the
problems below, but I need feed back to make sure I'm headed in the
right direction. TIA
On Fri, 2003-01-17 at 14:50, GrandMasterLee wrote:
> Hey all,
> I've got two issues here. Both issues were seen with 2.4.19aa1. The
> second issue was seen with 2.4.20aa1 also.
>
>
> 1. This message between two linux machines during backup (rsync), across
> GBE:
>
> "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.
> XFS mounting file"
>
> I saw some info on LKML archives about this, but no resolution or
> reason. The system reporting the errors has an EEPRO1000 and is
> connected via crossover to a system with embedded BCM5700s. MTU is 9000
>
> 2. tar xjvf breaks the machine: Usually black-screens.
>
> When untarring say, bzipped kernel source, though other tars have caused
> this too, the system will get very slow, the untarring will stop, and
> then about 2 - 5 mins later, everything stops. Sometimes this causes a
> black screen, other times, it's just frozen with whatever's on the
> screen. The system must be hard booted for it to recover, usually
> needing to hold the power button down till forced power off too.(5
> seconds)
>
> I thought this might be memory related, so I umounted /dev/shm after a
> reboot, and tried my untar test again. Usually I could untar 2 times
> before the system entered the aforementioned state. I then tried
> 2.4.20aa1, and got the same result. I then tried just 2.4.20 + XFS
> patches, and now my system is actually faster at most things than it was
> prior. I'm not sure why.
>
> The system mentioned in #2 is an AMD Athlon-C with 512MB RAM two HDDs a
> CDRW and a DVD-ROM drive. It is 100% XFS and LVM is used for 5 volumes,
> but not / .
>
> Any help with this would be greatly appreciated.
>
--
GrandMasterLee <masterlee@digitalroadkill.net>
prev parent reply other threads:[~2003-01-17 22:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-17 20:50 Two on the kernel GrandMasterLee
2003-01-17 22:32 ` GrandMasterLee [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=1042842769.1291.20.camel@UberGeek \
--to=masterlee@digitalroadkill.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.