All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sam Varshavchik" <mrsam@courier-mta.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Deadlock with linux kernel
Date: Mon, 29 Oct 2001 02:08:55 GMT	[thread overview]
Message-ID: <courier.3BDCBA37.00004670@ny.email-scan.com> (raw)
In-Reply-To: <fa.e6tgf0v.g6kp2s@ifi.uio.no> <fa.dja9fnv.cka9g7@ifi.uio.no>
In-Reply-To: <fa.dja9fnv.cka9g7@ifi.uio.no>

Mika Liljeberg writes: 

> 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.

A small SMP bug did indeed slip through in 2.4.6 that nails some SMP 
hardware dead cold.  It should be fixed in the -ac tree know.  Have no idea 
about the spontaneous reboots you were seeing with the earlier kernels. 

> 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).

Yup.  If you have the right combination of hardware, in 2.4.6+ you could 
sometimes end up in an infinite loop while holding a spinlock.  I was able 
to hit the jackpot with dual P-IIIs on a 440GX with two aic7xxx HBAs. 

This wouldn't explain your spontaneous reboots, but try booting with 
"noapic". 

-- 
Sam 


       reply	other threads:[~2001-10-29  2:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.e6tgf0v.g6kp2s@ifi.uio.no>
     [not found] ` <fa.dja9fnv.cka9g7@ifi.uio.no>
2001-10-29  2:08   ` Sam Varshavchik [this message]
2001-10-26 18:33 Deadlock with linux kernel 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
2001-10-26 17:44 ` Alan Cox
2001-10-26 18:44   ` Jeff Golds
2001-10-26 18:52     ` Andreas Dilger

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=courier.3BDCBA37.00004670@ny.email-scan.com \
    --to=mrsam@courier-mta.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 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.