mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "J.O. Aho" <trizt@iname.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: mark@mtfhpc.demon.co.uk,
	linux-kernel maillist <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, 3 Jan 2006 15:01:09 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.64.0601031456240.25341@lai.local.lan> (raw)
In-Reply-To: <20051212.142654.62759069.davem@davemloft.net>

On Mon, 12 Dec 2005, David S. Miller wrote:

> From: "J.O. Aho" <trizt@iname.com>
> Date: Mon, 12 Dec 2005 11:38:32 +0100 (CET)
>
>> I have been using gcc-3.3.5 (64bits) when building the kernel, today
>> I did upgrade to gcc-3.3.6 (64bits), but still have the same problem
>> with the X11.  For build normal system applications and tools I have
>> gcc-3.3.6 (32bit).
>
> I use gcc-4.0.2 and gcc-3.4.5 for all of my kernel builds.

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.

Thanks again for all help.

-- 
      //Aho

  ------------------------------------------------------------------------
   E-Mail: trizt@iname.com            URL: http://www.kotiaho.net/~trizt/
      ICQ: 13696780
   System: Linux System                        (PPC7447/1000 AMD K7A/2000)
  ------------------------------------------------------------------------
             EU forbids you to send spam without my permission
  ------------------------------------------------------------------------

  parent reply	other threads:[~2006-01-03 14:01 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 [this message]
2006-01-03 20:18       ` David S. Miller
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=Pine.LNX.4.64.0601031456240.25341@lai.local.lan \
    --to=trizt@iname.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark@mtfhpc.demon.co.uk \
    --cc=sparclinux@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

all inboxes | Powered by JetHome®