Re: [PATCH] silo: Don't touch %tick_cmpr on sun4v cpus.
From: Jurij Smakov Date: Sun, 19 Aug 2012 23:29:05 +0100 > On Sun, Aug 19, 2012 at 03:24:45PM -0700, David Miller wrote: >> From: Jurij Smakov >> Date: Sun, 19 Aug 2012 16:41:42 +0100 >> >> > I just uploaded a new silo package (1.4.14+git20120819-1) including >> > these fixes to unstable, and would encourage everyone to test it (it >> > should appear on the mirrors within a few hours). After a grace period >> > of 10 days we are going to arrange for its propagation to testing, >> > given that no problems are reported. >> >> Thanks a lot Jurij. >> >> Just FYI I also pushed a ext4 fix into the SILO tree yesterday >> after I received positive feedback from a bug reporter. > > This fix is included in the latest uploaded version as well. Excellent. -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120819.152959.477498039314404709.da...@davemloft.net
Re: [PATCH] silo: Don't touch %tick_cmpr on sun4v cpus.
From: Jurij Smakov Date: Sun, 19 Aug 2012 16:41:42 +0100 > I just uploaded a new silo package (1.4.14+git20120819-1) including > these fixes to unstable, and would encourage everyone to test it (it > should appear on the mirrors within a few hours). After a grace period > of 10 days we are going to arrange for its propagation to testing, > given that no problems are reported. Thanks a lot Jurij. Just FYI I also pushed a ext4 fix into the SILO tree yesterday after I received positive feedback from a bug reporter. -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120819.152445.110365253381974516.da...@davemloft.net
Re: [PATCH] silo: Don't touch %tick_cmpr on sun4v cpus.
On Sun, Aug 19, 2012 at 03:24:45PM -0700, David Miller wrote: > From: Jurij Smakov > Date: Sun, 19 Aug 2012 16:41:42 +0100 > > > I just uploaded a new silo package (1.4.14+git20120819-1) including > > these fixes to unstable, and would encourage everyone to test it (it > > should appear on the mirrors within a few hours). After a grace period > > of 10 days we are going to arrange for its propagation to testing, > > given that no problems are reported. > > Thanks a lot Jurij. > > Just FYI I also pushed a ext4 fix into the SILO tree yesterday > after I received positive feedback from a bug reporter. This fix is included in the latest uploaded version as well. Best regards, -- Jurij Smakov ju...@wooyd.org Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120819222905.ga4...@wooyd.org
Re: [PATCH] silo: Don't touch %tick_cmpr on sun4v cpus.
On Wed, Aug 15, 2012 at 01:14:16AM -0700, David Miller wrote: > > This generates an illegal instruction exception. > > This has a long history. For the first sun4v port of SILO in commit > 494770a17eea7192d3242051e76f4da6d838e3a1 ("SILO Niagara/SUN4V > support") this code was removed entirely. > > But later this was found to regress older UltraSPARC boxes, so we put > it back in commit bd708e35bdcd8e92cb7c65368f2a356982df7cd8 ("Fix > Ultra10 SILO timer"). But that was wrong too. > > The OBP still owns the trap table when SILO runs and it uses the > %tick_cmpr generated interrupt. This has a bad interraction with how > we use the %tick register in SILO. > > SILO first reads the %tick register and remembers this value as the > time base. > > Later, we read %tick again, compute the difference, and use this to > calcualte the amount of time elapsed. > > OBP's %tick_cmpr interrupt handler is doing something funky, such as > resetting %tick, which makes our timeouts never actually expire. > > This issue doesn't exist on sun4v machines, and we absolutely cannot > try to touch the %tick_cmpr register as that generates an illegal > instruction trap on such cpus. > > Signed-off-by: David S. Miller > --- > > I just committed this into the SILO git repo. > > Debian folks, you really want this propagated into your installer as > soon as possible. All the install ISOs will crash in SILO on all > sun4v (Niagara) machines unless an explicit SILO boot target is given > on the boot command line. I used "boot cdrom install" to get around > this. > > It triggers any time the timer mechanism is enabled ("timeout=foo" is > specified in silo.conf) Thanks, David. I just uploaded a new silo package (1.4.14+git20120819-1) including these fixes to unstable, and would encourage everyone to test it (it should appear on the mirrors within a few hours). After a grace period of 10 days we are going to arrange for its propagation to testing, given that no problems are reported. Best regards, -- Jurij Smakov ju...@wooyd.org Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120819154142.ga14...@wooyd.org