mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pete Clements <clem@clem.clem-digital.net>
To: mikpe@csd.uu.se (Mikael Pettersson)
Cc: clem@clem.clem-digital.net, akpm@digeo.com, linux-kernel@vger.kernel.org
Subject: Re: 2.5.73 -- Uninitialised timer! (i386)
Date: Tue, 24 Jun 2003 19:16:33 -0400 (EDT)	[thread overview]
Message-ID: <200306242316.TAA28624@clem.clem-digital.net> (raw)
In-Reply-To: <16120.50188.29.739261@gargle.gargle.HOWL> from Mikael Pettersson at "Jun 24, 2003 11:35: 7 pm"

Quoting Mikael Pettersson
  > 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
  > 

Patch applied, cleared up the traces.

-- 
Pete Clements 
clem@clem.clem-digital.net

  parent reply	other threads:[~2003-06-24 23:02 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
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 [this message]
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=200306242316.TAA28624@clem.clem-digital.net \
    --to=clem@clem.clem-digital.net \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@csd.uu.se \
    /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®