mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mikael Pettersson <mikpe@csd.uu.se>
To: Pete Clements <clem@clem.clem-digital.net>
Cc: akpm@digeo.com (Andrew Morton),
	linux-kernel@vger.kernel.org (linux-kernel)
Subject: Re: 2.5.73 -- Uninitialised timer! (i386)
Date: Tue, 24 Jun 2003 23:35:07 +0200	[thread overview]
Message-ID: <16120.50188.29.739261@gargle.gargle.HOWL> (raw)
In-Reply-To: <200306242033.QAA27440@clem.clem-digital.net>

Pete Clements writes:
 > Quoting Andrew Morton
 >   > 
 >   > Well it beats me.  That timer is clearly initialised OK.
 >   > 
 >   > What compiler version are you using?  Can you try
 >   > a different one>?
 > 
 > Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.4/specs
 > gcc version 2.95.4 20011002 (Debian prerelease)
 > 
 > Only compiler currently installed.  Have four systems (3 single
 > processor, 1 dual) all running Debian--woody with same versions.
 > On the UP systems, will see several of these traces during boot.
 > After that, it is very seldom (0 to 3 in 12 hours). Have seen none
 > on the SMP system.  Recompiled one of the UP systems with SMP
 > enabled and no longer saw the trace during boot and post. Have
 > not seen this prior to 2.5.73.

Apply the patch below (which I posted to LKML yesterday btw).
2.5.73 incorrectly removed the workaround needed to prevent
gcc-2.95.x from miscompiling spinlocks on UP (they become
empty structs, and gcc-2.95.x has problems with those).

/Mikael

--- linux-2.5.73/include/linux/spinlock.h.~1~	2003-06-23 13:07:39.000000000 +0200
+++ linux-2.5.73/include/linux/spinlock.h	2003-06-23 22:58:29.000000000 +0200
@@ -146,8 +146,13 @@
 /*
  * gcc versions before ~2.95 have a nasty bug with empty initializers.
  */
-typedef struct { } spinlock_t;
-#define SPIN_LOCK_UNLOCKED (spinlock_t) { }
+#if (__GNUC__ > 2)
+  typedef struct { } spinlock_t;
+  #define SPIN_LOCK_UNLOCKED (spinlock_t) { }
+#else
+  typedef struct { int gcc_is_buggy; } spinlock_t;
+  #define SPIN_LOCK_UNLOCKED (spinlock_t) { 0 }
+#endif
 
 /*
  * If CONFIG_SMP is unset, declare the _raw_* definitions as nops

  reply	other threads:[~2003-06-24 21:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030624124800.72bfb98d.akpm@digeo.com>
2003-06-24 20:33 ` Pete Clements
2003-06-24 21:35   ` Mikael Pettersson [this message]
2003-06-24 22:31     ` Andrew Morton
2003-06-25  9:21       ` Mikael Pettersson
2003-06-25 16:09         ` Jeff
2003-06-24 23:16     ` Pete Clements
2003-06-24 18:02 Pete Clements

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=16120.50188.29.739261@gargle.gargle.HOWL \
    --to=mikpe@csd.uu.se \
    --cc=akpm@digeo.com \
    --cc=clem@clem.clem-digital.net \
    --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®