All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: James Simmons <jsimmons@edgeglobal.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: PowerPC kernel bug. (fwd)
Date: Mon, 20 Dec 1999 14:29:59 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.20.9912201428210.7400-100000@imperial.edgeglobal.com> (raw)



Geert I know you work with the PowerPC people. I don't belong to the list
so it might not go threw. So could you post it as well.

Subject: PowerPC kernel bug.
Date:    Mon, 13 Dec 1999 22:03:26 -0500 (EST)
From:    James Simmons <jsimmons@edgeglobal.com>
To:      GLX mailing list <glx-dev@lists.openprojects.net>, FrameBuffer List
<linux-fbdev@vuser.vu.union.edu>, Linux Kernel Mailing List
<linux-kernel@vger.rutgers.edu>


This message is toward the Fbdev/kernel group to fix this bug but I wanted
to let the GLX group what caused the memset problem on PowerPC. On a
PowerPC when you mmap the framebuffer and use memset on the mmapped
image you get a SIGBUS. Thanks Marcus for finding out what was causing the
problem.

>I noticed today that it's actually a bug in the PPC-kernel. The
>specification for the dcbz (data cache block zero) instruction
>states that for uncached memory the exception handler should clear
>the memory, but on Linux it just causes a SIGBUS to be sent to the
>app...
-----------
==============


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

                 reply	other threads:[~1999-12-20 19:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=Pine.LNX.4.20.9912201428210.7400-100000@imperial.edgeglobal.com \
    --to=jsimmons@edgeglobal.com \
    --cc=geert@linux-m68k.org \
    --cc=linuxppc-dev@lists.linuxppc.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.