From owner-freebsd-stable@freebsd.org Sun Oct 7 03:23:42 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7773110AD428 for ; Sun, 7 Oct 2018 03:23:42 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io1-xd2d.google.com (mail-io1-xd2d.google.com [IPv6:2607:f8b0:4864:20::d2d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0219D708A9 for ; Sun, 7 Oct 2018 03:23:41 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io1-xd2d.google.com with SMTP id l25-v6so13504118ioj.0 for ; Sat, 06 Oct 2018 20:23:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=lHyOt2LmDX5P/Kpr3iGOsThVpH44Dq6Uj7fnwzvbotA=; b=ECfVcb9punTk7Bvnjn/V9WQMKZ/T+TIir1gfS4CTPjaJ7EPdVuw4RpR+jgirR4f875 atBAJOqJSjCWqDN9sd24QHHDUQtte+R3H6g1NvogJMBhZojt2LE6LEx3eUSjKbMBqthh NwboJfGvHJChsdcBLokqEukUlrWAjXJ+qM4Vfzf77y1ADrcviTGOozeq1861HWk7sC2Y vnqwxpEzMa7a0ViAqScIHibYVG2lsoMlN54J0sskgc2Xp0IqfuhR55Jh08dWTa+IlC0n Mk5JNpxECDram1SSLoE43DPhfvJaP/4V5d9X3cAsXYdwS3dnjQZtbWQqBAhxQikqPdsU u8Uw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=lHyOt2LmDX5P/Kpr3iGOsThVpH44Dq6Uj7fnwzvbotA=; b=DGfYxQ/5za1a0iQGiZzozuIYLb6Ral1HBiZblR7bk4TwO3lRi0E6Xw96N5qEJUPftQ uTKdwVT1QCJsbJCEEIivpCl6lK1vvRu8IpddChRZoolMF4Q3q6+tXPEzXdEDAPwVVmXV jKGilB4UVhgvNPB7HpA+vWoNBXQ4/XiuJ6DvMTRco91nZ98nOCdlPTKK1arZ8660Vg6F wLIVO52S2B0beFuzIiwIcvbmu2OBBJM4PEQTHeET77SsSufRIPYYq4JQOFq4gsn/ae9p iIhzE14NVDyY59TUmFj4peYl0yLqrJm72Msp0b150884SZF9Z5UBguvTcf543tFfg2nk YE7w== X-Gm-Message-State: ABuFfogUm42kAvM36vgk9OEQhVCM2LkogYPF8j/97OD0aUQ4pnl97bbY dOE6A4PJxnKICxTRWqwHgC0n7K8SNu18h6Ey5/QnorrPigM= X-Google-Smtp-Source: ACcGV63w/fW1dDfs1yJ6sLsXTtzSJSdT8rqvpxMXsJCpWu9NsKHGU1dXGmEMeQl90jn0LVcIg+4n895lRonQxdcDiDo= X-Received: by 2002:a6b:e715:: with SMTP id b21-v6mr12791113ioh.37.1538882620704; Sat, 06 Oct 2018 20:23:40 -0700 (PDT) MIME-Version: 1.0 From: Warner Losh Date: Sat, 6 Oct 2018 21:23:29 -0600 Message-ID: Subject: dmesg submission service -- please submit today To: FreeBSD-STABLE Mailing List Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.27 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 Oct 2018 03:23:42 -0000 [[ I sent this to -current earlier in the day, but I thought I'd widen the scope ]] Greetings, As you can tell, the project is looking to clear some of the deadwood from its driver lists. One problem is that we have to guess what's in used based on our personal experience. This has proven to be less reliable than hoped in the 10/100 discussions that are going on now. So, to that end, I'd like to request as many people as possible submit their current dmesg to the service at http://dmesgd.nycbug.org/index.cgi so that we have a better basis for future preliminary lists of drivers for other parts of the tree. Please take the time to make these submissions regardless of what your current hardware is. Please submit for any machine you'd like to upgrade to FreeBSD 12 or 13. Heck, submit for any machine you have running, if you'd like. Identifying information is generally masked out. This is just a request by me. I'll be using the data in about a month to look at old parallel scsi driver use. Though not definitive, it will be suggestive of what's in use. The data is currently a bit thin, so I thought I'd see what a message like this could do to improve that situation. This should be viewed as a personal suggestion right now... Warner P.S. I know there's other user generated data sites out there, but this appears to be the only one that's actually still working. From owner-freebsd-stable@freebsd.org Sun Oct 7 05:40:18 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B7CF110B2589 for ; Sun, 7 Oct 2018 05:40:18 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io1-xd29.google.com (mail-io1-xd29.google.com [IPv6:2607:f8b0:4864:20::d29]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CAA175325 for ; Sun, 7 Oct 2018 05:40:18 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io1-xd29.google.com with SMTP id p4-v6so13587273iom.3 for ; Sat, 06 Oct 2018 22:40:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=uZMkPpJazamZ8l1NLOAJkyLgY/SqHeQKZn3QLVeWtOo=; b=AviK/ZhLKORomIhNoNOeXBTL0+u/+9vXGaZxayfoC3E5mGrRoyb1vyoR3xF23oK5xI zX00avcVluhEoPEwAzcCNGgCRocWg191bTZknDrHcJEU5S2fHmR+CISy27ZFiHIrGVkK pgPSmaouFEeFolRWUpBxBxRqTFuwnhpNenAj2B1dS6rXpjgPO/1VFVpYXUZoJaLlBCDk i5jn+ik2zomMgT3YGHZxJfjOayWpj82IV7i5AxB6SsPkOMmZH2TUp7G3Hak2lsWkESsB j2OzLqHNoaEFpGdWdIKi8Ljn3Jo5Ert1uJlfQqud2mAlCBUcl7sFORpvBr8IGgiyjc1c HZHQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=uZMkPpJazamZ8l1NLOAJkyLgY/SqHeQKZn3QLVeWtOo=; b=ciLCgDrL7Kb/t7/PwMn7B4DW2WGtkSQ+jIC24NueEXWJ4U3dBYDKpg3rxb5OInCSm2 sgz0j3JswuOGzWOnr20I+XH+pbGwaOF1FSB5SCEFrGofRnFQxGgI4K0L+D7a9AGxiK9R rPJibRqpwR52mipJvHgErwA0t8CT9xEWPC4wjIbcHvmc2GTfle8+7RSdV814WiqmkUEW 0h3tDYEFVcl0UawO/OmCY20+5I/HuTg9KTk/30icSELk5XBgwX7lYivmxK2w5zUW3j4Q NMrBV/SS1bN/UnF4bH91Vfrq9hrxtTGlyKjJ2Uay2MHjjfcwqh4jq40/2iE/Y1csvf+e 9aVQ== X-Gm-Message-State: ABuFfoj2DUg+yCgic2NgDUg74zgU/C5NDShr9GPxHRI3b4L1dWt69oGc KeHgFhhR2odVj+aACpjFntDZ+Ou2BYwubffUvVL7PFcRmYM= X-Google-Smtp-Source: ACcGV62WGS6wPhmPChbAC0LgubCfBsPlChEbFk/OC0hmNIwMJ3aCZU4dxaG7Vlwo6ZGq2+m4y9jgTDbBZzpWautSqqA= X-Received: by 2002:a6b:d004:: with SMTP id x4-v6mr11951708ioa.299.1538890817341; Sat, 06 Oct 2018 22:40:17 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Warner Losh Date: Sat, 6 Oct 2018 23:40:06 -0600 Message-ID: Subject: Re: dmesg submission service -- please submit today To: FreeBSD-STABLE Mailing List Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.27 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 Oct 2018 05:40:18 -0000 On Sat, Oct 6, 2018 at 9:23 PM Warner Losh wrote: > [[ I sent this to -current earlier in the day, but I thought I'd widen the > scope ]] > > Greetings, > > As you can tell, the project is looking to clear some of the deadwood from > its driver lists. One problem is that we have to guess what's in used based > on our personal experience. This has proven to be less reliable than hoped > in the 10/100 discussions that are going on now. > > So, to that end, I'd like to request as many people as possible submit > their current dmesg to the service at http://dmesgd.nycbug.org/index.cgi so > that we have a better basis for future preliminary lists of drivers for > other parts of the tree. Please take the time to make these submissions > regardless of what your current hardware is. Please submit for any machine > you'd like to upgrade to FreeBSD 12 or 13. Heck, submit for any machine you > have running, if you'd like. Identifying information is generally masked > out. > > This is just a request by me. I'll be using the data in about a month to > look at old parallel scsi driver use. Though not definitive, it will be > suggestive of what's in use. The data is currently a bit thin, so I thought > I'd see what a message like this could do to improve that situation. This > should be viewed as a personal suggestion right now... > > Warner > > P.S. I know there's other user generated data sites out there, but this > appears to be the only one that's actually still working. > This one-liner works to submit, though you'll need to change username, email and maybe tweak the description if your system doesn't have decent smbios entries. It's also x86 centric, since other systems won't have this information as readily available. curl -v -d "nickname=$USER" -d "email=$USER@$(hostname)" -d "description=FreeBSD/$(uname -m) on $(kenv smbios.system.maker) $(kenv smbios.system.product)" -d "do=addd" --data-urlencode 'dmesg@/var/run/dmesg.boot' http://dmesgd.nycbug.org/index.cgi Hope helps facilitate submission of entries. Thanks to Charles Sprickman for the idea of using a curl one-liner. Warner From owner-freebsd-stable@freebsd.org Sun Oct 7 17:10:05 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 207AE10C6C78 for ; Sun, 7 Oct 2018 17:10:05 +0000 (UTC) (envelope-from hruodr@gmail.com) Received: from mail-ed1-x52d.google.com (mail-ed1-x52d.google.com [IPv6:2a00:1450:4864:20::52d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8A98A8B9BB for ; Sun, 7 Oct 2018 17:10:04 +0000 (UTC) (envelope-from hruodr@gmail.com) Received: by mail-ed1-x52d.google.com with SMTP id y20-v6so8953212eds.10 for ; Sun, 07 Oct 2018 10:10:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:subject:in-reply-to:message-id:references:user-agent :mime-version; bh=ujBHweBJC73r16LjAEsZnG+MNchdm418DgIYr6k5Jnw=; b=uaNxPAKv09KEH45Iywu9FfvQ3grJtfOp+mC/Ym2iTg5o12WkUhTzOP05V+EdABPGgu r7Z+QkKyMuvUmPZMPRV6qsf6aCgc1lshIxGS7kGNeXEwNs/nYxSPtmbrw16uP4nO4uQv zHQrhBGPYX/eBCePECXu5GQB+c1VrMb+BoKsqsPXCy+GFA1A5fviIlwK0WRnRfKt3X/a pTD4/ksWPLcXwQymhPQeWsTszxRmWcrNKNkM8oofLSX1FI9IwJlX0YXgk3rgu6/kJdGG hocoHRU9YXU7T+vXV2M9TBLuYfquinWIbx4XuiN+uEETY2+qern2G6K68whK+vlZTujf UBMg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:in-reply-to:message-id :references:user-agent:mime-version; bh=ujBHweBJC73r16LjAEsZnG+MNchdm418DgIYr6k5Jnw=; b=AE5xPvsfa2/MFlyyuxI3DvkxJx9Kxnxkz0U/FY86yd+uWE/W1GRXGjq30yjhG0fMER rSyOp6DZjgHOihto6yZ/1GZFP93u30vDz7Eq00MWZQZnOU/TwKr2AObUF0jZUz99VFr3 bje5P73Cx5CXpmQ1Oy9zJSFUqgYoP0gYS88iUjouE2bCwj5mK9ILpFq994NGqN3moHKO /KXZDOJwhjlcxcVpq5/8rajtxsAE6/z1yr2Xxd0xHd6ocdDDWZLe0Uhcdg8f7FUSKKgw uFSAzi/64GvsEVkgt1NMR6d8oRrSrOqOJg9TpsnFg9t0ieB6GDIXzpEGWtNK9NTZGZ5t MvTA== X-Gm-Message-State: ABuFfoi50+d9cj0TquVZWF4dYaCMRBp9supSC0pKC5cOAIvV9EO/ZMiq kW4NGMmyhQiprl3B1JwJl4E3X2a9 X-Google-Smtp-Source: ACcGV602Jy6/94j4Jd/w/ehlf7nJCsh1oYL+I54SbBES0AdnERHRzIVdpev+tm6HS4MweP8iGvVA8g== X-Received: by 2002:aa7:d0ce:: with SMTP id u14-v6mr25400568edo.250.1538932202992; Sun, 07 Oct 2018 10:10:02 -0700 (PDT) Received: from fbsd.fritz.box (i577BC166.versanet.de. [87.123.193.102]) by smtp.gmail.com with ESMTPSA id j15-v6sm2557438ejy.3.2018.10.07.10.10.01 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 07 Oct 2018 10:10:01 -0700 (PDT) Date: Sun, 7 Oct 2018 17:03:01 +0000 (UTC) From: Roderick To: FreeBSD-STABLE Mailing List Subject: Re: dmesg submission service -- please submit today In-Reply-To: Message-ID: References: User-Agent: Alpine 2.21.9999 (BSF 287 2018-06-16) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.27 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 Oct 2018 17:10:05 -0000 On Sat, 6 Oct 2018, Warner Losh wrote: > As you can tell, the project is looking to clear some of the deadwood from > its driver lists. One problem is that we have to guess what's in used based > on our personal experience. This has proven to be less reliable than hoped > in the 10/100 discussions that are going on now. Should I dump a dmesg with any device I have connected to every computer I have? Deadline today? Or better I risk not be able to read data on old SCSI discs I am not using now? Best regards Rodrigo From owner-freebsd-stable@freebsd.org Sun Oct 7 17:26:16 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 931DD10C7394 for ; Sun, 7 Oct 2018 17:26:16 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-ot1-x335.google.com (mail-ot1-x335.google.com [IPv6:2607:f8b0:4864:20::335]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2F3568C36B for ; Sun, 7 Oct 2018 17:26:16 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-ot1-x335.google.com with SMTP id p23so5766093otf.11 for ; Sun, 07 Oct 2018 10:26:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=bKgw+ApCzJV9+hBflJbHoLn6zt8sJD9MwXT/PLbmvgM=; b=SC9jhOB8VdnTHiRlvktne1b47DZgPIWUcHCx3HwdF6oQdfhVLnPgntoBG5TJ+BJSj/ XHDsBkLFGYZcbqTsqlQBM5sFLX0IBLhT7vC7HU5uaKptZc8uNjw69+OlvfMA6EDBy1NC 5M4DxYaLxCxvi22bwTG9LNXSM/ZD0b/LPTs6LnnKiKxOArEACPKUMCZRuq8GTJtgw4nT 935onOdD6tkSgRO3DAlOeeWsxolYkyKht/ZWgQpbJV5Adkco7Fy0GFo7KuHCdCtDNrGm WEMS7XQF4RzNadekyzW2YAzz1Ez0NcPOYsHQmQ5LHO1AREekXlms63Dubv1klf+xbYLj MKyw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=bKgw+ApCzJV9+hBflJbHoLn6zt8sJD9MwXT/PLbmvgM=; b=kP3lVXdeQsQas9t23qtZeaN0B5hHTRmz2Pcke2LAS0+M9YfoaS+qQclMhJOZPXEgNX 0tWAM3hWcmaxYJ+UMCLzAlTtlEUaI25N6j1IoHaso5QWYbsarGa+vQcmDZObikP/KarY o0Ccp5cUFTenGfz+CS+tt/5qNIFzvZfMysdP+ivNxIpvh5cRHBDj2lMuuuPVYf0XI+df D2oU6pr4a2oe/rIgODcXMvbH1FOwH0XLzXa9MUyvPzng2rATYDXLVSs3TTyuB1NnhEwC ExwLwB2FcH6j+hVGP3llKyK1wU7y9PplO8dt+FfR8U2UHgzu0jINNFUng6+SLlsamJkj UQug== X-Gm-Message-State: ABuFfoi2/ffW78YpJHzWoWAXiE3KiX+9YwuLb2XJgS8QY1BkRucCVVsv aDIMWzvrNxrzNcGJ8ZtUDoRWF+sLPEiGi17TfA8= X-Google-Smtp-Source: ACcGV61OxscI5P7z1sSyZwYk/NoniUMTgytufgyE7nXOrTwnqhvL9pU/q1tTV8rZ8iXxX3LM5M/CnOBH5XylX+t9AxQ= X-Received: by 2002:a9d:34f:: with SMTP id 73mr12499616otv.343.1538933175120; Sun, 07 Oct 2018 10:26:15 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Kevin Oberman Date: Sun, 7 Oct 2018 10:25:57 -0700 Message-ID: Subject: Re: dmesg submission service -- please submit today To: hruodr@gmail.com Cc: FreeBSD-STABLE Mailing List Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.27 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 Oct 2018 17:26:16 -0000 Warner said that he would look at submissions in about a month. "I'll be using the data in about a month to look at old parallel scsi driver use." He's looking for information on what drivers are still needed, so only if the SCSI drives require in different drivers (unlikely) would that be needed. I suspect that, unless you use CardBus type stuff, just the /var/run/dmesg.boot should be all that i required. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 On Sun, Oct 7, 2018 at 10:11 AM Roderick wrote: > > On Sat, 6 Oct 2018, Warner Losh wrote: > > > As you can tell, the project is looking to clear some of the deadwood > from > > its driver lists. One problem is that we have to guess what's in used > based > > on our personal experience. This has proven to be less reliable than > hoped > > in the 10/100 discussions that are going on now. > > Should I dump a dmesg with any device I have connected to every computer > I have? Deadline today? > > Or better I risk not be able to read data on old SCSI discs I am not > using now? > > Best regards > Rodrigo > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@freebsd.org Sun Oct 7 18:20:38 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 87FD210C8949 for ; Sun, 7 Oct 2018 18:20:38 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it1-x131.google.com (mail-it1-x131.google.com [IPv6:2607:f8b0:4864:20::131]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1F7618E500 for ; Sun, 7 Oct 2018 18:20:38 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it1-x131.google.com with SMTP id q70-v6so8735838itb.3 for ; Sun, 07 Oct 2018 11:20:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=yP02jxEiVbTYWZWoRL/F+zNe0Gbaxt8xhNTOLXPn4xU=; b=qMJpXP2NPQRrD7g5q58klSrRmN5pmtPtYc7cmIBLgk3vR9JpMZHBkhFr/eF8c0zPOy tdrUTrAy8h0+r7IaCeA2/UdGJmmj4K6EPDbKZsNW7efGb60uC3PI9YS7FbuSYkY//tBI B+UUhCaB2XHYaCouXGYZpOxEcJpg3zYwndkkrp/zWg+46WET9II8CR7rU9Cc1/viKBUW oN501UmO+Ei04hNpv04I9HpXwPyY2pwgw/RcrJpTQzZLSyGp8POIgfrPT52HaGId4iyZ cCmLS/psXt9g+RGk+dER9TDCJR24OvGDQZp9UHuJaWIyPeRbslRCQmqrwNCAxyqoYvPq ZZGg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=yP02jxEiVbTYWZWoRL/F+zNe0Gbaxt8xhNTOLXPn4xU=; b=Z+TlnEnSuVhKzkHhOI8eEYJm58W6mku0sD8kDqHUpWC8Z1EYi1+foWUmdVk77lpMYF Id28QGfUktU4o+NvNWm4nLwqauYeznxqscOSuynfc/2C/MYv8/FFj8x8Zccfx/tAAdbP lA/lsKTk6RE8zZvLlEdzcR5acd3j0d4q4gRDjVcgs8YdowLAKs4JM1V7kMgt1CaraOIf FuSa0Pcm5rrnbFNaDZb+KdGBMBQHhWNBdzYzBxEXpHyu5I1m64wimXDgkps90eOatCU3 3O9tApoU2D37dT5NcKuILwxSd+fY+2v5pQOIDkWzCFUe27QZLBGWqO/wuLL6fC5uX3PY grRA== X-Gm-Message-State: ABuFfohFPmhF6G+csc0TZ6tO1Hz2M6doYa+LslxBbJoXjU5yZza8P52x CaVI6SICtHIsvU0QaB42rW29H6gTYtWQFAG6NsSDHA== X-Google-Smtp-Source: ACcGV63GS8mGl8QOK8AjHOq/X6n4uH9K/67v7Ehm8gCYtd/Joj5wrfXhv7MSv25nfZElzpeL+hu99ahdNG2iNfAHZk0= X-Received: by 2002:a24:9ed7:: with SMTP id p206-v6mr1104777itd.39.1538936437218; Sun, 07 Oct 2018 11:20:37 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Warner Losh Date: Sun, 7 Oct 2018 12:20:25 -0600 Message-ID: Subject: Re: dmesg submission service -- please submit today To: hruodr@gmail.com Cc: FreeBSD-STABLE Mailing List Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.27 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 Oct 2018 18:20:38 -0000 On Sun, Oct 7, 2018 at 11:11 AM Roderick wrote: > > On Sat, 6 Oct 2018, Warner Losh wrote: > > > As you can tell, the project is looking to clear some of the deadwood > from > > its driver lists. One problem is that we have to guess what's in used > based > > on our personal experience. This has proven to be less reliable than > hoped > > in the 10/100 discussions that are going on now. > > Should I dump a dmesg with any device I have connected to every computer > I have? Deadline today? > > Or better I risk not be able to read data on old SCSI discs I am not > using now? > There's no deadline, per se. And there will be at least two drivers that will survive the purge (ahc and mpt). At the present time, they are the only two known to be working for real workloads. So chances are you are already using one of these devices, and if not they are cheap, so there will be a fallback to getting data off of parallel SCSI disks, as well as continued support for parallel scsi tape drives, scsi CD, etc. FreeBSD will support a way to access these devices for years to come. The reason I'm looking at this is because CAM has become rather twisted in places over the years. Many of the reasons for the twistiness can be traced directly to weird workarounds for devices that are almost certainly no longer in use. I'd like to eliminate them. Some can be eliminated because they were for a particular ISA device that's no longer in the tree. But I can't do the others until I know which ones, if any, need to remain. This is why I was asking for dmesgs now so I can start to get a feel for which devices are even still in use on any FreeBSD version, let alone more modern ones. Looking at the NIC data it's clear that we have devices that are wildly popular, and then ones that aren't used with very little in between. Unlike in NIC land, there's a more real and tangible cost that I can point to for continuing old devices in the tree, and I said 'about a month from now' so I can come up with examples of what's a problem, as well as look at data to see what devices still have users, etc, to avoid some of the back-and-forth that we had at the start of the 10/100 discussions as people with devices that turned out to be popular rightly complained. I think having a well articulated reason other than 'it's old' will also help the community understand the cost of keeping things in the tree so we can better judge of the current level of 'benefit' justifies that cost. And any elimination will be safely past 12.0 and won't be back-ported, so anything that works today should work for 12.x releases over the next 3-5 years at the very least. I know that these kinds of discussions can be fraught and I'm doing my best to be honest and open about what's going in, why we want to do thing, and giving plenty of time for the communities that are using FreeBSD to let us know of that use in advance of any decisions being made. I'm hoping the extra data people provide will help us make the initial selection process be more data driven rather than 'best guess' which turned out to be not very good. tl;dr: Not removing anything before 12, devices documented as still working will remain, there's cheap alternatives for removed drivers, don't panic. Warner From owner-freebsd-stable@freebsd.org Sun Oct 7 18:21:33 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D318610C8A9E for ; Sun, 7 Oct 2018 18:21:32 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io1-xd33.google.com (mail-io1-xd33.google.com [IPv6:2607:f8b0:4864:20::d33]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 69BD38E72E for ; Sun, 7 Oct 2018 18:21:32 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io1-xd33.google.com with SMTP id n18-v6so14259981ioa.9 for ; Sun, 07 Oct 2018 11:21:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=L/UrADMuFMI8eBNjhus8wtCnbcwTv0iSAsisAq8rNds=; b=MGBbXXuxnToq4wFosIN+sdotT9s6yIrpMQ/X9Z2OhU5+Zna/+oQZnkuoo5TDYwLHOB QUtWQB/13utML/BkDz0RBwxvw4gTJy/m/u4Ha/gmd9ynYSdQ3DujbdIFj9EDycfTyLWD uTbx6AYytP8xcPY/hmQ0MN+B1YuLJdYiQWZUr2DWe0Mp8u5JfBj32DmN7xsTPu4z1p7J s5LzmQsznA+O1K2BkrDNM7zDCpd+ECCAEy3gjhtk5m7dc458Le9kcU0CZEAusDlxPtoL iLGY10+W0jr3ZmxpnHqPoacmw1pqI8It4lVJDXzUbvX4lq5bmQIbw5q2ohsar+zcw+U0 0AZQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=L/UrADMuFMI8eBNjhus8wtCnbcwTv0iSAsisAq8rNds=; b=tmI3jr+o1uxuvB/7d+nSnvEbxtEdJxcim/2x8SQguuz1OC2yHRYLmO4rNrLfOoTXyE mzaRWDNJ8FxhkON9raxAAT4r/ADiBe7QhfBTLrRTf31w1sYjOai/LVV4pmtARiSwSUCy f/KrgdzBi8LBtNWlupLkeNhtEzKNcn5IufJknY5+sMbz2bkY8csLcF5j5+yQsPtp3iRG Vd/NrZvtBspoOpMXrzrdoOWshfVN0OJqyrvqkIPjSCI4B1DrDgvcgrstFark4nrb7iVy O+IhpMl/rC+nVP3km3Pox48Kqlwi/Q78Jr9piOUk1HUR5p8m1rZqOhL/+H9cdPAK9Rvd 4hMA== X-Gm-Message-State: ABuFfojdMFj7GgxBMhwRVw9ljKWMzDltBW+73N5LwqD0zZdIcYiUEUn9 J+Cb/iOxhnMEytr+vlBml9U54mrr1NWH7ZUELzEsuw== X-Google-Smtp-Source: ACcGV63Kh4u+kn1b/WSN6N8+xC/sbXKs7KnOfCek6nDBiYsJeF36DIcGTTDzq5r2e6ia6x35KsCn4lZnUKKDP5/fVo8= X-Received: by 2002:a6b:e715:: with SMTP id b21-v6mr14373683ioh.37.1538936491680; Sun, 07 Oct 2018 11:21:31 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Warner Losh Date: Sun, 7 Oct 2018 12:21:20 -0600 Message-ID: Subject: Re: dmesg submission service -- please submit today To: Kevin Oberman Cc: hruodr@gmail.com, FreeBSD-STABLE Mailing List Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.27 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 Oct 2018 18:21:33 -0000 On Sun, Oct 7, 2018 at 11:27 AM Kevin Oberman wrote: > He's looking for information on what drivers are still needed, so only if > the SCSI drives require in different drivers (unlikely) would that be > needed. I suspect that, unless you use CardBus type stuff, just the > /var/run/dmesg.boot should be all that i required. > CardBus, PC Card and USB are much harder to quantify. Warner From owner-freebsd-stable@freebsd.org Sun Oct 7 21:00:17 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C894210CC57E for ; Sun, 7 Oct 2018 21:00:16 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 67DAF93FD8 for ; Sun, 7 Oct 2018 21:00:16 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 2C91410CC57B; Sun, 7 Oct 2018 21:00:16 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1B70E10CC57A for ; Sun, 7 Oct 2018 21:00:16 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B50BF93FD0 for ; Sun, 7 Oct 2018 21:00:15 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) 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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 0E67A1DD75 for ; Sun, 7 Oct 2018 21:00:15 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w97L0EYA065242 for ; Sun, 7 Oct 2018 21:00:14 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w97L0EXj065241 for stable@FreeBSD.org; Sun, 7 Oct 2018 21:00:14 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201810072100.w97L0EXj065241@kenobi.freebsd.org> X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@FreeBSD.org using -f From: bugzilla-noreply@FreeBSD.org To: stable@FreeBSD.org Subject: Problem reports for stable@FreeBSD.org that need special attention Date: Sun, 7 Oct 2018 21:00:14 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.27 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 Oct 2018 21:00:17 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- New | 230620 | "install -d" issue Open | 227213 | FreeBSD 10.4 kernel deadlocks on sysctlmemlock 2 problems total for which you should take action. From owner-freebsd-stable@freebsd.org Sun Oct 7 23:41:54 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D6C7B10ABEFE for ; Sun, 7 Oct 2018 23:41:54 +0000 (UTC) (envelope-from rleigh@codelibre.net) Received: from b-painless.mh.aa.net.uk (b-painless.mh.aa.net.uk [81.187.30.52]) (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 9D84D710DF for ; Sun, 7 Oct 2018 23:41:54 +0000 (UTC) (envelope-from rleigh@codelibre.net) Received: from 0.a.3.c.a.6.a.4.1.3.f.e.a.2.1.d.d.b.d.d.0.6.8.0.0.b.8.0.1.0.0.2.ip6.arpa ([2001:8b0:860:ddbd:d12a:ef31:4a6a:c3a0]) by b-painless.mh.aa.net.uk with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.89) (envelope-from ) id 1g9IgL-0004cL-LR for freebsd-stable@freebsd.org; Mon, 08 Oct 2018 00:41:53 +0100 Subject: Re: dmesg submission service -- please submit today To: freebsd-stable@freebsd.org References: From: Roger Leigh Message-ID: <0ca6d0d5-4e18-adbe-8b33-090d6ef66067@codelibre.net> Date: Sun, 7 Oct 2018 23:41:43 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.27 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 Oct 2018 23:41:55 -0000 On 07/10/2018 05:40, Warner Losh wrote: >> I'd like to request as many people as possible submit >> their current dmesg to the service at http://dmesgd.nycbug.org/index.cgi so >> that we have a better basis for future preliminary lists of drivers for >> other parts of the tree. > This one-liner works to submit, though you'll need to change username, > email and maybe tweak the description if your system doesn't have decent > smbios entries. It's also x86 centric, since other systems won't have this > information as readily available. Out of interest, has FreeBSD considered implementing an equivalent of Debian's "popularity-contest" package, which periodically submits anonymised lists of installed packages? On FreeBSD this could be from the pkg database, and could also include hardware information. In Debian, it's opt-in at install time, or installable afterward. If FreeBSD had a similar package and installer opt-in, this could potentially provide useful usage statistics without any privacy concerns. Regards, Roger From owner-freebsd-stable@freebsd.org Sun Oct 7 23:58:02 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3AD3810AC766 for ; Sun, 7 Oct 2018 23:58:02 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io1-xd2a.google.com (mail-io1-xd2a.google.com [IPv6:2607:f8b0:4864:20::d2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CE22B71718 for ; Sun, 7 Oct 2018 23:58:01 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io1-xd2a.google.com with SMTP id t7-v6so14553279ioj.13 for ; Sun, 07 Oct 2018 16:58:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=I4fpBnNBP//niYXSxvn3FRwi9Nt6DSoGhqJnEzCdeMw=; b=Pky7zQSEEdz4l4oy4aYpdAi3I0YeEC+7otn8RRl3eJiZ7w1B4kYdPbxAFnt+P812Tu L2qSC8Rijo3XRZMKA/jduIS0HaUgWXfO7mJhP885lwf304EGB2dR5P8z0P7DnZG/9ien tRe9psbKxIeBmwGm/bbb4jwwNGSqliTfaC16HVWOGJCuSdjyHYKCX/RhG3TZs0XGRG1c NFJhhi5nP3JB1sENvcnkjt7fmqwSMFFhXMz9VDkhkmxHhHoG5qmKQzJbXy+EHfcSpowO jlwpgBV7ud6CI+EG5POu5TXruPYsfuxMfZ5mYQiXfvD/V0RFlMZ1bHC6DtWOH3Wxjkds 3Erw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=I4fpBnNBP//niYXSxvn3FRwi9Nt6DSoGhqJnEzCdeMw=; b=iq71VeIvwRLx5Xf4h9nyPUsNrBVUec88kQE4VumI9QlJ4AeUn7yXX0jEc1sLJjx+Gi uFJ0WkK+UOKmKerFs4TnSR63lQamA7z4umQpYNTQ8eCceBk9TYEajP1xxtzPKwo0tb8q iwPo/DrIqcEKpYa2PIEks3IhcLIoNJnSphUfVkO9tnLUhvfCyD+0ZZl+sQsD6Kqc+QPe Jb6p7RAPqR/lGIkg6VcA4M+C0j+s+usuXqty8TS7dT1/StiKMT6vZYG05STI1hsOesfa Amy0+FNPFlxoqGO/FEYcctwKgkrf8g9yDg96asQZ/pCYPlG19c9Of7UqJ0q0nLzvjjIO VRcQ== X-Gm-Message-State: ABuFfojfgmprNfvdDfm2gMwjSVSb6vRHcLrIHY8yzaVGu97N3lkcyWSs 6xBAR2rzSh7Vjc3/UO33UbI1sXvZ3VqbA38+uTitEb3z X-Google-Smtp-Source: ACcGV62yT7wUtxraJTI+C+LV4y2DM/0TlsFW0WRwfgia4Gw2Aipq888ojoq3qUFK2S3kcgQXZjrUItTVRAwSGlVy0vo= X-Received: by 2002:a6b:d004:: with SMTP id x4-v6mr13747658ioa.299.1538956680959; Sun, 07 Oct 2018 16:58:00 -0700 (PDT) MIME-Version: 1.0 References: <0ca6d0d5-4e18-adbe-8b33-090d6ef66067@codelibre.net> In-Reply-To: <0ca6d0d5-4e18-adbe-8b33-090d6ef66067@codelibre.net> From: Warner Losh Date: Sun, 7 Oct 2018 17:57:49 -0600 Message-ID: Subject: Re: dmesg submission service -- please submit today To: rleigh@codelibre.net Cc: FreeBSD-STABLE Mailing List Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.27 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 Oct 2018 23:58:02 -0000 On Sun, Oct 7, 2018 at 5:45 PM Roger Leigh wrote: > On 07/10/2018 05:40, Warner Losh wrote: > > >> I'd like to request as many people as possible submit > >> their current dmesg to the service at > http://dmesgd.nycbug.org/index.cgi so > >> that we have a better basis for future preliminary lists of drivers for > >> other parts of the tree. > > > This one-liner works to submit, though you'll need to change username, > > email and maybe tweak the description if your system doesn't have decent > > smbios entries. It's also x86 centric, since other systems won't have > this > > information as readily available. > > Out of interest, has FreeBSD considered implementing an equivalent of > Debian's "popularity-contest" package, which periodically submits > anonymised lists of installed packages? On FreeBSD this could be from > the pkg database, and could also include hardware information. > > In Debian, it's opt-in at install time, or installable afterward. If > FreeBSD had a similar package and installer opt-in, this could > potentially provide useful usage statistics without any privacy concerns. > We've talked about that, but haven't implemented it. I'd like to figure out how we can send anonymized structured data about the system, including hardware and software installed. bsdstats kinda sorts did something like this, but their data is unavailable (which is what motivated my current experiment). Warner From owner-freebsd-stable@freebsd.org Mon Oct 8 05:22:08 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 898EB10B32FA for ; Mon, 8 Oct 2018 05:22:08 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from vtr.rulingia.com (vtr.rulingia.com [IPv6:2001:19f0:5801:ebe:5400:1ff:fe53:30fd]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vtr.rulingia.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BE1B67A294 for ; Mon, 8 Oct 2018 05:22:07 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from server.rulingia.com (ppp59-167-167-3.static.internode.on.net [59.167.167.3]) by vtr.rulingia.com (8.15.2/8.15.2) with ESMTPS id w985LgOn036919 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 8 Oct 2018 16:21:48 +1100 (AEDT) (envelope-from peter@rulingia.com) X-Bogosity: Ham, spamicity=0.000000 Received: from server.rulingia.com (localhost.rulingia.com [127.0.0.1]) by server.rulingia.com (8.15.2/8.15.2) with ESMTPS id w985LTsr035836 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 8 Oct 2018 16:21:29 +1100 (AEDT) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.15.2/8.15.2/Submit) id w985LTdi035835; Mon, 8 Oct 2018 16:21:29 +1100 (AEDT) (envelope-from peter) Date: Mon, 8 Oct 2018 16:21:29 +1100 From: Peter Jeremy To: Roger Leigh Cc: freebsd-stable@freebsd.org Subject: Re: dmesg submission service -- please submit today Message-ID: <20181008052129.GH21091@server.rulingia.com> References: <0ca6d0d5-4e18-adbe-8b33-090d6ef66067@codelibre.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Ycz6tD7Th1CMF4v7" Content-Disposition: inline In-Reply-To: <0ca6d0d5-4e18-adbe-8b33-090d6ef66067@codelibre.net> X-PGP-Key: http://www.rulingia.com/keys/peter.pgp User-Agent: Mutt/1.10.0 (2018-05-17) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.27 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 Oct 2018 05:22:08 -0000 --Ycz6tD7Th1CMF4v7 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2018-Oct-07 23:41:43 +0000, Roger Leigh wrote: >Out of interest, has FreeBSD considered implementing an equivalent of=20 >Debian's "popularity-contest" package, which periodically submits=20 >anonymised lists of installed packages? On FreeBSD this could be from=20 >the pkg database, and could also include hardware information. There's ports/sysutils/bsdstats but I'm not sure how popular that is. --=20 Peter Jeremy --Ycz6tD7Th1CMF4v7 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEE7rKYbDBnHnTmXCJ+FqWXoOSiCzQFAlu66VlfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVF QjI5ODZDMzA2NzFFNzRFNjVDMjI3RTE2QTU5N0EwRTRBMjBCMzQACgkQFqWXoOSi CzT1MQ/+OXYcTfFB91FwlloGyKRwZpz3Bo/uwhK0rXCZyWV3K+XGKRfDErp0gcN7 pHDWB4LaDn4451/Ry832NYyeHWxhV8dhx6bL71ZucDzKlhMNpY/Lt4B+aw2KH1pw vnim0BEhFBYboJNr3FD14QLO3riAhUOHX+FzCKnWYnolYWe4/ZY12EvVVnKK0nEa KMUSB1rq4XhO+pc3cnRVG+524wF03cqNx/uUaNr4s19cVHzVxUzEP/SsXnOrZHPy USL+NM44pe6VrdVejVqydrHzvIg44ikLqZSMi1WAIWc3UGj/SfVfnCIhOq8AJVzW VODoQqKU4yIzfnLTE6Lh8OKaS/MJmChDSBl0vXBabOEtw9yx1Cy1U3UXlPu4XLsK QW6wCsfoDhg+4mAOUUDzQlrmwlaOm7RNNQiuq/4Oo0UdXZZ094gxEiRRzegJcGut 8Ex8xOGIqHRnlfLC3gpdimYT/3hHq8TxuGoSdXNVeAMySyUQGYfwmXoj4QBHWn+6 Jju6tenk71xLxPTrGRKiHyuWb5U8jI4xp2D3n5oejmt7LklLEvVbfxYN7C1Q515N UEmdU0LCfd+000CDnPpd0A0wS44jEuGQB3ClQ3XNzTIOm2cIIbbIzGE+3ANfjvQL /8VOB9L4XtIDMCJ6V1wOHvLgkMOZKaK0sMcDP+0NdnrE646AKUM= =U8Jn -----END PGP SIGNATURE----- --Ycz6tD7Th1CMF4v7-- From owner-freebsd-stable@freebsd.org Mon Oct 8 05:32:45 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D7DB410B373C for ; Mon, 8 Oct 2018 05:32:44 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io1-xd35.google.com (mail-io1-xd35.google.com [IPv6:2607:f8b0:4864:20::d35]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6EFB97A720 for ; Mon, 8 Oct 2018 05:32:44 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io1-xd35.google.com with SMTP id t7-v6so14904438ioj.13 for ; Sun, 07 Oct 2018 22:32:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=SBweXKuPh6iphc9rSz0eWpU3BOpgmTHeqV1jWhfFD7k=; b=JtuvF1wtRc6c8eFnXOlH3BcTcE+GYxsZD0nNWQMFDoZSUt52jm9CU58x/8uFqgXDt2 pSI7d0fRkj7qJp3kAHQOwQu9zasmUNFYyxF9ndHRSPE6WURkcjcwaeHZZneyJcoliTfd EX9/dFSlWRlMXCg+vKNly3f6WBoaETZsjcg/XB4H3CgF09Cxa4XY2s6Gr27otD+NG41s u2TKAm5u5pq7Q/CNDjagHk5nTmjLwbYMFjp6dR3l4uifA/uwA9+qNB0F1Kung5vVSa+z hH2zL6PI2wDOr8gRDFIlnCiAZBHqqxwhoxGPtwmV3kix1KnDU5nydlKnK+fPyhpWWnMj v2JQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=SBweXKuPh6iphc9rSz0eWpU3BOpgmTHeqV1jWhfFD7k=; b=FgEae00f8ietX2FdQ0LiNMhZncKL45aFBTMps1PVuzOJ2PKlYEUzmrMBA5xK93vHM1 ghGuwKijdj4GJmdT7yFkllyGwzacv8g/vwFy38znuD9TIr6Ckee4tdTB+T5Z5dAtaHY5 Ygbf0nvO5HT4x3G0o6niHU5l5p1nU6BEHHLKQz2p+AWl7CORue7laUeZ4Csf8JeYROy/ o16bTUq+rLRk+zaApZUWs325WPa7fvCCtOWB10qJHq2Z5ClmvqggqYBaEHBDuIZAtkHO arpyr1zMy7bfa5Ri/WOd0VPX/qmiKomF1IocVFHQJpH6BFhz7OCqLm/jn4ubOINBl4rx 2B7Q== X-Gm-Message-State: ABuFfojYGgx0AdpaYqxvHSzkqgVqtrAEpZDUYNWZVP8YpnOHfSW4AAQW kePtL56nyVmk0puSfgiSx7+hSMKD6ONrwn8hqt88qw== X-Google-Smtp-Source: ACcGV60LW5J+qNoZge+GXn3V1Yf/yokHy3iihkD6LFlBwBbn6e6epwkOA7eEp0e/NMxb6deMQzhTGVE+CUaw9JVAn8o= X-Received: by 2002:a6b:3902:: with SMTP id g2-v6mr14681148ioa.168.1538976763623; Sun, 07 Oct 2018 22:32:43 -0700 (PDT) MIME-Version: 1.0 References: <0ca6d0d5-4e18-adbe-8b33-090d6ef66067@codelibre.net> <20181008052129.GH21091@server.rulingia.com> In-Reply-To: <20181008052129.GH21091@server.rulingia.com> From: Warner Losh Date: Sun, 7 Oct 2018 23:32:32 -0600 Message-ID: Subject: Re: dmesg submission service -- please submit today To: Peter Jeremy Cc: rleigh@codelibre.net, FreeBSD-STABLE Mailing List Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.27 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 Oct 2018 05:32:45 -0000 On Sun, Oct 7, 2018 at 11:23 PM Peter Jeremy wrote: > On 2018-Oct-07 23:41:43 +0000, Roger Leigh wrote: > >Out of interest, has FreeBSD considered implementing an equivalent of > >Debian's "popularity-contest" package, which periodically submits > >anonymised lists of installed packages? On FreeBSD this could be from > >the pkg database, and could also include hardware information. > > There's ports/sysutils/bsdstats but I'm not sure how popular that is. > It appears to be broken :( Warner From owner-freebsd-stable@freebsd.org Mon Oct 8 16:45:27 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E281510C4733 for ; Mon, 8 Oct 2018 16:45:26 +0000 (UTC) (envelope-from staroscik@gmail.com) Received: from mail-wr1-x431.google.com (mail-wr1-x431.google.com [IPv6:2a00:1450:4864:20::431]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 50E7871CFC for ; Mon, 8 Oct 2018 16:45:26 +0000 (UTC) (envelope-from staroscik@gmail.com) Received: by mail-wr1-x431.google.com with SMTP id n1-v6so21570440wrt.10 for ; Mon, 08 Oct 2018 09:45:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=77idFrOFc4vbUREYbFPjJrxRyAMS+cQaK01RLNo9CEM=; b=Z724qLP0FfoZtqgas/JBOqFw9Zdg+mWja4mxwpMk58gtUhq9A+U2SWDvglIkTyEwgV cTl8YTkTFSRFq3b8OIRcl8gnDHW8YtUgKg0YgScEprrzaLeiqm+pAta2QLKzgW7X4aWz /JRikYIGJQIn3gh4dXw8NGYHEyHGVGmLBPakjFXe5nqvhUmqX6H+6xEC2mnZzlJpKne8 goymEOKwKELx3BCuggu1a3SBEvArjPuB3QGGD1ohakq4/XV4LEwy0T1badnZjaI/vAWo KEJi+v3++3G7zX2WThdd5SmKg4eEwZDdZPjdElwdInTrJf4VgJA8NghgdnHltgFYNFPk oNPg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=77idFrOFc4vbUREYbFPjJrxRyAMS+cQaK01RLNo9CEM=; b=rBMjane7i4Gjg8eZCNWU4q+Wo5etwbf9m1qC3x5adYCad+wgHZ501071PcvH+7H+8X jp/XLWIzDWgE/qRYiCxyccN/6SG9ZljGcO9JWFHtwtQbTxnwsWCg7RO70xev8GMoqbGj 1Nmcoy3n4+rIbiMhqyJQzCRCPjTo7Xulvo32KqNMKurXCcXjJQEDX4xrg/RBO4CiaRrp ZYeTGvBScSy7VfP8F759ekVCGDwFS/iIZxPKoCCRAVQmIXCAaHSSL2QBMh/sO1ZgeVRJ tInMwEGuYMsT3IfRRGUtw5cUTzVlOW83Msi1+EQHCVbyAPjZbXMdXqgx3joq/1vjRUBk 96ng== X-Gm-Message-State: ABuFfoiBaUg5W/PHYy9MWG+gmhgRwemhFz/+R5CdsMPRvKc9fQeJCzW7 evpu1Mj69v8cG8YP8KpaAdNHc83ZlZFR0NTrpnpaUg== X-Google-Smtp-Source: ACcGV63dlwW2iVJfCgOwL/WSy5x4x1NMV2RDRyXnhrNlCUni8nUfqpqHQ9uCBcXx63dbdbGNH8kuXencvGT0aEmQVNA= X-Received: by 2002:adf:f0d2:: with SMTP id x18-v6mr18469548wro.287.1539017124582; Mon, 08 Oct 2018 09:45:24 -0700 (PDT) MIME-Version: 1.0 From: Matt S Date: Mon, 8 Oct 2018 09:45:16 -0700 Message-ID: Subject: Re: dmesg submission service -- please submit today To: freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.27 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 Oct 2018 16:45:27 -0000 It really seems like the project would benefit from having better hardware stats. If you make it a package, people have to be educated to get it and use it--not that it doesn't have value, it just isn't well exposed and you will only get stats from the most clueful users. I would suggest making anonymized stat upload part of the install and upgrade process, to get wider coverage. - When installing, there's a new step or checkbox with an opt-in for hardware data sharing, defaulting to off - If you opt in, your info is uploaded as part of the install process - Expose the same functionality in a new system-level command like 'freebsd-uploadstats' and make it an optional but suggested part of the upgrade process, which is something most users will see repeatedly if they continue to be users. Perhaps the local machine can generate a hash of the report, check that with the server before the upload goes through. Hardware doesn't change that often. I do not want the project to turn in to Google or Microsoft, but knowing the hardware in use is a pretty worthy goal. MS From owner-freebsd-stable@freebsd.org Mon Oct 8 17:09:52 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1FDB710C50AE for ; Mon, 8 Oct 2018 17:09:52 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-io1-xd2a.google.com (mail-io1-xd2a.google.com [IPv6:2607:f8b0:4864:20::d2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 943AB729E1 for ; Mon, 8 Oct 2018 17:09:51 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-io1-xd2a.google.com with SMTP id w2-v6so10202874ioc.1 for ; Mon, 08 Oct 2018 10:09:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=d1ZManbecSztex+pUG7KXuCUbKKUuP4mpOOFC8uOI/g=; b=dq39S0FBJXK6pavNLqU+cgqROH9rsQBHjSJvrQMjcelJ3JEkIbRcekVX6L8ks8sh8v hxUketjuNgN4U3zEniBZ1KPyyTfpgJsNiqPtx1HuWDalaNO+yRHWRZnE+W0YxKMlD5dz 9yA9vwIAa7W7eQVwqKMf6WbP18HCxTz6yFVvncJSs7+DrMDGq0G0nzwODIIvVfkzVGmm 9GAxwSNaB/IWzruxmge0zSSjd1GzaFdoFI/+wwTDXH4llNvbZW7bYFZhqw9kNRG8i8kz 4k5eepp5OFMUdr5sgwbMOObbysZFW2sRu1Hu0gH5njLlOXk+zl+PhBwxiPuGkTWj25Kh 6Gdw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=d1ZManbecSztex+pUG7KXuCUbKKUuP4mpOOFC8uOI/g=; b=cJs/lhWVtTu7Bf8MliEwtDxPgwSVASs/bPKyRzpD08mrwjyx80ytg/FNUf/OkHEGAj 6LpUlnouLJJuOaHeeJxOzsVIkbH0crdQtu2DAjWaYka4+lnX+X1/C786UO86B8/t+hdi XavoGAnpuWdewCPpMu3bFVOpTXHsrlGGpIggjCmoZ1Kthodi6gnAyTEmpzogF9srxIVq s1duRD3Pi2Q+h+EVTjc4oEYXCIu4ek2OTkzJX9V7F8HF+Y3ZmOGy7zlgPNTtOLcZS7hW o6yDztxG4OhKfhwPBxsBDO4012OvkvHeEJkhRo7ddPm/bQciVADgiwxp4LHnJlsj324Q TAiA== X-Gm-Message-State: ABuFfog7Hs+P9jRTg9UWSvUSepa7TC1liYfttsfRiVKMH/dCtVknzkGj nB2DmWF8Q3NUaVJUXHrJEEojylhEGMsX6ruN1VA= X-Google-Smtp-Source: ACcGV61euVvvaTXSYSPsTQRxAiEOfOGlunrPCTnYKwUSfzk2OjqgWn+vGWUDV4n9EflULi39W2s75nH0TW/Jh+WhEmI= X-Received: by 2002:a6b:8d8a:: with SMTP id p132-v6mr15737061iod.240.1539018591023; Mon, 08 Oct 2018 10:09:51 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: blubee blubeeme Date: Tue, 9 Oct 2018 01:09:39 +0800 Message-ID: Subject: Re: dmesg submission service -- please submit today To: staroscik@gmail.com Cc: freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.27 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 Oct 2018 17:09:52 -0000 On Tue, Oct 9, 2018 at 12:48 AM Matt S wrote: > It really seems like the project would benefit from having better hardware > stats. If you make it a package, people have to be educated to get it and > use it--not that it doesn't have value, it just isn't well exposed and you > will only get stats from the most clueful users. > > I would suggest making anonymized stat upload part of the install and > upgrade process, to get wider coverage. > > - When installing, there's a new step or checkbox with an opt-in for > hardware data sharing, defaulting to off > - If you opt in, your info is uploaded as part of the install process > - Expose the same functionality in a new system-level command like > 'freebsd-uploadstats' and make it an optional but suggested part of the > upgrade process, which is something most users will see repeatedly if they > continue to be users. > > Perhaps the local machine can generate a hash of the report, check that > with the server before the upload goes through. Hardware doesn't change > that often. > > I do not want the project to turn in to Google or Microsoft, but knowing > the hardware in use is a pretty worthy goal. > > MS > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > https://en.wikipedia.org/wiki/Dark_pattern From owner-freebsd-stable@freebsd.org Mon Oct 8 17:25:09 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 14D7C10C58FB for ; Mon, 8 Oct 2018 17:25:09 +0000 (UTC) (envelope-from staroscik@gmail.com) Received: from mail-wr1-x429.google.com (mail-wr1-x429.google.com [IPv6:2a00:1450:4864:20::429]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 83FAD7364B for ; Mon, 8 Oct 2018 17:25:08 +0000 (UTC) (envelope-from staroscik@gmail.com) Received: by mail-wr1-x429.google.com with SMTP id y16so21697247wrw.3 for ; Mon, 08 Oct 2018 10:25:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=jHps4r9r2sB7gnUUUAZpZaJebhENTmcrW8oY699i2io=; b=rodrFZodbxJdU/IQ/5oDac7DkKl1Nw3Db08KeEQfLL4WIhzlQgUPwaR7945bXU1YOh IMyusbM1UwTHEY+0jxb+CsJVK7a5JzW31gpA0OY3S2JD6jCp1LcDJTTZJ3NdtKYnPnQ8 CONeot29hXFt/Cd2z/qD16LyQY4Y1rN+zUBmxfLG5p4w9Bmtrf0OASVxzE9G0eMY7FzQ h6dUcanylQOm8na66YfHZPZRWVVPkbseymclABZ6kArTEEbO6qcQ6K5qXY7iR0uxhrIu t18PoENt3Pboevb7r73XSI6Ueh2S9SzxlufU5wemFv620kHgwUj8fr2hYcFsMiVpp5i0 9jSA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=jHps4r9r2sB7gnUUUAZpZaJebhENTmcrW8oY699i2io=; b=WR/gs9JUQ0aylZA5pmmcmLrD69fXvnwpzX0qS7A9514/8og9IW8oo6o6yIg/nDtZsX 2GGTNeAYFDv1JYcZesOwogAJYSnxHqHj2GMJRbsErscl/6bY0CH6leP7ZxOVOxcHqzYM auRxFwwBtjMcNFbiFYko4VzW1KpxLMR+Kz5bQGqjRoTI8MPzl5SSzOti4yFc1dFbe6Hd t6a4tTfMD0qlxS50YAduNmp3/qPMDXJ9yGpXE9ieshBqtpBeJhKwCKXzknsCIlrFnlMC iQN7WyjNQa3oN6U3X/J4Y/DqEZ2zyJMI/ELJoj8A2PH63IP6ZWJ+A5utqScxhtyFHHpS /Wsw== X-Gm-Message-State: ABuFfoj5I6JuPPtd8psq57cUMt4qsgO4LWTJAwFLJ7D4Q4SouCVRKErw 9TXQTO+erzAq1uDS1rJ42AMbW5/sXBbGG35i1ZSjCdV7 X-Google-Smtp-Source: ACcGV62uCdwWxeLY0AcQwaYIGuxqiNPPd389Z+kivuctibaWoqHVdjfLfS0a5jpl2x6YX1G2rXk5hP6v9vmvB2y04QA= X-Received: by 2002:adf:ad65:: with SMTP id p92-v6mr18114021wrc.7.1539019507116; Mon, 08 Oct 2018 10:25:07 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Matt S Date: Mon, 8 Oct 2018 10:24:58 -0700 Message-ID: Subject: Re: dmesg submission service -- please submit today To: gurenchan@gmail.com Cc: freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.27 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 Oct 2018 17:25:09 -0000 I don't see how "dark pattern" applies because this doesn't trick you into an ongoing subversive data-sharing arrangement. In this idea, install asks you if you want to share stats once--you are not opted in to a system. Then, when processing upgrades, the Handbook would remind you that the report ability exists and this is a good time to do it if you've made any changes. Nothing happens without your explicit agreement during install, and nothing happens afterwards unless you type in a command, every time. If the current data is adequate for the project's needs, nothing needs to change. If the project needs to know more about hardware stats, the request to get hardware info needs to be somewhat visible. Making it an optional part of installing/updating seems reasonable to me. I'm assuming we trust the project, but if the idea of easier stat-sharing is offensive, then I guess there's nothing to talk about. On Mon, Oct 8, 2018 at 10:09 AM blubee blubeeme wrote: > > > On Tue, Oct 9, 2018 at 12:48 AM Matt S wrote: > >> It really seems like the project would benefit from having better hardware >> stats. If you make it a package, people have to be educated to get it and >> use it--not that it doesn't have value, it just isn't well exposed and you >> will only get stats from the most clueful users. >> >> I would suggest making anonymized stat upload part of the install and >> upgrade process, to get wider coverage. >> >> - When installing, there's a new step or checkbox with an opt-in for >> hardware data sharing, defaulting to off >> - If you opt in, your info is uploaded as part of the install process >> - Expose the same functionality in a new system-level command like >> 'freebsd-uploadstats' and make it an optional but suggested part of the >> upgrade process, which is something most users will see repeatedly if they >> continue to be users. >> >> Perhaps the local machine can generate a hash of the report, check that >> with the server before the upload goes through. Hardware doesn't change >> that often. >> >> I do not want the project to turn in to Google or Microsoft, but knowing >> the hardware in use is a pretty worthy goal. >> >> MS >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >> > https://en.wikipedia.org/wiki/Dark_pattern > From owner-freebsd-stable@freebsd.org Tue Oct 9 07:41:27 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E401B10C3B01 for ; Tue, 9 Oct 2018 07:41:26 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from ipmail06.adl6.internode.on.net (ipmail06.adl6.internode.on.net [150.101.137.145]) by mx1.freebsd.org (Postfix) with ESMTP id 1F2BB7AC99 for ; Tue, 9 Oct 2018 07:41:25 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from ppp118-210-155-206.bras1.adl6.internode.on.net (HELO leader.local) ([118.210.155.206]) by ipmail06.adl6.internode.on.net with ESMTP; 09 Oct 2018 18:06:15 +1030 Subject: Re: dmesg submission service -- please submit today To: freebsd-stable@freebsd.org References: From: Shane Ambler Message-ID: <0732fe1a-9eed-f87f-1691-486afcab6a52@ShaneWare.Biz> Date: Tue, 9 Oct 2018 18:06:13 +1030 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-AU Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.27 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 Oct 2018 07:41:27 -0000 On 9/10/18 3:15 am, Matt S wrote: > It really seems like the project would benefit from having better hardware > stats. If you make it a package, people have to be educated to get it and > use it--not that it doesn't have value, it just isn't well exposed and you > will only get stats from the most clueful users. > > I would suggest making anonymized stat upload part of the install and > upgrade process, to get wider coverage. > > - When installing, there's a new step or checkbox with an opt-in for > hardware data sharing, defaulting to off > - If you opt in, your info is uploaded as part of the install process > - Expose the same functionality in a new system-level command like > 'freebsd-uploadstats' and make it an optional but suggested part of the > upgrade process, which is something most users will see repeatedly if they > continue to be users. > > Perhaps the local machine can generate a hash of the report, check that > with the server before the upload goes through. Hardware doesn't change > that often. There is the bsdstats port for system version and hardware details, as the site has had errors listing hardware details for some time it may not last much longer. With the amount of TrueOS entries, it would indicate that they probably have (had?) it as a default install. If the FreeBSD project or foundation doesn't want to collect this data then a company that relies on *BSD, like iX Systems, may want to step up and provide servers to collect this data. I do think it would be better as an official project data collection rather than a third party service. -- FreeBSD - the place to B...Software Developing Shane Ambler From owner-freebsd-stable@freebsd.org Tue Oct 9 10:32:20 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 90AFD10C90AC for ; Tue, 9 Oct 2018 10:32:20 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 33B4A81988 for ; Tue, 9 Oct 2018 10:32:20 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: by mailman.ysv.freebsd.org (Postfix) id ED24110C90AB; Tue, 9 Oct 2018 10:32:19 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DC18610C90A9 for ; Tue, 9 Oct 2018 10:32:19 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from constantine.ingresso.co.uk (unknown [IPv6:2a02:b90:3002:411::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 837CB81985 for ; Tue, 9 Oct 2018 10:32:19 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from [2a02:b90:3002:411::6] (helo=dilbert.ingresso.co.uk) by constantine.ingresso.co.uk with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91 (FreeBSD)) (envelope-from ) id 1g9pJI-000EuE-BO for stable@freebsd.org; Tue, 09 Oct 2018 10:32:16 +0000 Received: from petefrench by dilbert.ingresso.co.uk with local (Exim 4.91 (FreeBSD)) (envelope-from ) id 1g9pJI-00011K-5m for stable@freebsd.org; Tue, 09 Oct 2018 11:32:16 +0100 To: stable@freebsd.org Subject: Latest update to ATI driver broke in same way as using DRM-next did Message-Id: From: Pete French Date: Tue, 09 Oct 2018 11:32:16 +0100 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.27 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 Oct 2018 10:32:20 -0000 So this is kind of interesting - I posted here last month about trying to use drm-next and it not finding my 2nd monitor properly. I did try and subscribe to x11@ but for some reaosn that didnt work, and I didnt worry abotu it too much so didnt investigate further as I wont be running 12.0 for a while. But this morning I just did a small update of ports, and it upgraded the driver from xf86-video-ati-7.9.0_3,1 to 18.1.0,1 ... and that acts in the same way, i.e. only runs on one monitor and cant see the 2nd. I thought it was a bit too much of a co-incidence, as I would guess both the old and new drivers share substantial amounts of code. I rolled back to the old driver and this is the dmesg outoput it gives if thats of any help... info: [drm] Radeon Display Connectors info: [drm] Connector 0: info: [drm] DP-1 info: [drm] HPD4 info: [drm] DDC: 0x6450 0x6450 0x6454 0x6454 0x6458 0x6458 0x645c 0x645c info: [drm] Encoders: info: [drm] DFP1: INTERNAL_UNIPHY2 info: [drm] Connector 1: info: [drm] DP-2 info: [drm] HPD5 info: [drm] DDC: 0x6470 0x6470 0x6474 0x6474 0x6478 0x6478 0x647c 0x647c info: [drm] Encoders: info: [drm] DFP2: INTERNAL_UNIPHY2 info: [drm] Connector 2: info: [drm] DVI-I-1 info: [drm] HPD1 info: [drm] DDC: 0x6460 0x6460 0x6464 0x6464 0x6468 0x6468 0x646c 0x646c info: [drm] Encoders: info: [drm] DFP3: INTERNAL_UNIPHY info: [drm] CRT1: INTERNAL_KLDSCP_DAC1 info: [drm] Internal thermal controller with fan control info: [drm] radeon: power management initialized info: [drm] Connector DP-1: get mode from tunables: info: [drm] - kern.vt.fb.modes.DP-1 info: [drm] - kern.vt.fb.default_mode info: [drm] Connector DP-2: get mode from tunables: info: [drm] - kern.vt.fb.modes.DP-2 info: [drm] - kern.vt.fb.default_mode info: [drm] Connector DVI-I-1: get mode from tunables: info: [drm] - kern.vt.fb.modes.DVI-I-1 info: [drm] - kern.vt.fb.default_mode info: [drm] fb mappable at 0xE0142000 info: [drm] vram apper at 0xE0000000 info: [drm] size 9437184 info: [drm] fb depth is 24 info: [drm] pitch is 8192 fbd0 on drmn0 VT: Replacing driver "vga" with new "fb". info: [drm] Initialized radeon 2.29.0 20080528 for drmn0 on minor 0 From owner-freebsd-stable@freebsd.org Wed Oct 10 04:30:33 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E401210C7D0B for ; Wed, 10 Oct 2018 04:30:32 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 924658DEC1; Wed, 10 Oct 2018 04:30:32 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from mousie.catspoiler.org (unknown [76.212.85.177]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: truckman) by smtp.freebsd.org (Postfix) with ESMTPSA id 0658F82E1; Wed, 10 Oct 2018 04:30:31 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Date: Tue, 9 Oct 2018 21:30:29 -0700 (PDT) From: Don Lewis Subject: early boot netisr_init() panic on older AMD SMP machine with recent 11-STABLE To: freebsd-stable@FreeBSD.org cc: nwhitehorn@FreeBSD.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=us-ascii Content-Disposition: INLINE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.27 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 Oct 2018 04:30:33 -0000 My desktop machine has an older AMD SMP CPU and tracks 11-STABLE. For about six months or so it frequently panics early in boot. If I retry a sufficient number of times I can get a successful boot, but this is rather annoying. A normal boot looks like this: Copyright (c) 1992-2018 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 11.2-STABLE #16 r339017M: Sat Sep 29 19:18:41 PDT 2018 dl@mousie.catspoiler.org:/usr/obj/usr/src/sys/GENERICDDB amd64 FreeBSD clang version 6.0.1 (tags/RELEASE_601/final 335540) (based on LLVM 6.0.1 ) WARNING: WITNESS option enabled, expect reduced performance. VT(vga): resolution 640x480 CPU: AMD Athlon(tm) II X3 450 Processor (3214.60-MHz K8-class CPU) Origin="AuthenticAMD" Id=0x100f53 Family=0x10 Model=0x5 Stepping=3 Features=0x178bfbff Features2=0x802009 AMD Features=0xee500800 AMD Features2=0x37ff SVM: NP,NRIP,NAsids=64 TSC: P-state invariant real memory = 34359738368 (32768 MB) avail memory = 33275473920 (31733 MB) Event timer "LAPIC" quality 100 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 3 CPUs FreeBSD/SMP: 1 package(s) x 3 core(s) ioapic0: Changing APIC ID to 2 ioapic0 irqs 0-23 on motherboard SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! Timecounter "TSC-low" frequency 1607298818 Hz quality 800 random: entropy device external interface [SNIP] An unsuccessful boot looks like this (hand transcribed): [SNIP] ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 3 CPUs FreeBSD/SMP: 1 package(s) x 3 core(s) ioapic0: Changing APIC ID to 2 ioapic0 irqs 0-23 on motherboard SMP: AP CPU #2 Launched! SMP: AP CPU #1 Launched! Timecounter "TSC-low" frequency 1607298818 Hz quality 800 panic: netisr_init: not on CPU 0 cpuid = 2 KDB: stack backtrace: db_trace_selfwrapper() ... vpanic() ... doadump() ... netisr_init() ... mi_startup() ... btext() ... This problem may be silently occuring on many other machines. This machine is running a custom kernel with INVARIANTS and WITNESS. The panic is coming from a KASSERT(), which is only checked when the kernel is built with INVARIANTS. This KASSERT was removed from 12.0-CURRENT with this commit: https://svnweb.freebsd.org/base/head/sys/net/netisr.c?r1=301270&r2=302595 Revision 302595 - (view) (download) (annotate) - [select for diffs] Modified Mon Jul 11 21:25:28 2016 UTC (2 years, 2 months ago) by nwhitehorn File length: 44729 byte(s) Diff to previous 301270 Remove assumptions in MI code that the BSP is CPU 0. Perhaps this should be MFC'ed, but it seems odd that the BSP is non-deterministic. From owner-freebsd-stable@freebsd.org Wed Oct 10 19:07:06 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 44E4610B9389 for ; Wed, 10 Oct 2018 19:07:06 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F29C78D2C7; Wed, 10 Oct 2018 19:07:05 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from mousie.catspoiler.org (unknown [76.212.85.177]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: truckman) by smtp.freebsd.org (Postfix) with ESMTPSA id 53BF9DC22; Wed, 10 Oct 2018 19:07:05 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Date: Wed, 10 Oct 2018 12:07:03 -0700 (PDT) From: Don Lewis Subject: Re: early boot netisr_init() panic on older AMD SMP machine with recent 11-STABLE To: freebsd-stable@FreeBSD.org, jhb@FreeBSD.org cc: nwhitehorn@FreeBSD.org In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=us-ascii Content-Disposition: INLINE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.27 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 Oct 2018 19:07:06 -0000 On 9 Oct, Don Lewis wrote: > My desktop machine has an older AMD SMP CPU and tracks 11-STABLE. For > about six months or so it frequently panics early in boot. If I retry a > sufficient number of times I can get a successful boot, but this is > rather annoying. > > A normal boot looks like this: > > Copyright (c) 1992-2018 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 11.2-STABLE #16 r339017M: Sat Sep 29 19:18:41 PDT 2018 > dl@mousie.catspoiler.org:/usr/obj/usr/src/sys/GENERICDDB amd64 > FreeBSD clang version 6.0.1 (tags/RELEASE_601/final 335540) (based on LLVM 6.0.1 > ) > WARNING: WITNESS option enabled, expect reduced performance. > VT(vga): resolution 640x480 > CPU: AMD Athlon(tm) II X3 450 Processor (3214.60-MHz K8-class CPU) > Origin="AuthenticAMD" Id=0x100f53 Family=0x10 Model=0x5 Stepping=3 > Features=0x178bfbff MOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT> > Features2=0x802009 > AMD Features=0xee500800> > AMD Features2=0x37ff SKINIT,WDT> > SVM: NP,NRIP,NAsids=64 > TSC: P-state invariant > real memory = 34359738368 (32768 MB) > avail memory = 33275473920 (31733 MB) > Event timer "LAPIC" quality 100 > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 3 CPUs > FreeBSD/SMP: 1 package(s) x 3 core(s) > ioapic0: Changing APIC ID to 2 > ioapic0 irqs 0-23 on motherboard > SMP: AP CPU #1 Launched! > SMP: AP CPU #2 Launched! > Timecounter "TSC-low" frequency 1607298818 Hz quality 800 > random: entropy device external interface > [SNIP] > > An unsuccessful boot looks like this (hand transcribed): > [SNIP] > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 3 CPUs > FreeBSD/SMP: 1 package(s) x 3 core(s) > ioapic0: Changing APIC ID to 2 > ioapic0 irqs 0-23 on motherboard > SMP: AP CPU #2 Launched! > SMP: AP CPU #1 Launched! > Timecounter "TSC-low" frequency 1607298818 Hz quality 800 > panic: netisr_init: not on CPU 0 > cpuid = 2 > KDB: stack backtrace: > db_trace_selfwrapper() ... > vpanic() ... > doadump() ... > netisr_init() ... > mi_startup() ... > btext() ... > > This problem may be silently occuring on many other machines. This > machine is running a custom kernel with INVARIANTS and WITNESS. The > panic is coming from a KASSERT(), which is only checked when the kernel > is built with INVARIANTS. > > This KASSERT was removed from 12.0-CURRENT with this commit: > https://svnweb.freebsd.org/base/head/sys/net/netisr.c?r1=301270&r2=302595 > > Revision 302595 - (view) (download) (annotate) - [select for diffs] > Modified Mon Jul 11 21:25:28 2016 UTC (2 years, 2 months ago) by nwhitehorn > File length: 44729 byte(s) > Diff to previous 301270 > > Remove assumptions in MI code that the BSP is CPU 0. > > Perhaps this should be MFC'ed, but it seems odd that the BSP is > non-deterministic. I now wonder if this panic is a side effect of EARLY_AP_STARTUP, which was enabled by default in 11-STABLE GENERIC back in May, so the timeframe fits. Since the panic only happens with INVARIANTS enabled, most users are unlikely to to encounter this problem. From owner-freebsd-stable@freebsd.org Wed Oct 10 21:42:43 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E8FE810BD360; Wed, 10 Oct 2018 21:42:42 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from d.mail.sonic.net (d.mail.sonic.net [64.142.111.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6419E73081; Wed, 10 Oct 2018 21:42:42 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from comporellon.tachypleus.net (cpe-75-82-218-62.socal.res.rr.com [75.82.218.62]) (authenticated bits=0) by d.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id w9ALgTpS027768 (version=TLSv1.2 cipher=AES128-SHA bits=128 verify=NOT); Wed, 10 Oct 2018 14:42:30 -0700 Subject: =?UTF-8?Q?Re=3a_FreeBSD_12_PowerPC_won=e2=80=99t_boot_at_all=2e?= To: Andreas Tobler , Alex McKeever , FreeBSD Current , FreeBSD Stable References: <187374964.4382554.1538652870884.ref@mail.yahoo.com> <187374964.4382554.1538652870884@mail.yahoo.com> From: Nathan Whitehorn Openpgp: preference=signencrypt Autocrypt: addr=nwhitehorn@freebsd.org; keydata= xsFNBFuARN8BEADLKYsG3l1aq/M21R59I/5EsEfvtvd15ZJ9lDHcWPuxzIfGnu2LMpe5PrFP e/Y4bcsPrlB4S3I3ooIUDvoEEsDeqgqlZod3QevOK/RjLqiqx1i/4mKnobJ++3ppyVVIccgN sUrj786OYCFCI/W+uWw7cbKewNeaL//Z/TDKlHLkssiy6qmZbNQ0ZjcMLJKUesk4eVg2TtTD HNe42ZuxbUC9iLYieO4c7kQB4qiFhagDRiObXrLzvm2MQYeAaNVRqID+mfI75TWrQ+t98iVu mHvFu461eeteq59jg6H/IL07ACxL+HzEVM+D6tPtPrz7ppr3wiZL5Cu17yu0nAx0nhJTV8ZB qza1rOVun0x65S14L41XD2HkmBDxTaRlTg8ypnkLFo8kh+MEq4k67apL/DUGcaUjKy2TVUC7 3igLO/DwQHrkWx2RrOmS3xS0TgGXVmB47nq2Zveo3fcjporQK63n2sbLkS70cfAJAJ9KHEIx u9am44iW5Ku3+mVLgQYybtcUxlk/Jw/BA5V6KUcDQMd5kTm0MyagziqMaT+57ceYxwRBK4HC DCLRpSOHV81/YzyL5vnwfHsxADm3091rd0uwr8uRCQn7wLvlcFyp/JKSFkVnE1oo7UE4QQJZ GbSJyvj7GdXu0LdghALcMj/thdb+js4D3UuCaAMecgVSscxEIQARAQABzS5OYXRoYW4gV2hp dGVob3JuIDxud2hpdGVob3JuQGljZWN1YmUud2lzYy5lZHU+wsGOBBMBCAA4FiEEPWQg+qgh ST6Avw1hOLZNlGaE6HcFAluAUl4CGwMFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AACgkQOLZN lGaE6HeHFw//fN2CzkiW1yedjLGEQ3uXRMgu6geRgWdtkgg/pOhn5OLSQI4R59kjvHNHHqln 1QYdxe63lsbe+7CRsTKuke3/mgsQ1h6n7cCzsoXVP3eLtWjshAz7spwUcdRRFTSbwkMzKcRn plpr+ByZDw98vnpQo10J5xYmf6if6wcEpVlazwnC5G1gHktM4X0jrlAUKSgVx7MG8o4G6af9 7MQJINAG6g6+BlBH3u5fmPunKi9qgHsZxKnTZneD2mO5u2x6p1qmqybvfvWI5UEvktPeEext JBeXXqdex+HWmAbLYznLUoBloBl+fW5Lo9VapkcGubvGC0WLr/gYuamAApwoFpa4/SBqgmHr JSsPqoDtheWt9oYzuYkYW5+tpJQoDVdG3KCOQJSYZIbNT8HyviFY32ZSn6gIn2qP/5E+rA8J +6/57XCZXPazE4FiPNbwY/OwZoi7w0yRKcdmJoSoC/GdjtQbjyeARbAaHIcudeU/bB3paGS2 rHkoW4iR5TnK/V/QJvNT4KC6Dw3m6pfBIzsF+smcyjz+MzBFQNvSOtG4kJQooKcMsThas8oX VTx+WsqNAVOeQKTOU74jlUYKm5+w5aIOJbc8jg1LlTWJus1SxYtxT9lgNwOCUhE/j6Ueq9jG V9POWg31C44akWmnK8rS4PImUBsPKwtxUNM6BhfZRbtIjQ7OwU0EW4BFQQEQAOLKFtg6us0A LA7LtvjxIskIgqFJjHw2ka/UtdJ432P9kvmBq7z4v0+m/gkxCOOG0yDi2Cv/ALJobsyb56tb U6MU0SRjTio35S2jit369B1BDC2TLNF337sUquUx0l4wkEXEBefvLRYouF8BRbkgjveg7sA4 NjsiduQx92vPJnBoaH2OWxqDbr5X6kF5cx9jPrKUJ4ZqH/raE/SSDhtow4aKO0nWbteVGck1 5W1X/S8KziPXKazxCQ8qprQRTAehsdG/bSbWD95hp3TAlEbl4N4UqqS7n4jCZunCeii2TDZH Vvx/lpFAT2ezx646p2PUmH5hpiVMgbY5uHcyahwNf+eNOO7gotnNYoieoLw4fUeTYOq+s3IN isCB4iovQcZOCYSzmwRolQRggX0tBSenR6Pgp38YjVIkWvMHhxbVifAusjvVbm/GQeA2MaCt kog53Iyfo7ri9DeNpVuRc/47BxHi8JtdyyGgLO13Ajcwc6V7KLeDmw/SXJAMssuWQlXzs8Og spNvtymBh5rq4TlxAY65L3Yv/yh0izEztOJO3Ob9y3gLrp7TeDI0EO9SyGuFXbgWY/NXlDwW HWguMgO7DWM/KxeaMYyHfnffIeQ6uhM21y42I7NV11mWwycv/XJkID3fd7GWBecakdYnYI/7 FYMDHmsUQPmSMkbqCqYcZe47ABEBAAHCwXYEGAEIACAWIQQ9ZCD6qCFJPoC/DWE4tk2UZoTo dwUCW4BFQQIbDAAKCRA4tk2UZoTod2RbEACbQ2bwJ3++bvqclErbekf7BXYja37/HxGE67q3 9xf28hen8vWGtXwq4bWmZT5H8bBqXigA4bUU4nN4X3xEDfTyqkQMuDTnnwT7Y61B4QEqhi4a q4adf/KP0l1UCg4CJ0KS931Han+VbiuUcbadu1ZX37Ef6g/hG+mt59FeXDMU0rers2Bpr8zB 8ywojAsVC92kvOHLsCQtdCsPzC+R6B1bY6/Re9slM1NBd+2k4BUVhYu8Fb8Ir37OmN0aGQzY uRczfrmR/OV5/1+g5XeYSFbq/0Q3KkFWLHfimff8lb9GRWrdvOUpYyGluv49b/G5o9lSxPwX yBfaoVi/WDDfJ/XJw9H90XK68TYxPfEQkeuLEEzg+Bz3Zeduyo2Zx4S5apLqAbv0RzduXgIG YZVPu8R4ya8nQWHeUpot17lt8SL7yFkMJaAXk27QqUAaxjqnGBLn70YMWXFGySfvjgaR1Ftu /S/HSKqH7m8aFYZftqs7ZojXNdqGHZKRrIx6hRUYuZQM8uxHDweF4jF+QIwYIUmtry5h8iti Sjt9KHjpkH3Wz5o1mk6cbFNN+wgpHplDl/iZMZjFskTAJfEsYHVSSm21zcYvvogrbqYvciMT ty65+0A8Gz9tMbcNx9ePaGoM+9jeFehrzTjdaiTiC+umSd/Y29DCW4OBMr1VfufVVKbfAQ== Message-ID: <5028f483-8156-9ef0-704a-97e23bc60825@freebsd.org> Date: Wed, 10 Oct 2018 14:42:29 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Content-Language: en-US X-Sonic-CAuth: UmFuZG9tSVZEr+AnjRyqViynKtYk+pHRUTvWNlDkJXrvVGtyW13p6mdlsduJvkgR4d08izHxQPq1FBH0XtriPnZv72V3m3jYfmPeH3bQ3z8= X-Sonic-ID: C;1PYcY9XM6BGWfdTsia6IwQ== M;Ik9YY9XM6BGWfdTsia6IwQ== X-Spam-Flag: No X-Sonic-Spam-Details: 0.0/5.0 by cerberusd X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.27 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 Oct 2018 21:42:43 -0000 This probably seems to come from the loader geli support. If I rebuild loader with WITHOUT_LOADER_GELI=1 set, everything is fine. Could anyone else who is having trouble try to reproduce that? -Nathan On 10/5/18 1:38 PM, Andreas Tobler wrote: > On 04.10.18 13:34, Alex McKeever wrote: >> Subject says it all, that and it inverts the boot selector when >> selected. Tested it on my eMac G4 1.25 GHz (Retail). Last version of >> FreeBSD that works for me is 11.1, as 11.2 doesn’t boot all the way >> (hangs on cryptosoft0) > > What image did you try? ALPHA8 should boot, but is not stable yet. If > there will be an APLHA9, it should boot and should be stable, at least > it is here. > > Andreas > _______________________________________________ > 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" > From owner-freebsd-stable@freebsd.org Wed Oct 10 22:21:25 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 55A2D10BE3E9 for ; Wed, 10 Oct 2018 22:21:25 +0000 (UTC) (envelope-from tyler@monkeypox.org) Received: from sanddollar.geekisp.com (sanddollar.geekisp.com [216.168.135.167]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mail.geekisp.com", Issuer "mail.geekisp.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E5386745BE for ; Wed, 10 Oct 2018 22:21:24 +0000 (UTC) (envelope-from tyler@monkeypox.org) Received: (qmail 8617 invoked by uid 1003); 10 Oct 2018 22:14:46 -0000 Received: from unknown (HELO grape.brokenco.de) (tyler@monkeypox.org@50.0.170.232) by mail.geekisp.com with (AES256-SHA encrypted) SMTP; 10 Oct 2018 22:14:45 -0000 Date: Wed, 10 Oct 2018 15:14:38 -0700 From: "R. Tyler Croy" To: freebsd-stable@FreeBSD.org Subject: Peculiar failure of re(4) to active a link after a RAM upgrade Message-ID: <20181010221438.GF28842@grape.brokenco.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="f6nK9RR+X1IX2pXa" Content-Disposition: inline User-Agent: Mutt/1.10.1 (2018-07-13) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.27 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 Oct 2018 22:21:25 -0000 --f6nK9RR+X1IX2pXa Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I recently upgraded my 11.2-STABLE machine from 4 to 16GB of memory. Upon reboot the dual-NIC re(4) card which had been previously working failed to either negotiate or activate a link (i.e. lights up :)) with my DSL modem. ifcnofig lists the interface as 'no carrier' I verified that both ports (re0 and re1) were working by plugging network cables into my switch, and found that both were able to activate a link properly. When I plugin the DSL modem's cable into my em(4) based NIC, that activates a link properly. Regardless of which re(4) NIC I stick the cable into, it fails to create a link (ifconfig lists em0 as 'active'), while the same cable works properly in an em(4) NIC. I'm running r339079 right now, and if I remember correctly, had upgraded the world prior to the RAM upgrade, so it _seems_ like the RAM upgrade is the only variable which changed. I'm really clueless as to what would even be happening underneath the covers here, and would appreciate any pointers in the right direction for debugging here :) Cheers, -R Tyler Croy -- GitHub: https://github.com/rtyler Twitter: https://twitter.com/agentdero --f6nK9RR+X1IX2pXa Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQSQYoZaRujHSSvxiNcUJsfcP1HhbwUCW755zAAKCRAUJsfcP1Hh b270AJ4vRyv4NIjn3zA2n1iWgt8O/dte9gCfUpXTdcz7QyRuHFbw5MBuTRFz74Y= =u0a4 -----END PGP SIGNATURE----- --f6nK9RR+X1IX2pXa-- From owner-freebsd-stable@freebsd.org Thu Oct 11 20:40:44 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3A1BF10C6CEB; Thu, 11 Oct 2018 20:40:44 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from smtp.vangyzen.net (hotblack.vangyzen.net [199.48.133.146]) (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 DD1C280E86; Thu, 11 Oct 2018 20:40:43 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from disco.vangyzen.net (unknown [70.97.188.230]) by smtp.vangyzen.net (Postfix) with ESMTPSA id C29F35648D; Thu, 11 Oct 2018 15:40:35 -0500 (CDT) Subject: Re: Good motherboard for Ryzen (first-gen) From: Eric van Gyzen To: freebsd-stable@FreeBSD.org, freebsd-current@freebsd.org References: <205656c3-52a5-a75f-c352-8bf923b47b1f@vangyzen.net> Message-ID: Date: Thu, 11 Oct 2018 15:40:34 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0.1 MIME-Version: 1.0 In-Reply-To: <205656c3-52a5-a75f-c352-8bf923b47b1f@vangyzen.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.27 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 Oct 2018 20:40:44 -0000 On 9/21/18 9:53 PM, Eric van Gyzen wrote: > I would like to build a Ryzen desktop.  Can anyone recommend a good > motherboard? > > I'm planning on a first-gen, because the second-gen has similar > stability problems as the first-gen had, and AMD hasn't released errata > for the second-gen yet (as far as I know...I would love to be wrong). > > I would like to be a cool kid with a Threadripper, but I can't justify > the cost, so I'm thinking maybe a Ryzen 7 with /only/ 8 cores.  :) > > Ideally, I want an Intel NIC, ECC memory support, and a 3-year warranty. Thanks for all the responses. They were very helpful. Here is what I ended up building: Mobo: ASUS Prime X470-Pro CPU: Ryzen 7 2700X 3.7GHz 8-Core RAM: Corsair Vengeance LPX 2 x 16GB DDR4-2666 PC4-21300 C16 Video: ASUS GeForce GTX 1060 6GB Disk: Samsung 970 EVO 500GB TLC NAND M.2 2280 PCIe NVMe 3.0 x4 PSU: EVGA SuperNOVA G3 750 Watt 80 Plus Gold ATX Fan: Cooler Master Hyper 212 EVO Universal CPU Cooler It's running FreeBSD head. BIOS version is 4018 (2018-07-12). So far, it has been perfectly stable. No crashes, no lockups. It has been my work-from-home desktop for just over a week now. I'm overclocking the memory a little, but nothing else. The NIC works. The sound works, though I've only tested the rear analog output. The video card works with the nvidia-driver, currently 390.87. It's driving two 2560x1440 monitors over HDMI. The only problem so far: I can't get NUMA enabled. I've set Memory Interleave to "off", but the BIOS still doesn't generate an ACPI SRAT table. I'm still working on this. Eric From owner-freebsd-stable@freebsd.org Fri Oct 12 09:50:47 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1F48110B44FB for ; Fri, 12 Oct 2018 09:50:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id B0B5C7AEB0 for ; Fri, 12 Oct 2018 09:50:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 75BE610B44FA; Fri, 12 Oct 2018 09:50:46 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3BC7E10B44F8 for ; Fri, 12 Oct 2018 09:50:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CF4EE7AEA7 for ; Fri, 12 Oct 2018 09:50:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) 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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 29C8617A07 for ; Fri, 12 Oct 2018 09:50:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w9C9ojTa088105 for ; Fri, 12 Oct 2018 09:50:45 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w9C9ojKr088104 for stable@FreeBSD.org; Fri, 12 Oct 2018 09:50:45 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: stable@FreeBSD.org Subject: [Bug 221146] [ixgbe] Problem with second laggport Date: Fri, 12 Oct 2018 09:50:41 +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: 11.1-STABLE X-Bugzilla-Keywords: IntelNetworking, regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: maciej@suszko.eu X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: net@FreeBSD.org X-Bugzilla-Flags: mfc-stable11? X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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.27 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 Oct 2018 09:50:47 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221146 Maciej Suszko changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |maciej@suszko.eu --- Comment #23 from Maciej Suszko --- Same problem here on Dell PowerEdge R740xd running 11.2-RELEASE-p4, sources modified to include latest mrsas drviers (DELL PERC H740P). root@host:~ # uname -a FreeBSD host 11.2-RELEASE-p4 FreeBSD 11.2-RELEASE-p4 #0 r338999M: Fri Sep 28 19:27:30 UTC 2018 root@host:/usr/obj/usr/src/sys/GENERIC amd64 root@host:~ # dmesg -a| grep '^ix[01]' ix0: po= rt 0x4020-0x403f mem 0x9d900000-0x9d9fffff,0x9da04000-0x9da07fff at device 0.0 numa-domain 0 on pci5 ix0: Using MSI-X interrupts with 9 vectors ix0: Ethernet address: xx:xx:xx:xx:xx:98 ix0: PCI Express Bus: Speed 5.0GT/s Width x8 ix0: netmap queues/slots: TX 8/2048, RX 8/2048 ix1: po= rt 0x4000-0x401f mem 0x9d800000-0x9d8fffff,0x9da00000-0x9da03fff at device 0.1 numa-domain 0 on pci5 ix1: Using MSI-X interrupts with 9 vectors ix1: Ethernet address: xx:xx:xx:xx:xx:9a ix1: PCI Express Bus: Speed 5.0GT/s Width x8 ix1: netmap queues/slots: TX 8/2048, RX 8/2048 ix0: link state changed to UP ix0: flags=3D8843 metric 0 mtu 1500 ix1: flags=3D8802 metric 0 mtu 1500 ix1: flags=3D8802 metric 0 mtu 1500 ix1: link state changed to UP ix1: link state changed to DOWN ix1: link state changed to UP I can attach ix1 to lagg0 later, after system boot... doing this within rc.= conf (in pair with ix0) does not work, ix1 shows 'no carrier' and it doesn't cha= nge it's state after removing from lagg0, interface down/up. root@host:~ # ifconfig ix0 ix0: flags=3D8843 metric 0 mtu 1500 =20=20=20=20=20=20=20 options=3De407bb ether xx:xx:xx:xx:xx:98 hwaddr xx:xx:xx:xx:xx:98 nd6 options=3D29 media: Ethernet autoselect (10Gbase-Twinax ) status: active root@host:~ # ifconfig ix1 ix1: flags=3D8843 metric 0 mtu 1500 =20=20=20=20=20=20=20 options=3De407bb ether xx:xx:xx:xx:xx:98 hwaddr xx:xx:xx:xx:xx:9a nd6 options=3D29 media: Ethernet autoselect (10Gbase-Twinax ) status: active root@host:~ # ifconfig lagg0 lagg0: flags=3D8843 metric 0 mtu 15= 00 =20=20=20=20 options=3De407bb ether xx:xx:xx:xx:xx:98 nd6 options=3D29 media: Ethernet autoselect status: active groups: lagg=20 laggproto lacp lagghash l2,l3,l4 laggport: ix0 flags=3D1c laggport: ix1 flags=3D1c --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-stable@freebsd.org Fri Oct 12 19:12:08 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 11FB910C77D6 for ; Fri, 12 Oct 2018 19:12:08 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from out.migadu.com (out.migadu.com [91.121.223.63]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.migadu.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7EF487191A for ; Fri, 12 Oct 2018 19:12:06 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: (Migadu outbound); Fri, 12 Oct 2018 19:11:58 +0000 Authentication-Results: out.migadu.com; auth=pass (plain) Received: from [192.168.1.141] ([62.122.208.146]) by out.migadu.com (Haraka/2.8.16) with ESMTPSA id 6C09D512-36A3-4285-9B54-87CF6DD0A4A7.1 envelope-from (authenticated bits=0) (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 verify=FAIL); Fri, 12 Oct 2018 19:11:58 +0000 Date: Fri, 12 Oct 2018 22:11:56 +0300 From: Greg V Subject: Re: Good motherboard for Ryzen (first-gen) To: Eric van Gyzen Cc: freebsd-stable@FreeBSD.org, freebsd-current@freebsd.org Message-Id: <1539371516.5420.0@smtp.migadu.com> In-Reply-To: References: <205656c3-52a5-a75f-c352-8bf923b47b1f@vangyzen.net> X-Mailer: geary/0.12.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed DKIM-Signature: v=1; a=rsa-sha256; bh=0KouCfhWhs7XBGME6p6ZoEjkvN/C0d8hlK7dx+H/yJg=; c=relaxed/simple; d=unrelenting.technology; h=from:subject:date:to; s=default; b=RwFZK5PvWfRUjsnEYQraLhbSPauQs8Rqlaw1iVpeZxI/dQsNjvtpLuyOtgoIs9jq8E8AJNxgQm+vdF0TcVBoACfnCBwxbSI9At/yJet4usUMT2wedh+81V1fWDpr9Y/ql4mvlsM2ExYcwW6CEwez7f0hZWTV9p2rdUsxzaT4DWA= X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.27 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 Oct 2018 19:12:08 -0000 On Thu, Oct 11, 2018 at 11:40 PM, Eric van Gyzen wrote: > On 9/21/18 9:53 PM, Eric van Gyzen wrote: >> I would like to build a Ryzen desktop. Can anyone recommend a good >> motherboard? >> >> I'm planning on a first-gen, because the second-gen has similar >> stability problems as the first-gen had, and AMD hasn't released >> errata for the second-gen yet (as far as I know...I would love to >> be wrong). >> >> I would like to be a cool kid with a Threadripper, but I can't >> justify the cost, so I'm thinking maybe a Ryzen 7 with /only/ 8 >> cores. :) >> >> Ideally, I want an Intel NIC, ECC memory support, and a 3-year >> warranty. > > Thanks for all the responses. They were very helpful. Here is what > I ended up building: > > Mobo: ASUS Prime X470-Pro > CPU: Ryzen 7 2700X 3.7GHz 8-Core > RAM: Corsair Vengeance LPX 2 x 16GB DDR4-2666 PC4-21300 C16 > Video: ASUS GeForce GTX 1060 6GB > Disk: Samsung 970 EVO 500GB TLC NAND M.2 2280 PCIe NVMe 3.0 x4 > PSU: EVGA SuperNOVA G3 750 Watt 80 Plus Gold ATX > Fan: Cooler Master Hyper 212 EVO Universal CPU Cooler > > It's running FreeBSD head. BIOS version is 4018 (2018-07-12). So > far, it has been perfectly stable. No crashes, no lockups. It has > been my work-from-home desktop for just over a week now. I'm > overclocking the memory a little, but nothing else. The NIC works. > The sound works, though I've only tested the rear analog output. The > video card works with the nvidia-driver, currently 390.87. It's > driving two 2560x1440 monitors over HDMI. > > The only problem so far: I can't get NUMA enabled. I've set Memory > Interleave to "off", but the BIOS still doesn't generate an ACPI SRAT > table. I'm still working on this. You won't ever get NUMA enabled. Because Ryzen 7 2700X is not a NUMA processor! :) Only Threadripper and EPYC are. Desktop Ryzen has a "slightly NUMA-like" thing going on, it's recognized as 'cache groups' in the line: FreeBSD/SMP: 1 package(s) x 2 cache groups x 4 core(s) x 2 hardware threads But it's not actual NUMA. From owner-freebsd-stable@freebsd.org Sat Oct 13 18:07:30 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8495710D156A; Sat, 13 Oct 2018 18:07:30 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gate2.funkthat.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 081E78456A; Sat, 13 Oct 2018 18:07:29 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (localhost [127.0.0.1]) by gold.funkthat.com (8.15.2/8.15.2) with ESMTPS id w9DI7KuJ048378 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 13 Oct 2018 11:07:20 -0700 (PDT) (envelope-from jmg@gold.funkthat.com) Received: (from jmg@localhost) by gold.funkthat.com (8.15.2/8.15.2/Submit) id w9DI7KBn048377; Sat, 13 Oct 2018 11:07:20 -0700 (PDT) (envelope-from jmg) Date: Sat, 13 Oct 2018 11:07:20 -0700 From: John-Mark Gurney To: Warner Losh Cc: Brooks Davis , FreeBSD-STABLE Mailing List , FreeBSD Net , "freebsd-arch@freebsd.org" , freebsd-fcp@freebsd.org Subject: Re: FCP-0101: Deprecating most 10/100 Ethernet drivers Message-ID: <20181013180720.GW75530@funkthat.com> Mail-Followup-To: Warner Losh , Brooks Davis , FreeBSD-STABLE Mailing List , FreeBSD Net , "freebsd-arch@freebsd.org" , freebsd-fcp@freebsd.org References: <20181004154744.79EA3154E@spqr.komquats.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 11.0-RELEASE-p7 amd64 X-PGP-Fingerprint: D87A 235F FB71 1F3F 55B7 ED9B D5FF 5A51 C0AC 3D65 X-Files: The truth is out there X-URL: https://www.funkthat.com/ X-Resume: https://www.funkthat.com/~jmg/resume.html X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? User-Agent: Mutt/1.6.1 (2016-04-27) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (gold.funkthat.com [127.0.0.1]); Sat, 13 Oct 2018 11:07:21 -0700 (PDT) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.27 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 Oct 2018 18:07:30 -0000 Warner Losh wrote this message on Thu, Oct 04, 2018 at 09:53 -0600: > On Thu, Oct 4, 2018 at 9:46 AM Cy Schubert > wrote: > > > I'm willing to help out with rl(4) as I have one here. Others, not > > scheduled for removal, that I can help one way or another are are NICs, > > including wireless, currently installed here. > > > > There's an iflib man page that's a decent place to start. The API has > evolved over time, so corrections to the man page would be welcome (and > committed as quickly as the freeze allows). I'm reading through the current > iflib drivers to see which one would be best to recommend. Can you recommend one? It'd be nice to just document which driver you should use as a reference in the iflib man page... I looked briefly at converting awg over to iflib, but the iflib man pages were very sparce in any text to describe what each function needs to do... It says it in very high level, which is useful if you already know what needs to be done.. for example: ifdi_tx_queues_alloc() Mandatory function that is called during iflib_attach to allocate transmit queues. vaddrs and paddrs are arrays of virtual and physical addresses respectively of the hardware transmit queues. ntxqs is the number of queues per qset. ntxqsets is the number of qsets. It says it allocates memory for the queue, but upon allocation where does it put the values? It sounds like vaddrs and paddrs arrays are already allocated and you just use these addresses... But there is no way I can write code from this description... Also, lots of terminology is missing, like what is a qset? -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not."