All of lore.kernel.org
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: John David Anglin <dave.anglin@bell.net>,
	linux-parisc <linux-parisc@vger.kernel.org>
Subject: Re: fixmap problem on PA11 hardware
Date: Sun, 31 Oct 2021 22:22:29 +0100	[thread overview]
Message-ID: <0a068f90-84bb-dbe1-b8b3-6fd7709b814a@gmx.de> (raw)
In-Reply-To: <a10ff403-3869-9eb1-8213-b51e6ca8d219@bell.net>

On 10/27/21 22:14, John David Anglin wrote:
> On 2021-10-27 3:09 p.m., Helge Deller wrote:
>> In the archives I found this old thread, which might be related:
>> https://www.spinics.net/lists/linux-parisc/msg09391.html
> These seems unlikely as both 7100LC and 7300LC are PA-RISC 1.1 processors (1.1c vs. 1.1e).  Big difference
> seems to be cache.

Yes, there were at least two problems.
I just sent two patches to the list which fix the crashes.
But FTRACE still doesn't work on PA1.x machines as expected,
while the same code seems to work on PA2.x machines (running the same 32bit kernel).

The PA7100LC reports (machine: 715/64):
Kprobe smoke test: started
Kprobe smoke test: kretprobe handler not called
Kprobe smoke test: kretprobe handler not called
Kprobe smoke test: kretprobe handler2 not called
Kprobe smoke test: BUG: 3 error(s) running handlers

On the PA7300LC (machine B160L):
Kprobe smoke test: started
Kprobe smoke test: kprobe pre_handler not called
Kprobe smoke test: kprobe post_handler not called
Kprobe smoke test: kprobe pre_handler not called
Kprobe smoke test: kprobe post_handler not called
Kprobe smoke test: kprobe pre_handler2 not called
Kprobe smoke test: kprobe post_handler2 not called
Kprobe smoke test: kretprobe handler not called
Kprobe smoke test: kretprobe handler not called
Kprobe smoke test: kretprobe handler2 not called
Kprobe smoke test: BUG: 9 error(s) running handlers

On the PA8x00 (machine C3000):
Kprobe smoke test: started
Kprobe smoke test: passed successfully

Helge

  reply	other threads:[~2021-10-31 21:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-27 19:09 fixmap problem on PA11 hardware Helge Deller
2021-10-27 20:14 ` John David Anglin
2021-10-31 21:22   ` Helge Deller [this message]
2021-10-31 22:47     ` John David Anglin
2021-10-31 23:07       ` Helge Deller
2021-10-31 23:56         ` John David Anglin
2021-11-01  0:01           ` John David Anglin
2021-11-01  0:06             ` John David Anglin
2021-11-01 18:09               ` Helge Deller
2021-11-02 21:25                 ` John David Anglin

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=0a068f90-84bb-dbe1-b8b3-6fd7709b814a@gmx.de \
    --to=deller@gmx.de \
    --cc=dave.anglin@bell.net \
    --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 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.