From: rct@gherkin.sa.wlk.com (Bob_Tracy)
To: "Mohammad A. Haque" <mhaque@haque.net>
Cc: dep <dennispowell@earthlink.net>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: test12 lockups -- need feedback
Date: Thu, 14 Dec 2000 08:41:20 -0600 (CST) [thread overview]
Message-ID: <m146ZZQ-0005keC@gherkin.sa.wlk.com> (raw)
In-Reply-To: <3A38B9C8.B11C4ABC@haque.net> "from Mohammad A. Haque at Dec 14, 2000 07:15:04 am"
Mohammad A. Haque wrote:
> Were you connected to a network or receiving/sending anything?
>
> dep wrote:
> >
> > okay. got it here this morning, too. solid lock -- no dumping out of
> > x, no changing terminals, no mouse, no keyboard.
> >
> > k6-2-550 @ 500; 256mb memory, fic 503a mb with via chipset.
This one is going to be fun to track down. So far, with a personal
sample size of three machines, 2.4.0-test12 is stable on two, locks
up in a predictable and repeatable manner on one. First, the stable
machines:
(1) P150 MMX Toshiba Tecra 730XCDT notebook, egcs-2.91.66, openwin
with XFree86 3.3.6.
(2) Cyrix 6x86 MII 233, egcs-2.91.66, AfterStep with XFree86 4.0.1,
NVIDIA-0.9-5 video driver.
The unstable machine:
Gateway PII 333, egcs-2.91.66, AfterStep with XFree86 3.3.6.
Running "startx" as "root" --> ok: no problem.
Running "startx" as normal user --> I get as far as the grey moire
pattern with the black "X" cursor in the center of the screen, and
the machine locks up solid. Cannot switch consoles, machine doesn't
respond to pings (much less remote access attempts), no disk activity,
no "oops" messages in any of the logfiles. Absolutely repeatable.
Machine works fine with earlier kernels.
Does anyone have a feeling one way or the other as far as this being
related to the CPU type? I can try building a pre-PII CPU kernel on
the unstable machine and see if that makes any difference.
--
Bob Tracy rct@frus.com
-----------------------------------------------------------------
"We might not be in hell, but we can see the gates from here."
--Phoenix resident, Summer of 2000
-
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:[~2000-12-14 15:12 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-13 23:22 Mohammad A. Haque
2000-12-14 0:22 ` Mikael Djurfeldt
2000-12-14 0:29 ` Mikael Djurfeldt
2000-12-14 1:28 ` dep
2000-12-14 2:58 ` Mohammad A. Haque
2000-12-14 3:48 ` Mohammad A. Haque
2000-12-14 12:21 ` Ingo Oeser
2000-12-14 11:42 ` Mohammad A. Haque
2000-12-15 15:20 ` Ingo Oeser
2000-12-14 12:10 ` dep
2000-12-14 12:15 ` Mohammad A. Haque
2000-12-14 13:16 ` dep
2000-12-14 14:41 ` Bob_Tracy [this message]
2000-12-14 18:38 ` ip_defrag is broken (was: Re: test12 lockups -- need feedback) Ion Badulescu
2000-12-14 19:27 ` David S. Miller
2000-12-14 19:52 ` Ion Badulescu
2000-12-14 19:43 ` David S. Miller
2000-12-14 20:07 ` Ion Badulescu
2000-12-14 19:55 ` Netfilter is broken (was Re: ip_defrag is broken (was: Re: test12 lockups -- need feedback)) David S. Miller
2000-12-15 0:11 ` David S. Miller
2000-12-15 0:48 ` Andi Kleen
2000-12-15 1:25 ` Harald Welte
2000-12-15 0:20 ` Harald Welte
2000-12-14 20:35 ` ip_defrag is broken (was: Re: test12 lockups -- need feedback) Mohammad A. Haque
2000-12-14 20:23 ` David S. Miller
2000-12-14 21:25 ` Mohammad A. Haque
2000-12-14 22:50 ` Mohammad A. Haque
2000-12-14 23:58 ` Mohammad A. Haque
2000-12-15 8:52 ` Jasper Spaans
2000-12-15 9:22 ` Tom Leete
2000-12-15 2:25 ` Tom Leete
2000-12-15 13:12 ` Rusty Russell
2000-12-14 20:49 ` Bob_Tracy
2000-12-14 10:11 test12 lockups -- need feedback Martin Bahlinger
2000-12-14 18:52 Eckhard Jokisch
2000-12-15 18:47 ` Ingo Oeser
2000-12-15 17:52 ` H. Peter Anvin
2000-12-15 18:06 ` Alan Cox
2000-12-15 19:21 ` Ingo Oeser
2000-12-15 19:16 ` Ingo Oeser
2000-12-15 18:50 ` mike
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=m146ZZQ-0005keC@gherkin.sa.wlk.com \
--to=rct@gherkin.sa.wlk.com \
--cc=dennispowell@earthlink.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mhaque@haque.net \
/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
all inboxes | Powered by JetHome®