From: "David S. Miller" <davem@davemloft.net>
To: trizt@iname.com
Cc: mark@mtfhpc.demon.co.uk, linux-kernel@vger.kernel.org,
sparclinux@vger.kernel.org
Subject: Re: Sparc: Kernel 2.6.13 to 2.6.15-rc2 bug when running X11
Date: Tue, 03 Jan 2006 12:18:01 -0800 (PST) [thread overview]
Message-ID: <20060103.121801.18743523.davem@davemloft.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0601031456240.25341@lai.local.lan>
From: "J.O. Aho" <trizt@iname.com>
Date: Tue, 3 Jan 2006 15:01:09 +0100 (CET)
> After a small chat at #Gentoo-Sparc at freenode, I thought that I should
> just say that the problem with X locking up is still there (15-rc7),
> regardless of gcc version, and that the problem has to do with the UPA
> code according those who know a lot more than I do.
What "UPA code"?
We don't even have so much as a UPA driver in the Linux kernel.
So it's hard to know what is being spoken about. Maybe something
in the X server?
Perhaps these experts should explain :-)
next prev parent reply other threads:[~2006-01-03 20:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-12 10:13 Mark Fortescue
2005-12-12 10:38 ` J.O. Aho
2005-12-12 22:26 ` David S. Miller
2005-12-18 22:03 ` J.O. Aho
2005-12-18 23:10 ` David S. Miller
2006-01-03 14:01 ` J.O. Aho
2006-01-03 20:18 ` David S. Miller [this message]
2006-01-03 21:15 ` J.O. Aho
-- strict thread matches above, loose matches on Subject: below --
2005-12-06 2:04 J.O. Aho
2005-12-06 2:17 ` David S. Miller
2005-12-06 16:10 ` J.O. Aho
2005-12-06 23:23 ` David S. Miller
2005-12-07 11:05 ` J.O. Aho
2005-12-07 14:07 ` Ben Collins
2005-12-07 15:42 ` J.O. Aho
2005-12-07 20:34 ` David S. Miller
2005-12-07 21:22 ` J.O. Aho
2005-12-07 21:32 ` David S. Miller
2005-12-09 12:07 ` J.O. Aho
2005-12-10 22:25 ` J.O. Aho
2005-12-10 22:35 ` David S. Miller
2005-12-10 22:52 ` J.O. Aho
2005-12-10 23:00 ` David S. Miller
2005-12-10 23:22 ` J.O. Aho
2005-12-12 5:07 ` David S. Miller
2005-12-12 8:26 ` J.O. Aho
2005-12-12 16:28 ` J.O. Aho
2006-02-01 13:15 ` J.O. Aho
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=20060103.121801.18743523.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@mtfhpc.demon.co.uk \
--cc=sparclinux@vger.kernel.org \
--cc=trizt@iname.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
all inboxes | Powered by JetHome®