Messages in this thread | | | From | Pete Clements <> | Subject | Re: 2.5.73 -- Uninitialised timer! (i386) | Date | Tue, 24 Jun 2003 19:16:33 -0400 (EDT) |
| |
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 - 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/
| |