From mboxrd@z Thu Jan 1 00:00:00 1970 From: William Lee Irwin III Subject: Re: [2/2] 2.6.22-rc4: known regressions v3 Date: Thu, 14 Jun 2007 08:02:19 -0700 Message-ID: <20070614150219.GG6909@holomorphy.com> References: <46704923.1010009@googlemail.com> <46704C44.8020602@googlemail.com> <20070614020055.GL15426@holomorphy.com> <20070614142146.GN15426@holomorphy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Michal Piotrowski , Andrew Morton , LKML , Netdev , Dan Aloni , Chad Tindel , Jay Vosburgh , Stephen Hemminger , sparclinux@vger.kernel.org, David Miller , Mikael Pettersson , linux-pm@lists.linux-foundation.org, "Rafael J. Wysocki" , Pavel Machek , Greg Kroah-Hartman , Alex Riesen , Andi Kleen , Ioan Ionita To: Mark Fortescue Return-path: Content-Disposition: inline In-Reply-To: Sender: sparclinux-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Thu, Jun 14, 2007 at 03:57:25PM +0100, Mark Fortescue wrote: > Benh's ptep_set_access_flags() patch needs to be applied in order to get > anyware with sun4c for all kernels >= linux-2.6.15. If not applied, you > will be lucky to get sash running as your init and even that will have > very limitit capabilities before it locks up the processor (power up > reset required). > It has been applied to both the kernels I used for testing so this > problem is independent of the ptep_set_access_flags patch but that > does not mean that it is not a related issue. > I will try to get some testing done over the weekend to narrow down > when the random illegal instructions first occour. > If I start with 2.6.21 then if that is OK, then I should be able to narow > the issue down without too much trouble. If it is between 2.6.20 and > 2.6.21 then it will be a right pig as there are a large number of commits > that don't compile for sun4c between these two. What I am hoping is that > it occours in the 2.6.22-rc2 as per the x86_64. Sounds like I'll be digging through my hardware stockpiles this weekend to find a functional sun4c box. -- wli