From: John Gluck <jgluckca@home.com>
To: unlisted-recipients:; (no To-header on input)@localhost.localdomain
Cc: linux-kernel@vger.kernel.org
Subject: Re: Deadlock with linux kernel
Date: Fri, 26 Oct 2001 15:16:24 -0400 [thread overview]
Message-ID: <3BD9B688.36E2F08C@home.com> (raw)
In-Reply-To: <Pine.LNX.4.33L.0110261537170.22127-100000@duckman.distro.conectiva> <3BD9AE9D.53D53936@resilience.com> <3BD9B066.57EDDDAB@welho.com>
Hi
This is interesting. I've never had a lockup with any kernel.
I wonder if it might be related to the type of uses the machine is put to.
My machine is a Dual PIII based of the intel GX chipset. It serves as
Workstation primarily but also does firewalling and acts as a gateway for my
other PCs. Mostly the load isn't too heavy but I do crank it up a lot when I
compile KDE and have several parts building at the same time.
John
Mika Liljeberg wrote:
> Jeff Golds wrote:
> > No, it only hung just after boot one time. However, I was doing a
> > kernel build when it hung (I was trying to make a new kernel to try out
> > as I had just rebooted).
> >
> > Most times, the machine will stay up for a day or two then lock during a
> > kernel build.
>
> Hi Jeff,
>
> I have the exact same symptoms on my PII SMP, 440BX chipset machine, and
> I believe it started around version 2.4.6 as you say. Prior to that, my
> machine would reboot randomly without warning. The latest kernel that
> neither reboots nor locks up is 2.4.0-test9. Sometimes it takes two
> hours, sometimes it takes two days, sometimes it takes longer.
>
> The machine just freezes solid, nothing appears on the console, sysrq
> won't work, leds won't blink, and I suspect the CPUs are spinning (I can
> hear the CPU fans pick up speed, when it happens). The lockups don't
> seem to have any relation to what the machine is doing at the time. An
> idle machine seems to lock up just as readily as a busy one.
>
> Regards,
>
> MikaL
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-10-26 19:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-26 18:33 Jeff Golds
2001-10-26 17:38 ` Rik van Riel
2001-10-26 18:42 ` Jeff Golds
2001-10-26 18:50 ` Mika Liljeberg
2001-10-26 19:16 ` John Gluck [this message]
2001-10-26 17:44 ` Alan Cox
2001-10-26 18:44 ` Jeff Golds
2001-10-26 18:52 ` Andreas Dilger
[not found] <fa.e6tgf0v.g6kp2s@ifi.uio.no>
[not found] ` <fa.dja9fnv.cka9g7@ifi.uio.no>
2001-10-29 2:08 ` Sam Varshavchik
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=3BD9B688.36E2F08C@home.com \
--to=jgluckca@home.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
all inboxes | Powered by JetHome®