Date: Sat, 7 Oct 2006 23:01:29 -0700
From: Andrew Morton <akpm@osdl.org>
To: Wink Saville <wink@saville.com>
Cc: Arjan van de Ven <arjan@infradead.org>, Matthias Hentges <oe@hentges.net>,
       linux-kernel@vger.kernel.org, linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Hang in fb_notifier_call_chain with nvidia framebuffer
Message-Id: <20061007230129.323ac807.akpm@osdl.org>
In-Reply-To: <4523E09C.9000609@saville.com>
References: <45206777.7020405@saville.com>
	<1159808447.4652.6.camel@mhcln03>
	<4521E326.2000406@saville.com>
	<1159882225.2891.525.camel@laptopd505.fenrus.org>
	<4523E09C.9000609@saville.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1015
Lines: 37

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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/