From owner-freebsd-amd64@FreeBSD.ORG Sun Jan 8 11:30:14 2012 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1EE91106566B for ; Sun, 8 Jan 2012 11:30:14 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E7EA48FC0A for ; Sun, 8 Jan 2012 11:30:13 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q08BUDqK099334 for ; Sun, 8 Jan 2012 11:30:13 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q08BUDvk099331; Sun, 8 Jan 2012 11:30:13 GMT (envelope-from gnats) Date: Sun, 8 Jan 2012 11:30:13 GMT Message-Id: <201201081130.q08BUDvk099331@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: umage X-Mailman-Approved-At: Sun, 08 Jan 2012 11:46:50 +0000 Cc: Subject: Re: amd64/160561: no C-states on atom D525 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: umage List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jan 2012 11:30:14 -0000 The following reply was made to PR amd64/160561; it has been noted by GNATS. From: umage To: bug-followup@FreeBSD.org, theultramage@gmail.com Cc: Subject: Re: amd64/160561: no C-states on atom D525 Date: Sun, 08 Jan 2012 12:05:42 +0100 A freebsd user with an identical issue pointed me at http://download.intel.com/embedded/processors/prodbrief/323288.pdf which lists various atom processors and their "C-states supported". Turns out D525 has no C-state power management, so what we encountered was not a bug, but an intentional (but not advertised) hardware 'feature'. From owner-freebsd-amd64@FreeBSD.ORG Sun Jan 8 12:17:19 2012 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6E141106568A; Sun, 8 Jan 2012 12:17:19 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 082E38FC0A; Sun, 8 Jan 2012 12:17:19 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q08CHI78048149; Sun, 8 Jan 2012 12:17:18 GMT (envelope-from avg@freefall.freebsd.org) Received: (from avg@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q08CHIQm048144; Sun, 8 Jan 2012 12:17:18 GMT (envelope-from avg) Date: Sun, 8 Jan 2012 12:17:18 GMT Message-Id: <201201081217.q08CHIQm048144@freefall.freebsd.org> To: theultramage@gmail.com, avg@FreeBSD.org, freebsd-amd64@FreeBSD.org From: avg@FreeBSD.org X-Mailman-Approved-At: Sun, 08 Jan 2012 12:25:07 +0000 Cc: Subject: Re: amd64/160561: no C-states on atom D525 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jan 2012 12:17:19 -0000 Synopsis: no C-states on atom D525 State-Changed-From-To: open->closed State-Changed-By: avg State-Changed-When: Sun Jan 8 12:16:43 UTC 2012 State-Changed-Why: Per the submitter this is not a FreeBSD problem. http://www.freebsd.org/cgi/query-pr.cgi?pr=160561 From owner-freebsd-amd64@FreeBSD.ORG Sun Jan 8 16:41:36 2012 Return-Path: Delivered-To: amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 44C3D106566B; Sun, 8 Jan 2012 16:41:36 +0000 (UTC) (envelope-from lists@yamagi.org) Received: from mail.yamagi.org (unknown [IPv6:2a01:4f8:121:2102:1::7]) by mx1.freebsd.org (Postfix) with ESMTP id CE0F58FC0A; Sun, 8 Jan 2012 16:41:35 +0000 (UTC) Received: from happy.home.yamagi.org (g224129135.adsl.alicedsl.de [92.224.129.135]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yamagi.org (Postfix) with ESMTPSA id 1FE951666334; Sun, 8 Jan 2012 17:41:33 +0100 (CET) Date: Sun, 8 Jan 2012 17:41:12 +0100 From: Yamagi Burmeister To: kostikbel@gmail.com Message-Id: <20120108174112.50e030ba.lists@yamagi.org> In-Reply-To: <20120102063700.GF50300@deviant.kiev.zoral.com.ua> References: <20111226220756.GR50300@deviant.kiev.zoral.com.ua> <20120102063700.GF50300@deviant.kiev.zoral.com.ua> X-Mailer: Sylpheed 3.1.2 (GTK+ 2.24.6; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="PGP-SHA1"; boundary="Signature=_Sun__8_Jan_2012_17_41_12_+0100_kuU+DV/Jqkt+Aq8r" X-Mailman-Approved-At: Sun, 08 Jan 2012 17:17:21 +0000 Cc: amd64@freebsd.org, arch@freebsd.org, sparc64@freebsd.org Subject: Re: AVX X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jan 2012 16:41:36 -0000 --Signature=_Sun__8_Jan_2012_17_41_12_+0100_kuU+DV/Jqkt+Aq8r Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, I've tested your patch on a Core2Duo with XSAVE but (of course) without AVX on 10-CURRENT as of today (r229812): CPU: Intel(R) Core(TM)2 Duo CPU T6670 @ 2.20GHz (2194.55-MHz K8-class CPU) Origin =3D "GenuineIntel" Id =3D 0x1067a Family =3D 6 Model =3D 17 Stepping =3D 10 Features=3D0xbfebfbff Features2=3D0x408e3bd AMD Features=3D0x20100800 AMD Features2=3D0x1=20 Everything's fine: - System is booting without a problem - All applications are working - AVX applications are still failing with SIGILL But there's one problem: While a shutdown (shutdown -p now) is always successfull a reboot (shutdown -r now) and suspend (zzz) are resulting=20 in a double panic. The first panic is a "Fatal trap 9: general protection fault while in kernel mode" on "cpuid =3D 1; apic id =3D 01". The process is always "idle: cpu1". The second panic is also "Fatal trap 9: general protection fault while in kernel mode" but with "cpuid =3D 0; apic id =3D 00". The process is always "init".=20 Since it's a dual core cpu, one panic for each processor core?=20 I'm unable to get a core dump and ddb is unresponsive to any keyboard input. A serial console is unavailable, since it's a laptop... Nevertheless I've uploaded screenshots of both panics to: =20 http://deponie.yamagi.org/freebsd/debug/avx=20 On Mon, 2 Jan 2012 08:37:00 +0200 Kostik Belousov wrote: > The patch > http://people.freebsd.org/~kib/misc/avx.2.patch > is the commit candidate. Compared with avx.1.patch, it includes > several bugfixes, some move of code around, and finishes the > implementation of getcontextx(3) for non-x86 architectures. >=20 > Please note that variant of getcontextx() is required for deferred > signal delivery from libthr. This is the reason for Cc:ing sparc64@, > could somebody test the patch on this architecture ? I used the > http://people.freebsd.org/~kib/misc/defer_sig.c to test deferred > delivery on amd64. >=20 > Another missed testing point is machines capable of XSAVE but lacking > AVX extensions. I think most Core2 fall into this category, but my Core2 > machine is disassembled. Could anybody test the patch on non-SandyBridge > machine having XSAVE support ? You can check the capability using > ports/sysutils/x86info or looking at the early boot Features2 line, > which shall contain the XSAVE. --=20 Homepage: www.yamagi.org XMPP: yamagi@yamagi.org GnuPG/GPG: 0xEFBCCBCB --Signature=_Sun__8_Jan_2012_17_41_12_+0100_kuU+DV/Jqkt+Aq8r Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAk8JxzwACgkQWTjlg++8y8t4jgCfWd8oyl3al8qrCbC2A5ZbiA7U 24UAnRQJoOVK7JWDzrXpCBGKJ6BnrNMn =kXS0 -----END PGP SIGNATURE----- --Signature=_Sun__8_Jan_2012_17_41_12_+0100_kuU+DV/Jqkt+Aq8r-- From owner-freebsd-amd64@FreeBSD.ORG Sun Jan 8 19:59:18 2012 Return-Path: Delivered-To: amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E7C3C1065675; Sun, 8 Jan 2012 19:59:17 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id 667608FC1A; Sun, 8 Jan 2012 19:59:16 +0000 (UTC) Received: from skuns.kiev.zoral.com.ua (localhost [127.0.0.1]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id q08JxDJY083633 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 8 Jan 2012 21:59:13 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.5/8.14.5) with ESMTP id q08JxDfc047052; Sun, 8 Jan 2012 21:59:13 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.5/8.14.5/Submit) id q08JxDvF047051; Sun, 8 Jan 2012 21:59:13 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 8 Jan 2012 21:59:13 +0200 From: Kostik Belousov To: Yamagi Burmeister Message-ID: <20120108195913.GI31224@deviant.kiev.zoral.com.ua> References: <20111226220756.GR50300@deviant.kiev.zoral.com.ua> <20120102063700.GF50300@deviant.kiev.zoral.com.ua> <20120108174112.50e030ba.lists@yamagi.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+OcHDfVcPO70+1iC" Content-Disposition: inline In-Reply-To: <20120108174112.50e030ba.lists@yamagi.org> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-3.9 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: amd64@freebsd.org, arch@freebsd.org Subject: Re: AVX X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jan 2012 19:59:18 -0000 --+OcHDfVcPO70+1iC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jan 08, 2012 at 05:41:12PM +0100, Yamagi Burmeister wrote: > Hi, > I've tested your patch on a Core2Duo with XSAVE but (of course) without > AVX on 10-CURRENT as of today (r229812): >=20 > CPU: Intel(R) Core(TM)2 Duo CPU T6670 @ 2.20GHz (2194.55-MHz > K8-class CPU) Origin =3D "GenuineIntel" Id =3D 0x1067a Family =3D 6 Mo= del > =3D 17 Stepping =3D 10 > Features=3D0xbfebfbff MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > Features2=3D0x408e3bd PDCM,SSE4.1,XSAVE> > AMD Features=3D0x20100800 AMD Features2=3D0x1=20 Is this Features excerpt from the patched kernel, or from pristine svn sources ? If the later, please show me the Features from the patched kernel. >=20 > Everything's fine: > - System is booting without a problem > - All applications are working > - AVX applications are still failing with SIGILL >=20 > But there's one problem: While a shutdown (shutdown -p now) is always > successfull a reboot (shutdown -r now) and suspend (zzz) are resulting=20 > in a double panic. The first panic is a "Fatal trap 9: general > protection fault while in kernel mode" on "cpuid =3D 1; apic id =3D 01". > The process is always "idle: cpu1". >=20 > The second panic is also "Fatal trap 9: general protection fault while > in kernel mode" but with "cpuid =3D 0; apic id =3D 00". The process is > always "init".=20 >=20 > Since it's a dual core cpu, one panic for each processor core?=20 >=20 > I'm unable to get a core dump and ddb is unresponsive to any keyboard > input. A serial console is unavailable, since it's a laptop... > Nevertheless I've uploaded screenshots of both panics to: > =20 > http://deponie.yamagi.org/freebsd/debug/avx=20 I thought that I correctly handled savectx, but apparently I did not. The issue for sleep enter could be fixed by the avx.4.patch, I am not sure about shutdown -r panic. http://people.freebsd.org/~kib/misc/avx.4.patch --+OcHDfVcPO70+1iC Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk8J9ZEACgkQC3+MBN1Mb4hCkACfRfaVp2kkmdloEwBMrrxK6wms QCcAoJBGCqQasa9UV9hZbSTAxS4mHVnv =oOp+ -----END PGP SIGNATURE----- --+OcHDfVcPO70+1iC-- From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 9 00:10:12 2012 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1928F1065680 for ; Mon, 9 Jan 2012 00:10:12 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E6D3F8FC2A for ; Mon, 9 Jan 2012 00:10:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q090ABC1003022 for ; Mon, 9 Jan 2012 00:10:11 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q090ABOE003021; Mon, 9 Jan 2012 00:10:11 GMT (envelope-from gnats) Resent-Date: Mon, 9 Jan 2012 00:10:11 GMT Resent-Message-Id: <201201090010.q090ABOE003021@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-amd64@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Devin Teske Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4BCED1065670 for ; Mon, 9 Jan 2012 00:09:38 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from red.freebsd.org (red.freebsd.org [IPv6:2001:4f8:fff6::22]) by mx1.freebsd.org (Postfix) with ESMTP id 1CCA98FC17 for ; Mon, 9 Jan 2012 00:09:38 +0000 (UTC) Received: from red.freebsd.org (localhost [127.0.0.1]) by red.freebsd.org (8.14.4/8.14.4) with ESMTP id q0909bAZ056287 for ; Mon, 9 Jan 2012 00:09:37 GMT (envelope-from nobody@red.freebsd.org) Received: (from nobody@localhost) by red.freebsd.org (8.14.4/8.14.4/Submit) id q0909bf7056286; Mon, 9 Jan 2012 00:09:37 GMT (envelope-from nobody) Message-Id: <201201090009.q0909bf7056286@red.freebsd.org> Date: Mon, 9 Jan 2012 00:09:37 GMT From: Devin Teske To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: amd64/163938: [PATCH] Fix SVN r228985 regression X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jan 2012 00:10:12 -0000 >Number: 163938 >Category: amd64 >Synopsis: [PATCH] Fix SVN r228985 regression >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Jan 09 00:10:11 UTC 2012 >Closed-Date: >Last-Modified: >Originator: Devin Teske >Release: 9.0-RELEASE >Organization: FIS Global, Inc. >Environment: FreeBSD scribe.vicor.com 9.0-RELEASE FreeSBD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 root@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 >Description: If booting from the interactive loader(8) prompt when beastie_disable="YES" is set in loader.conf(5), it causes a spurious warning on the console when booting the kernel. This spurious warning has caused some to be concerned, though they need not be. The warning is only shown when executing "boot" from the _interactive_ loader(8) prompt and does not cause any problems (boot continues to succeed). The attached patch gets rid of this warning for those that (a) set beastie_disable="YES" in loader.conf(5) and (b) commonly drop to the interactive loader(8) prompt to execute "boot" or "boot -s" (for example). >How-To-Repeat: First, make sure that SVN rev 228985 (the revision that introduced this spurious warning) is applied to the system. Add beastie_disable="YES" to loader.conf(5). Reboot your system and as your system is booting (after the kernel has been loaded [but not-yet executed]), escape the autoboot 10-second delay by pressing the SPACE bar. Then, at the "ok" prompt, type "boot". Before the kernel is executed, the warning "menu-unset not found" appears. However, your system will continue to boot. >Fix: The attached patch modifies sys/boot/forth/loader.4th to check the beastie_disable variable before attempting to evaluate the "menu-unset" function. Getting rid of the warning (which is merely a by-product of a failed catch-throw statement only when executing interactively with the loader) will go far to eliminate people's concerns as well as simply clean up the boot to prevent spurious warnings. Patch attached with submission follows: --- sys/boot/forth/loader.4th.orig Thu Dec 29 22:24:59 2011 +++ sys/boot/forth/loader.4th Sun Jan 8 15:05:46 2012 @@ -44,6 +44,14 @@ only forth also support-functions also builtins definitions : try-menu-unset + s" beastie_disable" getenv + dup -1 <> if + s" YES" compare-insensitive 0= if + exit + then + else + drop + then s" menu-unset" ['] evaluate catch if 2drop >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 9 00:28:49 2012 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F263510656DF; Mon, 9 Jan 2012 00:28:49 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id C4F078FC13; Mon, 9 Jan 2012 00:28:49 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q090SnWx021198; Mon, 9 Jan 2012 00:28:49 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q090SnTA021194; Mon, 9 Jan 2012 00:28:49 GMT (envelope-from linimon) Date: Mon, 9 Jan 2012 00:28:49 GMT Message-Id: <201201090028.q090SnTA021194@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-amd64@FreeBSD.org, pluknet@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/163938: [PATCH] Fix SVN r228985 regression X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jan 2012 00:28:50 -0000 Synopsis: [PATCH] Fix SVN r228985 regression Responsible-Changed-From-To: freebsd-amd64->pluknet Responsible-Changed-By: linimon Responsible-Changed-When: Mon Jan 9 00:28:18 UTC 2012 Responsible-Changed-Why: Over to committer of revision in question. http://www.freebsd.org/cgi/query-pr.cgi?pr=163938 From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 9 11:06:58 2012 Return-Path: Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B164A106566C for ; Mon, 9 Jan 2012 11:06:58 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 9EF3D8FC14 for ; Mon, 9 Jan 2012 11:06:58 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q09B6wr2042101 for ; Mon, 9 Jan 2012 11:06:58 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q09B6wwF042099 for freebsd-amd64@FreeBSD.org; Mon, 9 Jan 2012 11:06:58 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 9 Jan 2012 11:06:58 GMT Message-Id: <201201091106.q09B6wwF042099@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-amd64@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-amd64@FreeBSD.org X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jan 2012 11:06:58 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/163736 amd64 Freebsd 8.2 with MPD5 and about 100 PPPoE clients pani o amd64/163710 amd64 setjump in userboot.so causes stack corruption o amd64/163625 amd64 Install problems of RC3 amd64 on ASRock N68 GE3 UCC o amd64/163568 amd64 hard drive naming o amd64/163285 amd64 when installing gnome2-lite not all dependent packages o amd64/163284 amd64 print manager failed to install correctly o amd64/163114 amd64 no boot on Via Nanao netbook Samsung NC20 o amd64/163092 amd64 FreeBSD 9.0-RC2 fails to boot from raid-z2 if AHCI is o amd64/163048 amd64 normal user cant mount ntfs-3g o amd64/162936 amd64 fails boot and destabilizes other OSes on FreeBSD 9 RC o amd64/162489 amd64 After some time X blanks the screen and does not respo o amd64/162314 amd64 not able to install FreeBSD-8.2-RELEASE-amd64-dvd1 as o amd64/162219 amd64 [REGRESSION] In KDE 4.7.2 cant enable OpenGL,in 4.6.5 o amd64/162170 amd64 Unable to install due to freeze at "run_interrupt_driv o amd64/161974 amd64 FreeBSD 9 new installer installs succesful, renders ma o kern/160833 amd64 Keyboard USB doesn't work o amd64/157386 amd64 [powerd] Enabling powerd(8) with default settings on I o amd64/156106 amd64 [boot] boot0 fails to start o amd64/155135 amd64 [boot] Does Not Boot On a Very Standard Hardware o amd64/154957 amd64 [boot] Install boot CD won't boot up - keeps rebooting o amd64/154629 amd64 [panic] Fatal trap 9: general protection fault while i o amd64/153935 amd64 [hang] system hangs while trying to do 'shutdown -h no o amd64/153831 amd64 [boot] CD bootloader won't on Tyan s2912G2nr o amd64/153496 amd64 [hyper-v] [install] Install on Hyper-V leaves corrupt o amd64/153372 amd64 [panic] kernel panic o amd64/153175 amd64 [amd64] Kernel Panic on only FreeBSD 8 amd64 o amd64/152874 amd64 [install] 8.1 install fails where 7.3 works due to lac o amd64/152430 amd64 [boot] HP ProLiant Microserver n36l cannot boot into i f amd64/151385 amd64 [boot] Installation hangs on MacBook o amd64/145991 amd64 [NOTES] [patch] Add a requires line to /sys/amd64/conf o amd64/144405 amd64 [build] [patch] include /usr/obj/lib32 in cleanworld t s amd64/143173 amd64 [ata] Promise FastTrack TX4 + SATA DVD, installer can' p amd64/141413 amd64 [hang] Tyan 2881 m3289 SMDC freeze f amd64/140715 amd64 [boot] Dell M600 Blade fails to boot 7.2+ 64 bit f amd64/139998 amd64 [panic][net] 7.2 amd64 panic in rtrequest1_fib f amd64/139924 amd64 [boot] cd or dvd not load o amd64/137942 amd64 [pci] 8.0-BETA2 having problems with Asus M2N-SLI-delu f amd64/135265 amd64 [mpt] Boot from install cd hangs on HP DL160 G5 with L f amd64/133977 amd64 [panic] [ffs] "panic: ffs_blkfree: freeing free block" f amd64/133701 amd64 Recompiling the kernel with k8temp or smbios break GEO f amd64/132574 amd64 [boot] [hang] Freeze on bootstrap loader (CD) using AT f amd64/131456 amd64 [acpi] [ata] ACPI & ATA problems f amd64/130368 amd64 [hang] Switching from xorg to console locks up compute f amd64/129889 amd64 [boot] [hang] The booting process stops at the line mo f amd64/129315 amd64 [em] amd64 motherboard: Intel DG965WH motherboard comp o amd64/127640 amd64 [amd64] gcc(1) will not build shared libraries with -f f amd64/125002 amd64 [install] amd64, SATA hard disks not detected f amd64/124432 amd64 [panic] 7.0-STABLE panic: invalbuf: dirty bufs f amd64/122549 amd64 7.0-RELEASE-amd64-bootonly.iso doesn't work w/ serial f amd64/120202 amd64 [amd64] [patch] [panic] kernel panic at start_all_aps, o amd64/115194 amd64 LCD screen remains blank after Dell XPS M1210 lid is c f amd64/91405 amd64 [asr] [panic] Kernel panic caused by asr on 6.0-amd64 52 problems total. From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 9 09:37:57 2012 Return-Path: Delivered-To: amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3E9A4106566C; Mon, 9 Jan 2012 09:37:57 +0000 (UTC) (envelope-from lists@yamagi.org) Received: from mail.yamagi.org (unknown [IPv6:2a01:4f8:121:2102:1::7]) by mx1.freebsd.org (Postfix) with ESMTP id CBF288FC0A; Mon, 9 Jan 2012 09:37:56 +0000 (UTC) Received: from happy.home.yamagi.org (f054056137.adsl.alicedsl.de [78.54.56.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yamagi.org (Postfix) with ESMTPSA id 7C1701666334; Mon, 9 Jan 2012 10:37:54 +0100 (CET) Date: Mon, 9 Jan 2012 10:37:47 +0100 From: Yamagi Burmeister To: kostikbel@gmail.com Message-Id: <20120109103747.578d4e44.lists@yamagi.org> In-Reply-To: <20120108195913.GI31224@deviant.kiev.zoral.com.ua> References: <20111226220756.GR50300@deviant.kiev.zoral.com.ua> <20120102063700.GF50300@deviant.kiev.zoral.com.ua> <20120108174112.50e030ba.lists@yamagi.org> <20120108195913.GI31224@deviant.kiev.zoral.com.ua> X-Mailer: Sylpheed 3.1.2 (GTK+ 2.24.6; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="PGP-SHA1"; boundary="Signature=_Mon__9_Jan_2012_10_37_47_+0100_HicVJVGVxC0j/NuV" X-Mailman-Approved-At: Mon, 09 Jan 2012 11:56:42 +0000 Cc: amd64@freebsd.org, arch@freebsd.org Subject: Re: AVX X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jan 2012 09:37:57 -0000 --Signature=_Mon__9_Jan_2012_10_37_47_+0100_HicVJVGVxC0j/NuV Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: quoted-printable First, thank you for working on AVX, it's much appreciated. On Sun, 8 Jan 2012 21:59:13 +0200 Kostik Belousov wrote: > > CPU: Intel(R) Core(TM)2 Duo CPU T6670 @ 2.20GHz (2194.55-MHz > > K8-class CPU) Origin =3D "GenuineIntel" Id =3D 0x1067a Family =3D 6 = Model > > =3D 17 Stepping =3D 10 > > Features=3D0xbfebfbff > MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > > Features2=3D0x408e3bd > PDCM,SSE4.1,XSAVE> > > AMD Features=3D0x20100800 AMD Features2=3D0x1=20 > Is this Features excerpt from the patched kernel, or from pristine svn > sources ? If the later, please show me the Features from the patched > kernel. That was the output of the patched kernel. > I thought that I correctly handled savectx, but apparently I did not. > The issue for sleep enter could be fixed by the avx.4.patch, I am not > sure about shutdown -r panic. >=20 > http://people.freebsd.org/~kib/misc/avx.4.patch Both panics are gone. The system goes into suspend just fine and even resumes. And no more panics at reboot. --=20 Homepage: www.yamagi.org XMPP: yamagi@yamagi.org GnuPG/GPG: 0xEFBCCBCB --Signature=_Mon__9_Jan_2012_10_37_47_+0100_HicVJVGVxC0j/NuV Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAk8KtXIACgkQWTjlg++8y8vr0wCgq2Ou7DqWxfGAPqOU5psR0flm o3oAoJaZygWcC4WJQAKdCgYiDYnzpZaI =6Q6W -----END PGP SIGNATURE----- --Signature=_Mon__9_Jan_2012_10_37_47_+0100_HicVJVGVxC0j/NuV-- From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 9 17:20:10 2012 Return-Path: Delivered-To: amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7F708106564A; Mon, 9 Jan 2012 17:20:10 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-legacy.sentex.ca (freebsd-legacy.sentex.ca [IPv6:2607:f3e0:0:3::6502:9a]) by mx1.freebsd.org (Postfix) with ESMTP id 40C838FC19; Mon, 9 Jan 2012 17:20:10 +0000 (UTC) Received: from freebsd-legacy.sentex.ca (localhost [127.0.0.1]) by freebsd-legacy.sentex.ca (8.14.5/8.14.5) with ESMTP id q09HK3Kw076183; Mon, 9 Jan 2012 17:20:03 GMT (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-legacy.sentex.ca (8.14.5/8.14.5/Submit) id q09HK3vJ076182; Mon, 9 Jan 2012 17:20:03 GMT (envelope-from tinderbox@freebsd.org) Date: Mon, 9 Jan 2012 17:20:03 GMT Message-Id: <201201091720.q09HK3vJ076182@freebsd-legacy.sentex.ca> X-Authentication-Warning: freebsd-legacy.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Cc: Subject: [releng_8 tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jan 2012 17:20:10 -0000 TB --- 2012-01-09 14:44:10 - tinderbox 2.8 running on freebsd-legacy.sentex.ca TB --- 2012-01-09 14:44:10 - starting RELENG_8 tinderbox run for amd64/amd64 TB --- 2012-01-09 14:44:10 - cleaning the object tree TB --- 2012-01-09 14:44:51 - cvsupping the source tree TB --- 2012-01-09 14:44:51 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca -s /usr/home/tinderbox/RELENG_8/amd64/amd64/supfile TB --- 2012-01-09 14:44:58 - building world TB --- 2012-01-09 14:44:58 - CROSS_BUILD_TESTING=YES TB --- 2012-01-09 14:44:58 - MAKEOBJDIRPREFIX=/obj TB --- 2012-01-09 14:44:58 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-01-09 14:44:58 - SRCCONF=/dev/null TB --- 2012-01-09 14:44:58 - TARGET=amd64 TB --- 2012-01-09 14:44:58 - TARGET_ARCH=amd64 TB --- 2012-01-09 14:44:58 - TZ=UTC TB --- 2012-01-09 14:44:58 - __MAKE_CONF=/dev/null TB --- 2012-01-09 14:44:58 - cd /src TB --- 2012-01-09 14:44:58 - /usr/bin/make -B buildworld >>> World build started on Mon Jan 9 14:45:02 UTC 2012 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> stage 5.1: building 32 bit shim libraries >>> World build completed on Mon Jan 9 16:58:53 UTC 2012 TB --- 2012-01-09 16:58:53 - generating LINT kernel config TB --- 2012-01-09 16:58:53 - cd /src/sys/amd64/conf TB --- 2012-01-09 16:58:53 - /usr/bin/make -B LINT TB --- 2012-01-09 16:58:53 - cd /src/sys/amd64/conf TB --- 2012-01-09 16:58:53 - /usr/sbin/config -m LINT TB --- 2012-01-09 16:58:53 - building LINT kernel TB --- 2012-01-09 16:58:53 - CROSS_BUILD_TESTING=YES TB --- 2012-01-09 16:58:53 - MAKEOBJDIRPREFIX=/obj TB --- 2012-01-09 16:58:53 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-01-09 16:58:53 - SRCCONF=/dev/null TB --- 2012-01-09 16:58:53 - TARGET=amd64 TB --- 2012-01-09 16:58:53 - TARGET_ARCH=amd64 TB --- 2012-01-09 16:58:53 - TZ=UTC TB --- 2012-01-09 16:58:53 - __MAKE_CONF=/dev/null TB --- 2012-01-09 16:58:53 - cd /src TB --- 2012-01-09 16:58:53 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Jan 9 16:58:53 UTC 2012 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue vnode_if.c :> hack.c cc -shared -nostdlib hack.c -o hack.So rm -f hack.c MAKE=/usr/bin/make sh /src/sys/conf/newvers.sh LINT cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue vers.c linking kernel nfs_nfsdsubs.o(.data+0x0): undefined reference to `sysctl__vfs_nfsd_children' *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-01-09 17:20:03 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-01-09 17:20:03 - ERROR: failed to build LINT kernel TB --- 2012-01-09 17:20:03 - 7001.13 user 1282.68 system 9352.52 real http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8-amd64-amd64.full From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 9 20:22:20 2012 Return-Path: Delivered-To: amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E26F51065672; Mon, 9 Jan 2012 20:22:19 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id 6204A8FC0C; Mon, 9 Jan 2012 20:22:18 +0000 (UTC) Received: from skuns.kiev.zoral.com.ua (localhost [127.0.0.1]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id q09KMFNP059559 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 9 Jan 2012 22:22:15 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.5/8.14.5) with ESMTP id q09KMFR3054492; Mon, 9 Jan 2012 22:22:15 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.5/8.14.5/Submit) id q09KMEgo054491; Mon, 9 Jan 2012 22:22:14 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 9 Jan 2012 22:22:14 +0200 From: Kostik Belousov To: Yamagi Burmeister Message-ID: <20120109202214.GZ31224@deviant.kiev.zoral.com.ua> References: <20111226220756.GR50300@deviant.kiev.zoral.com.ua> <20120102063700.GF50300@deviant.kiev.zoral.com.ua> <20120108174112.50e030ba.lists@yamagi.org> <20120108195913.GI31224@deviant.kiev.zoral.com.ua> <20120109103747.578d4e44.lists@yamagi.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9C8JZALFROMdO0HE" Content-Disposition: inline In-Reply-To: <20120109103747.578d4e44.lists@yamagi.org> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-3.9 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: amd64@freebsd.org, arch@freebsd.org, marius@freebsd.org, flo@freebsd.org Subject: Re: AVX X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jan 2012 20:22:20 -0000 --9C8JZALFROMdO0HE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jan 09, 2012 at 10:37:47AM +0100, Yamagi Burmeister wrote: > First, thank you for working on AVX, it's much appreciated. >=20 > On Sun, 8 Jan 2012 21:59:13 +0200 > Kostik Belousov wrote: >=20 > > > CPU: Intel(R) Core(TM)2 Duo CPU T6670 @ 2.20GHz (2194.55-MHz > > > K8-class CPU) Origin =3D "GenuineIntel" Id =3D 0x1067a Family =3D 6= Model > > > =3D 17 Stepping =3D 10 > > > Features=3D0xbfebfbff > > MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > > > Features2=3D0x408e3bd > > PDCM,SSE4.1,XSAVE> > > > AMD Features=3D0x20100800 AMD Features2=3D0x1=20 > > Is this Features excerpt from the patched kernel, or from pristine svn > > sources ? If the later, please show me the Features from the patched > > kernel. >=20 > That was the output of the patched kernel. I see. The issue was that cpu_feature2, which is decoded to print the Features2 line, is retrieved much earlier then XCR0 is updated by fpu initialization code. I added a cludge to reload cpu_feature2 if XSAVE was indeed enabled. So now you should see OSXSAVE reported if XSAVE is indeed enabled. >=20 > > I thought that I correctly handled savectx, but apparently I did not. > > The issue for sleep enter could be fixed by the avx.4.patch, I am not > > sure about shutdown -r panic. > >=20 > > http://people.freebsd.org/~kib/misc/avx.4.patch >=20 > Both panics are gone. The system goes into suspend just fine and even > resumes. And no more panics at reboot. Very good, thank you for testing. I decided to avoid use of __fillcontextx() for !x86 architectures for now, since nobody seems to know what happens on sparc64. Florian, can you, please, retest the defer_sig to see if it works now ? I hope that this is commit candidate: http://people.freebsd.org/~kib/misc/avx.5.patch --9C8JZALFROMdO0HE Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk8LTHYACgkQC3+MBN1Mb4jcFgCeL5DpuUjELfEVHpjT3IS9h3VE hC4AoM/xGLzjJD04zenoDKCWjlYwFLCy =++UU -----END PGP SIGNATURE----- --9C8JZALFROMdO0HE-- From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 10 09:54:16 2012 Return-Path: Delivered-To: amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 94BCB106564A; Tue, 10 Jan 2012 09:54:16 +0000 (UTC) (envelope-from lists@yamagi.org) Received: from mail.yamagi.org (unknown [IPv6:2a01:4f8:121:2102:1::7]) by mx1.freebsd.org (Postfix) with ESMTP id 2A4868FC12; Tue, 10 Jan 2012 09:54:15 +0000 (UTC) Received: from happy.home.yamagi.org (g231180128.adsl.alicedsl.de [92.231.180.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yamagi.org (Postfix) with ESMTPSA id 6F6541666334; Tue, 10 Jan 2012 10:54:13 +0100 (CET) Date: Tue, 10 Jan 2012 10:54:03 +0100 From: Yamagi Burmeister To: kostikbel@gmail.com Message-Id: <20120110105403.f5a425a4.lists@yamagi.org> In-Reply-To: <20120109202214.GZ31224@deviant.kiev.zoral.com.ua> References: <20111226220756.GR50300@deviant.kiev.zoral.com.ua> <20120102063700.GF50300@deviant.kiev.zoral.com.ua> <20120108174112.50e030ba.lists@yamagi.org> <20120108195913.GI31224@deviant.kiev.zoral.com.ua> <20120109103747.578d4e44.lists@yamagi.org> <20120109202214.GZ31224@deviant.kiev.zoral.com.ua> X-Mailer: Sylpheed 3.1.2 (GTK+ 2.24.6; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="PGP-SHA1"; boundary="Signature=_Tue__10_Jan_2012_10_54_03_+0100_L.B.l=db+vIoMNs1" X-Mailman-Approved-At: Tue, 10 Jan 2012 12:12:36 +0000 Cc: amd64@freebsd.org, arch@freebsd.org, marius@freebsd.org, flo@freebsd.org Subject: Re: AVX X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jan 2012 09:54:16 -0000 --Signature=_Tue__10_Jan_2012_10_54_03_+0100_L.B.l=db+vIoMNs1 Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, 9 Jan 2012 22:22:14 +0200 Kostik Belousov wrote: > > > > CPU: Intel(R) Core(TM)2 Duo CPU T6670 @ 2.20GHz (2194.55-MHz > > > > K8-class CPU) Origin =3D "GenuineIntel" Id =3D 0x1067a Family =3D= 6 Model > > > > =3D 17 Stepping =3D 10 > > > > Features=3D0xbfebfbff > > > MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,P= BE> > > > > Features2=3D0x408e3bd > > > PDCM,SSE4.1,XSAVE> > > > > AMD Features=3D0x20100800 AMD Features2=3D0x1= =20 > > > Is this Features excerpt from the patched kernel, or from pristine svn > > > sources ? If the later, please show me the Features from the patched > > > kernel. > >=20 > > That was the output of the patched kernel. > I see. The issue was that cpu_feature2, which is decoded to print the > Features2 line, is retrieved much earlier then XCR0 is updated by > fpu initialization code. I added a cludge to reload cpu_feature2 if > XSAVE was indeed enabled. So now you should see OSXSAVE reported if > XSAVE is indeed enabled. Seems to be okay now: Features2=3D0xc08e3bd --=20 Homepage: www.yamagi.org XMPP: yamagi@yamagi.org GnuPG/GPG: 0xEFBCCBCB --Signature=_Tue__10_Jan_2012_10_54_03_+0100_L.B.l=db+vIoMNs1 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAk8MCsQACgkQWTjlg++8y8trmgCg5P3Gu9JU342L+r2YS4S8j8lF bX0AoNp3UmN9nZnTGN47QELh2c0xdHXQ =rMlb -----END PGP SIGNATURE----- --Signature=_Tue__10_Jan_2012_10_54_03_+0100_L.B.l=db+vIoMNs1-- From owner-freebsd-amd64@FreeBSD.ORG Thu Jan 12 04:40:09 2012 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B15A9106564A for ; Thu, 12 Jan 2012 04:40:09 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 741508FC18 for ; Thu, 12 Jan 2012 04:40:09 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q0C4e9qh056853 for ; Thu, 12 Jan 2012 04:40:09 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q0C4e9QF056852; Thu, 12 Jan 2012 04:40:09 GMT (envelope-from gnats) Resent-Date: Thu, 12 Jan 2012 04:40:09 GMT Resent-Message-Id: <201201120440.q0C4e9QF056852@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-amd64@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Justin Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9A6D7106564A for ; Thu, 12 Jan 2012 04:39:24 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from red.freebsd.org (red.freebsd.org [IPv6:2001:4f8:fff6::22]) by mx1.freebsd.org (Postfix) with ESMTP id 89F358FC08 for ; Thu, 12 Jan 2012 04:39:24 +0000 (UTC) Received: from red.freebsd.org (localhost [127.0.0.1]) by red.freebsd.org (8.14.4/8.14.4) with ESMTP id q0C4dOwm025921 for ; Thu, 12 Jan 2012 04:39:24 GMT (envelope-from nobody@red.freebsd.org) Received: (from nobody@localhost) by red.freebsd.org (8.14.4/8.14.4/Submit) id q0C4dOJ1025920; Thu, 12 Jan 2012 04:39:24 GMT (envelope-from nobody) Message-Id: <201201120439.q0C4dOJ1025920@red.freebsd.org> Date: Thu, 12 Jan 2012 04:39:24 GMT From: Justin To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 X-Mailman-Approved-At: Thu, 12 Jan 2012 11:26:47 +0000 Cc: Subject: amd64/164036: Moused fails on 9_0_RELENG X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jan 2012 04:40:09 -0000 >Number: 164036 >Category: amd64 >Synopsis: Moused fails on 9_0_RELENG >Confidential: no >Severity: critical >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jan 12 04:40:09 UTC 2012 >Closed-Date: >Last-Modified: >Originator: Justin >Release: 9_0_RELENG-amd64 >Organization: >Environment: 9_0_RELENG_amd64 >Description: My logitech PS/2 mouse doesn't get detected. verbose dmesg - http://paste.pocoo.org/show/532596 /boot/device.hints - http://paste.pocoo.org/show/532599 KERNCONF - http://paste.pocoo.org/show/532667/ I've tried using various parameters such as "debug.acpi.disabled="hostres" and some in /etc/X11/xorg.conf but it didn't work. On running "moused -d -i all -p /dev/psm0" I get "moused: unable to open /dev/psm0: No such file or directory" The problem appears to be - "atkbdc0: failed to probe at port 0x60 on isa0" >How-To-Repeat: Install 9_RC3 or 9_0_RELENG and enable moused thru sysinstall. >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Thu Jan 12 12:43:43 2012 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 464631065670; Thu, 12 Jan 2012 12:43:43 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 19EF78FC08; Thu, 12 Jan 2012 12:43:43 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) by cyrus.watson.org (Postfix) with ESMTPSA id C494C46B0D; Thu, 12 Jan 2012 07:43:42 -0500 (EST) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 4C187B90E; Thu, 12 Jan 2012 07:43:42 -0500 (EST) From: John Baldwin To: freebsd-amd64@freebsd.org Date: Thu, 12 Jan 2012 07:39:26 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p10; KDE/4.5.5; amd64; ; ) References: <201201120439.q0C4dOJ1025920@red.freebsd.org> In-Reply-To: <201201120439.q0C4dOJ1025920@red.freebsd.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201201120739.26518.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 12 Jan 2012 07:43:42 -0500 (EST) Cc: freebsd-gnats-submit@freebsd.org, Justin Subject: Re: amd64/164036: Moused fails on 9_0_RELENG X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jan 2012 12:43:43 -0000 On Wednesday, January 11, 2012 11:39:24 pm Justin wrote: > > >Number: 164036 > >Category: amd64 > >Synopsis: Moused fails on 9_0_RELENG > >Confidential: no > >Severity: critical > >Priority: medium > >Responsible: freebsd-amd64 > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Thu Jan 12 04:40:09 UTC 2012 > >Closed-Date: > >Last-Modified: > >Originator: Justin > >Release: 9_0_RELENG-amd64 > >Organization: > >Environment: > 9_0_RELENG_amd64 > >Description: > My logitech PS/2 mouse doesn't get detected. > > verbose dmesg - http://paste.pocoo.org/show/532596 > > /boot/device.hints - http://paste.pocoo.org/show/532599 > > KERNCONF - http://paste.pocoo.org/show/532667/ > > I've tried using various parameters such as "debug.acpi.disabled="hostres" and some in /etc/X11/xorg.conf but it didn't work. > > On running "moused -d -i all -p /dev/psm0" I get "moused: unable to open /dev/psm0: No such file or directory" > > The problem appears to be - > "atkbdc0: failed to probe at port 0x60 on isa0" Yes, that would be the root cause. Can you verbosely boot a kernel that doesn't have sound, many of the messages from the verbose dmesg above were lost. -- John Baldwin From owner-freebsd-amd64@FreeBSD.ORG Thu Jan 12 12:50:11 2012 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B9495106566C for ; Thu, 12 Jan 2012 12:50:11 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id A2C458FC1B for ; Thu, 12 Jan 2012 12:50:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q0CCoBD0042670 for ; Thu, 12 Jan 2012 12:50:11 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q0CCoBuN042669; Thu, 12 Jan 2012 12:50:11 GMT (envelope-from gnats) Date: Thu, 12 Jan 2012 12:50:11 GMT Message-Id: <201201121250.q0CCoBuN042669@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: John Baldwin Cc: Subject: Re: amd64/164036: Moused fails on 9_0_RELENG X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John Baldwin List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jan 2012 12:50:11 -0000 The following reply was made to PR amd64/164036; it has been noted by GNATS. From: John Baldwin To: freebsd-amd64@freebsd.org Cc: Justin , freebsd-gnats-submit@freebsd.org Subject: Re: amd64/164036: Moused fails on 9_0_RELENG Date: Thu, 12 Jan 2012 07:39:26 -0500 On Wednesday, January 11, 2012 11:39:24 pm Justin wrote: > > >Number: 164036 > >Category: amd64 > >Synopsis: Moused fails on 9_0_RELENG > >Confidential: no > >Severity: critical > >Priority: medium > >Responsible: freebsd-amd64 > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Thu Jan 12 04:40:09 UTC 2012 > >Closed-Date: > >Last-Modified: > >Originator: Justin > >Release: 9_0_RELENG-amd64 > >Organization: > >Environment: > 9_0_RELENG_amd64 > >Description: > My logitech PS/2 mouse doesn't get detected. > > verbose dmesg - http://paste.pocoo.org/show/532596 > > /boot/device.hints - http://paste.pocoo.org/show/532599 > > KERNCONF - http://paste.pocoo.org/show/532667/ > > I've tried using various parameters such as "debug.acpi.disabled="hostres" and some in /etc/X11/xorg.conf but it didn't work. > > On running "moused -d -i all -p /dev/psm0" I get "moused: unable to open /dev/psm0: No such file or directory" > > The problem appears to be - > "atkbdc0: failed to probe at port 0x60 on isa0" Yes, that would be the root cause. Can you verbosely boot a kernel that doesn't have sound, many of the messages from the verbose dmesg above were lost. -- John Baldwin From owner-freebsd-amd64@FreeBSD.ORG Thu Jan 12 15:15:00 2012 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AB75F106566B; Thu, 12 Jan 2012 15:15:00 +0000 (UTC) (envelope-from freebsd.users@gmail.com) Received: from mail-ey0-f182.google.com (mail-ey0-f182.google.com [209.85.215.182]) by mx1.freebsd.org (Postfix) with ESMTP id 121AA8FC13; Thu, 12 Jan 2012 15:14:59 +0000 (UTC) Received: by eaai12 with SMTP id i12so85952eaa.13 for ; Thu, 12 Jan 2012 07:14:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=mZB6cqdpHYWFYPdYuXM/iLyEuGsA4UAnvHRVbHMXg7s=; b=HhkFPQqV7mEHGFlbKazL/iVgQMnKqkv97HF/j9EYzSMV1PZeYAs8CqmfSXkros2B8U kdnnVEQE+IJXPfHSDRhtudEUUMOMNNNJiOex9d5Wc5XAQDBv416feF2Bn7NwCMr5nXzw e6atxrnEDSPXFhTnY+sNOYQdxq7aKDEc0/q20= MIME-Version: 1.0 Received: by 10.213.105.144 with SMTP id t16mr54531ebo.95.1326379462400; Thu, 12 Jan 2012 06:44:22 -0800 (PST) Received: by 10.213.35.207 with HTTP; Thu, 12 Jan 2012 06:44:22 -0800 (PST) In-Reply-To: <201201120739.26518.jhb@freebsd.org> References: <201201120439.q0C4dOJ1025920@red.freebsd.org> <201201120739.26518.jhb@freebsd.org> Date: Thu, 12 Jan 2012 22:44:22 +0800 Message-ID: From: dave shar To: John Baldwin Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Thu, 12 Jan 2012 16:17:56 +0000 Cc: freebsd-gnats-submit@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: amd64/164036: Moused fails on 9_0_RELENG X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jan 2012 15:15:00 -0000 On Thu, Jan 12, 2012 at 8:39 PM, John Baldwin wrote: > On Wednesday, January 11, 2012 11:39:24 pm Justin wrote: >> >> >Number: =A0 =A0 =A0 =A0 164036 >> >Category: =A0 =A0 =A0 amd64 >> >Synopsis: =A0 =A0 =A0 Moused fails on 9_0_RELENG >> >Confidential: =A0 no >> >Severity: =A0 =A0 =A0 critical >> >Priority: =A0 =A0 =A0 medium >> >Responsible: =A0 =A0freebsd-amd64 >> >State: =A0 =A0 =A0 =A0 =A0open >> >Quarter: >> >Keywords: >> >Date-Required: >> >Class: =A0 =A0 =A0 =A0 =A0sw-bug >> >Submitter-Id: =A0 current-users >> >Arrival-Date: =A0 Thu Jan 12 04:40:09 UTC 2012 >> >Closed-Date: >> >Last-Modified: >> >Originator: =A0 =A0 Justin >> >Release: =A0 =A0 =A0 =A09_0_RELENG-amd64 >> >Organization: >> >Environment: >> 9_0_RELENG_amd64 >> >Description: >> My logitech PS/2 mouse doesn't get detected. >> >> verbose dmesg - http://paste.pocoo.org/show/532596 >> >> /boot/device.hints - http://paste.pocoo.org/show/532599 >> >> KERNCONF - http://paste.pocoo.org/show/532667/ >> >> I've tried using various parameters such as "debug.acpi.disabled=3D"host= res" > and some in /etc/X11/xorg.conf but it didn't work. >> >> On running "moused -d -i all -p /dev/psm0" I get "moused: unable to open > /dev/psm0: No such file or directory" >> >> The problem appears to be - >> "atkbdc0: failed to probe at port 0x60 on > isa0" > > Yes, that would be the root cause. =A0Can you verbosely boot a kernel tha= t > doesn't have sound, many of the messages from the verbose dmesg above wer= e > lost. > > -- > John Baldwin Here is verbose boot without sound devices - http://paste.pocoo.org/show/53= 3788/ From owner-freebsd-amd64@FreeBSD.ORG Thu Jan 12 15:20:09 2012 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ADFB2106566B for ; Thu, 12 Jan 2012 15:20:09 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 94D198FC1A for ; Thu, 12 Jan 2012 15:20:09 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q0CFK9qn078976 for ; Thu, 12 Jan 2012 15:20:09 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q0CFK94A078975; Thu, 12 Jan 2012 15:20:09 GMT (envelope-from gnats) Date: Thu, 12 Jan 2012 15:20:09 GMT Message-Id: <201201121520.q0CFK94A078975@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: dave shar X-Mailman-Approved-At: Thu, 12 Jan 2012 16:56:16 +0000 Cc: Subject: Re: amd64/164036: Moused fails on 9_0_RELENG X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dave shar List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jan 2012 15:20:09 -0000 The following reply was made to PR amd64/164036; it has been noted by GNATS. From: dave shar To: John Baldwin Cc: freebsd-amd64@freebsd.org, freebsd-gnats-submit@freebsd.org Subject: Re: amd64/164036: Moused fails on 9_0_RELENG Date: Thu, 12 Jan 2012 22:44:22 +0800 On Thu, Jan 12, 2012 at 8:39 PM, John Baldwin wrote: > On Wednesday, January 11, 2012 11:39:24 pm Justin wrote: >> >> >Number: =A0 =A0 =A0 =A0 164036 >> >Category: =A0 =A0 =A0 amd64 >> >Synopsis: =A0 =A0 =A0 Moused fails on 9_0_RELENG >> >Confidential: =A0 no >> >Severity: =A0 =A0 =A0 critical >> >Priority: =A0 =A0 =A0 medium >> >Responsible: =A0 =A0freebsd-amd64 >> >State: =A0 =A0 =A0 =A0 =A0open >> >Quarter: >> >Keywords: >> >Date-Required: >> >Class: =A0 =A0 =A0 =A0 =A0sw-bug >> >Submitter-Id: =A0 current-users >> >Arrival-Date: =A0 Thu Jan 12 04:40:09 UTC 2012 >> >Closed-Date: >> >Last-Modified: >> >Originator: =A0 =A0 Justin >> >Release: =A0 =A0 =A0 =A09_0_RELENG-amd64 >> >Organization: >> >Environment: >> 9_0_RELENG_amd64 >> >Description: >> My logitech PS/2 mouse doesn't get detected. >> >> verbose dmesg - http://paste.pocoo.org/show/532596 >> >> /boot/device.hints - http://paste.pocoo.org/show/532599 >> >> KERNCONF - http://paste.pocoo.org/show/532667/ >> >> I've tried using various parameters such as "debug.acpi.disabled=3D"host= res" > and some in /etc/X11/xorg.conf but it didn't work. >> >> On running "moused -d -i all -p /dev/psm0" I get "moused: unable to open > /dev/psm0: No such file or directory" >> >> The problem appears to be - >> "atkbdc0: failed to probe at port 0x60 on > isa0" > > Yes, that would be the root cause. =A0Can you verbosely boot a kernel tha= t > doesn't have sound, many of the messages from the verbose dmesg above wer= e > lost. > > -- > John Baldwin Here is verbose boot without sound devices - http://paste.pocoo.org/show/53= 3788/ From owner-freebsd-amd64@FreeBSD.ORG Thu Jan 12 19:45:02 2012 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 999ED106564A; Thu, 12 Jan 2012 19:45:02 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 661CF8FC16; Thu, 12 Jan 2012 19:45:02 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) by cyrus.watson.org (Postfix) with ESMTPSA id 1E35646B94; Thu, 12 Jan 2012 14:45:02 -0500 (EST) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id A325CB947; Thu, 12 Jan 2012 14:45:01 -0500 (EST) From: John Baldwin To: dave shar Date: Thu, 12 Jan 2012 14:45:00 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p10; KDE/4.5.5; amd64; ; ) References: <201201120439.q0C4dOJ1025920@red.freebsd.org> <201201120739.26518.jhb@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201201121445.01133.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 12 Jan 2012 14:45:01 -0500 (EST) Cc: freebsd-gnats-submit@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: amd64/164036: Moused fails on 9_0_RELENG X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jan 2012 19:45:02 -0000 On Thursday, January 12, 2012 9:44:22 am dave shar wrote: > >> The problem appears to be - > >> "atkbdc0: failed to probe at port 0x60 on > > isa0" > > > > Yes, that would be the root cause. Can you verbosely boot a kernel that > > doesn't have sound, many of the messages from the verbose dmesg above were > > lost. > > > > -- > > John Baldwin > > Here is verbose boot without sound devices - http://paste.pocoo.org/show/533788/ Hmm, I dont' see atkbdc in there at all, however, I wonder if the fact that ACPI gives 0x60 to your PS/2 mouse device is what breaks this: psmcpnp0: port 0x60,0x64 irq 12 on acpi0 Can you provide your acpidump -d output (note, it will be large)? -- John Baldwin From owner-freebsd-amd64@FreeBSD.ORG Thu Jan 12 19:50:40 2012 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9A8751065670 for ; Thu, 12 Jan 2012 19:50:40 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 89BBA8FC16 for ; Thu, 12 Jan 2012 19:50:40 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q0CJoe2s009502 for ; Thu, 12 Jan 2012 19:50:40 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q0CJoecl009496; Thu, 12 Jan 2012 19:50:40 GMT (envelope-from gnats) Date: Thu, 12 Jan 2012 19:50:40 GMT Message-Id: <201201121950.q0CJoecl009496@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: John Baldwin Cc: Subject: Re: amd64/164036: Moused fails on 9_0_RELENG X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John Baldwin List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jan 2012 19:50:40 -0000 The following reply was made to PR amd64/164036; it has been noted by GNATS. From: John Baldwin To: dave shar Cc: freebsd-amd64@freebsd.org, freebsd-gnats-submit@freebsd.org Subject: Re: amd64/164036: Moused fails on 9_0_RELENG Date: Thu, 12 Jan 2012 14:45:00 -0500 On Thursday, January 12, 2012 9:44:22 am dave shar wrote: > >> The problem appears to be - > >> "atkbdc0: failed to probe at port 0x60 on > > isa0" > > > > Yes, that would be the root cause. Can you verbosely boot a kernel that > > doesn't have sound, many of the messages from the verbose dmesg above were > > lost. > > > > -- > > John Baldwin > > Here is verbose boot without sound devices - http://paste.pocoo.org/show/533788/ Hmm, I dont' see atkbdc in there at all, however, I wonder if the fact that ACPI gives 0x60 to your PS/2 mouse device is what breaks this: psmcpnp0: port 0x60,0x64 irq 12 on acpi0 Can you provide your acpidump -d output (note, it will be large)? -- John Baldwin From owner-freebsd-amd64@FreeBSD.ORG Fri Jan 13 13:08:05 2012 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DDC2C1065672; Fri, 13 Jan 2012 13:08:05 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id B05508FC14; Fri, 13 Jan 2012 13:08:05 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) by cyrus.watson.org (Postfix) with ESMTPSA id 6726F46B09; Fri, 13 Jan 2012 08:08:05 -0500 (EST) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id E9533B915; Fri, 13 Jan 2012 08:08:04 -0500 (EST) From: John Baldwin To: Justin Smith Date: Fri, 13 Jan 2012 08:08:03 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p10; KDE/4.5.5; amd64; ; ) References: <201201120439.q0C4dOJ1025920@red.freebsd.org> <201201121445.01133.jhb@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201201130808.03827.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Fri, 13 Jan 2012 08:08:05 -0500 (EST) Cc: freebsd-gnats-submit@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: amd64/164036: Moused fails on 9_0_RELENG X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jan 2012 13:08:05 -0000 On Thursday, January 12, 2012 9:19:32 pm Justin Smith wrote: > acpidump -d - http://paste.pocoo.org/show/534042/ Hmm, what an odd system. It has two different sets of PS/2 keyboard/mouse devices (PSKE and PSMS vs PS2K and PS2M). Still, it's not clear why neither of those worked. Can you get devinfo -vr output? -- John Baldwin From owner-freebsd-amd64@FreeBSD.ORG Fri Jan 13 13:10:13 2012 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4DA0C106564A for ; Fri, 13 Jan 2012 13:10:13 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 1E3CD8FC15 for ; Fri, 13 Jan 2012 13:10:13 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q0DDADAr082820 for ; Fri, 13 Jan 2012 13:10:13 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q0DDACSY082819; Fri, 13 Jan 2012 13:10:12 GMT (envelope-from gnats) Date: Fri, 13 Jan 2012 13:10:12 GMT Message-Id: <201201131310.q0DDACSY082819@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: John Baldwin Cc: Subject: Re: amd64/164036: Moused fails on 9_0_RELENG X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John Baldwin List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jan 2012 13:10:13 -0000 The following reply was made to PR amd64/164036; it has been noted by GNATS. From: John Baldwin To: Justin Smith Cc: freebsd-amd64@freebsd.org, freebsd-gnats-submit@freebsd.org Subject: Re: amd64/164036: Moused fails on 9_0_RELENG Date: Fri, 13 Jan 2012 08:08:03 -0500 On Thursday, January 12, 2012 9:19:32 pm Justin Smith wrote: > acpidump -d - http://paste.pocoo.org/show/534042/ Hmm, what an odd system. It has two different sets of PS/2 keyboard/mouse devices (PSKE and PSMS vs PS2K and PS2M). Still, it's not clear why neither of those worked. Can you get devinfo -vr output? -- John Baldwin From owner-freebsd-amd64@FreeBSD.ORG Fri Jan 13 15:21:40 2012 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D19D8106567C; Fri, 13 Jan 2012 15:21:40 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id A2E988FC19; Fri, 13 Jan 2012 15:21:40 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) by cyrus.watson.org (Postfix) with ESMTPSA id 5BD8C46B09; Fri, 13 Jan 2012 10:21:40 -0500 (EST) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id B06C3B967; Fri, 13 Jan 2012 10:21:39 -0500 (EST) From: John Baldwin To: Justin Smith Date: Fri, 13 Jan 2012 10:18:45 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p10; KDE/4.5.5; amd64; ; ) References: <201201120439.q0C4dOJ1025920@red.freebsd.org> <201201130808.03827.jhb@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201201131018.45939.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Fri, 13 Jan 2012 10:21:39 -0500 (EST) Cc: freebsd-gnats-submit@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: amd64/164036: Moused fails on 9_0_RELENG X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jan 2012 15:21:40 -0000 On Friday, January 13, 2012 9:20:53 am Justin Smith wrote: > Yeah, its strange for sure. But I have this issue on two different > systems with different hardware (ASUS board & BIOSTAR Board). > > devinfo -vr : http://paste.pocoo.org/show/534240/ Hmm. So the "problem" is your BIOS putting the keyboard resources on the PS/2 port. You can fix this by editing your AML and moving the IO Port resources out of _CRS for the PS2M device and moving them to the PS2K device instead. However, fixing it automatically would be a bigger pain as we would need to patch both the atkbdc and psmcpnp drivers to cooperate to move the I/O ports over. We already have a similar hack for handling IRQ 12. We should perhaps expand that further so that we have atkbdc somehow attach to both PS/2 devices and merge any resources into a single logical device. -- John Baldwin From owner-freebsd-amd64@FreeBSD.ORG Fri Jan 13 15:30:14 2012 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 342AD1065670 for ; Fri, 13 Jan 2012 15:30:14 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 1FD528FC22 for ; Fri, 13 Jan 2012 15:30:14 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q0DFUDMx010673 for ; Fri, 13 Jan 2012 15:30:14 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q0DFUD8S010670; Fri, 13 Jan 2012 15:30:13 GMT (envelope-from gnats) Date: Fri, 13 Jan 2012 15:30:13 GMT Message-Id: <201201131530.q0DFUD8S010670@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: John Baldwin Cc: Subject: Re: amd64/164036: Moused fails on 9_0_RELENG X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John Baldwin List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jan 2012 15:30:14 -0000 The following reply was made to PR amd64/164036; it has been noted by GNATS. From: John Baldwin To: Justin Smith Cc: freebsd-amd64@freebsd.org, freebsd-gnats-submit@freebsd.org Subject: Re: amd64/164036: Moused fails on 9_0_RELENG Date: Fri, 13 Jan 2012 10:18:45 -0500 On Friday, January 13, 2012 9:20:53 am Justin Smith wrote: > Yeah, its strange for sure. But I have this issue on two different > systems with different hardware (ASUS board & BIOSTAR Board). > > devinfo -vr : http://paste.pocoo.org/show/534240/ Hmm. So the "problem" is your BIOS putting the keyboard resources on the PS/2 port. You can fix this by editing your AML and moving the IO Port resources out of _CRS for the PS2M device and moving them to the PS2K device instead. However, fixing it automatically would be a bigger pain as we would need to patch both the atkbdc and psmcpnp drivers to cooperate to move the I/O ports over. We already have a similar hack for handling IRQ 12. We should perhaps expand that further so that we have atkbdc somehow attach to both PS/2 devices and merge any resources into a single logical device. -- John Baldwin From owner-freebsd-amd64@FreeBSD.ORG Fri Jan 13 16:55:30 2012 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 74D33106564A; Fri, 13 Jan 2012 16:55:30 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 4685D8FC0A; Fri, 13 Jan 2012 16:55:30 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) by cyrus.watson.org (Postfix) with ESMTPSA id DBEA846B3F; Fri, 13 Jan 2012 11:55:29 -0500 (EST) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 6AC0FB922; Fri, 13 Jan 2012 11:55:29 -0500 (EST) From: John Baldwin To: Justin Smith Date: Fri, 13 Jan 2012 11:54:36 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p10; KDE/4.5.5; amd64; ; ) References: <201201120439.q0C4dOJ1025920@red.freebsd.org> <201201131018.45939.jhb@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201201131154.36090.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Fri, 13 Jan 2012 11:55:29 -0500 (EST) Cc: freebsd-gnats-submit@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: amd64/164036: Moused fails on 9_0_RELENG X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jan 2012 16:55:30 -0000 On Friday, January 13, 2012 11:17:35 am Justin Smith wrote: > On Fri, Jan 13, 2012 at 11:18 PM, John Baldwin wrote: > > On Friday, January 13, 2012 9:20:53 am Justin Smith wrote: > >> Yeah, its strange for sure. But I have this issue on two different > >> systems with different hardware (ASUS board & BIOSTAR Board). > >> > >> devinfo -vr : http://paste.pocoo.org/show/534240/ > > > > Hmm. So the "problem" is your BIOS putting the keyboard resources on the PS/2 > > port. You can fix this by editing your AML and moving the IO Port resources > > out of _CRS for the PS2M device and moving them to the PS2K device instead. > > > > However, fixing it automatically would be a bigger pain as we would need to > > patch both the atkbdc and psmcpnp drivers to cooperate to move the I/O ports > > over. We already have a similar hack for handling IRQ 12. We should perhaps > > expand that further so that we have atkbdc somehow attach to both PS/2 devices > > and merge any resources into a single logical device. > > > > -- > > John Baldwin > > Been there done that (ASUS board AML), doesn't work. I have no > settings for PS2M to PS2K on BIOSTAR BIOS. Err, not a BIOS setting, but actually editing the AML. Assuming you edited the ASUS AML, can you show me a diff of the original and modified AML? -- John Baldwin From owner-freebsd-amd64@FreeBSD.ORG Fri Jan 13 17:00:29 2012 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 965CD106564A for ; Fri, 13 Jan 2012 17:00:29 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 410848FC13 for ; Fri, 13 Jan 2012 17:00:29 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q0DH0TOE093330 for ; Fri, 13 Jan 2012 17:00:29 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q0DH0TXv093329; Fri, 13 Jan 2012 17:00:29 GMT (envelope-from gnats) Date: Fri, 13 Jan 2012 17:00:29 GMT Message-Id: <201201131700.q0DH0TXv093329@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: John Baldwin Cc: Subject: Re: amd64/164036: Moused fails on 9_0_RELENG X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John Baldwin List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jan 2012 17:00:29 -0000 The following reply was made to PR amd64/164036; it has been noted by GNATS. From: John Baldwin To: Justin Smith Cc: freebsd-amd64@freebsd.org, freebsd-gnats-submit@freebsd.org Subject: Re: amd64/164036: Moused fails on 9_0_RELENG Date: Fri, 13 Jan 2012 11:54:36 -0500 On Friday, January 13, 2012 11:17:35 am Justin Smith wrote: > On Fri, Jan 13, 2012 at 11:18 PM, John Baldwin wrote: > > On Friday, January 13, 2012 9:20:53 am Justin Smith wrote: > >> Yeah, its strange for sure. But I have this issue on two different > >> systems with different hardware (ASUS board & BIOSTAR Board). > >> > >> devinfo -vr : http://paste.pocoo.org/show/534240/ > > > > Hmm. So the "problem" is your BIOS putting the keyboard resources on the PS/2 > > port. You can fix this by editing your AML and moving the IO Port resources > > out of _CRS for the PS2M device and moving them to the PS2K device instead. > > > > However, fixing it automatically would be a bigger pain as we would need to > > patch both the atkbdc and psmcpnp drivers to cooperate to move the I/O ports > > over. We already have a similar hack for handling IRQ 12. We should perhaps > > expand that further so that we have atkbdc somehow attach to both PS/2 devices > > and merge any resources into a single logical device. > > > > -- > > John Baldwin > > Been there done that (ASUS board AML), doesn't work. I have no > settings for PS2M to PS2K on BIOSTAR BIOS. Err, not a BIOS setting, but actually editing the AML. Assuming you edited the ASUS AML, can you show me a diff of the original and modified AML? -- John Baldwin From owner-freebsd-amd64@FreeBSD.ORG Sat Jan 14 04:01:09 2012 Return-Path: Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 70602106566C for ; Sat, 14 Jan 2012 04:01:09 +0000 (UTC) (envelope-from famd64@paz.bz) Received: from mail.qcislands.net (mail.qcislands.net [207.34.147.83]) by mx1.freebsd.org (Postfix) with ESMTP id 5433C8FC08 for ; Sat, 14 Jan 2012 04:01:09 +0000 (UTC) Received: from 100-236-53-209.qcislands.net ([209.53.236.100] helo=[192.168.1.5]) by mail.qcislands.net with esmtp (Exim 4.75) (envelope-from ) id 1RlubV-000LH7-8M; Fri, 13 Jan 2012 19:48:31 -0800 Message-ID: <4F10FB1A.2060609@paz.bz> Date: Fri, 13 Jan 2012 19:48:42 -0800 From: Jim Pazarena User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: freebsd-amd64@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-local_scan: locally submitted (100) Cc: Subject: 2 Tb limit X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jan 2012 04:01:09 -0000 Is there any way to create file systems bigger than 2Tb? I was hoping that a 64-bit OS may have this ability. I have a ProLiant rack server which I installed a 4Tb raid -before- I discovered that I couldn't exceed 2Tb. -- Jim Pazarena famd64@paz.bz From owner-freebsd-amd64@FreeBSD.ORG Sat Jan 14 04:06:57 2012 Return-Path: Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 284791065672 for ; Sat, 14 Jan 2012 04:06:57 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from noop.in-addr.com (mail.in-addr.com [IPv6:2001:470:8:162::1]) by mx1.freebsd.org (Postfix) with ESMTP id F2EB68FC16 for ; Sat, 14 Jan 2012 04:06:56 +0000 (UTC) Received: from gjp by noop.in-addr.com with local (Exim 4.77 (FreeBSD)) (envelope-from ) id 1RlutC-0008hD-Rd; Fri, 13 Jan 2012 23:06:46 -0500 Date: Fri, 13 Jan 2012 23:06:46 -0500 From: Gary Palmer To: Jim Pazarena Message-ID: <20120114040646.GA99101@in-addr.com> References: <4F10FB1A.2060609@paz.bz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4F10FB1A.2060609@paz.bz> X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on noop.in-addr.com); SAEximRunCond expanded to false Cc: freebsd-amd64@FreeBSD.org Subject: Re: 2 Tb limit X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jan 2012 04:06:57 -0000 On Fri, Jan 13, 2012 at 07:48:42PM -0800, Jim Pazarena wrote: > Is there any way to create file systems bigger than 2Tb? > I was hoping that a 64-bit OS may have this ability. > > I have a ProLiant rack server which I installed a 4Tb raid > -before- I discovered that I couldn't exceed 2Tb. FreeBSD can use filesystems many times larger than 2TiB, however I suspect the problem you are running into is with the default MBR partition table which is limited to 2TIB. Try using a GPT partition table instead. Regards, Gary From owner-freebsd-amd64@FreeBSD.ORG Sat Jan 14 04:27:01 2012 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4D0D31065673 for ; Sat, 14 Jan 2012 04:27:01 +0000 (UTC) (envelope-from freebsd@penx.com) Received: from btw.pki2.com (btw.pki2.com [IPv6:2001:470:a:6fd::2]) by mx1.freebsd.org (Postfix) with ESMTP id 1E5E18FC15 for ; Sat, 14 Jan 2012 04:27:01 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) by btw.pki2.com (8.14.5/8.14.5) with ESMTP id q0E4QshT024613; Fri, 13 Jan 2012 20:26:54 -0800 (PST) (envelope-from freebsd@penx.com) From: Dennis Glatting To: Jim Pazarena In-Reply-To: <4F10FB1A.2060609@paz.bz> References: <4F10FB1A.2060609@paz.bz> Content-Type: text/plain; charset="us-ascii" Date: Fri, 13 Jan 2012 20:08:48 -0800 Message-ID: <1326514128.19458.2.camel@btw.pki2.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-yoursite-MailScanner-Information: Dennis Glatting X-yoursite-MailScanner-ID: q0E4QshT024613 X-yoursite-MailScanner: Found to be clean X-MailScanner-From: freebsd@penx.com X-yoursite-MailScanner-Watermark: 1327120017.96202@KA2vhiGkBs3HTcEbwE+JdQ Cc: freebsd-amd64@freebsd.org Subject: Re: 2 Tb limit X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jan 2012 04:27:01 -0000 On Fri, 2012-01-13 at 19:48 -0800, Jim Pazarena wrote: > Is there any way to create file systems bigger than 2Tb? > I was hoping that a 64-bit OS may have this ability. > > I have a ProLiant rack server which I installed a 4Tb raid > -before- I discovered that I couldn't exceed 2Tb. Hmm... 12-2.5TB drives in a RAIDz ZFS volume. bd3> df -lh Filesystem Size Used Avail Capacity Mounted on /dev/gpt/disk0 916G 7.2G 835G 1% / devfs 1.0k 1.0k 0B 100% /dev disk-1 24T 1.7G 24T 0% /disk-1 disk-1/zvol 24T 53k 24T 0% /disk-1/zvol