From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 19 09:49:42 2012 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 56076106566C; Mon, 19 Mar 2012 09:49:42 +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 2944C8FC08; Mon, 19 Mar 2012 09:49:42 +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 q2J9ngaB058536; Mon, 19 Mar 2012 09:49:42 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q2J9ngoI058532; Mon, 19 Mar 2012 09:49:42 GMT (envelope-from linimon) Date: Mon, 19 Mar 2012 09:49:42 GMT Message-Id: <201203190949.q2J9ngoI058532@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-amd64@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: amd64/166229: [boot] Unable to install FreeBSD 9 on Acer Extensa 5220 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, 19 Mar 2012 09:49:42 -0000 Old Synopsis: Unable to install FreeBSD 9 on Acer Extensa 5220 New Synopsis: [boot] Unable to install FreeBSD 9 on Acer Extensa 5220 Responsible-Changed-From-To: freebsd-bugs->freebsd-amd64 Responsible-Changed-By: linimon Responsible-Changed-When: Mon Mar 19 09:49:02 UTC 2012 Responsible-Changed-Why: reassign from misc/ http://www.freebsd.org/cgi/query-pr.cgi?pr=166229 From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 19 11:07: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 B6A781065670 for ; Mon, 19 Mar 2012 11:07:05 +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 A0CC18FC0C for ; Mon, 19 Mar 2012 11:07:05 +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 q2JB75f4033508 for ; Mon, 19 Mar 2012 11:07:05 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q2JB74SI033506 for freebsd-amd64@FreeBSD.org; Mon, 19 Mar 2012 11:07:04 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 19 Mar 2012 11:07:04 GMT Message-Id: <201203191107.q2JB74SI033506@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, 19 Mar 2012 11:07:05 -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/166229 amd64 [boot] Unable to install FreeBSD 9 on Acer Extensa 522 o amd64/165850 amd64 [build] 8.3-RC1 (amd64): world doesn't build with CPUT o amd64/165845 amd64 [build] Unable to build kernel on 8.2-STABLE o amd64/165351 amd64 [boot] Error while installing or booting the freeBSD O o amd64/164773 amd64 [boot] 9.0 amd64 fails to boot on HP DL145 G3 [regress o amd64/164707 amd64 FreeBSD 9 installer does not work with IBM uefi o amd64/164643 amd64 Kernel Panic at 9.0-RELEASE o amd64/164619 amd64 when logged in as root the user and group applications o amd64/164457 amd64 [install] Can't install FreeBSD 9.0 (amd64) on HP Blad o amd64/164301 amd64 [install] 9.0 - Can't install, no DHCP lease o amd64/164136 amd64 after fresh install 8.1 release or 8.2 release the har o amd64/164116 amd64 [boot] FreeBSD 9.0-RELEASE installations mediums fails o amd64/164089 amd64 FreeBSD-9.0-RELEASE-amd64-memstick.img does not boot o amd64/164073 amd64 /etc/rc warning after booting o amd64/164036 amd64 [keyboard] Moused fails on 9_0_RELENG 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 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 o amd64/137942 amd64 [pci] 8.0-BETA2 having problems with Asus M2N-SLI-delu o amd64/127640 amd64 [amd64] gcc(1) will not build shared libraries with -f o amd64/115194 amd64 LCD screen remains blank after Dell XPS M1210 lid is c 50 problems total. From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 19 15:25:41 2012 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A21E61065674; Mon, 19 Mar 2012 15:25:41 +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 759288FC15; Mon, 19 Mar 2012 15:25:41 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) by cyrus.watson.org (Postfix) with ESMTPSA id 13DC246B3B; Mon, 19 Mar 2012 11:25:41 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 9D4C8B924; Mon, 19 Mar 2012 11:25:40 -0400 (EDT) From: John Baldwin To: freebsd-amd64@freebsd.org, freebsd-bugs@freebsd.org Date: Mon, 19 Mar 2012 08:09:34 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p10; KDE/4.5.5; amd64; ; ) References: <201203190949.q2J9ngoI058532@freefall.freebsd.org> In-Reply-To: <201203190949.q2J9ngoI058532@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201203190809.34514.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 19 Mar 2012 11:25:40 -0400 (EDT) Cc: Subject: Re: amd64/166229: [boot] Unable to install FreeBSD 9 on Acer Extensa 5220 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, 19 Mar 2012 15:25:41 -0000 On Monday, March 19, 2012 5:49:42 am linimon@freebsd.org wrote: > Old Synopsis: Unable to install FreeBSD 9 on Acer Extensa 5220 > New Synopsis: [boot] Unable to install FreeBSD 9 on Acer Extensa 5220 > > Responsible-Changed-From-To: freebsd-bugs->freebsd-amd64 > Responsible-Changed-By: linimon > Responsible-Changed-When: Mon Mar 19 09:49:02 UTC 2012 > Responsible-Changed-Why: > reassign from misc/ Can you drop into DDB and use 'ps' and possibly 'tr 0' to see what the boot is waiting on? -- John Baldwin From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 19 15:25:49 2012 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 49F39106567C for ; Mon, 19 Mar 2012 15:25:48 +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 4C9B38FC14 for ; Mon, 19 Mar 2012 15:25:48 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) by cyrus.watson.org (Postfix) with ESMTPSA id 02E7046B39; Mon, 19 Mar 2012 11:25:48 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 63A37B93E; Mon, 19 Mar 2012 11:25:47 -0400 (EDT) From: John Baldwin To: Kai Gallasch Date: Mon, 19 Mar 2012 09:42:32 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p10; KDE/4.5.5; amd64; ; ) References: <201203141040.q2EAe3Os043367@freefall.freebsd.org> <201203150933.35265.jhb@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201203190942.32374.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 19 Mar 2012 11:25:47 -0400 (EDT) Cc: freebsd-amd64@freebsd.org Subject: Re: amd64/164773: [boot] 9.0 amd64 fails to boot on HP DL145 G3 [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, 19 Mar 2012 15:25:49 -0000 On Saturday, March 17, 2012 10:54:02 am Kai Gallasch wrote: > > Am 15.03.2012 um 14:33 schrieb John Baldwin: > > > On Wednesday, March 14, 2012 6:40:03 am Kai Gallasch wrote: > >> The following reply was made to PR amd64/164773; it has been noted by GNATS. > >> > >> From: Kai Gallasch > >> To: bug-followup@FreeBSD.org, > >> jshupe@hermetek.com > >> Cc: > >> Subject: Re: amd64/164773: [boot] 9.0 amd64 fails to boot on HP DL145 G3 > > [regression] > >> Date: Wed, 14 Mar 2012 11:25:10 +0100 > >> > >> Booting the DL145 G3 with disabled ehci in GENERIC kernel changes = > >> nothing, the boot process still times out with > >> "mount waiting for: usbus1 usbus0" > > > > Hmm, if you are still able to try, it would be interesting to build a kernel > > without USB at all to see if it can boot ok. Also, it might be good to break > > into DDB in a kernel with USB enabled and run 'show intrcnt' to see if the USB > > devices are seeing any interrupts. > > I installed 8.3 on this server and did a makeworld into 9.0 REL (GENERIC kernel without USB support) > > Now the bootup from drom disk stops with the message: > "Entropy harvesting: interrupts ethernet point_to_point" > and I cannot enter DDB (vga console, ctrl-alt-esc), although it is compiled into the kernel. > > However. I have the option to boot into single-user, before "Entropy harvesting: interrupts ethernet point_to_point" shows up. > > FYI: Additionally I tried to boot the 9.0-RELEASE-AMD64 memstick on another HP/Compaq server (DL385 G2) and the bootup also stops with the same "mount waiting for: usbus1 usbus0" message, as the DL145G3 does. > > Is DDB active on the 9.0-RELEASE-AMD64 memstick? Hmm, I'm not sure if it is. If it isn't, you can build a 9.0 kernel that contains DDB and replace the kernel image on the memstick with that from another machine. -- John Baldwin From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 19 19:00:34 2012 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3C9981065670 for ; Mon, 19 Mar 2012 19:00:34 +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 270E58FC17 for ; Mon, 19 Mar 2012 19:00:34 +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 q2JJ0Xi2073120 for ; Mon, 19 Mar 2012 19:00:33 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q2JJ0X3j073119; Mon, 19 Mar 2012 19:00:33 GMT (envelope-from gnats) Date: Mon, 19 Mar 2012 19:00:33 GMT Message-Id: <201203191900.q2JJ0X3j073119@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Mark Linimon X-Mailman-Approved-At: Mon, 19 Mar 2012 20:02:14 +0000 Cc: Subject: Re: amd64/166229: [boot] Unable to install FreeBSD 9 on Acer Extensa 5220 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Mark Linimon List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Mar 2012 19:00:34 -0000 The following reply was made to PR amd64/166229; it has been noted by GNATS. From: Mark Linimon To: bug-followup@FreeBSD.org Cc: Subject: Re: amd64/166229: [boot] Unable to install FreeBSD 9 on Acer Extensa 5220 Date: Mon, 19 Mar 2012 13:58:44 -0500 ----- Forwarded message from John Baldwin ----- Date: Mon, 19 Mar 2012 08:09:34 -0400 From: John Baldwin To: freebsd-amd64@freebsd.org, freebsd-bugs@freebsd.org Subject: Re: amd64/166229: [boot] Unable to install FreeBSD 9 on Acer Extensa 5220 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p10; KDE/4.5.5; amd64; ; ) Can you drop into DDB and use 'ps' and possibly 'tr 0' to see what the boot is waiting on? -- John Baldwin ----- End forwarded message ----- From owner-freebsd-amd64@FreeBSD.ORG Tue Mar 20 05:16:51 2012 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B93EC106566C for ; Tue, 20 Mar 2012 05:16:51 +0000 (UTC) (envelope-from daniel.mansfield@unsw.edu.au) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) by mx1.freebsd.org (Postfix) with ESMTP id 906D68FC0A for ; Tue, 20 Mar 2012 05:16:51 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1S9rRC-000423-P6 for freebsd-amd64@freebsd.org; Mon, 19 Mar 2012 22:16:50 -0700 Date: Mon, 19 Mar 2012 22:16:50 -0700 (PDT) From: dman To: freebsd-amd64@freebsd.org Message-ID: <1332220610771-5579074.post@n5.nabble.com> In-Reply-To: <201112091800.pB9I0S5H085666@freefall.freebsd.org> References: <201112071911.pB7JBqFn006541@vestein.arb-phys.uni-dortmund.de> <201112091800.pB9I0S5H085666@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Tue, 20 Mar 2012 05:28:33 +0000 Subject: Re: amd64/163114: no boot on Via Nanao netbook Samsung NC20 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, 20 Mar 2012 05:16:51 -0000 I'm having the same problem on my VIA Nano X2 L4350. Here is a verbose boot log from 8.3-RC1 http://freebsd.1045724.n5.nabble.com/file/n5579074/verbose_boot_8.3-RC1.log verbose_boot_8.3-RC1.log when booted the last lines are: device_attach: est0 attach returned 6 Device configuration finished. procfs registered panic: No usable event timer found! cpuid = 0 KDB: stack backtrace: ... -- View this message in context: http://freebsd.1045724.n5.nabble.com/amd64-163114-no-boot-on-Via-Nanao-netbook-Samsung-NC20-tp5056757p5579074.html Sent from the freebsd-amd64 mailing list archive at Nabble.com. From owner-freebsd-amd64@FreeBSD.ORG Tue Mar 20 08:50:09 2012 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AD954106566C for ; Tue, 20 Mar 2012 08:50: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 7C2958FC16 for ; Tue, 20 Mar 2012 08:50: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 q2K8o9d9078682 for ; Tue, 20 Mar 2012 08:50:09 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q2K8o9ps078681; Tue, 20 Mar 2012 08:50:09 GMT (envelope-from gnats) Date: Tue, 20 Mar 2012 08:50:09 GMT Message-Id: <201203200850.q2K8o9ps078681@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Robert Peters X-Mailman-Approved-At: Tue, 20 Mar 2012 12:42:41 +0000 Cc: Subject: Re: amd64/166229: [boot] Unable to install FreeBSD 9 on Acer Extensa 5220 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Robert Peters List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Mar 2012 08:50:09 -0000 The following reply was made to PR amd64/166229; it has been noted by GNATS. From: Robert Peters To: bug-followup@freebsd.org, r2p2.gw@googlemail.com Cc: Subject: Re: amd64/166229: [boot] Unable to install FreeBSD 9 on Acer Extensa 5220 Date: Tue, 20 Mar 2012 09:43:46 +0100 Is DDB enabled in the live cd by default? If not it could be complicated to compile the kernel without getting it to boot. Never did this DDb thing before but I will give it a try. From owner-freebsd-amd64@FreeBSD.ORG Tue Mar 20 14:50:16 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 789391065670 for ; Tue, 20 Mar 2012 14:50:16 +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 63CDB8FC08 for ; Tue, 20 Mar 2012 14:50:16 +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 q2KEoGMY017443 for ; Tue, 20 Mar 2012 14:50:16 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q2KEoGLv017442; Tue, 20 Mar 2012 14:50:16 GMT (envelope-from gnats) Date: Tue, 20 Mar 2012 14:50:16 GMT Message-Id: <201203201450.q2KEoGLv017442@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Mark Linimon X-Mailman-Approved-At: Tue, 20 Mar 2012 14:51:21 +0000 Cc: Subject: Re: amd64/163114: no boot on Via Nanao netbook Samsung NC20 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Mark Linimon List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Mar 2012 14:50:16 -0000 The following reply was made to PR amd64/163114; it has been noted by GNATS. From: Mark Linimon To: bug-followup@FreeBSD.org Cc: Subject: Re: amd64/163114: no boot on Via Nanao netbook Samsung NC20 Date: Tue, 20 Mar 2012 09:46:45 -0500 ----- Forwarded message from dman ----- Date: Mon, 19 Mar 2012 22:16:50 -0700 (PDT) From: dman To: freebsd-amd64@freebsd.org Subject: Re: amd64/163114: no boot on Via Nanao netbook Samsung NC20 I'm having the same problem on my VIA Nano X2 L4350. Here is a verbose boot log from 8.3-RC1 http://freebsd.1045724.n5.nabble.com/file/n5579074/verbose_boot_8.3-RC1.log verbose_boot_8.3-RC1.log when booted the last lines are: device_attach: est0 attach returned 6 Device configuration finished. procfs registered panic: No usable event timer found! cpuid = 0 KDB: stack backtrace: ... -- View this message in context: http://freebsd.1045724.n5.nabble.com/amd64-163114-no-boot-on-Via-Nanao-netbook-Samsung-NC20-tp5056757p5579074.html Sent from the freebsd-amd64 mailing list archive at Nabble.com. _______________________________________________ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" ----- End forwarded message ----- From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 22 18:02:08 2012 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 669BA106567D; Thu, 22 Mar 2012 18:02:08 +0000 (UTC) (envelope-from jlott@averesystems.com) Received: from zimbra.averesystems.com (75-149-8-245-Pennsylvania.hfc.comcastbusiness.net [75.149.8.245]) by mx1.freebsd.org (Postfix) with ESMTP id F324E8FC20; Thu, 22 Mar 2012 18:02:07 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by zimbra.averesystems.com (Postfix) with ESMTP id 91894446005; Thu, 22 Mar 2012 14:05:15 -0400 (EDT) X-Virus-Scanned: amavisd-new at averesystems.com Received: from zimbra.averesystems.com ([127.0.0.1]) by localhost (zimbra.averesystems.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SlBK-nbBOAtJ; Thu, 22 Mar 2012 14:05:14 -0400 (EDT) Received: from jlott-mac.arriad.com (fw.arriad.com [10.0.0.16]) by zimbra.averesystems.com (Postfix) with ESMTPSA id 1064F446004; Thu, 22 Mar 2012 14:05:14 -0400 (EDT) From: Jeremiah Lott Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Thu, 22 Mar 2012 14:01:59 -0400 Message-Id: To: freebsd-amd64@freebsd.org Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) Cc: alc@freebsd.org, kib@freebsd.org Subject: page fault after wiring page 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, 22 Mar 2012 18:02:08 -0000 We've been seeing some panics and deadlocks that appear to be related to = getting a page fault when accessing a page after it has been wired (on = amd64). All the ones we have seen are related to sysctl handlers that = call sysctl_wire_old_buffer, then lock a mutex, then call SYSCTL_OUT. = When it does the copyout, it gets a page fault even though the page has = been wired, sometimes causing it to sleep while holding a mutex or = recurse on non-recursable mutexes. Here are the two panics that are = most easy to follow: Sleeping thread (tid 100458, pid 2737) owns a non-sleepable lock sched_switch() at 0xffffffff80603bf5 =3D sched_switch+0x146 mi_switch() at 0xffffffff805e8e15 =3D mi_switch+0x183 sleepq_switch() at 0xffffffff8061e6e7 =3D sleepq_switch+0xb1 sleepq_wait() at 0xffffffff8061f0ea =3D sleepq_wait+0x3d _sx_slock_hard() at 0xffffffff805e7ca7 =3D _sx_slock_hard+0x41d _sx_slock() at 0xffffffff805e7e32 =3D _sx_slock+0x3d vm_map_lookup() at 0xffffffff807909e4 =3D vm_map_lookup+0x54 vm_fault() at 0xffffffff80786c20 =3D vm_fault+0x11c trap_pfault() at 0xffffffff80844dd0 =3D trap_pfault+0xe1 trap() at 0xffffffff80845286 =3D trap+0x337 calltrap() at 0xffffffff80827f28 =3D calltrap+0x8 --- trap 0xc, rip =3D 0xffffffff8084296b, rsp =3D 0xffffff811391e7e0, = rbp =3D 0xffffff811391e810 --- copyout() at 0xffffffff8084296b =3D copyout+0x3b sysctl_rtsock() at 0xffffffff806a5ef7 =3D sysctl_rtsock+0x499 sysctl_root() at 0xffffffff805eab9e =3D sysctl_root+0xea userland_sysctl() at 0xffffffff805eae6e =3D userland_sysctl+0x14f sysctl() at 0xffffffff805eb258 =3D sysctl+0x9a amd64_syscall() at 0xffffffff80844065 =3D amd64_syscall+0x145 Xfast_syscall() at 0xffffffff8082821c =3D Xfast_syscall+0xfc login: panic: _mtx_lock_sleep: recursed on non-recursive mutex process = lock @ ../../../amd64/amd64/trap.c:731 cpuid =3D 0 KDB: stack backtrace: gdb_trace_self_wrapper() at 0xffffffff8057e7ea =3D = gdb_trace_self_wrapper+0x2a kdb_backtrace() at 0xffffffff8062ffdc =3D kdb_backtrace+0x37 panic() at 0xffffffff805f89ca =3D panic+0x2ad _mtx_lock_flags() at 0xffffffff805e9376 =3D _mtx_lock_flags _mtx_lock_flags() at 0xffffffff805e9417 =3D _mtx_lock_flags+0xa1 trap_pfault() at 0xffffffff80880450 =3D trap_pfault+0xa1 trap() at 0xffffffff80880ac7 =3D trap+0x4b8 calltrap() at 0xffffffff80861af8 =3D calltrap+0x8 --- trap 0xc, rip =3D 0xffffffff8087de8b, rsp =3D 0xffffff807b7e9410, = rbp =3D 0xffffff807b7e9440 --- copyout() at 0xffffffff8087de8b =3D copyout+0x3b sysctl_out_proc() at 0xffffffff805ed305 =3D sysctl_out_proc+0x16c sysctl_root() at 0xffffffff80606141 =3D sysctl_root+0x13a userland_sysctl() at 0xffffffff8060640a =3D userland_sysctl+0x14f sysctl() at 0xffffffff806067f8 =3D sysctl+0x9a amd64_syscall() at 0xffffffff8087f635 =3D amd64_syscall+0x145 Xfast_syscall() at 0xffffffff80861dec =3D Xfast_syscall+0xfc --- syscall (202, FreeBSD ELF64, sysctl), rip =3D 0x801c12b0c, rsp =3D = 0x7fffffffb768, rbp =3D 0x7fffffffb7b0 --- --- curthread 0xffffff000465b000, tid 100142 After doing some instrumentation, I think I've figured out what is = causing this. It seems that when I am wiring the page, in some = situations the page table entry is being changed from read-only -> = read-write as well as being wired. I haven't figured out the exact = scenario that causes this, but I can definitely see it in my added = trace. Here is an example page table entry transition I am seeing in = pmap_enter that is called as a result of the wire: pmap_enter: origpte: 80000000ad201425 newpte: 80000000ad201607 This means that we are setting PG_W (wired) and PG_RW (read/write) in = this pmap_enter operation. Everytime I saw a page-fault after wiring it = was immediately preceded by a transition like this (in the cases that = did not page fault, the page table entry already had PG_RW set). This = made me suspect that a read-only version of the page table entry was = cached in the TLB. I noticed we invalidate in some situations in = pmap_enter, but this transition is not one of them. I was able to = eliminate the panics by making this change: diff --git a/src/sys/amd64/amd64/pmap.c b/src/sys/amd64/amd64/pmap.c --- a/src/sys/amd64/amd64/pmap.c +++ b/src/sys/amd64/amd64/pmap.c @@ -3251,6 +3251,11 @@ validate: if (opa !=3D VM_PAGE_TO_PHYS(m) || = ((origpte & PG_NX) =3D=3D 0 && (newpte & = PG_NX))) invlva =3D TRUE; + if ((newpte & PG_W) && + ((origpte & PG_RW) =3D=3D 0) && + (newpte & PG_RW)) { + invlva =3D TRUE; + } } if ((origpte & (PG_M | PG_RW)) =3D=3D (PG_M | = PG_RW)) { if ((origpte & PG_MANAGED) !=3D 0) I wanted to see if anyone has seen issues in this area, and if this fix = seems appropriate. I'm running 8.2, but I didn't see any obvious = changes to pmap stuff in head which would change this behavior. Thanks = for any feedback, Jeremiah Lott Avere Systems= From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 22 18:35:12 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 515E81065674; Thu, 22 Mar 2012 18:35:12 +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 82F1A8FC14; Thu, 22 Mar 2012 18:35:11 +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 q2MIYxLM066267; Thu, 22 Mar 2012 20:34:59 +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 q2MIYw9m065434; Thu, 22 Mar 2012 20:34:58 +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 q2MIYwGb065433; Thu, 22 Mar 2012 20:34:58 +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: Thu, 22 Mar 2012 20:34:58 +0200 From: Konstantin Belousov To: Jeremiah Lott Message-ID: <20120322183458.GF2358@deviant.kiev.zoral.com.ua> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="xkJEvbTYpfqRozZ0" Content-Disposition: inline In-Reply-To: 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=-4.0 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: alc@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: page fault after wiring page 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, 22 Mar 2012 18:35:12 -0000 --xkJEvbTYpfqRozZ0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Mar 22, 2012 at 02:01:59PM -0400, Jeremiah Lott wrote: > We've been seeing some panics and deadlocks that appear to be related to = getting a page fault when accessing a page after it has been wired (on amd6= 4). All the ones we have seen are related to sysctl handlers that call sys= ctl_wire_old_buffer, then lock a mutex, then call SYSCTL_OUT. When it does= the copyout, it gets a page fault even though the page has been wired, som= etimes causing it to sleep while holding a mutex or recurse on non-recursab= le mutexes. Here are the two panics that are most easy to follow: >=20 > Sleeping thread (tid 100458, pid 2737) owns a non-sleepable lock > sched_switch() at 0xffffffff80603bf5 =3D sched_switch+0x146 > mi_switch() at 0xffffffff805e8e15 =3D mi_switch+0x183 > sleepq_switch() at 0xffffffff8061e6e7 =3D sleepq_switch+0xb1 > sleepq_wait() at 0xffffffff8061f0ea =3D sleepq_wait+0x3d > _sx_slock_hard() at 0xffffffff805e7ca7 =3D _sx_slock_hard+0x41d > _sx_slock() at 0xffffffff805e7e32 =3D _sx_slock+0x3d > vm_map_lookup() at 0xffffffff807909e4 =3D vm_map_lookup+0x54 > vm_fault() at 0xffffffff80786c20 =3D vm_fault+0x11c > trap_pfault() at 0xffffffff80844dd0 =3D trap_pfault+0xe1 > trap() at 0xffffffff80845286 =3D trap+0x337 > calltrap() at 0xffffffff80827f28 =3D calltrap+0x8 > --- trap 0xc, rip =3D 0xffffffff8084296b, rsp =3D 0xffffff811391e7e0, rbp= =3D 0xffffff811391e810 --- > copyout() at 0xffffffff8084296b =3D copyout+0x3b > sysctl_rtsock() at 0xffffffff806a5ef7 =3D sysctl_rtsock+0x499 > sysctl_root() at 0xffffffff805eab9e =3D sysctl_root+0xea > userland_sysctl() at 0xffffffff805eae6e =3D userland_sysctl+0x14f > sysctl() at 0xffffffff805eb258 =3D sysctl+0x9a > amd64_syscall() at 0xffffffff80844065 =3D amd64_syscall+0x145 > Xfast_syscall() at 0xffffffff8082821c =3D Xfast_syscall+0xfc >=20 > login: panic: _mtx_lock_sleep: recursed on non-recursive mutex process lo= ck @ ../../../amd64/amd64/trap.c:731 > cpuid =3D 0 > KDB: stack backtrace: > gdb_trace_self_wrapper() at 0xffffffff8057e7ea =3D gdb_trace_self_wrapper= +0x2a > kdb_backtrace() at 0xffffffff8062ffdc =3D kdb_backtrace+0x37 > panic() at 0xffffffff805f89ca =3D panic+0x2ad > _mtx_lock_flags() at 0xffffffff805e9376 =3D _mtx_lock_flags > _mtx_lock_flags() at 0xffffffff805e9417 =3D _mtx_lock_flags+0xa1 > trap_pfault() at 0xffffffff80880450 =3D trap_pfault+0xa1 > trap() at 0xffffffff80880ac7 =3D trap+0x4b8 > calltrap() at 0xffffffff80861af8 =3D calltrap+0x8 > --- trap 0xc, rip =3D 0xffffffff8087de8b, rsp =3D 0xffffff807b7e9410, rbp= =3D 0xffffff807b7e9440 --- > copyout() at 0xffffffff8087de8b =3D copyout+0x3b > sysctl_out_proc() at 0xffffffff805ed305 =3D sysctl_out_proc+0x16c > sysctl_root() at 0xffffffff80606141 =3D sysctl_root+0x13a > userland_sysctl() at 0xffffffff8060640a =3D userland_sysctl+0x14f > sysctl() at 0xffffffff806067f8 =3D sysctl+0x9a > amd64_syscall() at 0xffffffff8087f635 =3D amd64_syscall+0x145 > Xfast_syscall() at 0xffffffff80861dec =3D Xfast_syscall+0xfc > --- syscall (202, FreeBSD ELF64, sysctl), rip =3D 0x801c12b0c, rsp =3D 0x= 7fffffffb768, rbp =3D 0x7fffffffb7b0 --- > --- curthread 0xffffff000465b000, tid 100142 >=20 > After doing some instrumentation, I think I've figured out what is causin= g this. It seems that when I am wiring the page, in some situations the pa= ge table entry is being changed from read-only -> read-write as well as bei= ng wired. I haven't figured out the exact scenario that causes this, but I= can definitely see it in my added trace. Here is an example page table en= try transition I am seeing in pmap_enter that is called as a result of the = wire: >=20 > pmap_enter: origpte: 80000000ad201425 newpte: 80000000ad201607 >=20 > This means that we are setting PG_W (wired) and PG_RW (read/write) in thi= s pmap_enter operation. Everytime I saw a page-fault after wiring it was i= mmediately preceded by a transition like this (in the cases that did not pa= ge fault, the page table entry already had PG_RW set). This made me suspec= t that a read-only version of the page table entry was cached in the TLB. = I noticed we invalidate in some situations in pmap_enter, but this transiti= on is not one of them. I was able to eliminate the panics by making this c= hange: >=20 > diff --git a/src/sys/amd64/amd64/pmap.c b/src/sys/amd64/amd64/pmap.c > --- a/src/sys/amd64/amd64/pmap.c > +++ b/src/sys/amd64/amd64/pmap.c > @@ -3251,6 +3251,11 @@ validate: > if (opa !=3D VM_PAGE_TO_PHYS(m) || ((orig= pte & > PG_NX) =3D=3D 0 && (newpte & PG_NX))) > invlva =3D TRUE; > + if ((newpte & PG_W) && > + ((origpte & PG_RW) =3D=3D 0) && > + (newpte & PG_RW)) { > + invlva =3D TRUE; > + } > } > if ((origpte & (PG_M | PG_RW)) =3D=3D (PG_M | PG_= RW)) { > if ((origpte & PG_MANAGED) !=3D 0) >=20 > I wanted to see if anyone has seen issues in this area, and if this fix s= eems appropriate. I'm running 8.2, but I didn't see any obvious changes to= pmap stuff in head which would change this behavior. Thanks for any feedb= ack, >=20 > Jeremiah Lott > Avere Systems This should be the issue fixed in the r233291. --xkJEvbTYpfqRozZ0 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (FreeBSD) iEYEARECAAYFAk9rcNAACgkQC3+MBN1Mb4hyDgCcC4HAZSGcRJOYwxRV08Rguk3X KmAAn207yJzVN/FORpBPyDzFb9LNaKb8 =59Ts -----END PGP SIGNATURE----- --xkJEvbTYpfqRozZ0-- From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 22 18:24:18 2012 Return-Path: Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9365E106566B; Thu, 22 Mar 2012 18:24:18 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 84D148FC12; Thu, 22 Mar 2012 18:24:17 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id UAA11729; Thu, 22 Mar 2012 20:24:12 +0200 (EET) (envelope-from avg@FreeBSD.org) Message-ID: <4F6B6E4C.9030503@FreeBSD.org> Date: Thu, 22 Mar 2012 20:24:12 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:10.0.2) Gecko/20120221 Thunderbird/10.0.2 MIME-Version: 1.0 To: Jeremiah Lott References: In-Reply-To: X-Enigmail-Version: 1.3.5 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Thu, 22 Mar 2012 20:29:28 +0000 Cc: alc@FreeBSD.org, kib@FreeBSD.org, freebsd-amd64@FreeBSD.org Subject: Re: page fault after wiring page 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, 22 Mar 2012 18:24:18 -0000 I see that you've already CC-ed the right people :-) Does this commit look related http://svn.freebsd.org/changeset/base/233291 ? on 22/03/2012 20:01 Jeremiah Lott said the following: > We've been seeing some panics and deadlocks that appear to be related to getting a page fault when accessing a page after it has been wired (on amd64). All the ones we have seen are related to sysctl handlers that call sysctl_wire_old_buffer, then lock a mutex, then call SYSCTL_OUT. When it does the copyout, it gets a page fault even though the page has been wired, sometimes causing it to sleep while holding a mutex or recurse on non-recursable mutexes. Here are the two panics that are most easy to follow: > > Sleeping thread (tid 100458, pid 2737) owns a non-sleepable lock > sched_switch() at 0xffffffff80603bf5 = sched_switch+0x146 > mi_switch() at 0xffffffff805e8e15 = mi_switch+0x183 > sleepq_switch() at 0xffffffff8061e6e7 = sleepq_switch+0xb1 > sleepq_wait() at 0xffffffff8061f0ea = sleepq_wait+0x3d > _sx_slock_hard() at 0xffffffff805e7ca7 = _sx_slock_hard+0x41d > _sx_slock() at 0xffffffff805e7e32 = _sx_slock+0x3d > vm_map_lookup() at 0xffffffff807909e4 = vm_map_lookup+0x54 > vm_fault() at 0xffffffff80786c20 = vm_fault+0x11c > trap_pfault() at 0xffffffff80844dd0 = trap_pfault+0xe1 > trap() at 0xffffffff80845286 = trap+0x337 > calltrap() at 0xffffffff80827f28 = calltrap+0x8 > --- trap 0xc, rip = 0xffffffff8084296b, rsp = 0xffffff811391e7e0, rbp = 0xffffff811391e810 --- > copyout() at 0xffffffff8084296b = copyout+0x3b > sysctl_rtsock() at 0xffffffff806a5ef7 = sysctl_rtsock+0x499 > sysctl_root() at 0xffffffff805eab9e = sysctl_root+0xea > userland_sysctl() at 0xffffffff805eae6e = userland_sysctl+0x14f > sysctl() at 0xffffffff805eb258 = sysctl+0x9a > amd64_syscall() at 0xffffffff80844065 = amd64_syscall+0x145 > Xfast_syscall() at 0xffffffff8082821c = Xfast_syscall+0xfc > > login: panic: _mtx_lock_sleep: recursed on non-recursive mutex process lock @ ../../../amd64/amd64/trap.c:731 > cpuid = 0 > KDB: stack backtrace: > gdb_trace_self_wrapper() at 0xffffffff8057e7ea = gdb_trace_self_wrapper+0x2a > kdb_backtrace() at 0xffffffff8062ffdc = kdb_backtrace+0x37 > panic() at 0xffffffff805f89ca = panic+0x2ad > _mtx_lock_flags() at 0xffffffff805e9376 = _mtx_lock_flags > _mtx_lock_flags() at 0xffffffff805e9417 = _mtx_lock_flags+0xa1 > trap_pfault() at 0xffffffff80880450 = trap_pfault+0xa1 > trap() at 0xffffffff80880ac7 = trap+0x4b8 > calltrap() at 0xffffffff80861af8 = calltrap+0x8 > --- trap 0xc, rip = 0xffffffff8087de8b, rsp = 0xffffff807b7e9410, rbp = 0xffffff807b7e9440 --- > copyout() at 0xffffffff8087de8b = copyout+0x3b > sysctl_out_proc() at 0xffffffff805ed305 = sysctl_out_proc+0x16c > sysctl_root() at 0xffffffff80606141 = sysctl_root+0x13a > userland_sysctl() at 0xffffffff8060640a = userland_sysctl+0x14f > sysctl() at 0xffffffff806067f8 = sysctl+0x9a > amd64_syscall() at 0xffffffff8087f635 = amd64_syscall+0x145 > Xfast_syscall() at 0xffffffff80861dec = Xfast_syscall+0xfc > --- syscall (202, FreeBSD ELF64, sysctl), rip = 0x801c12b0c, rsp = 0x7fffffffb768, rbp = 0x7fffffffb7b0 --- > --- curthread 0xffffff000465b000, tid 100142 > > After doing some instrumentation, I think I've figured out what is causing this. It seems that when I am wiring the page, in some situations the page table entry is being changed from read-only -> read-write as well as being wired. I haven't figured out the exact scenario that causes this, but I can definitely see it in my added trace. Here is an example page table entry transition I am seeing in pmap_enter that is called as a result of the wire: > > pmap_enter: origpte: 80000000ad201425 newpte: 80000000ad201607 > > This means that we are setting PG_W (wired) and PG_RW (read/write) in this pmap_enter operation. Everytime I saw a page-fault after wiring it was immediately preceded by a transition like this (in the cases that did not page fault, the page table entry already had PG_RW set). This made me suspect that a read-only version of the page table entry was cached in the TLB. I noticed we invalidate in some situations in pmap_enter, but this transition is not one of them. I was able to eliminate the panics by making this change: > > diff --git a/src/sys/amd64/amd64/pmap.c b/src/sys/amd64/amd64/pmap.c > --- a/src/sys/amd64/amd64/pmap.c > +++ b/src/sys/amd64/amd64/pmap.c > @@ -3251,6 +3251,11 @@ validate: > if (opa != VM_PAGE_TO_PHYS(m) || ((origpte & > PG_NX) == 0 && (newpte & PG_NX))) > invlva = TRUE; > + if ((newpte & PG_W) && > + ((origpte & PG_RW) == 0) && > + (newpte & PG_RW)) { > + invlva = TRUE; > + } > } > if ((origpte & (PG_M | PG_RW)) == (PG_M | PG_RW)) { > if ((origpte & PG_MANAGED) != 0) > > I wanted to see if anyone has seen issues in this area, and if this fix seems appropriate. I'm running 8.2, but I didn't see any obvious changes to pmap stuff in head which would change this behavior. Thanks for any feedback, > > Jeremiah Lott > Avere Systems -- Andriy Gapon From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 22 21:09:17 2012 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 75D441065670; Thu, 22 Mar 2012 21:09:17 +0000 (UTC) (envelope-from jlott@averesystems.com) Received: from zimbra.averesystems.com (75-149-8-245-Pennsylvania.hfc.comcastbusiness.net [75.149.8.245]) by mx1.freebsd.org (Postfix) with ESMTP id 3F80F8FC17; Thu, 22 Mar 2012 21:09:16 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by zimbra.averesystems.com (Postfix) with ESMTP id D2707446004; Thu, 22 Mar 2012 17:12:30 -0400 (EDT) X-Virus-Scanned: amavisd-new at averesystems.com Received: from zimbra.averesystems.com ([127.0.0.1]) by localhost (zimbra.averesystems.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L-GxiCWaOL79; Thu, 22 Mar 2012 17:12:30 -0400 (EDT) Received: from jlott-mac.arriad.com (fw.arriad.com [10.0.0.16]) by zimbra.averesystems.com (Postfix) with ESMTPSA id 1B67E446002; Thu, 22 Mar 2012 17:12:30 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Jeremiah Lott In-Reply-To: <20120322183458.GF2358@deviant.kiev.zoral.com.ua> Date: Thu, 22 Mar 2012 17:09:15 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20120322183458.GF2358@deviant.kiev.zoral.com.ua> To: Konstantin Belousov X-Mailer: Apple Mail (2.1084) Cc: alc@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: page fault after wiring page 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, 22 Mar 2012 21:09:17 -0000 On Mar 22, 2012, at 2:34 PM, Konstantin Belousov wrote: >=20 > This should be the issue fixed in the r233291. Agreed. I pulled back r233291 as well as r223886, r223888, and r223889 = into my 8.2-based branch and it seems to fix the issue. Thanks, Jeremiah= From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 22 22:37:52 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 05ADE1065673 for ; Thu, 22 Mar 2012 22:37:52 +0000 (UTC) (envelope-from tomdean@speakeasy.org) Received: from asbnvacz-mailrelay01.megapath.net (asbnvacz-mailrelay01.megapath.net [207.145.128.243]) by mx1.freebsd.org (Postfix) with ESMTP id C8A338FC16 for ; Thu, 22 Mar 2012 22:37:51 +0000 (UTC) Received: from mail6.sea5.speakeasy.net (mail6.sea5.speakeasy.net [69.17.117.50]) by asbnvacz-mailrelay01.megapath.net (Postfix) with ESMTP id 31ACEA71BBB for ; Thu, 22 Mar 2012 18:37:45 -0400 (EDT) Received: (qmail 8812 invoked from network); 22 Mar 2012 22:37:44 -0000 Received: by simscan 1.4.0 ppid: 28056, pid: 32253, t: 0.3343s scanners: clamav: 0.88.2/m:52/d:10739 spam: 3.0.4 Received: from unknown (HELO P9X79.tddhome) (tomdean@[24.113.107.31]) (envelope-sender ) by mail6.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 22 Mar 2012 22:37:44 -0000 Message-ID: <4F6BA9C3.8030704@speakeasy.org> Date: Thu, 22 Mar 2012 15:37:55 -0700 From: "Thomas D. Dean" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:10.0.2) Gecko/20120310 Thunderbird/10.0.2 MIME-Version: 1.0 To: gecko@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail6.sea5 X-Spam-Level: * X-Spam-Status: No, score=1.4 required=8.0 tests=FORGED_RCVD_HELO, RATWARE_GECKO_BUILD,WEIRD_PORT autolearn=disabled version=3.0.4 Cc: freebsd-amd64@freebsd.org Subject: Strange Printing with CUPS 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, 22 Mar 2012 22:37:52 -0000 > uname -a FreeBSD P9X79.tddhome 9.0-STABLE FreeBSD 9.0-STABLE #0: Thu Feb 23 20:06:18 PST 2012 root@P9X79.tddhome:/usr/obj/usr/src/sys/GENERIC amd64 > ls /var/db/pkg | grep cup cups-1.5.0/ cups-base-1.5.2/ cups-client-1.5.2_1/ cups-image-1.5.2/ cups-pstoraster-8.15.4_6/ cups-smb-backend-1.0_6/ I cannot determine if this is a port problem or a install/config problem or missing something. When I print to a windows printer (HP C4100) using the seamonkey port it appears the fonts are strange. Characters on the printed page are only partially formed and mostly unreadable. Printing the same web page from windows and linux (seamonkey) CUPS produces the expected quality print. Using lpr with a text file works as expected. I think I am missing something on the FreeBSD machine, but, what? From http://localhost:631/printers/C4100 Description: HP Photosmart C4100 Location: HP C4100 on Driver: HP DeskJet Series (color, 2-sided printing) Connection: smb:///C4100 Defaults: job-sheets=none, none media=na_letter_8.5x11in sides=one-sided Tom Dean From owner-freebsd-amd64@FreeBSD.ORG Fri Mar 23 15:38:54 2012 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AFDCB1065673; Fri, 23 Mar 2012 15:38:54 +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 200AA8FC19; Fri, 23 Mar 2012 15:38:53 +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 q2NFchWV038317; Fri, 23 Mar 2012 17:38:43 +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 q2NFchPM097087; Fri, 23 Mar 2012 17:38:43 +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 q2NFcgFc097086; Fri, 23 Mar 2012 17:38:42 +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: Fri, 23 Mar 2012 17:38:42 +0200 From: Konstantin Belousov To: Jeremiah Lott Message-ID: <20120323153842.GL2358@deviant.kiev.zoral.com.ua> References: <20120322183458.GF2358@deviant.kiev.zoral.com.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="tCj5P50694qw/4D5" Content-Disposition: inline In-Reply-To: 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=-4.0 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: alc@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: page fault after wiring page 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, 23 Mar 2012 15:38:54 -0000 --tCj5P50694qw/4D5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Mar 22, 2012 at 05:09:15PM -0400, Jeremiah Lott wrote: > On Mar 22, 2012, at 2:34 PM, Konstantin Belousov wrote: > >=20 > > This should be the issue fixed in the r233291. >=20 > Agreed. I pulled back r233291 as well as r223886, r223888, and r223889 i= nto my 8.2-based branch and it seems to fix the issue. Thanks, >=20 Which remind me to merge r223889 into stable/8. Thank you for testing. --tCj5P50694qw/4D5 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (FreeBSD) iEYEARECAAYFAk9smQEACgkQC3+MBN1Mb4h3aACgo2bT2q8y8AKWLsG/V869/ZR5 hSYAmwfiSyj3eOM6gSL66Q1T36IkDNXU =rTd+ -----END PGP SIGNATURE----- --tCj5P50694qw/4D5--