From owner-freebsd-hackers@freebsd.org Sun Jul 10 01:25:19 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 03143B83CC7 for ; Sun, 10 Jul 2016 01:25:19 +0000 (UTC) (envelope-from karl@denninger.net) Received: from mail.denninger.net (denninger.net [70.169.168.7]) (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 B31BB1BB4 for ; Sun, 10 Jul 2016 01:25:18 +0000 (UTC) (envelope-from karl@denninger.net) Received: from [192.168.1.40] (Karl-Desktop.Denninger.net [192.168.1.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.denninger.net (Postfix) with ESMTPSA id 8DB5139C5BB for ; Sat, 9 Jul 2016 20:25:11 -0500 (CDT) To: freebsd-hackers@freebsd.org From: Karl Denninger Subject: 11-Beta1 problem with virtual KVM Message-ID: <4dc72d13-bdbf-3947-0564-4e8553475b17@denninger.net> Date: Sat, 9 Jul 2016 20:24:48 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-512; boundary="------------ms030806070004000009090304" X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Jul 2016 01:25:19 -0000 This is a cryptographically signed message in MIME format. --------------ms030806070004000009090304 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable It looks like the VGA "synthetic" adapter that the system is outputting on for the console now has one extra scan line. This results in the last line being half cut-off on my java-based KVM.... very annoying and it makes it extremely difficult to work on the system via it. This was *not* a problem with 10.x; it's a new issue for 11. Ideas to fix? Setting rows does not do it. --=20 Karl Denninger karl@denninger.net /The Market Ticker/ /[S/MIME encrypted email preferred]/ --------------ms030806070004000009090304 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgMFADCABgkqhkiG9w0BBwEAAKCC Bl8wggZbMIIEQ6ADAgECAgEpMA0GCSqGSIb3DQEBCwUAMIGQMQswCQYDVQQGEwJVUzEQMA4G A1UECBMHRmxvcmlkYTESMBAGA1UEBxMJTmljZXZpbGxlMRkwFwYDVQQKExBDdWRhIFN5c3Rl bXMgTExDMRwwGgYDVQQDExNDdWRhIFN5c3RlbXMgTExDIENBMSIwIAYJKoZIhvcNAQkBFhND dWRhIFN5c3RlbXMgTExDIENBMB4XDTE1MDQyMTAyMjE1OVoXDTIwMDQxOTAyMjE1OVowWjEL MAkGA1UEBhMCVVMxEDAOBgNVBAgTB0Zsb3JpZGExGTAXBgNVBAoTEEN1ZGEgU3lzdGVtcyBM TEMxHjAcBgNVBAMTFUthcmwgRGVubmluZ2VyIChPQ1NQKTCCAiIwDQYJKoZIhvcNAQEBBQAD ggIPADCCAgoCggIBALmEWPhAdphrWd4K5VTvE5pxL3blRQPyGF3ApjUjgtavqU1Y8pbI3Byg XDj2/Uz9Si8XVj/kNbKEjkRh5SsNvx3Fc0oQ1uVjyCq7zC/kctF7yLzQbvWnU4grAPZ3IuAp 3/fFxIVaXpxEdKmyZAVDhk9az+IgHH43rdJRIMzxJ5vqQMb+n2EjadVqiGPbtG9aZEImlq7f IYDTnKyToi23PAnkPwwT+q1IkI2DTvf2jzWrhLR5DTX0fUYC0nxlHWbjgpiapyJWtR7K2YQO aevQb/3vN9gSojT2h+cBem7QIj6U69rEYcEDvPyCMXEV9VcXdcmW42LSRsPvZcBHFkWAJqMZ Myiz4kumaP+s+cIDaXitR/szoqDKGSHM4CPAZV9Yh8asvxQL5uDxz5wvLPgS5yS8K/o7zDR5 vNkMCyfYQuR6PAJxVOk5Arqvj9lfP3JSVapwbr01CoWDBkpuJlKfpQIEeC/pcCBKknllbMYq yHBO2TipLyO5Ocd1nhN/nOsO+C+j31lQHfOMRZaPQykXVPWG5BbhWT7ttX4vy5hOW6yJgeT/ o3apynlp1cEavkQRS8uJHoQszF6KIrQMID/JfySWvVQ4ksnfzwB2lRomrdrwnQ4eG/HBS+0l eozwOJNDIBlAP+hLe8A5oWZgooIIK/SulUAsfI6Sgd8dTZTTYmlhAgMBAAGjgfQwgfEwNwYI KwYBBQUHAQEEKzApMCcGCCsGAQUFBzABhhtodHRwOi8vY3VkYXN5c3RlbXMubmV0Ojg4ODgw CQYDVR0TBAIwADARBglghkgBhvhCAQEEBAMCBaAwCwYDVR0PBAQDAgXgMCwGCWCGSAGG+EIB DQQfFh1PcGVuU1NMIEdlbmVyYXRlZCBDZXJ0aWZpY2F0ZTAdBgNVHQ4EFgQUxRyULenJaFwX RtT79aNmIB/u5VkwHwYDVR0jBBgwFoAUJHGbnYV9/N3dvbDKkpQDofrTbTUwHQYDVR0RBBYw FIESa2FybEBkZW5uaW5nZXIubmV0MA0GCSqGSIb3DQEBCwUAA4ICAQBPf3cYtmKowmGIYsm6 eBinJu7QVWvxi1vqnBz3KE+HapqoIZS8/PolB/hwiY0UAE1RsjBJ7yEjihVRwummSBvkoOyf G30uPn4yg4vbJkR9lTz8d21fPshWETa6DBh2jx2Qf13LZpr3Pj2fTtlu6xMYKzg7cSDgd2bO sJGH/rcvva9Spkx5Vfq0RyOrYph9boshRN3D4tbWgBAcX9POdXCVfJONDxhfBuPHsJ6vEmPb An+XL5Yl26XYFPiODQ+Qbk44Ot1kt9s7oS3dVUrh92Qv0G3J3DF+Vt6C15nED+f+bk4gScu+ JHT7RjEmfa18GT8DcT//D1zEke1Ymhb41JH+GyZchDRWtjxsS5OBFMzrju7d264zJUFtX7iJ 3xvpKN7VcZKNtB6dLShj3v/XDsQVQWXmR/1YKWZ93C3LpRs2Y5nYdn6gEOpL/WfQFThtfnat HNc7fNs5vjotaYpBl5H8+VCautKbGOs219uQbhGZLYTv6okuKcY8W+4EJEtK0xB08vqr9Jd0 FS9MGjQE++GWo+5eQxFt6nUENHbVYnsr6bYPQsZH0CRNycgTG9MwY/UIXOf4W034UpR82TBG 1LiMsYfb8ahQJhs3wdf1nzipIjRwoZKT1vGXh/cj3gwSr64GfenURBxaFZA5O1acOZUjPrRT n3ci4McYW/0WVVA3lDGCBRMwggUPAgEBMIGWMIGQMQswCQYDVQQGEwJVUzEQMA4GA1UECBMH RmxvcmlkYTESMBAGA1UEBxMJTmljZXZpbGxlMRkwFwYDVQQKExBDdWRhIFN5c3RlbXMgTExD MRwwGgYDVQQDExNDdWRhIFN5c3RlbXMgTExDIENBMSIwIAYJKoZIhvcNAQkBFhNDdWRhIFN5 c3RlbXMgTExDIENBAgEpMA0GCWCGSAFlAwQCAwUAoIICTTAYBgkqhkiG9w0BCQMxCwYJKoZI hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNjA3MTAwMTI0NDhaME8GCSqGSIb3DQEJBDFCBECj YBNRBxDuY8x5IqfI1RxDOKh4mdrGAebnK8D2WXaNufIkH6UFk6ckKzMNwN972RuCgmYtDQaC WvQNBtsy2XB3MGwGCSqGSIb3DQEJDzFfMF0wCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBAjAK BggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYI KoZIhvcNAwICASgwgacGCSsGAQQBgjcQBDGBmTCBljCBkDELMAkGA1UEBhMCVVMxEDAOBgNV BAgTB0Zsb3JpZGExEjAQBgNVBAcTCU5pY2V2aWxsZTEZMBcGA1UEChMQQ3VkYSBTeXN0ZW1z IExMQzEcMBoGA1UEAxMTQ3VkYSBTeXN0ZW1zIExMQyBDQTEiMCAGCSqGSIb3DQEJARYTQ3Vk YSBTeXN0ZW1zIExMQyBDQQIBKTCBqQYLKoZIhvcNAQkQAgsxgZmggZYwgZAxCzAJBgNVBAYT AlVTMRAwDgYDVQQIEwdGbG9yaWRhMRIwEAYDVQQHEwlOaWNldmlsbGUxGTAXBgNVBAoTEEN1 ZGEgU3lzdGVtcyBMTEMxHDAaBgNVBAMTE0N1ZGEgU3lzdGVtcyBMTEMgQ0ExIjAgBgkqhkiG 9w0BCQEWE0N1ZGEgU3lzdGVtcyBMTEMgQ0ECASkwDQYJKoZIhvcNAQEBBQAEggIAmrtFY1C0 EvzyAxR480g289U41jfmwBHGoSHgLif9P3xgL0aSIpDsJZJkPKQ+ytFz1HFkcBa0EY75QqoX c/TdwdJkheCLfSzVBILDJEVTCWaKqQh3wWIHNEfVIvBTsLcaTcZN5kuXPNXKSKTDWPMheV/u h2KRrqSntlydKCYttaDKp2QgFo6mraLHJCS0DNnytW/8o5XqNDZr77SSOHCb/1+/84kWbH6U eDMjcxIJiovE/LLzmLyecZgPmRyaZ7DYDcTaka5wuGJz52PqePGrFe+jgw1jAFRaKcoc/2oh ZGfaKGODAgOLPSD2ZtPZ5U9CKf33aYOQFp+OGu8C+Gtjj/6Kj5PrtqxXM5sEJYCMfpKRyEGE LMnD99WTVGB8XlMAtHsb1A9o/lCgPs+8iiwoHTGpMsx86+v1uK7pgcgg13oeAOBwzBXYHgAq OSwV88qrNjAq3N2hymabYv6s0HnjTkIilPhajnbj0EJaHQX3rkBB7E4URU6d3t/vNFbEYiFZ pwuqK1/y4oX9gnWgTKn/9cvmjkbY3nsM2cOsVUHrov8Wj6MbxsUq2nhYf5AdQWuQRbgQkXV4 g041d36YkGgTqg3o86m7D7y5IExjTchl98NcneNWm7ff5UZT4nFRGP0BtjFH/FFaHa1kqBMS GE2JNMOfeNXxMdWuhHxSn8BEzmIAAAAAAAA= --------------ms030806070004000009090304-- From owner-freebsd-hackers@freebsd.org Sun Jul 10 18:03:10 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2501CB832E0 for ; Sun, 10 Jul 2016 18:03:10 +0000 (UTC) (envelope-from ori@eigenstate.org) Received: from mimir.eigenstate.org (mimir.eigenstate.org [206.124.132.107]) by mx1.freebsd.org (Postfix) with ESMTP id E93431A57 for ; Sun, 10 Jul 2016 18:03:08 +0000 (UTC) (envelope-from ori@eigenstate.org) Received: from oneeye (unknown [98.207.157.125]) by mimir.eigenstate.org (Postfix) with ESMTPSA id 21645600C9 for ; Sun, 10 Jul 2016 13:54:44 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eigenstate.org; s=mail; t=1468173284; bh=9oUNb2c7iOH9zpMPOC1KO2YDEMXedF7pbGd49Q/lyLo=; h=Date:From:To:Subject; b=XQRsPyMFacCuC4NziQe2IbP9Zhruf2DanguwlvqlDlGw0VlYkX2DOr3iVcZu04zeP 0POZPxFboKsiK4iq4y/GDGt+4Z9jeMC9etySiDvw3o1/6Ge8RvbU07bqLb8Hr81zrw gqehinjNwvDtUIRU5or+gkwhmo4PZ86F0SyUVPQo= Date: Sun, 10 Jul 2016 10:54:42 -0700 From: Ori Bernstein To: freebsd-hackers@freebsd.org Subject: ZFS Deadlock: 'Directory of Death' Message-Id: <20160710105442.3e566a9595ed70f2d29a0f1a@eigenstate.org> X-Mailer: Sylpheed 3.5.0 (GTK+ 2.24.29; amd64-portbld-freebsd10.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Jul 2016 18:03:10 -0000 I've got a fun issue: There's a directory of death on my desktop running ZFS. When installing ports, I Any program that tries to touch a directory in /usr/ports hangs, deadlocked in the VFS cache lookup: $ sudo procstat -kk 94688 PID TID COMM TDNAME KSTACK 94688 102697 fuser - mi_switch+0xe1 sleepq_wait+0x3a sleeplk+0x15d __lockmgr_args+0x91a vop_stdlock+0x3c VOP_LOCK1_APV+0xab _vn_lock+0x43 vget+0x73 cache_lookup+0x5d5 vfs_cache_lookup+0xac VOP_LOOKUP_APV+0xa1 lookup+0x5a1 namei+0x4d4 kern_statat_vnhook+0xae sys_stat+0x2d amd64_syscall+0x40f Xfast_syscall+0xfb The process that seems to have triggered this was a port install of NPM, which seems to have deadlocked while renaming some files: $ ps a 93931 93931 15- D 0:11.87 npm (node) $ sudo procstat -kk 93931 PID TID COMM TDNAME KSTACK 93931 101449 node - mi_switch+0xe1 sleepq_catch_signals+0xab sleepq_wait_sig+0xf _sleep+0x27d umtxq_sleep+0x125 do_sem_wait+0x4db __umtx_op_sem_wait+0x73 amd64_syscall+0x40f Xfast_syscall+0xfb 93931 101977 node - mi_switch+0xe1 sleepq_catch_signals+0xab sleepq_wait_sig+0xf _sleep+0x27d kern_kevent_fp+0x399 kern_kevent+0x9f sys_kevent+0x12a amd64_syscall+0x40f Xfast_syscall+0xfb 93931 102252 node V8 WorkerThread mi_switch+0xe1 sleepq_catch_signals+0xab sleepq_wait_sig+0xf _sleep+0x27d umtxq_sleep+0x125 do_sem_wait+0x4db __umtx_op_sem_wait+0x73 amd64_syscall+0x40f Xfast_syscall+0xfb 93931 102258 node V8 WorkerThread mi_switch+0xe1 sleepq_catch_signals+0xab sleepq_wait_sig+0xf _sleep+0x27d umtxq_sleep+0x125 do_sem_wait+0x4db __umtx_op_sem_wait+0x73 amd64_syscall+0x40f Xfast_syscall+0xfb 93931 102262 node V8 WorkerThread mi_switch+0xe1 sleepq_catch_signals+0xab sleepq_wait_sig+0xf _sleep+0x27d umtxq_sleep+0x125 do_sem_wait+0x4db __umtx_op_sem_wait+0x73 amd64_syscall+0x40f Xfast_syscall+0xfb 93931 102266 node V8 WorkerThread mi_switch+0xe1 sleepq_catch_signals+0xab sleepq_wait_sig+0xf _sleep+0x27d umtxq_sleep+0x125 do_sem_wait+0x4db __umtx_op_sem_wait+0x73 amd64_syscall+0x40f Xfast_syscall+0xfb 93931 102279 node - mi_switch+0xe1 sleepq_catch_signals+0xab sleepq_wait_sig+0xf _sleep+0x27d umtxq_sleep+0x125 do_wait+0x387 __umtx_op_wait_uint_private+0x83 amd64_syscall+0x40f Xfast_syscall+0xfb 93931 102285 node - mi_switch+0xe1 sleepq_wait+0x3a sleeplk+0x15d __lockmgr_args+0xca0 vop_stdlock+0x3c VOP_LOCK1_APV+0xab _vn_lock+0x43 vputx+0x21f zfs_rename_unlock+0x3e zfs_freebsd_rename+0xe39 VOP_RENAME_APV+0xab kern_renameat+0x4a6 amd64_syscall+0x40f Xfast_syscall+0xfb 93931 102287 node - mi_switch+0xe1 sleepq_wait+0x3a sleeplk+0x15d __lockmgr_args+0x91a vop_stdlock+0x3c VOP_LOCK1_APV+0xab _vn_lock+0x43 zfs_lookup+0x45d zfs_freebsd_lookup+0x6d VOP_CACHEDLOOKUP_APV+0xa1 vfs_cache_lookup+0xd6 VOP_LOOKUP_APV+0xa1 lookup+0x5a1 namei+0x4d4 kern_renameat+0x1b7 amd64_syscall+0x40f Xfast_syscall+0xfb 93931 102294 node - mi_switch+0xe1 sleepq_wait+0x3a sleeplk+0x15d __lockmgr_args+0x91a vop_stdlock+0x3c VOP_LOCK1_APV+0xab _vn_lock+0x43 vget+0x73 cache_lookup+0x5d5 vfs_cache_lookup+0xac VOP_LOOKUP_APV+0xa1 lookup+0x5a1 namei+0x4d4 kern_renameat+0x1b7 amd64_syscall+0x40f Xfast_syscall+0xfb The specific directory that is causing this issue is: /usr/ports/www/npm/work/stage/usr/local/lib/node_modules/npm/node_modules/npmlog/node_modules/gauge Right now I'm running on a stock FreeBSD 10.3 release. FreeBSD oneeye 10.3-RELEASE-p4 FreeBSD 10.3-RELEASE-p4 #0: Sat May 28 12:23:44 UTC 2016 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 I'm going to guess that this deadlock will go away if I reboot this box, but I haven't rebooted yet. Since this isn't really impacting anything important that I'm doing, I can keep it up for a bit if someone wants me to gather some extra information to track down the root cause. -- Ori Bernstein From owner-freebsd-hackers@freebsd.org Sun Jul 10 18:07:36 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BD582B833A4 for ; Sun, 10 Jul 2016 18:07:36 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from mx1.scaleengine.net (mx1.scaleengine.net [209.51.186.6]) (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 901601B98 for ; Sun, 10 Jul 2016 18:07:36 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [10.1.1.2] (unknown [10.1.1.2]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 7A898101B for ; Sun, 10 Jul 2016 18:07:29 +0000 (UTC) Subject: Re: ZFS Deadlock: 'Directory of Death' To: freebsd-hackers@freebsd.org References: <20160710105442.3e566a9595ed70f2d29a0f1a@eigenstate.org> From: Allan Jude Message-ID: <8133e3d5-cfc8-5e6c-44cf-079b2e11d896@freebsd.org> Date: Sun, 10 Jul 2016 14:07:28 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <20160710105442.3e566a9595ed70f2d29a0f1a@eigenstate.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Jul 2016 18:07:36 -0000 On 2016-07-10 13:54, Ori Bernstein wrote: > I've got a fun issue: There's a directory of death on my desktop running ZFS. > When installing ports, I Any program that tries to touch a directory in > /usr/ports hangs, deadlocked in the VFS cache lookup: > > $ sudo procstat -kk 94688 > PID TID COMM TDNAME KSTACK > 94688 102697 fuser - mi_switch+0xe1 sleepq_wait+0x3a sleeplk+0x15d __lockmgr_args+0x91a vop_stdlock+0x3c VOP_LOCK1_APV+0xab _vn_lock+0x43 vget+0x73 cache_lookup+0x5d5 vfs_cache_lookup+0xac VOP_LOOKUP_APV+0xa1 lookup+0x5a1 namei+0x4d4 kern_statat_vnhook+0xae sys_stat+0x2d amd64_syscall+0x40f Xfast_syscall+0xfb > > > The process that seems to have triggered this was a port install of NPM, which seems to have > deadlocked while renaming some files: > > $ ps a 93931 > 93931 15- D 0:11.87 npm (node) > > $ sudo procstat -kk 93931 > PID TID COMM TDNAME KSTACK > 93931 101449 node - mi_switch+0xe1 sleepq_catch_signals+0xab sleepq_wait_sig+0xf _sleep+0x27d umtxq_sleep+0x125 do_sem_wait+0x4db __umtx_op_sem_wait+0x73 amd64_syscall+0x40f Xfast_syscall+0xfb > 93931 101977 node - mi_switch+0xe1 sleepq_catch_signals+0xab sleepq_wait_sig+0xf _sleep+0x27d kern_kevent_fp+0x399 kern_kevent+0x9f sys_kevent+0x12a amd64_syscall+0x40f Xfast_syscall+0xfb > 93931 102252 node V8 WorkerThread mi_switch+0xe1 sleepq_catch_signals+0xab sleepq_wait_sig+0xf _sleep+0x27d umtxq_sleep+0x125 do_sem_wait+0x4db __umtx_op_sem_wait+0x73 amd64_syscall+0x40f Xfast_syscall+0xfb > 93931 102258 node V8 WorkerThread mi_switch+0xe1 sleepq_catch_signals+0xab sleepq_wait_sig+0xf _sleep+0x27d umtxq_sleep+0x125 do_sem_wait+0x4db __umtx_op_sem_wait+0x73 amd64_syscall+0x40f Xfast_syscall+0xfb > 93931 102262 node V8 WorkerThread mi_switch+0xe1 sleepq_catch_signals+0xab sleepq_wait_sig+0xf _sleep+0x27d umtxq_sleep+0x125 do_sem_wait+0x4db __umtx_op_sem_wait+0x73 amd64_syscall+0x40f Xfast_syscall+0xfb > 93931 102266 node V8 WorkerThread mi_switch+0xe1 sleepq_catch_signals+0xab sleepq_wait_sig+0xf _sleep+0x27d umtxq_sleep+0x125 do_sem_wait+0x4db __umtx_op_sem_wait+0x73 amd64_syscall+0x40f Xfast_syscall+0xfb > 93931 102279 node - mi_switch+0xe1 sleepq_catch_signals+0xab sleepq_wait_sig+0xf _sleep+0x27d umtxq_sleep+0x125 do_wait+0x387 __umtx_op_wait_uint_private+0x83 amd64_syscall+0x40f Xfast_syscall+0xfb > 93931 102285 node - mi_switch+0xe1 sleepq_wait+0x3a sleeplk+0x15d __lockmgr_args+0xca0 vop_stdlock+0x3c VOP_LOCK1_APV+0xab _vn_lock+0x43 vputx+0x21f zfs_rename_unlock+0x3e zfs_freebsd_rename+0xe39 VOP_RENAME_APV+0xab kern_renameat+0x4a6 amd64_syscall+0x40f Xfast_syscall+0xfb > 93931 102287 node - mi_switch+0xe1 sleepq_wait+0x3a sleeplk+0x15d __lockmgr_args+0x91a vop_stdlock+0x3c VOP_LOCK1_APV+0xab _vn_lock+0x43 zfs_lookup+0x45d zfs_freebsd_lookup+0x6d VOP_CACHEDLOOKUP_APV+0xa1 vfs_cache_lookup+0xd6 VOP_LOOKUP_APV+0xa1 lookup+0x5a1 namei+0x4d4 kern_renameat+0x1b7 amd64_syscall+0x40f Xfast_syscall+0xfb > 93931 102294 node - mi_switch+0xe1 sleepq_wait+0x3a sleeplk+0x15d __lockmgr_args+0x91a vop_stdlock+0x3c VOP_LOCK1_APV+0xab _vn_lock+0x43 vget+0x73 cache_lookup+0x5d5 vfs_cache_lookup+0xac VOP_LOOKUP_APV+0xa1 lookup+0x5a1 namei+0x4d4 kern_renameat+0x1b7 amd64_syscall+0x40f Xfast_syscall+0xfb > > The specific directory that is causing this issue is: > > /usr/ports/www/npm/work/stage/usr/local/lib/node_modules/npm/node_modules/npmlog/node_modules/gauge > > Right now I'm running on a stock FreeBSD 10.3 release. > > FreeBSD oneeye 10.3-RELEASE-p4 FreeBSD 10.3-RELEASE-p4 #0: Sat May 28 12:23:44 UTC 2016 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 > > I'm going to guess that this deadlock will go away if I reboot this box, but > I haven't rebooted yet. Since this isn't really impacting anything important > that I'm doing, I can keep it up for a bit if someone wants me to gather some > extra information to track down the root cause. > It looks like your problem is similar to: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209158 If you read that PR and find your problem is similar, please add your information to that post. -- Allan Jude From owner-freebsd-hackers@freebsd.org Sun Jul 10 18:36:43 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 93442B83974 for ; Sun, 10 Jul 2016 18:36:43 +0000 (UTC) (envelope-from ori@eigenstate.org) Received: from mimir.eigenstate.org (mimir.eigenstate.org [206.124.132.107]) by mx1.freebsd.org (Postfix) with ESMTP id 730F21953; Sun, 10 Jul 2016 18:36:43 +0000 (UTC) (envelope-from ori@eigenstate.org) Received: from oneeye (unknown [98.207.157.125]) by mimir.eigenstate.org (Postfix) with ESMTPSA id 8E802600C9; Sun, 10 Jul 2016 14:36:42 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eigenstate.org; s=mail; t=1468175802; bh=FcK5FeJyR7oxngeU/JXiXpTQ3TU+TmRGbG07b5PErnA=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=Aa184s9i4IZArkItAe5feSEcqHzhMeyTMU0CGPOy+//Pmxyktj/QB1Un6Xb+7HuN9 dB53o8/ra1iRwpiNpLGwUIf+wlH8qeonMGIyDEh1kYSeNLaouAtjOG3cWdXuloCjdm 7/f5qJJB/oAy+xe/qoudoNC9QA6Z56joOAngoB6U= Date: Sun, 10 Jul 2016 11:36:41 -0700 From: Ori Bernstein To: Allan Jude Cc: freebsd-hackers@freebsd.org Subject: Re: ZFS Deadlock: 'Directory of Death' Message-Id: <20160710113641.960c9b52e67ed09d6bb05e29@eigenstate.org> In-Reply-To: <8133e3d5-cfc8-5e6c-44cf-079b2e11d896@freebsd.org> References: <20160710105442.3e566a9595ed70f2d29a0f1a@eigenstate.org> <8133e3d5-cfc8-5e6c-44cf-079b2e11d896@freebsd.org> X-Mailer: Sylpheed 3.5.0 (GTK+ 2.24.29; amd64-portbld-freebsd10.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Jul 2016 18:36:43 -0000 Looks like it, down to very very similar stack traces. On Sun, 10 Jul 2016 14:07:28 -0400, Allan Jude wrote: > On 2016-07-10 13:54, Ori Bernstein wrote: > > I've got a fun issue: There's a directory of death on my desktop running ZFS. > > When installing ports, I Any program that tries to touch a directory in > > /usr/ports hangs, deadlocked in the VFS cache lookup: > > > > $ sudo procstat -kk 94688 > > PID TID COMM TDNAME KSTACK > > 94688 102697 fuser - mi_switch+0xe1 sleepq_wait+0x3a sleeplk+0x15d __lockmgr_args+0x91a vop_stdlock+0x3c VOP_LOCK1_APV+0xab _vn_lock+0x43 vget+0x73 cache_lookup+0x5d5 vfs_cache_lookup+0xac VOP_LOOKUP_APV+0xa1 lookup+0x5a1 namei+0x4d4 kern_statat_vnhook+0xae sys_stat+0x2d amd64_syscall+0x40f Xfast_syscall+0xfb > > > > > > The process that seems to have triggered this was a port install of NPM, which seems to have > > deadlocked while renaming some files: > > > > $ ps a 93931 > > 93931 15- D 0:11.87 npm (node) > > > > $ sudo procstat -kk 93931 > > PID TID COMM TDNAME KSTACK > > 93931 101449 node - mi_switch+0xe1 sleepq_catch_signals+0xab sleepq_wait_sig+0xf _sleep+0x27d umtxq_sleep+0x125 do_sem_wait+0x4db __umtx_op_sem_wait+0x73 amd64_syscall+0x40f Xfast_syscall+0xfb > > 93931 101977 node - mi_switch+0xe1 sleepq_catch_signals+0xab sleepq_wait_sig+0xf _sleep+0x27d kern_kevent_fp+0x399 kern_kevent+0x9f sys_kevent+0x12a amd64_syscall+0x40f Xfast_syscall+0xfb > > 93931 102252 node V8 WorkerThread mi_switch+0xe1 sleepq_catch_signals+0xab sleepq_wait_sig+0xf _sleep+0x27d umtxq_sleep+0x125 do_sem_wait+0x4db __umtx_op_sem_wait+0x73 amd64_syscall+0x40f Xfast_syscall+0xfb > > 93931 102258 node V8 WorkerThread mi_switch+0xe1 sleepq_catch_signals+0xab sleepq_wait_sig+0xf _sleep+0x27d umtxq_sleep+0x125 do_sem_wait+0x4db __umtx_op_sem_wait+0x73 amd64_syscall+0x40f Xfast_syscall+0xfb > > 93931 102262 node V8 WorkerThread mi_switch+0xe1 sleepq_catch_signals+0xab sleepq_wait_sig+0xf _sleep+0x27d umtxq_sleep+0x125 do_sem_wait+0x4db __umtx_op_sem_wait+0x73 amd64_syscall+0x40f Xfast_syscall+0xfb > > 93931 102266 node V8 WorkerThread mi_switch+0xe1 sleepq_catch_signals+0xab sleepq_wait_sig+0xf _sleep+0x27d umtxq_sleep+0x125 do_sem_wait+0x4db __umtx_op_sem_wait+0x73 amd64_syscall+0x40f Xfast_syscall+0xfb > > 93931 102279 node - mi_switch+0xe1 sleepq_catch_signals+0xab sleepq_wait_sig+0xf _sleep+0x27d umtxq_sleep+0x125 do_wait+0x387 __umtx_op_wait_uint_private+0x83 amd64_syscall+0x40f Xfast_syscall+0xfb > > 93931 102285 node - mi_switch+0xe1 sleepq_wait+0x3a sleeplk+0x15d __lockmgr_args+0xca0 vop_stdlock+0x3c VOP_LOCK1_APV+0xab _vn_lock+0x43 vputx+0x21f zfs_rename_unlock+0x3e zfs_freebsd_rename+0xe39 VOP_RENAME_APV+0xab kern_renameat+0x4a6 amd64_syscall+0x40f Xfast_syscall+0xfb > > 93931 102287 node - mi_switch+0xe1 sleepq_wait+0x3a sleeplk+0x15d __lockmgr_args+0x91a vop_stdlock+0x3c VOP_LOCK1_APV+0xab _vn_lock+0x43 zfs_lookup+0x45d zfs_freebsd_lookup+0x6d VOP_CACHEDLOOKUP_APV+0xa1 vfs_cache_lookup+0xd6 VOP_LOOKUP_APV+0xa1 lookup+0x5a1 namei+0x4d4 kern_renameat+0x1b7 amd64_syscall+0x40f Xfast_syscall+0xfb > > 93931 102294 node - mi_switch+0xe1 sleepq_wait+0x3a sleeplk+0x15d __lockmgr_args+0x91a vop_stdlock+0x3c VOP_LOCK1_APV+0xab _vn_lock+0x43 vget+0x73 cache_lookup+0x5d5 vfs_cache_lookup+0xac VOP_LOOKUP_APV+0xa1 lookup+0x5a1 namei+0x4d4 kern_renameat+0x1b7 amd64_syscall+0x40f Xfast_syscall+0xfb > > > > The specific directory that is causing this issue is: > > > > /usr/ports/www/npm/work/stage/usr/local/lib/node_modules/npm/node_modules/npmlog/node_modules/gauge > > > > Right now I'm running on a stock FreeBSD 10.3 release. > > > > FreeBSD oneeye 10.3-RELEASE-p4 FreeBSD 10.3-RELEASE-p4 #0: Sat May 28 12:23:44 UTC 2016 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 > > > > I'm going to guess that this deadlock will go away if I reboot this box, but > > I haven't rebooted yet. Since this isn't really impacting anything important > > that I'm doing, I can keep it up for a bit if someone wants me to gather some > > extra information to track down the root cause. > > > > It looks like your problem is similar to: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209158 > > If you read that PR and find your problem is similar, please add your > information to that post. > > > -- > Allan Jude > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" -- Ori Bernstein From owner-freebsd-hackers@freebsd.org Sun Jul 10 22:14:55 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 067F7B84EB5 for ; Sun, 10 Jul 2016 22:14:55 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from mx1.scaleengine.net (mx1.scaleengine.net [209.51.186.6]) (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 DE34C1592 for ; Sun, 10 Jul 2016 22:14:54 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [10.1.1.2] (unknown [10.1.1.2]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 9C7751397 for ; Sun, 10 Jul 2016 22:14:53 +0000 (UTC) Subject: Re: ZFS Deadlock: 'Directory of Death' To: freebsd-hackers@freebsd.org References: <20160710105442.3e566a9595ed70f2d29a0f1a@eigenstate.org> <8133e3d5-cfc8-5e6c-44cf-079b2e11d896@freebsd.org> <20160710113641.960c9b52e67ed09d6bb05e29@eigenstate.org> From: Allan Jude Message-ID: Date: Sun, 10 Jul 2016 18:14:52 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <20160710113641.960c9b52e67ed09d6bb05e29@eigenstate.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Jul 2016 22:14:55 -0000 On 2016-07-10 14:36, Ori Bernstein wrote: > Looks like it, down to very very similar stack traces. > > On Sun, 10 Jul 2016 14:07:28 -0400, Allan Jude wrote: > >> On 2016-07-10 13:54, Ori Bernstein wrote: >>> I've got a fun issue: There's a directory of death on my desktop running ZFS. >>> When installing ports, I Any program that tries to touch a directory in >>> /usr/ports hangs, deadlocked in the VFS cache lookup: >>> >>> $ sudo procstat -kk 94688 >>> PID TID COMM TDNAME KSTACK >>> 94688 102697 fuser - mi_switch+0xe1 sleepq_wait+0x3a sleeplk+0x15d __lockmgr_args+0x91a vop_stdlock+0x3c VOP_LOCK1_APV+0xab _vn_lock+0x43 vget+0x73 cache_lookup+0x5d5 vfs_cache_lookup+0xac VOP_LOOKUP_APV+0xa1 lookup+0x5a1 namei+0x4d4 kern_statat_vnhook+0xae sys_stat+0x2d amd64_syscall+0x40f Xfast_syscall+0xfb >>> >>> >>> The process that seems to have triggered this was a port install of NPM, which seems to have >>> deadlocked while renaming some files: >>> >>> $ ps a 93931 >>> 93931 15- D 0:11.87 npm (node) >>> >>> $ sudo procstat -kk 93931 >>> PID TID COMM TDNAME KSTACK >>> 93931 101449 node - mi_switch+0xe1 sleepq_catch_signals+0xab sleepq_wait_sig+0xf _sleep+0x27d umtxq_sleep+0x125 do_sem_wait+0x4db __umtx_op_sem_wait+0x73 amd64_syscall+0x40f Xfast_syscall+0xfb >>> 93931 101977 node - mi_switch+0xe1 sleepq_catch_signals+0xab sleepq_wait_sig+0xf _sleep+0x27d kern_kevent_fp+0x399 kern_kevent+0x9f sys_kevent+0x12a amd64_syscall+0x40f Xfast_syscall+0xfb >>> 93931 102252 node V8 WorkerThread mi_switch+0xe1 sleepq_catch_signals+0xab sleepq_wait_sig+0xf _sleep+0x27d umtxq_sleep+0x125 do_sem_wait+0x4db __umtx_op_sem_wait+0x73 amd64_syscall+0x40f Xfast_syscall+0xfb >>> 93931 102258 node V8 WorkerThread mi_switch+0xe1 sleepq_catch_signals+0xab sleepq_wait_sig+0xf _sleep+0x27d umtxq_sleep+0x125 do_sem_wait+0x4db __umtx_op_sem_wait+0x73 amd64_syscall+0x40f Xfast_syscall+0xfb >>> 93931 102262 node V8 WorkerThread mi_switch+0xe1 sleepq_catch_signals+0xab sleepq_wait_sig+0xf _sleep+0x27d umtxq_sleep+0x125 do_sem_wait+0x4db __umtx_op_sem_wait+0x73 amd64_syscall+0x40f Xfast_syscall+0xfb >>> 93931 102266 node V8 WorkerThread mi_switch+0xe1 sleepq_catch_signals+0xab sleepq_wait_sig+0xf _sleep+0x27d umtxq_sleep+0x125 do_sem_wait+0x4db __umtx_op_sem_wait+0x73 amd64_syscall+0x40f Xfast_syscall+0xfb >>> 93931 102279 node - mi_switch+0xe1 sleepq_catch_signals+0xab sleepq_wait_sig+0xf _sleep+0x27d umtxq_sleep+0x125 do_wait+0x387 __umtx_op_wait_uint_private+0x83 amd64_syscall+0x40f Xfast_syscall+0xfb >>> 93931 102285 node - mi_switch+0xe1 sleepq_wait+0x3a sleeplk+0x15d __lockmgr_args+0xca0 vop_stdlock+0x3c VOP_LOCK1_APV+0xab _vn_lock+0x43 vputx+0x21f zfs_rename_unlock+0x3e zfs_freebsd_rename+0xe39 VOP_RENAME_APV+0xab kern_renameat+0x4a6 amd64_syscall+0x40f Xfast_syscall+0xfb >>> 93931 102287 node - mi_switch+0xe1 sleepq_wait+0x3a sleeplk+0x15d __lockmgr_args+0x91a vop_stdlock+0x3c VOP_LOCK1_APV+0xab _vn_lock+0x43 zfs_lookup+0x45d zfs_freebsd_lookup+0x6d VOP_CACHEDLOOKUP_APV+0xa1 vfs_cache_lookup+0xd6 VOP_LOOKUP_APV+0xa1 lookup+0x5a1 namei+0x4d4 kern_renameat+0x1b7 amd64_syscall+0x40f Xfast_syscall+0xfb >>> 93931 102294 node - mi_switch+0xe1 sleepq_wait+0x3a sleeplk+0x15d __lockmgr_args+0x91a vop_stdlock+0x3c VOP_LOCK1_APV+0xab _vn_lock+0x43 vget+0x73 cache_lookup+0x5d5 vfs_cache_lookup+0xac VOP_LOOKUP_APV+0xa1 lookup+0x5a1 namei+0x4d4 kern_renameat+0x1b7 amd64_syscall+0x40f Xfast_syscall+0xfb >>> >>> The specific directory that is causing this issue is: >>> >>> /usr/ports/www/npm/work/stage/usr/local/lib/node_modules/npm/node_modules/npmlog/node_modules/gauge >>> >>> Right now I'm running on a stock FreeBSD 10.3 release. >>> >>> FreeBSD oneeye 10.3-RELEASE-p4 FreeBSD 10.3-RELEASE-p4 #0: Sat May 28 12:23:44 UTC 2016 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 >>> >>> I'm going to guess that this deadlock will go away if I reboot this box, but >>> I haven't rebooted yet. Since this isn't really impacting anything important >>> that I'm doing, I can keep it up for a bit if someone wants me to gather some >>> extra information to track down the root cause. >>> >> >> It looks like your problem is similar to: >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209158 >> >> If you read that PR and find your problem is similar, please add your >> information to that post. >> >> >> -- >> Allan Jude >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > > There is a patch in that PR that might be worth trying if you have the ability to experiment a bit with it. -- Allan Jude From owner-freebsd-hackers@freebsd.org Mon Jul 11 08:31:17 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C9FC8B91642 for ; Mon, 11 Jul 2016 08:31:17 +0000 (UTC) (envelope-from ori@eigenstate.org) Received: from mimir.eigenstate.org (mimir.eigenstate.org [206.124.132.107]) by mx1.freebsd.org (Postfix) with ESMTP id B5C6F1D31 for ; Mon, 11 Jul 2016 08:31:17 +0000 (UTC) (envelope-from ori@eigenstate.org) Received: from oneeye (unknown [98.207.157.125]) by mimir.eigenstate.org (Postfix) with ESMTPSA id A1547600C9 for ; Mon, 11 Jul 2016 04:31:16 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eigenstate.org; s=mail; t=1468225876; bh=OgH0f5UKAlR+FWdXPZSlgSbT1vyLsSdRpMZeMdoh6s8=; h=Date:From:Cc:Subject:In-Reply-To:References; b=mm2+9IEt4MaJXBovW5xjNX3FN/+uS6eP1WtVb8UA9XffARqK/ebtRxIwRio0zqeEe eIRNeBCLcsFagff+tS2uvGHPThf0GZ6Dx9ZwcHbni4ATTYa51yTvBTt+dcq758WEVm KpMhJeSmf4qu6WLS9im5suTrFjsuvgSz1sweqfD0= Date: Mon, 11 Jul 2016 01:31:15 -0700 From: Ori Bernstein Cc: freebsd-hackers@freebsd.org Subject: Re: ZFS Deadlock: 'Directory of Death' Message-Id: <20160711013115.c408cae424b7e18498e10b69@eigenstate.org> In-Reply-To: References: <20160710105442.3e566a9595ed70f2d29a0f1a@eigenstate.org> <8133e3d5-cfc8-5e6c-44cf-079b2e11d896@freebsd.org> <20160710113641.960c9b52e67ed09d6bb05e29@eigenstate.org> X-Mailer: Sylpheed 3.5.0 (GTK+ 2.24.29; amd64-portbld-freebsd10.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jul 2016 08:31:17 -0000 On Sun, 10 Jul 2016 18:14:52 -0400, Allan Jude wrote: > On 2016-07-10 14:36, Ori Bernstein wrote: > >> > >> It looks like your problem is similar to: > >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209158 > >> > >> If you read that PR and find your problem is similar, please add your > >> information to that post. > > > Looks like it, down to very very similar stack traces. > > > > On Sun, 10 Jul 2016 14:07:28 -0400, Allan Jude wrote: > > > There is a patch in that PR that might be worth trying if you have the > ability to experiment a bit with it. Going to take a shot at seeing if I can reproduce it reliably tomorrow, and then see if D6533 solves my issue. -- Ori Bernstein From owner-freebsd-hackers@freebsd.org Mon Jul 11 16:55:15 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8E44EB922DB for ; Mon, 11 Jul 2016 16:55:15 +0000 (UTC) (envelope-from ruben@rubenkerkhof.com) Received: from mail-oi0-x229.google.com (mail-oi0-x229.google.com [IPv6:2607:f8b0:4003:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5785619B0 for ; Mon, 11 Jul 2016 16:55:15 +0000 (UTC) (envelope-from ruben@rubenkerkhof.com) Received: by mail-oi0-x229.google.com with SMTP id w18so13266010oiw.3 for ; Mon, 11 Jul 2016 09:55:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rubenkerkhof.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ope61lr6SV5UX0Vx97cufyn7bHT23kNKjZPNM6blS2w=; b=lTa8WF9wkO7lqc8DyjkVo17bBXylBAz0kKfCNx73kEjCoa7f3lRvBCmNTgURCwNChw RUJD9GaOWnkYhJZ1+PvZVlgXTiQ6AItUGz9geaXkU4sc1WmeOW5t+zx+ZDneaq/R1ibr 4HFMTy+/Hl4DEzLU1y50KRHjKT1RzvWwHJbWY= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ope61lr6SV5UX0Vx97cufyn7bHT23kNKjZPNM6blS2w=; b=AwKF0065mAZk46b+sY6gKQLR2nvoh8J3M5fSKEZo02tD8dpYlBgKVPD8+eo+Pcm8y7 +HVAsdjLuDFcJSkUhLbKwN6mQdyMD4+NFLJYQnl9e8atO1TymvikDog5WwqxFta90qwV JnxILOjX1sgnt1Q5gtJAkD4ltauog5ZDpCNuO9rwObSh3wMOQGkMksZ2How6m91ewBb2 MuRK7ywLw7ZORPzp3WpLdpppcarePIL4pqViKp6pE455QpCjtgef0IgxruyUtTy9248C OniEzmGaH1fDjZczywpxhRnQlpC0WoJews5c1F1jSLTXAFGIxqvSXOfphUaBdfusT1MF bDVg== X-Gm-Message-State: ALyK8tK625hfM4zW4x5kZj+ar8qRry0L6ro30yIvIfo1I2UxPg7p8K8uw2LuXBoRmqOrfahA7SGclk8JjfM/Fg== X-Received: by 10.202.107.210 with SMTP id g201mr10122089oic.155.1468256114417; Mon, 11 Jul 2016 09:55:14 -0700 (PDT) MIME-Version: 1.0 Received: by 10.157.51.38 with HTTP; Mon, 11 Jul 2016 09:54:54 -0700 (PDT) In-Reply-To: <4dc72d13-bdbf-3947-0564-4e8553475b17@denninger.net> References: <4dc72d13-bdbf-3947-0564-4e8553475b17@denninger.net> From: Ruben Kerkhof Date: Mon, 11 Jul 2016 18:54:54 +0200 Message-ID: Subject: Re: 11-Beta1 problem with virtual KVM To: Karl Denninger Cc: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jul 2016 16:55:15 -0000 Dear Karl, On Sun, Jul 10, 2016 at 3:24 AM, Karl Denninger wrote: > It looks like the VGA "synthetic" adapter that the system is outputting > on for the console now has one extra scan line. > > This results in the last line being half cut-off on my java-based > KVM.... very annoying and it makes it extremely difficult to work on the > system via it. > > This was *not* a problem with 10.x; it's a new issue for 11. > > Ideas to fix? Setting rows does not do it. FWIW, I'm seeing the same on various Supermicro KVMs. This is indeed very annoying since it hides the prompt. I've been planning to open an issue in BZ but haven't had the time yet. Kind regards, Ruben Kerkhof From owner-freebsd-hackers@freebsd.org Mon Jul 11 17:13:05 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9939BB92A49 for ; Mon, 11 Jul 2016 17:13:05 +0000 (UTC) (envelope-from karl@denninger.net) Received: from mail.denninger.net (denninger.net [70.169.168.7]) (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 6D06A1DD0 for ; Mon, 11 Jul 2016 17:13:05 +0000 (UTC) (envelope-from karl@denninger.net) Received: from [192.168.1.40] (Karl-Desktop.Denninger.net [192.168.1.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.denninger.net (Postfix) with ESMTPSA id 22EC33A78F5 for ; Mon, 11 Jul 2016 12:13:02 -0500 (CDT) Subject: Re: 11-Beta1 problem with virtual KVM To: freebsd-hackers@freebsd.org References: <4dc72d13-bdbf-3947-0564-4e8553475b17@denninger.net> From: Karl Denninger Message-ID: <4e137b8a-4dd4-10c9-7843-83452c217a70@denninger.net> Date: Mon, 11 Jul 2016 12:12:36 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-512; boundary="------------ms040600010401050104090903" X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jul 2016 17:13:05 -0000 This is a cryptographically signed message in MIME format. --------------ms040600010401050104090903 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 7/11/2016 11:54, Ruben Kerkhof wrote: > Dear Karl, > > On Sun, Jul 10, 2016 at 3:24 AM, Karl Denninger wr= ote: >> It looks like the VGA "synthetic" adapter that the system is outputtin= g >> on for the console now has one extra scan line. >> >> This results in the last line being half cut-off on my java-based >> KVM.... very annoying and it makes it extremely difficult to work on t= he >> system via it. >> >> This was *not* a problem with 10.x; it's a new issue for 11. >> >> Ideas to fix? Setting rows does not do it. > FWIW, I'm seeing the same on various Supermicro KVMs. > This is indeed very annoying since it hides the prompt. > > I've been planning to open an issue in BZ but haven't had the time yet.= > It also impacts a real monitor; I had to resize the screen that I had used on one of my test machines for quite some time. It appears they changed the scan line count or something similar in the driver. --=20 Karl Denninger karl@denninger.net /The Market Ticker/ /[S/MIME encrypted email preferred]/ --------------ms040600010401050104090903 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgMFADCABgkqhkiG9w0BBwEAAKCC Bl8wggZbMIIEQ6ADAgECAgEpMA0GCSqGSIb3DQEBCwUAMIGQMQswCQYDVQQGEwJVUzEQMA4G A1UECBMHRmxvcmlkYTESMBAGA1UEBxMJTmljZXZpbGxlMRkwFwYDVQQKExBDdWRhIFN5c3Rl bXMgTExDMRwwGgYDVQQDExNDdWRhIFN5c3RlbXMgTExDIENBMSIwIAYJKoZIhvcNAQkBFhND dWRhIFN5c3RlbXMgTExDIENBMB4XDTE1MDQyMTAyMjE1OVoXDTIwMDQxOTAyMjE1OVowWjEL MAkGA1UEBhMCVVMxEDAOBgNVBAgTB0Zsb3JpZGExGTAXBgNVBAoTEEN1ZGEgU3lzdGVtcyBM TEMxHjAcBgNVBAMTFUthcmwgRGVubmluZ2VyIChPQ1NQKTCCAiIwDQYJKoZIhvcNAQEBBQAD ggIPADCCAgoCggIBALmEWPhAdphrWd4K5VTvE5pxL3blRQPyGF3ApjUjgtavqU1Y8pbI3Byg XDj2/Uz9Si8XVj/kNbKEjkRh5SsNvx3Fc0oQ1uVjyCq7zC/kctF7yLzQbvWnU4grAPZ3IuAp 3/fFxIVaXpxEdKmyZAVDhk9az+IgHH43rdJRIMzxJ5vqQMb+n2EjadVqiGPbtG9aZEImlq7f IYDTnKyToi23PAnkPwwT+q1IkI2DTvf2jzWrhLR5DTX0fUYC0nxlHWbjgpiapyJWtR7K2YQO aevQb/3vN9gSojT2h+cBem7QIj6U69rEYcEDvPyCMXEV9VcXdcmW42LSRsPvZcBHFkWAJqMZ Myiz4kumaP+s+cIDaXitR/szoqDKGSHM4CPAZV9Yh8asvxQL5uDxz5wvLPgS5yS8K/o7zDR5 vNkMCyfYQuR6PAJxVOk5Arqvj9lfP3JSVapwbr01CoWDBkpuJlKfpQIEeC/pcCBKknllbMYq yHBO2TipLyO5Ocd1nhN/nOsO+C+j31lQHfOMRZaPQykXVPWG5BbhWT7ttX4vy5hOW6yJgeT/ o3apynlp1cEavkQRS8uJHoQszF6KIrQMID/JfySWvVQ4ksnfzwB2lRomrdrwnQ4eG/HBS+0l eozwOJNDIBlAP+hLe8A5oWZgooIIK/SulUAsfI6Sgd8dTZTTYmlhAgMBAAGjgfQwgfEwNwYI KwYBBQUHAQEEKzApMCcGCCsGAQUFBzABhhtodHRwOi8vY3VkYXN5c3RlbXMubmV0Ojg4ODgw CQYDVR0TBAIwADARBglghkgBhvhCAQEEBAMCBaAwCwYDVR0PBAQDAgXgMCwGCWCGSAGG+EIB DQQfFh1PcGVuU1NMIEdlbmVyYXRlZCBDZXJ0aWZpY2F0ZTAdBgNVHQ4EFgQUxRyULenJaFwX RtT79aNmIB/u5VkwHwYDVR0jBBgwFoAUJHGbnYV9/N3dvbDKkpQDofrTbTUwHQYDVR0RBBYw FIESa2FybEBkZW5uaW5nZXIubmV0MA0GCSqGSIb3DQEBCwUAA4ICAQBPf3cYtmKowmGIYsm6 eBinJu7QVWvxi1vqnBz3KE+HapqoIZS8/PolB/hwiY0UAE1RsjBJ7yEjihVRwummSBvkoOyf G30uPn4yg4vbJkR9lTz8d21fPshWETa6DBh2jx2Qf13LZpr3Pj2fTtlu6xMYKzg7cSDgd2bO sJGH/rcvva9Spkx5Vfq0RyOrYph9boshRN3D4tbWgBAcX9POdXCVfJONDxhfBuPHsJ6vEmPb An+XL5Yl26XYFPiODQ+Qbk44Ot1kt9s7oS3dVUrh92Qv0G3J3DF+Vt6C15nED+f+bk4gScu+ JHT7RjEmfa18GT8DcT//D1zEke1Ymhb41JH+GyZchDRWtjxsS5OBFMzrju7d264zJUFtX7iJ 3xvpKN7VcZKNtB6dLShj3v/XDsQVQWXmR/1YKWZ93C3LpRs2Y5nYdn6gEOpL/WfQFThtfnat HNc7fNs5vjotaYpBl5H8+VCautKbGOs219uQbhGZLYTv6okuKcY8W+4EJEtK0xB08vqr9Jd0 FS9MGjQE++GWo+5eQxFt6nUENHbVYnsr6bYPQsZH0CRNycgTG9MwY/UIXOf4W034UpR82TBG 1LiMsYfb8ahQJhs3wdf1nzipIjRwoZKT1vGXh/cj3gwSr64GfenURBxaFZA5O1acOZUjPrRT n3ci4McYW/0WVVA3lDGCBRMwggUPAgEBMIGWMIGQMQswCQYDVQQGEwJVUzEQMA4GA1UECBMH RmxvcmlkYTESMBAGA1UEBxMJTmljZXZpbGxlMRkwFwYDVQQKExBDdWRhIFN5c3RlbXMgTExD MRwwGgYDVQQDExNDdWRhIFN5c3RlbXMgTExDIENBMSIwIAYJKoZIhvcNAQkBFhNDdWRhIFN5 c3RlbXMgTExDIENBAgEpMA0GCWCGSAFlAwQCAwUAoIICTTAYBgkqhkiG9w0BCQMxCwYJKoZI hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNjA3MTExNzEyMzZaME8GCSqGSIb3DQEJBDFCBECa iGord5z0c5bDGaTw/czxX2RbJRNHA30PgZ2L0x29ZJhqGHFDKqHeWKe06b034GW1D0/vTKTk xkRNozafJJ+fMGwGCSqGSIb3DQEJDzFfMF0wCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBAjAK BggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYI KoZIhvcNAwICASgwgacGCSsGAQQBgjcQBDGBmTCBljCBkDELMAkGA1UEBhMCVVMxEDAOBgNV BAgTB0Zsb3JpZGExEjAQBgNVBAcTCU5pY2V2aWxsZTEZMBcGA1UEChMQQ3VkYSBTeXN0ZW1z IExMQzEcMBoGA1UEAxMTQ3VkYSBTeXN0ZW1zIExMQyBDQTEiMCAGCSqGSIb3DQEJARYTQ3Vk YSBTeXN0ZW1zIExMQyBDQQIBKTCBqQYLKoZIhvcNAQkQAgsxgZmggZYwgZAxCzAJBgNVBAYT AlVTMRAwDgYDVQQIEwdGbG9yaWRhMRIwEAYDVQQHEwlOaWNldmlsbGUxGTAXBgNVBAoTEEN1 ZGEgU3lzdGVtcyBMTEMxHDAaBgNVBAMTE0N1ZGEgU3lzdGVtcyBMTEMgQ0ExIjAgBgkqhkiG 9w0BCQEWE0N1ZGEgU3lzdGVtcyBMTEMgQ0ECASkwDQYJKoZIhvcNAQEBBQAEggIAZ3quNm4s F6Zlx0Oj0zT/NSSFgcjgFkw0ad/w8Papp0XNdLa3nV5BkscBQjfbdZ7un10LzakHF4nA89iy MsZszku4Zx6kWXpjK3ZPjJ7G+Yt/R5Pvn5Z/sEZ+dNrjrU7wQ0y67u/68Tum9U5xa0HkZkhF bo2z0f5cgYKo99LQl/Xboysq1ZzZehd8S9fnIHsVr2HigDpvYfWR8nGFQOp/5yqBLKz7HCzn yog0Wr2lkQWEkG0SWXasONaJ9k1P6mlzcA3VSF2ZeSqKm7f7crcBM/B6X7Vfr4mBlJapsRgq V2pvxtJ4mWms+/EJgTb0tPIeuo1+WSNm30Pg4LZtfF5vJijxScaW904TskeWnvJKzPXKULU6 LfR8SUVvsr4H9tE2TykpAQdlgNqlJEJMfnD6Prp5iExlnj0ryqj230hvu3JEOT0WlBuHolPy NnrmlgcvIyB8CP1/RDAx3bASI3Y21s8GOh/rhuzFj4B67Rncqv5gzp0yx77pIQYRyZR3+IUj mpmNS7DspQ77/u3NXefn1RiiVdmfTCzlf5lIuUC/EHu7h69yZNYQNv3H8LHodzB0c9SpM30r /5CrAuYtvIw5lt3APXkbP176zH77eKYBpED92tPafUqhygnCqp2ZDeXskU/x0p864mpnHMPk dVUBv/AdBKLcxWt8Y6snQ0+GjtEAAAAAAAA= --------------ms040600010401050104090903-- From owner-freebsd-hackers@freebsd.org Mon Jul 11 17:22:20 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A1A86B92CDF for ; Mon, 11 Jul 2016 17:22:20 +0000 (UTC) (envelope-from vangyzen@FreeBSD.org) Received: from smtp.vangyzen.net (hotblack.vangyzen.net [IPv6:2607:fc50:1000:7400:216:3eff:fe72:314f]) by mx1.freebsd.org (Postfix) with ESMTP id 8C97C13E3 for ; Mon, 11 Jul 2016 17:22:20 +0000 (UTC) (envelope-from vangyzen@FreeBSD.org) Received: from sweettea.beer.town (unknown [76.164.8.130]) by smtp.vangyzen.net (Postfix) with ESMTPSA id ABE815648C; Mon, 11 Jul 2016 12:22:19 -0500 (CDT) Subject: Re: 11-Beta1 problem with virtual KVM To: Karl Denninger , freebsd-hackers@freebsd.org References: <4dc72d13-bdbf-3947-0564-4e8553475b17@denninger.net> <4e137b8a-4dd4-10c9-7843-83452c217a70@denninger.net> From: Eric van Gyzen Message-ID: Date: Mon, 11 Jul 2016 12:22:16 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: <4e137b8a-4dd4-10c9-7843-83452c217a70@denninger.net> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jul 2016 17:22:20 -0000 On 07/11/16 12:12 PM, Karl Denninger wrote: > On 7/11/2016 11:54, Ruben Kerkhof wrote: >> Dear Karl, >> >> On Sun, Jul 10, 2016 at 3:24 AM, Karl Denninger wrote: >>> It looks like the VGA "synthetic" adapter that the system is outputting >>> on for the console now has one extra scan line. >>> >>> This results in the last line being half cut-off on my java-based >>> KVM.... very annoying and it makes it extremely difficult to work on the >>> system via it. >>> >>> This was *not* a problem with 10.x; it's a new issue for 11. >>> >>> Ideas to fix? Setting rows does not do it. >> FWIW, I'm seeing the same on various Supermicro KVMs. >> This is indeed very annoying since it hides the prompt. >> >> I've been planning to open an issue in BZ but haven't had the time yet. >> > It also impacts a real monitor; I had to resize the screen that I had > used on one of my test machines for quite some time. It appears they > changed the scan line count or something similar in the driver. You might try adding this to /boot/loader.conf and rebooting: kern.vty="sc" That will at least narrow down the problem to the new vt(4). Eric From owner-freebsd-hackers@freebsd.org Mon Jul 11 17:35:33 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D11C7B924CB for ; Mon, 11 Jul 2016 17:35:33 +0000 (UTC) (envelope-from karl@denninger.net) Received: from mail.denninger.net (denninger.net [70.169.168.7]) (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 8B67012C3 for ; Mon, 11 Jul 2016 17:35:33 +0000 (UTC) (envelope-from karl@denninger.net) Received: from [192.168.1.40] (Karl-Desktop.Denninger.net [192.168.1.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.denninger.net (Postfix) with ESMTPSA id 8F14B3A7A4D for ; Mon, 11 Jul 2016 12:35:31 -0500 (CDT) Subject: Re: 11-Beta1 problem with virtual KVM To: freebsd-hackers@freebsd.org References: <4dc72d13-bdbf-3947-0564-4e8553475b17@denninger.net> <4e137b8a-4dd4-10c9-7843-83452c217a70@denninger.net> From: Karl Denninger Message-ID: <27ab24b9-ef8c-0ce5-c70b-d7fe3a201946@denninger.net> Date: Mon, 11 Jul 2016 12:35:06 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-512; boundary="------------ms080601040005050503030604" X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jul 2016 17:35:33 -0000 This is a cryptographically signed message in MIME format. --------------ms080601040005050503030604 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 7/11/2016 12:22, Eric van Gyzen wrote: > On 07/11/16 12:12 PM, Karl Denninger wrote: >> On 7/11/2016 11:54, Ruben Kerkhof wrote: >>> Dear Karl, >>> >>> On Sun, Jul 10, 2016 at 3:24 AM, Karl Denninger = wrote: >>>> It looks like the VGA "synthetic" adapter that the system is outputt= ing >>>> on for the console now has one extra scan line. >>>> >>>> This results in the last line being half cut-off on my java-based >>>> KVM.... very annoying and it makes it extremely difficult to work on= the >>>> system via it. >>>> >>>> This was *not* a problem with 10.x; it's a new issue for 11. >>>> >>>> Ideas to fix? Setting rows does not do it. >>> FWIW, I'm seeing the same on various Supermicro KVMs. >>> This is indeed very annoying since it hides the prompt. >>> >>> I've been planning to open an issue in BZ but haven't had the time ye= t. >>> >> It also impacts a real monitor; I had to resize the screen that I had >> used on one of my test machines for quite some time. It appears they >> changed the scan line count or something similar in the driver. > You might try adding this to /boot/loader.conf and rebooting: > > kern.vty=3D"sc" > > That will at least narrow down the problem to the new vt(4). kern.vty=3D"sc" returns me to a reasonable console that works properly over the KVM. Looks like the "new" vt has problems.... this will bite (at least) anyone with a SuperMicro IPMI/KVM and there's a lot of those out there...= --=20 Karl Denninger karl@denninger.net /The Market Ticker/ /[S/MIME encrypted email preferred]/ --------------ms080601040005050503030604 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgMFADCABgkqhkiG9w0BBwEAAKCC Bl8wggZbMIIEQ6ADAgECAgEpMA0GCSqGSIb3DQEBCwUAMIGQMQswCQYDVQQGEwJVUzEQMA4G A1UECBMHRmxvcmlkYTESMBAGA1UEBxMJTmljZXZpbGxlMRkwFwYDVQQKExBDdWRhIFN5c3Rl bXMgTExDMRwwGgYDVQQDExNDdWRhIFN5c3RlbXMgTExDIENBMSIwIAYJKoZIhvcNAQkBFhND dWRhIFN5c3RlbXMgTExDIENBMB4XDTE1MDQyMTAyMjE1OVoXDTIwMDQxOTAyMjE1OVowWjEL MAkGA1UEBhMCVVMxEDAOBgNVBAgTB0Zsb3JpZGExGTAXBgNVBAoTEEN1ZGEgU3lzdGVtcyBM TEMxHjAcBgNVBAMTFUthcmwgRGVubmluZ2VyIChPQ1NQKTCCAiIwDQYJKoZIhvcNAQEBBQAD ggIPADCCAgoCggIBALmEWPhAdphrWd4K5VTvE5pxL3blRQPyGF3ApjUjgtavqU1Y8pbI3Byg XDj2/Uz9Si8XVj/kNbKEjkRh5SsNvx3Fc0oQ1uVjyCq7zC/kctF7yLzQbvWnU4grAPZ3IuAp 3/fFxIVaXpxEdKmyZAVDhk9az+IgHH43rdJRIMzxJ5vqQMb+n2EjadVqiGPbtG9aZEImlq7f IYDTnKyToi23PAnkPwwT+q1IkI2DTvf2jzWrhLR5DTX0fUYC0nxlHWbjgpiapyJWtR7K2YQO aevQb/3vN9gSojT2h+cBem7QIj6U69rEYcEDvPyCMXEV9VcXdcmW42LSRsPvZcBHFkWAJqMZ Myiz4kumaP+s+cIDaXitR/szoqDKGSHM4CPAZV9Yh8asvxQL5uDxz5wvLPgS5yS8K/o7zDR5 vNkMCyfYQuR6PAJxVOk5Arqvj9lfP3JSVapwbr01CoWDBkpuJlKfpQIEeC/pcCBKknllbMYq yHBO2TipLyO5Ocd1nhN/nOsO+C+j31lQHfOMRZaPQykXVPWG5BbhWT7ttX4vy5hOW6yJgeT/ o3apynlp1cEavkQRS8uJHoQszF6KIrQMID/JfySWvVQ4ksnfzwB2lRomrdrwnQ4eG/HBS+0l eozwOJNDIBlAP+hLe8A5oWZgooIIK/SulUAsfI6Sgd8dTZTTYmlhAgMBAAGjgfQwgfEwNwYI KwYBBQUHAQEEKzApMCcGCCsGAQUFBzABhhtodHRwOi8vY3VkYXN5c3RlbXMubmV0Ojg4ODgw CQYDVR0TBAIwADARBglghkgBhvhCAQEEBAMCBaAwCwYDVR0PBAQDAgXgMCwGCWCGSAGG+EIB DQQfFh1PcGVuU1NMIEdlbmVyYXRlZCBDZXJ0aWZpY2F0ZTAdBgNVHQ4EFgQUxRyULenJaFwX RtT79aNmIB/u5VkwHwYDVR0jBBgwFoAUJHGbnYV9/N3dvbDKkpQDofrTbTUwHQYDVR0RBBYw FIESa2FybEBkZW5uaW5nZXIubmV0MA0GCSqGSIb3DQEBCwUAA4ICAQBPf3cYtmKowmGIYsm6 eBinJu7QVWvxi1vqnBz3KE+HapqoIZS8/PolB/hwiY0UAE1RsjBJ7yEjihVRwummSBvkoOyf G30uPn4yg4vbJkR9lTz8d21fPshWETa6DBh2jx2Qf13LZpr3Pj2fTtlu6xMYKzg7cSDgd2bO sJGH/rcvva9Spkx5Vfq0RyOrYph9boshRN3D4tbWgBAcX9POdXCVfJONDxhfBuPHsJ6vEmPb An+XL5Yl26XYFPiODQ+Qbk44Ot1kt9s7oS3dVUrh92Qv0G3J3DF+Vt6C15nED+f+bk4gScu+ JHT7RjEmfa18GT8DcT//D1zEke1Ymhb41JH+GyZchDRWtjxsS5OBFMzrju7d264zJUFtX7iJ 3xvpKN7VcZKNtB6dLShj3v/XDsQVQWXmR/1YKWZ93C3LpRs2Y5nYdn6gEOpL/WfQFThtfnat HNc7fNs5vjotaYpBl5H8+VCautKbGOs219uQbhGZLYTv6okuKcY8W+4EJEtK0xB08vqr9Jd0 FS9MGjQE++GWo+5eQxFt6nUENHbVYnsr6bYPQsZH0CRNycgTG9MwY/UIXOf4W034UpR82TBG 1LiMsYfb8ahQJhs3wdf1nzipIjRwoZKT1vGXh/cj3gwSr64GfenURBxaFZA5O1acOZUjPrRT n3ci4McYW/0WVVA3lDGCBRMwggUPAgEBMIGWMIGQMQswCQYDVQQGEwJVUzEQMA4GA1UECBMH RmxvcmlkYTESMBAGA1UEBxMJTmljZXZpbGxlMRkwFwYDVQQKExBDdWRhIFN5c3RlbXMgTExD MRwwGgYDVQQDExNDdWRhIFN5c3RlbXMgTExDIENBMSIwIAYJKoZIhvcNAQkBFhNDdWRhIFN5 c3RlbXMgTExDIENBAgEpMA0GCWCGSAFlAwQCAwUAoIICTTAYBgkqhkiG9w0BCQMxCwYJKoZI hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNjA3MTExNzM1MDZaME8GCSqGSIb3DQEJBDFCBEA+ kh9t8HqV9NdOreumkB/VXqW5MWQKrgjlIU6HZztxtB4a/QAUJMeLGGKEGxXm++NSLeoG8qKc +wrBiIytl8gJMGwGCSqGSIb3DQEJDzFfMF0wCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBAjAK BggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYI KoZIhvcNAwICASgwgacGCSsGAQQBgjcQBDGBmTCBljCBkDELMAkGA1UEBhMCVVMxEDAOBgNV BAgTB0Zsb3JpZGExEjAQBgNVBAcTCU5pY2V2aWxsZTEZMBcGA1UEChMQQ3VkYSBTeXN0ZW1z IExMQzEcMBoGA1UEAxMTQ3VkYSBTeXN0ZW1zIExMQyBDQTEiMCAGCSqGSIb3DQEJARYTQ3Vk YSBTeXN0ZW1zIExMQyBDQQIBKTCBqQYLKoZIhvcNAQkQAgsxgZmggZYwgZAxCzAJBgNVBAYT AlVTMRAwDgYDVQQIEwdGbG9yaWRhMRIwEAYDVQQHEwlOaWNldmlsbGUxGTAXBgNVBAoTEEN1 ZGEgU3lzdGVtcyBMTEMxHDAaBgNVBAMTE0N1ZGEgU3lzdGVtcyBMTEMgQ0ExIjAgBgkqhkiG 9w0BCQEWE0N1ZGEgU3lzdGVtcyBMTEMgQ0ECASkwDQYJKoZIhvcNAQEBBQAEggIAND0gn9PW VJ4gWAJIfDYxIttM9IpgTk4gZCJGeTC1WG42Ed6YALdKJNFaIM0eKrbVAO9EF+5e/s5MrJz0 yGlzVP2imCT4IV2FgHjK1ApjrLtr6LFwRf+2Z2mnTYye4BLGYpwIuF+XudsUF0vOgqi+zjKI akMVrD3CvvHP6Y3OG+6/VA3PZQ1i8nkCx7TQ4izLA+ecjx+ZwzNZGqi6Q3RldwXeg1hyHgi1 wv1xM67XTUkCg0Ktk5cB8H8vfXNMvzMS6xKQ1oW7fn8rEYUao+ZPyO3kO26tPmNpBoqYkKk9 RYuMUgHYvGI/76R1BKr11XcW+gG7sEitvvcZHYzyYBdVtY7Jn9AThFUjysIfDw1haHQor+tC hugcVXjcKzvfLORbNjmfHgG6UnbIwmozUTHvQNE1fdNhckZv9CDrcYkWAg8CrBULxVYHHTEh wl5+4FVaeh8PCIW5cDrH8x03sdQzfvfbtXveyZgJpQ12xTzGsSj0RfbcqobhBIpxRR4zwwEU LQIXjx3MkaNvnQ4I5Dr+hfWIAwLr5NKwP4XuFIwU8/G9wpxBwFBM7kvCTtBZRk9gmcakeUKU s36nLeeNK+d8SimpyVVpV9OmH1HYZ5/eNbDqvLzxOyFg8hOLj3PcytcmHDiWy4O0C5u/Zcoi rIQaXXe2gkqwiqW4HOpACFz15d8AAAAAAAA= --------------ms080601040005050503030604-- From owner-freebsd-hackers@freebsd.org Wed Jul 13 05:10:43 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DF8F3B971F0 for ; Wed, 13 Jul 2016 05:10:43 +0000 (UTC) (envelope-from wojtek@puchar.net) Received: from puchar.net (puchar.net [194.1.144.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "puchar.net", Issuer "puchar.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7405E1E08 for ; Wed, 13 Jul 2016 05:10:42 +0000 (UTC) (envelope-from wojtek@puchar.net) Received: Received: from 127.0.0.1 (localhost [127.0.0.1]) by puchar.net (8.15.2/8.14.9) with ESMTPS id u6D5AThu051527 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 13 Jul 2016 07:10:29 +0200 (CEST) (envelope-from wojtek@puchar.net) Received: from laptop.wojtek.intra (localhost [127.0.0.1]) by laptop.wojtek.intra (8.14.9/8.14.9) with ESMTP id u6D5APDS011007; Wed, 13 Jul 2016 07:10:25 +0200 (CEST) (envelope-from wojtek@puchar.net) Received: from localhost (wojtek@localhost) by laptop.wojtek.intra (8.14.9/8.14.9/Submit) with ESMTP id u6D5AJ0I011004; Wed, 13 Jul 2016 07:10:20 +0200 (CEST) (envelope-from wojtek@puchar.net) X-Authentication-Warning: laptop.wojtek.intra: wojtek owned process doing -bs Date: Wed, 13 Jul 2016 07:10:19 +0200 (CEST) From: Wojciech Puchar X-X-Sender: wojtek@laptop.wojtek.intra To: Karl Denninger cc: freebsd-hackers@freebsd.org Subject: Re: 11-Beta1 problem with virtual KVM In-Reply-To: <27ab24b9-ef8c-0ce5-c70b-d7fe3a201946@denninger.net> Message-ID: References: <4dc72d13-bdbf-3947-0564-4e8553475b17@denninger.net> <4e137b8a-4dd4-10c9-7843-83452c217a70@denninger.net> <27ab24b9-ef8c-0ce5-c70b-d7fe3a201946@denninger.net> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (puchar.net [10.0.1.1]); Wed, 13 Jul 2016 07:10:29 +0200 (CEST) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jul 2016 05:10:44 -0000 >> >> That will at least narrow down the problem to the new vt(4). > kern.vty="sc" returns me to a reasonable console that works properly > over the KVM. anyway - does it make any sense to use vt(4) on servers, where only text console is needed? From owner-freebsd-hackers@freebsd.org Wed Jul 13 06:05:06 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7116EB97FB3 for ; Wed, 13 Jul 2016 06:05:06 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from mx1.scaleengine.net (mx1.scaleengine.net [209.51.186.6]) (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 5311C1EBC for ; Wed, 13 Jul 2016 06:05:06 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [10.1.1.2] (unknown [10.1.1.2]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 31D99174D for ; Wed, 13 Jul 2016 06:04:59 +0000 (UTC) Subject: Re: 11-Beta1 problem with virtual KVM To: freebsd-hackers@freebsd.org References: <4dc72d13-bdbf-3947-0564-4e8553475b17@denninger.net> <4e137b8a-4dd4-10c9-7843-83452c217a70@denninger.net> <27ab24b9-ef8c-0ce5-c70b-d7fe3a201946@denninger.net> From: Allan Jude Message-ID: <373b3dac-fce8-f599-9d1c-cf65b5d0ebfd@freebsd.org> Date: Wed, 13 Jul 2016 02:04:58 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jul 2016 06:05:06 -0000 On 2016-07-13 01:10, Wojciech Puchar wrote: >>> >>> That will at least narrow down the problem to the new vt(4). >> kern.vty="sc" returns me to a reasonable console that works properly >> over the KVM. > anyway - does it make any sense to use vt(4) on servers, where only text > console is needed? > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" It is the default, and it should work. -- Allan Jude From owner-freebsd-hackers@freebsd.org Wed Jul 13 08:57:50 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 69A1AB97328 for ; Wed, 13 Jul 2016 08:57:50 +0000 (UTC) (envelope-from timp87@gmail.com) Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 15B5D138A for ; Wed, 13 Jul 2016 08:57:50 +0000 (UTC) (envelope-from timp87@gmail.com) Received: by mail-wm0-x234.google.com with SMTP id o80so58324514wme.1 for ; Wed, 13 Jul 2016 01:57:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=hEqao3+Z+EnTX1j8Mk4yLzL3MOK/JPKlBLF3IBZJQ+Q=; b=fCfYPNMU0QTgyQfXvMYnPStPnzYWi3k3rjw2n39iMtAXBe2c3RCy90uuIMyVay1VCe t50psmHGqNLtO4AoadHWZMaG0p4FQc8GvObSViT5qP4rgY9Mokq9EzF5qCuGUZHIrVRd J/gDY+rZCnazZiuMylGeYgVzbLZwzG+7BTiYFlkjx+ybF3gbIZqaALmVmtYnHF90Mxrj z3upjqEjCnXWN90oUgVMpvmkGmoQ7VrLWS7UlWKSTMk3GYbXNSgK6goNEgKfEHT8GQ8G 61RQPEDzpdB6GKuSlEnXAXYIak3j1VhQzP7LdNZQXTG9M+13PqWLRGyb3rbVkbUFv27i sfkw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=hEqao3+Z+EnTX1j8Mk4yLzL3MOK/JPKlBLF3IBZJQ+Q=; b=K3jyHS1kr2NOdmN9tze/w3T3k4kL25QKGh2L9hRRGRWBnSqlU0Tx/H7kKqhKLJJvqL iOKMpNL0YplvlbILAUt74nKkAwXr18sxX0Gkg8lIOgXrExxC1eEbkutRjhX5qCYnhJqB 3iwFSmIPutfo8LYk7L+Z0sqKBFmpGdyVzBJQM6AEX3BB90Lwg9J307NCbEc1mz4opbaS reWZ1c3Fdp4eQTn6Ufocst2VAr27sbRAjMsNdXsa7Ca/Uqxm1usoH2bBOePnWptjs20n wTBWd0YJqL/+VVO6YgA5841IzUgoQTbwq3AORMYuqBT9p4wmtktHYF61zYpmBI6erEYG NM/A== X-Gm-Message-State: ALyK8tLGZmNXYMR7BZxMbHBYr0oAAkvwWluyVjGmOA0EeQAXEcJSxssdXoOLrwejkV2o1RTxm5bqh3do+tkWuA== X-Received: by 10.28.92.80 with SMTP id q77mr5204271wmb.66.1468400268534; Wed, 13 Jul 2016 01:57:48 -0700 (PDT) MIME-Version: 1.0 Received: by 10.28.63.9 with HTTP; Wed, 13 Jul 2016 01:57:47 -0700 (PDT) In-Reply-To: <4dc72d13-bdbf-3947-0564-4e8553475b17@denninger.net> References: <4dc72d13-bdbf-3947-0564-4e8553475b17@denninger.net> From: Pavel Timofeev Date: Wed, 13 Jul 2016 11:57:47 +0300 Message-ID: Subject: Re: 11-Beta1 problem with virtual KVM To: Karl Denninger Cc: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jul 2016 08:57:50 -0000 2016-07-10 4:24 GMT+03:00 Karl Denninger : > It looks like the VGA "synthetic" adapter that the system is outputting > on for the console now has one extra scan line. > > This results in the last line being half cut-off on my java-based > KVM.... very annoying and it makes it extremely difficult to work on the > system via it. > > This was *not* a problem with 10.x; it's a new issue for 11. > > Ideas to fix? Setting rows does not do it. > > > -- > Karl Denninger > karl@denninger.net > /The Market Ticker/ > /[S/MIME encrypted email preferred]/ Hi! Have you tried to set vt(4) into the textmode? From owner-freebsd-hackers@freebsd.org Wed Jul 13 10:39:00 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5C3F6B97393; Wed, 13 Jul 2016 10:39:00 +0000 (UTC) (envelope-from shrikanth07@gmail.com) Received: from mail-oi0-x243.google.com (mail-oi0-x243.google.com [IPv6:2607:f8b0:4003:c06::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 24DEA1A22; Wed, 13 Jul 2016 10:39:00 +0000 (UTC) (envelope-from shrikanth07@gmail.com) Received: by mail-oi0-x243.google.com with SMTP id c199so3944315oig.1; Wed, 13 Jul 2016 03:39:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=bWChwR9es9dvNxIfy7Tttb3oZYqpc0oDXEkeFA0cpHY=; b=nDMp41pqTWVlQKt3tekoeWUFHesZT3vjHb/EkmiCuGy7javiB7VuCh42wZ68Tgt74Y aq7npJbavp4+06fimamJx4y98/jJBF49VqRnbQqpmwhZbjIR+x1F8R+gAXmGVB4+hOip 5wIAgE1sx/epSMexF4aRJ4+vcQ3GJofcVgn7wS2iC8GyUzgdTXJpuVO+P7LE1kSobOmO HtZh0pT3Iv+mKwXrSykH9HJ6VfUK3K7977iaOlmoCD448fACvokKyAYxiX1F6oviUaqH A3BlRnKgajTdTbvfN0fRKRPdNtXIzkfro5jkGXZq2sAae8Jmwk7/peurdVHGM2Id+iqa yHcQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=bWChwR9es9dvNxIfy7Tttb3oZYqpc0oDXEkeFA0cpHY=; b=PlattCT+DZdjO2RMQ2G7KOcRrBp0cSwNWdUIaXQXoh/FDirBvUFvXARUs0xVxpzMUd 1cQuadBgFq0tCIJ5sMmtgB5c8s4ox73L9psb3tlftA5TpWm6D8ZDo0jHLDO35p5Fac8p 9HGDKp5INQCwZ/7GQA/bC4ZawY3UWe0u+8VC3kZiyEdtyHtXsxmGLGkZ2PWJ4bnhdQsA kRifp4LcH5Ixd74sD3hx/NCXkvl2tjwHRyGaUTJEBleuRxKm9hWBbjfZLbmIwTUvr/nv GUvGAuO8DorxVKW9XwbI6ltsc0+kuEecjK7egMFJUSf5GHZzs8dirIgd+qz1gqTc1YZL NCmw== X-Gm-Message-State: ALyK8tICIJO8X22LjMUhWoIWFB8ZFTc4rUL8t8DZoOcia5e3hG33lv/ruHiTT31lkY0Gw11EiTCHGOQbAKvtrw== X-Received: by 10.202.74.9 with SMTP id x9mr732298oia.165.1468406339097; Wed, 13 Jul 2016 03:38:59 -0700 (PDT) MIME-Version: 1.0 Received: by 10.157.32.17 with HTTP; Wed, 13 Jul 2016 03:38:58 -0700 (PDT) From: Shrikanth Kamath Date: Wed, 13 Jul 2016 03:38:58 -0700 Message-ID: Subject: rogue module allocating 4G wired memory / pmap_growkernel does vm_page_alloc to get 4G wired To: freebsd-hackers@freebsd.org, freebsd-amd64@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jul 2016 10:39:00 -0000 I have this broadcom sdk module while getting loaded by a rc script calling kldload triggers a 4G jump in the wired memory (as shown by output of top) # top ... ... Mem: 77M Active, 644M Inact, 4473M Wired, 1600K Cache, 606M Buf, 2734M Free ... Upon using dtrace I get the responsible stack trace as this one which does most vm_page_alloc 0 10310 vm_page_alloc:entry kernel`pmap_growkernel+0x1cc kernel`vm_map_insert+0x3ee kernel`vm_map_find+0x14d kernel`link_elf_load_file+0x845 kernel`linker_load_module+0x6ec kernel`kern_kldload+0xab kernel`sys_kldload+0x84 kernel`amd64_syscall+0x3b6 kernel`0xffffffff805413a7 And the number of page allocations that happen in this context does also sum up to around 4G. It showed the total page allocations that happened in this context was vm_page_alloc 1045039 which is approx 3.99G. On probing a little deeper, the link_elf_load_file calls for vm_map_find with mapspace of 20MB. This results in a call to vm_map_findspace which I believe first checks if it can do a contiguous allocation within the kernel_map else it goes trying to map it beyond the kernel_map. Probing further we see that before the call to vm_map_find the kernel_vm_end is at the default value of kernbase at 0xffffffff80000000 The vm_map_findspace then picks the new start address to be 0xffffffff83d68000. The call to pmap_growkernel does grow the number of kernel page table entries to match the new end address i.e 0xffffffff85136000 and thereby kernel_vm_end is also adjusted to 0xffffffff85200000 from the initial default value of 0xffffffff80000000. Is my understanding correct here that vm_map_find is unable to allocate the 20MB mapspace requested in the kernel_map and hence calls pmap_growkernel thereby resulting in the wired memory increase? -- Shrikanth R K From owner-freebsd-hackers@freebsd.org Thu Jul 14 21:02:00 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B165BB9944B for ; Thu, 14 Jul 2016 21:02:00 +0000 (UTC) (envelope-from arlie@worldash.org) Received: from ansuz.worldash.org (ansuz.worldash.org [198.144.201.100]) by mx1.freebsd.org (Postfix) with ESMTP id 99C9D1161 for ; Thu, 14 Jul 2016 21:02:00 +0000 (UTC) (envelope-from arlie@worldash.org) Received: by ansuz.worldash.org (Postfix, from userid 1000) id 8706FE2E7B; Thu, 14 Jul 2016 14:04:48 -0700 (PDT) Date: Thu, 14 Jul 2016 14:04:48 -0700 From: Arlie Stephens To: freebsd-hackers@freebsd.org Subject: Zone Allocator Initialization Question Message-ID: <20160714210448.GA16971@worldash.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Jul 2016 21:02:00 -0000 Hi Folks, I'm chasing yet another kernel memory corruption in an obsolete version of FreeBSD (8.4 in this case). I expect that it will turn out to be a bug in some local customization, as they usually are. So I'm not looking for help with actually debugging it ;-) What I would like help with is understanding something my instrumentation is reporting, on systems that don't appear to have the problem. In brief, I'm seeing what appears to be uma_zalloc() returning a pointer to a virtual address that does not have PG_SLAB set on the vm_page_t for the corresponding physical page. Most allocations from that zone are fine; I only see one strange one, and that's fairly early in the system lifetime. (It's one of the "struct file" for files opened by init.) Is there some kind of bootstrap situation with the zone allocator, where certain early use zones get their first memory via a path that doesn't mark PG_SLAB? And if so, is there any other way to recognize those addresses as coming from a zone? (My corruption is scribbling on process' fd_ofiles[] arrays, so I'm trying to write a sanity checker, and was really surprised to find a valid-seeming struct file * that didn't appear to have come from the right place.) Thanks in advance for any enlightenment. -- Arlie (Arlie Stephens arlie@worldash.org) From owner-freebsd-hackers@freebsd.org Fri Jul 15 15:38:44 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E0056B9957F; Fri, 15 Jul 2016 15:38:44 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (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 9F5AB1989; Fri, 15 Jul 2016 15:38:44 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (envelope-from ) id <1bO5CG-0028UX-0D>; Fri, 15 Jul 2016 17:38:36 +0200 Received: from x5ce10071.dyn.telefonica.de ([92.225.0.113] helo=thor.walstatt.dynvpn.de) by inpost2.zedat.fu-berlin.de (Exim 4.85) with esmtpsa (TLSv1.2:AES256-GCM-SHA384:256) (envelope-from ) id <1bO5CF-001tgv-M9>; Fri, 15 Jul 2016 17:38:35 +0200 Date: Fri, 15 Jul 2016 17:38:37 +0200 From: "O. Hartmann" To: Matthew Macy Cc: "freebsd-current@freebsd.org" , "freebsd-x11@freebsd.org" , "freebsd-hackers@freebsd.org" Subject: Re: 4.6 DRM/i915 update CFT (Sandy Bridge?)/IvyBridge/Haswell/Broadwell/SkyLake/KabyLake supported Message-ID: <20160715173837.6248139c.ohartman@zedat.fu-berlin.de> In-Reply-To: <154d7562f75.116fac600120763.1508477402245154899@nextbsd.org> References: <154d7562f75.116fac600120763.1508477402245154899@nextbsd.org> Organization: FU Berlin X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/28SrI07_X576LnF7mNvfngi"; protocol="application/pgp-signature" X-Originating-IP: 92.225.0.113 X-ZEDAT-Hint: A X-Mailman-Approved-At: Fri, 15 Jul 2016 16:07:30 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jul 2016 15:38:45 -0000 --Sig_/28SrI07_X576LnF7mNvfngi Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Am Sun, 22 May 2016 00:20:30 -0700 Matthew Macy schrieb: > I'm happy to announce a call for testers for the 4.6 update of drm and > i915. The driver has been successfully tested on IvyBridge, Haswell, > Broadwell and Skylake. At least basic HW 3D acceleration should work, > VGA and DP out are known to work. Video decode has only been tried > once and that did not work. >=20 > At this point I'm most interested in taking an inventory of what is > broken where. My priorities are common sense: >=20 > a) stability > b) fixing 2D artifacts > c) fixing 3D problems > d) video decode=20 > d) output support > e) other features >=20 > At this time "prime" (needed for switching between GPUs, compute > APIs, and DRI3) is not yet supported. All the pieces are in place but > support existing functionality is a higher priority. Userptr (mapping > user memory in to the driver) requires VM changes. Support is > planned, but likely post-11. >=20 >=20 > A few caveats are in order: > - The only reported test on Sandy Bridge indicated severe artifacts. > - Arrandale (pre-Sandy Bridge) and earlier are not yet supported by > =C2=A0 this update. The intel_i810 code has been heavily localized for=20 > =C2=A0 FreeBSD making it more difficult to integrate. Thus there are > =C2=A0 holes in the gmch support. > - This update is 64-bit only. There is no good reason to be running > =C2=A0 in 32-bit mode on any of the hardware supported by this driver. > - Although it works fine for me on my Skylake the one other tester > =C2=A0 I have reports from indicates that the driver isn't actually > =C2=A0 attaching and creating aliases for the drm device nodes. >=20 > Please send issue/success reports to the freebsd-x11 mailing list. > I may be preoccupied with work matters for periods of time. Sending > it to the list makes sure that the messages don't get lost. >=20 >=20 > If you encounter problems with startx, please try loading the i915 > kmod in isolation and make sure that it switches correctly to vt_fb. > If you're not running efifb you'll notice a change in resolution. > If it works but is slow or has artifacts you may try switching to > UXA by removing =C2=A0/etc/X11/xorg.conf.d/20-intel.conf (if you're using > the USB image). If you've built from source, try configuring SNA > instead. SNA is much better behaved for me. >=20 > The usual rules apply for kernel debugging. There should be copious > information on that in the handbook and elsewhere. If that proves > to be problematic for people I will send out a follow up mail. >=20 > A couple observations: >=20 > - The FreeBSD PTB insist that a debugger be in tree but that it > =C2=A0 pre-date GPL2, consequently kernels are, by default compiled with > =C2=A0 DWARF2 which is very poor at retain debug information in the > =C2=A0 presence of any optimization. If this is a problem, either > =C2=A0 recompile everything with -O0 (add CFLAGS +=3D -O0 in drm2 and > =C2=A0 i915kms Makefiles, and pass COPTFLAGS=3D-O0 to buildkernel) or > =C2=A0 install a newer kgdb from ports. >=20 > - The purpose of encrypted swap is that the data on disk be > =C2=A0 unrecoverable. This is somewhat at cross purposes with savecore. > =C2=A0 So don't do that. > =C2=A0=20 >=20 > Now that this is out I will be switching gears to bringing up amdgpu > and radeon support. I have no hardware that uses the radeon driver > so I will have to rely on Jean for testing and support there. >=20 >=20 > Those of you wishing to try your hand at testing from source can > fetch our repo from github at: >=20 >=20 > https://github.com/iotamudelta/freebsd-base-graphics >=20 > Make sure to check out the drm-next-4.6 branch. >=20 >=20 > If you'd rather just try it on a usb pen driver you can also > obtain a prebuilt memstick image with this branch installed > along with xorg and some commonly used ports at:=20 >=20 > http://www.bsddesktop.com/images/disk_YYMMDDHH.img.xz >=20 > There is no root password and the user/pw is joeuser/joeuser. >=20 >=20 > If you're curious about what's on it, the script used to > create the image is here: >=20 > http://www.bsddesktop.com/images/usbcreate.sh >=20 >=20 > If you'd like to help out with collecting data on what > laptops are supported please run Warren Block's > notebookstats script: >=20 > http://www.bsddesktop.com/images/notebookstats >=20 > It's also installed under /usr/local/bin on the image. >=20 > If I've missed anything please let me know and I will follow up. >=20 > -M >=20 >=20 > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" When is a Broadwell support supposed to appear in CURRENT? Regrads, oh --Sig_/28SrI07_X576LnF7mNvfngi Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJXiQN9AAoJEOgBcD7A/5N8I18IAMIoXEGSu0ba4lYmmnIrM5kR pwMvB0IPUP5nLEPHLL4/PoybkqNS1zX3TksO7Qyy2brTP/3bwpOhgX4zXRUqugIO I6v3PybFAH3mzK6HBie82wtzTyZXTAe2SBmyLMq8vLxd4oyKOoQe9nl6mgLWK09j nsXP2aA327Dl9dkaSUKGIhpwjYBTHiE5Luayp56w4ZbfzY1JW07GSThEmX5g2OS+ RsuQbbYpxbbxEj5OTP8GK7kzz4zc8D9aQ2zencwCuB8nQ6/nZct43nVBX7Vu/nkL 21KJTXkrwExpZewUBpTrXMWWUJYBvlH+QrptV5YOL7iBEVPtafCsg6wyQCfoFMU= =m9Df -----END PGP SIGNATURE----- --Sig_/28SrI07_X576LnF7mNvfngi-- From owner-freebsd-hackers@freebsd.org Fri Jul 15 18:36:12 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 26ED1B99E4B; Fri, 15 Jul 2016 18:36:12 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from sender163-mail.zoho.com (sender163-mail.zoho.com [74.201.84.163]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 173E61247; Fri, 15 Jul 2016 18:36:11 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1468607763446125.42673548539801; Fri, 15 Jul 2016 11:36:03 -0700 (PDT) Date: Fri, 15 Jul 2016 11:36:03 -0700 From: Matthew Macy To: "O. Hartmann" Cc: "freebsd-current@freebsd.org" , "freebsd-x11@freebsd.org" , "freebsd-hackers@freebsd.org" Message-ID: <155efd813c6.1202df80646763.9140174277761846209@nextbsd.org> In-Reply-To: <20160715173837.6248139c.ohartman@zedat.fu-berlin.de> References: <154d7562f75.116fac600120763.1508477402245154899@nextbsd.org> <20160715173837.6248139c.ohartman@zedat.fu-berlin.de> Subject: Re: 4.6 DRM/i915 update CFT (Sandy Bridge?)/IvyBridge/Haswell/Broadwell/SkyLake/KabyLake supported MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Priority: Medium User-Agent: Zoho Mail X-Mailer: Zoho Mail X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jul 2016 18:36:12 -0000 > > > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > When is a Broadwell support supposed to appear in CURRENT? > > Regrads, > > oh When at least the non-VM patches to sys/ make it in. I have no direct say in that. -M From owner-freebsd-hackers@freebsd.org Fri Jul 15 19:44:00 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 27EBCB9843B for ; Fri, 15 Jul 2016 19:44:00 +0000 (UTC) (envelope-from arlie@worldash.org) Received: from ansuz.worldash.org (ansuz.worldash.org [198.144.201.100]) by mx1.freebsd.org (Postfix) with ESMTP id 075721F6B for ; Fri, 15 Jul 2016 19:43:59 +0000 (UTC) (envelope-from arlie@worldash.org) Received: by ansuz.worldash.org (Postfix, from userid 1000) id 3C23CE2E7B; Fri, 15 Jul 2016 12:52:35 -0700 (PDT) Date: Fri, 15 Jul 2016 12:52:35 -0700 From: Arlie Stephens To: freebsd-hackers@freebsd.org Subject: Re: Zone Allocator Initialization Question Message-ID: <20160715195235.GA7003@worldash.org> References: <20160714210448.GA16971@worldash.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160714210448.GA16971@worldash.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jul 2016 19:44:00 -0000 Never mind. This is beautiful code; very easy to follow. I'm now self-educated on zone allocator initialization. If I'd realized it would be this clear, I wouldn't have bothered the list by posting a query. Kudos to the authors. --Arlie On Jul 14 2016, Arlie Stephens wrote: > > Hi Folks, > > I'm chasing yet another kernel memory corruption in an obsolete > version of FreeBSD (8.4 in this case). I expect that it will turn out > to be a bug in some local customization, as they usually are. So I'm > not looking for help with actually debugging it ;-) > > What I would like help with is understanding something my > instrumentation is reporting, on systems that don't appear to have the > problem. > > In brief, I'm seeing what appears to be uma_zalloc() returning a > pointer to a virtual address that does not have PG_SLAB set on the > vm_page_t for the corresponding physical page. > > Most allocations from that zone are fine; I only see one strange one, > and that's fairly early in the system lifetime. (It's one of the > "struct file" for files opened by init.) > > Is there some kind of bootstrap situation with the zone allocator, > where certain early use zones get their first memory via a path that > doesn't mark PG_SLAB? And if so, is there any other way to recognize > those addresses as coming from a zone? (My corruption is scribbling on > process' fd_ofiles[] arrays, so I'm trying to write a sanity checker, > and was really surprised to find a valid-seeming struct file * that > didn't appear to have come from the right place.) > > Thanks in advance for any enlightenment. > -- Arlie (Arlie Stephens arlie@worldash.org) From owner-freebsd-hackers@freebsd.org Fri Jul 15 20:19:06 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A1A3AB98EAA; Fri, 15 Jul 2016 20:19:06 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-it0-x22f.google.com (mail-it0-x22f.google.com [IPv6:2607:f8b0:4001:c0b::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 69194150A; Fri, 15 Jul 2016 20:19:06 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-it0-x22f.google.com with SMTP id h190so28610416ith.1; Fri, 15 Jul 2016 13:19:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=LaAiABvGPvsyGE85i1EDbTR4YuLdu3bzvl1cwJOIicI=; b=ZGi+9ezSSFb+wAhwGFnsvqzP0CV+n0s2TgzK/7kSg2UiHKZQkUlEvEFARe5xjBqVK6 Kof92nBA5ucOCb9nps+5UcMeDX+0hZCSVm+ybJhMkvDllgkmN9A+tpmH2rXPCmEWVPKP bb+ZOoLsDgjNcn1eWeCSG0qgvfDqJ5+yoSzO3PpUcLzNfgofhrGNKdyzdnKTDiQLiMyE Zb57q+ZS7o8UcnWHg5Nr1t2cGpUd2z/sUs/k0ZQM6gew3vSurJeOp5C7+N8n+FXF3p3u futr4Bcv0a7sSU/z8zO/NbnKTSXu0XV0JGHKJEtFcvPqS3oubZgu2qXt+GdixFvhOZn8 eS1A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=LaAiABvGPvsyGE85i1EDbTR4YuLdu3bzvl1cwJOIicI=; b=E/8R0xLXERZy0/VtrkZCHDw1J8rk8frCAwA5v+pNpNzDQZvGxGGE2wNIp1tHuPmPF+ EbEonmZDQXBuMMLiSydFu3bkCW3UOUv4mmTiahrg/8O37AmwK3cFXNDGB95H0IN60Aox GkLc1s08czSHPn0kd80MZCSkKFviy2zUn89OF5iM8BfmXZDmgnaguLqiaRfc1dYfBy7O kJ9+FnHIaLpHgzFTOWENswA4QumMveW04c7Te7ZNl3iSCrqbUn485aNVLEHWxEcWxh3e Stuk0mUousklMJKL3MyAnN8CgmTc0Oa877mx7Z8PlWfshEdPIc2Q/nrcde63VDdta3Vf 8TKA== X-Gm-Message-State: ALyK8tLxoKKE9t1ljZtjbDm8ZGWLZlCCcj+VpkSutEe7FWrEyBtHGIWBWVJKBJGUZLm7L+5rZ48yYY0c4woO9A== X-Received: by 10.36.200.131 with SMTP id w125mr22255381itf.80.1468613945792; Fri, 15 Jul 2016 13:19:05 -0700 (PDT) MIME-Version: 1.0 Received: by 10.36.141.129 with HTTP; Fri, 15 Jul 2016 13:19:04 -0700 (PDT) In-Reply-To: <155efd813c6.1202df80646763.9140174277761846209@nextbsd.org> References: <154d7562f75.116fac600120763.1508477402245154899@nextbsd.org> <20160715173837.6248139c.ohartman@zedat.fu-berlin.de> <155efd813c6.1202df80646763.9140174277761846209@nextbsd.org> From: Adrian Chadd Date: Fri, 15 Jul 2016 13:19:04 -0700 Message-ID: Subject: Re: 4.6 DRM/i915 update CFT (Sandy Bridge?)/IvyBridge/Haswell/Broadwell/SkyLake/KabyLake supported To: Matthew Macy Cc: "O. Hartmann" , "freebsd-hackers@freebsd.org" , "freebsd-x11@freebsd.org" , "freebsd-current@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Mailman-Approved-At: Fri, 15 Jul 2016 20:30:24 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jul 2016 20:19:06 -0000 Heh, I'll get mmacy to poke me some more so I can start landing more stuff in -head to enable this. -adrian From owner-freebsd-hackers@freebsd.org Sat Jul 16 07:41:42 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3FCBFB9A924; Sat, 16 Jul 2016 07:41:42 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (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 E5E1B1F38; Sat, 16 Jul 2016 07:41:41 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (envelope-from ) id <1bOKEE-00134X-GA>; Sat, 16 Jul 2016 09:41:38 +0200 Received: from x55b38391.dyn.telefonica.de ([85.179.131.145] helo=thor.walstatt.dynvpn.de) by inpost2.zedat.fu-berlin.de (Exim 4.85) with esmtpsa (TLSv1.2:AES256-GCM-SHA384:256) (envelope-from ) id <1bOKEE-002uHX-88>; Sat, 16 Jul 2016 09:41:38 +0200 Date: Sat, 16 Jul 2016 09:41:45 +0200 From: "O. Hartmann" To: Adrian Chadd Cc: Matthew Macy , "freebsd-hackers@freebsd.org" , "freebsd-x11@freebsd.org" , "freebsd-current@freebsd.org" Subject: Re: 4.6 DRM/i915 update CFT (Sandy Bridge?)/IvyBridge/Haswell/Broadwell/SkyLake/KabyLake supported Message-ID: <20160716094145.3d636c0a.ohartman@zedat.fu-berlin.de> In-Reply-To: References: <154d7562f75.116fac600120763.1508477402245154899@nextbsd.org> <20160715173837.6248139c.ohartman@zedat.fu-berlin.de> <155efd813c6.1202df80646763.9140174277761846209@nextbsd.org> Organization: FU Berlin X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/R5Ph0KJfEgHC+0itOLjmg+R"; protocol="application/pgp-signature" X-Originating-IP: 85.179.131.145 X-ZEDAT-Hint: A X-Mailman-Approved-At: Sat, 16 Jul 2016 11:00:21 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Jul 2016 07:41:42 -0000 --Sig_/R5Ph0KJfEgHC+0itOLjmg+R Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Am Fri, 15 Jul 2016 13:19:04 -0700 Adrian Chadd schrieb: > Heh, I'll get mmacy to poke me some more so I can start landing more > stuff in -head to enable this. >=20 >=20 >=20 > -adrian That is nice to hear. Thank you. Regards, Oliver --Sig_/R5Ph0KJfEgHC+0itOLjmg+R Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJXieU6AAoJEOgBcD7A/5N8oSwIALlo26gciUxcWGVoyGw5HMjS SI8BLe8w9J2+dWyK9kIV1MvulnCV1AsophQc53UifsjuCjUrEC3c+XqVOlN53se/ S5lWo894x3IB1Cz8NnJidmAvJWdI7E0uJxCubZ4w/pUm9p/NsX1sTuVywIiOOlr/ Fn+/VtCrwflEKIg+ci1cxxQrsZd3/d5VtITDZNje5LeoODboVfbpW+HoCbfaZznc lYw9OUfASnEUI/b4mgjupQNq0DKQjECgjTv+T1P9BNaBTkt+P+hFAV/+u2jUCPXM gJNPryjBGXnzuKrM6uhpvasAI3DT2Fqm0yUW2Qe2M15TBNC0bZ1gG2d+3+3mnS8= =aJP0 -----END PGP SIGNATURE----- --Sig_/R5Ph0KJfEgHC+0itOLjmg+R--