public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tom Leete <tleete@mountain.net>
To: "David S. Miller" <davem@redhat.com>
Cc: jgarzik@mandrakesoft.com, linux-kernel@vger.kernel.org
Subject: Re: Hard lockups solved
Date: Tue, 14 Nov 2000 23:09:18 -0500	[thread overview]
Message-ID: <3A120C6E.ADFE4C24@mountain.net> (raw)
In-Reply-To: <3A1073B4.CDCA21DF@mountain.net> <200011140114.RAA14493@pizda.ninka.net>

"David S. Miller" wrote:
> 
>    Date: Mon, 13 Nov 2000 18:05:24 -0500
>    From: Tom Leete <tleete@mountain.net>
> 
>    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.
> 
> The bugs I was "fixing" there were due to problems in wait queue
> exclusivity nesting.  We instead fixed wait queue exclusivity nesting
> so it actually worked in test11-pre3, can you see if by itself that
> kernel does not show your problems too?
> 
> Thanks.
> 
> Later,
> David S. Miller
> davem@redhat.com

Done. Yes, it's fixed in vanilla test11-pre3, to go by
limited testing. ftp, 15 Meg in 4 files -- no deathlike
sleep, md5sums agree. That load would have certainly
triggered the problem before. On to pre5.

Thanks again,
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-15  4:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-13 23:05 Hard lockups solved Tom Leete
2000-11-14  1:14 ` David S. Miller
2000-11-15  4:09   ` Tom Leete [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=3A120C6E.ADFE4C24@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox