From owner-freebsd-stable@FreeBSD.ORG Sun Dec 7 13:30:20 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 94F33391 for ; Sun, 7 Dec 2014 13:30:20 +0000 (UTC) Received: from mail.webmatic.de (mail.webmatic.de [212.78.101.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.webmatic.de", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 54760169 for ; Sun, 7 Dec 2014 13:30:19 +0000 (UTC) Received: from [192.168.178.27] (p54AF2560.dip0.t-ipconnect.de [84.175.37.96]) by mail.webmatic.de (Postfix) with ESMTPSA id 46ADF8A044; Sun, 7 Dec 2014 14:30:11 +0100 (CET) Message-ID: <5484565F.4070201@chef-ingenieur.de> Date: Sun, 07 Dec 2014 14:30:07 +0100 From: Thomas Krause User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Scot Hetzel Subject: Re: freebsd-update 10.0 -> 10.1 segmentation fault (nsswitch.conf w mysql) References: <1d89bae75778743583265187bc41a4ca@chef-ingenieur.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2014 13:30:20 -0000 Am 06.12.2014 20:31, schrieb Scot Hetzel: > On Sat, Dec 6, 2014 at 4:35 AM, Thomas Krause > wrote: >> Hi, >> binary update from Freebsd 10.0 to 10.1 Release fails after >> 1st reboot with 10.1 kernel and running >> >> # freebsd-update install >> Segmentation fault >> >> I found, removing the mysql entry from /etc/nsswitch.conf helps. >> But running >> >> # freebsd-update install >> >> again, I get "Segmentation fault" again - the "old" nsswitch.conf >> with mysql entries were installed. >> >> How can I fix that (where come the old nsswitch.conf from - a >> find / doesn't help). >> > What port are you using to provide the MySQL support for nsswitch? libnss-mysql-1.5_3 NSS module using a MySQL database for backend > > I checked the net/libnss-mysql port, and it doesn't touch nsswitch.conf. > > Did you check your ${PREFIX}/etc/rc.d scripts to see if a script is > modifying /etc/nsswitch.conf? > no there is no rc-script that modifies nsswitch.conf. I was able to upgrade to 10.1 by extracting the base.txz. freebsd-upgrade doesn't work if you use a modified nsswitch.conf. Regards, Thomas. From owner-freebsd-stable@FreeBSD.ORG Sun Dec 7 14:57:55 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9F253144 for ; Sun, 7 Dec 2014 14:57:55 +0000 (UTC) Received: from isis.morrow.me.uk (isis.morrow.me.uk [204.109.63.142]) by mx1.freebsd.org (Postfix) with ESMTP id 79F7BB99 for ; Sun, 7 Dec 2014 14:57:54 +0000 (UTC) Received: from anubis.morrow.me.uk (unknown [93.89.81.46]) (Authenticated sender: mauzo) by isis.morrow.me.uk (Postfix) with ESMTPSA id 747A445087; Sun, 7 Dec 2014 14:48:32 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.8.3 isis.morrow.me.uk 747A445087 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=morrow.me.uk; s=dkim201101; t=1417963714; bh=45oaSUuw3tVIPKc0fOtETx/UbYSERes+y/PS+hOonUU=; h=Date:From:To:Subject:In-Reply-To; b=LYd9dNzqdaBIO8CAs0IvC3EWpxckgMYxEzBLDGUtdMX3TUN6WvBR1iwQMT3o18wlW l/NXmXqb1NQ0zzBQuTvhWoUimoTVWADMWrIVtV5hrRAwZsVs2EYGB252i3KrefOSVv wTzgP4zl81RYzA/uUdOgDUr3oWzJRREezFxf3Hr8= X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.98.4 at isis.morrow.me.uk Received: by anubis.morrow.me.uk (Postfix, from userid 5001) id 1C530162F1; Sun, 7 Dec 2014 14:48:28 +0000 (GMT) Date: Sun, 7 Dec 2014 14:48:27 +0000 From: Ben Morrow To: freebsd-stable@chef-ingenieur.de, freebsd-stable@freebsd.org Subject: Re: freebsd-update 10.0 -> 10.1 segmentation fault (nsswitch.conf w mysql) Message-ID: <20141207144825.GA17366@anubis.morrow.me.uk> Mail-Followup-To: freebsd-stable@chef-ingenieur.de, freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1d89bae75778743583265187bc41a4ca@chef-ingenieur.de> X-Newsgroups: gmane.os.freebsd.stable User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2014 14:57:55 -0000 Quoth Thomas Krause : > > binary update from Freebsd 10.0 to 10.1 Release fails after > 1st reboot with 10.1 kernel and running > > # freebsd-update install > Segmentation fault > > I found, removing the mysql entry from /etc/nsswitch.conf helps. > But running > > # freebsd-update install > > again, I get "Segmentation fault" again - the "old" nsswitch.conf > with mysql entries were installed. When doing an upgrade, freebsd-update merges your changes into the files under /etc and stashes the merged version away to install when the time comes. This means if you make changes between 'freebsd-update upgrade' and the final 'freebsd-update install' these will be overwritten by the install. > How can I fix that (where come the old nsswitch.conf from - a > find / doesn't help). No, it wouldn't. f-u stores the files gzipped and named by hash, so neither find nor grep -r would find anything. Ben From owner-freebsd-stable@FreeBSD.ORG Mon Dec 8 17:28:50 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3F9F1613 for ; Mon, 8 Dec 2014 17:28:50 +0000 (UTC) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id 2E956284 for ; Mon, 8 Dec 2014 17:28:50 +0000 (UTC) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id 8B6CCF99 for ; Mon, 8 Dec 2014 17:27:24 +0000 (UTC) Date: Mon, 8 Dec 2014 17:27:24 +0000 (GMT) From: jenkins-admin@freebsd.org To: freebsd-stable@freebsd.org Message-ID: <221794600.12.1418059644504.JavaMail.jenkins@jenkins-9.freebsd.org> In-Reply-To: <1338473455.11.1418053276067.JavaMail.jenkins@jenkins-9.freebsd.org> References: <1338473455.11.1418053276067.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: Jenkins build is back to normal : Build-UFS-image #618 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Jenkins-Job: Build-UFS-image X-Jenkins-Result: SUCCESS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2014 17:28:50 -0000 See From owner-freebsd-stable@FreeBSD.ORG Tue Dec 9 02:18:38 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4B5A3C27 for ; Tue, 9 Dec 2014 02:18:38 +0000 (UTC) Received: from mail3.transactionware.com (mail.transactionware.com [203.14.245.7]) by mx1.freebsd.org (Postfix) with SMTP id C1A1B78D for ; Tue, 9 Dec 2014 02:18:37 +0000 (UTC) Received: (qmail 93708 invoked by uid 907); 9 Dec 2014 02:18:30 -0000 Received: from Unknown (HELO jmmacpro.tmst.com.au) (203.14.245.130) (smtp-auth username janm, mechanism plain) by mail3.transactionware.com (qpsmtpd/0.84) with (DHE-RSA-AES256-SHA encrypted) ESMTPSA; Tue, 09 Dec 2014 13:18:30 +1100 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Subject: Re: 10.1 regression: process using serial port becomes unkillable when no modem control signals From: Jan Mikkelsen In-Reply-To: <20141205095659.GF97072@kib.kiev.ua> Date: Tue, 9 Dec 2014 13:18:54 +1100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20141205095659.GF97072@kib.kiev.ua> To: Konstantin Belousov X-Mailer: Apple Mail (2.1993) Cc: marcel@freebsd.org, FreeBSD Stable Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2014 02:18:38 -0000 Hi, > On 5 Dec 2014, at 20:57, Konstantin Belousov = wrote: >=20 > On Fri, Dec 05, 2014 at 06:44:51PM +1100, Jan Mikkelsen wrote: >> Hi, >>=20 >> I have just found this problem on a machine upgraded to 10.1. >>=20 >> When running mgetty on a serial port with nothing connected and then = killing it the process becomes unkillable. This prevents ???shutdown = -r??? from completing, which is particularly annoying. >>=20 >> Giving the serial port a device which provides the right modem = control signals lets the process exit immediately. The same hardware = with 9.3 was fine. >>=20 >> Below is the kernel stack trace on the unkillable process. >>=20 >> Does this ring any bells for anyone? >=20 > This sounds as something that might be fixed by r272786 and r272789 > in HEAD. I did not looked into details too close. >=20 > The changes are not in stable/10, apply manually and test. These resolved the problem. Applying these changes to stable/10 seems = like it would be a good idea. Thanks! Jan. >>=20 >> Thanks, >>=20 >> Jan Mikkelsen >>=20 >> (kgdb) bt >> #0 sched_switch (td=3D0xfffff80236e1a920, newtd=3D, flags=3D) at = /usr/home/janm/p4/freebsd-image-std-2014.2/FreeBSD/src/sys/kern/sched_ule.= c:1945 >> #1 0xffffffff80939ba1 in mi_switch (flags=3D260, newtd=3D0x0) at = /usr/home/janm/p4/freebsd-image-std-2014.2/FreeBSD/src/sys/kern/kern_synch= .c:494 >> #2 0xffffffff80976d6b in sleepq_catch_signals = (wchan=3D0xfffff8000c7344b8, pri=3D0) at = /usr/home/janm/p4/freebsd-image-std-2014.2/FreeBSD/src/sys/kern/subr_sleep= queue.c:426 >> #3 0xffffffff80976c1f in sleepq_wait_sig (wchan=3D0x0, pri=3D0) at = /usr/home/janm/p4/freebsd-image-std-2014.2/FreeBSD/src/sys/kern/subr_sleep= queue.c:631 >> #4 0xffffffff808e345a in _cv_wait_sig (cvp=3D0xfffff8000c7344b8, = lock=3D0xfffff8000c734408) at = /usr/home/janm/p4/freebsd-image-std-2014.2/FreeBSD/src/sys/kern/kern_condv= ar.c:258 >> #5 0xffffffff809957a5 in ttydev_leave (tp=3D0xfffff8000c734400) at = /usr/home/janm/p4/freebsd-image-std-2014.2/FreeBSD/src/sys/kern/tty.c:1392= >> #6 0xffffffff80994d30 in ttydev_close (dev=3D, = fflag=3D0, devtype=3D0, td=3D0x0) at = /usr/home/janm/p4/freebsd-image-std-2014.2/FreeBSD/src/sys/kern/tty.c:353 >> #7 0xffffffff8081ec63 in devfs_close (ap=3D0xfffffe0c541d57e0) at = /usr/home/janm/p4/freebsd-image-std-2014.2/FreeBSD/src/sys/fs/devfs/devfs_= vnops.c:592 >> #8 0xffffffff80e6d281 in VOP_CLOSE_APV (vop=3D, = a=3D) at vnode_if.c:535 >> #9 0xffffffff809df673 in vn_close (vp=3D0xfffff80236a6f588, flags=3D3,= file_cred=3D0xfffff806a300b200, td=3D0xfffff80236e1a920) at = vnode_if.h:225 >> #10 0xffffffff809de4c8 in vn_closefile (fp=3D0xfffff8001243d9b0, = td=3D0xfffff80236e1a920) at = /usr/home/janm/p4/freebsd-image-std-2014.2/FreeBSD/src/sys/kern/vfs_vnops.= c:1557 >> #11 0xffffffff808204bc in devfs_close_f (fp=3D0xfffff8001243d9b0, = td=3D0x0) at = /usr/home/janm/p4/freebsd-image-std-2014.2/FreeBSD/src/sys/fs/devfs/devfs_= vnops.c:611 >> #12 0xffffffff808ed249 in _fdrop (fp=3D0xfffff8001243d9b0, td=3D0x0) = at file.h:343 >> #13 0xffffffff808ef9ae in closef (fp=3D, = td=3D) at = /usr/home/janm/p4/freebsd-image-std-2014.2/FreeBSD/src/sys/kern/kern_descr= ip.c:2335 >> #14 0xffffffff808ef5c9 in fdescfree (td=3D0xfffff80236e1a920) at = /usr/home/janm/p4/freebsd-image-std-2014.2/FreeBSD/src/sys/kern/kern_descr= ip.c:2103 >> #15 0xffffffff808fb8fb in exit1 (td=3D0xfffff80236e1a920, rv=3D) at = /usr/home/janm/p4/freebsd-image-std-2014.2/FreeBSD/src/sys/kern/kern_exit.= c:329 >> #16 0xffffffff808fb37e in sys_sys_exit (td=3D0x0, uap=3D) at = /usr/home/janm/p4/freebsd-image-std-2014.2/FreeBSD/src/sys/kern/kern_exit.= c:153 >> #17 0xffffffff80d4f521 in amd64_syscall (td=3D0xfffff80236e1a920, = traced=3D0) at subr_syscall.c:134 >>=20 >>=20 >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Tue Dec 9 08:34:19 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5F22E45E for ; Tue, 9 Dec 2014 08:34:19 +0000 (UTC) Received: from smtp.free.de (smtp.free.de [91.204.6.103]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CF61F6D for ; Tue, 9 Dec 2014 08:34:18 +0000 (UTC) Received: (qmail 90167 invoked from network); 9 Dec 2014 09:34:07 +0100 Received: from smtp.free.de (HELO orwell) (k@free.de@[91.204.4.103]) (envelope-sender ) by smtp.free.de (qmail-ldap-1.03) with AES128-SHA encrypted SMTP for ; 9 Dec 2014 09:34:07 +0100 Date: Tue, 9 Dec 2014 09:34:05 +0100 From: Kai Gallasch To: freebsd-stable@freebsd.org Subject: Re: 10.1 RC4 r273903 - zpool scrub on ssd mirror - ahci command timeout Message-ID: <20141209093405.6dd2c268@orwell> In-Reply-To: <545ACCEF.5000300@multiplay.co.uk> References: <20141106003240.344dedf6@orwell> <545AB64F.1060502@multiplay.co.uk> <20141106012739.509b96b5@orwell> <545ACCEF.5000300@multiplay.co.uk> Organization: FREE! X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.23; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/YDEQFYLCZWGw5j7u2ru5=EY"; protocol="application/pgp-signature" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2014 08:34:19 -0000 --Sig_/YDEQFYLCZWGw5j7u2ru5=EY Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Am Thu, 06 Nov 2014 01:20:47 +0000 schrieb Steven Hartland : > Try recabling and re-seating, if it still happens try to identify if > its the disk or backplane by moving it in the chassis. We had a > machine here recently where it was backplane issue and simply > replacing it fixed the issue. Steven. In the last weeks I took some time to single out the reason for the AHCI timeouts with the two Samsung SSD drives. Just for the record, my original post on the FreeBSD mailing list archive: http://lists.freebsd.org/pipermail/freebsd-stable/2014-November/080914.html I changed / tried the following to get rid of the AHCI timouts, but no chance, they still show :-/ Hardware: - Changed all four SATA cables with cables of an identical spare server - Changed all four SATA cables with certified SATA3 cables - Replaced the 2.5" -> 3.5" drive converters with ones of another manufacturer - Replaced the drive backplane of the server - Directly hooking the two SSDs up to the SATA connectors on the mainboard - Experimentally put an LSI 9212-4i4e PCIe SATA/SAS Controller into the server and and connected the SATA cables to it. - Same as before, but using the certified SATA3 cables - Same as before, but this time connecting the two SSDs directly to the 9212-4i4e - Same as before, connecting the two SSD directly to the 9212-4i4e, but this time with the original SATA cables BIOS: - Temporarily disabled Power Management - Tried disabling "Enable Hot Plug" Option The difference between using the SATA connectors of the mainboard and using the LSI 9212-4i4e is, that the LSI controller seems to be more picky about CRC errors on the SATA bus and bus problems even show without starting a zfs scrub. When doing a scrub using the LSI controller there are plenty of timeouts and in one test, one of the SSD drives even disappeard from the SATA bus. Of course all the time during testing the two Hitachi non-SSD SATA drives did not show any problems at all - although also connected to the mainboard or the LSI controller during the testing. So I now think the whole problem centers around the Samsung 850 PRO 512GB SSDs. Too bad I do not have the budget to just buy two Intel (or other) SSDs of similar size and see if the timeouts disappear.. I wonder if this is a firmware issue with the drive or just some misguided fancy energy saving feature of this particular drive model causing the whole trouble. Both drives have serial numbers not far apart and smartctl claims there are no errors on the SSDs. Any ideas (left) ? Regards, Kai. --=20 PGP-KeyID =3D 0xE401B671927D4A5C I am not a robot. --Sig_/YDEQFYLCZWGw5j7u2ru5=EY Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJUhrP9AAoJEHBlTXxPsfWIj3oP/3VvAq8fVVM02tyHI1ZGCLGO YX+I+plC37NmAFQTjcVpTt7hUO+QBLWmkT9TkCmrmfQ9XaY/zxWiMPxAy1G+ecH4 o1o8vhOMGXbVpbVfXWGwXkp8dHagER+Rhd9Sx23JPRo3TuHhU6qkKex2/rbk6mVg 2+j74y5MA41jOBo+R4NdR98tqQ3dG/S2GdgQPFWjbZcrnS5r2UD8lcQIaUnyuRbJ nd1W6ckILDeOSnPWhHCJ6UIkWTwxWwJ1A7Ji1PaBG3MT8RWJPsySS31NY6pJVjRr lEefOEQpYPPP4bi2T0YIC6KA4OOmD/ZXDqFimnKNzGBQVa2dG7bU8yt6XCY2Kszf 2bKD2W/gglHTfa524xssCQI84qQwsn1BdAcHfUqUqMuIAQLvEOEESrawsrIWkBYk edeUhA/tcNgacVeD49TrUU1oVoHKEHBcuSBehcxg6p/uxSVSXzU/X9d/zrjsG3Pz p8ZiZLrPKS0qHNrjLzA0Nog/WSbAWCKnWqhv2cIJlH/Xro1HuVlj4i8NmzdexPkm o0IqL+PSl4O6vwQoWQTge+DZyWunNkGMJM4nH7ZGYJAI87+yvVxddHtsZFi/Iq99 J7WOmQagUStQgi7QK0EEHzGElBJi138Gw0CM8g4yvf1yUa4u4XgLMGYXvj+NSD+P S6YiEhkjSS68NIuxP6ff =u7id -----END PGP SIGNATURE----- --Sig_/YDEQFYLCZWGw5j7u2ru5=EY-- From owner-freebsd-stable@FreeBSD.ORG Tue Dec 9 09:04:22 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E3862E46 for ; Tue, 9 Dec 2014 09:04:22 +0000 (UTC) Received: from lmtp.galacsys.net (webmail.galacsys.net [IPv6:2001:1b78:0:1:d918:51d7:0:1]) by mx1.freebsd.org (Postfix) with ESMTP id AC7473E5 for ; Tue, 9 Dec 2014 09:04:22 +0000 (UTC) Received: from martymac.org (webmail.galacsys.net [217.24.81.215]) by lmtp.galacsys.net (Postfix) with ESMTP id EE09D1FA5DE4; Tue, 9 Dec 2014 10:04:20 +0100 (CET) From: "Ganael LAPLANCHE" To: Kai Gallasch ,freebsd-stable@freebsd.org Subject: Re: 10.1 RC4 r273903 - zpool scrub on ssd mirror - ahci command timeout X-Openwebmail-Date: Tue, 9 Dec 2014 10:04:20 +0100 Message-Id: <20141209090157.M14881@martymac.org> In-Reply-To: <20141209093405.6dd2c268@orwell> References: <20141106003240.344dedf6@orwell> <545AB64F.1060502@multiplay.co.uk> <20141106012739.509b96b5@orwell> <545ACCEF.5000300@multiplay.co.uk> <20141209093405.6dd2c268@orwell> X-Mailer: Open WebMail 2.01 20030425 X-OriginatingIP: 157.99.255.127 (ganael.laplanche@martymac.org) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Date: Tue, 09 Dec 2014 09:04:23 -0000 X-List-Received-Date: Tue, 09 Dec 2014 09:04:23 -0000 On Tue, 9 Dec 2014 09:34:05 +0100, Kai Gallasch wrote Hi Kai, > Any ideas (left) ? There is a PR for AHCI timeouts : https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195349 I don't know if it is related to your problem but maybe you can try the suggested workaround ? Regards, -- Ganael LAPLANCHE http://www.martymac.org | http://contribs.martymac.org FreeBSD: martymac , http://www.FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Tue Dec 9 09:52:59 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A9FA5791 for ; Tue, 9 Dec 2014 09:52:59 +0000 (UTC) Received: from mail-wi0-f175.google.com (mail-wi0-f175.google.com [209.85.212.175]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3E887B02 for ; Tue, 9 Dec 2014 09:52:58 +0000 (UTC) Received: by mail-wi0-f175.google.com with SMTP id l15so7274344wiw.8 for ; Tue, 09 Dec 2014 01:52:51 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=9alrQeN+iyjEhCqwcAUGnxnO55FFm7MQF8UhkiXgrZo=; b=EetrPebDBIxTgzlRrY4J8O2Ls7bmpEJpo1aK2NgHl1btsc1OAUdkFd3C4yUzpXzD07 B2O5Xq7B1c4fDGRaboZPVtVsxMKJdXv5b3u9cy5PUGgbzGEn9gZOVZbGut7qx647/p8O oWctO+Zto85+P1tgHRIlj12HiwSUugT/bbavOul+rkm0CzYHoApFgDJyZNH2YneTCNG2 /PS02JL1gnkAmKw6PYBDagvRDIvOqezkDD9KIAu9ugz4gkISNE/0CiB4FyUbHPcNCH5/ qTOi1RiwkG0+QkUScrR6sETxNkCkln55tu3pEsnE89W+a+nt/cHBHTUfzqgYrqx8/enA YBUQ== X-Gm-Message-State: ALoCoQmwscjDMIAhqjUc3m600zzBCqb5CqupG8GeR5WWKtAxOsIZlOlO6Ac8ScSz+Fka3GJ9ClUM X-Received: by 10.180.76.201 with SMTP id m9mr30304580wiw.52.1418117234585; Tue, 09 Dec 2014 01:27:14 -0800 (PST) Received: from [10.10.1.68] (82-69-141-170.dsl.in-addr.zen.co.uk. [82.69.141.170]) by mx.google.com with ESMTPSA id bj3sm13040892wib.3.2014.12.09.01.27.13 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 09 Dec 2014 01:27:13 -0800 (PST) Message-ID: <5486BFF6.10309@multiplay.co.uk> Date: Tue, 09 Dec 2014 09:25:10 +0000 From: Steven Hartland User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: 10.1 RC4 r273903 - zpool scrub on ssd mirror - ahci command timeout References: <20141106003240.344dedf6@orwell> <545AB64F.1060502@multiplay.co.uk> <20141106012739.509b96b5@orwell> <545ACCEF.5000300@multiplay.co.uk> <20141209093405.6dd2c268@orwell> In-Reply-To: <20141209093405.6dd2c268@orwell> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2014 09:52:59 -0000 On 09/12/2014 08:34, Kai Gallasch wrote: > Am Thu, 06 Nov 2014 01:20:47 +0000 > schrieb Steven Hartland : > >> Try recabling and re-seating, if it still happens try to identify if >> its the disk or backplane by moving it in the chassis. We had a >> machine here recently where it was backplane issue and simply >> replacing it fixed the issue. > Steven. > > In the last weeks I took some time to single out the reason for the AHCI > timeouts with the two Samsung SSD drives. > > Just for the record, my original post on the FreeBSD mailing > list archive: > > http://lists.freebsd.org/pipermail/freebsd-stable/2014-November/080914.html > > > I changed / tried the following to get rid of the AHCI timouts, but no > chance, they still show :-/ > > Hardware: > > - Changed all four SATA cables with cables of an identical spare server > - Changed all four SATA cables with certified SATA3 cables > - Replaced the 2.5" -> 3.5" drive converters with ones of another > manufacturer > - Replaced the drive backplane of the server > - Directly hooking the two SSDs up to the SATA connectors on the > mainboard > - Experimentally put an LSI 9212-4i4e PCIe SATA/SAS Controller into the > server and and connected the SATA cables to it. > - Same as before, but using the certified SATA3 cables > - Same as before, but this time connecting the two SSDs directly to the > 9212-4i4e > - Same as before, connecting the two SSD directly to the 9212-4i4e, but > this time with the original SATA cables > > > BIOS: > - Temporarily disabled Power Management > - Tried disabling "Enable Hot Plug" Option > > > The difference between using the SATA connectors of the mainboard and > using the LSI 9212-4i4e is, that the LSI controller seems to be more > picky about CRC errors on the SATA bus and bus problems even show > without starting a zfs scrub. When doing a scrub using the LSI > controller there are plenty of timeouts and in one test, one of the SSD > drives even disappeard from the SATA bus. > > Of course all the time during testing the two Hitachi non-SSD SATA > drives did not show any problems at all - although also connected to > the mainboard or the LSI controller during the testing. > > So I now think the whole problem centers around the Samsung 850 PRO > 512GB SSDs. Too bad I do not have the budget to just buy two Intel (or > other) SSDs of similar size and see if the timeouts disappear.. > > I wonder if this is a firmware issue with the drive or just some > misguided fancy energy saving feature of this particular drive > model causing the whole trouble. > > Both drives have serial numbers not far apart and smartctl claims there > are no errors on the SSDs. > > Any ideas (left) ? > Have you tried dropping the speed on the ahci controller e.g. hint.ahcich.0.sata_rev="2" I can't say I've used Samsung 850 Pro's but we do have plenty of 840's, which are attached to LSI controllers in service here and never had an issue. The other issue might have is bad MB, where the issue is actually occurring in memory. Given you have replaced the controller and cables this might be your issue. So try replacing the Memory, MB, CPU etc. The last time I had really bad corruption issues the problem turned out to be dodgy Intel CPU. Also someone posted on the list not yesterday they had constant CKSUM errors from ZFS and it turned out to be their power causing the issue and running the server of a sign wave based UPS made the problem go away. Regards Steve From owner-freebsd-stable@FreeBSD.ORG Tue Dec 9 10:09:03 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DF8F5C2A for ; Tue, 9 Dec 2014 10:09:03 +0000 (UTC) Received: from smtp.free.de (smtp.free.de [91.204.6.103]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5ABC0C53 for ; Tue, 9 Dec 2014 10:09:03 +0000 (UTC) Received: (qmail 39241 invoked from network); 9 Dec 2014 11:08:59 +0100 Received: from smtp.free.de (HELO orwell) (k@free.de@[91.204.4.103]) (envelope-sender ) by smtp.free.de (qmail-ldap-1.03) with AES128-SHA encrypted SMTP for ; 9 Dec 2014 11:08:59 +0100 Date: Tue, 9 Dec 2014 11:08:57 +0100 From: Kai Gallasch To: freebsd-stable@freebsd.org Subject: Re: 10.1 RC4 r273903 - zpool scrub on ssd mirror - ahci command timeout Message-ID: <20141209110857.6bb9bcbd@orwell> In-Reply-To: <20141209090157.M14881@martymac.org> References: <20141106003240.344dedf6@orwell> <545AB64F.1060502@multiplay.co.uk> <20141106012739.509b96b5@orwell> <545ACCEF.5000300@multiplay.co.uk> <20141209093405.6dd2c268@orwell> <20141209090157.M14881@martymac.org> Organization: FREE! X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.23; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/4ki=HT6Fq8P1xA3z3vESpzF"; protocol="application/pgp-signature" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2014 10:09:04 -0000 --Sig_/4ki=HT6Fq8P1xA3z3vESpzF Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Am Tue, 9 Dec 2014 09:04:26 +0000 (UTC) schrieb "Ganael LAPLANCHE" : > On Tue, 9 Dec 2014 09:34:05 +0100, Kai Gallasch wrote >=20 > Hi Kai, >=20 > > Any ideas (left) ? >=20 > There is a PR for AHCI timeouts : >=20 > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D195349 >=20 > I don't know if it is related to your problem but maybe you can try > the suggested workaround ? Thank you for this information. But no. My problem seems to be unrelated.. K. echo 'hint.ahci.0.msi=3D"0"' >> /boot/loader.conf After reboot: # zpool scrub ssdpool # zpool status ssdpool pool: ssdpool state: ONLINE status: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected. action: Determine if the device needs to be replaced, and clear the errors using 'zpool clear' or replace the device with 'zpool replace'. see: http://illumos.org/msg/ZFS-8000-9P scan: scrub in progress since Tue Dec 9 10:36:24 2014 5.36G scanned out of 115G at 166M/s, 0h11m to go 24.5K repaired, 4.65% done config: NAME STATE READ WRITE CKSUM ssdpool ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 gpt/ssdpool0 ONLINE 0 0 13 (repairing) gpt/ssdpool1 ONLINE 0 0 0 errors: No known data errors After the zpool scrub finished: # zpool status ssdpool pool: ssdpool state: ONLINE status: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected. action: Determine if the device needs to be replaced, and clear the errors using 'zpool clear' or replace the device with 'zpool replace'. see: http://illumos.org/msg/ZFS-8000-9P scan: scrub repaired 38.5K in 0h9m with 0 errors on Tue Dec 9 10:45:58 2014 config: NAME STATE READ WRITE CKSUM ssdpool ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 gpt/ssdpool0 ONLINE 0 0 15 gpt/ssdpool1 ONLINE 0 0 4 # zpool clear ssdpool # zpool scrub ssdpool This "zpool scrub" run one SSD drive is lost during the scrub :-/ A "camcontrol rescan all" does not bring the missing ssd drive back.. # zpool status ssdpool pool: ssdpool state: DEGRADED status: One or more devices could not be opened. Sufficient replicas exist for the pool to continue functioning in a degraded state. action: Attach the missing device and online it using 'zpool online'. see: http://illumos.org/msg/ZFS-8000-2Q scan: scrub canceled on Tue Dec 9 10:58:42 2014 config: NAME STATE READ WRITE CKSUM ssdpool DEGRADED 0 0 0 mirror-0 DEGRADED 0 0 0 gpt/ssdpool0 ONLINE 0 0 0 2481016284460057031 UNAVAIL 297 215 47 was /dev/gpt/ssdpool1 ahcich3: Timeout on slot 24 port 0 ahcich3: is 00000000 cs fc00001f ss ff00001f rs ff00001f tfd 40 serr 000000= 00 cmd 0024d917 (ada3:ahcich3:0:0:0): READ_FPDMA_QUEUED. ACB: 60 24 1b 4a c6 40 1e 00 00 00= 00 00 (ada3:ahcich3:0:0:0): CAM status: Command timeout (ada3:ahcich3:0:0:0): Retrying command ahcich3: AHCI reset: device not ready after 31000ms (tfd =3D 00000080) ahcich3: Timeout on slot 4 port 0 ahcich3: is 00000000 cs 00000010 ss 00000000 rs 00000010 tfd 80 serr 000000= 00 cmd 0024c417 (aprobe0:ahcich3:0:0:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00 0= 0 00 (aprobe0:ahcich3:0:0:0): CAM status: Command timeout (aprobe0:ahcich3:0:0:0): Retrying command ahcich3: AHCI reset: device not ready after 31000ms (tfd =3D 00000080) ahcich3: Timeout on slot 4 port 0 ahcich3: is 00000000 cs 00000010 ss 00000000 rs 00000010 tfd 80 serr 000000= 00 cmd 0024c417 (aprobe0:ahcich3:0:0:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00 0= 0 00 (aprobe0:ahcich3:0:0:0): CAM status: Command timeout (aprobe0:ahcich3:0:0:0): Error 5, Retries exhausted ahcich3: AHCI reset: device not ready after 31000ms (tfd =3D 00000080) ahcich3: Timeout on slot 4 port 0 ahcich3: is 00000000 cs 00000010 ss 00000000 rs 00000010 tfd 80 serr 000000= 00 cmd 0024c417 (aprobe0:ahcich3:0:0:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00 0= 0 00 (aprobe0:ahcich3:0:0:0): CAM status: Command timeout (aprobe0:ahcich3:0:0:0): Error 5, Retry was blocked ada3 at ahcich3 bus 0 scbus3 target 0 lun 0 ada3: s/n S1SXNSAFA06835A detached ahcich3: AHCI reset: device not ready after 31000ms (tfd =3D 00000080) ahcich3: Timeout on slot 4 port 0 ahcich3: is 00000000 cs 00000010 ss 00000000 rs 00000010 tfd 80 serr 000000= 00 cmd 0024c417 (aprobe0:ahcich3:0:0:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00 0= 0 00 (aprobe0:ahcich3:0:0:0): CAM status: Command timeout (aprobe0:ahcich3:0:0:0): Retrying command ahcich3: AHCI reset: device not ready after 31000ms (tfd =3D 00000080) ahcich3: Timeout on slot 4 port 0 ahcich3: is 00000000 cs 00000010 ss 00000000 rs 00000010 tfd 80 serr 000000= 00 cmd 0024c417 (aprobe0:ahcich3:0:0:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00 0= 0 00 (aprobe0:ahcich3:0:0:0): CAM status: Command timeout (aprobe0:ahcich3:0:0:0): Error 5, Retries exhausted ahcich3: AHCI reset: device not ready after 31000ms (tfd =3D 00000080) ahcich3: Poll timeout on slot 4 port 0 ahcich3: is 00000000 cs 00000010 ss 00000000 rs 00000010 tfd 80 serr 000000= 00 cmd 0024c417 (aprobe0:ahcich3:0:0:0): NOP. ACB: 00 00 00 00 00 00 00 00 00 00 00 00 (aprobe0:ahcich3:0:0:0): CAM status: Command timeout (aprobe0:ahcich3:0:0:0): Error 5, Retries exhausted ahcich3: Timeout on slot 4 port 0 ahcich3: is 00000000 cs 00000010 ss 00000000 rs 00000010 tfd 80 serr 000000= 00 cmd 0024c417 (ada3:ahcich3:0:0:0): SETFEATURES ENABLE RCACHE. ACB: ef aa 00 00 00 40 00 = 00 00 00 00 00 (ada3:ahcich3:0:0:0): CAM status: Unconditionally Re-queue Request (ada3:ahcich3:0:0:0): Error 5, Periph was invalidated ahcich3: AHCI reset: device not ready after 31000ms (tfd =3D 00000080) ahcich3: Poll timeout on slot 4 port 0 ahcich3: is 00000000 cs 00000010 ss 00000000 rs 00000010 tfd 80 serr 000000= 00 cmd 0024c417 (aprobe0:ahcich3:0:0:0): NOP. ACB: 00 00 00 00 00 00 00 00 00 00 00 00 (aprobe0:ahcich3:0:0:0): CAM status: Command timeout (aprobe0:ahcich3:0:0:0): Error 5, Retries exhausted ahcich3: Timeout on slot 4 port 0 ahcich3: is 00000000 cs 0001fff0 ss 0001fff0 rs 0001fff0 tfd 80 serr 000000= 00 cmd 0024c417 (ada3:ahcich3:0:0:0): READ_FPDMA_QUEUED. ACB: 60 24 1b 4a c6 40 1e 00 00 00= 00 00 (ada3:ahcich3:0:0:0): CAM status: Command timeout (ada3:ahcich3:0:0:0): Error 5, Periph was invalidated (ada3:ahcich3:0:0:0): READ_FPDMA_QUEUED. ACB: 60 15 3f 4a c6 40 1e 00 00 00= 00 00 (ada3:ahcich3:0:0:0): CAM status: Unconditionally Re-queue Request (ada3:ahcich3:0:0:0): Error 5, Periph was invalidated (ada3:ahcich3:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 08 ed c4 21 40 20 00 00 0= 0 00 00 (ada3:ahcich3:0:0:0): CAM status: Unconditionally Re-queue Request (ada3:ahcich3:0:0:0): Error 5, Periph was invalidated (ada3:ahcich3:0:0:0): READ_FPDMA_QUEUED. ACB: 60 00 71 19 d3 40 04 00 00 01= 00 00 (ada3:ahcich3:0:0:0): CAM status: Unconditionally Re-queue Request (ada3:ahcich3:0:0:0): Error 5, Periph was invalidated (ada3:ahcich3:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 f0 bb 43 23 40 20 00 00 0= 0 00 00 (ada3:ahcich3:0:0:0): CAM status: Unconditionally Re-queue Request (ada3:ahcich3:0:0:0): Error 5, Periph was invalidated (ada3:ahcich3:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 e8 bb 45 23 40 20 00 00 0= 0 00 00 (ada3:ahcich3:0:0:0): CAM status: Unconditionally Re-queue Request (ada3:ahcich3:0:0:0): Error 5, Periph was invalidated (ada3:ahcich3:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 e8 bb 46 23 40 20 00 00 0= 0 00 00 (ada3:ahcich3:0:0:0): CAM status: Unconditionally Re-queue Request (ada3:ahcich3:0:0:0): Error 5, Periph was invalidated (ada3:ahcich3:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 e8 bb 47 23 40 20 00 00 0= 0 00 00 (ada3:ahcich3:0:0:0): CAM status: Unconditionally Re-queue Request (ada3:ahcich3:0:0:0): Error 5, Periph was invalidated (ada3:ahcich3:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 e8 bb 48 23 40 20 00 00 0= 0 00 00 (ada3:ahcich3:0:0:0): CAM status: Unconditionally Re-queue Request (ada3:ahcich3:0:0:0): Error 5, Periph was invalidated (ada3:ahcich3:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 e8 bb 49 23 40 20 00 00 0= 0 00 00 (ada3:ahcich3:0:0:0): CAM status: Unconditionally Re-queue Request (ada3:ahcich3:0:0:0): Error 5, Periph was invalidated (ada3:ahcich3:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 e8 bb 4a 23 40 20 00 00 0= 0 00 00 (ada3:ahcich3:0:0:0): CAM status: Unconditionally Re-queue Request (ada3:ahcich3:0:0:0): Error 5, Periph was invalidated (ada3:ahcich3:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 e8 bb 4b 23 40 20 00 00 0= 0 00 00 (ada3:ahcich3:0:0:0): CAM status: Unconditionally Re-queue Request (ada3:ahcich3:0:0:0): Error 5, Periph was invalidated (ada3:ahcich3:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 e8 bb 4c 23 40 20 00 00 0= 0 00 00 (ada3:ahcich3:0:0:0): CAM status: Unconditionally Re-queue Request (ada3:ahcich3:0:0:0): Error 5, Periph was invalidated (ada3:ahcich3:0:0:0): Periph destroyed ahcich3: AHCI reset: device not ready after 31000ms (tfd =3D 00000080) ahcich3: Poll timeout on slot 16 port 0 ahcich3: is 00000000 cs 00010000 ss 00000000 rs 00010000 tfd 80 serr 000000= 00 cmd 0024d017 (aprobe0:ahcich3:0:0:0): NOP. ACB: 00 00 00 00 00 00 00 00 00 00 00 00 (aprobe0:ahcich3:0:0:0): CAM status: Command timeout (aprobe0:ahcich3:0:0:0): Error 5, Retries exhausted --=20 PGP-KeyID =3D 0xE401B671927D4A5C I am a robot. --Sig_/4ki=HT6Fq8P1xA3z3vESpzF Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJUhso5AAoJEHBlTXxPsfWIUfAP/3PBpfvPXY/eCbXtF5Kh+08+ pTASCmwlAjyB2HGQG3MkknyhcDzLU9Anaht+R4qAiUF579i5Zzn/2Vg/516h+Fon HSIZPQUOrrvKbAqY5gAaAwLWiIBtphL1jt1tZBtLlDLA0cZ6DsRa7XWlsCrtoraV G54kTGczCc3gZR7m7QJr0b9CPA8DNp0dEUZVUpIN3fq7NRWXkp88TY7AJyHclkPz LHH8DMK8/uLwwCFkrmUIpYRdAsu1VdvWvYMDiFa36v+ZbbG+f1HPyJa6GiSIHX3C Tdrb5KWij8eNdRXFsoil4dTIQXfqdKOfgcVZVXI7cztI5LBqUrHNMp7hxgHvF8QT u7XPn+GhBMkbPCGZJCu5cl37gz7Mom2mHa96eMTj8Ezcbg8OJCtPCdkluDwEpaNK mxE8OprktNDRD9jcCUShC6ZzisEp0phWunobaO74pyZ3GSOwHnJBx8YOR56Gb7x9 KwF033fi3TRGvf32P0GlmQbJc2U1/q9tNmaoeubOsIjOliUE8EBKP/vu+zSj+3sY iwpvIjJFhhs42iAPrmESJzk3kwjZl2ZSHMLrQHLRlX07q1GVg6a5xKGJY1DyXtLR QA0XWbcKabXEb+Yt/AkMI1CKQp6fvJoJVcFij03Ln8iQ96Iiu8tlxNnkbsEsqRQ4 NRaJ8rchIfPs0HlF0Hqv =MglT -----END PGP SIGNATURE----- --Sig_/4ki=HT6Fq8P1xA3z3vESpzF-- From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 03:12:45 2014 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D57B38AB for ; Wed, 10 Dec 2014 03:12:45 +0000 (UTC) Received: from smtp.des.no (smtp.des.no [194.63.250.102]) by mx1.freebsd.org (Postfix) with ESMTP id 99B8F130 for ; Wed, 10 Dec 2014 03:12:45 +0000 (UTC) Received: from nine.des.no (smtp.des.no [194.63.250.102]) by smtp-int.des.no (Postfix) with ESMTP id 5C57A9A01; Wed, 10 Dec 2014 03:12:44 +0000 (UTC) Received: by nine.des.no (Postfix, from userid 1001) id E1F5F31ED; Wed, 10 Dec 2014 04:12:44 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Dmitry Morozovsky Subject: Re: /bin/freebsd-version does not get rebuilt in NO_CLEAN build: References: Date: Wed, 10 Dec 2014 04:12:44 +0100 In-Reply-To: (Dmitry Morozovsky's message of "Sun, 23 Nov 2014 00:34:06 +0300 (MSK)") Message-ID: <86ppbs42qb.fsf@nine.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2014 03:12:45 -0000 Dmitry Morozovsky writes: > I'm usually using -DNO_CLEAN builds including upgrades; however, it > turns out that freebsd-version utility does not depend really on > newvers.sh [...] Should be fixed in r275659. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 11:05:38 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 17BE0531 for ; Wed, 10 Dec 2014 11:05:38 +0000 (UTC) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 89FC8E25 for ; Wed, 10 Dec 2014 11:05:37 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.14.5/8.14.5) with ESMTP id sBAB0x5l004714; Wed, 10 Dec 2014 14:00:59 +0300 (MSK) (envelope-from marck@rinet.ru) Date: Wed, 10 Dec 2014 14:00:59 +0300 (MSK) From: Dmitry Morozovsky To: =?ISO-8859-15?Q?Dag-Erling_Sm=F8rgrav?= Subject: Re: /bin/freebsd-version does not get rebuilt in NO_CLEAN build: In-Reply-To: <86ppbs42qb.fsf@nine.des.no> Message-ID: References: <86ppbs42qb.fsf@nine.des.no> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (woozle.rinet.ru [0.0.0.0]); Wed, 10 Dec 2014 14:02:06 +0300 (MSK) Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2014 11:05:38 -0000 On Wed, 10 Dec 2014, Dag-Erling Sm?rgrav wrote: > > I'm usually using -DNO_CLEAN builds including upgrades; however, it > > turns out that freebsd-version utility does not depend really on > > newvers.sh [...] > > Should be fixed in r275659. Indeed. Thanks! -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck@FreeBSD.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 13:20:55 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9836AB3 for ; Wed, 10 Dec 2014 13:20:55 +0000 (UTC) Received: from smtp24.services.sfr.fr (smtp24.services.sfr.fr [93.17.128.83]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 57A60F4B for ; Wed, 10 Dec 2014 13:20:54 +0000 (UTC) Received: from filter.sfr.fr (localhost [93.4.34.137]) by msfrf2418.sfr.fr (SMTP Server) with ESMTP id 4675E7000066 for ; Wed, 10 Dec 2014 14:13:31 +0100 (CET) Authentication-Results: sfrmc.priv.atos.fr; dkim=none (no signature); dkim-adsp=none (no policy) header.from=listjm@club-internet.fr Received: from [192.168.1.67] (137.34.4.93.rev.sfr.net [93.4.34.137]) by msfrf2418.sfr.fr (SMTP Server) with ESMTP id 209FC70000A8 for ; Wed, 10 Dec 2014 14:13:31 +0100 (CET) X-SFR-UUID: 20141210131331133.209FC70000A8@msfrf2418.sfr.fr Message-ID: <548846F8.4080208@club-internet.fr> Date: Wed, 10 Dec 2014 14:13:28 +0100 From: Juan =?iso-8859-1?b?UmFt824=?= Molina Menor User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: System hang on shutdown when running freebsd-update Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2014 13:20:55 -0000 > >/ Another update. I narrowed down the issue due to /sbin/init being replaced. This might be the magic that freebsd-update does to make the crash happen. (Although there might be more situations that cause a hang.) > />/ > />/ I can completely reliably trigger the hang on a default 10.1-RELEASE install on UFS2 in VMware Fusion with the following procedure: > />/ > />/ # chflags noschg /sbin/init > />/ # cp -Rp /sbin/init /sbin/init2 > />/ # rm -f /sbin/init > />/ # mv /sbin/init2 /sbin/init > />/ # chflags schg /sbin/init > />/ # reboot > />/ => Hang after "All buffers synced." > /These commands do not trigger the issue here on a 10.1-RELEASE on VMware > Player, but do it in a real system with the same release, both i386. > When I last freebsd-updated this latter machine from 10.0 to > 10.1-RELEASE, I also remember seeing the hang on shutdown. > > Hope it helps, > Juan The hang occurs again when running freebsd-update to install the security advisories of today on a 10.1-RELEASE i386. No problem under VMWare, same version. Best regards, Juan From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 13:37:02 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 41152867 for ; Wed, 10 Dec 2014 13:37:02 +0000 (UTC) Received: from icp-osb-irony-out1.external.iinet.net.au (icp-osb-irony-out1.external.iinet.net.au [203.59.1.210]) by mx1.freebsd.org (Postfix) with ESMTP id B9B4E1B4 for ; Wed, 10 Dec 2014 13:37:01 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AiAGANBLiFR90bfD/2dsb2JhbABZgwa0YQEBAQEBAQaYNwKBFxYBAQEBAX2EAwEFMgFGEAsNFCUPBRgdFBOIN9dMAQEBAQYCIIYNiXYHgyGBFQWWcoENhF0lhR6GLoQCKjCCQwEBAQ X-IronPort-AV: E=Sophos;i="5.07,552,1413216000"; d="scan'208";a="281076578" Received: from unknown (HELO smtp.phoenix) ([125.209.183.195]) by icp-osb-irony-out1.iinet.net.au with ESMTP; 10 Dec 2014 21:36:59 +0800 Received: by smtp.phoenix (Postfix, from userid 1001) id 89A7175D; Thu, 11 Dec 2014 00:36:58 +1100 (AEDT) Date: Thu, 11 Dec 2014 00:36:58 +1100 From: andrew clarke To: Juan =?iso-8859-1?Q?Ram=F3n?= Molina Menor Subject: Re: System hang on shutdown when running freebsd-update Message-ID: <20141210133658.GA12721@ozzmosis.com> References: <548846F8.4080208@club-internet.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <548846F8.4080208@club-internet.fr> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2014 13:37:02 -0000 On Wed 2014-12-10 14:13:28 UTC+0100, Juan Ramón Molina Menor (listjm@club-internet.fr) wrote: > > >/ Another update. I narrowed down the issue due to /sbin/init being > > >replaced. This might be the magic that freebsd-update does to make the > > >crash happen. (Although there might be more situations that cause a > > >hang.) > > > > />/ I can completely reliably trigger the hang on a default > > />/ 10.1-RELEASE install on UFS2 in VMware Fusion with the following > > >>/ procedure: > > />/ > > />/ # chflags noschg /sbin/init > > />/ # cp -Rp /sbin/init /sbin/init2 > > />/ # rm -f /sbin/init > > />/ # mv /sbin/init2 /sbin/init > > />/ # chflags schg /sbin/init > > />/ # reboot > > />/ => Hang after "All buffers synced." > > /These commands do not trigger the issue here on a 10.1-RELEASE on VMware > > Player, but do it in a real system with the same release, both i386. > > When I last freebsd-updated this latter machine from 10.0 to > > 10.1-RELEASE, I also remember seeing the hang on shutdown. > > > > Hope it helps, > > Juan > > The hang occurs again when running freebsd-update to install the > security advisories of today on a 10.1-RELEASE i386. No problem under > VMWare, same version. > > Best regards, > Juan A FreeBSD 10.1-REL amd64 VM here also hangs after /sbin/reboot is run, after installing updates with freebsd-update. The VM runs under VirtualBox on an Ubuntu 14.04 host. On hard-resetting the VM, it appears the filesystem (UFS) wasn't flushed: Dec 11 00:29:52 vbox-freebsd kernel: WARNING: / was not properly dismounted Regards Andrew From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 14:28:43 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7202A9E7 for ; Wed, 10 Dec 2014 14:28:43 +0000 (UTC) Received: from smtp24.services.sfr.fr (smtp24.services.sfr.fr [93.17.128.83]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0AD5B9D2 for ; Wed, 10 Dec 2014 14:28:42 +0000 (UTC) Received: from filter.sfr.fr (localhost [93.4.34.137]) by msfrf2418.sfr.fr (SMTP Server) with ESMTP id DC6BE70000A8; Wed, 10 Dec 2014 15:28:39 +0100 (CET) Authentication-Results: sfrmc.priv.atos.fr; dkim=none (no signature); dkim-adsp=none (no policy) header.from=listjm@club-internet.fr Received: from [192.168.1.67] (137.34.4.93.rev.sfr.net [93.4.34.137]) by msfrf2418.sfr.fr (SMTP Server) with ESMTP id A12B770000A5; Wed, 10 Dec 2014 15:28:39 +0100 (CET) X-SFR-UUID: 20141210142839660.A12B770000A5@msfrf2418.sfr.fr Message-ID: <54885894.2060006@club-internet.fr> Date: Wed, 10 Dec 2014 15:28:36 +0100 From: Juan =?iso-8859-1?b?UmFt824=?= Molina Menor User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: andrew clarke Subject: Re: System hang on shutdown when running freebsd-update References: <548846F8.4080208@club-internet.fr> <20141210133658.GA12721@ozzmosis.com> In-Reply-To: <20141210133658.GA12721@ozzmosis.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2014 14:28:43 -0000 El 10/12/2014 14:36, andrew clarke escribió: > On Wed 2014-12-10 14:13:28 UTC+0100, Juan Ramón Molina Menor (listjm@club-internet.fr) wrote: > >>>> / Another update. I narrowed down the issue due to /sbin/init being >>>> replaced. This might be the magic that freebsd-update does to make the >>>> crash happen. (Although there might be more situations that cause a >>>> hang.) >>> >>> />/ I can completely reliably trigger the hang on a default >>> />/ 10.1-RELEASE install on UFS2 in VMware Fusion with the following >>>>> / procedure: >>> />/ >>> />/ # chflags noschg /sbin/init >>> />/ # cp -Rp /sbin/init /sbin/init2 >>> />/ # rm -f /sbin/init >>> />/ # mv /sbin/init2 /sbin/init >>> />/ # chflags schg /sbin/init >>> />/ # reboot >>> />/ => Hang after "All buffers synced." >>> /These commands do not trigger the issue here on a 10.1-RELEASE on VMware >>> Player, but do it in a real system with the same release, both i386. >>> When I last freebsd-updated this latter machine from 10.0 to >>> 10.1-RELEASE, I also remember seeing the hang on shutdown. >>> >>> Hope it helps, >>> Juan >> >> The hang occurs again when running freebsd-update to install the >> security advisories of today on a 10.1-RELEASE i386. No problem under >> VMWare, same version. >> >> Best regards, >> Juan > > A FreeBSD 10.1-REL amd64 VM here also hangs after /sbin/reboot is run, > after installing updates with freebsd-update. The VM runs under > VirtualBox on an Ubuntu 14.04 host. > > On hard-resetting the VM, it appears the filesystem (UFS) wasn't flushed: > > Dec 11 00:29:52 vbox-freebsd kernel: WARNING: / was not properly dismounted Yes, I forgot that, same here on bare metal. > > Regards > Andrew > From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 15:23:54 2014 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D9152D38 for ; Wed, 10 Dec 2014 15:23:54 +0000 (UTC) Received: from nm48-vm10.bullet.mail.gq1.yahoo.com (nm48-vm10.bullet.mail.gq1.yahoo.com [67.195.87.230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A034CB9 for ; Wed, 10 Dec 2014 15:23:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1418225028; bh=xMlQdy7hQHhaz81j7sGak31w3dDXvXOPzSBbXvmYXHI=; h=Date:From:Reply-To:To:Subject:From:Subject; b=TtewUApLPPPhuUKCXoIGLDZSX8bsqc+J9uqTo80zDStqLv2JJi6kuI48z9AGjiZNUOc6nk8f7WCypOmpMjdU6rxCpoDaH+5A/G07D7uCdv+GIosU6CB7XI9vF/pwLRcN4YcwEIiu+EFT6w3qJ7v8TYJAsaZaenB0/JjO3p/DeqBK+2zltSzJb88leRaGKombz82ICxROvSEcwidnEIllg5CZ43XBIxZe13SKXRcmwv/Fr5j4QJkWR2nTSfFL4kg+faadI4PuPt/29U6b80JAg+uvCDTCPFWlWt0Bbuy0JQBXqqwf52ELVCcGYs6SRXAaZVj8+Y8tGmigqy6RjyFoxg== DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s2048; d=yahoo.com; b=B4F7iVYy/qPEL2VKKhqlU5gEWDOtsquPQyfZyYxkwuXOXqDNk3hQs5urrltlWImCUqheJpxP8+WrYUIHlh0Y1JM5F7R0gs7q9snfbf7KzwgmnK07bur+xxrWaNVZr0wnga7453MNuA2vgeG2i6RAT8S0ThYB2EUbodSWWRGz0xZdObggUoNXNRn+ekZjKclNMrjymjSsEqaWgZvM0ii4zd825thg7Cq7Kkosja0B8GUIV8oyMO+6GO79MxO8m2elY7Fwz8x4KXbY7IY9NsJI1LSzycQqvr75yVxCDYbCs/jrYc9Q1xBwCm4zSesX1Eo9pWhfZr7bDr0lAPDY8FID/A==; Received: from [127.0.0.1] by nm48.bullet.mail.gq1.yahoo.com with NNFMP; 10 Dec 2014 15:23:48 -0000 Received: from [98.137.12.63] by nm48.bullet.mail.gq1.yahoo.com with NNFMP; 10 Dec 2014 15:20:47 -0000 Received: from [98.139.215.142] by tm8.bullet.mail.gq1.yahoo.com with NNFMP; 10 Dec 2014 15:20:46 -0000 Received: from [98.139.212.224] by tm13.bullet.mail.bf1.yahoo.com with NNFMP; 10 Dec 2014 15:20:46 -0000 Received: from [127.0.0.1] by omp1033.mail.bf1.yahoo.com with NNFMP; 10 Dec 2014 15:20:46 -0000 X-Yahoo-Newman-Property: ymail-4 X-Yahoo-Newman-Id: 382584.80744.bm@omp1033.mail.bf1.yahoo.com X-YMail-OSG: .._kasYVM1n3kTXJlWxEQn.YzheGO6VyjdxYtQwnYs1sWAg2VC_S6VdrhwgPvAO 5.foEKw2SfF7zDaYKjYRiTtUeHHjT4dQ9d.rvJ91IOsnQ5VaZ8ULXn4xlN5aYfiqMkIMXpgGfyAp 6jVz1A9xtbHaojSibtzYElOWS3nyu.DWrtsyPAt81QUzIBFST7M8RQquNQY9ypRfeakzuPafIrpZ 1MjbZeXBeDhqQMUMP5nV7hd7DGsKXfAcYG8bz5GCXi2gaUwPnKIKyF.jYBhayqCEgdFWwnuNc2sv FtuF3lUBT_9fdDJkhP17LJ8O8WO6tQr6iO4Ks6eiws2QqObiEtWVeK_W34ztcfFMktoCh9C8WUfy bSpzStM9km48DW8VIMA_TipQ8RBxIKnR.R3jawGnH5ifMITN5rM58TJvLpx6u6x2yPihiJlzeyno ve3vsDNH6AEml7dri8h8MLC9mgN63F4KtM_sBPcCPl1FNStfv1kswJp6TZUsaAzW1793PKM9aMTd xIPrCsQ-- Received: by 76.13.27.54; Wed, 10 Dec 2014 15:20:45 +0000 Date: Wed, 10 Dec 2014 15:20:45 +0000 (UTC) From: Filippo Moretti Reply-To: Filippo Moretti To: "stable@freebsd.org" Message-ID: <1192938802.7895425.1418224845347.JavaMail.yahoo@jws10663.mail.bf1.yahoo.com> Subject: Kbd problem in 10.1-STABLE MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2014 15:23:54 -0000 My kbd (Logitech Deluxe 660 cordless) no longer works after updating 10.1-S= TABLE from November 24 to December 8.The kernel configuration file is uncha= nged,the mouse which is on the same receiver works.root@sting:/home/filippo= # uname -a FreeBSD sting 10.1-STABLE FreeBSD 10.1-STABLE #6 r274620: Mon Nov 24 19:02:= 17 CET 2014=C2=A0=C2=A0=C2=A0=C2=A0 root@sting:/usr/obj/usr/src/sys/STING_V= T=C2=A0 i386 I booted kernel.old and everything works. dmesgCopyright (c) 1992-2014 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 The Regents of the University of= California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 10.1-STABLE #6 r274620: Mon Nov 24 19:02:17 CET 2014 =C2=A0=C2=A0=C2=A0 root@sting:/usr/obj/usr/src/sys/STING_VT i386 FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512 VT: running with driver "vga". CPU: Intel(R) Pentium(R) 4 CPU 3.20GHz (3200.05-MHz 686-class CPU) =C2=A0 Origin =3D "GenuineIntel"=C2=A0 Id =3D 0xf41=C2=A0 Family =3D 0xf=C2= =A0 Model =3D 0x4=C2=A0 Stepping =3D 1 =C2=A0 Features=3D0xbfebfbff =C2=A0 Features2=3D0x441d =C2=A0 AMD Features=3D0x100000 =C2=A0 TSC: P-state invariant real memory=C2=A0 =3D 4294967296 (4096 MB) avail memory =3D 3016171520 (2876 MB) Event timer "LAPIC" quality 400 ACPI APIC Table: FreeBSD/SMP: 1 package(s) x 1 core(s= ) x 2 HTT threads =C2=A0cpu0 (BSP): APIC ID:=C2=A0 0 =C2=A0cpu1 (AP/HT): APIC ID:=C2=A0 1 ioapic0 irqs 0-23 on motherboard random: initialized acpi0: on motherboard acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, b7f00000 (3) failed cpu0: on acpi0 cpu1: on acpi0 attimer0: port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 atrtc0: port 0x70-0x71 irq 8 on acpi0 Event timer "RTC" frequency 32768 Hz quality 0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0x9800-0x98ff mem 0xc0000000-0xc7fff= fff,0xd0000000-0xd000ffff irq 16 at device 0.0 on pci1 vgapci1: mem 0xdf9d0000-0xdf9dffff at device 0.1 o= n pci1 hdac0: mem 0xdfffc000-0xdfffffff irq 16 at de= vice 27.0 on pci0 pcib2: at device 28.0 on pci0 pci5: on pcib2 re0: port 0xa80= 0-0xa8ff mem 0xdfdff000-0xdfdfffff,0xcf6fc000-0xcf6fffff irq 16 at device 0= .0 on pci5 re0: Using 1 MSI-X message re0: Chip rev. 0x2c000000 re0: MAC rev. 0x00200000 miibus0: on re0 rgephy0: PHY 1 on miibus0 rgephy0:=C2=A0 none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100= baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX,= 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto,= auto-flow re0: Using defaults for TSO: 65518/35/2048 re0: Ethernet address: e8:de:27:01:b2:4b pcib3: at device 28.1 on pci0 pci4: on pcib3 pcib4: at device 28.2 on pci0 pci3: on pcib4 pcib5: at device 28.3 on pci0 pci2: on pcib5 uhci0: port 0xcc00-0x= cc1f irq 23 at device 29.0 on pci0 uhci0: LegSup =3D 0x2f00 usbus0 on uhci0 uhci1: port 0xd000-0x= d01f irq 19 at device 29.1 on pci0 uhci1: LegSup =3D 0x2f00 usbus1 on uhci1 uhci2: port 0xd400-0x= d41f irq 18 at device 29.2 on pci0 uhci2: LegSup =3D 0x2f00 usbus2 on uhci2 uhci3: port 0xd800-0x= d81f irq 16 at device 29.3 on pci0 uhci3: LegSup =3D 0x2f00 usbus3 on uhci3 ehci0: mem 0xdfffbc00-0xdfffbfff = irq 23 at device 29.7 on pci0 usbus4: waiting for BIOS to give up control usbus4: timed out waiting for BIOS usbus4 on ehci0 pcib6: at device 30.0 on pci0 pci6: on pcib6 pci6: at device 0.0 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177= ,0x376,0xffa0-0xffaf at device 31.1 on pci0 ata0: at channel 0 on atapci0 ata1: at channel 1 on atapci0 atapci1: port 0xec00-0xec07,0xe800-0xe803,0= xe400-0xe407,0xe000-0xe003,0xdc00-0xdc0f irq 19 at device 31.2 on pci0 ata2: at channel 0 on atapci1 ata3: at channel 1 on atapci1 acpi_button0: on acpi0 uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 orm0: at iomem 0xc0000-0xccfff pnpid ORM0000 on isa0 p4tcc0: on cpu0 p4tcc1: on cpu1 Timecounters tick every 1.000 msec random: unblocking device. usbus0: 12Mbps Full Speed USB v1.0 hdacc0: at cad 2 on hdac0 hdaa0: at nid 1 on hdacc0usbus1: 12Mb= ps Full Speed USB v1.0 usbus2: 12Mbps Full Speed USB v1.0 usbus3: 12Mbps Full Speed USB v1.0 ugen0.1: at usbus0 uhub0: on usbus0 ugen1.1: at usbus1 uhub1: on usbus1 ugen2.1: at usbus2 uhub2: on usbus2 ugen3.1: at usbus3 uhub3: on usbus3 usbus4: 480Mbps High Speed USB v2.0 ugen4.1: at usbus4 uhub4: on usbus4 uhub_attach: Turning port 1 power on uhub_attach: Turning port 1 power on uhub_attach: Turning port 1 power on uhub_attach: Turning port 1 power on uhub_attach: Turning port 1 power on uhub_attach: Turning port 2 power on uhub_attach: Turning port 2 power on uhub_attach: Turning port 2 power on uhub_attach: Turning port 2 power on uhub0: 2 ports with 2 removable, self powereduhub2: 2 ports with 2 removabl= e, self powered uhub3: 2 ports with 2 removable, self powered uhub_attach: Turning port 2 power on uhub_attach: Turning port 3 power on uhub_attach: Turning port 4 power on uhub_attach: Turning port 5 power on uhub_attach: Turning port 6 power on uhub_attach: Turning port 7 power on uhub_attach: Turning port 8 power on uhub4: 8 ports with 8 removable, self powered ada0 at ata2 bus 0 scbus2 target 0 lun 0 ada0: ATA-8 SATA 3.x device ada0: Serial Number WD-WCC1UAR3R4CE ada0: 150.000MB/s transfers (SATA, UDMA5, PIO 8192bytes) ada0: 476940MB (976773168 512 byte sectors: 16H 63S/T 16383C) ada0: quirks=3D0x1<4K> ada0: Previously was known as ad4 ada1 at ata3 bus 0 scbus3 target 0 lun 0 ada1: ATA-8 SATA 2.x device ada1: Serial Number WD-WMASY0544230 ada1: 150.000MB/s transfers (SATA, UDMA5, PIO 8192bytes) ada1: 476940MB (976773168 512 byte sectors: 16H 63S/T 16383C) ada1: Previously was known as ad6 cd0 at ata3 bus 0 scbus3 target 1 lun 0cd0: 150.000MB/s transfers (SATA, UD= MA5, ATAPI 12bytes, PIO 8192bytes) cd0: Attempt to query device size failed: NOT READY, Medium not present - t= ray closed SMP: AP CPU #1 Launched! Timecounter "TSC-low" frequency 1600026116 Hz quality 1000 Trying to mount root from ufs:/dev/ada1p2 [rw]... ugen3.2: at usbus3 ukbd0: on usbus3 kbd0 at ukbd0 ums0: on usbus3 ums0: 10 buttons and [XYZT] coordinates ID=3D2 Any help appreciatedsincerelyFilippo From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 20:01:27 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E3E492C8 for ; Wed, 10 Dec 2014 20:01:27 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BC518BEB for ; Wed, 10 Dec 2014 20:01:27 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id AB614B97D; Wed, 10 Dec 2014 15:01:26 -0500 (EST) From: John Baldwin To: freebsd-stable@freebsd.org Subject: Re: SuperMicro IPMI/SOL and ipmitool troubles Date: Thu, 4 Dec 2014 15:50:46 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20140415; KDE/4.5.5; amd64; ; ) References: <201411201351.29190.jhb@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201412041550.46397.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Wed, 10 Dec 2014 15:01:26 -0500 (EST) Cc: Daniel O'Connor , Dmitry Morozovsky , Andreas Nilsson X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2014 20:01:28 -0000 On Thursday, November 20, 2014 4:01:52 pm Andreas Nilsson wrote: > On Thu, Nov 20, 2014 at 7:51 PM, John Baldwin wrote: > Sure thing, below is the output from the machine where this started, for me > at least. Still a X9SCI/X9SCA machine: > > Set in progress : set-complete > Enabled : true > Force Encryption : false > Force Authentication : false > Privilege Level : USER > Character Accumulate Level (ms) : 0 > Character Send Threshold : 0 > Retry Count : 0 > Retry Interval (ms) : 0 > Volatile Bit Rate (kbps) : 115.2 > Non-Volatile Bit Rate (kbps) : 115.2 So do you have the conspeed set to 115200 in your loader.conf or are you still trying to use 9600? -- John Baldwin From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 20:48:28 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 81D33428 for ; Wed, 10 Dec 2014 20:48:28 +0000 (UTC) Received: from tau.lfms.nl (tau.lfms.nl [93.189.130.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2A98991 for ; Wed, 10 Dec 2014 20:48:27 +0000 (UTC) Received: from sim.dt.lfms.nl (dt.lfms.nl [83.84.86.53]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by tau.lfms.nl (Postfix) with ESMTPS id 6925D892E2 for ; Wed, 10 Dec 2014 21:48:19 +0100 (CET) Received: from [192.168.130.112] (borax.dt.lfms.nl [192.168.130.112]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by sim.dt.lfms.nl (Postfix) with ESMTPS id 31EB39C09085 for ; Wed, 10 Dec 2014 21:48:19 +0100 (CET) From: Walter Hop Message-Id: <7FE045BA-246F-460F-81F5-CFC312072A92@spam.lifeforms.nl> Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Subject: Re: System hang on shutdown when running freebsd-update Date: Wed, 10 Dec 2014 21:48:18 +0100 References: <548846F8.4080208@club-internet.fr> <20141210133658.GA12721@ozzmosis.com> <54885894.2060006@club-internet.fr> To: freebsd-stable@freebsd.org In-Reply-To: <54885894.2060006@club-internet.fr> X-Mailer: Apple Mail (2.1993) Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2014 20:48:28 -0000 > On 10 Dec 2014, at 15:28, Juan Ram=F3n Molina Menor = wrote: >=20 >> A FreeBSD 10.1-REL amd64 VM here also hangs after /sbin/reboot is = run, >> after installing updates with freebsd-update. The VM runs under >> VirtualBox on an Ubuntu 14.04 host. >>=20 >> On hard-resetting the VM, it appears the filesystem (UFS) wasn't = flushed: >>=20 >> Dec 11 00:29:52 vbox-freebsd kernel: WARNING: / was not properly = dismounted >=20 > Yes, I forgot that, same here on bare metal. I=92d expect it to happen again, since the update touched /sbin/init, = and that seems to be a way to get reboot/unmount hanging with = UFS2+softupdates. (See my minimal example in = https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D195458 = ) A workaround to prevent the hang/fsck is to first disable softupdates on = / before doing the freebsd-update. We updated around 40 boxes with this = one weird trick, and we did not have the problem. I=92ve tried if the hang is apparent in a 11-CURRENT snapshot too, and = it is. (Tried the iso snapshot available today, which is r273635). = WITNESS indicates a lock order reversal, which looks related to me: root@current:~ # chflags noschg /sbin/init root@current:~ # cp -Rp /sbin/init /sbin/init2 lock order reversal: 1st 0xfffffe007b842fa0 bufwait (bufwait) @ = /usr/src/sys/kern/vfs_bio.c:3093 2nd 0xfffff80002b9ea00 dirhash (dirhash) @ = /usr/src/sys/ufs/ufs/ufs_dirhash.c:284 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame = 0xfffffe000025c270 kdb_backtrace() at kdb_backtrace+0x39/frame 0xfffffe000025c320 witness_checkorder() at witness_checkorder+0xdad/frame = 0xfffffe000025c3b0 _sx_xlock() at _sx_xlock+0x75/frame 0xfffffe000025c3f0 ufsdirhash_add() at ufsdirhash_add+0x3a/frame 0xfffffe000025c430 ufs_direnter() at ufs_direnter+0x6a0/frame 0xfffffe000025c4f0 ufs_makeinode() at ufs_makeinode+0x560/frame 0xfffffe000025c6a0 VOP_CREATE_APV() at VOP_CREATE_APV+0xf1/frame 0xfffffe000025c6d0 vn_open_cred() at vn_open_cred+0x29d/frame 0xfffffe000025c820 kern_openat() at kern_openat+0x26f/frame 0xfffffe000025c9a0 amd64_syscall() at amd64_syscall+0x25a/frame 0xfffffe000025cab0 Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe000025cab0 --- syscall (5, FreeBSD ELF64, sys_open), rip =3D 0x80094f01a, rsp =3D = 0x7fffffffe958, rbp =3D 0x7fffffffe9c0 --- Screenshot is here: http://lf.ms/current-r273635-hang-1.png = Finally, when rebooting, another lock order reversal appears and the = system hangs. I don=92t have a text log of this, so I=92ll copy the first few lines: Syncing disks, vnodes remaining=851 0 0 done All buffers synced. lock order reversal: 1st 0xfffff80002e65d50 ufs (ufs) @ /usr/src/sys/kern/vfs_mount.c:1223 2nd 0xfffff80002e665f0 devfs (devfs) @ = /usr/src/sys/kern/vfs_subr.c:2144 Screenshot is here: http://lf.ms/current-r273635-hang-2.png = I don=92t have kernel hacking experience, but these source files look = awfully related to the parts that we are having problems with. I would really love some research into this and possibly an errata for = 10.1. What can we do to make this actionable? WH --=20 Walter Hop | PGP key: https://lifeforms.nl/pgp From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 21:20:54 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 23875E76 for ; Wed, 10 Dec 2014 21:20:54 +0000 (UTC) Received: from tau.lfms.nl (tau.lfms.nl [93.189.130.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D7832405 for ; Wed, 10 Dec 2014 21:20:53 +0000 (UTC) Received: from sim.dt.lfms.nl (dt.lfms.nl [83.84.86.53]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by tau.lfms.nl (Postfix) with ESMTPS id 1A891893D9 for ; Wed, 10 Dec 2014 22:20:52 +0100 (CET) Received: from [192.168.130.112] (borax.dt.lfms.nl [192.168.130.112]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by sim.dt.lfms.nl (Postfix) with ESMTPS id E063D9C09085 for ; Wed, 10 Dec 2014 22:20:51 +0100 (CET) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Subject: Re: System hang on shutdown when running freebsd-update From: Walter Hop In-Reply-To: <7FE045BA-246F-460F-81F5-CFC312072A92@spam.lifeforms.nl> Date: Wed, 10 Dec 2014 22:20:51 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <3F59BF15-82EF-4434-9882-2C8E208C6599@spam.lifeforms.nl> References: <548846F8.4080208@club-internet.fr> <20141210133658.GA12721@ozzmosis.com> <54885894.2060006@club-internet.fr> <7FE045BA-246F-460F-81F5-CFC312072A92@spam.lifeforms.nl> To: freebsd-stable@freebsd.org X-Mailer: Apple Mail (2.1993) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2014 21:20:54 -0000 > On 10 Dec 2014, at 21:48, Walter Hop = wrote: >=20 > I=92ve tried if the hang is apparent in a 11-CURRENT snapshot too, and = it is. (Tried the iso snapshot available today, which is r273635). I lied! That was not the latest snapshot available, my apologies. I = retried with a snapshot from 7 Dec (r275582). In r275582, the LOR when fiddling with /sbin/init is the same as in = 10.1, but the behavior at reboot is different, although it is still = pathological (=93Giving up on 1 buffers=94) . Screenshot: = http://lf.ms/current-r275582-hang-givingup.png I have hit this behavior twice on r275582, but not on 10.1. So something = has changed in CURRENT after r273635, but the basic problem still seems = to be there. --=20 Walter Hop | PGP key: https://lifeforms.nl/pgp From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 21:45:39 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B2E916BE; Wed, 10 Dec 2014 21:45:39 +0000 (UTC) Received: from mail-la0-x235.google.com (mail-la0-x235.google.com [IPv6:2a00:1450:4010:c03::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 30C0992E; Wed, 10 Dec 2014 21:45:39 +0000 (UTC) Received: by mail-la0-f53.google.com with SMTP id gm9so3279817lab.12 for ; Wed, 10 Dec 2014 13:45:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=SyYCM/tX8sw3GHjeFbpIg8eQ8/o46QeauQk4z7cJfxU=; b=ywKDhj06f1zweW05345nH3lf7VQVaYD7INH+wt1giMnmQqtl9jW/klWoNtASgxMMSc h0d80LRXL9k5c011pIu1W/PUnWpHi0+pyMeJwoSoiLcQT0zi+GqkhDaPzuHtDapdv+fP tPEls8GxijD5Um5gIljomsxvAwEdfvPdOlYaiFygZO/pYExEM/fVkW9n/ARoaEavU78a +Kfe9zLsXxTB0uFJu45JIOIXFkZksp3TPAZ5Va0ZJM4iCUwO9M3klcynjNnF1X2b1uAt 8iYk3nyvVOCNv3Da6VbLX2soODnzkLoNr2igYBP16mwE7lM4BswX0UOyGv+9hhwWuxqq ekFg== MIME-Version: 1.0 X-Received: by 10.112.132.67 with SMTP id os3mr6258940lbb.90.1418247937290; Wed, 10 Dec 2014 13:45:37 -0800 (PST) Received: by 10.25.170.130 with HTTP; Wed, 10 Dec 2014 13:45:37 -0800 (PST) In-Reply-To: <201412041550.46397.jhb@freebsd.org> References: <201411201351.29190.jhb@freebsd.org> <201412041550.46397.jhb@freebsd.org> Date: Wed, 10 Dec 2014 22:45:37 +0100 Message-ID: Subject: Re: SuperMicro IPMI/SOL and ipmitool troubles From: Andreas Nilsson To: John Baldwin Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: Daniel O'Connor , FreeBSD Stable Mailing List , Dmitry Morozovsky X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2014 21:45:39 -0000 On Thu, Dec 4, 2014 at 9:50 PM, John Baldwin wrote: > On Thursday, November 20, 2014 4:01:52 pm Andreas Nilsson wrote: > > On Thu, Nov 20, 2014 at 7:51 PM, John Baldwin wrote: > > Sure thing, below is the output from the machine where this started, for > me > > at least. Still a X9SCI/X9SCA machine: > > > > Set in progress : set-complete > > Enabled : true > > Force Encryption : false > > Force Authentication : false > > Privilege Level : USER > > Character Accumulate Level (ms) : 0 > > Character Send Threshold : 0 > > Retry Count : 0 > > Retry Interval (ms) : 0 > > Volatile Bit Rate (kbps) : 115.2 > > Non-Volatile Bit Rate (kbps) : 115.2 > > So do you have the conspeed set to 115200 in your loader.conf or are you > still > trying to use 9600? > > -- > John Baldwin > It is set 115200 yes. At least if hw.uart.console="br:115200" works as expected. Best regards Andreas From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 23:04:42 2014 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D53075A7 for ; Wed, 10 Dec 2014 23:04:42 +0000 (UTC) Received: from oslo.ath.cx (oslo.ath.cx [IPv6:2a01:4f8:200:42e4::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "oslo.ath.cx", Issuer "oslo.ath.cx" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 32CC8187 for ; Wed, 10 Dec 2014 23:04:41 +0000 (UTC) Received: by oslo.ath.cx (OpenSMTPD) with ESMTP id 38c71cc3; for ; Thu, 11 Dec 2014 00:04:39 +0100 (CET) Date: Thu, 11 Dec 2014 00:04:39 +0100 From: "Herbert J. Skuhra" To: stable@freebsd.org Subject: Re: Kbd problem in 10.1-STABLE Message-ID: <20141210230439.GA5740@oslo.ath.cx> References: <1192938802.7895425.1418224845347.JavaMail.yahoo@jws10663.mail.bf1.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1192938802.7895425.1418224845347.JavaMail.yahoo@jws10663.mail.bf1.yahoo.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2014 23:04:42 -0000 On Wed, Dec 10, 2014 at 03:20:45PM +0000, Filippo Moretti via freebsd-stable wrote: > My kbd (Logitech Deluxe 660 cordless) no longer works after updating > 10.1-STABLE from November 24 to December 8.The kernel configuration file > is unchanged,the mouse which is on the same receiver > works.root@sting:/home/filippo # uname -a > FreeBSD sting 10.1-STABLE FreeBSD 10.1-STABLE #6 r274620: Mon Nov 24 > 19:02:17 CET 2014     root@sting:/usr/obj/usr/src/sys/STING_VT  i386 > I booted kernel.old and everything works. Try to enable kbdmux or revert r274861. There is already a PR for this issue: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195491 -- Herbert From owner-freebsd-stable@FreeBSD.ORG Thu Dec 11 01:38:25 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4712C43C for ; Thu, 11 Dec 2014 01:38:25 +0000 (UTC) Received: from ipmail05.adl6.internode.on.net (ipmail05.adl6.internode.on.net [150.101.137.143]) by mx1.freebsd.org (Postfix) with ESMTP id 9ACE9324 for ; Thu, 11 Dec 2014 01:38:23 +0000 (UTC) Received: from ppp14-2-30-215.lns21.adl2.internode.on.net (HELO leader.local) ([14.2.30.215]) by ipmail05.adl6.internode.on.net with ESMTP; 11 Dec 2014 12:08:21 +1030 Message-ID: <5488F58D.7060708@ShaneWare.Biz> Date: Thu, 11 Dec 2014 12:08:21 +1030 From: Shane Ambler User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: FreeBSD stable Subject: Help debugging stable/10 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Dec 2014 01:38:25 -0000 Since upgrading to 10.1 (RC2) I have had trouble getting uptimes greater than 1 day. I have little experience debugging the OS so could use some help. # uname -a FreeBSD leader.local 10.1-STABLE FreeBSD 10.1-STABLE #0 r275364: Tue Dec 2 08:13:06 ACDT 2014 root@leader.local:/usr/obj/usr/src-stable/sys/GENERIC amd64 This is on an ASUS P8H61-M LE/USB3 corei5 8GB with 3x 2TB Seagate drives in raidz. Full backtraces and dmesg at http://shaneware.biz/freebsddebugdata/ The thing that breaks which forces me to reset the machine is that I am unable to start new processes. Existing processes continue to work I just can't start new ones. Some simple commands do work but top ps procstat usbconfig all fail to start. I have been able use script to get some backtraces from kgdb before restarting. Back in RC2 and 3 I had it freeze up leaving me to reset, since RC4 and now on stable I have been able to close up most processes before resetting. I don't know how to re-create this issue on command, but I just had 4 days uptime which is the best I've had in the last month. How do I find what is preventing new processes starting? What can I do to get more data when things go south? I noticed an odd thing in the backtrace today - Thread 16 (Thread 101376): #0 sched_switch (td=0xfffff8011c1e7000, newtd=, flags=) at /usr/src-stable/sys/kern/sched_ule.c:1945 #1 0x0000000000000020 in ?? () #2 0xfffffe021e5a8200 in ?? () #3 0xffffffff80913166 in malloc (size=, mtp=, flags=) at /usr/src-stable/sys/kern/kern_malloc.c:352 #4 0xec81485354415541 in ?? () #5 0x4dce894d00000268 in ?? () #6 0xd58949cc8949c789 in ?? () #7 0x9358253c8148fb89 in ?? () #8 0x850f000000008164 in ?? () #16890 0x067ee8f68944df89 in ?? () #16891 0x8618251c8948fdd7 in ?? () #16892 0x415b10c4834882c1 in ?? () #16893 0x0000000000c35d5e in ?? () #16894 0x0000000000000000 in ?? () Yes there are nearly 17,000 lines in that backtrace, no idea what it is though. -- FreeBSD - the place to B...Software Developing Shane Ambler From owner-freebsd-stable@FreeBSD.ORG Thu Dec 11 05:34:43 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D20084FC for ; Thu, 11 Dec 2014 05:34:43 +0000 (UTC) Received: from mail3.transactionware.com (mail.transactionware.com [203.14.245.7]) by mx1.freebsd.org (Postfix) with SMTP id 4336DEA4 for ; Thu, 11 Dec 2014 05:34:42 +0000 (UTC) Received: (qmail 81166 invoked by uid 907); 11 Dec 2014 05:34:31 -0000 Received: from Unknown (HELO jmmacpro.tmst.com.au) (203.14.245.130) (smtp-auth username janm, mechanism plain) by mail3.transactionware.com (qpsmtpd/0.84) with (DHE-RSA-AES256-SHA encrypted) ESMTPSA; Thu, 11 Dec 2014 16:34:31 +1100 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Subject: Re: bsdtar POLA change in 10.0? From: Jan Mikkelsen In-Reply-To: Date: Thu, 11 Dec 2014 16:34:55 +1100 Content-Transfer-Encoding: quoted-printable Message-Id: <5BEC32C8-3611-419C-A0C8-3AB4DA776A27@transactionware.com> References: <53171DAE.5070203@li.ru> <1394110822.21224.91297125.0B659AFB@webmail.messagingengine.com> <56BC2D25-7163-43A2-AB04-9A808AA98F85@gmail.com> To: Ronald Klop X-Mailer: Apple Mail (2.1993) Cc: libarchive-discuss@googlegroups.com, freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Dec 2014 05:34:43 -0000 > On 7 Mar 2014, at 20:42, Ronald Klop wrote: >=20 > On Thu, 06 Mar 2014 19:43:28 +0100, Warner Losh = wrote: >=20 >>=20 >> On Mar 6, 2014, at 6:00 AM, Mark Felder wrote: >>=20 >>>=20 >>>=20 >>> On Wed, Mar 5, 2014, at 6:50, Marat N.Afanasyev wrote: >>>> I wonder why >>>>=20 >>>> bsdtar --one-file-system >>>>=20 >>>> suddenly started to skip archiving of mount-points? And no mention = of >>>> such behaviour change either in UPDATING or errata :( >>>>=20 >>>=20 >>> --one-file-system >>> (c, r, and u modes) Do not cross mount points. >>>=20 >>> Isn't that what it's supposed to do? Skip any mounted filesystems? = Was >>> it broken before? Or do I simply not understand the behavior you're >>> seeing. >>=20 >> Before it would archive the directory where the other filesystem was = mounted, but nothing else. >>=20 >> Now it doesn=E2=80=99t archive that directory. >>=20 >> I believe this is a bug, since that directory (but nothing in it or = under it) still belongs to this filesystem... >>=20 >> Warner >=20 > I cc'ed libarchive-discuss@googlegroups.com for more exposure to the = issue. >=20 Reviving an old discussion =E2=80=94 this just caused my build process = for 10.1 to create root filesystems without /dev, which is obviously = constraining. Using the --one-file-system option should should preserve mount point = directories. Will this be fixed? Jan. From owner-freebsd-stable@FreeBSD.ORG Thu Dec 11 21:59:15 2014 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B2E09AB7 for ; Thu, 11 Dec 2014 21:59:15 +0000 (UTC) Received: from drone068.ral.icpbounce.com (drone068.ral.icpbounce.com [64.132.109.60]) by mx1.freebsd.org (Postfix) with ESMTP id 73BB9A26 for ; Thu, 11 Dec 2014 21:59:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; s=default; d=icontactmail4.com; h=Mime-Version:From:To:Date:Reply-To:Subject:List-Unsubscribe:Feedback-ID:Content-Type:Message-ID; bh=mrs5FatuIRPaYS9oZvBliFa2KqwnDzyWtFB2iEWjHUg=; b=WyPQpZa4OPYntnhniOjw4gWjZHlXJhx9mBZgb4H7q0tk9BuLbC1E5DEbLKpRZnL4xyu9LrXWSvc9 5ilXp82h8I6d5lrrimxDt88y2bUL6Syx6HRwlG+1EbVTumJjJI5PmPeQtcRRjn/fPndunnpShauz A+ZSuItDNUrIT4xLLOA= Mime-Version: 1.0 From: "Classical Academic Press" To: Date: Thu, 11 Dec 2014 16:19:09 -0500 Reply-To: rjames@classicalsubjects.com Subject: Confirm your subscription to 2015 homeschool insights Errors-To: bounces+1283964.24412559.165907@icpbounce.com X-List-Unsubscribe: X-Unsubscribe-Web: Feedback-ID: 1283964_4541_165907:1283964_4541:1283964:icontact X-ICPINFO: X-Return-Path-Hint: bounces+1283964.24412559.165907@icpbounce.com Message-ID: <0.0.72.1D9.1D015881A1A32F2.0@drone068.ral.icpbounce.com> Content-Type: text/plain; charset = "utf-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Dec 2014 21:59:15 -0000 Will you join us? We would be honored to have you receive our homeschool monthly eNewsletter We typically send out 1 or 2 emails a month. You'll receive words of wisdom from our publisher Dr. Christopher Perrin as well as 5=E2=80=937 links to t= he most excellent and insightful articles on education, children, and parenting which we have collected in our daily research. You'll also be the first to know about new products, reviews, free webinars, or specials. Your privacy is important to us. We will not share your email with anyone and you can unsubcribe at any time. Pax, Rebecca James Director Classical Academic Press 2151 Market St Camp Hill, PA 17011 www.ClassicalAcademicPress.com Tel: (717) 730-0711 References 1. http://classicalacademicpress.com/ 2. https://www.facebook.com/classicalacademicpress 3. https://twitter.com/ClassicalAcadPr=0AConfirm to All Lists:=0Ahttps://ap= p.icontact.com/icp/confirm.php?r=3D24412559&s=3DY66G&gid=3D14130,48702&c=3D1283964=0A=0A=0A - OR - =0A=0A=0A =0A Co= nfirm to list: 1. Homeschool=0A https://app.= icontact.com/icp/confirm.php?r=3D24412559&s=3DY66G&gid=3D14130&c=3D1283964&l=3D4541&m=3D165907=0A Conf= irm to list: 2015 homeschool =0A https://ap= p.icontact.com/icp/confirm.php?r=3D24412559&s=3DY66G&gid=3D48702&c=3D1283964&l=3D4541&m=3D165907=0A This message was sen= t to stable@freebsd.org from: Classical Academic Press | rjames@classicalsubjects.com | Classical Academic Press | 2151 Market St | Camp Hill, PA 17011=0A=0A=0A From owner-freebsd-stable@FreeBSD.ORG Fri Dec 12 01:36:53 2014 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2F37E9C7 for ; Fri, 12 Dec 2014 01:36:53 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 15C3939E for ; Fri, 12 Dec 2014 01:36:53 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sBC1aqwU010032 for ; Fri, 12 Dec 2014 01:36:52 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-stable@FreeBSD.org Subject: [Bug 194534] [freebsd-update] upgrade from FreeBSD-10-RELEASE to FreeBSD-10.1RC2 system fail to boot. Date: Fri, 12 Dec 2014 01:36:53 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 10.1-RC2 X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: sasamotikomi@gmail.com X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2014 01:36:53 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194534 --- Comment #2 from sasamotikomi@gmail.com --- (In reply to Glen Barber from comment #1) > I am unable to reproduce this. > > Please provide more information about your machine configuration. Probably I "downgrade" to 9.1 for some reason https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193380 # freebsd-upgrade upgrade -r 9.1-RELEASE And just replaced my kernel with 10-RELEASE and try update -- You are receiving this mail because: You are on the CC list for the bug. From owner-freebsd-stable@FreeBSD.ORG Fri Dec 12 08:05:02 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 21FC5923 for ; Fri, 12 Dec 2014 08:05:02 +0000 (UTC) Received: from mail3.transactionware.com (mail.transactionware.com [203.14.245.7]) by mx1.freebsd.org (Postfix) with SMTP id 8676FBC for ; Fri, 12 Dec 2014 08:05:00 +0000 (UTC) Received: (qmail 79987 invoked by uid 907); 12 Dec 2014 08:04:49 -0000 Received: from Unknown (HELO jmmacpro.tmst.com.au) (203.14.245.130) (smtp-auth username janm, mechanism plain) by mail3.transactionware.com (qpsmtpd/0.84) with (DHE-RSA-AES256-SHA encrypted) ESMTPSA; Fri, 12 Dec 2014 19:04:49 +1100 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Subject: Re: bsdtar POLA change in 10.0? From: Jan Mikkelsen In-Reply-To: <5BEC32C8-3611-419C-A0C8-3AB4DA776A27@transactionware.com> Date: Fri, 12 Dec 2014 19:05:13 +1100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <53171DAE.5070203@li.ru> <1394110822.21224.91297125.0B659AFB@webmail.messagingengine.com> <56BC2D25-7163-43A2-AB04-9A808AA98F85@gmail.com> <5BEC32C8-3611-419C-A0C8-3AB4DA776A27@transactionware.com> To: Ronald Klop X-Mailer: Apple Mail (2.1993) Cc: libarchive-discuss@googlegroups.com, freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2014 08:05:02 -0000 > On 11 Dec 2014, at 16:34, Jan Mikkelsen = wrote: >=20 >=20 >> On 7 Mar 2014, at 20:42, Ronald Klop wrote: >>=20 >> On Thu, 06 Mar 2014 19:43:28 +0100, Warner Losh = wrote: >>=20 >>>=20 >>> On Mar 6, 2014, at 6:00 AM, Mark Felder wrote: >>>=20 >>>>=20 >>>>=20 >>>> On Wed, Mar 5, 2014, at 6:50, Marat N.Afanasyev wrote: >>>>> I wonder why >>>>>=20 >>>>> bsdtar --one-file-system >>>>>=20 >>>>> suddenly started to skip archiving of mount-points? And no mention = of >>>>> such behaviour change either in UPDATING or errata :( >>>>>=20 >>>>=20 >>>> --one-file-system >>>> (c, r, and u modes) Do not cross mount points. >>>>=20 >>>> Isn't that what it's supposed to do? Skip any mounted filesystems? = Was >>>> it broken before? Or do I simply not understand the behavior you're >>>> seeing. >>>=20 >>> Before it would archive the directory where the other filesystem was = mounted, but nothing else. >>>=20 >>> Now it doesn=E2=80=99t archive that directory. >>>=20 >>> I believe this is a bug, since that directory (but nothing in it or = under it) still belongs to this filesystem... >>>=20 >>> Warner >>=20 >> I cc'ed libarchive-discuss@googlegroups.com for more exposure to the = issue. >>=20 >=20 > Reviving an old discussion =E2=80=94 this just caused my build process = for 10.1 to create root filesystems without /dev, which is obviously = constraining. >=20 > Using the --one-file-system option should should preserve mount point = directories. Will this be fixed? In case anyone is interested, this has been fixed upstream: = https://github.com/libarchive/libarchive/commit/fa9e61aa1531153b7748d4e0d8= dda8f52a0893d7 Jan. From owner-freebsd-stable@FreeBSD.ORG Fri Dec 12 08:15:31 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0075FB3A for ; Fri, 12 Dec 2014 08:15:30 +0000 (UTC) Received: from eu1sys200aog105.obsmtp.com (eu1sys200aog105.obsmtp.com [207.126.144.119]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4F1461BA for ; Fri, 12 Dec 2014 08:15:29 +0000 (UTC) Received: from mail-wg0-f46.google.com ([74.125.82.46]) (using TLSv1) by eu1sys200aob105.postini.com ([207.126.147.11]) with SMTP ID DSNKVIqkCL/jprnfkXrc82YO36s9/MFoa67q@postini.com; Fri, 12 Dec 2014 08:15:30 UTC Received: by mail-wg0-f46.google.com with SMTP id x13so8447080wgg.19 for ; Fri, 12 Dec 2014 00:15:04 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:message-id:to:subject:reply-to; bh=d+91hBo/4fUvvMmBlDdTKUL3X4UFO8+kxgPRijQzQWk=; b=Rqupu/BDQ349D0uDC9XF6tmp/56ORb/JxBTbQjcLqwQdCBRIVl5jA3+tFdDlYxI1lZ duhamkseAfETtQ1ad5y/bUmBTHaYtW7tGB1iIwxTbFuOseRPGBcCw1hqoi4AYuBIUy9h Zpjp8cytcEqRErn8czWpeiE3xk46yT9zqj56mXvQeq3+USMRi9LjjsBCeq0xHVR2a+3D uardrN2WcRxqE9xq3WaASg+zm5trPeEiSxfPWFwxYNVFH+m8mBFJqM0Xy6DXpMiyhI3T do8IyU05iVNny7F6qZvy4NI+2upm/ag+VuhzAIIVZslCsNd5kiNVWG8PPYW4nLISScae V9qg== X-Gm-Message-State: ALoCoQnhyY2TVY0/asFO7nOFU1j9LN7jMLxLDaQrQNdYP700Ok4liMNOnt0XaI4f7aiBHJBdz9cD8gqB5RMP4f/Lxmu0j33CbMh13n3vNOPpEBSzvVTbfYjeD51D4bMx1UlFgO4XWR44WLKFeqIxwkazqXctvHhIAw== X-Received: by 10.194.157.4 with SMTP id wi4mr10139962wjb.54.1418372104805; Fri, 12 Dec 2014 00:15:04 -0800 (PST) X-Received: by 10.194.157.4 with SMTP id wi4mr10139945wjb.54.1418372104668; Fri, 12 Dec 2014 00:15:04 -0800 (PST) Received: from mech-as221.men.bris.ac.uk (mech-as221.men.bris.ac.uk. [137.222.187.221]) by mx.google.com with ESMTPSA id cz3sm825187wjb.23.2014.12.12.00.15.03 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 12 Dec 2014 00:15:04 -0800 (PST) Date: Fri, 12 Dec 2014 00:15:04 -0800 (PST) X-Google-Original-Date: Fri, 12 Dec 2014 08:15:02 GMT Received: from mech-as221.men.bris.ac.uk (localhost [127.0.0.1]) by mech-as221.men.bris.ac.uk (8.14.9/8.14.9) with ESMTP id sBC8F2hl087106 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Fri, 12 Dec 2014 08:15:03 GMT (envelope-from mexas@mech-as221.men.bris.ac.uk) Received: (from mexas@localhost) by mech-as221.men.bris.ac.uk (8.14.9/8.14.9/Submit) id sBC8F2XQ087105 for freebsd-stable@freebsd.org; Fri, 12 Dec 2014 08:15:02 GMT (envelope-from mexas) From: Anton Shterenlikht Message-Id: <201412120815.sBC8F2XQ087105@mech-as221.men.bris.ac.uk> To: freebsd-stable@freebsd.org Subject: freebsd-update: Installing updates...install: ///usr/src/contrib/tzdata/zone1970.tab: No such file or directory Reply-To: mexas@bris.ac.uk X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2014 08:15:31 -0000 I'm trying to update from 10.0-RELEASE-p12 amd64 to 10.0-RELEASE-p13. I get: # freebsd-update fetch Looking up update.FreeBSD.org mirrors... 5 mirrors found. Fetching metadata signature for 10.0-RELEASE from update4.freebsd.org... done. Fetching metadata index... done. Inspecting system... done. Preparing to download files... done. The following files will be added as part of updating to 10.0-RELEASE-p13: /usr/src/contrib/tzdata/zone1970.tab # freebsd-update install Installing updates...install: ///usr/src/contrib/tzdata/zone1970.tab: No such file or directory done. # Please advise Thanks Anton From owner-freebsd-stable@FreeBSD.ORG Fri Dec 12 08:29:39 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 413E7D6C for ; Fri, 12 Dec 2014 08:29:39 +0000 (UTC) Received: from mail-oi0-x235.google.com (mail-oi0-x235.google.com [IPv6:2607:f8b0:4003:c06::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 02A9D313 for ; Fri, 12 Dec 2014 08:29:39 +0000 (UTC) Received: by mail-oi0-f53.google.com with SMTP id x69so4810322oia.26 for ; Fri, 12 Dec 2014 00:29:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=r+ZXJAlIEG5nBoXuR2NPu9wQ/XyqmowcYkf3QM1lrOA=; b=OBxyPXUZPw2rUty+2jAg3XdgOeXamcBtEdr6COseFYVFObM5zntLDooT04zHOHvZik Wsfp/g1zzrNgEpJtdIzqM9d4AwHbQpdkGl3cYywrOsN/k+xtRpLWutmE/XdUTeCX0E5w 4O1aq6i0jhkcEeeQ44UG64JhxdtHbl0smiuzKL3LRFGJdpJ6gp7QcKLOfhojuAHhitPI gTEEL5aKn/254um90N7FLh7FtYujVmvUrX65qeym293i84F7xyIjB6STTpEEKa+d+jo0 6PRBrNWih3oSqhkyNf5p7nmJvU+eQ/Va+T18pcZ2T3N6jLuZ7ybWaBBfh6r6ckbmzYQJ UBpg== X-Received: by 10.60.134.20 with SMTP id pg20mr9381317oeb.36.1418372978157; Fri, 12 Dec 2014 00:29:38 -0800 (PST) MIME-Version: 1.0 Sender: royce.williams@gmail.com Received: by 10.202.198.133 with HTTP; Fri, 12 Dec 2014 00:29:16 -0800 (PST) In-Reply-To: <201412120815.sBC8F2XQ087105@mech-as221.men.bris.ac.uk> References: <201412120815.sBC8F2XQ087105@mech-as221.men.bris.ac.uk> From: Royce Williams Date: Thu, 11 Dec 2014 23:29:16 -0900 X-Google-Sender-Auth: FKwjf0TpaU0hjE154D5Lq_qfg-U Message-ID: Subject: Re: freebsd-update: Installing updates...install: ///usr/src/contrib/tzdata/zone1970.tab: No such file or directory To: mexas@bris.ac.uk Content-Type: text/plain; charset=UTF-8 Cc: freebsd-stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2014 08:29:39 -0000 On Thu, Dec 11, 2014 at 11:15 PM, Anton Shterenlikht wrote: > I'm trying to update from 10.0-RELEASE-p12 amd64 to > 10.0-RELEASE-p13. > > I get: > > # freebsd-update fetch > Looking up update.FreeBSD.org mirrors... 5 mirrors found. > Fetching metadata signature for 10.0-RELEASE from update4.freebsd.org... done. > Fetching metadata index... done. > Inspecting system... done. > Preparing to download files... done. > > The following files will be added as part of updating to 10.0-RELEASE-p13: > /usr/src/contrib/tzdata/zone1970.tab > # freebsd-update install > Installing updates...install: ///usr/src/contrib/tzdata/zone1970.tab: No such file or directory > done. > # You can create the missing directory path: # mkdir -p /usr/src/contrib/tzdata/ freebsd-update does not always create the paths itself. Royce From owner-freebsd-stable@FreeBSD.ORG Fri Dec 12 09:00:55 2014 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3BA1757B for ; Fri, 12 Dec 2014 09:00:55 +0000 (UTC) Received: from smtp.digiware.nl (smtp.digiware.nl [31.223.170.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BE9948E8 for ; Fri, 12 Dec 2014 09:00:54 +0000 (UTC) Received: from rack1.digiware.nl (unknown [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id 5D19D16A403 for ; Fri, 12 Dec 2014 10:00:46 +0100 (CET) X-Virus-Scanned: amavisd-new at digiware.nl Received: from smtp.digiware.nl ([127.0.0.1]) by rack1.digiware.nl (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o5TGQCwWbx08; Fri, 12 Dec 2014 10:00:26 +0100 (CET) Received: from [IPv6:2001:4cb8:3:1:2d10:607d:f923:e425] (unknown [IPv6:2001:4cb8:3:1:2d10:607d:f923:e425]) by smtp.digiware.nl (Postfix) with ESMTP id 06CF916A404 for ; Fri, 12 Dec 2014 09:50:15 +0100 (CET) Message-ID: <548AAC45.8080800@digiware.nl> Date: Fri, 12 Dec 2014 09:50:13 +0100 From: Willem Jan Withagen Organization: Digiware Management b.v. User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: "stable@freebsd.org" Subject: Re: missing /usr/lib/libc_nonshared.a References: <54837FAC.801@digiware.nl> In-Reply-To: <54837FAC.801@digiware.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2014 09:00:55 -0000 On 2014-12-06 23:14, Willem Jan Withagen wrote: > Hi, > > Still trying to upgrade from 9.3 to 10.1, which seemed to get going. > Completely started over again with cleaned out /etc/{make.src}.conf. > Then build/installed 9.3 again which also included clang this time. > > but building the toolchain generates: > -------------------------------------------------------------- >>>> stage 2.3: build tools > -------------------------------------------------------------- > cd /usr/src10; MAKEOBJDIRPREFIX=/usr/obj INSTALL="sh > /usr/src10/tools/install.sh" > PATH=/usr/obj/usr/src10/tmp/legacy/usr/sbin:/usr/obj/usr/src10/tmp/legacy/usr/bin:/usr/obj/usr/src10/tmp/legacy/usr/games:/usr/obj/usr/src10/tmp/legacy/bin:/sbin:/bin:/usr/sbin:/usr/bin > WORLDTMP=/usr/obj/usr/src10/tmp VERSION="FreeBSD 10.1-STABLE amd64 > 1001503" MAKEFLAGS="-m /usr/src10/tools/build/mk -m > /usr/src10/share/mk" COMPILER_TYPE=gcc > /usr/obj/usr/src10/make.amd64/bmake -f Makefile.inc1 TARGET=amd64 > TARGET_ARCH=amd64 DESTDIR= BOOTSTRAPPING=903506 SSP_CFLAGS= > -DNO_LINT -DNO_CPU_CFLAGS -DNO_WARNS -DNO_CTF -DEARLY_BUILD -DNO_TESTS > build-tools > ===> bin/csh (obj,build-tools) > grep 'ERR_' /usr/src10/bin/csh/../../contrib/tcsh/sh.err.c | grep > '^#define' >> sh.err.h > cc -E -O2 -pipe -I. -I/usr/src10/bin/csh > -I/usr/src10/bin/csh/../../contrib/tcsh -D_PATH_TCSHELL='"/bin/csh"' > -std=gnu99 -I/usr/obj/usr/src10/tmp/legacy/usr/include > /usr/src10/bin/csh/../../contrib/tcsh/tc.const.c > /usr/src10/bin/csh/../../contrib/tcsh/sh.char.h > /usr/src10/bin/csh/config.h > /usr/src10/bin/csh/../../contrib/tcsh/config_f.h > /usr/src10/bin/csh/../../contrib/tcsh/sh.types.h sh.err.h -D_h_tc_const > | grep 'Char STR' | sed -e 's/Char \([a-zA-Z0-9_]*\)\(.*\)/extern Char > \1[];/' | sort >> tc.const.h > cc -o gethost -L/usr/obj/usr/src10/tmp/legacy/usr/lib -O2 -pipe -I. > -I/usr/src10/bin/csh -I/usr/src10/bin/csh/../../contrib/tcsh > -D_PATH_TCSHELL='"/bin/csh"' -std=gnu99 > -I/usr/obj/usr/src10/tmp/legacy/usr/include > /usr/src10/bin/csh/../../contrib/tcsh/gethost.c > /usr/bin/ld: cannot find /usr/lib/libc_nonshared.a > *** Error code 1 > ----------------- > > Now I can fudge around this, by getting this lib from another 10.x > system, but changes are that things are nog 100% compatible. > > So how do I get this lib first, before starting to build bin/csh. > > The other question is: > why am I still using gcc for the toolchain even since I now have > clang onboard? Turn out that the only way I could cheat make in to going anywhere was to: cd /usr/src/lib/libc_nonshared make make install And only then the build seems to progress. This all even though the /usr/obj tree holds: [~] wjw > locate libc_non /usr/objs/amd64/usr/src10/lib/libc_nonshared /usr/objs/amd64/usr/src10/lib/libc_nonshared/.depend /usr/objs/amd64/usr/src10/lib/libc_nonshared/__iconv.o /usr/objs/amd64/usr/src10/lib/libc_nonshared/__iconv_free_list.o /usr/objs/amd64/usr/src10/lib/libc_nonshared/__iconv_get_list.o /usr/objs/amd64/usr/src10/lib/libc_nonshared/__stub.o /usr/objs/amd64/usr/src10/lib/libc_nonshared/iconv.o /usr/objs/amd64/usr/src10/lib/libc_nonshared/iconv_canonicalize.o /usr/objs/amd64/usr/src10/lib/libc_nonshared/iconv_close.o /usr/objs/amd64/usr/src10/lib/libc_nonshared/iconv_open.o /usr/objs/amd64/usr/src10/lib/libc_nonshared/iconv_open_into.o /usr/objs/amd64/usr/src10/lib/libc_nonshared/iconv_set_relocation_prefix.o /usr/objs/amd64/usr/src10/lib/libc_nonshared/iconvctl.o /usr/objs/amd64/usr/src10/lib/libc_nonshared/iconvlist.o /usr/objs/amd64/usr/src10/lib/libc_nonshared/libc_nonshared.a /usr/objs/amd64/usr/src10/tmp/usr/lib/libc_nonshared.a And I would expect csh to be build against: /usr/objs/amd64/usr/src10/tmp/usr/lib/libc_nonshared.a But for what happened, I conclude that it is linked against /usr/lib. --WjW From owner-freebsd-stable@FreeBSD.ORG Fri Dec 12 09:36:32 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C711BB08 for ; Fri, 12 Dec 2014 09:36:32 +0000 (UTC) Received: from eu1sys200aog133.obsmtp.com (eu1sys200aog133.obsmtp.com [207.126.144.209]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 22D95C2B for ; Fri, 12 Dec 2014 09:36:31 +0000 (UTC) Received: from mail-wi0-f180.google.com ([209.85.212.180]) (using TLSv1) by eu1sys200aob133.postini.com ([207.126.147.11]) with SMTP ID DSNKVIq3F8vSzVwEEFVbeyTPiDw1jc5Elc0o@postini.com; Fri, 12 Dec 2014 09:36:32 UTC Received: by mail-wi0-f180.google.com with SMTP id n3so1903444wiv.13 for ; Fri, 12 Dec 2014 01:36:23 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:message-id:to:subject:reply-to; bh=gox4LYR7vVACXC0q7j+9Akycpd1YId70F1AG6deosCA=; b=mD3pEXg9VxveE1a5YgtU6jdbTdU9xY9p1GiodCRHK5jNQxCP24dhMyQnYClEm9vWm8 ddWI08uDhRPTlOqb0CIZSQqzYiBcO37W9GYnfz4H68VX8kWcUpy19VarwG4VMOnSUAZJ 0oRerUrrE/jKdvNt2gyJxX+zq+PbRnFJaJ/YjNgh+m/0GVsn3AA3UM9HtnAJjgIAKWdc ciR7XmR6mOUhEPxa19LPyITPB/EjY6aZA8bnw3ibYLh/jcViKMNREU5xkzTO0c3N29/T 2AxjcVIWmSo3wINFx/V7jRJGal1qJmAGMcrc/UDZauydCz3X1ascKnIs5lNUTALH4vtJ lJAA== X-Received: by 10.194.94.132 with SMTP id dc4mr25979025wjb.56.1418376632486; Fri, 12 Dec 2014 01:30:32 -0800 (PST) X-Gm-Message-State: ALoCoQkXIr5QYyjRxlOy7EOupeImoSWopaguCdH9IFilufhRZozeRf1gFCX4jqvvoXaE51Qje4pnsbwVvnmNaS5KjDxwRWPYuovgDkSO6RLcGvOJ8sA99HroGYuZDm11iNs7ABYLCbU/+dJya7Cl05HIGhJj0JW8fw== X-Received: by 10.194.94.132 with SMTP id dc4mr25979006wjb.56.1418376632354; Fri, 12 Dec 2014 01:30:32 -0800 (PST) Received: from mech-as221.men.bris.ac.uk (mech-as221.men.bris.ac.uk. [137.222.187.221]) by mx.google.com with ESMTPSA id d2sm1048216wjs.32.2014.12.12.01.30.31 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 12 Dec 2014 01:30:31 -0800 (PST) Date: Fri, 12 Dec 2014 01:30:31 -0800 (PST) X-Google-Original-Date: Fri, 12 Dec 2014 09:30:30 GMT Received: from mech-as221.men.bris.ac.uk (localhost [127.0.0.1]) by mech-as221.men.bris.ac.uk (8.14.9/8.14.9) with ESMTP id sBC9UURT041707 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Fri, 12 Dec 2014 09:30:30 GMT (envelope-from mexas@mech-as221.men.bris.ac.uk) Received: (from mexas@localhost) by mech-as221.men.bris.ac.uk (8.14.9/8.14.9/Submit) id sBC9UUEF041702 for freebsd-stable@freebsd.org; Fri, 12 Dec 2014 09:30:30 GMT (envelope-from mexas) From: Anton Shterenlikht Message-Id: <201412120930.sBC9UUEF041702@mech-as221.men.bris.ac.uk> To: freebsd-stable@freebsd.org Subject: wrong patchlevel after freebsd-update install? Reply-To: mexas@bris.ac.uk X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2014 09:36:32 -0000 On 10.0-RELEASE-p12 amd64 I updated to p13 as: freebsd-update fetch freebsd-update install reboot However, uname still shows the old patchlevel: # uname -a FreeBSD 001cc0f01814.anet.bris.ac.uk 10.0-RELEASE-p12 FreeBSD 10.0-RELEASE-p12 #0: Tue Nov 4 05:07:17 UTC 2014 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 # But freebsd-update fetch suggests I'm already at p13: # freebsd-update fetch Looking up update.FreeBSD.org mirrors... 5 mirrors found. Fetching metadata signature for 10.0-RELEASE from update5.freebsd.org... done. Fetching metadata index... done. Inspecting system... done. Preparing to download files... done. No updates needed to update system to 10.0-RELEASE-p13. # So has the update p12 -> p13 succeded? Please clarify Thanks Anton From owner-freebsd-stable@FreeBSD.ORG Fri Dec 12 09:41:01 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E35C7DAF for ; Fri, 12 Dec 2014 09:41:01 +0000 (UTC) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A4DFCCF1 for ; Fri, 12 Dec 2014 09:41:01 +0000 (UTC) Received: from pi by home.opsec.eu with local (Exim 4.82 (FreeBSD)) (envelope-from ) id 1XzMiZ-000MQ0-BH; Fri, 12 Dec 2014 10:40:59 +0100 Date: Fri, 12 Dec 2014 10:40:59 +0100 From: Kurt Jaeger To: Anton Shterenlikht Subject: Re: wrong patchlevel after freebsd-update install? Message-ID: <20141212094059.GX44537@home.opsec.eu> References: <201412120930.sBC9UUEF041702@mech-as221.men.bris.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201412120930.sBC9UUEF041702@mech-as221.men.bris.ac.uk> Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2014 09:41:02 -0000 Hi! > On 10.0-RELEASE-p12 amd64 I updated to p13 as: > > freebsd-update fetch > freebsd-update install > reboot Please add another freebsd-update install for the user-space. > But freebsd-update fetch suggests I'm already at p13: Yes. > So has the update p12 -> p13 succeded? I think, yes. Use freebsd-version to compare. Some updates only change userspace, not kernels and uname stays on the old patch level. Yes, annoying, not trivial to fix. -- pi@opsec.eu +49 171 3101372 6 years to go ! From owner-freebsd-stable@FreeBSD.ORG Fri Dec 12 09:56:35 2014 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 27AC9FAD for ; Fri, 12 Dec 2014 09:56:35 +0000 (UTC) Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A8BA2E19 for ; Fri, 12 Dec 2014 09:56:34 +0000 (UTC) Received: by mail-wi0-f169.google.com with SMTP id r20so3984911wiv.4 for ; Fri, 12 Dec 2014 01:56:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type; bh=NVPRL4cszQQu6NajdIzUHif5hfRStjJD3SvY6PX9BQg=; b=f3t/BiOTAhyuKz5J872cRPjpokFAy1P/xt2YOryvbMwRNXlAgMeGrTVgrL+MJEkUu6 uWAn5pZvvkDg8cqZdv7LaQkw1jfpgJISGJiW2kRAIypHoPk8rmrIMMa0e9cKrgfETYQf uOnzku6FNKSmXIY3n2cnM3LK37U+DWkD1kU7ylEak52rmPnwVBS2AuVGZ9trP1lvalPc oy6+TvoUTWNZVXep1fup/MyBx7fDDISAKSa0YT70ARnZBx2zqu2P8LCjwKI2J0CLCKoJ BpsLDNXHYLoiUlW5zTboNyH+a4FfT+myXBMYwD3xWPX/DHJOOT/5WJrnQwcRQlDhVL1T 14ww== X-Received: by 10.180.73.178 with SMTP id m18mr5839654wiv.65.1418378192856; Fri, 12 Dec 2014 01:56:32 -0800 (PST) Received: from t510.bsoft-company.ro (ip5450aabf.adsl-surfen.hetnet.nl. [84.80.170.191]) by mx.google.com with ESMTPSA id f7sm1377470wiz.13.2014.12.12.01.56.32 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 12 Dec 2014 01:56:32 -0800 (PST) Message-ID: <548ABBCF.2020701@gmail.com> Date: Fri, 12 Dec 2014 10:56:31 +0100 From: Andrei Brezan User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: stable@freebsd.org Subject: Kernel panic when closing Xorg Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2014 09:56:35 -0000 Hi, I can replicate this as it happens almost every time (3 out of last for attempts) I close the Xorg server. It happens on FreeBSD 10.1-STABLE #0 r275689 with generic kernel. What I don't understand why the instruction pointer is 0x0 and where to go from here. I'm running latest packages from the ports tree. Someone please let me know there is a path to go from here: http://pastebin.com/zdkZ98W1 Thanks, -- Andrei From owner-freebsd-stable@FreeBSD.ORG Fri Dec 12 10:24:36 2014 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6FB996AF for ; Fri, 12 Dec 2014 10:24:36 +0000 (UTC) Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com [IPv6:2a00:1450:400c:c05::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 08BD5164 for ; Fri, 12 Dec 2014 10:24:35 +0000 (UTC) Received: by mail-wi0-f182.google.com with SMTP id h11so2068595wiw.3 for ; Fri, 12 Dec 2014 02:24:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type; bh=NiTtfQ6ci5QVm5nCeu+PHzORUgjI7B8bs9kHCNnPcOI=; b=XIggAokQnaXQ5HDgaxzSCBJiFguZbY4XViCnQ1ibzt5g8sbozECUpcDz3RfIt4DxQc bNEy0kRfqtpONXeE4vY/MZIQLcy4XQi5zRgbda+Guj98NXXEX37twj7+4TfHNkP42VJv UWs2n9G8vWhClEo84b2Gb2sL0SE8toTXk1ynUfYLfVc79NsI/jRPLfA9VOozQ+RezJtc DH32HAt5JLVVmGpx4dnWNNuEfY7fkcQ70o3U+1dptAmawzobgv2unlVgNYcyE8gBkOcP dxTQt+JCTEFrBHp0fFNP4STdOWigsbdFDThjk2mSaVjw0q08TNXSOhyVXs6Y9nz7z2kD wBhQ== X-Received: by 10.180.218.39 with SMTP id pd7mr6288014wic.21.1418379874078; Fri, 12 Dec 2014 02:24:34 -0800 (PST) Received: from t510.bsoft-company.ro (ip5450aabf.adsl-surfen.hetnet.nl. [84.80.170.191]) by mx.google.com with ESMTPSA id c10sm1252451wjy.4.2014.12.12.02.24.33 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 12 Dec 2014 02:24:33 -0800 (PST) Message-ID: <548AC261.6090703@gmail.com> Date: Fri, 12 Dec 2014 11:24:33 +0100 From: Andrei Brezan User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: stable@freebsd.org Subject: Re: Kernel panic when closing Xorg References: <548ABBCF.2020701@gmail.com> In-Reply-To: <548ABBCF.2020701@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2014 10:24:36 -0000 On 12/12/14 10:56, Andrei Brezan wrote: > Hi, > > I can replicate this as it happens almost every time (3 out of last > for attempts) I close the Xorg server. It happens on FreeBSD > 10.1-STABLE #0 r275689 with generic kernel. What I don't understand > why the instruction pointer is 0x0 and where to go from here. I'm > running latest packages from the ports tree. > > Someone please let me know there is a path to go from here: > http://pastebin.com/zdkZ98W1 Tried a few more times, 3 out of 6 attempts to quit X resulted in a kernel panic. After a couple of successful start/stop sequences for X it panicked in the same manner shortly after it started up. -- Andrei From owner-freebsd-stable@FreeBSD.ORG Fri Dec 12 10:41:37 2014 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2A33093C for ; Fri, 12 Dec 2014 10:41:37 +0000 (UTC) Received: from mail-wg0-x22f.google.com (mail-wg0-x22f.google.com [IPv6:2a00:1450:400c:c00::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id ABE3D373 for ; Fri, 12 Dec 2014 10:41:36 +0000 (UTC) Received: by mail-wg0-f47.google.com with SMTP id n12so8766623wgh.20 for ; Fri, 12 Dec 2014 02:41:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type; bh=DQ35HNi5Eu8mmpOJE2Vbuom4+JEsw0j9I1s8u9ssq7g=; b=KOMNX9zY1qg+N+LWX+3s1kIDTLR+OwSdeurMZi0idUkM0jR84k2TVRnQgoEZSZSvy0 EiFvO8L2q1jooQX9i5qJo0E0s+gcIVNgsnJ98s21ZiuXXr59f0XV2ZkSTyeOu2PgTFdm qe4UlsnB8l3BpEm8F2AkTBG5pryAGrHNIFvIYnhkOZy/SP3DkMYI8jIsncpd8eCUicE0 407pIWoAQVgMyISYvxVliG26vtuPmezonts1GWlj8IutpGmbfHKSt1oUhgOMIGXW4vKi dXzYBb7YlvRVJioOy80TBUVgUlrYcYaHSOBT+IUTSZ55IfEIZwW/RvOKEbjiDIhR/iDg bPBw== X-Received: by 10.194.191.227 with SMTP id hb3mr26203896wjc.79.1418380895122; Fri, 12 Dec 2014 02:41:35 -0800 (PST) Received: from t510.bsoft-company.ro (ip5450aabf.adsl-surfen.hetnet.nl. [84.80.170.191]) by mx.google.com with ESMTPSA id gf6sm1300375wjc.11.2014.12.12.02.41.34 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 12 Dec 2014 02:41:34 -0800 (PST) Message-ID: <548AC65E.6070208@gmail.com> Date: Fri, 12 Dec 2014 11:41:34 +0100 From: Andrei Brezan User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: stable@freebsd.org Subject: Re: Kernel panic when closing Xorg References: <548ABBCF.2020701@gmail.com> <548AC261.6090703@gmail.com> In-Reply-To: <548AC261.6090703@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2014 10:41:37 -0000 On 12/12/14 11:24, Andrei Brezan wrote: > On 12/12/14 10:56, Andrei Brezan wrote: >> Hi, >> >> I can replicate this as it happens almost every time (3 out of last >> for attempts) I close the Xorg server. It happens on FreeBSD >> 10.1-STABLE #0 r275689 with generic kernel. What I don't understand >> why the instruction pointer is 0x0 and where to go from here. I'm >> running latest packages from the ports tree. >> >> Someone please let me know there is a path to go from here: >> http://pastebin.com/zdkZ98W1 > > Tried a few more times, 3 out of 6 attempts to quit X resulted in a > kernel panic. After a couple of successful start/stop sequences for X > it panicked in the same manner shortly after it started up. Sorry for the noise, seems to be an issue with the nvidia-driver, followed http://docs.freebsd.org/cgi/getmsg.cgi?fetch=112339+0+current/freebsd-x11, updated the driver and it seems to be working ok now. -- Andrei From owner-freebsd-stable@FreeBSD.ORG Fri Dec 12 11:16:57 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 487B3E3 for ; Fri, 12 Dec 2014 11:16:57 +0000 (UTC) Received: from eu1sys200aog135.obsmtp.com (eu1sys200aog135.obsmtp.com [207.126.144.213]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 58AD18C8 for ; Fri, 12 Dec 2014 11:16:03 +0000 (UTC) Received: from mail-wi0-f180.google.com ([209.85.212.180]) (using TLSv1) by eu1sys200aob135.postini.com ([207.126.147.11]) with SMTP ID DSNKVIrOVq2KhNUvIsX58BAWjoJr6184sOMj@postini.com; Fri, 12 Dec 2014 11:16:04 UTC Received: by mail-wi0-f180.google.com with SMTP id n3so2211369wiv.1 for ; Fri, 12 Dec 2014 03:15:34 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:message-id:to:subject:cc:reply-to :in-reply-to; bh=er6ca1sGYUllHZZSb6sutcvGBP5Neimn2BipeaDakeQ=; b=D+x1n39+vypz1LdijIrB3cPVfeL+B1ICCb3cxl//UOmQwgYhC6NTxpKAJX/4Cl4vR0 NRI2Fake9KfJrxnzGRpQYiFSf6wPVJlCYVPJBcGKER/d8+aMfsgw1di5GSxoYrYhMJ6W HbpMfl7JbdvlBjEe+T9ffsDGlZmzEYJfBwBjgVKWHRVGB4Tx+XlBwqWD3dVQCVFN672C FjZJVlXT45FwYLqeewgBG0pjH/w63SxhUW3S/zkfPiCMnIFZ1q7qf4xjUUV7aYbkC2oa NjnwdeuBh8qZgkdtRmxrlerspl7zcfvwWCTRqWSFghrYT59dwBApSasBg0srSNwOkQtG YuFw== X-Gm-Message-State: ALoCoQnNuBQkn62/z/ndHgd+qKPt0KEeIF8bNyWnmFP/iX1IGJQ+daH7Ygr52yvPAnHWgY6ijyZS5PBpZCXms5CPp4pWMK/MeDD5JIOC6d2gU/othe/SzO6E3HnMSYrMf4Q69+VXLY6q3uQpAIc07cKMF5vUs4Z/Qw== X-Received: by 10.181.13.42 with SMTP id ev10mr6550680wid.78.1418382934088; Fri, 12 Dec 2014 03:15:34 -0800 (PST) X-Received: by 10.181.13.42 with SMTP id ev10mr6550666wid.78.1418382933989; Fri, 12 Dec 2014 03:15:33 -0800 (PST) Received: from mech-as221.men.bris.ac.uk (mech-as221.men.bris.ac.uk. [137.222.187.221]) by mx.google.com with ESMTPSA id h13sm1546417wiw.4.2014.12.12.03.15.32 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 12 Dec 2014 03:15:33 -0800 (PST) Date: Fri, 12 Dec 2014 03:15:33 -0800 (PST) X-Google-Original-Date: Fri, 12 Dec 2014 11:15:31 GMT Received: from mech-as221.men.bris.ac.uk (localhost [127.0.0.1]) by mech-as221.men.bris.ac.uk (8.14.9/8.14.9) with ESMTP id sBCBFWj3027867 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 12 Dec 2014 11:15:32 GMT (envelope-from mexas@mech-as221.men.bris.ac.uk) Received: (from mexas@localhost) by mech-as221.men.bris.ac.uk (8.14.9/8.14.9/Submit) id sBCBFV3m027866; Fri, 12 Dec 2014 11:15:31 GMT (envelope-from mexas) From: Anton Shterenlikht Message-Id: <201412121115.sBCBFV3m027866@mech-as221.men.bris.ac.uk> To: lists@opsec.eu, mexas@bris.ac.uk Subject: Re: wrong patchlevel after freebsd-update install? Reply-To: mexas@bris.ac.uk In-Reply-To: <20141212094059.GX44537@home.opsec.eu> Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2014 11:16:57 -0000 >From lists@opsec.eu Fri Dec 12 11:09:15 2014 > >Please add another > >freebsd-update install > >for the user-space. Sorry, what do you mean by "user-space"? Running freebsd-update install now does not achive anything: # freebsd-update install No updates are available to install. # >Use > >freebsd-version > >to compare. % freebsd-version 10.0-RELEASE-p13 > Some updates only change userspace, not kernels and >uname stays on the old patch level. Yes, annoying, not trivial to fix. Perhaps this is the case. Thanks Anton From owner-freebsd-stable@FreeBSD.ORG Fri Dec 12 11:18:28 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7C0A71EA for ; Fri, 12 Dec 2014 11:18:28 +0000 (UTC) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3DA7E8E5 for ; Fri, 12 Dec 2014 11:18:28 +0000 (UTC) Received: from pi by home.opsec.eu with local (Exim 4.82 (FreeBSD)) (envelope-from ) id 1XzOEt-000MeL-LK; Fri, 12 Dec 2014 12:18:27 +0100 Date: Fri, 12 Dec 2014 12:18:27 +0100 From: Kurt Jaeger To: Anton Shterenlikht Subject: Re: wrong patchlevel after freebsd-update install? Message-ID: <20141212111827.GY44537@home.opsec.eu> References: <20141212094059.GX44537@home.opsec.eu> <201412121115.sBCBFV3m027866@mech-as221.men.bris.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201412121115.sBCBFV3m027866@mech-as221.men.bris.ac.uk> Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2014 11:18:28 -0000 Hi! > >From lists@opsec.eu Fri Dec 12 11:09:15 2014 > > > >Please add another > > > >freebsd-update install > > > >for the user-space. > > Sorry, what do you mean by "user-space"? Some updates install kernel-updates and user-space changes. Some only kernel-updates, and other only user-space changes. > Running freebsd-update install now does not achive anything: > > # freebsd-update install > No updates are available to install. > # Then the second ... install was not necessary, I see. p12 -> p13 was a user-space only update. -- pi@opsec.eu +49 171 3101372 6 years to go ! From owner-freebsd-stable@FreeBSD.ORG Fri Dec 12 13:09:50 2014 Return-Path: Delivered-To: stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BA198543 for ; Fri, 12 Dec 2014 13:09:50 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A279A6CE for ; Fri, 12 Dec 2014 13:09:50 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sBCD9oN0045185 for ; Fri, 12 Dec 2014 13:09:50 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: stable@FreeBSD.org Subject: [Bug 193360] [panic] [syscons] random syscons panic Date: Fri, 12 Dec 2014 13:09:50 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 9.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: sasamotikomi@gmail.com X-Bugzilla-Status: New X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2014 13:09:50 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193360 --- Comment #3 from sasamotikomi@gmail.com --- (In reply to John Baldwin from comment #2) > For these and the other various PRs you opened recently, you need to remove > the 'grep 0x' from the 'nm -n' output. That removes most of the useful > symbols and isn't helpful. In addition, far more useful would be to get > stack traces, especially if you have core.txt.N files, the kgdb stack trace > in that file would be the first thing needed to look at any of these. > > As I mentioned on another bug, a dmesg from this machine wouldn't hurt > either, but I doubt that either ed(4) or xl(4) is relevant. nm -n /boot/kernel9.1/kernel | grep c0e1e c0e1e170 t pmap_update_pde_user c0e1e1a0 T pmap_lazyfix_action c0e1e1f0 T pmap_copy_page c0e1e350 T pmap_release c0e1e600 T pmap_activate c0e1e6f0 T pmap_kenter_temporary c0e1e730 T pmap_map c0e1e820 T pmap_unmapdev c0e1e8c0 t pmap_unuse_pt c0e1e920 t pmap_remove_pte c0e1ea00 t pmap_remove_page c0e1ea50 t get_pv_entry -- You are receiving this mail because: You are on the CC list for the bug. From owner-freebsd-stable@FreeBSD.ORG Fri Dec 12 15:12:28 2014 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id ABD37A89 for ; Fri, 12 Dec 2014 15:12:28 +0000 (UTC) Received: from tensor.andric.com (tensor.andric.com [IPv6:2001:7b8:3a7:1:2d0:b7ff:fea0:8c26]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "tensor.andric.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 39E876B4 for ; Fri, 12 Dec 2014 15:12:28 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7::9c14:1cbd:353e:a894] (unknown [IPv6:2001:7b8:3a7:0:9c14:1cbd:353e:a894]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 23858B80A; Fri, 12 Dec 2014 16:12:24 +0100 (CET) Subject: Re: missing /usr/lib/libc_nonshared.a Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Content-Type: multipart/signed; boundary="Apple-Mail=_32F4F639-CDA8-499A-803A-C3C5C572DE73"; protocol="application/pgp-signature"; micalg=pgp-sha1 X-Pgp-Agent: GPGMail 2.5b3 From: Dimitry Andric In-Reply-To: <548AAC45.8080800@digiware.nl> Date: Fri, 12 Dec 2014 16:12:10 +0100 Message-Id: References: <54837FAC.801@digiware.nl> <548AAC45.8080800@digiware.nl> To: Willem Jan Withagen X-Mailer: Apple Mail (2.1993) Cc: "stable@freebsd.org" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2014 15:12:28 -0000 --Apple-Mail=_32F4F639-CDA8-499A-803A-C3C5C572DE73 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii On 12 Dec 2014, at 09:50, Willem Jan Withagen wrote: > > On 2014-12-06 23:14, Willem Jan Withagen wrote: >> Still trying to upgrade from 9.3 to 10.1, which seemed to get going. >> Completely started over again with cleaned out /etc/{make.src}.conf. >> Then build/installed 9.3 again which also included clang this time. >> >> but building the toolchain generates: >> -------------------------------------------------------------- >>>>> stage 2.3: build tools >> -------------------------------------------------------------- ... >> cc -o gethost -L/usr/obj/usr/src10/tmp/legacy/usr/lib -O2 -pipe -I. >> -I/usr/src10/bin/csh -I/usr/src10/bin/csh/../../contrib/tcsh >> -D_PATH_TCSHELL='"/bin/csh"' -std=gnu99 >> -I/usr/obj/usr/src10/tmp/legacy/usr/include >> /usr/src10/bin/csh/../../contrib/tcsh/gethost.c >> /usr/bin/ld: cannot find /usr/lib/libc_nonshared.a >> *** Error code 1 >> ----------------- >> >> Now I can fudge around this, by getting this lib from another 10.x >> system, but changes are that things are nog 100% compatible. >> >> So how do I get this lib first, before starting to build bin/csh. This part of buildworld uses the compiler, include files, linker and libraries from your existing system. E.g. it is normal for this part to use /usr/bin/ld, /usr/lib, and so on. On a 9.3 system, I would not expect ld to search for libc_nonshared.a, since that is a feature introduced in 10.0, where /usr/lib/libc.so was changed from a symlink to a linker script. Can you please check on your system, what /usr/lib/libc.so is? Is it a symlink or a plain text file? If it is the latter, your system is most likely polluted with 10.x installation left-overs. >> >> The other question is: >> why am I still using gcc for the toolchain even since I now have >> clang onboard? For the early stages of buildworld, e.g. bootstrap-tools, build-tools and cross-tools, it is normal that the system compiler is used, e.g. just /usr/bin/cc. On a 9.x system, that is usually gcc, but this does not say anything about the later stages of buildworld, which will be built with the toolchain produced in the cross-tools stage. For 10.x, that is usually clang. > Turn out that the only way I could cheat make in to going anywhere was to: > cd /usr/src/lib/libc_nonshared > make > make install > > And only then the build seems to progress. I think it is better to inspect your /usr/lib/libc.so, and find out if it is accidentally replaced by a linker script. > This all even though the /usr/obj tree holds: > [~] wjw > locate libc_non > /usr/objs/amd64/usr/src10/lib/libc_nonshared > /usr/objs/amd64/usr/src10/lib/libc_nonshared/.depend > /usr/objs/amd64/usr/src10/lib/libc_nonshared/__iconv.o > /usr/objs/amd64/usr/src10/lib/libc_nonshared/__iconv_free_list.o > /usr/objs/amd64/usr/src10/lib/libc_nonshared/__iconv_get_list.o > /usr/objs/amd64/usr/src10/lib/libc_nonshared/__stub.o > /usr/objs/amd64/usr/src10/lib/libc_nonshared/iconv.o > /usr/objs/amd64/usr/src10/lib/libc_nonshared/iconv_canonicalize.o > /usr/objs/amd64/usr/src10/lib/libc_nonshared/iconv_close.o > /usr/objs/amd64/usr/src10/lib/libc_nonshared/iconv_open.o > /usr/objs/amd64/usr/src10/lib/libc_nonshared/iconv_open_into.o > /usr/objs/amd64/usr/src10/lib/libc_nonshared/iconv_set_relocation_prefix.o > /usr/objs/amd64/usr/src10/lib/libc_nonshared/iconvctl.o > /usr/objs/amd64/usr/src10/lib/libc_nonshared/iconvlist.o > /usr/objs/amd64/usr/src10/lib/libc_nonshared/libc_nonshared.a > /usr/objs/amd64/usr/src10/tmp/usr/lib/libc_nonshared.a > > And I would expect csh to be build against: > /usr/objs/amd64/usr/src10/tmp/usr/lib/libc_nonshared.a > > But for what happened, I conclude that it is linked against /usr/lib. During the early stages of buildworld, this is completely normal, and expected. -Dimitry --Apple-Mail=_32F4F639-CDA8-499A-803A-C3C5C572DE73 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.26 iEYEARECAAYFAlSLBdYACgkQsF6jCi4glqP9pgCgjtcTGQ1BYiH5C+6kTYacMCD1 rvoAnRgpy7TacFCzRZEAFMImRJo4Bqiq =RxbK -----END PGP SIGNATURE----- --Apple-Mail=_32F4F639-CDA8-499A-803A-C3C5C572DE73-- From owner-freebsd-stable@FreeBSD.ORG Fri Dec 12 15:30:14 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5000EFDD for ; Fri, 12 Dec 2014 15:30:14 +0000 (UTC) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.126.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gromit.dlib.vt.edu", Issuer "Chumby Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 2496B894 for ; Fri, 12 Dec 2014 15:30:13 +0000 (UTC) Received: from macbook.chumby.lan (c-71-63-94-21.hsd1.va.comcast.net [71.63.94.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gromit.dlib.vt.edu (Postfix) with ESMTPSA id 87975119; Fri, 12 Dec 2014 10:23:04 -0500 (EST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: wrong patchlevel after freebsd-update install? From: Paul Mather In-Reply-To: <201412120930.sBC9UUEF041702@mech-as221.men.bris.ac.uk> Date: Fri, 12 Dec 2014 10:23:03 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: <7B7C7B31-B89F-4770-8DA1-CE7D0BD513EB@gromit.dlib.vt.edu> References: <201412120930.sBC9UUEF041702@mech-as221.men.bris.ac.uk> To: mexas@bris.ac.uk X-Mailer: Apple Mail (2.1878.6) Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2014 15:30:14 -0000 On Dec 12, 2014, at 4:30 AM, Anton Shterenlikht = wrote: > On 10.0-RELEASE-p12 amd64 I updated to p13 as: >=20 > freebsd-update fetch > freebsd-update install > reboot >=20 > However, uname still shows the old patchlevel: >=20 > # uname -a > FreeBSD 001cc0f01814.anet.bris.ac.uk 10.0-RELEASE-p12 FreeBSD = 10.0-RELEASE-p12 #0: Tue Nov 4 05:07:17 UTC 2014 = root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 > # >=20 > But freebsd-update fetch suggests I'm already at p13: >=20 > # freebsd-update fetch > Looking up update.FreeBSD.org mirrors... 5 mirrors found. > Fetching metadata signature for 10.0-RELEASE from = update5.freebsd.org... done. > Fetching metadata index... done. > Inspecting system... done. > Preparing to download files... done. >=20 > No updates needed to update system to 10.0-RELEASE-p13. > # >=20 > So has the update p12 -> p13 succeeded? What does "freebsd-version" report? If it returns 10.0-RELEASE-p13 then = your freebsd-update succeeded. > Please clarify It's my understanding that uname only gets updated when freebsd-update = updates the kernel. I think that's why freebsd-version was introduced. >=20 > Thanks >=20 > Anton Cheers, Paul. From owner-freebsd-stable@FreeBSD.ORG Fri Dec 12 15:32:24 2014 Return-Path: Delivered-To: stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2CEC4198 for ; Fri, 12 Dec 2014 15:32:24 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 155A3956 for ; Fri, 12 Dec 2014 15:32:24 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sBCFWNRO097579 for ; Fri, 12 Dec 2014 15:32:23 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: stable@FreeBSD.org Subject: [Bug 193389] [panic] ufs_dirbad: /: bad dir Date: Fri, 12 Dec 2014 15:32:24 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: mikej@mikej.com X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2014 15:32:24 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193389 mikej@mikej.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mikej@mikej.com --- Comment #3 from mikej@mikej.com --- I am also getting this error under current. FreeBSD d620 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r275582: Mon Dec 8 02:36:47 UTC 2014 root@grind.freebsd.org:/usr/obj/usr/src/sys/GENERIC i386 panic: ufs_dirbad: /: bad dir ino 8668611 at offset 12288: mangled entry http://mail.mikej.com/core.txt.0 http://mail.mikej.com/info.0 http://mail.mikej.com/core.txt.1 http://mail.mikej.com/info.1 http://mail.mikej.com/smartctl-a.ada0 http://mail.mikej.com/dmesg.d620 I am getting DMA errors on the device though, not sure if this is a driver or disk problem. This is a SSD device, the laptop had been running with a Seagate Momentus under windows and linux without issue. I will swap drives tonight and see if the problem is isolated to the SSD or not and report back and perform any other suggested tasks for trouble shooting. Now this is so odd I will mention it but I can't fathom why it would matter, but all my panics have always happened immediately after running "man". So far no panics while running X, firefox, and a lot of other applications. Thanks. -- You are receiving this mail because: You are on the CC list for the bug. From owner-freebsd-stable@FreeBSD.ORG Fri Dec 12 19:34:55 2014 Return-Path: Delivered-To: stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7175142F for ; Fri, 12 Dec 2014 19:34:55 +0000 (UTC) Received: from nagini.codelibre.net (nagini.codelibre.net [IPv6:2001:41c8:1:5750::2]) by mx1.freebsd.org (Postfix) with ESMTP id D028982B for ; Fri, 12 Dec 2014 19:34:54 +0000 (UTC) Received: by nagini.codelibre.net (Postfix, from userid 1000) id 4836118714; Fri, 12 Dec 2014 19:34:47 +0000 (GMT) Date: Fri, 12 Dec 2014 19:34:47 +0000 From: Roger Leigh To: stable@FreeBSD.org Subject: Hard system lockups with 10.1, probably drm/newcons/radeonkms-related Message-ID: <20141212193447.GA1657@codelibre.net> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="3uo+9/B/ebqu+fSQ" Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2014 19:34:55 -0000 --3uo+9/B/ebqu+fSQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi folks, With 10.1-RELEASE, I've enabled newcons at boot with kern.vty="vt" in loader.conf. With the latest Xorg/drm installed with pkg, I'm seeing intermittent hangs and hard lockups of the system. I've included the logs for one which recovered earlier today, but later on it just locked up completely and I don't have logs for that since I had to do a hard reset. I had to install and enable hal+dbus to get a working keyboard and mouse when running X, despite both working fine on the console! Not sure what the trigger is. Possibly also related to input. The first hard hang was after logging in with "mwm" via kdm4. It didn't start mwm, so I ran "mwm&" in the xterm; it locked up when I clicked and dragged the window title, i.e. when initiating the drag event. The second hang was while typing into a tmux session inside a konsole window. Nothing particularly special happening at the moment it locked up. I'm happy to do further debugging, but given that it locks up the whole system, I'm not sure how to go about getting any useful information at that point. The graphics card is an AMD Radeon HD 6800 Series using /dev/dri/card0. Starting X11 automatically loads the needed modules: # kldstat Id Refs Address Size Name 1 59 0xffffffff80200000 1755658 kernel 2 1 0xffffffff81956000 267f48 zfs.ko 3 2 0xffffffff81bbe000 6780 opensolaris.ko 4 1 0xffffffff81c11000 2b58 uhid.ko 5 1 0xffffffff81c14000 357f ums.ko 6 2 0xffffffff81c18000 28c0 vboxnetflt.ko 7 2 0xffffffff81c1b000 b998 netgraph.ko 8 2 0xffffffff81c27000 434c0 vboxdrv.ko 9 1 0xffffffff81c6b000 40a7 ng_ether.ko 10 1 0xffffffff81c70000 3ec0 vboxnetadp.ko 11 1 0xffffffff81c74000 11a57a radeonkms.ko 12 1 0xffffffff81d8f000 47f80 drm2.ko 13 4 0xffffffff81dd7000 1ff2 iicbus.ko 14 1 0xffffffff81dd9000 1a46 iic.ko 15 1 0xffffffff81ddb000 1e48 iicbb.ko 16 1 0xffffffff81ddd000 18f3 radeonkmsfw_BARTS_pfp.ko 17 1 0xffffffff81ddf000 1ce8 radeonkmsfw_BARTS_me.ko 18 1 0xffffffff81de1000 136f radeonkmsfw_BTC_rlc.ko 19 1 0xffffffff81de3000 6585 radeonkmsfw_BARTS_mc.ko Kernel log for the recoverable hang: Dec 12 13:23:23 sorilea kernel: drmn0: error: GPU lockup CP stall for more than 10000m sec Dec 12 13:23:23 sorilea kernel: drmn0: warning: GPU lockup (waiting for 0x000000000008 7184 last fence id 0x0000000000087177) Dec 12 13:23:23 sorilea kernel: drmn0: info: Saved 407 dwords of commands on ring 0. Dec 12 13:23:23 sorilea kernel: drmn0: info: GPU softreset: 0x00000003 Dec 12 13:23:23 sorilea kernel: drmn0: info: GRBM_STATUS = 0xA0003828 Dec 12 13:23:23 sorilea kernel: drmn0: info: GRBM_STATUS_SE0 = 0x00000007 Dec 12 13:23:23 sorilea kernel: drmn0: info: GRBM_STATUS_SE1 = 0x00000007 Dec 12 13:23:23 sorilea kernel: drmn0: info: SRBM_STATUS = 0x200000C0 Dec 12 13:23:23 sorilea kernel: drmn0: info: R_008674_CP_STALLED_STAT1 = 0x00000000 Dec 12 13:23:23 sorilea kernel: drmn0: info: R_008678_CP_STALLED_STAT2 = 0x00010100 Dec 12 13:23:23 sorilea kernel: drmn0: info: R_00867C_CP_BUSY_STAT = 0x00020182 Dec 12 13:23:23 sorilea kernel: drmn0: info: R_008680_CP_STAT = 0x80038243 Dec 12 13:23:23 sorilea kernel: drmn0: info: GRBM_SOFT_RESET=0x00007F6B Dec 12 13:23:23 sorilea kernel: drmn0: info: GRBM_STATUS = 0x00003828 Dec 12 13:23:23 sorilea kernel: drmn0: info: GRBM_STATUS_SE0 = 0x00000007 Dec 12 13:23:23 sorilea kernel: drmn0: info: GRBM_STATUS_SE1 = 0x00000007 Dec 12 13:23:23 sorilea kernel: drmn0: info: SRBM_STATUS = 0x200000C0 Dec 12 13:23:23 sorilea kernel: drmn0: info: R_008674_CP_STALLED_STAT1 = 0x00000000 Dec 12 13:23:23 sorilea kernel: drmn0: info: R_008678_CP_STALLED_STAT2 = 0x00000000 Dec 12 13:23:23 sorilea kernel: drmn0: info: R_00867C_CP_BUSY_STAT = 0x00000000 Dec 12 13:23:23 sorilea kernel: drmn0: info: R_008680_CP_STAT = 0x00000000 Dec 12 13:23:23 sorilea kernel: drmn0: info: GPU reset succeeded, trying to resume Dec 12 13:23:23 sorilea kernel: info: [drm] probing gen 2 caps for device 1002:5a16 = 2/0 Dec 12 13:23:23 sorilea kernel: info: [drm] enabling PCIE gen 2 link speeds, disable w ith radeon.pcie_gen2=0 Dec 12 13:23:23 sorilea kernel: info: [drm] PCIE GART of 512M enabled (table at 0x0000 000000040000). Dec 12 13:23:23 sorilea kernel: drmn0: info: WB enabled Dec 12 13:23:23 sorilea kernel: drmn0: info: fence driver on ring 0 use gpu addr 0x000 0000040000c00 and cpu addr 0x0xfffff8007e940c00 Dec 12 13:23:23 sorilea kernel: drmn0: info: fence driver on ring 3 use gpu addr 0x000 0000040000c0c and cpu addr 0x0xfffff8007e940c0c Dec 12 13:23:23 sorilea kernel: info: [drm] ring test on 0 succeeded in 4 usecs Dec 12 13:23:23 sorilea kernel: info: [drm] ring test on 3 succeeded in 2 usecs Dec 12 13:23:33 sorilea kernel: drmn0: error: GPU lockup CP stall for more than 10000m sec Dec 12 13:23:33 sorilea kernel: drmn0: warning: GPU lockup (waiting for 0x000000000008 7185 last fence id 0x0000000000087177) Dec 12 13:23:33 sorilea kernel: error: [drm:pid939:r600_ib_test] *ERROR* radeon: fence wait failed (-11). Dec 12 13:23:33 sorilea kernel: error: [drm:pid939:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on GFX ring (-11). Dec 12 13:23:33 sorilea kernel: drmn0: error: ib ring test failed (-11). Dec 12 13:23:33 sorilea kernel: drmn0: info: GPU softreset: 0x00000003 Dec 12 13:23:33 sorilea kernel: drmn0: info: GRBM_STATUS = 0xA0003828 Dec 12 13:23:33 sorilea kernel: drmn0: info: GRBM_STATUS_SE0 = 0x00000007 Dec 12 13:23:33 sorilea kernel: drmn0: info: GRBM_STATUS_SE1 = 0x00000007 Dec 12 13:23:33 sorilea kernel: drmn0: info: SRBM_STATUS = 0x200000C0 Dec 12 13:23:33 sorilea kernel: drmn0: info: R_008674_CP_STALLED_STAT1 = 0x00000000 Dec 12 13:23:33 sorilea kernel: drmn0: info: R_008678_CP_STALLED_STAT2 = 0x00004100 Dec 12 13:23:33 sorilea kernel: drmn0: info: R_00867C_CP_BUSY_STAT = 0x00020182 Dec 12 13:23:33 sorilea kernel: drmn0: info: R_008680_CP_STAT = 0x80028243 Dec 12 13:23:33 sorilea kernel: drmn0: info: GRBM_SOFT_RESET=0x00007F6B Dec 12 13:23:33 sorilea kernel: drmn0: info: GRBM_STATUS = 0x00003828 Dec 12 13:23:33 sorilea kernel: drmn0: info: GRBM_STATUS_SE0 = 0x00000007 Dec 12 13:23:33 sorilea kernel: drmn0: info: GRBM_STATUS_SE1 = 0x00000007 Dec 12 13:23:33 sorilea kernel: drmn0: info: SRBM_STATUS = 0x200000C0 Dec 12 13:23:33 sorilea kernel: drmn0: info: R_008674_CP_STALLED_STAT1 = 0x00000000 Dec 12 13:23:33 sorilea kernel: drmn0: info: R_008678_CP_STALLED_STAT2 = 0x00000000 Dec 12 13:23:33 sorilea kernel: drmn0: info: R_00867C_CP_BUSY_STAT = 0x00000000 Dec 12 13:23:33 sorilea kernel: drmn0: info: R_008680_CP_STAT = 0x00000000 Dec 12 13:23:33 sorilea kernel: drmn0: info: GPU reset succeeded, trying to resume Dec 12 13:23:33 sorilea kernel: info: [drm] probing gen 2 caps for device 1002:5a16 = 2/0 Dec 12 13:23:33 sorilea kernel: info: [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 Dec 12 13:23:33 sorilea kernel: info: [drm] PCIE GART of 512M enabled (table at 0x0000000000040000). Dec 12 13:23:33 sorilea kernel: drmn0: info: WB enabled Dec 12 13:23:33 sorilea kernel: drmn0: info: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0x0xfffff8007e940c00 Dec 12 13:23:33 sorilea kernel: drmn0: info: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0x0xfffff8007e940c0c Dec 12 13:23:33 sorilea kernel: info: [drm] ring test on 0 succeeded in 4 usecs Dec 12 13:23:33 sorilea kernel: info: [drm] ring test on 3 succeeded in 2 usecs Dec 12 13:23:33 sorilea kernel: info: [drm] ib test on ring 0 succeeded in 0 usecs Dec 12 13:23:33 sorilea kernel: info: [drm] ib test on ring 3 succeeded in 1 usecs It worked perfectly for 5 hours after this recovery. Thanks all, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `- GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 --3uo+9/B/ebqu+fSQ Content-Type: application/octet-stream Content-Disposition: attachment; filename="Xorg.0.log.old.xz" Content-Transfer-Encoding: base64 /Td6WFoAAATm1rRGAgAhARYAAAB0L+Wj4PcBIXtdAC2IMEZDZYdxGZ3Q7R97rK/hhwP44Yww 1U2aTYg/bTlXRj+VzmJ47H6G5BI3bBFuBnAWqxfjrS3XAdDml0uHt6Q7x5YeJt3MzH7GTqYy lKN4tULXowkp+fuwnVJgaIz8a794I0mqjxti6r+uf/DaL5rqHafgXCn/8R1wm7x+Dwfx56Uw wvgZqab+BqAMIpByplr8DONcAoZnJ6fhf/WcB3P5/yaFBvNE6CtH3Ll2rJz/YoYEpWgvGtz2 rD8Syvw0ZvW+klIeIOnFpB73RboSM8N6syvYTNR/Jdv6bDvICCo1QR1VbL5t9LE7XYvs0GJE CfQCUQ3V4JmVCRaw6ZIgxnmb3XSjGiPdJNI/Zb1LKw1daeHVz63QIOJJZlBt67GRGqDX8a7B B4NXu0aMbWdHf75lEKRz/5dtW0XhM/l2jNE4lrjGPTIl6aSF4dOV7AcxbM9X1avKuo3G5EXT epCZ6znEFF/aBgaCCk2+p1A20/QIbC7vOP8lL/hqqvTiiE78ldl4b4qlABf0cVH4UZZFhxNS O+ZpoUDUbur7DHCLNDyrS/Ma90W3bpiLhPNJFJNDx/iMl0b5uqml6pol1hvPZ904qOJVKwbD zc8nSB0UZR4T1QeMEaLUiTKy1p1QvbIloFZDigHNFIGab/MFdsgqGuaqh5aqXenW9B8AUIZn HkmhKt0SbqHUqKJlZcmzi+5h2URtpXvXVA9I8bGKFD8IADR8/UYbpUEEcGRSESoWqcEAnwEi LSdqza0ZMkYDjUtyw/25ZwMU56t7s8LBbB5iLhqjHTRr7wA5PbZYI+wSbF/iMrGYRtzBz/RW +/1yZfjrjTj7de0CqWMjpmApqZBJg4hVxwErSOyhiJM5K5gX1qg4stTUc1LB/vD88hFvxSTB xozakgjrIdUVJYZ7s7SeSfEDjAzzsOwHKiOtdQ4Zc3tf8E0xoGGjWHwf4dBvCQkpHb+3wpHq 0yw+UY0h/maffw+iIsk5qUw0DQ5EgNboqbRRfd0DvZSBanOu//5OighpptcLP11oqeON4g7X TCSWRXOlm/px7j5PAjwjglD86GMYu0eVZaCzhexWK8iAGf3ebYOPPiGkolRaqiG7OjXor2w6 y1QEs9gbRd7odfEIMoz1c6vGJ+fojSgq/W7/nJkpjY8PrIKc5gyZrLAOkE3fqq1zOJpQ4gbh YkmGpgA/dNYRObDIS7x29whMyaGINtVEgM9DkNpPVSJMAl1ou9iaoZ0XH6A58JmUycXdDn18 Eyyq8aOcsdw22giam1c4O/UgyhUUW+LpODXER4eSVjYV7DACzKwT98o7LyP5M03JhhqOT03+ AXmQJ01ykMQT4ZRLi7v0SGX/PqxscwEejL/3mIgiRdGGMddxenzk16r/m7v85M0D4xwovCl8 dMZI4qS/qEiwQ42F5Wv0SJ2hV9yZZWGXl3+OxNdxw+j6ykUDGLmkJZRc6uie6n/nouTWb1q+ 0gF8oWDUNgXGfUk+/nmk1lkmn3nFgBsd0vU/vrRrU4nnlyNUsCCRtw962Y2t6qg2jRS1ZYqn DMce/lF3jrOUpddHRJek8tOPW9vJRyG+GVzyx+kTktTNK3tU1wTPEYhV9uXLcyv7nL4aMvE+ Xvtpy3T8gZohvSGGGhLS9VJv6bCr0NlGm/XtZeAh32Xxn9D2mcpguJbdCHgzfmPfQQQPs8Cx PQMzkc7sauvDpP2mrRdZ8V3PpgjmRF6cD30hNF6dOrqmjHQn+mfS6cpPhJOnwvUodi/liz2e pWhOmDiz1XZALX1lJ7CCVZnbmneTL65zqEEaQ8PoYyd4pCNk1Cr11BNy3XGFTRuGnIqytcu9 bDTYgTmDXoAlxN2r49Vz3OXnNpbqZf3TD2rhIgiyvy3qNl2cCphazeGb1yhvtAVsoy2TTS6e Ndj6WU4YoxlUOdghcBfyt+xMeRNKAcIDw0wI06aqk3lP5fq/2sls2crTp6eOhkdnicNl+lir 6dYLYf2wpvRBy+faDNb+wHYzNpwD6UAHf/m0BPLuNUpz5WkmkEDGjuDyvT972FaAR9FM9Uy1 3tTZygO8FZZSXBRpVQU0gUvxrFcUGzOlXu2lcEi1bZ37Io0fDuLORSFOFdSb4M76OxVLzzZ6 dEHOQrzp47BpZPmgGq2Gd7ImsklotiXYEG8/qNdHO8FGDlNQXEDknz7+IvfFxndc7cs701Af wwY9kQjOOP8jr8WRvQKayyJAVgh1g5Mit8f/oblMXvTxmyGbVI6fI0LMc3TIxUpiNJVxlZmd hhZLVvQ2fqOBV4xv2MBaYOLdykDzABEfKy0lnj84+sqo+Y2ccgQxmF/3MSyrXfrk/x9KihDC 5tGhg39jqIR1TZfEOnZtbToKV2wT/lFKNiA7MaOoCfBGUmmMt9MymvCcqALalAxko235wbj4 07o4sMA8rjfRigCitCyjiFi575LfI/HBFuwx5mLtU11JBwFSEptmC+rfUylKPel6ztC70n4c Miz4vug/L7n57QbP3xDJqzX/HhTJ1ZXsKKDVQ8PW45TtEOvEABlIUPVhbKx3bAavBNcaV8Lm 91++PmifLilTUbO9oq2nLEHYEPuH4X27xqfwDyJ10CItoPdHXsb3arOP/p4wZgDGLx01y12K U9a9O6z7fxRWKxJiE7ih6OfQjq0hwY0/DFaS8x6MUsBzAUIinVI+72isnwvIgnFiVfLeew+v RPwNAcbQ6EV7ZeyegnE+gUd1fCSyKq8GqsK24w5QurYg8Gvfy7zsaTooPeSuRoNJXkXw/HVn 4GTd6AXqx8GC6wXPnAgrk/djjk3XmvWVM211ZjUrMRmjcMUj+vjg5d789b/7c2Q7c5y51XJi CWs7OmQd/JOYP000Lg8ICLyehmVY4mLeMlnufhYZiDJvbq5CvJVXv9ubUneaQTgTpEJlIBe1 tl8DcNqJHDOlP52H/u29geaWrXjlnakpuacrt+A/X7taAeDHon6QD3flnt6HOxkOiZeQqJHe Vx+73nZRDuEAQE3pX2/3NcJfPKqBoJMnbf5QiZaDKAWMKK6sStlMLdOkZ1BakuC0R6F4CIdy j5MF+6/cGji0mfKhgDlatpMPjETJNCiEs+tf9SRIsJKvTQw+3tsPgXjibL2Q0I1o3gSE/NTL uMeaG4k/W3HlNMM7YKXoZq0m97oESktRtLZguB6FB4v0ORJ3wBlsISQD0z6bVZmHzIZE33Fr FFEyp5G4z1TzUzsd1oQDlNDrxdnDpQWbUeqtHFlzZzHuEPQqWvfL+SnZSnQ4pnTkBkFIlrtu v3laQKJS6FH6+Lu4ZvFiFuai+YZGJX08EFruuwR1ImqWnuitbsYWLJu2nCNfuta4DEF1mw+W 224vbUuMYNR04YG/NInNgQwIK0B/5ZSw4y65WsPGMicpyiLln0vbJR/GnM0AqlVHGgT2w250 pe57iOrtYSfg5se0t0K/GTyOBvXixteZ9Z/DizVwWldNEXAlHVpjY48B2If2isMM+WXiEP2O 8EI4u61lw5Cc/X/8Y4YxQepGWKScV8WN2Pk7rm6/B4ukBwpa2o2krUnOQgVEI1YJnQCZgBB1 wKc8afg1zBYHuBwpW8xVONabo9PSzFU+dNia2ButKrTru7Wib0nsbYbrmkOWe9I3f4GZktxK 0eVIwT1bKaTJu9pIXIcigiQD+bSNH3uhZg1QHvJw4gBrBzl8fKx3GwkT3XpUiXwem9woQkXa L1XAytsL4dAuCsvhBcZb0LiZoa3jRB/u3drbekXBwFKIlGZsHOdGqU5LeicH3ilSUZrZ/3T4 TjA/YG4ThQjIKhaiU3Sdw1mcI5HB+vmO6I8/lreIfrgpEt00x7w15BZDyNcB2xzUqEZhEOmk aYQ0/9AtozVhdjlCB5QH0mJki81s5ZHHltgLIgG9dUTY/tetzoz4Y9vCOx3aDeqtH5MkTpjr LEXQS/uxKDmNkBJr8rg9gt8HZ+Y2ApEPAg6OpeI0az1enEhhts2gcRirGeBEuPO5LgQmmlgd y+C9qlOQLBtP9If14OkPRZAK8UHvXkBJfl+U6qK0wuVrmIwie2YwG4KURyF8KFEqj0XtTHzA 9Yx0DB8c4MhJMeuNi7eYP/ADaBetrO5zu/VagLPLa4xDZcyHh+zB77YeXU3U/1juakiRERsF 3i3LF1/oc1WmE/2POqNXB31Psb1reQxLBvJuRnyB2G4IMFRLh2UKcofCAq1dKETTcZP7emjJ 7NkZavg0DavueiHZVvimlH1h3IgWFBp+CG8g1uQpx6qW75ih5SqrXdD5UqQRBAVmdie8IVJv rsUiK9pWNLjleDUjsckuu7YIvDS+CLnlr/IYS0K3oczvZPp552/oJaY4nrxbTafg1/25PzPY 7CC/jqvT5bVVZgKo4Tpo+dgYz4aQWM+kn2qewUgruDTMeJebQLIFLUB6mZU2qundqE0GXg+j m9s08rIIYsMFSeLFjEboAYBXs5Akqs9xUzR+fX/kmXpnwRvd4vxOC0xuzzcdgid65ncqwngu nn3444CTfS7qLhS7si4oGvJ6iHapYuq94B5G+yES52Jd8lOFmk/KVPSB1lWFtRvs2ryUe2bc w/AY+JKCr9QUwqEZIxzXLwKGrLEqjzVDrRQQatIYaZuydxJuk4ogIwnnttVD5qOr7cx8GscO cUq/dxcbSaDmuaknW79jxC/kKOUH+ZfZaWAbpfj1fIAgu8Sn7yWYGoFH9Jh9oLqQ/bkuqYyM TpNWuh+qEG2664YmQOpCC+mMeieooGZmcfLWhTzEM8jokK7asvzKOu6nibIWMPeyOAzl+o54 Nd5tv8cx7DiKluFLviG9P0nG6WtaIdn5lwrbFb/uEoRLQciZ69/AFGo+Da1+mBMut8oerUaD rBIOoi66A919NRWw+zkA4AwGbYfkKk61tyN4EsPDGjEH6AwyQBJeFUWKRDwg3gazLnbtJiDF +5ZSDW2EnM5YL+T3eCJBevbQ1nBu9vbjWTsYNW45hRZ4ym1ZqX1RLsUC9sFb9DkpamYue1DP UaJcXcxMbZwDRofyh8eY8QL11GiyOzaVoDbET2yKdOrSqNGsb0FtgL3/JiO8yNYOYJ33qr8J N5jkSVt6J7oOtm4fwK0VcCVq1sf89TsCfCszI4DGo5dy1gaiWPZ4GbMBY4oqSgbVMjUJxE4/ taIyqGQJEYRPqz9gSYyH59aW57+cnCwrXA6aUrR4ccm/DqD1ybT8uxDdif4GfQrZSfEb3Pry 8KSXEJQCBOalc2sl8i/T02YUo1xBxMJiW948mQ/ESNquLKy79VjpzC3Vi1hYeFxQ547P/UPg VhlOmbt3epPAE+BALZdRxA6ylfxFZEvkW4V/48ZVufUIG47N9a91ULYEKhOPK/GBq19hTFSr HU6sUifn9nUTsY2LAh6glFNaXwP59C7YvX3lU8pXtQDeI0sGSOMVfFcnPU1Q8ESWNHb/3WEJ Ydx7SwmzGwKLp0QEbnaqqk0B/d08YQ8fSUrjt85EYGVpEk0oBlSW08kXPlpcoHfGMmC6KGIa xrrKOmqOTge5v+E9hVh1tWKxlRhHdWPISW67MXhWAxTEvcoLZVHmKTG2z9SjCP/ZIwSpDjll iCz9ha1Yt8L7cTJ2FyzlIYBnwolG3s979e0BYsXWCCeU5XGLslYXyd7i1vd3+2C36EUAmYqc MSlBatu20CRyCeQhBUAG183nD5sHba1g/NDv+SsW4a6SI39M0lAExbsCBPuNClO5XeNnQXrU 2sjX2qvOyKWfMc9Jm0pn1RUv9x1UGjp+6lR+mg4Bz0OUufaAShrs8t3cM9jUuk237VlCMz81 8I+mV2uosHrybjfP+Nr9lp/zbr75RCSffKqeOIY0ihiIdL4+30dkxYRzeUuV8fi7NelggHT2 BtepCyq87ZnVMHqRHJF/oPD5WL1yqWgkQWWKdiQHGEnizWd8DTeBqQQgVPi7ekkgS14nSx5/ nN+we8sRuB4+YV3uodnXX/ViS+09hsWZsffiDaBupC0hzsqfUh3bVrO2gl5eBoJRsfW8qqwX tQr0z2aX/DlP4rMwNMVAsiuwz2farUHlTZfSV6mY2oH9BTMw4mDurlThL5WObv1zQvuTXJzR mPp5qF5wQ78sQntfrPmxdeL9aXpVuDXhg3y9xop1yg6fWmsquMgJSu3ZHAimN3k2uqPuA9dW 77NyaQ/OvO81M4RWkNAQUU1p8KaCVDCBJ0YzdFJodwFl1x3heE5a3iisq1MaxZ+nX+pibxqW ScTeI+Hm5GFl/ETPLNZI5nrv1OsJAJdSn6OpWxz8k6TFNuFfcks2+6bTdxK95rYXLU3+efYb QMhJ+rkEtkIb2ZjOWxh37VOgGMTXHCAndeK3tv1Shkt4hpc09bgRD0BwEZa2rxDE0AP804so QDZEr1dPOeE8Oz7LU4X0cOFkA5UA5zhLVpA1DmXCkzgHFjgqcBIRlEYWB8q2Prp1KOYzBWjn LSO55OQVGcArT9znKn5yeSF+9Y9Cu5d3EDX5AjR6kxm1zoEheAPV9V/8AMKvG4M1rUl8/XOR bzK/VYeSERJ2k+tch1Dx/D5mRmctdnz1/ahF3GdF6C6bo6dGlAtZC40JlDlrp8FKITJvFUHK C9TS7V8m8JA+GVr+hfovfdb2Hq4qJWsmAgFjJ7Z30ObMe2coGooL8ttLO8jHf9SQTqj6h5It dxCPt3rWTOKUup3nc2Xgx5EhsQ4g6d0DrXvZGOaqq0mCwcf2HvqnhOxIiAQiKUIvs1g019ve eGyWaBZp7/odZOEidDf3t+/JGHB7AX/yM6An3ga05O5FuZXx/KKsssX7w5BDKI07yUkjfctL xIWE0mtmPaxOnoZp8xtIcdlfQHtnjjyRv6B+7p7PP2b5YOfHUNmkUE3yzLry3eT8tymNl+eq QVq5XiN+WLo0/9pRt3FgWoknS5qzMaynBQO6eqM7YSp29tKadQdKKJ4Apz4Rv1uov2Re0+lN XxkwlSRxIum1f6Lg+j49oGfn3gu1dIieksH7vh1BUh4aBkSF925g0AQ8hJRWZ4cbbPvRzNW4 q+UlrKV062ijzwEMq8EKnWAu8rYjeHlmZFTADgT5li9L2qKt2RznNWOZFrRER8zHfNqQHSSp yLzGeotU6/Psl49YbYfK3aDOv6j/jxOgU3NQ5uUbG1EGxPRcN2fg535V9AwDxqyDCtKFI+Yy ZFaxTzbzlk+YYBjQ4n0Dz9c932GOdwBXlsaE7WvsmP3jJSKEutlD3vqDVZKCwVroFA0FKNT5 2c7DgBDhb59ySY0yHjRlGAhdqjk9+hJl7GO9vqqeji/+RD11DaS1Mf0AFAf3zmmx6wLPc5xA QCARcwpgKS44KWtSCeNvhrcTyUFarf/2Nh2dTYH16WIUxvDy2rip1YKLH//cv5ygiiL7vPTg KAl2vXf+BHbXeNDvQlKwZWekgEBgKJY94IMlkdcfL/jaiReh3psUjPxO6JA/oR3+bL08OX54 5v4Luzq7qnJ3F4H8J024KCyaKXWajxKVE1DIJiQ/B2W1RdrFoS4i5PJ1tIslJstW5b6BBMBF IiA0W/pCuYhPcdy6RV0iJ1grHSvXavKviHhEiMMC4/ZYna9kyhhjpRW0ecT44aWa+erO7XtM NdkNWiW9l13ADQVhh/TXfHbkG7iWG0Z4LvBjEXRU92ehSAY0+kmoZdhsGub8H6DBiHnowTsI MAYYAkefzWdTNnXPvsW/9/9TsdoNUlAvcMKZ0blcHDZzgWBWKQe5iMP+oRUIq3BGbEg385EE bD+aV0txBGM8+z785Akec1qu5sV/m5qZ55fCHzs6xpOZnsyIFElLD78M9RqL3CebA/er0fkk 6G5IMix5gZEt/Nlmy1fgnst9Kg6DkcGManpB6qTBT64mue/hoBcqFsIGuqjgTgi+gmBVZOO7 fZTASzPtFiA8tpafiSIBovfN9WeXN98mkatxCDJWUDi9VTxpHRbrUBRfAJmgWIu8TuIt+0EV vr3pE3k2PmGy/rKdUyK4yoYASCWVZ35I+xreKAiPtnfIV2QMJ5Sea2RzzKeXJVMzL/6DeNAj c9J34pdwxvrkY7zyWLeqBS2m2juU/IKNkwY2tGlDIKZ0kl/ZVECG9Yc8ggL12hZq8W1836xg K3mSx3+RigF41OC9hbpPFii05Qttoo/oHAcdjNeqmEu6gxzlgDs9shu/4DLiqjyloRAvqDPd 3+x0fsOZGhYnmsDHXJi4fIjr7YbgGh+oeKA9ForrlOHSWJYWECgtEi1nHKCWB+T5HBVfJ5LJ hoFKHOQYL7zoJmRNCPn1RRcNTYY/ThLEIJeOveiDlizZfS+iRXdpLASyi2irNXzslmkP8AAI VUgib5TQenwMXB3lPti3jERuXjtLrxa3UV/xhAIRyz1FW6rjeJVTeoYGxKn3vibDAqrV+HSG SeaFUcqvuNv94U2YoBnH2YXHOrKFma6dqBlABPIo+Bpl9dLXloBWx5Mq76iwuN3WBvvpy1pZ XiajMuhmUXSwKFrMBJ/Wzhm5EhXKqD2iTb9KgJm92PV14RQ+o9sq5QMpBHBwo6ok3gymU0wo GfnJKXF8cfwgQGyDNTPzNYF4cG8UZmNsKftqS2HwCtKMgKuAgKyXJdaGDocN6CmXMrewl98l cm+F+P7oIHB3Td5CI6cc+F+RHaQWCY8Ei8ZYUjiGD4IRHk5g4slqXKhFh+p58LG3nKlBtDSM OhCWk0jR4QOCYb6Cx08ZILiOYYu3eWlNCW8etM+ROxt4vRo4+Hm1FParfWpi+szYJaPj28ok pnzSEhs/XlHpwNobHwsH2WvQnRP0oPYuq9FwTAF7mRrHo9//RPT0mTjgQR0drS/PmAYJQA1R 5tfEmqCrfNeGyYQbjLrXJWilFu2Knoo8WPGWTuQQ6PpGjEy4btuxGKqEap9rt+0indnR4Qri S2zRiUqpEwyskYFl4soBuCvQf0w9hUdjCxP8xS6dQNFCMRFSgXrGuFUgMtckE/5BKBbZU+ma XpqW4ug/izrhEgiuJ3X0R2LBXt8FtyZKL5zuXHdvgHhP584YDN8ftDXedfRd10d06wAbq9hc Hm7nr1IPH3jxWhXIfSThqnbX7h/nulb4qkElb6eGYk6Z2ydxKsqWkvXyCU8Iw6he3FdBuHSV CSIefqwwvn8HhgjrnZEKsfBr2aEG1cHHQ+nowubG1AFMmNrxNL1eFXMvPFt+BqCgLXzOsXWf 6mPzGqaufK4oEtg+sfX/EqfqJqrBBGNi5r6Om9oOxgZ82r6SmCB45HVyL8tXm7mrOa7K8Y3r MFeV8fub/gtMEkQeqJdu4/vtgUv5m01ZY2cn3g6WSBTem7gDHp5ysWYqMltKeN5092t7M1bX QrWv1tjJijvZR11OQee5I8ZH9MSX1URfdcCEGJe30W92j5jBouWJxviDG0pF5IFaC2E3hen9 8S8zJ4b96jbkCzBV4A6vYQYUQBdDYx908ohwygH4PabmEhhm7lbjLwlhWideZFxcnG6MGLQv 8DYlWvdhN40OWiK3DnPuMyWDKwXRh4GkJpPdRlPo5TZj5h3OGBQ/5oTCeH/8c3oCORdYdWfC Op63gjxBUQ6StWMewbre5fttLD+VvV4pGsV7lDqIm/3fQimhW/loGvQsYRxeRanB8mvZbrrn qZ1NQveV/q44RtOx+WdIoJIhtqTdinr9o9tBtQnykKgT+0XmFXfHLdKOYvbzS8hZI7DjFdn2 meSTWMfW8u4mlg5J8xLAOim53t9ShHCP5SkcjjCIoBFJYApvjQDXSIERK0prGSBySm+TKbwl DFdLopodsSj9O8DOWlogn9eymnBdS9oyE6vjuAnNKVwqbxrqsRJpUwwCNDcDeA4fUK/48J4/ rLw6KvkLmccsotJzSmye3X2D1ocDgan/PnpKpu4bKzFXFiHjxA7pCLbRastvzuKsL8dfd4Wu l+8FXPSmS5TNYOqXVZP2tqmyUmfytObA37raggbmofXSYx9aZERAX42ebCG8Z2JZNEXTHdw4 x9M2DnqLlX2D+0zeSjJTY0PXgaKLuD5tTuz3V1IDIPb0i5b/ZCy1qMqaf9tI/spkZQsk1eOi wxT3RnFhdr+qE1YyZQdLXnR9irna6y2a5aDYypdwGRwIM+DiVLXwjGf9S/0lcT3roSjfEqpz o18YNV42pnCwGGBsp/vlJx4HICqjIh45aMTT4q7Uf3W2jHipPkXHsr4L/AA8EZrxzXYAjwls YA4S+UPeiAeYor4R0zD3bXIfgzdmRYTSqF7MmUMjIflx3ssnxSC5mkEY1SvnoMa4gaEERfNO khzdQQBf3mhK8+CM/Q1oJINOApw++IpGYIjuHe/i6Dgylp3WnV5cs1gnH8rrITLqFVXYdIlp 5UYwb0oT6OG1awDCDKS5oWupFefO3Q43I4ZTLKfNV7MgTDJCkmzIvrcojJlhuvGnzX5wFIAC EACOBOStVVMavxNSZaSxitg/xUkyZiIvlo8XOWQvnljLB/gruZi0LZ3SlH0jma4EW/4uC6kq vHkc7xFJpdMHkXBEEpXazagngIJ2UuJUPqRfRE1VD7aHQ/56A1FPM2W/snkD8JQ7QdJ6zQ0M hnQw23V8FZn6CtWluwHWfWJ8/oIQnAR2fSQ0RZH5zQRKBH/hOUvAcNjYz9MuNMU4jcycwYVs 3n2R7AF62u4YeuKIYbe1cjJC4uxG1dGn8dZL5cdYJibgdI+jKTxOj2vkTIZTax5LVpd/Wg9U Uy5hisFd6oBpGCP56IO7OMkct/n64Evlmian7EPV3p5kZMhUckousOCF4Rg6+6QjmZ3NTWon YeCgLzKZ66fbuou27BKTaJIlzkHZFv9kEZOahFEWcHkz/GkG3UvrY8d/y6p9GHfEV9KXp8MP 4B6/a3ZROILM77P3Z4Xe8KSQCDqTxnbsFnuQHqTIaX6mYvaeBEHA+9Sg3D6uSvQKnlV/vqSM Cb36F9uFawf2PRfKv6GKtFrAebysY+ga8l29yFdQPQlzMW/lFeiQ5UcGGKe1WAKCq9BqALkB t768wEMHIPpdYUXijBPEgJPmvgyGNIrBHOhRcIxZGaCuzrwLSD5GbnaYhOALmetWx/DTU9tW VRJWdPl8+Aej1NR6r6WSgXhxEuV/W7Vep6mK+oAA4GR1TzBi8tUUPSyqeZZVJr6VPsrMrPaQ jihlUtIAfOnLMFke1lU5QhomK4JQlz8aVhykbe1oGnTe8OZFuAYw0ldZPTkA8GPkWfvpvcWr yP7Mze2VnX4QzmnVHK/jcpL/rWLcAM2xZzY3seRxvjybsOsTL6Dkcf/Vi5oP5rH5sEXU1GzP ZesGFhrQcXJQhj33nI9aSE/hqqbe/YJfe76XuA2RWZXkHXtEZfvQN3SnCeOHZUAKnBNuLoeR w4MLC0FbaF1gpiustdU6WXC5SCykzSU8K4Sk7v1mp0FQA/9Tox/HTAuwJJnGAavcBRKuRTpC MqV9BORvHH/WYhi3bcvpAAAAd7UOZghsgm8AAZdDgu4DAGYAZBOxxGf7AgAAAAAEWVo= --3uo+9/B/ebqu+fSQ-- From owner-freebsd-stable@FreeBSD.ORG Fri Dec 12 19:49:24 2014 Return-Path: Delivered-To: stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3E2667AB for ; Fri, 12 Dec 2014 19:49:24 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2668F985 for ; Fri, 12 Dec 2014 19:49:24 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sBCJnOjv059749 for ; Fri, 12 Dec 2014 19:49:24 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: stable@FreeBSD.org Subject: [Bug 193389] [panic] ufs_dirbad: /: bad dir Date: Fri, 12 Dec 2014 19:49:23 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: mckusick@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2014 19:49:24 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193389 Kirk McKusick changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mckusick@FreeBSD.org --- Comment #4 from Kirk McKusick --- It appears that the offending directory has moved since your first run. Could you please run the following commands to find the offending directory: find / -xdev -inum 8668611 -print ls -ld find / -xdev -inum 1777399 -print ls -ld Also, as noted by Adrian Chadd in comment #1 include the output of a full fsck of the filesystem would be useful (after you have run the above commands). -- You are receiving this mail because: You are on the CC list for the bug. From owner-freebsd-stable@FreeBSD.ORG Fri Dec 12 19:59:53 2014 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 619FCB3E for ; Fri, 12 Dec 2014 19:59:53 +0000 (UTC) Received: from drone102.ral.icpbounce.com (drone102.ral.icpbounce.com [216.27.86.159]) by mx1.freebsd.org (Postfix) with ESMTP id 03A14A8A for ; Fri, 12 Dec 2014 19:59:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; s=default; d=icontactmail4.com; h=Mime-Version:From:To:Date:Reply-To:Subject:List-Unsubscribe:Feedback-ID:Content-Type:Message-ID; bh=T7p907GpO1tcUtECoJVWK3S8xj6QB5hZCcDVKV/YS/Y=; b=MjTCylF5sMtqb1up1zU86rdIdGHvnwPOVp5K1YAKIbsAhgGeeEfDUyXMDjN0D9E9j3RJySD4pUdl nZLr4xKN1fUKSH9//7SAUF9Pr7/ZIjeeHZbnKOjDA+VUkQQZPahTIIU09viHJLm/WH1NWBWihZVf sobPx6WocLKditGEJpI= Mime-Version: 1.0 From: "Dr. Christopher Perrin" To: Date: Fri, 12 Dec 2014 14:59:51 -0500 Reply-To: rjames@ClassicalSubjects.com Subject: Classical Academic Press Insights - December 2014 Errors-To: bounces+1283964.24412559.165982@icpbounce.com X-List-Unsubscribe: X-Unsubscribe-Web: Feedback-ID: 1283964_4541_165982:1283964_4541:1283964:icontact X-ICPINFO: X-Return-Path-Hint: bounces+1283964.24412559.165982@icpbounce.com Message-ID: <0.0.C2.1DB.1D0164630D61EC0.0@drone102.ral.icpbounce.com> Content-Type: text/plain; charset = "utf-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2014 19:59:53 -0000 A Word from Christopher: Felix Dies Nativitatis! Here is a small Christmas etymological study for the many language lovers in our CAP customer family: As you know (or might guess), Felix Dies Nativitatis is the rough equivalent of our "Merry Christmas," but even closer to the British "Happy Christmas." Let's take a closer look: Felix: This word is related to the Latin word felicitas which means "fertility, happiness, felicity" and "good fortune." Felix can mean "fruitful, fertile," but also "fortunate, favorable, lucky," and even "rich, successful" and "blessed with healing power." Dies: This is Latin word for "day." We get the word "diurnal, diary" and "journal" from dies. Nativitatis: This is the genitive of nativitas, the Latin word for "birth" and in particular the birth of Christ=E2=80=94also known as the nativity. N= ativitas is related to natus (born) and the English words "native, nation" and "national." So when we say Felix Dies Nativitatis we are saying something like "Happy (fruitful, favorable) Day of (Christ's) Nativity!" Perhaps this is a nerdy way to greet you this Christmas, but I trust that many of you cannot help but be cheered by a word study of this favorite holiday! Pax, Christopher [1] Do you want to receive the 2015/16 Classical Academic Press Catalog? [2] Live-Online Spring 2015 Classes Grades 7-12 [3] The Art of Argument: An Introduction to the Informal Fallacies [4] The Discovery of Deduction: Formal Logic I [5] Intro to Rhetoric=E2=80=94The Argument Builder: Constructing an Argumen= t Piece by Piece [6] Personal Writing Tutor Released! [7]The Man Born to Be King Literature Guide 20% Off [8]ALL Walking to Wisdom Literature Guides (including discounted bundles!)=E2=80=94use code MBTBK20LIT Insightful Links for schools & home schools: [9] 50 Great Teachers: Socrates, The Ancient World's Teaching Superstar -ar= ticle [10] Major study of teenage sleep patterns aims to assess impact on learnin= g -article [11]Many technologies have promised to revolutionize education, but so far = none has. -Veritasium YouTube video [12] To Teach Facts, Start With Feelings -article [13] The Liberal Arts and the Fate of American Democracy -article [14] Best Children's Books of 2014 -Kirkus Reviews [15] The Latin Vote=E2=80=94Why everyone should learn the ancient languages= -blog post [16] Three Little Pigs, Forgotten Fairy Tales=E2=80=94Latin Vocabulary Prac= tice -YouTube video [17] 50 Reasons Homeschooled Kids Love Being Homeschooled -blog post [18] The Liberal Arts Tradition: A Philosophy of Christian Classical Educat= ion -book review [19] Two pages of Classical Academic Press Christmas specials here! *The links posted are not necessarily the opinions expressed by Dr. Christopher Perrin or Classical Academic Press and are used for knowledge and research. Have a conversation with us! [22] Facebook [23] Twitter [24] Pinterest [25] Inside Classica= l Ed [26]www.ClassicalAcademicPress.com [27]www.Headventureland.com We would love to hear from you! Email: info@ClassicalSubjects.com Toll Free (866) 730-0711 2151 Market St., Camp Hill, PA 17011 References: 1. http://classicalacademicpress.com/catalog-request/ 2. http://classicalacademicpress.com/live-teacher-led-online-courses/ 3. http://classicalacademicpress.com/the-art-of-argument-an-introduction-to= -the-informal-fallacies-spring-2015-course/#.VItG4Et5ZRE 5. http://classicalacademicpress.com/the-argument-builder-constructing-an-a= rgument-piece-by-piece-spring-2015-course/#.VFjlphZ5ZRE 6. http://classicalacademicpress.com/personal-writing-tutor-spring-2015/#.V= FjmIhZ5ZRE 7. http://classicalacademicpress.com/the-man-born-to-be-king-walking-to-wis= dom-full-program/#.VIsLuEt5ZRE 8. http://classicalacademicpress.com/brands/Walking-to-Wisdom-Literature-Gu= ides.html?sort=3Dpricedesc 9. http://www.npr.org/blogs/ed/2014/10/29/359325963/50-great-teachers-socra= tes-the-ancient-worlds-teaching-superstar 10. http://www.theguardian.com/lifeandstyle/2014/oct/09/study-teenage-sleep= -patterns-assess-impact-learning 11. https://www.youtube.com/watch?v=3DGEmuEWjHr5c 12. http://www.edutopia.org/blog/teach-facts-start-with-feelings-hunter-maa= ts-katie-obrien?utm_source=3Dfacebook&utm_medium=3Dpost&utm_campaign=3Dblog= -teach-facts-start-with-feelings-link 13. http://www.rhodes.edu/magazine/28562.asp 14. https://www.kirkusreviews.com/issue/best-of-2014/section/children/ 15. http://www.newcriterion.com/articles.cfm/The-Latin-vote-7987 16. https://www.youtube.com/watch?v=3DZrX5k7I3gAA#t=3D256 17. http://www.weirdunsocializedhomeschoolers.com/why-homeschooled-kids-lik= e-being-homeschooled/ 18. http://classicalsubjects.com/resources/2014-Fall-SCL-Journal-Book-Revie= w-Clark-Jain.pdf 19. http://classicalacademicpress.com/christmas-specials/?sort=3Dpricedesc 20. https://www.facebook.com/classicalacademicpress 21. https://twitter.com/ClassicalAcadPr 22. http://pinterest.com/classicalpress/ 23. http://insideclassicaled.com/ 24. http://classicalacademicpress.com/ 25. http://www.headventureland.com/=0A=0AThis message was sent to stable@freebsd.org from: Dr. Christopher Perrin | rjames@ClassicalSubjects.com | Classical Academic Press | 2151 Market St | Camp Hill, PA 17011=0A=0AUnsubscribe:=0Ahttp://app.icontact.com/icp/mmail-mprofile.pl?r=3D24412559&l=3D4541&s=3DY66G&m=3D165982&c=3D1283964=0A=0A=0A From owner-freebsd-stable@FreeBSD.ORG Sat Dec 13 00:39:58 2014 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 098BF232; Sat, 13 Dec 2014 00:39:58 +0000 (UTC) Received: from smtp.digiware.nl (unknown [IPv6:2001:4cb8:90:ffff::3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A8331A6B; Sat, 13 Dec 2014 00:39:57 +0000 (UTC) Received: from rack1.digiware.nl (unknown [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id 734F216A406; Sat, 13 Dec 2014 01:39:53 +0100 (CET) X-Virus-Scanned: amavisd-new at digiware.nl Received: from smtp.digiware.nl ([127.0.0.1]) by rack1.digiware.nl (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d9RRG8-6BUP7; Sat, 13 Dec 2014 01:34:52 +0100 (CET) Received: from [IPv6:2001:4cb8:3:1:7c0e:cd5d:381f:40b2] (unknown [IPv6:2001:4cb8:3:1:7c0e:cd5d:381f:40b2]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id 56C1D16A402; Sat, 13 Dec 2014 00:24:50 +0100 (CET) Message-ID: <548B7941.4080303@digiware.nl> Date: Sat, 13 Dec 2014 00:24:49 +0100 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Dimitry Andric Subject: Re: missing /usr/lib/libc_nonshared.a References: <54837FAC.801@digiware.nl> <548AAC45.8080800@digiware.nl> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "stable@freebsd.org" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Dec 2014 00:39:58 -0000 On 12-12-2014 16:12, Dimitry Andric wrote: > On 12 Dec 2014, at 09:50, Willem Jan Withagen wrote: >> >> On 2014-12-06 23:14, Willem Jan Withagen wrote: >>> Still trying to upgrade from 9.3 to 10.1, which seemed to get going. >>> Completely started over again with cleaned out /etc/{make.src}.conf. >>> Then build/installed 9.3 again which also included clang this time. >>> >>> but building the toolchain generates: >>> -------------------------------------------------------------- >>>>>> stage 2.3: build tools >>> -------------------------------------------------------------- > ... >>> cc -o gethost -L/usr/obj/usr/src10/tmp/legacy/usr/lib -O2 -pipe -I. >>> -I/usr/src10/bin/csh -I/usr/src10/bin/csh/../../contrib/tcsh >>> -D_PATH_TCSHELL='"/bin/csh"' -std=gnu99 >>> -I/usr/obj/usr/src10/tmp/legacy/usr/include >>> /usr/src10/bin/csh/../../contrib/tcsh/gethost.c >>> /usr/bin/ld: cannot find /usr/lib/libc_nonshared.a >>> *** Error code 1 >>> ----------------- >>> >>> Now I can fudge around this, by getting this lib from another 10.x >>> system, but changes are that things are nog 100% compatible. >>> >>> So how do I get this lib first, before starting to build bin/csh. > > This part of buildworld uses the compiler, include files, linker and > libraries from your existing system. E.g. it is normal for this part to > use /usr/bin/ld, /usr/lib, and so on. > > On a 9.3 system, I would not expect ld to search for libc_nonshared.a, > since that is a feature introduced in 10.0, where /usr/lib/libc.so was > changed from a symlink to a linker script. > > Can you please check on your system, what /usr/lib/libc.so is? Is it a > symlink or a plain text file? If it is the latter, your system is most > likely polluted with 10.x installation left-overs. Right, then this is a consequence of something I'm trying to repair.... I thought I build world+kernel. So I installed kernel and rebooted, Only to find out that instalworld did not make it very far. After that I started fidgeting, hoping to somehow get to 10.1. So my guess is that things get very upset if one is building on a system with a 10.1 kernel, and a 9.3 world. >>> The other question is: >>> why am I still using gcc for the toolchain even since I now have >>> clang onboard? > > For the early stages of buildworld, e.g. bootstrap-tools, build-tools > and cross-tools, it is normal that the system compiler is used, e.g. > just /usr/bin/cc. > > On a 9.x system, that is usually gcc, but this does not say anything > about the later stages of buildworld, which will be built with the > toolchain produced in the cross-tools stage. For 10.x, that is usually > clang. > > >> Turn out that the only way I could cheat make in to going anywhere was to: >> cd /usr/src/lib/libc_nonshared >> make >> make install >> >> And only then the build seems to progress. > > I think it is better to inspect your /usr/lib/libc.so, and find out if > it is accidentally replaced by a linker script. /* $FreeBSD: stable/10/lib/libc/libc.ldscript 258398 2013-11-20 20:24:59Z peter $ */ GROUP ( /lib/libc.so.7 /usr/lib/libc_nonshared.a /usr/lib/libssp_nonshared.a ) So that seem to be the case >> This all even though the /usr/obj tree holds: >> [~] wjw > locate libc_non >> /usr/objs/amd64/usr/src10/lib/libc_nonshared >> /usr/objs/amd64/usr/src10/lib/libc_nonshared/.depend >> /usr/objs/amd64/usr/src10/lib/libc_nonshared/__iconv.o >> /usr/objs/amd64/usr/src10/lib/libc_nonshared/__iconv_free_list.o >> /usr/objs/amd64/usr/src10/lib/libc_nonshared/__iconv_get_list.o >> /usr/objs/amd64/usr/src10/lib/libc_nonshared/__stub.o >> /usr/objs/amd64/usr/src10/lib/libc_nonshared/iconv.o >> /usr/objs/amd64/usr/src10/lib/libc_nonshared/iconv_canonicalize.o >> /usr/objs/amd64/usr/src10/lib/libc_nonshared/iconv_close.o >> /usr/objs/amd64/usr/src10/lib/libc_nonshared/iconv_open.o >> /usr/objs/amd64/usr/src10/lib/libc_nonshared/iconv_open_into.o >> /usr/objs/amd64/usr/src10/lib/libc_nonshared/iconv_set_relocation_prefix.o >> /usr/objs/amd64/usr/src10/lib/libc_nonshared/iconvctl.o >> /usr/objs/amd64/usr/src10/lib/libc_nonshared/iconvlist.o >> /usr/objs/amd64/usr/src10/lib/libc_nonshared/libc_nonshared.a >> /usr/objs/amd64/usr/src10/tmp/usr/lib/libc_nonshared.a >> >> And I would expect csh to be build against: >> /usr/objs/amd64/usr/src10/tmp/usr/lib/libc_nonshared.a >> >> But for what happened, I conclude that it is linked against /usr/lib. > > During the early stages of buildworld, this is completely normal, and > expected. I just manually went into /usr/src/lib/libc_nonshared and ran make make install And now I'm trying to build world on a 1.8GHz atom, so that is slow.... Even just compiling clang is already a serious undertaking. --WjW From owner-freebsd-stable@FreeBSD.ORG Sat Dec 13 14:31:51 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F11CFDF5 for ; Sat, 13 Dec 2014 14:31:51 +0000 (UTC) Received: from cdptpa-queue02.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.226]) by mx1.freebsd.org (Postfix) with ESMTP id 9C22BE67 for ; Sat, 13 Dec 2014 14:31:50 +0000 (UTC) Received: from cdptpa-oedge-vip.email.rr.com ([107.14.174.243]) by cdptpa-queue05.email.rr.com (InterMail vM.8.04.01.13 201-2343-100-167-20131028) with ESMTP id <20141213130331.FFDT22017.cdptpa-queue05.email.rr.com@cdptpa-oedge-vip.email.rr.com> for ; Sat, 13 Dec 2014 13:03:31 +0000 Received: from [24.166.126.146] ([24.166.126.146:13156] helo=localhost) by cdptpa-oedge03 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id 26/0B-27430-F753C845; Sat, 13 Dec 2014 12:47:59 +0000 Received: from luna (unknown [10.1.0.26]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by localhost (Postfix) with ESMTPSA id 0D9CF4876 for ; Sat, 13 Dec 2014 07:47:59 -0500 (EST) Message-ID: <1418474921.2156.20.camel@michaeleichorn.com> Subject: Re: wrong patchlevel after freebsd-update install? From: "Michael B. Eichorn" To: freebsd-stable@freebsd.org Date: Sat, 13 Dec 2014 07:48:41 -0500 In-Reply-To: <7B7C7B31-B89F-4770-8DA1-CE7D0BD513EB@gromit.dlib.vt.edu> References: <201412120930.sBC9UUEF041702@mech-as221.men.bris.ac.uk> <7B7C7B31-B89F-4770-8DA1-CE7D0BD513EB@gromit.dlib.vt.edu> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.12.8 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-RR-Connecting-IP: 107.14.168.142:25 X-Cloudmark-Score: 0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Dec 2014 14:31:52 -0000 On Fri, 2014-12-12 at 10:23 -0500, Paul Mather wrote: > On Dec 12, 2014, at 4:30 AM, Anton Shterenlikht wrote: > > > On 10.0-RELEASE-p12 amd64 I updated to p13 as: > > > > freebsd-update fetch > > freebsd-update install > > reboot > > > > However, uname still shows the old patchlevel: > > > > # uname -a > > FreeBSD 001cc0f01814.anet.bris.ac.uk 10.0-RELEASE-p12 FreeBSD 10.0-RELEASE-p12 #0: Tue Nov 4 05:07:17 UTC 2014 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 > > # > > > > But freebsd-update fetch suggests I'm already at p13: > > > > # freebsd-update fetch > > Looking up update.FreeBSD.org mirrors... 5 mirrors found. > > Fetching metadata signature for 10.0-RELEASE from update5.freebsd.org... done. > > Fetching metadata index... done. > > Inspecting system... done. > > Preparing to download files... done. > > > > No updates needed to update system to 10.0-RELEASE-p13. > > # > > > > So has the update p12 -> p13 succeeded? > > What does "freebsd-version" report? If it returns 10.0-RELEASE-p13 then your freebsd-update succeeded. > > > Please clarify > > It's my understanding that uname only gets updated when freebsd-update updates the kernel. I think that's why freebsd-version was introduced. > > > > > Thanks > > > > Anton > > Cheers, > > Paul. > > I have similar question about the 10.1-RELEASE-p1 update I ran the update as: # freebsd-update fetch # freebsd-update install # ezjail-admin update -u # reboot Yet when I run: # freebsd-version -ku 10.1-RELEASE 10.1-RELEASE-p1 # uname -a FreeBSD terra.michaeleichorn.com 10.1-RELEASE FreeBSD 10.1-RELEASE #0 r274401: Tue Nov 11 21:02:49 UTC 2014 root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 Do I have a problem here or is this the expected behavior? I thought that 'freebsd-version -k' would report the new patchlevel even if there was not a kernel update. For the record 'freebsd-update fetch' and 'freebsd-update install' report no updates to install. Regards, Ike From owner-freebsd-stable@FreeBSD.ORG Sat Dec 13 14:58:55 2014 Return-Path: Delivered-To: stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DB7C6190 for ; Sat, 13 Dec 2014 14:58:55 +0000 (UTC) Received: from constantine.ingresso.co.uk (constantine.ingresso.co.uk [IPv6:2a02:b90:3002:e550::3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A1EF18B for ; Sat, 13 Dec 2014 14:58:55 +0000 (UTC) Received: from dilbert.london-internal.ingresso.co.uk ([10.64.50.6] helo=dilbert.ingresso.co.uk) by constantine.ingresso.co.uk with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.84 (FreeBSD)) (envelope-from ) id 1Xzo9k-000JF8-7P; Sat, 13 Dec 2014 14:58:52 +0000 Received: from petefrench by dilbert.ingresso.co.uk with local (Exim 4.84 (FreeBSD)) (envelope-from ) id 1Xzo9k-000HwJ-55; Sat, 13 Dec 2014 14:58:52 +0000 Date: Sat, 13 Dec 2014 14:58:52 +0000 To: stable@FreeBSD.org, rleigh@codelibre.net Subject: Re: Hard system lockups with 10.1, probably drm/newcons/radeonkms-related References: <20141212193447.GA1657@codelibre.net> In-Reply-To: <20141212193447.GA1657@codelibre.net> User-Agent: Heirloom mailx 12.4 7/29/08 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: From: Pete French X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Dec 2014 14:58:55 -0000 > Subject: Hard system lockups with 10.1, probably drm/newcons/radeonkms-related > > > Hi folks, > > With 10.1-RELEASE, I've enabled newcons at boot with > kern.vty="vt" > in loader.conf. With the latest Xorg/drm installed with pkg, I'm > seeing intermittent hangs and hard lockups of the system. I've > included the logs for one which recovered earlier today, but later > on it just locked up completely and I don't have logs for that > since I had to do a hard reset. I had to install and enable > hal+dbus to get a working keyboard and mouse when running X, > despite both working fine on the console! Interesting, as I was about to write something very similar about latest xorg under 9.3-STABLE. I have been seeing the same, hangs and hard lockups. I thought it was the card so I replaced it, but the result is the same. I am also using the new console, and I am also using Radeons. This is definetly video related - it never happens using the system remotely, and sometimes it is just the graphics which locks up (I can ssh in and shutdown). Occasionally, the lockup clears itself and the graphics comes back. Very puzzling - it can go for days without a lokcup, then sometimes I will gte several in the space of an afternoon. -pete. From owner-freebsd-stable@FreeBSD.ORG Sat Dec 13 16:42:03 2014 Return-Path: Delivered-To: stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0C63DF0C for ; Sat, 13 Dec 2014 16:42:03 +0000 (UTC) Received: from ks3095507.kimsufi.com (unknown [IPv6:2001:41d0:1:d501::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B363FB9E for ; Sat, 13 Dec 2014 16:42:02 +0000 (UTC) Received: from localhost.ikivesi.net (dsl-hkibrasgw4-50dc5d-59.dhcp.inet.fi [80.220.93.59]) by ks3095507.kimsufi.com (Postfix) with ESMTPSA id 4BC6618C0868; Sat, 13 Dec 2014 18:34:30 +0200 (EET) X-DKIM: OpenDKIM Filter v2.6.8 ks3095507.kimsufi.com 4BC6618C0868 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ikivesi.net; s=ikivesi; t=1418488470; bh=p/y37Mfz9FHDmoTSh+7zEJA7pRQHKnl6nz63Y8/gISk=; h=References:From:To:Cc:Subject:In-reply-to:Date:From; b=E87/14F46aJuofscPb2V4OqGnx34kd2aEK3AktqJle1hGDpisLfmNiR6e/Hf1FArL l66sfpLLtulXjedVuOCuCHb0cMAyu/Cu9LJw17/JRsFLZsn0hsL1HMABfCwXv+JxO0 zKDAR4INboYo87P0OFB7HouaNcgfAynRRKyLlp58= References: <20141212193447.GA1657@codelibre.net> From: Mikael Ikivesi To: Pete French Subject: Re: Hard system lockups with 10.1, probably drm/newcons/radeonkms-related In-reply-to: Date: Sat, 13 Dec 2014 18:40:50 +0200 Message-ID: <86iohfv6y5.fsf@ikivesi.net> MIME-Version: 1.0 Content-Type: text/plain Cc: rleigh@codelibre.net, stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Dec 2014 16:42:03 -0000 I also experienced these hard freezes. Nothing on logs and I get forced to do a hard reset. This never happens on console and for me it has only happened while running X. The occurences have long and random intervals. With first beta of 10.1 I had few maybe separated by a week each. With 10.1 release I tought the issued had been resolved until I got the first one just yesterday. The machine just freezes and kills all the output to graphic card (screen instantly goes to power saving mode). Only once I was able to get anything to logs: Oct 23 23:11:23 localhost kernel: drmn0: error: GPU lockup CP stall for more than 10000msec Oct 23 23:11:23 localhost kernel: drmn0: warning: GPU lockup (waiting for 0x0000000000795fa9 last fence id 0x0000000000795f85) Oct 23 23:11:23 localhost kernel: drmn0: info: Saved 1143 dwords of commands on ring 0. Oct 23 23:11:23 localhost kernel: drmn0: info: GPU softreset: 0x00000003 Oct 23 23:11:23 localhost kernel: drmn0: info: GRBM_STATUS = 0xA0003828 Oct 23 23:11:23 localhost kernel: drmn0: info: GRBM_STATUS_SE0 = 0x00000007 Oct 23 23:11:23 localhost kernel: drmn0: info: GRBM_STATUS_SE1 = 0x00000007 Oct 23 23:11:23 localhost kernel: drmn0: info: SRBM_STATUS = 0x200000C0 Oct 23 23:11:23 localhost kernel: drmn0: info: R_008674_CP_STALLED_STAT1 = 0x00000000 Oct 23 23:11:23 localhost kernel: drmn0: info: R_008678_CP_STALLED_STAT2 = 0x00004100 Oct 23 23:11:23 localhost kernel: drmn0: info: R_00867C_CP_BUSY_STAT = 0x00020182 Oct 23 23:11:23 localhost kernel: drmn0: info: R_008680_CP_STAT = 0x80028243 Oct 23 23:11:23 localhost kernel: drmn0: info: GRBM_SOFT_RESET=0x00007F6B Oct 23 23:11:23 localhost kernel: drmn0: info: GRBM_STATUS = 0x00003828 Oct 23 23:11:23 localhost kernel: drmn0: info: GRBM_STATUS_SE0 = 0x00000007 Oct 23 23:11:23 localhost kernel: drmn0: info: GRBM_STATUS_SE1 = 0x00000007 Oct 23 23:11:23 localhost kernel: drmn0: info: SRBM_STATUS = 0x200000C0 Oct 23 23:11:23 localhost kernel: drmn0: info: R_008674_CP_STALLED_STAT1 = 0x00000000 Oct 23 23:11:23 localhost kernel: drmn0: info: R_008678_CP_STALLED_STAT2 = 0x00000000 Oct 23 23:11:23 localhost kernel: drmn0: info: R_00867C_CP_BUSY_STAT = 0x00000000 Oct 23 23:11:23 localhost kernel: drmn0: info: R_008680_CP_STAT = 0x00000000 Oct 23 23:11:23 localhost kernel: drmn0: info: GPU reset succeeded, trying to resume Oct 23 23:11:23 localhost kernel: info: [drm] probing gen 2 caps for device 1022:9603 = 2/0 Oct 23 23:11:23 localhost kernel: info: [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 Oct 23 23:11:23 localhost kernel: info: [drm] PCIE GART of 512M enabled (table at 0x0000000000040000). Oct 23 23:11:23 localhost kernel: drmn0: info: WB enabled Oct 23 23:11:23 localhost kernel: drmn0: info: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0x0xfffff800324ecc00 Oct 23 23:11:23 localhost kernel: drmn0: info: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0x0xfffff800324ecc0c Oct 23 23:11:23 localhost kernel: info: [drm] ring test on 0 succeeded in 2 usecs Oct 23 23:11:23 localhost kernel: info: [drm] ring test on 3 succeeded in 1 usecs Oct 23 23:11:23 localhost kernel: info: [drm] ib test on ring 0 succeeded in 0 usecs Oct 23 23:11:23 localhost kernel: info: [drm] ib test on ring 3 succeeded in 1 usecs This log was with RC2 if I rememeber correctly. The GPU stall happened first and produced otherwise same symptoms except it was able to resume few some seconds later. But after few minutes the hard freeze occured without anything in logs. These freezes have happened mostly with very low strain on system (idle, returning from screensaver, the one with the log happened while typing text in emacs). I have left the desktop powered on for days without any problems. (I usually power off for the night). I have not been able to ssh to system while in frozen state nor does it respond to power down button. Mikael Ikivesi http://ikivesi.net Pete French writes: >> Subject: Hard system lockups with 10.1, probably drm/newcons/radeonkms-related >> >> >> Hi folks, >> >> With 10.1-RELEASE, I've enabled newcons at boot with >> kern.vty="vt" >> in loader.conf. With the latest Xorg/drm installed with pkg, I'm >> seeing intermittent hangs and hard lockups of the system. I've >> included the logs for one which recovered earlier today, but later >> on it just locked up completely and I don't have logs for that >> since I had to do a hard reset. I had to install and enable >> hal+dbus to get a working keyboard and mouse when running X, >> despite both working fine on the console! > > Interesting, as I was about to write something very similar about > latest xorg under 9.3-STABLE. I have been seeing the same, > hangs and hard lockups. I thought it was the card so I replaced it, but > the result is the same. > > I am also using the new console, and I am also using Radeons. > > This is definetly video related - it never happens using the system > remotely, and sometimes it is just the graphics which locks up (I > can ssh in and shutdown). Occasionally, the lockup clears itself and > the graphics comes back. > > Very puzzling - it can go for days without a lokcup, then sometimes > I will gte several in the space of an afternoon. > > -pete. > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Sat Dec 13 18:32:05 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0DFAE79D for ; Sat, 13 Dec 2014 18:32:05 +0000 (UTC) Received: from mail-ig0-x231.google.com (mail-ig0-x231.google.com [IPv6:2607:f8b0:4001:c05::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C48A17B7 for ; Sat, 13 Dec 2014 18:32:04 +0000 (UTC) Received: by mail-ig0-f177.google.com with SMTP id z20so3163978igj.4 for ; Sat, 13 Dec 2014 10:32:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=NqQf5JOoBEOUsCZfaddJo1CsMhCitD6Cc+5WCNww+Ts=; b=KI8iN+OdV47/tGVUpkGpYo1SeUNPT0IwOtL6nfznICxOlfEf26xclUPPig7iTs4ZxA Kckd6++RGjgzdsiUla8HvcDUkHQlqQT2iqiU/BPZEfn8iPWk34IHUBBpSw8j5bnZqjxd 9eeanm2DLelOVNUBAGnisPZaJx1BNcTqTdSm62kVfGTakU+WV/LBMb5rzyh1oPOGSIi7 +Ao97bIfFSRQcc919lprj2CPj0U6LsTykHIWbxt20vzbZ335BCO2hd011fzOErhV+VpT NmyVbYgFp+l+quSEINfsdkPezqUyB0cB4fSLGH0oTnEVCFmcva9mgEvXuJytqYcKkgfS AKSQ== MIME-Version: 1.0 X-Received: by 10.107.168.18 with SMTP id r18mr21549033ioe.76.1418495524236; Sat, 13 Dec 2014 10:32:04 -0800 (PST) Sender: kob6558@gmail.com Received: by 10.107.52.19 with HTTP; Sat, 13 Dec 2014 10:32:04 -0800 (PST) In-Reply-To: <1418474921.2156.20.camel@michaeleichorn.com> References: <201412120930.sBC9UUEF041702@mech-as221.men.bris.ac.uk> <7B7C7B31-B89F-4770-8DA1-CE7D0BD513EB@gromit.dlib.vt.edu> <1418474921.2156.20.camel@michaeleichorn.com> Date: Sat, 13 Dec 2014 10:32:04 -0800 X-Google-Sender-Auth: ayKax7kr7I8kS-DE-F2dHM9ZEm0 Message-ID: Subject: Re: wrong patchlevel after freebsd-update install? From: Kevin Oberman To: "Michael B. Eichorn" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: FreeBSD-STABLE Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Dec 2014 18:32:05 -0000 On Sat, Dec 13, 2014 at 4:48 AM, Michael B. Eichorn wrote: > On Fri, 2014-12-12 at 10:23 -0500, Paul Mather wrote: > > On Dec 12, 2014, at 4:30 AM, Anton Shterenlikht > wrote: > > > > > On 10.0-RELEASE-p12 amd64 I updated to p13 as: > > > > > > freebsd-update fetch > > > freebsd-update install > > > reboot > > > > > > However, uname still shows the old patchlevel: > > > > > > # uname -a > > > FreeBSD 001cc0f01814.anet.bris.ac.uk 10.0-RELEASE-p12 FreeBSD > 10.0-RELEASE-p12 #0: Tue Nov 4 05:07:17 UTC 2014 > root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 > > > # > > > > > > But freebsd-update fetch suggests I'm already at p13: > > > > > > # freebsd-update fetch > > > Looking up update.FreeBSD.org mirrors... 5 mirrors found. > > > Fetching metadata signature for 10.0-RELEASE from > update5.freebsd.org... done. > > > Fetching metadata index... done. > > > Inspecting system... done. > > > Preparing to download files... done. > > > > > > No updates needed to update system to 10.0-RELEASE-p13. > > > # > > > > > > So has the update p12 -> p13 succeeded? > > > > What does "freebsd-version" report? If it returns 10.0-RELEASE-p13 then > your freebsd-update succeeded. > > > > > Please clarify > > > > It's my understanding that uname only gets updated when freebsd-update > updates the kernel. I think that's why freebsd-version was introduced. > > > > > > > > Thanks > > > > > > Anton > > > > Cheers, > > > > Paul. > > > > > > I have similar question about the 10.1-RELEASE-p1 update > > I ran the update as: > # freebsd-update fetch > # freebsd-update install > # ezjail-admin update -u > # reboot > > Yet when I run: > # freebsd-version -ku > 10.1-RELEASE > 10.1-RELEASE-p1 > > # uname -a > FreeBSD terra.michaeleichorn.com 10.1-RELEASE FreeBSD 10.1-RELEASE #0 > r274401: Tue Nov 11 21:02:49 UTC 2014 > root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 > > Do I have a problem here or is this the expected behavior? > > I thought that 'freebsd-version -k' would report the new patchlevel even > if there was not a kernel update. > > For the record 'freebsd-update fetch' and 'freebsd-update install' > report no updates to install. > > Regards, > > Ike > This is normal and expected. FreeBSD, when built from sources as was always done before freebsd-update(8) came long, always built the kernel (buildkernel) and non-kernel or "user land" (buildworld) from one set of sources and, as a result, the kernel version as reported by uname(1) was all that was normally used. Along came binary updates (freebsd-update) andit became perfectly normal to install an update that only patched the kernel or the user space. As a result, security patches often resulted in updates that uname(1) did not change because the kernel was not updated. des@ created freebsd-version about a year ago to deal with this. The 10.0-p1 update was such a case where the kernel was not updated, so uname still reports the version as 10.1-RELEASE. For more information on this, see the freebsd-version man page. It goes into this in far more detail. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com From owner-freebsd-stable@FreeBSD.ORG Sat Dec 13 20:13:02 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 306743D1 for ; Sat, 13 Dec 2014 20:13:02 +0000 (UTC) Received: from host.rentabin.com.au (host.rentabin.com.au [122.201.114.152]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E37B2100 for ; Sat, 13 Dec 2014 20:13:01 +0000 (UTC) Received: from usbwalls by host.rentabin.com.au with local (Exim 4.82) (envelope-from ) id 1XzsnF-0007Lc-16 for freebsd-stable@freebsd.org; Sun, 14 Dec 2014 06:55:57 +1100 To: freebsd-stable@freebsd.org Subject: Facebook password change X-PHP-Script: usbwallsocket.com.au/ for 127.0.0.1 From: "Facebook" X-Mailer: grasslandtromboneV8.75 Reply-To: "Facebook" Mime-Version: 1.0 Message-Id: Date: Sun, 14 Dec 2014 06:55:57 +1100 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host.rentabin.com.au X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [511 509] / [47 12] X-AntiAbuse: Sender Address Domain - host.rentabin.com.au X-Get-Message-Sender-Via: host.rentabin.com.au: authenticated_id: usbwalls/from_h Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Dec 2014 20:13:02 -0000 Facebook facebook Hi, Your Facebook password was been reset on Saturday, December 13, 2014 at 07:55PM (UTC) due to suspicious activity of your account. Operating system: Windows Browser: Google Chrome IP address: 182.125.92.56 Estimated location: Pomfret, MD, US To restore the password complete this form, please, your request will be considered within 24 hours. Thanks, The Facebook Security Team Facebook, Inc., Attention: Department 425, PO Box 10005, Palo Alto, CA 94303 From owner-freebsd-stable@FreeBSD.ORG Sat Dec 13 20:32:38 2014 Return-Path: Delivered-To: stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 357228AE for ; Sat, 13 Dec 2014 20:32:38 +0000 (UTC) Received: from constantine.ingresso.co.uk (constantine.ingresso.co.uk [IPv6:2a02:b90:3002:e550::3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F219D300 for ; Sat, 13 Dec 2014 20:32:37 +0000 (UTC) Received: from dilbert.london-internal.ingresso.co.uk ([10.64.50.6] helo=dilbert.ingresso.co.uk) by constantine.ingresso.co.uk with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.84 (FreeBSD)) (envelope-from ) id 1XztMg-0001vj-WC; Sat, 13 Dec 2014 20:32:35 +0000 Received: from petefrench by dilbert.ingresso.co.uk with local (Exim 4.84 (FreeBSD)) (envelope-from ) id 1XztMg-000KOk-Tt; Sat, 13 Dec 2014 20:32:34 +0000 To: petefrench@ingresso.co.uk, rleigh@codelibre.net, stable@FreeBSD.org Subject: Re: Hard system lockups with 10.1, probably drm/newcons/radeonkms-related Message-Id: From: Pete French Date: Sat, 13 Dec 2014 20:32:34 +0000 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Dec 2014 20:32:38 -0000 "Mesa 10.3 brings major improvements in stability and performance, especially for Radeon owners, compared to Mesa 9.1. For instance, it fixes many of the GPU lockups you may see." (from http://blogs.freebsdish.org/graphics/2014/10/17/mesa-10-3-0-committed/) Interesting comment... am going to give new mesa a try on Monday (also means upgrading to 10.1, but have been meaning to do that anyway). -pete.