All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Leete <tleete@mountain.net>
To: "David S. Miller" <davem@redhat.com>
Cc: Jeff Garzik <jgarzik@mandrakesoft.com>, linux-kernel@vger.kernel.org
Subject: Hard lockups solved
Date: Mon, 13 Nov 2000 18:05:24 -0500	[thread overview]
Message-ID: <3A1073B4.CDCA21DF@mountain.net> (raw)

Hi,

My lockup problems started increasing in frequency, and it
became obvious that they were independent of the kernel I
booted. The shoe dropped, nic was failing. It's salvage now.

The bizarre shift errors on ftp are gone, so the data I sent
is irrelevant to the kernel.

The soft hangs I was getting were real, though perhaps
encouraged by nic failure. Your net/ipv4/tcp.c patch from
the NE2000 thread cured them even before I found the
hardware fault. Has that patch gone to the queue? I
recommend it.

Thanks,
Tom
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

             reply	other threads:[~2000-11-13 23:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-13 23:05 Tom Leete [this message]
2000-11-14  1:14 ` Hard lockups solved David S. Miller
2000-11-15  4:09   ` Tom Leete

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=3A1073B4.CDCA21DF@mountain.net \
    --to=tleete@mountain.net \
    --cc=davem@redhat.com \
    --cc=jgarzik@mandrakesoft.com \
    --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.