From: Andrew Morton <akpm@osdl.org>
To: Wink Saville <wink@saville.com>
Cc: Matthias Hentges <oe@hentges.net>,
linux-fbdev-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
Arjan van de Ven <arjan@infradead.org>
Subject: Re: Hang in fb_notifier_call_chain with nvidia framebuffer
Date: Sat, 7 Oct 2006 23:01:29 -0700 [thread overview]
Message-ID: <20061007230129.323ac807.akpm@osdl.org> (raw)
In-Reply-To: <4523E09C.9000609@saville.com>
On Wed, 04 Oct 2006 09:26:04 -0700
Wink Saville <wink@saville.com> wrote:
> Attached in the zip file is:
>
> log-hang1.txt -> log showing hang
> cfg-hang1 -> config file for hang condition
> cfg-ok -> config file that works
> fbmem.c -> Modifications to register_framebuffer
>
> To possibly assist I turned on debugging in nvidia.c and found that it
> hung in the call to register_framebuffer. I then added some additional
> debug in that routine and it appears the hang occurs in the call to
> fb_notifier_call_chain.
>
> Please let me know what else maybe needed.
Please:
- get sysrq working:
set CONFIG_MAGIC_SYSRQ=y, rebuild, reboot
echo 1 > /proc/sys/kernel/sysrq
dmesg -n 8
- make it hang
- Hit alt-sysrq-T
- Send us the resulting output
Thanks.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next parent reply other threads:[~2006-10-08 6:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <45206777.7020405@saville.com>
[not found] ` <1159808447.4652.6.camel@mhcln03>
[not found] ` <4521E326.2000406@saville.com>
[not found] ` <1159882225.2891.525.camel@laptopd505.fenrus.org>
[not found] ` <4523E09C.9000609@saville.com>
2006-10-08 6:01 ` Andrew Morton [this message]
2006-10-08 8:14 ` Hang in fb_notifier_call_chain with nvidia framebuffer Wink Saville
2006-10-08 9:07 ` Andrew Morton
2006-10-08 18:06 ` Wink Saville
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=20061007230129.323ac807.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=oe@hentges.net \
--cc=wink@saville.com \
/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;
as well as URLs for NNTP newsgroup(s).