From: David Ford <david@linux.com>
To: "H. Peter Anvin" <hpa@zytor.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: test11-pre6 still very broken
Date: Fri, 17 Nov 2000 21:27:19 -0800 [thread overview]
Message-ID: <3A161337.6A1BE826@linux.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0011171935560.1796-100000@saturn.homenet> <8v4306$sga$1@cesium.transmeta.com>
[-- Attachment #1: Type: text/plain, Size: 757 bytes --]
> > 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
[...]
> It could be that -test5 and -test6 break some assumption kdb makes.
> It has been eminently stable here.
Whether or not the assumptions are made, the last testN series of kernels have
introduced two serious issues IMO. The first is the mysterious deadlocks and
no way to figure them out. With kdb the machine won't hang. Without it, it
deadlocks within 36 hours.
The second issue is usb. I now have two machines that lockup on boot in USB.
One is the above workstation, the second is a Compaq laptop. Unfortunately
I have no way of unplugging the USB hardware inside the laptop :P
-d
[-- Attachment #2: Card for David Ford --]
[-- Type: text/x-vcard, Size: 176 bytes --]
begin:vcard
n:Ford;David
x-mozilla-html:TRUE
adr:;;;;;;
version:2.1
email;internet:david@kalifornia.com
title:Blue Labs Developer
x-mozilla-cpt:;14688
fn:David Ford
end:vcard
next prev parent reply other threads:[~2000-11-18 5:58 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 [this message]
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
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=3A161337.6A1BE826@linux.com \
--to=david@linux.com \
--cc=hpa@zytor.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