From: William Lee Irwin III <wli@holomorphy.com>
To: Mark Fortescue <mark@mtfhpc.demon.co.uk>
Cc: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Netdev <netdev@vger.kernel.org>, Dan Aloni <da-x@monatomic.org>,
Chad Tindel <ctindel@users.sourceforge.net>,
Jay Vosburgh <fubar@us.ibm.com>,
Stephen Hemminger <shemminger@linux-foundation.org>,
sparclinux@vger.kernel.org, David Miller <davem@davemloft.net>,
Mikael Pettersson <mikpe@it.uu.se>,
linux-pm@lists.linux-foundation.org,
"Rafael J. Wysocki" <rjw@sisk.pl>, Pavel Machek <pavel@ucw.cz>,
Greg Kroah-Hartman <gregkh@suse.de>,
Alex Riesen <raa.lkml@gmail.com>, Andi Kleen <ak@suse.de>,
Ioan Ionita <opslynx@gmail.com>
Subject: Re: [2/2] 2.6.22-rc4: known regressions v3
Date: Thu, 14 Jun 2007 15:02:19 +0000 [thread overview]
Message-ID: <20070614150219.GG6909@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0706141539140.29274@mtfhpc.demon.co.uk>
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
WARNING: multiple messages have this Message-ID (diff)
From: William Lee Irwin III <wli@holomorphy.com>
To: Mark Fortescue <mark@mtfhpc.demon.co.uk>
Cc: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Netdev <netdev@vger.kernel.org>, Dan Aloni <da-x@monatomic.org>,
Chad Tindel <ctindel@users.sourceforge.net>,
Jay Vosburgh <fubar@us.ibm.com>,
Stephen Hemminger <shemminger@linux-foundation.org>,
sparclinux@vger.kernel.org, David Miller <davem@davemloft.net>,
Mikael Pettersson <mikpe@it.uu.se>,
linux-pm@lists.linux-foundation.org,
"Rafael J. Wysocki" <rjw@sisk.pl>, Pavel Machek <pavel@ucw.cz>,
Greg Kroah-Hartman <gregkh@suse.de>,
Alex Riesen <raa.lkml@gmail.com>, Andi Kleen <ak@suse.de>,
Ioan Ionita <opslynx@gmail.com>
Subject: Re: [2/2] 2.6.22-rc4: known regressions v3
Date: Thu, 14 Jun 2007 08:02:19 -0700 [thread overview]
Message-ID: <20070614150219.GG6909@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0706141539140.29274@mtfhpc.demon.co.uk>
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
next prev parent reply other threads:[~2007-06-14 15:02 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <46704923.1010009@googlemail.com>
2007-06-13 19:57 ` [2/2] 2.6.22-rc4: known regressions v3 Michal Piotrowski
2007-06-13 19:57 ` Michal Piotrowski
2007-06-13 20:21 ` Björn Steinbrink
2007-06-13 20:21 ` Björn Steinbrink
2007-06-13 20:21 ` Björn Steinbrink
2007-06-13 20:21 ` Björn Steinbrink
2007-06-13 20:50 ` Michal Piotrowski
2007-06-13 20:50 ` Michal Piotrowski
2007-06-13 20:50 ` Michal Piotrowski
2007-06-13 22:25 ` Mark Fortescue
2007-06-13 22:25 ` Mark Fortescue
2007-06-14 2:00 ` William Lee Irwin III
2007-06-14 2:00 ` William Lee Irwin III
2007-06-14 10:30 ` Mark Fortescue
2007-06-14 10:30 ` Mark Fortescue
2007-06-14 14:21 ` William Lee Irwin III
2007-06-14 14:21 ` William Lee Irwin III
2007-06-14 14:21 ` William Lee Irwin III
2007-06-14 14:57 ` Mark Fortescue
2007-06-14 14:57 ` Mark Fortescue
2007-06-14 14:57 ` Mark Fortescue
2007-06-14 15:02 ` William Lee Irwin III
2007-06-14 15:02 ` William Lee Irwin III [this message]
2007-06-14 15:02 ` William Lee Irwin III
2007-06-17 11:35 ` Mark Fortescue
2007-06-17 11:35 ` Mark Fortescue
2007-06-17 11:35 ` Mark Fortescue
2007-06-14 10:30 ` Mark Fortescue
2007-06-14 2:00 ` William Lee Irwin III
2007-06-13 22:25 ` Mark Fortescue
2007-06-14 21:39 ` Stephen Hemminger
2007-06-14 21:39 ` Stephen Hemminger
2007-06-14 21:39 ` Stephen Hemminger
2007-06-15 23:26 ` Linus Torvalds
2007-06-15 23:26 ` Linus Torvalds
2007-06-15 23:26 ` Linus Torvalds
2007-06-13 19:57 ` Michal Piotrowski
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=20070614150219.GG6909@holomorphy.com \
--to=wli@holomorphy.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=ctindel@users.sourceforge.net \
--cc=da-x@monatomic.org \
--cc=davem@davemloft.net \
--cc=fubar@us.ibm.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mark@mtfhpc.demon.co.uk \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=mikpe@it.uu.se \
--cc=netdev@vger.kernel.org \
--cc=opslynx@gmail.com \
--cc=pavel@ucw.cz \
--cc=raa.lkml@gmail.com \
--cc=rjw@sisk.pl \
--cc=shemminger@linux-foundation.org \
--cc=sparclinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.