From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: GL-related crash w/ X 4.3 & kernel 2.6
Date: Mon, 29 Dec 2003 19:57:32 +0000 [thread overview]
Message-ID: <marc-linux-ia64-107272856028654@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-107272704926812@msgid-missing>
>>>>> On Mon, 29 Dec 2003 19:41:44 +0000, Matthew Wilcox <willy@debian.org> said:
Matthew> The machine is a zx2000 workstation with a Radeon 7000/VE
Matthew> card. Kernel is 2.6.0 plus some additional changes (mostly
Matthew> jgarzik's latest netdrivers patch) [but it's happened with
Matthew> other 2.6 kernels]. The X server is Debian's 4.3.0-0pre1v5
Matthew> [but it's happened with other 4.3.0 releases].
Do you have DRI enabled? I pretty much had given up on Radeon hw
accelleration, because if failed for me in the same manner on both x86
and ia64. Perhaps things have improved in the meantime?
Hardware-accellerated OpenGL did work fine for me with Nvidia until
the recent glibc upgrade forced me to turn it off for now. I hadn't
tried FlightGear though.
>>>>> On Mon, 29 Dec 2003 19:41:44 +0000, Matthew Wilcox <willy@debian.org> said:
Matthew> Second, since neither strace nor gdb is willing to
Matthew> cooperate in helping to track this down, can anyone more
Matthew> knowledgable than I about the ways of GL suggest how to
Matthew> start debugging this?
You mean you can't use gdb to attach to the CPU-hogging processes? My
guess would be that the server and the app get stuck trying to acquire
a lock, which is incidentally an area that the Radeon DRI driver had
problems with in the past.
--david
next prev parent reply other threads:[~2003-12-29 19:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-29 19:41 GL-related crash w/ X 4.3 & kernel 2.6 Matthew Wilcox
2003-12-29 19:57 ` David Mosberger [this message]
2003-12-29 20:51 ` Matthew Wilcox
2003-12-29 21:40 ` David Mosberger
2003-12-29 22:34 ` Matthew Wilcox
-- strict thread matches above, loose matches on Subject: below --
2004-01-16 23:37 Stephane Eranian
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=marc-linux-ia64-107272856028654@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@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