From: John David Anglin <dave.anglin@bell.net>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Helge Deller <deller@gmx.de>, Parisc List <linux-parisc@vger.kernel.org>
Subject: Re: New Debian Kernel Packages
Date: Thu, 1 Aug 2013 19:29:51 -0400 [thread overview]
Message-ID: <BLU0-SMTP522B87E60AD62629BDAFE097500@phx.gbl> (raw)
In-Reply-To: <1375397525.2070.17.camel@dabdike>
On 1-Aug-13, at 6:52 PM, James Bottomley wrote:
> On Thu, 2013-08-01 at 18:39 -0400, John David Anglin wrote:
>> On 1-Aug-13, at 6:20 PM, Helge Deller wrote:
>>
>>> Hi Dave,
>>>
>>> On 07/30/2013 12:46 AM, John David Anglin wrote:
>>>> The following kernel packages are now in the parisc-linux.org
>>>> archive:
>>>>
>>>> linux-image-3.10-1-parisc-smp_3.10.3-1_hppa.deb
>>>> linux-image-3.10-1-parisc64-smp_3.10.3-1_hppa.deb
>>>> linux-image-3.10-1-parisc64_3.10.3-1_hppa.deb
>>>> linux-image-3.10-1-parisc_3.10.3-1_hppa.deb
>>>
>>> That's fantastic!
>>> This brings us one big step further to being able to build a real
>>> debian-unstable-installer boot CD.
>>>
>>> I'm still hoping the C8000 patches I pushed for inclusion into 3.11
>>> will then
>>> show up in stable 3.10 series soon as well. If that happens we will
>>> have a kernel
>>> which should boot on all machines - including the c8000.
>>
>>
>> I have bootstrap tested the linux-image-3.10-1-parisc64-
>> smp_3.10.3-1_hppa.deb package. We'll
>> have to see if 3.10 will be the Debian choice for the next release.
>>
>> As I mentioned in private, I have found that flush_cache_all() is the
>> principal problem causing random
>> segmentation faults on SMP systems.
>
> That would tend to indicate the architectural flush code is wrong: it
> isn't flushing all as it should be.
That thought had occurred to me. It's also possible that it doesn't
work
properly with the L3 added in the PA8800/PA8900 systems.
What seems to work is flushing all the user mappings.
I should note that I have also seen corruption of space register %sr1
(added checks in the routines that use pa_memcpy). I think the only
way that can happen is kernel stack corruption. Probably, this is also
caused by flush_cache_all. I know this issue has been around for
a long time.
I'll look at the flush code again.
Dave
--
John David Anglin dave.anglin@bell.net
next prev parent reply other threads:[~2013-08-01 23:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 22:46 New Debian Kernel Packages John David Anglin
2013-08-01 22:20 ` Helge Deller
2013-08-01 22:39 ` John David Anglin
2013-08-01 22:52 ` James Bottomley
2013-08-01 23:29 ` John David Anglin [this message]
2013-08-14 23:43 ` John David Anglin
2013-08-15 0:38 ` James Bottomley
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=BLU0-SMTP522B87E60AD62629BDAFE097500@phx.gbl \
--to=dave.anglin@bell.net \
--cc=James.Bottomley@HansenPartnership.com \
--cc=deller@gmx.de \
--cc=linux-parisc@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox