All of lore.kernel.org
 help / color / mirror / Atom feed
From: "BERTRAND Joël" <joel.bertrand@systella.fr>
To: sparclinux@vger.kernel.org
Subject: Re: sun4v_data_access_exception on new 2.6.23
Date: Fri, 12 Oct 2007 05:47:56 +0000	[thread overview]
Message-ID: <470F0A8C.2060502@systella.fr> (raw)
In-Reply-To: <470E6F28.2010709@systella.fr>

David Miller wrote:
> From: BERTRAND_Joël <joel.bertrand@systella.fr>
> Date: Thu, 11 Oct 2007 20:44:56 +0200
> 
>> 	Hello,
>>
>> 	I have built a 2.6.23 kernel on a T1000 server. I have seen this
>> message on system console :

	David,

> Looking at the trace some more, I'm %99.99999 sure you're using
> gcc-4.2.x to build this and that compiler is known to miscompile SMP
> sparc64 kernels.

	I a first time, I though that is was this trouble, but I can see the 
same bug with debian kernel provided by debian/testing (a 2.6.22 
kernel). I don't know what compiler was used to build debian kernel.

> gcc-4.1.x would never inline __flush_tsb_one() into flush_tsb_user(),
> yet as is evident in your backtraces this is exactly what has
> happened, therefore you must be using gcc-4.2.x or another non-4.1.x
> compiler to build this.

	OK, I will try to rebuild a kernel with gcc-4.1. Thanks for your help.

	Regards,

	JKB

  parent reply	other threads:[~2007-10-12  5:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-11 18:44 sun4v_data_access_exception on new 2.6.23 BERTRAND Joël
2007-10-11 21:42 ` David Miller
2007-10-11 22:37 ` David Miller
2007-10-12  5:47 ` BERTRAND Joël [this message]
2007-10-12  7:04 ` BERTRAND Joël
2007-10-12  8:37 ` David Miller
2007-10-12  8:50 ` David Miller
2007-10-12  8:52 ` BERTRAND Joël
2007-10-12  9:16 ` BERTRAND Joël
2007-10-12  9:27 ` David Miller

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=470F0A8C.2060502@systella.fr \
    --to=joel.bertrand@systella.fr \
    --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 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.