From owner-freebsd-stable@FreeBSD.ORG Wed Dec 29 07:31:31 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 94E0C16A4CE for ; Wed, 29 Dec 2004 07:31:31 +0000 (GMT) Received: from mail.distalzou.net (203.141.139.231.user.ad.il24.net [203.141.139.231]) by mx1.FreeBSD.org (Postfix) with ESMTP id DE0C043D2F for ; Wed, 29 Dec 2004 07:31:30 +0000 (GMT) (envelope-from devin@spamcop.net) Received: from plexi.pun-pun.prv ([192.168.7.29] helo=plexi) by mail.distalzou.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.43 (FreeBSD)) id 1CjYIl-0009a6-RQ; Wed, 29 Dec 2004 16:31:23 +0900 Date: Wed, 29 Dec 2004 16:31:23 +0900 (JST) From: Tod McQuillin X-X-Sender: devin@plexi.pun-pun.prv To: Igor Sysoev In-Reply-To: <20041229101325.R73628@is.park.rambler.ru> Message-ID: <20041229163016.G81711@plexi.pun-pun.prv> References: <20041228162708.P73628@is.park.rambler.ru> <20041229064721.GA21602@xor.obsecurity.org> <20041229101325.R73628@is.park.rambler.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: freebsd-stable@freebsd.org cc: Kris Kennaway Subject: Re: icc8 failed on 4.10: Illegal instruction X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Dec 2004 07:31:31 -0000 On Wed, 29 Dec 2004, Igor Sysoev wrote: > (gdb) disassemble $eip > ... > 0x80b13d3 <__intel_proc_init_ftzdaz+75>: mov 0x2c(%esp,1),%esi > 0x80b13d7 <__intel_proc_init_ftzdaz+79>: stmxcsr (%esp,1) > 0x80b13db <__intel_proc_init_ftzdaz+83>: mov (%esp,1),%eax > ... > (gdb) > > Strange, the code in __intel_proc_init_ftzdaz looks like the right code. > Right now I can not say from what extention "stmxcsr" come from. > Here is the features from dmesg: > Features=0xbfebfbff MOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> Google seems to indicate it's an SSE instruction. Do you have 'options CPU_ENABLE_SSE' in your kernel config? -- Tod McQuillin