From: Keith Owens <kaos@ocs.com.au>
To: Tigran Aivazian <tigran@aivazian.fsnet.co.uk>
Cc: linux-kernel@vger.kernel.org, kdb@oss.sgi.com, aprasad@in.ibm.com
Subject: Re: test11-pre6 still very broken
Date: Sat, 18 Nov 2000 15:38:59 +1100 [thread overview]
Message-ID: <20616.974522339@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Fri, 17 Nov 2000 20:00:49 -0000." <Pine.LNX.4.21.0011171935560.1796-100000@saturn.homenet>
On Fri, 17 Nov 2000 20:00:49 +0000 (GMT),
Tigran Aivazian <tigran@aivazian.fsnet.co.uk> wrote:
>The mysterious lockups in test11-pre5 continue in test11-pre6. It is very
>difficult because the lockups appear to be kdb-specific (and kdb itself
>goes mad) but when there is no kdb there is very little useful information
>one can extract from a dead system...
ftp://oss.sgi.com/projects/kdb/download/ix86/kdb-v1.6-2.4.0-test11-pre7.gz
Assorted bug fixes from my work in progress tree, including one that
fixes a race between user space use of debug and kdb, ltrace trips this.
Some people have reported keyboard lockups after leaving kdb. I have
not been able to reproduce this problem, let me know if you still see
it.
-
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/
prev parent reply other threads:[~2000-11-18 5:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-17 20:00 test11-pre6 still very broken Tigran Aivazian
2000-11-17 20:04 ` H. Peter Anvin
2000-11-18 5:27 ` David Ford
2000-11-18 6:31 ` Greg KH
2000-11-18 7:14 ` Jeff Garzik
2000-11-18 7:25 ` Ben Ford
2000-11-18 7:56 ` Greg KH
[not found] ` <8v6h3d@penguin.transmeta.com>
2000-11-18 17:00 ` Pavel Machek
2000-11-18 18:17 ` Linus Torvalds
2000-11-20 12:37 ` Thomas Sailer
2000-11-20 12:47 ` Vojtech Pavlik
2000-11-21 11:35 ` Thomas Sailer
2000-11-18 0:29 ` Keith Owens
2000-11-18 4:38 ` Keith Owens [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=20616.974522339@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=aprasad@in.ibm.com \
--cc=kdb@oss.sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tigran@aivazian.fsnet.co.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 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.