From: "Adrian McMenamin" <adrianmcmenamin@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: lethal@users.sourceforge.net
Subject: Re: Problems with framebuffer in 2.6.22-git17
Date: Sun, 22 Jul 2007 22:02:02 +0100 [thread overview]
Message-ID: <92a12cdb0707221402g4bce07b3u775d291fc2652f79@mail.gmail.com> (raw)
In-Reply-To: <92a12cdb0707221141i4398d6fdxa7994c5f1f809b0a@mail.gmail.com>
On 22/07/07, Adrian McMenamin <adrianmcmenamin@gmail.com> wrote:
> I ma having problems with the pvr2 fb on the Dreamcast in 2.6.22-git17
> - when the code is executed it appears to lock the Dreamcast up.
>
> The problem seems to be:
>
> fb_notifier_call_chain(FB_EVENT_FB_REGISTERED, &event);
>
> In drivers/video/fbmem.c
>
> This hasn't been an issue before, so are there any recent changes that
> might have caused this?
>
> (fb_notifier_call_chain calls a succession of stubs ending in
> __blocking_notifier_call_chain in kernel/sys.c)
Looking further, the problem can be further narrowed to
ret = nb->notifier_call(nb, val, v);
in
static int __kprobes notifier_call_chain(struct notifier_block **nl,
unsigned long val, void *v,
int nr_to_call, int *nr_calls)
In kernel/sys.c
next prev parent reply other threads:[~2007-07-22 21:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-22 18:41 Adrian McMenamin
2007-07-22 21:02 ` Adrian McMenamin [this message]
2007-07-22 23:22 ` Antonino A. Daplas
[not found] ` <8b67d60707231324k28f3cd45p287418fd77feaf00@mail.gmail.com>
2007-07-23 20:35 ` Adrian McMenamin
2007-07-23 21:06 ` Paul Mundt
2007-07-24 21:45 ` Adrian McMenamin
2007-07-25 23:33 ` Antonino A. Daplas
2007-07-27 19:47 ` Adrian McMenamin
2007-07-27 20:18 ` Adrian McMenamin
2007-07-27 21:31 ` Antonino A. Daplas
2007-07-27 22:25 ` Adrian McMenamin
2007-07-27 23:22 ` Antonino A. Daplas
2007-07-28 0:32 ` Adrian McMenamin
2007-07-28 0:52 ` Antonino A. Daplas
2007-07-28 1:06 ` Adrian McMenamin
2007-07-28 2:14 ` Antonino A. Daplas
2007-07-28 2:18 ` Antonino A. Daplas
2007-07-27 21:43 ` Antonino A. Daplas
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=92a12cdb0707221402g4bce07b3u775d291fc2652f79@mail.gmail.com \
--to=adrianmcmenamin@gmail.com \
--cc=lethal@users.sourceforge.net \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®