From: Doug McNaught <doug@wireboard.com>
To: Chris Evans <chris@scary.beasts.org>
Cc: Malcolm Beattie <mbeattie@sable.ox.ac.uk>,
<linux-kernel@vger.kernel.org>, <davem@redhat.com>
Subject: Re: Serious reproducible 2.4.x kernel hang
Date: 01 Feb 2001 13:41:57 -0500 [thread overview]
Message-ID: <m3bssmgs96.fsf@belphigor.mcnaught.org> (raw)
In-Reply-To: <Pine.LNX.4.30.0102011826060.397-100000@ferret.lmh.ox.ac.uk>
In-Reply-To: Chris Evans's message of "Thu, 1 Feb 2001 18:28:45 +0000 (GMT)"
Chris Evans <chris@scary.beasts.org> writes:
> [cc: davem because of the severity]
>
> On Thu, 1 Feb 2001, Malcolm Beattie wrote:
>
> > rid of the hang. So it looks as though some combination of
> > shutdown(2) and SIGABRT is at fault. After the hang the kernel-side
>
> Nope - I've nailed it to a _really_ simple test case. It looks like a
> read() on a shutdown() unix dgram socket just kills the kernel. Demo code
> below. I wonder if this affects UP or is SMP only?
Kills my UP K6-2 dead as a doornail (except for pings, as you say).
-Doug
-
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/
next prev parent reply other threads:[~2001-02-01 18:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-01 14:14 Serious reproducible 2.4.x kernel hang Chris Evans
2001-02-01 14:40 ` Malcolm Beattie
2001-02-01 15:27 ` Chris Evans
2001-02-01 15:30 ` Malcolm Beattie
2001-02-01 16:03 ` Chris Evans
2001-02-01 16:52 ` Malcolm Beattie
2001-02-01 18:28 ` Chris Evans
2001-02-01 18:41 ` Doug McNaught [this message]
2001-02-01 18:42 ` rui.sousa
2001-02-02 9:25 ` [Patch]Re: " Prasanna P Subash
2001-02-02 9:29 ` David S. Miller
2001-02-03 20:26 ` kees
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=m3bssmgs96.fsf@belphigor.mcnaught.org \
--to=doug@wireboard.com \
--cc=chris@scary.beasts.org \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbeattie@sable.ox.ac.uk \
/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