From: Andrew Morton <akpm@zip.com.au>
To: Lars Christensen <larsch@cs.auc.dk>
Cc: linux-kernel@vger.kernel.org, linux-bugs@nvidia.com
Subject: Re: 2.4.17 agpgart process hang on crash
Date: Sat, 02 Feb 2002 14:32:02 -0800 [thread overview]
Message-ID: <3C5C68E2.32D11734@zip.com.au> (raw)
In-Reply-To: <Pine.GSO.4.33.0202022219340.29744-100000@peta.cs.auc.dk>
Lars Christensen wrote:
>
> Hi. I have experienced a problem with the combination of kernel-2.4.16,
> the kernel agpgart module and NVIDIA supplied drivers. I don't know which
> is the cause of the problem.
>
> Symptoms: Whenever an OpenGL application crashes (segfault etc.), the
> process hangs and can't be killed. Responds to no signals (not even 9). ps
> -ef hangs, it seems, when the crashed process is to be listed (some other
> processes are listed first).
>
> Hardware: AMD Athlon 1.333HGZ, ASUS M266 motherboard (AMD761 AGP
> chipset), NVIDIA GeForce2 MX400 gfx card.
>
> The mem=nopentium option have no effect on the problem, but it doesn't
> occur if I use the NVIDIA AGP drivers or kernel 2.4.16 agp drivers. I am
> not able to test the 2.4.17 agpgart with other 3D hardware that nvidia.
>
This is possibly because the crashing application tries to dump
core, and the kernel gets a fault accessing the video card's
mapping, and deadlocks over the recursive attempt to take mmap_sem.
Please apply this patch:
http://www.zip.com.au/~akpm/linux/2.4/2.4.18-pre7/fbmem-mmap.patch
and send a report back.
-
next prev parent reply other threads:[~2002-02-02 22:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-02 21:55 2.4.17 agpgart process hang on crash Lars Christensen
2002-02-02 22:17 ` Alan Cox
2002-02-02 22:29 ` Lars Christensen
2002-02-02 22:32 ` Andrew Morton [this message]
2002-02-02 23:13 ` Lars Christensen
2002-02-02 23:32 ` Andrew Morton
2002-02-03 0:13 ` Lars Christensen
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=3C5C68E2.32D11734@zip.com.au \
--to=akpm@zip.com.au \
--cc=larsch@cs.auc.dk \
--cc=linux-bugs@nvidia.com \
--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 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.