From owner-freebsd-stable@freebsd.org Sun Aug 26 00:16:26 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 6015E109A371; Sun, 26 Aug 2018 00:16:26 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wr1-x42d.google.com (mail-wr1-x42d.google.com [IPv6:2a00:1450:4864:20::42d]) (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 D2876871CF; Sun, 26 Aug 2018 00:16:25 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wr1-x42d.google.com with SMTP id m27-v6so10423544wrf.3; Sat, 25 Aug 2018 17:16:25 -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=4j7aGeQLzfvQz4qUxylgDccutJyq99cc2ESqnWhB2yw=; b=PChe7xcp+zuNCHKANGGQgxMwKEvR+jo+CvuYRxYwsb4VZHINzp+Idqn9yG03iDluRh HSAKU2qVfyv7V6rlsHYF1asxU8gjfLtESNDitks6niq4u2Ijk8HMv8t46gdJUV2kKZpb /9rHgiWy/rOODRpjoc3bRCOCP7JZE92ga0LlPCLsftmK93m16VI/oh91Fgn8F4b2Qzbx HT1eGV9+8O39yPElhTWNvqyRvH1lBriIw+8G73JYNVqZvOnWXSnPK+U0BHg9xvdDX533 lLBKaqjLKPKnWo2rOhhJQ+He0gYaJYIeMNkTABWEEJ4nDK1rPUgM7NAPnyox0rrQbas4 Vrbw== 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=4j7aGeQLzfvQz4qUxylgDccutJyq99cc2ESqnWhB2yw=; b=T47pbCkV2sQc1rMQqqbGk3y4PLuYMyBTEUpDCnu7Fdi+yqHqA2YzeYbbUFbiAZzwvy 9TAIKYIXHP2WY8ho7g+CfU02Ie9GgAJX7KJbrxLJ/9YvSApLvihxMroqRD/dfv1cQWvi pnhoYK2Ko5jSNVc5PS6JZitWdJIoL1MEmTlGFfODqBCquiIRnLF+n5a1VOFw1qPHXlyY Daw4pjJwOVTwDvp5oMYW6NoID1Y0JWr3uwpMWVTEBVdUd6BnmcnaNOgZLnTlWI6S51yL OpAIENSFvW0iN0C0/7o3uiw3GU1ifKq9stnV/KJR9/eHgKiutkq+cVOlF/0hPQLcwPqc p2mw== X-Gm-Message-State: APzg51CWqs6Et9/M2c3PgQka6lZqzLRr51KKdfqctUOthAycgywYJ+dq yxu76JFjLgYx50j2eSWtIk9mSSDuoojd1tqfOrs= X-Google-Smtp-Source: ANB0Vda9/nGM8S76TKSBtkrhCcU3oVntKvmXDob9O2XzV9dnR9VXt8NwkLa6L1sWxTA/m5/NG5dDmCk51uZx3rhG7Ac= X-Received: by 2002:adf:fc44:: with SMTP id e4-v6mr1633402wrs.9.1535242583733; Sat, 25 Aug 2018 17:16:23 -0700 (PDT) MIME-Version: 1.0 References: <20180824215302.ivfna55jtrtc5trg@freebsd480.station> <86k1oepbdr.fsf@next.des.no> In-Reply-To: From: Johannes Lundberg Date: Sun, 26 Aug 2018 01:16:13 +0100 Message-ID: Subject: Re: drm / drm2 removal in 12 To: blubee blubeeme Cc: Ali Abdallah , FreeBSD current , Warner Losh , des@des.no, freebsd-stable@freebsd.org, mmacy@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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, 26 Aug 2018 00:16:26 -0000 On Sun, Aug 26, 2018 at 00:25 blubee blubeeme wrote: > On Sun, Aug 26, 2018 at 2:08 AM Dag-Erling Sm=C3=B8rgrav wro= te: > > > blubee blubeeme writes: > > > True on both points my tone is just a reflection of attitudes of the > > > individuals that I am currently addressing. > > > > Well, congratulations on alienating absolutely everybody you have > > interacted with on this topic. > > > > > Some people enjoy making contributions w/o waving a banner constantly > > > wanting acknowledgement, a pat on the head and good job from everyone= . > > > > The only person I see constantly craving attention and validation from > > others here is you. > > > > > How far will core FreeBSD bend over backwards to accommodate these > > > devs. > > > > The core team does not decide what goes into the tree or not. The > > developers do. > > > > > This is the beauty of an open source project, we bring the best to th= e > > > table, [...] > > > > Who exactly is =E2=80=9Cwe=E2=80=9D here? You are not a member of the = project, you do > > not speak for the project, and after seeing how you treat our fellow > > developers, our friends, most of us want nothing to do with you. If > > can't live with that, I'm sure you can figure out how to install Linux. > > > > DES > > -- > > Dag-Erling Sm=C3=B8rgrav - des@des.no > > > Some on here want to attack my personality because they think that I am > abrasive, fine but that's not the issue. > > Some claim that they run the code and it works wonderful for them with no > issues, again that's lovely keep on running the code. > > Nevertheless let me restate the point that you guys are all seeming to > miss; If you can go out and build custom kernels with custom options and > out of mainline tree that's fine, keep doing that until you have somethin= g > that's production ready and as easy to install as the rest of FreeBSD > system. > > The graphics stack on FreeBSD is pretty bad as it stands but all the > documentation currently out there is about using it as it stands now. > > Why do you need to rip out the current graphics drivers which will break > systems for the vast majority of silent users who will not complain and > just leave? > > ---- A little background ---- > Do you know why Samsung, Motorola, Sony, LG, Nokia, etc... never update > their phones to the latest android version? > > It's because the Linux kernel is such a mess they know it's a waste of > resources to try. You should not have to ask how or why I know this but i= f > it's unclear I was in the field. > ----------------------------------- > > Now you guys who claim to only be hobbyist doing this in their free time > expect to maintain this when those companies with all their resources > cannot? > > Those 30,000 ports many of them bring bugs with them because of this > Linuxkpi stuff. Just recently there was a user who said google earth > doesn't work the answer was it doesn't work and that's that. > > They get ported and then get dropped so while the ports tree is large, if > you actually try to use some of those programs they are broken, maintenan= ce > hell for the developers and confusion for the users. > > Johannes Lundberg I know that you are one of the main working on this > linuxkpi stuff but anyone else is free to answer as well. > > Let's have an open discussion why do you need to remove the current > graphics stack to continue with your work? This has been discussed over and over on the mailing list and I don=E2=80= =99t think anyone wants to do it over again so please feel free to search the archives. You=E2=80=99re misinformed. We are not removing anything for anyone. We are= moving it to ports. =E2=80=9Cpkg install drm-legacy-kmod=E2=80=9D will install those drivers fo= r you that were earlier in base. I thought we have been clear about this but maybe we haven=E2=80=99t been clear enough. > _______________________________________________ > 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 Sun Aug 26 00:47: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 755BF109AF04; Sun, 26 Aug 2018 00:47:17 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-it0-x230.google.com (mail-it0-x230.google.com [IPv6:2607:f8b0:4001:c0b::230]) (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 D78338892E; Sun, 26 Aug 2018 00:47:16 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-it0-x230.google.com with SMTP id t69-v6so6402791itb.4; Sat, 25 Aug 2018 17:47: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=3VhG/phqoT4owal3849cmtrCqcxotWaDAG0lx6WWTH4=; b=fAZ0eWepJXttmnSTiqHidreLrjegf8PumFDfMqbofoOCPrNQTKc1yiWTD4fRmuiC7t NbVOi/FxW8kG1dGV4B+hLWr2IXAGFq2jfP+3vLwXQW3WekGJeKTYOQ73SGKRA15QGQ85 bnsO+fbWt9Qn/AnPflt2p2dvzHE6o2jD6N9khj0yPLRiFqS7pF9ryzce6qtUEkaq0D5/ TU++vYo47FrlsiTTybJGcL+iB3ByGVoGzhS9jyiL6tg5jNM9vlIYgJZXXtxVqC3Sa4OX yKN6lt8/HCtXO8TXz36aFpMHA12dTiuxe5Umy9DIHuAAsyB9S68TjUEdo16USR0j1063 n5dQ== 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=3VhG/phqoT4owal3849cmtrCqcxotWaDAG0lx6WWTH4=; b=NwGY8CnPgJexV9nR0TQk0XiPSYZHPXu+F8HKvWvt2gJRXbbqyzxFqInMMhNMbzj+ST tC+/mnX8PpsXfNHOWYAviZ+4+2XdyRwDG+b0pOR/fdUwJOENwL+hA8gZtZq6rZI3XSek Q5CyGRjYcddiqOJPzP3NTeG29lBBJ5IYpAWmZqSOtuY8AyujASt2UtqONV50V5JXOO/X 9IZGPdTV/sNrrAxPuRT9fJAFdivCkyPKHaW0kRkBGo8QOwKOQl8MEu5ju4Afi6JRa148 4+11H4MrBy6uc7Lzu2Ky1hApXjxmIotYc7Pqj0Mo7aFNnZ55RUEeJw0JtL6UUbCZ+2HG h4jg== X-Gm-Message-State: APzg51B7BzHwTlu0SzwQkdAczi4Vkof2E2VFB7+n/fzGaj40ymtZzCGw +YeUNUU6zzeXjxbsNX9/v1XSLW7Q+5HAcKWLU1k5SdSNLxs= X-Google-Smtp-Source: ANB0VdYBvOQE7UYs8AC2UeGJ8NGuwbNysoPbH/IFVRcY24NI9lx48ZeH1JHVv7qdU8IdhdDFBZxUx1xSeCDjl0NOG4Y= X-Received: by 2002:a24:d0d6:: with SMTP id m205-v6mr2684513itg.89.1535244436166; Sat, 25 Aug 2018 17:47:16 -0700 (PDT) MIME-Version: 1.0 References: <20180824215302.ivfna55jtrtc5trg@freebsd480.station> <86k1oepbdr.fsf@next.des.no> In-Reply-To: From: blubee blubeeme Date: Sun, 26 Aug 2018 08:47:04 +0800 Message-ID: Subject: Re: drm / drm2 removal in 12 To: Johannes Lundberg Cc: Ali Abdallah , FreeBSD current , Warner Losh , des@des.no, freebsd-stable@freebsd.org, mmacy@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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, 26 Aug 2018 00:47:17 -0000 On Sun, Aug 26, 2018 at 8:16 AM Johannes Lundberg wrote: > > > On Sun, Aug 26, 2018 at 00:25 blubee blubeeme wrote= : > >> On Sun, Aug 26, 2018 at 2:08 AM Dag-Erling Sm=C3=B8rgrav wr= ote: >> >> > blubee blubeeme writes: >> > > True on both points my tone is just a reflection of attitudes of the >> > > individuals that I am currently addressing. >> > >> > Well, congratulations on alienating absolutely everybody you have >> > interacted with on this topic. >> > >> > > Some people enjoy making contributions w/o waving a banner constantl= y >> > > wanting acknowledgement, a pat on the head and good job from everyon= e. >> > >> > The only person I see constantly craving attention and validation from >> > others here is you. >> > >> > > How far will core FreeBSD bend over backwards to accommodate these >> > > devs. >> > >> > The core team does not decide what goes into the tree or not. The >> > developers do. >> > >> > > This is the beauty of an open source project, we bring the best to t= he >> > > table, [...] >> > >> > Who exactly is =E2=80=9Cwe=E2=80=9D here? You are not a member of the= project, you do >> > not speak for the project, and after seeing how you treat our fellow >> > developers, our friends, most of us want nothing to do with you. If >> > can't live with that, I'm sure you can figure out how to install Linux= . >> > >> > DES >> > -- >> > Dag-Erling Sm=C3=B8rgrav - des@des.no >> >> >> Some on here want to attack my personality because they think that I am >> abrasive, fine but that's not the issue. >> >> Some claim that they run the code and it works wonderful for them with n= o >> issues, again that's lovely keep on running the code. >> >> Nevertheless let me restate the point that you guys are all seeming to >> miss; If you can go out and build custom kernels with custom options and >> out of mainline tree that's fine, keep doing that until you have somethi= ng >> that's production ready and as easy to install as the rest of FreeBSD >> system. >> >> The graphics stack on FreeBSD is pretty bad as it stands but all the >> documentation currently out there is about using it as it stands now. >> >> Why do you need to rip out the current graphics drivers which will break >> systems for the vast majority of silent users who will not complain and >> just leave? >> >> ---- A little background ---- >> Do you know why Samsung, Motorola, Sony, LG, Nokia, etc... never update >> their phones to the latest android version? >> >> It's because the Linux kernel is such a mess they know it's a waste of >> resources to try. You should not have to ask how or why I know this but = if >> it's unclear I was in the field. >> ----------------------------------- >> >> Now you guys who claim to only be hobbyist doing this in their free time >> expect to maintain this when those companies with all their resources >> cannot? >> >> Those 30,000 ports many of them bring bugs with them because of this >> Linuxkpi stuff. Just recently there was a user who said google earth >> doesn't work the answer was it doesn't work and that's that. >> >> They get ported and then get dropped so while the ports tree is large, i= f >> you actually try to use some of those programs they are broken, >> maintenance >> hell for the developers and confusion for the users. >> >> Johannes Lundberg I know that you are one of the main working on this >> linuxkpi stuff but anyone else is free to answer as well. >> >> Let's have an open discussion why do you need to remove the current >> graphics stack to continue with your work? > > > This has been discussed over and over on the mailing list and I don=E2=80= =99t > think anyone wants to do it over again so please feel free to search the > archives. > > You=E2=80=99re misinformed. We are not removing anything for anyone. We a= re moving > it to ports. > =E2=80=9Cpkg install drm-legacy-kmod=E2=80=9D will install those drivers = for you that were > earlier in base. I thought we have been clear about this but maybe we > haven=E2=80=99t been clear enough. > > > >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.or= g >> " >> > Have you or anyone working on this drm-legacy-kmod stuff done any testing= s of how this will affect current users? 1) Take a [test] system with the current graphics stack installed and working. 2) Apply your patches to remove the drm from base to create a port 3) update the working [test] system after applying your changes How does your changes affect a [test] system that is already up and running= ? Have any of you guys tried that? Do you have any documentation on how it'll affect users. You guys want to remove things from the current system but you come with; it works for us hobbyists. Where do users go to get steps to do all of this stuff? You've repeatedly said what you want to do sure, but have you tested it? From owner-freebsd-stable@freebsd.org Sun Aug 26 01:08: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 15C1F109B796; Sun, 26 Aug 2018 01:08:42 +0000 (UTC) (envelope-from prvs=0776302e18=pmcnary@cameron.net) Received: from northmo.net (mailcleaner1.northmo.net [208.110.72.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B5D238938D; Sun, 26 Aug 2018 01:08:40 +0000 (UTC) (envelope-from prvs=0776302e18=pmcnary@cameron.net) Received: from [198.207.210.77] by northmo.net stage1 with esmtpsa (Exim MailCleaner) id 1ftjX7-0001pm-3L from ; Sat, 25 Aug 2018 20:08:01 -0500 Subject: Re: drm / drm2 removal in 12 To: blubee blubeeme , Johannes Lundberg Cc: freebsd-stable@freebsd.org, mmacy@freebsd.org, Ali Abdallah , FreeBSD current , des@des.no References: <20180824215302.ivfna55jtrtc5trg@freebsd480.station> <86k1oepbdr.fsf@next.des.no> From: Paul McNary Message-ID: <180f8f99-5fa1-1411-59e6-856e3ebc370c@cameron.net> Date: Sat, 25 Aug 2018 20:08:05 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-MailCleaner-RDNS: invalid reverse DNS for 198.207.210.77 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, 26 Aug 2018 01:08:42 -0000 I think you can pay XinuOS to support FreeBSD in a LTS situation. It is just like linux where you have to pay Red Hat, Suse, etc. They break things even with point releases. Suse majorly screwed with video drivers back in the 9.x series. Totally broke major release. Their answer then was pay us or re-install bare metal and figure it out on your own. Other wise linux has always been, you get what you get for free. BSD is the same. If you are lucky some one like red hat, suse, XinuOS will be supporting and make their notes public, otherwise the OSS model doesn't include anything more than community support for what ever that is worth. I just upgraded a system from FreeBSD 9.x to 12.x, it took 2 weeks and several incremental upgrades sometimes to multiple point releases with in a major release. There is nothing really for free. On 8/25/2018 7:47 PM, blubee blubeeme wrote: > On Sun, Aug 26, 2018 at 8:16 AM Johannes Lundberg > wrote: > >> >> On Sun, Aug 26, 2018 at 00:25 blubee blubeeme wrote: >> >>> On Sun, Aug 26, 2018 at 2:08 AM Dag-Erling Smørgrav wrote: >>> >>>> blubee blubeeme writes: >>>>> True on both points my tone is just a reflection of attitudes of the >>>>> individuals that I am currently addressing. >>>> Well, congratulations on alienating absolutely everybody you have >>>> interacted with on this topic. >>>> >>>>> Some people enjoy making contributions w/o waving a banner constantly >>>>> wanting acknowledgement, a pat on the head and good job from everyone. >>>> The only person I see constantly craving attention and validation from >>>> others here is you. >>>> >>>>> How far will core FreeBSD bend over backwards to accommodate these >>>>> devs. >>>> The core team does not decide what goes into the tree or not. The >>>> developers do. >>>> >>>>> This is the beauty of an open source project, we bring the best to the >>>>> table, [...] >>>> Who exactly is “we” here? You are not a member of the project, you do >>>> not speak for the project, and after seeing how you treat our fellow >>>> developers, our friends, most of us want nothing to do with you. If >>>> can't live with that, I'm sure you can figure out how to install Linux. >>>> >>>> DES >>>> -- >>>> Dag-Erling Smørgrav - des@des.no >>> >>> Some on here want to attack my personality because they think that I am >>> abrasive, fine but that's not the issue. >>> >>> Some claim that they run the code and it works wonderful for them with no >>> issues, again that's lovely keep on running the code. >>> >>> Nevertheless let me restate the point that you guys are all seeming to >>> miss; If you can go out and build custom kernels with custom options and >>> out of mainline tree that's fine, keep doing that until you have something >>> that's production ready and as easy to install as the rest of FreeBSD >>> system. >>> >>> The graphics stack on FreeBSD is pretty bad as it stands but all the >>> documentation currently out there is about using it as it stands now. >>> >>> Why do you need to rip out the current graphics drivers which will break >>> systems for the vast majority of silent users who will not complain and >>> just leave? >>> >>> ---- A little background ---- >>> Do you know why Samsung, Motorola, Sony, LG, Nokia, etc... never update >>> their phones to the latest android version? >>> >>> It's because the Linux kernel is such a mess they know it's a waste of >>> resources to try. You should not have to ask how or why I know this but if >>> it's unclear I was in the field. >>> ----------------------------------- >>> >>> Now you guys who claim to only be hobbyist doing this in their free time >>> expect to maintain this when those companies with all their resources >>> cannot? >>> >>> Those 30,000 ports many of them bring bugs with them because of this >>> Linuxkpi stuff. Just recently there was a user who said google earth >>> doesn't work the answer was it doesn't work and that's that. >>> >>> They get ported and then get dropped so while the ports tree is large, if >>> you actually try to use some of those programs they are broken, >>> maintenance >>> hell for the developers and confusion for the users. >>> >>> Johannes Lundberg I know that you are one of the main working on this >>> linuxkpi stuff but anyone else is free to answer as well. >>> >>> Let's have an open discussion why do you need to remove the current >>> graphics stack to continue with your work? >> >> This has been discussed over and over on the mailing list and I don’t >> think anyone wants to do it over again so please feel free to search the >> archives. >> >> You’re misinformed. We are not removing anything for anyone. We are moving >> it to ports. >> “pkg install drm-legacy-kmod” will install those drivers for you that were >> earlier in base. I thought we have been clear about this but maybe we >> haven’t been clear enough. >> >> >> >>> _______________________________________________ >>> 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 >>> " >>> >> Have you or anyone working on this drm-legacy-kmod stuff done any testings > of how this will affect current users? > > 1) Take a [test] system with the current graphics stack installed and > working. > 2) Apply your patches to remove the drm from base to create a port > 3) update the working [test] system after applying your changes > > How does your changes affect a [test] system that is already up and running? > > Have any of you guys tried that? Do you have any documentation on how it'll > affect users. > > You guys want to remove things from the current system but you come with; > it works for us hobbyists. > Where do users go to get steps to do all of this stuff? > > You've repeatedly said what you want to do sure, but have you tested it? > _______________________________________________ > 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 Aug 26 01:20: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 D253E109C124; Sun, 26 Aug 2018 01:20:51 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com [IPv6:2607:f8b0:4001:c06::22b]) (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 6334289A74; Sun, 26 Aug 2018 01:20:51 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-io0-x22b.google.com with SMTP id n18-v6so10059369ioa.9; Sat, 25 Aug 2018 18:20: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=MT7S3LL4hXws9ZtmbVTAia0Ytg/7VFRIjDPm/LtAI4s=; b=uJIitvdrQYVxK0GJFjA+M8mA1JI34QZ5ASfQwo9cskRYJj5Yk3itvgWzLjGr3XyZsR e6lKkwoOui+IEaC3XyrgRINeNbRj3MaNcqgHjSkTmb86V8e2O0+YaXhocjL5TqE6tdl1 D8wj6ye1Q/mAsmhVmRMuRJLUSfOvmtPjWUeRwna8BmoLFXBRZKRF5sMjLWT6YuS+pE0y Pcu/9YWInZ0YPYsWiB6JGWVYDJXA++2UwK/39h+GIEkYrXnRc3SavWh7HUhGgsoTjqak Nut7h1+XgppYaWQgywKVkhQoiVEbtIDdwe9ENNpFvBnPFligQOVdVL6vE//T+xVEBsJq NLSw== 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=MT7S3LL4hXws9ZtmbVTAia0Ytg/7VFRIjDPm/LtAI4s=; b=Fq3JA859f1cLf4mir26JRnir/z55N8Vth1xny/OmjQyNKuUYas/6CB1e+euvvSboio JyV3pBr+PgJ9IAPh+SMJQP004h+CktU3xys5z8CaWT4Beuq4B1+W7PcD9b6XZ81sVH6v carwRgWiDN2uhoZQDZhxgt0EaLt1HPBcchzZ/JT8ytrKUzSyCxLqIvQNuqww8hTkOhEP 2fJewEEX4HqENy2I/p0cZmGodLNw7Yab8C81gEpndENHk8bEaCYRBFm/4KsGxrzI8+B1 zTTVR//BPRJahR/BAQ42mW4wVuGWVaimFm0AFwFgHCJjLJM42H5dJ5VgL+D3xi7WYb+8 Jp8A== X-Gm-Message-State: APzg51BdKd59L2uAqN+CWUglgX++dbgKAdJ6yp/ynJNLnvAJ7x8PYCBe IotJBlraiOa6S9LqI+Vyo88Sn2B9ofKlb/BGRhs= X-Google-Smtp-Source: ANB0VdYd8QPnlPdsWh4xlOeZ2R8qPHiAqyAaIV41WlJM1l77Pc4f7kVFqgv9VDS+NgweOGyxHy18QhOTSdXcyzQBvZ8= X-Received: by 2002:a6b:b546:: with SMTP id e67-v6mr5933132iof.179.1535246450731; Sat, 25 Aug 2018 18:20:50 -0700 (PDT) MIME-Version: 1.0 References: <20180824215302.ivfna55jtrtc5trg@freebsd480.station> <86k1oepbdr.fsf@next.des.no> <180f8f99-5fa1-1411-59e6-856e3ebc370c@cameron.net> In-Reply-To: <180f8f99-5fa1-1411-59e6-856e3ebc370c@cameron.net> From: blubee blubeeme Date: Sun, 26 Aug 2018 09:20:39 +0800 Message-ID: Subject: Re: drm / drm2 removal in 12 To: pmcnary@cameron.net Cc: Johannes Lundberg , freebsd-stable@freebsd.org, mmacy@freebsd.org, Ali Abdallah , FreeBSD current , =?UTF-8?Q?Dag=2DErling_Sm=C3=B8rgrav?= Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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, 26 Aug 2018 01:20:52 -0000 On Sun, Aug 26, 2018 at 9:08 AM Paul McNary wrote: > I think you can pay XinuOS to support FreeBSD in a LTS situation. > It is just like linux where you have to pay Red Hat, Suse, etc. > They break things even with point releases. Suse majorly > screwed with video drivers back in the 9.x series. Totally > broke major release. Their answer then was pay us or > re-install bare metal and figure it out on your own. > Other wise linux has always been, you get what you get for free. > BSD is the same. If you are lucky some one like red hat, suse, XinuOS > will be supporting and make their notes public, otherwise the > OSS model doesn't include anything more than community support > for what ever that is worth. > I just upgraded a system from FreeBSD 9.x to 12.x, it took 2 weeks and > several incremental upgrades sometimes to multiple point releases > with in a major release. There is nothing really for free. > > > On 8/25/2018 7:47 PM, blubee blubeeme wrote: > > On Sun, Aug 26, 2018 at 8:16 AM Johannes Lundberg > > wrote: > > > >> > >> On Sun, Aug 26, 2018 at 00:25 blubee blubeeme > wrote: > >> > >>> On Sun, Aug 26, 2018 at 2:08 AM Dag-Erling Sm=C3=B8rgrav > wrote: > >>> > >>>> blubee blubeeme writes: > >>>>> True on both points my tone is just a reflection of attitudes of th= e > >>>>> individuals that I am currently addressing. > >>>> Well, congratulations on alienating absolutely everybody you have > >>>> interacted with on this topic. > >>>> > >>>>> Some people enjoy making contributions w/o waving a banner constant= ly > >>>>> wanting acknowledgement, a pat on the head and good job from > everyone. > >>>> The only person I see constantly craving attention and validation fr= om > >>>> others here is you. > >>>> > >>>>> How far will core FreeBSD bend over backwards to accommodate these > >>>>> devs. > >>>> The core team does not decide what goes into the tree or not. The > >>>> developers do. > >>>> > >>>>> This is the beauty of an open source project, we bring the best to > the > >>>>> table, [...] > >>>> Who exactly is =E2=80=9Cwe=E2=80=9D here? You are not a member of t= he project, you do > >>>> not speak for the project, and after seeing how you treat our fellow > >>>> developers, our friends, most of us want nothing to do with you. If > >>>> can't live with that, I'm sure you can figure out how to install > Linux. > >>>> > >>>> DES > >>>> -- > >>>> Dag-Erling Sm=C3=B8rgrav - des@des.no > >>> > >>> Some on here want to attack my personality because they think that I = am > >>> abrasive, fine but that's not the issue. > >>> > >>> Some claim that they run the code and it works wonderful for them wit= h > no > >>> issues, again that's lovely keep on running the code. > >>> > >>> Nevertheless let me restate the point that you guys are all seeming > to > >>> miss; If you can go out and build custom kernels with custom options > and > >>> out of mainline tree that's fine, keep doing that until you have > something > >>> that's production ready and as easy to install as the rest of FreeBSD > >>> system. > >>> > >>> The graphics stack on FreeBSD is pretty bad as it stands but all the > >>> documentation currently out there is about using it as it stands now. > >>> > >>> Why do you need to rip out the current graphics drivers which will > break > >>> systems for the vast majority of silent users who will not complain a= nd > >>> just leave? > >>> > >>> ---- A little background ---- > >>> Do you know why Samsung, Motorola, Sony, LG, Nokia, etc... never upda= te > >>> their phones to the latest android version? > >>> > >>> It's because the Linux kernel is such a mess they know it's a waste o= f > >>> resources to try. You should not have to ask how or why I know this > but if > >>> it's unclear I was in the field. > >>> ----------------------------------- > >>> > >>> Now you guys who claim to only be hobbyist doing this in their free > time > >>> expect to maintain this when those companies with all their resources > >>> cannot? > >>> > >>> Those 30,000 ports many of them bring bugs with them because of this > >>> Linuxkpi stuff. Just recently there was a user who said google earth > >>> doesn't work the answer was it doesn't work and that's that. > >>> > >>> They get ported and then get dropped so while the ports tree is large= , > if > >>> you actually try to use some of those programs they are broken, > >>> maintenance > >>> hell for the developers and confusion for the users. > >>> > >>> Johannes Lundberg I know that you are one of the main working on this > >>> linuxkpi stuff but anyone else is free to answer as well. > >>> > >>> Let's have an open discussion why do you need to remove the current > >>> graphics stack to continue with your work? > >> > >> This has been discussed over and over on the mailing list and I don=E2= =80=99t > >> think anyone wants to do it over again so please feel free to search t= he > >> archives. > >> > >> You=E2=80=99re misinformed. We are not removing anything for anyone. W= e are > moving > >> it to ports. > >> =E2=80=9Cpkg install drm-legacy-kmod=E2=80=9D will install those drive= rs for you that > were > >> earlier in base. I thought we have been clear about this but maybe we > >> haven=E2=80=99t been clear enough. > >> > >> > >> > >>> _______________________________________________ > >>> 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 > >>> " > >>> > >> Have you or anyone working on this drm-legacy-kmod stuff done any > testings > > of how this will affect current users? > > > > 1) Take a [test] system with the current graphics stack installed and > > working. > > 2) Apply your patches to remove the drm from base to create a port > > 3) update the working [test] system after applying your changes > > > > How does your changes affect a [test] system that is already up and > running? > > > > Have any of you guys tried that? Do you have any documentation on how > it'll > > affect users. > > > > You guys want to remove things from the current system but you come wit= h; > > it works for us hobbyists. > > Where do users go to get steps to do all of this stuff? > > > > You've repeatedly said what you want to do sure, but have you tested it= ? > > _______________________________________________ > > freebsd-stable@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.or= g > " > > I'll just post this again to try and keep the focus on the issue at hand. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Have you or anyone working on this drm-legacy-kmod stuff done any testings of how this will affect current users? 1) Take a [test] system with the current graphics stack installed and working. 2) Apply your patches to remove the drm from base to create a port 3) update the working [test] system after applying your changes How does your changes affect a [test] system that is already up and running= ? Have any of you guys tried that? Do you have any documentation on how it'll affect users. You guys want to remove things from the current system but you come with; it works for us hobbyists. Where do users go to get steps to do all of this stuff? You've repeatedly said what you want to do sure, but have you tested it? From owner-freebsd-stable@freebsd.org Sun Aug 26 02:22:12 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 2FAA7109E468; Sun, 26 Aug 2018 02:22:12 +0000 (UTC) (envelope-from randy@psg.com) Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 D579D8BC66; Sun, 26 Aug 2018 02:22:11 +0000 (UTC) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from ) id 1ftkgp-0001Zc-7d; Sun, 26 Aug 2018 02:22:07 +0000 Date: Sat, 25 Aug 2018 19:22:06 -0700 Message-ID: From: Randy Bush To: blubee blubeeme Cc: pmcnary@cameron.net, Johannes Lundberg , freebsd-stable@freebsd.org, mmacy@freebsd.org, Ali Abdallah , FreeBSD current , =?ISO-8859-1?Q?=22Dag-Erling_Sm=F8rgrav=22?= Subject: Re: drm / drm2 removal in 12 In-Reply-To: References: <20180824215302.ivfna55jtrtc5trg@freebsd480.station> <86k1oepbdr.fsf@next.des.no> <180f8f99-5fa1-1411-59e6-856e3ebc370c@cameron.net> User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/25.3 Mule/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII 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, 26 Aug 2018 02:22:12 -0000 > I'll just post this again to try and keep the focus on the issue at hand. plonk From owner-freebsd-stable@freebsd.org Sun Aug 26 02:34:55 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 DD9B9109ED18; Sun, 26 Aug 2018 02:34:55 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [18.222.6.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7E0D18C5E6; Sun, 26 Aug 2018 02:34:55 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (unknown [18.188.142.31]) by mail.soaustin.net (Postfix) with ESMTPSA id E1A3D13B37; Sun, 26 Aug 2018 02:34:53 +0000 (UTC) Date: Sun, 26 Aug 2018 02:34:52 +0000 From: Mark Linimon To: Randy Bush Cc: blubee blubeeme , pmcnary@cameron.net, Johannes Lundberg , freebsd-stable@freebsd.org, mmacy@freebsd.org, Ali Abdallah , FreeBSD current , =?iso-8859-1?Q?=22Dag-Erling_Sm=F8rgrav=22?= Subject: Re: drm / drm2 removal in 12 Message-ID: <20180826023452.GA17215@lonesome.com> References: <86k1oepbdr.fsf@next.des.no> <180f8f99-5fa1-1411-59e6-856e3ebc370c@cameron.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) 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, 26 Aug 2018 02:34:56 -0000 On Sat, Aug 25, 2018 at 07:22:06PM -0700, Randy Bush wrote: > plonk Indeed. I encourage everyone else to do the same. I'm far too old for proof-by-repetition. mcl From owner-freebsd-stable@freebsd.org Sun Aug 26 08:32:04 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 653EB106D847; Sun, 26 Aug 2018 08:32:04 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::2]) (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 F144E76525; Sun, 26 Aug 2018 08:32:03 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 775862600C9; Sun, 26 Aug 2018 10:32:00 +0200 (CEST) Subject: Re: drm / drm2 removal in 12 To: blubee blubeeme , pmcnary@cameron.net Cc: Johannes Lundberg , freebsd-stable@freebsd.org, mmacy@freebsd.org, Ali Abdallah , FreeBSD current , =?UTF-8?Q?Dag-Erling_Sm=c3=b8rgrav?= References: <20180824215302.ivfna55jtrtc5trg@freebsd480.station> <86k1oepbdr.fsf@next.des.no> <180f8f99-5fa1-1411-59e6-856e3ebc370c@cameron.net> From: Hans Petter Selasky Message-ID: Date: Sun, 26 Aug 2018 10:31:36 +0200 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; format=flowed Content-Language: en-US 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, 26 Aug 2018 08:32:04 -0000 On 8/26/18 3:20 AM, blubee blubeeme wrote: > Have you or anyone working on this drm-legacy-kmod stuff done any testings > of how this will affect current users? Hi Blubee, Are you here to try to stir a conflict? If so that is not appreciated. --HPS From owner-freebsd-stable@freebsd.org Sun Aug 26 10:42:01 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 B2BB61070EA0; Sun, 26 Aug 2018 10:42:01 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-it0-x22b.google.com (mail-it0-x22b.google.com [IPv6:2607:f8b0:4001:c0b::22b]) (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 4D4047A737; Sun, 26 Aug 2018 10:42:01 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-it0-x22b.google.com with SMTP id p16-v6so7128931itp.1; Sun, 26 Aug 2018 03:42:01 -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=Tkp9PepJttBCiS8JZcHevQE5tZPsx+AhTrGI24qLOOM=; b=PDeNJ15faEL6pCaGZlStjbYM2goNBZ0/RUcsO/YcIq3yg28wFKfU1HefKrVjlqnavo dY2e0ZH+0xLowGpw+a12BiyzH57YHnaryLa8DrpWHriqH76eDvdBxK6lzhieuER7ef1E fanrmJnWNZkOoh35O4TAigcFNAl+O13EqWL2M1pv9juJaHc4+RAcj7m0vbmPOKObgx4x CJvuBoPySxPjQK9tXXA0Feaxz+icDJ/SVQz0f2sViVa/XcgaId4CKATgZr43c+TzEKkL I21R5kLJ8Oidq97GrTMWqX92t4zsGAjKbXzT5cwglh25xxEqtvk1Ub6b5ZHunHCMYWHP xKCA== 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=Tkp9PepJttBCiS8JZcHevQE5tZPsx+AhTrGI24qLOOM=; b=Zktf5WdKSVaa+QGNX1lP+aBsFOMRExvynbAg0sehI/kg19qQwsVY+Uk0yep/Ym3Z85 1jPUgA7wYJ5FGAko6Br6Ha9ZTTiovkW6qc1V6aeYBc0Ge/scG9NV+nCV1Y+cZ22PiyqE mr4IYGt9YAJ79UNxGrsGag2dvSTkBnEKS7tBpWbiC47qLCJDF1oIj9tBr4pGR/CAmT/f I3JquMUKQGKJuYiIjKjqqvNMYO6XSnYhB3EMudP91we/rptTYoOad25Z6PLtPvsJLzSN HDzBrv/1nGuDhyONxPNKCwJw9FaeHRb+q+VX0LVjIIIE+J/PGO//MhvzJeVihbi7HX09 lcow== X-Gm-Message-State: APzg51ABWKj9VOYUbwlBENuVoafM/kaf9OTBxaB9Iq3DVfLtv7vc4mpB BtnBFsQau9ajSqSCbghhM0ulaJkJqoG1c8YhnUg= X-Google-Smtp-Source: ANB0VdZEXp58m0JXdOuj2EhgZoDgujzPZ0HcxLWtpl140k/M6LHvDJ3ynNXAl/0cFZPfMhgF3YwejXdGPfWH7osx/aQ= X-Received: by 2002:a02:1643:: with SMTP id a64-v6mr6867800jaa.133.1535280120561; Sun, 26 Aug 2018 03:42:00 -0700 (PDT) MIME-Version: 1.0 References: <20180824215302.ivfna55jtrtc5trg@freebsd480.station> <86k1oepbdr.fsf@next.des.no> <180f8f99-5fa1-1411-59e6-856e3ebc370c@cameron.net> In-Reply-To: From: blubee blubeeme Date: Sun, 26 Aug 2018 18:41:48 +0800 Message-ID: Subject: Re: drm / drm2 removal in 12 To: Hans Petter Selasky Cc: pmcnary@cameron.net, Johannes Lundberg , freebsd-stable@freebsd.org, mmacy@freebsd.org, Ali Abdallah , FreeBSD current , =?UTF-8?Q?Dag=2DErling_Sm=C3=B8rgrav?= 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, 26 Aug 2018 10:42:01 -0000 On Sun, Aug 26, 2018 at 4:32 PM Hans Petter Selasky wrote: > On 8/26/18 3:20 AM, blubee blubeeme wrote: > > Have you or anyone working on this drm-legacy-kmod stuff done any > testings > > of how this will affect current users? > > Hi Blubee, > > Are you here to try to stir a conflict? > If so that is not appreciated. > > --HPS > Hans, you of all people should know that's not true. I would think that trying to sneak in code during a code freeze that would break the release. Forcing the core devs to revert those changes and having to dust off old policies to try to keep you guys in check is what's stirring up conflicts, but hey; what do I know? It's really sad state when capable engineers are so obsessed with something that they cannot see the forest for the trees. Try to step away from the canvas and look at the big picture. If you don't mind me asking, Hans care to answer these questions below? 1) Take a [test] system with the current graphics stack installed and working. 2) Apply your patches to remove the drm from base to create a port 3) update the working [test] system after applying your changes How does your changes affect a [test] system that is already up and running? Have any of you guys tried that? Do you have any documentation on how it'll affect users. You guys want to remove things from the current system but you come with; it works for us hobbyists. Where do users go to get steps to do all of this stuff? You've repeatedly said what you want to do sure, but have you tested it? From owner-freebsd-stable@freebsd.org Sun Aug 26 11:20:15 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 2D2F610723AB; Sun, 26 Aug 2018 11:20:15 +0000 (UTC) (envelope-from meowthink@gmail.com) Received: from mail-oi0-x243.google.com (mail-oi0-x243.google.com [IPv6:2607:f8b0:4003:c06::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 92ABC7BF63; Sun, 26 Aug 2018 11:20:14 +0000 (UTC) (envelope-from meowthink@gmail.com) Received: by mail-oi0-x243.google.com with SMTP id x197-v6so4926177oix.5; Sun, 26 Aug 2018 04:20:14 -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=+6+plC/3fU8Kp1Osd/rb3wCKOICD0IZbAmKqk657Uh0=; b=QciaCnpdonODb0IF57MM49R/oUxCbg+IIqVfGeqKLBgx9GIjvhLwu/VgBupXgEk8wt sP2pZhX5SsEZL3PZdZnxkQtnJNDog8gB/gYOOMGKdn9G+v/O5N8Kvh8gDnFsKqve4lnM ErsFlftL3nSnluLhhHFUjxmVvaWyd4Xu/NDsqLuhpLzkt7scNPBenL9ot9A0t/GVXf9T 5ekHq2lQLuf0hy6yUmq+V5TQ1Cp/qBhi9c0XAnnPFOYnI2JTWNrhJJgG4CL7mhKRDdIQ uxssiLbhBdPPoNWq1hNayFPhk9HrEhL8YPi0AqTZIeW6GtqA8Tx9Z/N3UQDLe5ADhljb 3/2Q== 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=+6+plC/3fU8Kp1Osd/rb3wCKOICD0IZbAmKqk657Uh0=; b=BmPpVBCZVsn84jjK1F+l76/kDVYM8sAo7OsiN6Dt1RLAxCb8lXZvGsLJR9TGghWAt9 xbyjp44WjBWZGNkzJaiSim8KRv/oqMYOteo5RFXS9oKIY6DL6Hf94F+b3ZSOp7IMYsdC ogll12IjgQX/rtqSwex5jQ3ZcnSKioa0PLgtDTpDWOvgDvpOiAYSf0gjxcLI+6AzBY7s obnelzhGV/4TIM7g6XOMQcCKafUJCelf2r4m+tJuURRIZHCLc1oPFtxikb92qceEEBmh 5MLCM/BfPUIxOb88MAG0HUa7X2YulnSajIXvwMlXZ+ABijjkApzujUvslZSxMS7dLjMM ibTQ== X-Gm-Message-State: APzg51A6gHNRCYayegUO7322LTRW3cVNgceai5OK4Hi4eixhrC16e/34 AFStSkhram+K6zOKSuqZngC83b7K8gCUcJ4XFrqaMzp1 X-Google-Smtp-Source: ANB0VdbkRqzDGobf2fdslj2j+uGsiDmzbekXSadn68lHOadtPPsJWT92MdUAcIingPKeq7mlezRl9swIAIYaSXbYmlI= X-Received: by 2002:aca:4802:: with SMTP id v2-v6mr8802835oia.259.1535282413258; Sun, 26 Aug 2018 04:20:13 -0700 (PDT) MIME-Version: 1.0 From: Meowthink Date: Sun, 26 Aug 2018 19:20:00 +0800 Message-ID: Subject: Help diagnose my Ryzen build problem To: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" 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, 26 Aug 2018 11:20:15 -0000 Hello all, Recently I tried to build up a Ryzen system and run FreeBSD on it. CPU: AMD Ryzen 5 2400G with Radeon Vega Graphics (0x810f10) Mobo: Asrock Fatal1ty AB350 Gaming-ITX/ac ( with up-to-date BIOS with PinnaclePI-AM4_1.0.0.4, microcode 0x810100b ) Mem: 2x Crucial 16GB DDR4-2400 EUDIMM CL17 ( ECC Unregistered but ECC actually won't work :( ) But the system is unstable - it can't last few days even is nearly idle. System panics even at midnight. It almost panic while or after I built something large. Surprisly I didn't encourage a user program fault, bad binaries built etc., panics only. Then I tried lots of BIOS settings e.g. SMT, C6 idle current, underclock RAM, but none seems effect. It could pass memtest86 V7.5 without error, or various benchmarks under Windows. thus I think the problem is not in the hardware but software. In the mean time, I realized that the rate of irqs from xhci0 are too high - it's about 1998/s. I found [1] and tried to MFC r331665. It didn't fix the problem though, but disabling that bluetooth module stops the irq storm, after all. Then the system lasts much longer before panic. It eventually can compile ports tree, build the world, scrub the zpool, all done without annoying reboots. Then I assume this is [2] related? So I also tried cpuctl, bounding all processes to 2-7. But the problem is still there, only the chance become very low. It still panics occasionally, idling a week or stressing few hours - Stress seems to rise the chance of panic, but differently by types. Things like llvm will always build, but gcc will cause a panic per few passes. The system was 11.2 but then moved on to stable/11 (r337906 currently). I've got last 10 coredumps saved but my kernel isn't compile as debug. So I'll put some backtrace from core.txt.? in the end. Indeed I want to eliminate this problem. Could someone guide me how to figure out the problem? What should I try next? Best regards, Meowthink [1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224886 [2] https://reviews.freebsd.org/D11780 Backtraces newer - older: ------------------------------------------------------------------------ Panic while compiling gcc: #0 doadump (textdump=) at pcpu.h:230 230 pcpu.h: No such file or directory. in pcpu.h (kgdb) #0 doadump (textdump=) at pcpu.h:230 #1 0xffffffff80afa5fb in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:383 #2 0xffffffff80afaa21 in vpanic (fmt=, ap=) at /usr/src/sys/kern/kern_shutdown.c:776 #3 0xffffffff80afa863 in panic (fmt=) at /usr/src/sys/kern/kern_shutdown.c:707 #4 0xffffffff80f7c14f in trap_fatal (frame=0xfffffe081e962790, eva=18446735309538549504) at /usr/src/sys/amd64/amd64/trap.c:877 #5 0xffffffff80f7c1a9 in trap_pfault (frame=0xfffffe081e962790, usermode=0) at pcpu.h:230 #6 0xffffffff80f7b984 in trap (frame=0xfffffe081e962790) at /usr/src/sys/amd64/amd64/trap.c:415 #7 0xffffffff80f5bccc in calltrap () at /usr/src/sys/amd64/amd64/exception.S:231 #8 0xffffffff822950a8 in arc_change_state () at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c:1800 #9 0xffffffff8229328b in arc_access () at time.h:145 #10 0xffffffff82296232 in arc_write_done (zio=0xfffff8065f886410) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c:6169 #11 0xffffffff82334cbe in zio_done (zio=) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:4032 #12 0xffffffff8233070c in zio_execute (zio=0xfffff8065f886410) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:1768 #13 0xffffffff80b52cc4 in taskqueue_run_locked (queue=0xfffff8000d9e6e00) at /usr/src/sys/kern/subr_taskqueue.c:463 #14 0xffffffff80b53e28 in taskqueue_thread_loop (arg=) at /usr/src/sys/kern/subr_taskqueue.c:755 #15 0xffffffff80abd813 in fork_exit ( callout=0xffffffff80b53d90 , arg=0xfffff8000d967030, frame=0xfffffe081e962ac0) at /usr/src/sys/kern/kern_fork.c:1072 #16 0xffffffff80f5cc7e in fork_trampoline () at /usr/src/sys/amd64/amd64/exception.S:972 #17 0x0000000000000000 in ?? () Current language: auto; currently minimal (kgdb) ------------------------------------------------------------------------ backtrace panic when shuting down: #0 doadump (textdump=) at pcpu.h:230 230 pcpu.h: No such file or directory. in pcpu.h (kgdb) #0 doadump (textdump=) at pcpu.h:230 #1 0xffffffff80afa5fb in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:383 #2 0xffffffff80afaa21 in vpanic (fmt=, ap=) at /usr/src/sys/kern/kern_shutdown.c:776 #3 0xffffffff80afa863 in panic (fmt=) at /usr/src/sys/kern/kern_shutdown.c:707 #4 0xffffffff80f7c14f in trap_fatal (frame=0xfffffe081ed30700, eva=0) at /usr/src/sys/amd64/amd64/trap.c:877 #5 0xffffffff80f7c1a9 in trap_pfault (frame=0xfffffe081ed30700, usermode=0) at pcpu.h:230 #6 0xffffffff80f7b984 in trap (frame=0xfffffe081ed30700) at /usr/src/sys/amd64/amd64/trap.c:415 #7 0xffffffff80f5bccc in calltrap () at /usr/src/sys/amd64/amd64/exception.S:231 #8 0xffffffff80dfe4ad in vm_object_terminate (object=0xfffff805bf66d5a0) at /usr/src/sys/vm/vm_object.c:768 #9 0xffffffff80dfd0f8 in vm_object_deallocate (object=0x0) at /usr/src/sys/vm/vm_object.c:677 #10 0xffffffff80df3189 in _vm_map_unlock (map=, file=, line=) at /usr/src/sys/vm/vm_map.c:2939 #11 0xffffffff80df7be2 in vm_map_remove (map=0xfffff80018673000, start=4096, end=140737488351232) at /usr/src/sys/vm/vm_map.c:3137 #12 0xffffffff80df2e49 in vmspace_exit (td=0xfffff80039ec0620) at /usr/src/sys/vm/vm_map.c:337 #13 0xffffffff80ab72b9 in exit1 (td=0xfffff80039ec0620, rval=, signo=) at /usr/src/sys/kern/kern_exit.c:401 #14 0xffffffff80ab6ced in sys_sys_exit (td=, uap=) at /usr/src/sys/kern/kern_exit.c:180 #15 0xffffffff80f7d1d8 in amd64_syscall (td=0xfffff80039ec0620, traced=0) at subr_syscall.c:132 #16 0xffffffff80f5c5ad in fast_syscall_common () at /usr/src/sys/amd64/amd64/exception.S:494 #17 0x00000008028d034a in ?? () Previous frame inner to this frame (corrupt stack?) Current language: auto; currently minimal (kgdb) ------------------------------------------------------------------------ Panic while only running my single thread python script #0 doadump (textdump=) at pcpu.h:230 230 pcpu.h: No such file or directory. in pcpu.h (kgdb) #0 doadump (textdump=) at pcpu.h:230 #1 0xffffffff80afa5fb in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:383 #2 0xffffffff80afaa21 in vpanic (fmt=, ap=) at /usr/src/sys/kern/kern_shutdown.c:776 #3 0xffffffff80afa863 in panic (fmt=) at /usr/src/sys/kern/kern_shutdown.c:707 #4 0xffffffff80f7c14f in trap_fatal (frame=0xfffffe081f635ec0, eva=952) at /usr/src/sys/amd64/amd64/trap.c:877 #5 0xffffffff80f7c1a9 in trap_pfault (frame=0xfffffe081f635ec0, usermode=0) at pcpu.h:230 #6 0xffffffff80f7b984 in trap (frame=0xfffffe081f635ec0) at /usr/src/sys/amd64/amd64/trap.c:415 #7 0xffffffff80f5bccc in calltrap () at /usr/src/sys/amd64/amd64/exception.S:231 #8 0xffffffff80af57ad in __rw_wlock_hard (c=0xfffff80016f8f798, v=) at /usr/src/sys/kern/kern_rwlock.c:977 #9 0xffffffff80bbca92 in bufobj_invalbuf (bo=, flags=1, slpflag=1017770744, slptimeo=) at /usr/src/sys/kern/vfs_subr.c:1609 #10 0xffffffff80bbf8be in vgonel (vp=0xfffff8053ca9f1d8) at /usr/src/sys/kern/vfs_subr.c:1655 #11 0xffffffff80bbbcc4 in vnlru_free_locked (count=1, mnt_op=0x0) at /usr/src/sys/kern/vfs_subr.c:1227 #12 0xffffffff80bbbe14 in getnewvnode_reserve (count=1) at /usr/src/sys/kern/vfs_subr.c:1287 #13 0xffffffff82327fb4 in zfs_zget (zfsvfs=0xfffff80076574000, obj_num=34941, zpp=0xfffffe081f6362a8) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_znode.c:1122 #14 0xffffffff823421ad in zfs_dirent_lookup (dzp=0xfffff804ff94e420, name=0xfffffe081f6363e0 "filename.ext", zpp=0xfffffe081f6362a8, flag=2) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_dir.c:187 #15 0xffffffff82342267 in zfs_dirlook (dzp=0xfffff804ff94e420, name=, zpp=0xfffffe081f636360) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_dir.c:238 #16 0xffffffff8235a4ef in zfs_lookup () at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c:1658 #17 0xffffffff8235ac1e in zfs_freebsd_lookup (ap=0xfffffe081f636548) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c:4956 #18 0xffffffff810fe89c in VOP_CACHEDLOOKUP_APV (vop=, a=0xfffffe081f636548) at vnode_if.c:195 #19 0xffffffff80ba8d56 in vfs_cache_lookup (ap=) at vnode_if.h:80 #20 0xffffffff810fe77c in VOP_LOOKUP_APV (vop=, a=0xfffffe081f636610) at vnode_if.c:127 #21 0xffffffff80bb2761 in lookup (ndp=0xfffffe081f636748) at vnode_if.h:54 #22 0xffffffff80bb1c29 in namei (ndp=0xfffffe081f636748) at /usr/src/sys/kern/vfs_lookup.c:448 #23 0xffffffff80bc8238 in kern_statat (td=0xfffff8013ba1b620, flag=, fd=-100, path=0x80332c910
, pathseg=UIO_USERSPACE, sbp=0xfffffe081f636900, hook=0) at /usr/src/sys/kern/vfs_syscalls.c:2023 #24 0xffffffff80bc817d in sys_stat (td=, uap=0xfffff8013ba1bb58) at /usr/src/sys/kern/vfs_syscalls.c:1978 #25 0xffffffff80f7d1d8 in amd64_syscall (td=0xfffff8013ba1b620, traced=0) at subr_syscall.c:132 #26 0xffffffff80f5c5ad in fast_syscall_common () at /usr/src/sys/amd64/amd64/exception.S:494 #27 0x0000000801a5b9ca in ?? () Previous frame inner to this frame (corrupt stack?) Current language: auto; currently minimal (kgdb) ------------------------------------------------------------------------ Panic while using mplayer #0 doadump (textdump=) at pcpu.h:230 230 pcpu.h: No such file or directory. in pcpu.h (kgdb) #0 doadump (textdump=) at pcpu.h:230 #1 0xffffffff80af91cb in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:383 #2 0xffffffff80af95f1 in vpanic (fmt=, ap=) at /usr/src/sys/kern/kern_shutdown.c:776 #3 0xffffffff80af9433 in panic (fmt=) at /usr/src/sys/kern/kern_shutdown.c:707 #4 0xffffffff80f7a13f in trap_fatal (frame=0xfffffe081f70d380, eva=0) at /usr/src/sys/amd64/amd64/trap.c:877 #5 0xffffffff80f7a199 in trap_pfault (frame=0xfffffe081f70d380, usermode=0) at pcpu.h:230 #6 0xffffffff80f79974 in trap (frame=0xfffffe081f70d380) at /usr/src/sys/amd64/amd64/trap.c:415 #7 0xffffffff80f5a00c in calltrap () at /usr/src/sys/amd64/amd64/exception.S:231 #8 0xffffffff8088c030 in hdac_stream_start (dev=, child=, dir=0, stream=1, buf=1889533952, blksz=2048, blkcnt=2) at /usr/src/sys/dev/sound/pci/hda/hdac.c:1927 #9 0xffffffff8088437d in hdaa_channel_start (ch=) at hdac_if.h:84 #10 0xffffffff80887e0d in hdaa_channel_trigger (obj=, data=0xfffff8007102c480, go=1) at /usr/src/sys/dev/sound/pci/hda/hdaa.c:2161 #11 0xffffffff80893b8e in chn_trigger (c=0xfffff80071058400, go=1) at channel_if.h:131 #12 0xffffffff8089751b in chn_notify (c=0xfffff80071058400, flags=) at /usr/src/sys/dev/sound/pcm/channel.c:2281 #13 0xffffffff808b697f in vchan_trigger (obj=, data=, go=1) at /usr/src/sys/dev/sound/pcm/vchan.c:171 #14 0xffffffff80893b8e in chn_trigger (c=0xfffff80071057c00, go=1) at channel_if.h:131 #15 0xffffffff8089de10 in dsp_ioctl (i_dev=, cmd=, arg=0xfffffe081f70d8d0 "\003", mode=, td=) at /usr/src/sys/dev/sound/pcm/dsp.c:1733 #16 0xffffffff809c5b38 in devfs_ioctl_f (fp=0xfffff802c5563c80, com=2147766288, data=0xfffffe081f70d8d0, cred=0xfffff8004c482500, td=0xfffff802f24ac000) at /usr/src/sys/fs/devfs/devfs_vnops.c:791 #17 0xffffffff80b5c00d in kern_ioctl (td=0xfffff802f24ac000, fd=51, com=2147766288, data=) at file.h:323 #18 0xffffffff80b5bd2c in sys_ioctl (td=0xfffff802f24ac000, uap=0xfffff802f24ac538) at /usr/src/sys/kern/sys_generic.c:745 #19 0xffffffff80f7b1c8 in amd64_syscall (td=0xfffff802f24ac000, traced=0) at subr_syscall.c:132 #20 0xffffffff80f5a8ed in fast_syscall_common () at /usr/src/sys/amd64/amd64/exception.S:494 #21 0x0000000801fb94aa in ?? () Previous frame inner to this frame (corrupt stack?) Current language: auto; currently minimal (kgdb) ------------------------------------------------------------------------ Panic while ilde, seems like cronjobs triggered ZFS ARC cleanup. #0 doadump (textdump=) at pcpu.h:230 230 pcpu.h: No such file or directory. in pcpu.h (kgdb) #0 doadump (textdump=) at pcpu.h:230 #1 0xffffffff80af95fb in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:383 #2 0xffffffff80af9a21 in vpanic (fmt=, ap=) at /usr/src/sys/kern/kern_shutdown.c:776 #3 0xffffffff80af9863 in panic (fmt=) at /usr/src/sys/kern/kern_shutdown.c:707 #4 0xffffffff80f7b13f in trap_fatal (frame=0xfffffe081ee186e0, eva=201697507) at /usr/src/sys/amd64/amd64/trap.c:877 #5 0xffffffff80f7b199 in trap_pfault (frame=0xfffffe081ee186e0, usermode=0) at pcpu.h:230 #6 0xffffffff80f7a974 in trap (frame=0xfffffe081ee186e0) at /usr/src/sys/amd64/amd64/trap.c:415 #7 0xffffffff80f5a5bc in calltrap () at /usr/src/sys/amd64/amd64/exception.S:231 #8 0xffffffff80ad596e in free (addr=0xfffff802472af200, mtp=0xffffffff825bfc00) at /usr/src/sys/kern/kern_malloc.c:583 #9 0xffffffff8232a667 in zfs_inactive (vp=, cr=, ct=) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c:4333 #10 0xffffffff82332a1d in zfs_freebsd_inactive (ap=) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c:5364 #11 0xffffffff810ff6b2 in VOP_INACTIVE_APV (vop=, a=0xfffffe081ee18858) at vnode_if.c:1955 #12 0xffffffff80bbd7bc in vinactive (vp=0xfffff803ae8b3760, td=0xfffff803ae23b620) at vnode_if.h:807 #13 0xffffffff80bbdcc7 in vputx (vp=0xfffff803ae8b3760, func=1) at /usr/src/sys/kern/vfs_subr.c:2688 #14 0xffffffff80bc5180 in sys_fchdir (td=0xfffff803ae23b620, uap=) at /usr/src/sys/kern/vfs_syscalls.c:724 #15 0xffffffff80f7c1c8 in amd64_syscall (td=0xfffff803ae23b620, traced=0) at subr_syscall.c:132 #16 0xffffffff80f5ae9d in fast_syscall_common () at /usr/src/sys/amd64/amd64/exception.S:494 #17 0x00000008008a99aa in ?? () Previous frame inner to this frame (corrupt stack?) Current language: auto; currently minimal (kgdb) From owner-freebsd-stable@freebsd.org Sun Aug 26 11:45: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 39D471073044 for ; Sun, 26 Aug 2018 11:45:54 +0000 (UTC) (envelope-from endo.mulo@gmail.com) Received: from mail-oi0-x22b.google.com (mail-oi0-x22b.google.com [IPv6:2607:f8b0:4003:c06::22b]) (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 AE0487CDCC for ; Sun, 26 Aug 2018 11:45:53 +0000 (UTC) (envelope-from endo.mulo@gmail.com) Received: by mail-oi0-x22b.google.com with SMTP id t68-v6so11446325oie.12 for ; Sun, 26 Aug 2018 04:45:53 -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=8kOBL7Q5IDjFxXeUqlu1PcAHLd+WubQau0PpssY6j7o=; b=YNkIFWVghQD24kg0mwgN2FIdd+aynkQK/O0C2tpyaK8pHrHJUA6H9qnUqIms4hnSkp Ua1soOdGvwng0WH3tJ/VZEdt4BTPwKGAtWKjOszc4DZM7uSjvOW1aEIn0t1P/kFUO3cr G73RVhcvqMjULvLG/UTWoB/idCcQ8l0Vd/akjkE17YFUTUEXbArl5cmu4sJFXtc5oGgc JoDjb5lHjFCl6IX+Ec7JR0BTh2xv6OkMCrM0/7JWHbiVIR7bTNRVbaxQ5JR8bfFQ7Yrl 2/tnf5E8BzEmZZXx2aeXJyvQkcD8PyxPPZ8V2KPjooVdZhEu1d8j3dyfXHqECxPu+4Jo qxow== 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=8kOBL7Q5IDjFxXeUqlu1PcAHLd+WubQau0PpssY6j7o=; b=AVVjO6rf7h8mHGDgcqAmrMkLhmhIkFKplxwM/Nbzh4w6+VJ+iL5sY93XXl/4BK4JOO 5x+kWskrK074s1fq3lOSi+ebCojbOdvkUxaVWshdROeKqjTMgBOZJvPGgsgmVt5aiCpM dB7AuEFUQgy4PZ/zbZPporWZvVGIsXHsFyHIxUF37gnV1AN/2vEIp3A2xP8NH54YCX7w 30sVmt7LifjVVI9PxRfqpUSbl0/LagO+d/l4VTsQS1wgwBAvuPcAld1MpRt1pp0Pf2Sl yghJrSZWJdS7+E4Kdlt9YmXYY3vGc+jiTVPkumxKpN7cyo9Mnr5jXqKWMQjzYApkdBET fR6w== X-Gm-Message-State: APzg51DWa2qhRFIMT6pyL+bSxRpwihDnlUDlfpbiU6uq3aItW22XgBIl y82O11+ADAYY3cPKusSPr/yDPKutl43HuNnUgCeKN2IT X-Google-Smtp-Source: ANB0VdaSyFCW9HxNrf8WxxJwhaCEHgM0Vc2h0MeseguccxrlX3a9UhLjnSZWUdiMEpvIg/TFqEzEx0LnKOUqybPFDHY= X-Received: by 2002:aca:6541:: with SMTP id j1-v6mr5986842oiw.157.1535283952567; Sun, 26 Aug 2018 04:45:52 -0700 (PDT) MIME-Version: 1.0 From: "Dmitriy M." Date: Sun, 26 Aug 2018 14:45:42 +0300 Message-ID: Subject: Issue probably with `top` and Uncompressed ARC display 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: Sun, 26 Aug 2018 11:45:54 -0000 Hi all, Got issue with displaying Uncompressed ARC in `top` (K Uncompressed and negative Ratio) : ARC: 360G Total, 55G MFU, 271G MRU, 245M Anon, 7976M Header, 27G Other 281G Compressed, K Uncompressed, -5.70:1 Ratio Sysctl counters: [box:~]$ sysctl -a | grep compress vfs.zfs.sync_pass_dont_compress: 5 vfs.zfs.compressed_arc_enabled: 1 kstat.zfs.misc.arcstats.uncompressed_size: 2679818006016 kstat.zfs.misc.arcstats.compressed_size: 301540177408 Running pretty old 11.2-BETA3 FreeBSD 11.2-BETA3 #0 r334277 512GiB RAM total vfs.zfs.arc_max="360G" vfs.zfs.arc_min="360G" Is it (already known) bug in `top` or something wrong with system/ARC to worry about? I do not really believe that our data may be 8x compressed (on filesystem via `zfs get compressratio` got 2.10x), but nothing suspicious with system behaviour (CPU/IO/ZFS) was not noticed. Thanks! From owner-freebsd-stable@freebsd.org Sun Aug 26 12:12:22 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 2DF691074C05 for ; Sun, 26 Aug 2018 12:12:22 +0000 (UTC) (envelope-from oliver.pinter@hardenedbsd.org) Received: from mail-yw1-xc35.google.com (mail-yw1-xc35.google.com [IPv6:2607:f8b0:4864:20::c35]) (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 B3B1C7E44C for ; Sun, 26 Aug 2018 12:12:21 +0000 (UTC) (envelope-from oliver.pinter@hardenedbsd.org) Received: by mail-yw1-xc35.google.com with SMTP id y134-v6so4653469ywg.1 for ; Sun, 26 Aug 2018 05:12:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardenedbsd.org; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=u8VZKRcbTGQqQQrVs7twmEWcoqSUFBuQyH0CRjc6/L4=; b=Jf75kXKjewZhD1zmsaPkc1lMtsrcTb36y09b6xnUjs/znqjjvGuJIRZ+uw5ms5rOGL a3piA1zb9ViwDt+RnTRagDrLyqjx/vThJuUmANpqT0tSP30bdmitjj94GWWq78LT292d tgBmTtW02efzabQN0GaUiW8fUqjMoQK/s+T8SVy6l9nwTmfZ1gwYrt2YVrC4tOLoyG6e br29drO1UC4U3J8Ve9cosypUQLzhl3xu38rVmtDILJAziYKz+t6fDeZc1Vv91kHjnu2Z FMaC8wU5Unr7qjLgLk0UTlSKvwI9IYRPg35oxNBZqyORgTBOkT178txT9PNZaCzVuxCd cZ4g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=u8VZKRcbTGQqQQrVs7twmEWcoqSUFBuQyH0CRjc6/L4=; b=R0qaORyjbC1pu+tCBbXhhI6H6xPrtWu/xtHaXVtfWVpACvuX7fWMKiQS2nJxD0ELsT rez8jUypfdQAqySb0jJuYzoSzqvJv0Exo7NnqCRrKgkN4vsuHTAJTaLdU84473/ExLlD NNd2h1P+xBX6vRNVbGEYULzIBKLw3GPMmR6W6lSWXZTBZAq5LTSRwhO8WmWMqOTI/7D1 c2XbHnyUR+dVXE0D9Sh8tF0NE7n/9K8qkZairgKKupmXgkAQRt4ZhQdiKFiHeOf8tV9B eLWbnVpMvlJWs6Sks0h9jQbmlUi3NlG1flH9rFHI6CjmvS9Dtd73u1uTnSFIZhv6/rTw 0b5Q== X-Gm-Message-State: APzg51DeFKQWV9G3oCS6UgfwsIPFzdUvChp/ic+M4a7/GO/SAHtEfJ97 Npks54nBaezNqhLiawYb7d3bJy1zi5okFuqx4ROCVgOeFlY= X-Google-Smtp-Source: ANB0VdbLUrkVg/F0gwka23aLGYJnP5YeV+Hp9myRf8j3+2jNFDb6+Z+WTc+0nOot91ggQ38Dy2CSC83iMBPMppFkips= X-Received: by 2002:a81:3843:: with SMTP id f64-v6mr4625492ywa.79.1535285540753; Sun, 26 Aug 2018 05:12:20 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a25:f205:0:0:0:0:0 with HTTP; Sun, 26 Aug 2018 05:12:20 -0700 (PDT) In-Reply-To: References: <20180824215302.ivfna55jtrtc5trg@freebsd480.station> <86k1oepbdr.fsf@next.des.no> <180f8f99-5fa1-1411-59e6-856e3ebc370c@cameron.net> From: Oliver Pinter Date: Sun, 26 Aug 2018 14:12:20 +0200 Message-ID: Subject: drm / drm2 removal in 12 To: blubee blubeeme Cc: Hans Petter Selasky , "pmcnary@cameron.net" , Johannes Lundberg , "freebsd-stable@freebsd.org" , "mmacy@freebsd.org" , Ali Abdallah , FreeBSD current , =?UTF-8?Q?Dag=2DErling_Sm=C3=B8rgrav?= 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, 26 Aug 2018 12:12:22 -0000 On Sunday, August 26, 2018, blubee blubeeme wrote: > On Sun, Aug 26, 2018 at 4:32 PM Hans Petter Selasky > wrote: > > > On 8/26/18 3:20 AM, blubee blubeeme wrote: > > > Have you or anyone working on this drm-legacy-kmod stuff done any > > testings > > > of how this will affect current users? > > > > Hi Blubee, > > > > Are you here to try to stir a conflict? > > If so that is not appreciated. > > > > --HPS > > > Hans, you of all people should know that's not true. > > I would think that trying to sneak in code during a code freeze that would > break the release. Forcing the core devs to revert those changes and having > to dust off old policies to try to keep you guys in check is what's > stirring up conflicts, but hey; what do I know? Please use git pull or svn up. They are already reverted and you get back your old drivers. https://github.com/freebsd/freebsd/commit/ae526637c4a79045579abc632ffbfd b368c66ea8#diff-6ee1ee279be0fe8a84e853198b2b4c43 Please try to learn how to use development tools. https://github.com/freebsd/freebsd/commits/master/sys/dev/drm2 I think the latest binary snapshot from 12.0-ALPHA3 contains the old state of code if not, next should be. > It's really sad state when capable engineers are so obsessed with something > that they cannot see the forest for the trees. Try to step away from the > canvas and look at the big picture. Let's do some more step backwards, and see how the graphics driver developments works from the corporation side. They not bother about any of the BSDs, they focus only to Windows and Linux. If you want to use a recent (haha recent, something after 2014) you are forced to use new drivers from linux. The fore/advantage on the Linux side are the zillions of corporately paid kernel developers. They can just focus on a new hw supports, on freebsd side, there are no corporately paid drm driver developer. Sadly. In linux word their internal KPI (try a Google for a "stable API nonsense" words) moves so fastly, that porting of these drivers gets non trivial without a dedicated paid team. If you want to change on this situation, try to learn for you could help or send directed donations to freebsd foundation. ;) > > If you don't mind me asking, Hans care to answer these questions below? > 1) Take a [test] system with the current graphics stack installed and > working. > 2) Apply your patches to remove the drm from base to create a port > 3) update the working [test] system after applying your changes > > With the latest 12, nothing special. Only a deprecation notice gets printed, once the driver is loaded. > How does your changes affect a [test] system that is already up and > running? > > Have any of you guys tried that? Do you have any documentation on how it'll > affect users. > > You guys want to remove things from the current system but you come with; > it works for us hobbyists. > Where do users go to get steps to do all of this stuff? > > You've repeatedly said what you want to do sure, but have you tested it? > _______________________________________________ > 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 Sun Aug 26 17:01: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 164A0107B3B0 for ; Sun, 26 Aug 2018 17:01:38 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x22e.google.com (mail-it0-x22e.google.com [IPv6:2607:f8b0:4001:c0b::22e]) (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 A117386E84 for ; Sun, 26 Aug 2018 17:01:37 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x22e.google.com with SMTP id p16-v6so7726582itp.1 for ; Sun, 26 Aug 2018 10:01:37 -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=Qf5cQBY+6/RUQ78Spex+xq+7700adW2ZYtycUnSon10=; b=WsxkQH30FfyPitKo1v6Cep5XajeAlZ/UqQ2hxnnP9UpKlQXo+boRoeyZxFgOFNZVTi uzyvjCmdmGPLxzDQYf65SdUv4uaU9Yp0Hi5mD69GfAqn08oIr+DAmgciO1KWZ2PHF+Fg 6tqPvlLQppxErPU4p2rH78RHw9o5wGkUVt2/2DHcDhHY2v9TTIZAs0y9PDHzkfRtxJRy u3pUfxweFd7HEi8djIV+hSn3A5jnriqlB7RoIf9p+fShX6k47CBcyJznP4HsoxPnI6oi AZ0iOq7lOeMWYEPly5bk8zHhgqNvlMFBsMgnhCopJePf2ddHldhTmKpkxXCMknrXp/yE DB+w== 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=Qf5cQBY+6/RUQ78Spex+xq+7700adW2ZYtycUnSon10=; b=KSa8yK801THjPYEfhYIA24pRAYnN5YNDMo71Ea4y25c58sHUO3e4zjJdUpHEMmUh5z XvYfLXPmFrHcrnXmkDa8KyqsXsQIZQzGxlyrGEh6RZ0yrWhwEz8+CpBYMuNa3NLWWwN4 umVM7KtXZXNKtXdyZeitbKeRSrIQkzMaLcZ0rvW/rOpd3mwoqSIn/EuHsEnQpIee382a 7wydLmcZS1lSOI/dB3tN/TScNsTDSDYDZPsruvq64Ws0vYFeSUXy9RVbHupnbZBUZ1l0 AHw5ZDpE4sdQxnMi6dvDpJlF8YDEVh9EhzWVnf2YO32WJLHejUfCt9AqZ4wXiw/MfKUT sSuw== X-Gm-Message-State: APzg51Cj0axtYfJA/ySkx6QHRNdBqXNlkaemOvfz2yUVI34SQqrZw3It Th++xwZmtHCCH48ZB/yzxp8Mx1axw8Dast6Zd5W0dxAfwHJ9FA== X-Google-Smtp-Source: ANB0Vdb1r+og52ZQvt1GRIo9UU5vTzGf0hoI3bRVZDtSzO9srv6HR2oUhp0Z2es52S4BIPFzgQm/kxPSUg+EWzeN2/s= X-Received: by 2002:a02:3344:: with SMTP id k4-v6mr8075414jak.45.1535302896890; Sun, 26 Aug 2018 10:01:36 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Warner Losh Date: Sun, 26 Aug 2018 11:01:25 -0600 Message-ID: Subject: Re: drm / drm2 removal in 12 To: Matt Macy Cc: FreeBSD Current , 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, 26 Aug 2018 17:01:38 -0000 For those wondering at what's going on with this, I've shared the following with the developers@ mailing list. I thought I'd share it here to fight the misinformation that's swirling about. We don't have all the answers yet, and I'm working on it with others in the community to get the best outcome possible. We have to look at all the options and consider all the angles because this is a complicated and nuanced problems and 'simple' solutions are apt to create more problems than they solve. > https://reviews.freebsd.org/D16894 is the next step. I plan on committing > it later today or tomorrow barring big issues with it (it's already been > approved by members of the graphics working community and a member of > release engineering). > > It puts a big ugly deprecation notice and makes the drm modules dependent > on a build option. > > But it's not the last step. > > The only real issue we have is that we have two modules name the same: > i915kms.ko and radeonkmw.ko. There's also drm.ko, but versioning seems to > save us from that being an issue with the latest kernel and maybe loader (I > need to test that last detail, and fix what I think might be an issue > there). > > There's multiple ways you can fix this. One would be to turn off the build > on amd64 of these modules. This breaks old users, but not in a horrible way > (they can just turn it on and rebuild, or possibly install the port). > Second would be to fix the boot loader to have per-module paths (or rather > put the kernel path last) as well as doing similar hacks to the kernel > loader. This is fragile, but seems to have some promise. We can't just > change the module path for all modules at this late date, however. So this > solution, if it were working perfectly, could remove all POLA, but we risk > breaking other things. Third, there's been suggestion of having different > module dependencies such that you'd get the right driver no matter whether > or not you have the port installed, though I've not had a chance to see if > the kernel module version code might be able to load the right module > always, but we'd also need to change the boot loader since I don't think > the right logic is there. > > Finding the right solution is a bit tricky because there's so many > different scenarios to consider and test. The immediate next step is being > investigated to find the best path forward in a thoughtful, methodical way. > If you'd like to help, please contact me privately. I'm not sure a > discussion on developers would be fruitful: I'm providing detail here in > the interests of transparency, not because I'm looking for help, per se. > Before I do a next step, I'll circulate my preliminary conclusion along > with a write up for each of these possible solutions outlining the pros and > cons of each so we have it well documented for future reference. > > Longer term, after the freeze, the plan is to remove all the drm drivers, > the drm code and the drm module. We'll also remove the drm2 module builds, > intel and radeon drivers and firmware. We'll likely move what's left of > sys/dev/drm2 to sys/arm/dev/drm2 and hack the *files* files for it to build > in the new place (I have a review in phab to do this, the effort is almost > trivial). Arm is hard to share linux graphics drivers with, as documented > in https://gist.github.com/strejda/c98e513c2ec1d2e23005bb66a7bc6399, so > for the moment we need to stay with drm2 base for its graphics drivers. > That will develop independently of the other platforms, which can share > either drm-stable-kmod, drm-devel-kmod or drm-legacy-kmod ports at the path > forward. These details are in draft form, but are not likely to change a > huge amount. All the people / groups involved that I've spoken with are > on-board for this long-term plan. > > Also longer term, there's many social issues we need to solve. But I don't > want to derail getting the technical things done with them at the moment > playing the blame game. Suffice to say, after looking at things in detail, > I believe everybody from core on down to individual developers deserves > some blame for how we got here, and hyperbolic narratives that paint one > person or faction as evil are not only wrong, they are also part of the > problem. I promise I'll write up something with more specific detail once > we're through the technical phase of the drm work. > Warner From owner-freebsd-stable@freebsd.org Sun Aug 26 18:39: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 9F9EC107E097; Sun, 26 Aug 2018 18:39:54 +0000 (UTC) (envelope-from des@des.no) Received: from smtp.des.no (smtp.des.no [194.63.250.102]) by mx1.freebsd.org (Postfix) with ESMTP id 20C018B206; Sun, 26 Aug 2018 18:39:54 +0000 (UTC) (envelope-from des@des.no) Received: from next.des.no (smtp.des.no [194.63.250.102]) by smtp.des.no (Postfix) with ESMTP id 6FDD78515; Sun, 26 Aug 2018 18:39:47 +0000 (UTC) Received: by next.des.no (Postfix, from userid 1001) id 49CA68CBB; Sun, 26 Aug 2018 20:39:47 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: blubee blubeeme Cc: Hans Petter Selasky , pmcnary@cameron.net, Johannes Lundberg , freebsd-stable@freebsd.org, mmacy@freebsd.org, Ali Abdallah , FreeBSD current Subject: Re: drm / drm2 removal in 12 In-Reply-To: (blubee blubeeme's message of "Sun, 26 Aug 2018 18:41:48 +0800") References: <20180824215302.ivfna55jtrtc5trg@freebsd480.station> <86k1oepbdr.fsf@next.des.no> <180f8f99-5fa1-1411-59e6-856e3ebc370c@cameron.net> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (berkeley-unix) Date: Sun, 26 Aug 2018 20:39:47 +0200 Message-ID: <86d0u5otu4.fsf@next.des.no> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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, 26 Aug 2018 18:39:54 -0000 blubee blubeeme writes: > Hans Petter Selasky writes: > > Are you here to try to stir a conflict? If so that is not > > appreciated. > Hans, you of all people should know that's not true. And yet here we are. You have made it perfectly clear that you are not interested in an honest discussion. Your entire strategy is to wear people down until they either leave or agree with you just to shut you up. Like Hans Petter says, it is not appreciated. You clearly believe that you know better than anyone else how this should be handled, so instead of telling us, I suggest you just go do it. It only takes seconds to fork the FreeBSD mirror on Github, and a few minutes to clone it onto your machine. We look forward to hearing from you again when you have everything working perfectly and seamlessly out of the box for everybody on any equipment. I'm sure that Johannes, Niclas, Warner and others with a century of combined experience will be thrilled to see you succeed where they, by your account, have failed. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-stable@freebsd.org Sun Aug 26 19:40:58 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 300F51080214 for ; Sun, 26 Aug 2018 19:40:58 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-yb0-x230.google.com (mail-yb0-x230.google.com [IPv6:2607:f8b0:4002:c09::230]) (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 CA7DD8E767 for ; Sun, 26 Aug 2018 19:40:57 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mail-yb0-x230.google.com with SMTP id c1-v6so5299576ybq.5 for ; Sun, 26 Aug 2018 12:40:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=HzIi+6pHCXjz5ZqDqpR92oMAsOz+QXeaCMJmch0EeZQ=; b=im/r8A9fJdXYKzHstYcC7h3BbESJR6ZH844a+Ln+/pvPNaXYqPh8XS3EvjX8UbNQf3 XRnhifRuxmQNDhLevQzLfYPFQ3hWLL5HmuVw5l960HvmYeya6jlS4Xd4NZVcSbGurO7G oUgRGBl8/m7hw2bICHR/pkjM7rwmpV7FphBco= 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=HzIi+6pHCXjz5ZqDqpR92oMAsOz+QXeaCMJmch0EeZQ=; b=QUpUCI2gi3Z/a83szNDXVtIHGYFXITDP5ekGAOFxAcGlNstJ5hT/7xVFEogwI2Wv7i 7B7OCaSYbmfRWaM1KKhS+lV8exmIlHxZPygE8au+g8/fZQpHmi4lczIap1jaNrW1nKTB YadYg6pwRxBHoIjVZ4+vmS9ThjOUWzXDodQtGA7xMNe2S+4qFbhVsKFR0xoi/ZEHIpla w5qDXEG3Y3DVcB2svb4Gfapu0O5tAB1F44W0TmPnrOACU9WbGs/vzGuxI20chmSgOhyD bfGG8EVLk6JVtJTBKn6NkJkdy9iBCuy0qGV82pINjutMvOIQIXVNcKXAzLZI73SxYNsK xB/g== X-Gm-Message-State: APzg51D5HJ/R5GU3i5ypKOvThReDAqiygtJNDvci60FZ9rIjGrkhHaHG HZzNmrxkPL8wTEfg/HH8dmwpxBmBvbTWZKu2RNYWtA== X-Google-Smtp-Source: ANB0VdY7uLYN9W5AAo4whfR4flwFfpislJVvUTDlOFqBOWL2clnPHDtmqb/zTqiSTm3TjWLJi+lr3ngj4GjBRh03PLA= X-Received: by 2002:a25:5e08:: with SMTP id s8-v6mr5535626ybb.281.1535312456933; Sun, 26 Aug 2018 12:40:56 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Eitan Adler Date: Sun, 26 Aug 2018 12:40:30 -0700 Message-ID: Subject: Re: Issue probably with `top` and Uncompressed ARC display To: endo.mulo@gmail.com Cc: freebsd-stable Content-Type: text/plain; charset="UTF-8" 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, 26 Aug 2018 19:40:58 -0000 On Sun, 26 Aug 2018 at 04:47, Dmitriy M. wrote: > > Hi all, > > Got issue with displaying Uncompressed ARC in `top` (K Uncompressed and > negative Ratio) : ... I don't want to be the person that just asks you to test on HEAD but in this case, top(1) has been extensively modified in head/-current. You should be able to test by just doing this svn co svn://svn.freebsd.org/base/head/usr.bin/top cd top make $(make -V.OBJDIR)/top If its still an issue I'll look deeper. -- Eitan Adler From owner-freebsd-stable@freebsd.org Sun Aug 26 20:05: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 BD4B61080BD0 for ; Sun, 26 Aug 2018 20:05:43 +0000 (UTC) (envelope-from endo.mulo@gmail.com) Received: from mail-oi0-x231.google.com (mail-oi0-x231.google.com [IPv6:2607:f8b0:4003:c06::231]) (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 1F34C8F4D9 for ; Sun, 26 Aug 2018 20:05:43 +0000 (UTC) (envelope-from endo.mulo@gmail.com) Received: by mail-oi0-x231.google.com with SMTP id q204-v6so23769239oig.9 for ; Sun, 26 Aug 2018 13:05:43 -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=RC/8vDkvU0dCP5slAtx+294lgiOMOcPiRcbxtEzYyUg=; b=Z0C64l7ZClSk70JHDtV4cz3zleNAJ1xAqifvU/HLPTgQipY0C9GalxWadQppR6BTN9 AKAA6M8oN2r4PYPigDFamustJb8x7Py6qXYvdZXk7UUs3PqNqn1RKfCYX15DmbDbsTnI VOgsbEWx2AM6xV+ABZrNcfUpXBS+/CGajENsZrgdKd20ZzDtbusifWkswfqRiNeargd1 g0X/HDGSy9gAk0q0QXDfIQOCCTmpa7Vwmbrj5ktXGv31fiJfXTPNNL/r4vnBF9uoamM1 7aQkVzVS/ago0j12OSxNtSV51je90XDYOSqv1PofGkGbyU+iGY7V6LK2h8ShfszbVoSU 6j0Q== 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=RC/8vDkvU0dCP5slAtx+294lgiOMOcPiRcbxtEzYyUg=; b=ln8GHY1hR1PiY8RNOpubIs5PPungMEfob9BB/N1CMzi5348Vy6r71px+o+TgGYEC1n VW99FnHNQRbizz7tTEkm093tII9SaqIrx2nXgbE2ISCjwohFe8wzHCbQG4gGJ/0FwcB8 NXhlWPQiRsote3LwdoW3qxb+NElpuqT8A6z1WMmiIZG60msIwxEckci/4wgBpOosUixG xKt3NCAEB6yHRfCqtq7pUd3uZUC48khnMuoIfmICR+/qoVgmuaduukN8wauB4ahWLXo5 Q1C+eXYsq13HPfkRKDFxRmwWuIr9/sHSMk/uyzIJITvs1sU/MsGRk3MrG4HWgootB8w2 TXCQ== X-Gm-Message-State: APzg51A4mXTdp7PlmjvvBVWwHQU8BV4WyhIbfTKoFT0ConGwqGxhAhBn LMQB4mfv8JPqQANzPZEb05/GKYa9dkDUOf00ST2Nsi6M X-Google-Smtp-Source: ANB0VdYpPg/OBitDI/Uu1cAXRgJnzHzmqFdP65d35ZiZQRCJaUsg85JMluYEQL/LvpOd8XwOwjlVL+Kn+zl0e/yGbYY= X-Received: by 2002:aca:bb0a:: with SMTP id l10-v6mr10420142oif.153.1535313942289; Sun, 26 Aug 2018 13:05:42 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: "Dmitriy M." Date: Sun, 26 Aug 2018 23:05:31 +0300 Message-ID: Subject: Re: Issue probably with `top` and Uncompressed ARC display To: lists@eitanadler.com Cc: freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" 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, 26 Aug 2018 20:05:44 -0000 > On Sun, 26 Aug 2018 at 04:47, Dmitriy M. wrote: > > > > Hi all, > > > > Got issue with displaying Uncompressed ARC in `top` (K Uncompressed and > > negative Ratio) : > ... > > I don't want to be the person that just asks you to test on HEAD but > in this case, top(1) has been extensively modified in head/-current. > You should be able to test by just doing this > > svn co svn://svn.freebsd.org/base/head/usr.bin/top > cd top > make > $(make -V.OBJDIR)/top > > If its still an issue I'll look deeper. > Yes, issue still there: ARC: 360G Total, 56G MFU, 267G MRU, 187M Anon, 8007M Header, 23G Other 275G Compressed, K Uncompressed, -5.87:1 Ratio But to get `top` work I did some code skip in sysctl reading because my stable system says 'sysctl: unknown oid ', hope this is acceptable for my issue: --- machine.c (revision 338331) +++ machine.c (working copy) @@ -473,8 +473,8 @@ GETSYSCTL("vm.stats.vm.v_laundry_count", memory_stats[2]); GETSYSCTL("vm.stats.vm.v_wire_count", memory_stats[3]); GETSYSCTL("vm.stats.vm.v_free_count", memory_stats[5]); - GETSYSCTL("vm.stats.vm.v_swappgsin", nspgsin); - GETSYSCTL("vm.stats.vm.v_swappgsout", nspgsout); + //GETSYSCTL("vm.stats.vm.v_swappgsin", nspgsin); + //GETSYSCTL("vm.stats.vm.v_swappgsout", nspgsout); /* convert memory stats to Kbytes */ memory_stats[0] = pagetok(memory_stats[0]); memory_stats[1] = pagetok(memory_stats[1]); @@ -522,11 +522,11 @@ GETSYSCTL("kstat.zfs.misc.arcstats.hdr_size", arc_stat); GETSYSCTL("kstat.zfs.misc.arcstats.l2_hdr_size", arc_stat2); arc_stats[4] = (arc_stat + arc_stat2) >> 10; - GETSYSCTL("kstat.zfs.misc.arcstats.bonus_size", arc_stat); + //GETSYSCTL("kstat.zfs.misc.arcstats.bonus_size", arc_stat); arc_stats[5] = arc_stat >> 10; - GETSYSCTL("kstat.zfs.misc.arcstats.dnode_size", arc_stat); + //GETSYSCTL("kstat.zfs.misc.arcstats.dnode_size", arc_stat); arc_stats[5] += arc_stat >> 10; - GETSYSCTL("kstat.zfs.misc.arcstats.dbuf_size", arc_stat); + //GETSYSCTL("kstat.zfs.misc.arcstats.dbuf_size", arc_stat); arc_stats[5] += arc_stat >> 10; si->arc = arc_stats; } From owner-freebsd-stable@freebsd.org Sun Aug 26 20:15:24 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 A169B1081168 for ; Sun, 26 Aug 2018 20:15:24 +0000 (UTC) (envelope-from rollingbits@gmail.com) Received: from mail-qt0-x22b.google.com (mail-qt0-x22b.google.com [IPv6:2607:f8b0:400d:c0d::22b]) (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 3C2588FAD0 for ; Sun, 26 Aug 2018 20:15:24 +0000 (UTC) (envelope-from rollingbits@gmail.com) Received: by mail-qt0-x22b.google.com with SMTP id m13-v6so15864681qth.1 for ; Sun, 26 Aug 2018 13:15:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=content-transfer-encoding:from:mime-version:subject:message-id:date :to; bh=ZiQOy5E8fJZKiCPTrqf4ffnN3ZeWcyaFwf977J2JGjo=; b=NdF10CYY4Yl9h4e+lKr7Ht+P67iGDFPbA8COcgshA6wzs4OFRlganbUMKLG9A6Jw3r d8u9/kbdftKCNuJqAWWVbLk+5fZgcp4A0drNsm3bFtUc9imcOvVDKBixfQbPR8ccvi4R JTwAoZnWN3LNV7gHlvqsQQadcrGvbqO+p/2VW6r2GUUNED4A8k3qIgl2mlHd0APVijRP GKAvNYn/+DpJ5VyWiGi5WHsxhHqKJpkII1iUcKVbkF1kssFFwaOOkTNhEGCCZRKv6PnY yo6xCDTc+XoCQ/77bUFK640Dlxvc+o2zcFZI9F7FQQOJMEf24jeKHugEbguW41lFKK1U j6gQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:message-id:date:to; bh=ZiQOy5E8fJZKiCPTrqf4ffnN3ZeWcyaFwf977J2JGjo=; b=fWo50QfVPPINFLu8D86OP6WU3oSh7olAQ4w15v0EcrOgrlnNgB4S8Ki6an75nV+Q7r cKUx3/KHWZydQxK8JvmnJxSVuD4etT1BnSXbREpVpzFW6Rdq/IrZrL3j91+Ftuu/6B/d mCyfRowRGpncEYTVDkq1C3V9usQaDNgW1knbN7XyJnRVzhuaT+pqpDif5V0CMbs12l3w NpMAVLG4oJxG3uZV1C1wF6+1iDol64HOuiULJHTE60b6x6ykyMLQOLXWr81FS/7UOMQp /eFn6Hwp7/LFzjd5uFK3hnnLw2tV3a3pHShdtODn7yvL62229Na9COnDzgDODPXfVaEL kGuQ== X-Gm-Message-State: APzg51D8h/v2ioYCxkMRcaFrbWbXwD3cp8Al9ZlFGiccB8cMGdDxhyTS 0ePq5K/sIlCUjlBTQ4PtELf6iKle X-Google-Smtp-Source: ANB0VdZ0M0gASXv1cmE1Kx+H3TNS5w53JG376Delll5/ryaqSalLh94S1YEMxM8xhE8L5YrKwu+jHw== X-Received: by 2002:ac8:3f7c:: with SMTP id w57-v6mr10684501qtk.91.1535314523626; Sun, 26 Aug 2018 13:15:23 -0700 (PDT) Received: from [10.1.201.146] (187-26-161-70.3g.claro.net.br. [187.26.161.70]) by smtp.gmail.com with ESMTPSA id k190-v6sm7103613qkd.27.2018.08.26.13.15.22 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 26 Aug 2018 13:15:23 -0700 (PDT) From: =?utf-8?Q?Lucas_Nali_de_Magalh=C3=A3es?= Mime-Version: 1.0 (1.0) Subject: releng/11.2 src install oddness Message-Id: Date: Sun, 26 Aug 2018 17:15:19 -0300 To: freebsd-stable@freebsd.org X-Mailer: iPhone Mail (15G77) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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, 26 Aug 2018 20:15:25 -0000 Hi. I want to drop a note about what happened to me. I did an upgrade from relen= g/9.3 to releng/10.4 to releng/11.2 in an old computer during the last few w= eeks. Everything went fine modulus my rusty skills until today. I changed the generic kernel to remove 10 support and a few other things. I f= ollowed the proposed script and it built without major issues. When I reboot= ed into the new kernel, surprise: almost everything core dumped. make core d= umped, shutdown core dumped=E2=80=A6 I did a power off cycle, went through t= he old kernel, single user, and make installworld finished without issues. I= never saw this before. Then I rebooted into the new kernel and followed fro= m there on until the end. I'm a happy new releng/11.2 user now. Lc --=20 rollingbits =E2=80=94 =F0=9F=93=A7 rollingbits@gmail.com =F0=9F=93=A7 rollin= gbits@terra.com.br =F0=9F=93=A7 rollingbits@yahoo.com =F0=9F=93=A7 rollingbi= ts@globo.com =F0=9F=93=A7 rollingbits@icloud.com= From owner-freebsd-stable@freebsd.org Sun Aug 26 21:00:23 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 8F70C1081F87 for ; Sun, 26 Aug 2018 21:00:23 +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 2F65570D30 for ; Sun, 26 Aug 2018 21:00:23 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id E285F1081F86; Sun, 26 Aug 2018 21:00:22 +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 D18B91081F85 for ; Sun, 26 Aug 2018 21:00:22 +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 76B3E70D2A for ; Sun, 26 Aug 2018 21:00:22 +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 C5501C175 for ; Sun, 26 Aug 2018 21:00:21 +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 w7QL0Lst068782 for ; Sun, 26 Aug 2018 21:00:21 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w7QL0Ll7068773 for stable@FreeBSD.org; Sun, 26 Aug 2018 21:00:21 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201808262100.w7QL0Ll7068773@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, 26 Aug 2018 21:00:21 +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, 26 Aug 2018 21:00:23 -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 Aug 26 22:22:10 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 A6BD21084AB2; Sun, 26 Aug 2018 22:22:10 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-it0-x234.google.com (mail-it0-x234.google.com [IPv6:2607:f8b0:4001:c0b::234]) (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 368F573B2E; Sun, 26 Aug 2018 22:22:10 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-it0-x234.google.com with SMTP id g18-v6so8663258itg.2; Sun, 26 Aug 2018 15:22:10 -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=QjtdDPlm0M6MQYdA8TVvRLcJWMyj/HEwfMWAVTHET4Q=; b=o6bX4Jlswg7uSh0iEuGic5HCeLYz6o5eEMcXcR/rYetlT7rZLsIa9Ewo9lMP7wCc55 cTsJetyujUiEV+xXjdrlJUkAj5PTvrxWAbizoUKFSSFVy46c6ChpvntWN0xN7GYgig2T MaCW8sHeg5C30pKQoYA8JX37cMEItkCnYa1aNaAI5XqdLpcBHI36t8nbf/VmAH9XY+eo tefoYfMjRDdNiZVySzbv/2O8vr5DP9gzJu5IuThbKP1CXIrlAUiPmIJHxNdE2VBjusps yFd3XbOJ/S63UYLU9Pd1E6p+ieN8wg9bAuxtDX7x9NTM+0XQcsmzq0n1Fk1iuY22/vml Ij9A== 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=QjtdDPlm0M6MQYdA8TVvRLcJWMyj/HEwfMWAVTHET4Q=; b=b2+I9jFFase669TKbFDy2z4kxDzlZnKs6E+clAroFZZgYmb0HVTM+NBO7ZbBlMffmC aUGUiJSNo4376FHIowC5sz2zcBl1Lzwa2h1eRJsZfUUoA+jj9pfTvcB+wwJIyJBm6r/w fN1kj3VsrOrZHYupvXhLt4WAs2e+iNDKNs4tB60Rla7hmCJgXap2bJC0+qArWMBOSaFm GLNn1Hz9qUvrqJiN31+TKEhMRYjBTtMdPW4qBva+XXrJCGj+gOPOHgCci2B+hrSrMjDW NhmI6Beo7l+1BygTpvtdzCyqOlb8+uK7tm8NU5jHJGc0R8irn1q0Xqxp8wyddXqHDQqe zyaQ== X-Gm-Message-State: APzg51CBZ+uSZl1ByafCO1AdNDd8F7a/aXGgDPe6E7evGpyyisCdYtoD w9bSkdaZO7wbAXwVzQf9+St7OjH5nNqtJo2WF2o= X-Google-Smtp-Source: ANB0VdZGRenmnuc/ZxqyNJUUMG44iDt/iNJxqxMYI8Erk6QI84v3DlbUJMWHtBbxquJMIvxC8400xicxmIyPVFVd2xc= X-Received: by 2002:a24:d0d6:: with SMTP id m205-v6mr4886905itg.89.1535322129645; Sun, 26 Aug 2018 15:22:09 -0700 (PDT) MIME-Version: 1.0 References: <20180824215302.ivfna55jtrtc5trg@freebsd480.station> <86k1oepbdr.fsf@next.des.no> <180f8f99-5fa1-1411-59e6-856e3ebc370c@cameron.net> <86d0u5otu4.fsf@next.des.no> In-Reply-To: <86d0u5otu4.fsf@next.des.no> From: blubee blubeeme Date: Mon, 27 Aug 2018 06:21:57 +0800 Message-ID: Subject: Re: drm / drm2 removal in 12 To: =?UTF-8?Q?Dag=2DErling_Sm=C3=B8rgrav?= Cc: Hans Petter Selasky , pmcnary@cameron.net, Johannes Lundberg , freebsd-stable@freebsd.org, mmacy@freebsd.org, Ali Abdallah , FreeBSD current Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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, 26 Aug 2018 22:22:10 -0000 On Mon, Aug 27, 2018 at 2:39 AM Dag-Erling Sm=C3=B8rgrav wrote= : > blubee blubeeme writes: > > Hans Petter Selasky writes: > > > Are you here to try to stir a conflict? If so that is not > > > appreciated. > > Hans, you of all people should know that's not true. > > And yet here we are. > > You have made it perfectly clear that you are not interested in an > honest discussion. Your entire strategy is to wear people down until > they either leave or agree with you just to shut you up. Like Hans > Petter says, it is not appreciated. > > You clearly believe that you know better than anyone else how this > should be handled, so instead of telling us, I suggest you just go do > it. It only takes seconds to fork the FreeBSD mirror on Github, and a > few minutes to clone it onto your machine. We look forward to hearing > from you again when you have everything working perfectly and seamlessly > out of the box for everybody on any equipment. I'm sure that Johannes, > Niclas, Warner and others with a century of combined experience will be > thrilled to see you succeed where they, by your account, have failed. > > DES > -- > Dag-Erling Sm=C3=B8rgrav - des@des.no You seem to miss the point where the you avoid breaking the system for any users not on the bleeding edge. You technically adept guys can keep on hacking away, jumping through hoops and building your stuff as you see fit. Nobody will come take your steal your code away in the night. Feel free to keep on working on it, until implementing it doesn't break "old users" do the engineering work and improve your implementation. There are so many seemingly dead code projects around this linuxkpi stuff that you guys just pump out code and abandon inconsistent lack of documentation, lack of testing, it's just a huge mess. Work on cleaning all that stuff up and bring something sensible to the table, you cannot put onus on the core team to maintain that mess going forward because you're not capable of doing it yourselves. From owner-freebsd-stable@freebsd.org Sun Aug 26 22:33:36 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 3A4C610850AA; Sun, 26 Aug 2018 22:33:36 +0000 (UTC) (envelope-from ler@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 DE8917443E; Sun, 26 Aug 2018 22:33:35 +0000 (UTC) (envelope-from ler@FreeBSD.org) Received: from ler-imac.local (unknown [IPv6:2600:1700:210:b18f:24ab:a49d:f09f:2576]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: ler/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 314BE1C7AF; Sun, 26 Aug 2018 22:33:35 +0000 (UTC) (envelope-from ler@FreeBSD.org) Date: Sun, 26 Aug 2018 17:33:34 -0500 From: Larry Rosenman To: blubee blubeeme Cc: Dag-Erling =?utf-8?B?U23DuHJncmF2?= , Hans Petter Selasky , Johannes Lundberg , freebsd-stable@freebsd.org, FreeBSD current , mmacy@freebsd.org, Ali Abdallah , pmcnary@cameron.net Subject: Re: drm / drm2 removal in 12 Message-ID: <20180826223334.i4bc4pmux5gojzbq@ler-imac.local> Mail-Followup-To: blubee blubeeme , Dag-Erling =?utf-8?B?U23DuHJncmF2?= , Hans Petter Selasky , Johannes Lundberg , freebsd-stable@freebsd.org, FreeBSD current , mmacy@freebsd.org, Ali Abdallah , pmcnary@cameron.net References: <86k1oepbdr.fsf@next.des.no> <180f8f99-5fa1-1411-59e6-856e3ebc370c@cameron.net> <86d0u5otu4.fsf@next.des.no> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="ui23l4cp3frw7avh" Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20180716 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, 26 Aug 2018 22:33:36 -0000 --ui23l4cp3frw7avh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Aug 27, 2018 at 06:21:57AM +0800, blubee blubeeme wrote: >=20 > You seem to miss the point where the you avoid breaking the system for any > users not on the bleeding edge. >=20 > You technically adept guys can keep on hacking away, jumping through hoops > and building your stuff as you see fit. > Nobody will come take your steal your code away in the night. Feel free to > keep on working on it, until implementing it > doesn't break "old users" do the engineering work and improve your > implementation. >=20 > There are so many seemingly dead code projects around this linuxkpi stuff > that you guys just pump out code and abandon > inconsistent lack of documentation, lack of testing, it's just a huge mes= s. >=20 > Work on cleaning all that stuff up and bring something sensible to the > table, you cannot put onus on the core team to maintain > that mess going forward because you're not capable of doing it yourselves. If you don't like breakage, don't run HEAD/-CURRENT. If it's not out in HEAD/-CURRENT, we (the project, speaking as a ports committer) can't move forward. =20 --=20 Larry Rosenman https://people.FreeBSD.org/~ler/ Phone: +1 214-642-9640 E-Mail: ler@FreeBSD.org US Mail: 5708 Sabbia Drive, Round Rock, TX 78665-2106 --ui23l4cp3frw7avh Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQHBBAABCgCrFiEEHjgknedhWzvJgwVzaXyZsatIp30FAluDKr4tFIAAAAAAFQAP cGthLWFkZHJlc3NAZ251cGcub3JnbGVyQEZyZWVCU0Qub3JnXxSAAAAAAC4AKGlz c3Vlci1mcHJAbm90YXRpb25zLm9wZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxRTM4 MjQ5REU3NjE1QjNCQzk4MzA1NzM2OTdDOTlCMUFCNDhBNzdEAAoJEGl8mbGrSKd9 S5IH/1K1gAdz+y2slJ1bVUTtgCTBKWtAmhJiUIr23YS+9ZhEau0qJWQWPFg5VpCw cUpT52X3A2RuRFtO5QekW8l0crO7cqaEU/whGbMM67sTbE5Ue07ECiS7qYTpJcoG TMdU8tSB2pAAj6/czCj8GzHC8IYuyUu/A6m5dyzLTNgtt3GO6swB6jamFGBUYH6f 1Wfl6TMbzI8M7vW6CJgIidaKyFaoMxJLEFenmbOwSAkcSp7BH6GLmh2chE8/PXV+ yaX5XgYGsKoGlO2vHuFPcrne/PlzzPIfusqZpENke2OVqIlY5mpwssRsBL0WzMkz HZKj5wJ0788uo4KpYqtJXtjvtt0= =6XlB -----END PGP SIGNATURE----- --ui23l4cp3frw7avh-- From owner-freebsd-stable@freebsd.org Sun Aug 26 22:39:03 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 11B861085475; Sun, 26 Aug 2018 22:39:03 +0000 (UTC) (envelope-from mmacy@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 B81E7747E5; Sun, 26 Aug 2018 22:39:02 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: from mail-it0-f46.google.com (mail-it0-f46.google.com [209.85.214.46]) (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)) (Authenticated sender: mmacy) by smtp.freebsd.org (Postfix) with ESMTPSA id 7DE701C7B0; Sun, 26 Aug 2018 22:39:02 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: by mail-it0-f46.google.com with SMTP id u13-v6so131849iti.1; Sun, 26 Aug 2018 15:39:02 -0700 (PDT) X-Gm-Message-State: APzg51ANFKAlFFz3S2JMRRRRFUMdyrES1kixrBGlEcmhSAht/bBZrnDZ 8v3K+Fq9L1duBPn1rRoFuuwHzGm/K+zjwQ9fKSw= X-Google-Smtp-Source: ANB0VdaiH3PFdJU73Xia53h01lPGGdGR24ZKKht8hMDXa0KlM90tAmctaWMUMG/UeGymr2NHI3rcJ/VJ7ZQokuAQaAE= X-Received: by 2002:a02:2b12:: with SMTP id h18-v6mr8496157jaa.10.1535323141619; Sun, 26 Aug 2018 15:39:01 -0700 (PDT) MIME-Version: 1.0 References: <86k1oepbdr.fsf@next.des.no> <180f8f99-5fa1-1411-59e6-856e3ebc370c@cameron.net> <86d0u5otu4.fsf@next.des.no> <20180826223334.i4bc4pmux5gojzbq@ler-imac.local> In-Reply-To: <20180826223334.i4bc4pmux5gojzbq@ler-imac.local> From: Matthew Macy Date: Sun, 26 Aug 2018 15:38:49 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: drm / drm2 removal in 12 To: freebsd-stable@freebsd.org, freebsd-current Content-Type: text/plain; charset="UTF-8" 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, 26 Aug 2018 22:39:03 -0000 Please just stop responding to this person or we're going to have to migrate to moderated lists. You're legitimizing the voice of one person who project members have spend hours of their time (some even in person) trying to explain the time tradeoffs of supporting graphics. For some reason he isn't capable of understanding the technical issues and he isn't capable of constructively engaging the project. Thank you for your understanding. -M On Sun, Aug 26, 2018 at 3:33 PM Larry Rosenman wrote: > > On Mon, Aug 27, 2018 at 06:21:57AM +0800, blubee blubeeme wrote: > > > > You seem to miss the point where the you avoid breaking the system for any > > users not on the bleeding edge. > > > > You technically adept guys can keep on hacking away, jumping through hoops > > and building your stuff as you see fit. > > Nobody will come take your steal your code away in the night. Feel free to > > keep on working on it, until implementing it > > doesn't break "old users" do the engineering work and improve your > > implementation. > > > > There are so many seemingly dead code projects around this linuxkpi stuff > > that you guys just pump out code and abandon > > inconsistent lack of documentation, lack of testing, it's just a huge mess. > > > > Work on cleaning all that stuff up and bring something sensible to the > > table, you cannot put onus on the core team to maintain > > that mess going forward because you're not capable of doing it yourselves. > > If you don't like breakage, don't run HEAD/-CURRENT. If it's not out in > HEAD/-CURRENT, we (the project, speaking as a ports committer) can't > move forward. > > > -- > Larry Rosenman https://people.FreeBSD.org/~ler/ > Phone: +1 214-642-9640 E-Mail: ler@FreeBSD.org > US Mail: 5708 Sabbia Drive, Round Rock, TX 78665-2106 From owner-freebsd-stable@freebsd.org Mon Aug 27 03:47:26 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 9A618108B27B; Mon, 27 Aug 2018 03:47:26 +0000 (UTC) (envelope-from michelle@sorbs.net) Received: from hades.sorbs.net (hades.sorbs.net [72.12.213.40]) by mx1.freebsd.org (Postfix) with ESMTP id 3E9557C4D3; Mon, 27 Aug 2018 03:47:26 +0000 (UTC) (envelope-from michelle@sorbs.net) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed Received: from isux.com (gate.mhix.org [203.206.128.220]) by hades.sorbs.net (Oracle Communications Messaging Server 7.0.5.29.0 64bit (built Jul 9 2013)) with ESMTPSA id <0PE300F8JMX9U100@hades.sorbs.net>; Sun, 26 Aug 2018 19:58:33 -0700 (PDT) Subject: Re: drm / drm2 removal in 12 To: blubee blubeeme , Mark Linimon Cc: mmacy@freebsd.org, freebsd-stable@freebsd.org, Ali Abdallah , FreeBSD current References: <20180824215302.ivfna55jtrtc5trg@freebsd480.station> <20180825020424.GA16497@lonesome.com> From: Michelle Sullivan Message-id: <8f2d753e-3de3-5a2a-3298-9e1906c0f12e@sorbs.net> Date: Mon, 27 Aug 2018 12:47:03 +1000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:51.0) Gecko/20100101 Firefox/51.0 SeaMonkey/2.48 In-reply-to: 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, 27 Aug 2018 03:47:26 -0000 blubee blubeeme wrote: > On Sat, Aug 25, 2018 at 10:04 AM Mark Linimon wrote: > >> On Sat, Aug 25, 2018 at 07:07:24AM +0800, blubee blubeeme wrote: >>> Are these guys insane and please avoid the nonsense about you're doing >> this >>> in your spare time. >> Let us know how whatever OS you wind up using instead works for you. >> I suggest you look for one that will put up with your constant harangues. >> >> There are very few people on the mailing lists as nasty and rude as >> yourself. It is tiresome, demotivating, and childish. Please go >> elsewhere. >> >> mcl >> > Your opinion has been noted but this issue isn't about me. > > It's about the Graphics devs coding themselves into a corner and looking > for an easy button so they can continue to feel good about their toy. > > There's a reason the changes they tried to force down the FreeBSD source > tree was reverted; It does not meet any standards of quality. > > I have no inside knowledge other than my ability to think clearly and it's > obvious that The FreeBSD team wanted to hint at them that their code > doesn't pass the sniff test. > > Instead of being whiny brats improve your code and have it work without > breaking compatibility with what has been working for quite a long time. > > Here's the play by play; > You guys push this mess contaminating the FreeBSD source tree, some long > standing user tries to update their machines and it blows up; > 1) Most will just leave > 2) Some will complain > 2a) You guys will say; Read UPDATING..... bleh bleh blen > They'll get aggravated, thereby aggravating people who came to this > platform for Stability. > > Users who actually use FreeBSD to get things done do not time to trawl > these mailing lists, they have real world problems to solve with real world > constraints. > > There are OS with kqueue and all those things it's called Linux; You can go > there and play w/ that stuff to your hearts content. > > If you want your code to get merged, make sure it follows the guidelines > and not break the systems for people who are already using the platform. > > Now, I understand hearing harsh criticism about your work might hurt your > feelings and all but here's the antidote; > work harder, > improve your code, > try again when your code quality improves. > > You guys cannot expect people to accept these kludges in their systems that > they run everyday. > > It's an open source project, you can't get mad because your code isn't > accepted, it's your jobs and engineers to do better not expect users to > jump through hoops to accommodate your subpar attempts at coding. > > This isn't about me, it's about the quality of code that you guys are > trying to submit. > Not much to disagree with what you say here.. because that's why I no longer work on using FreeBSD instead having created my own fork which is something I can call stable, that can be patched for security issues and something that is usable across my environment. The one thing who you should be aware of and what I do disagree with you over is who you are speaking to ML is a long standing 'old hat' of FreeBSD and someone I respect and I know would not be putting 'kludges' and substandard code into the trees... Direct your anger elsewhere, whilst still making valid points. Regards, Michelle -- Michelle Sullivan http://www.mhix.org/ From owner-freebsd-stable@freebsd.org Mon Aug 27 07:19: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 4EFF0108F308 for ; Mon, 27 Aug 2018 07:19:18 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from kagate.punkt.de (kagate.punkt.de [217.29.33.131]) (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 8CD8B81FB1; Mon, 27 Aug 2018 07:19:17 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from hugo10.ka.punkt.de (hugo10.ka.punkt.de [217.29.44.10]) by gate1.intern.punkt.de with ESMTP id w7R7JAER044993; Mon, 27 Aug 2018 09:19:10 +0200 (CEST) Received: from [217.29.44.49] ([217.29.44.49]) by hugo10.ka.punkt.de (8.14.2/8.14.2) with ESMTP id w7R7JAwf004648; Mon, 27 Aug 2018 09:19:10 +0200 (CEST) (envelope-from hausen@punkt.de) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: ctld(8) 11.2-release lockup with w2k16 [Was: Re: ctld(8), multiple 'portal-group' on same socket (individual 'discovery-auth-group' restrictions)] From: "Patrick M. Hausen" In-Reply-To: <151ecc4c-5c6b-82ab-d24b-209d685002ad@omnilan.de> Date: Mon, 27 Aug 2018 09:19:10 +0200 Cc: FreeBSD Stable , =?utf-8?Q?Edward_Tomasz_Napiera=C5=82a?= Content-Transfer-Encoding: quoted-printable Message-Id: <790D823D-5C64-4CCF-930E-D093E209A643@punkt.de> References: <5444C94C.4050705@omnilan.de> <20141021104308.GA5990@brick.home> <3613504a-b017-bc3a-cd62-54d8bb051ea1@omnilan.de> <151ecc4c-5c6b-82ab-d24b-209d685002ad@omnilan.de> To: Harry Schmalzbauer X-Mailer: Apple Mail (2.3273) 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, 27 Aug 2018 07:19:18 -0000 Hi, all, > Am 25.08.2018 um 15:04 schrieb Harry Schmalzbauer = : > [...] > This is with 11.2 release. > It's a ESXi guest, which I used severla years with previous FreeBSD = versions without such massive iSCSI performance problems. >=20 > Using the same /dev/zvol with istgt(1) on the same 11.2-release VM = also solves the performance issue. >=20 > Is anybody using ctld(8) in production post 10.x? If so, without = observing a similar regression? Unfortunately I cannot directly help you here. My only iSCSI target = server is still on 10.4 ... But a suggestion: Install the latest BETA of FreeNAS (11.2-BETA2), and try if that shows = the same problems. It's based on 11.2-STABLE. If not, the FreeNAS source tree = and/or the community might prove helpful. Heck, possibly their ctld config contains = some tuning your's doesn't. Communication is via forum instead of mailing = lists, but they are a generally kind bunch of guys. I figure the number of actual users of iSCSI might be larger in that = community. HTH, Patrick --=20 punkt.de GmbH Internet - Dienstleistungen - Beratung Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100 76133 Karlsruhe info@punkt.de http://punkt.de AG Mannheim 108285 Gf: Juergen Egeling From owner-freebsd-stable@freebsd.org Mon Aug 27 08:13:13 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 A60EE1090878; Mon, 27 Aug 2018 08:13:12 +0000 (UTC) (envelope-from philnorm@gmail.com) Received: from mail-wr1-x444.google.com (mail-wr1-x444.google.com [IPv6:2a00:1450:4864:20::444]) (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 0D85D83AC5; Mon, 27 Aug 2018 08:13:12 +0000 (UTC) (envelope-from philnorm@gmail.com) Received: by mail-wr1-x444.google.com with SMTP id n2-v6so12714374wrw.7; Mon, 27 Aug 2018 01:13:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=0bgO3GpE1mos18FEev2lRklp1PG1szfc8sn993T2c8M=; b=lcDxkmFq7VtSLIMmiUpofEOsGTk2LraouyCpncdwzy00XyjLZSrxI3nMlYXqQ/t51b yyJ/sdMImsd1DqDFfbNbL5RdL9nNq7r3oKwTuMtfPGrtO49T1GlFqyGHJPqh1jYtq+/x k/ORqOdrM67gyHzVlq21Ym97QSuVSiayHvbEZNcy3iwikA0+5BQK7Gf1KdxAQNOHAH/o Zc2oqimUqcnAaWecGp7DNQF+RoKrTNnXkVU/PZ3y7UgcX150dz3sloUNAvgAbcpKA7fU BiKvRMWoUpIVpvPVRMqB0CdIXv71KSnGV2ShLOsRdzKgCtvWHdBG4Ewla+nTIKhp8OYp 8WwA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=0bgO3GpE1mos18FEev2lRklp1PG1szfc8sn993T2c8M=; b=WDX/uz7YKz2VArpFlR7rhDBAUmdesYlAAOabKmDheH2ES8aAT7ANrpsI3PfCUEauwO tUN+/SCoyqxYpZ0Xw3CzpoB7OccdO+H4mYqHlu+I5HW2OufZ3vkWfUD3XWZetyFSm7Iv 9woavHGXE5A7iVpsjND2VygyE+6v/x6xAzcMVxGpgtf365l0veFnPF8iaZd1C0kguz8H X21KlxjJgge5NB/+Xr6oOA8P/HZRNPynyXV3Iw9ogSASNt/UkWLEBmxD1F66zxztcoX7 j5Zy8MKwAYjpDiqVN2c4psOAUvrfu3OKsUiUSvW22qzbfQttmAgbe6oiyvGUEmn3G3cO u62w== X-Gm-Message-State: APzg51DBay7eaMZD6FhWAiL8WCBsx2QKHX4Km1nfoBqaRuu7l2HyqWRG ZVGVLAQa9YkwTKknsx9vP4TU0cjm+WqGnnAccUpEXg== X-Google-Smtp-Source: ANB0Vdb2LbJzJiGmTO1dMbGQYWckJxL2k2ftOys/ET49RsoSNNcI6F8Cscstz5iD4jgGJ+gMoTGmDLLJidv5erCYrdY= X-Received: by 2002:adf:db51:: with SMTP id f17-v6mr7494456wrj.212.1535357590931; Mon, 27 Aug 2018 01:13:10 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a1c:c204:0:0:0:0:0 with HTTP; Mon, 27 Aug 2018 01:13:10 -0700 (PDT) In-Reply-To: References: From: Phil Norman Date: Mon, 27 Aug 2018 10:13:10 +0200 Message-ID: Subject: Re: Help diagnose my Ryzen build problem To: Meowthink Cc: freebsd-hackers@freebsd.org, 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, 27 Aug 2018 08:13:13 -0000 Hi. I have a similar setup: Ryzen 3 and Fatal1ty X370 mini-ITX. I had some trouble with instability, although my problems weren't panics, but rather two issues. One was random lockups (with no evidence left in logs), but I *think* this was down to an inadequately cooled graphics card. The other problem I had was with USB. I got quite a spam of log messages about the USB reinitialisation. However, eventually I figured out that the problem didn't occur if I booted the system from a completely powered-down state. That is, use the physical switch on the PSU to cut power entirely, re-enable, then boot from that state. Since then I've had 67 days of uninterrupted uptime, with no USB issues at all. It sounds like your problem is different, but trying a boot-from-cold might be worthwhile, just in case ASRock have a consistent problem in this regard. Cheers, Phil On 26 August 2018 at 13:20, Meowthink wrote: > Hello all, > > Recently I tried to build up a Ryzen system and run FreeBSD on it. > CPU: AMD Ryzen 5 2400G with Radeon Vega Graphics (0x810f10) > Mobo: Asrock Fatal1ty AB350 Gaming-ITX/ac ( with up-to-date BIOS with > PinnaclePI-AM4_1.0.0.4, microcode 0x810100b ) > Mem: 2x Crucial 16GB DDR4-2400 EUDIMM CL17 ( ECC Unregistered but ECC > actually won't work :( ) > > But the system is unstable - it can't last few days even is nearly > idle. System panics even at midnight. It almost panic while or after I > built something large. Surprisly I didn't encourage a user program > fault, bad binaries built etc., panics only. > > Then I tried lots of BIOS settings e.g. SMT, C6 idle current, > underclock RAM, but none seems effect. > It could pass memtest86 V7.5 without error, or various benchmarks > under Windows. thus I think the problem is not in the hardware but > software. > > In the mean time, I realized that the rate of irqs from xhci0 are too > high - it's about 1998/s. I found [1] and tried to MFC r331665. It > didn't fix the problem though, but disabling that bluetooth module > stops the irq storm, after all. > > Then the system lasts much longer before panic. It eventually can > compile ports tree, build the world, scrub the zpool, all done without > annoying reboots. > Then I assume this is [2] related? So I also tried cpuctl, bounding > all processes to 2-7. > But the problem is still there, only the chance become very low. It > still panics occasionally, idling a week or stressing few hours - > Stress seems to rise the chance of panic, but differently by types. > Things like llvm will always build, but gcc will cause a panic per few > passes. > > The system was 11.2 but then moved on to stable/11 (r337906 > currently). I've got last 10 coredumps saved but my kernel isn't > compile as debug. So I'll put some backtrace from core.txt.? in the > end. > > Indeed I want to eliminate this problem. Could someone guide me how to > figure out the problem? What should I try next? > > Best regards, > Meowthink > > [1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224886 > [2] https://reviews.freebsd.org/D11780 > > Backtraces newer - older: > ------------------------------------------------------------------------ > Panic while compiling gcc: > > #0 doadump (textdump=) at pcpu.h:230 > 230 pcpu.h: No such file or directory. > in pcpu.h > (kgdb) #0 doadump (textdump=) at pcpu.h:230 > #1 0xffffffff80afa5fb in kern_reboot (howto=260) > at /usr/src/sys/kern/kern_shutdown.c:383 > #2 0xffffffff80afaa21 in vpanic (fmt=, > ap=) at /usr/src/sys/kern/kern_shutdown.c:776 > #3 0xffffffff80afa863 in panic (fmt=) > at /usr/src/sys/kern/kern_shutdown.c:707 > #4 0xffffffff80f7c14f in trap_fatal (frame=0xfffffe081e962790, > eva=18446735309538549504) at /usr/src/sys/amd64/amd64/trap.c:877 > #5 0xffffffff80f7c1a9 in trap_pfault (frame=0xfffffe081e962790, > usermode=0) > at pcpu.h:230 > #6 0xffffffff80f7b984 in trap (frame=0xfffffe081e962790) > at /usr/src/sys/amd64/amd64/trap.c:415 > #7 0xffffffff80f5bccc in calltrap () > at /usr/src/sys/amd64/amd64/exception.S:231 > #8 0xffffffff822950a8 in arc_change_state () > at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c:1800 > #9 0xffffffff8229328b in arc_access () at time.h:145 > #10 0xffffffff82296232 in arc_write_done (zio=0xfffff8065f886410) > at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c:6169 > #11 0xffffffff82334cbe in zio_done (zio=) > at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:4032 > #12 0xffffffff8233070c in zio_execute (zio=0xfffff8065f886410) > at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:1768 > #13 0xffffffff80b52cc4 in taskqueue_run_locked (queue=0xfffff8000d9e6e00) > at /usr/src/sys/kern/subr_taskqueue.c:463 > #14 0xffffffff80b53e28 in taskqueue_thread_loop (arg=) > at /usr/src/sys/kern/subr_taskqueue.c:755 > #15 0xffffffff80abd813 in fork_exit ( > callout=0xffffffff80b53d90 , > arg=0xfffff8000d967030, frame=0xfffffe081e962ac0) > at /usr/src/sys/kern/kern_fork.c:1072 > #16 0xffffffff80f5cc7e in fork_trampoline () > at /usr/src/sys/amd64/amd64/exception.S:972 > #17 0x0000000000000000 in ?? () > Current language: auto; currently minimal > (kgdb) > > ------------------------------------------------------------------------ > backtrace panic when shuting down: > > #0 doadump (textdump=) at pcpu.h:230 > 230 pcpu.h: No such file or directory. > in pcpu.h > (kgdb) #0 doadump (textdump=) at pcpu.h:230 > #1 0xffffffff80afa5fb in kern_reboot (howto=260) > at /usr/src/sys/kern/kern_shutdown.c:383 > #2 0xffffffff80afaa21 in vpanic (fmt=, > ap=) at /usr/src/sys/kern/kern_shutdown.c:776 > #3 0xffffffff80afa863 in panic (fmt=) > at /usr/src/sys/kern/kern_shutdown.c:707 > #4 0xffffffff80f7c14f in trap_fatal (frame=0xfffffe081ed30700, eva=0) > at /usr/src/sys/amd64/amd64/trap.c:877 > #5 0xffffffff80f7c1a9 in trap_pfault (frame=0xfffffe081ed30700, > usermode=0) > at pcpu.h:230 > #6 0xffffffff80f7b984 in trap (frame=0xfffffe081ed30700) > at /usr/src/sys/amd64/amd64/trap.c:415 > #7 0xffffffff80f5bccc in calltrap () > at /usr/src/sys/amd64/amd64/exception.S:231 > #8 0xffffffff80dfe4ad in vm_object_terminate (object=0xfffff805bf66d5a0) > at /usr/src/sys/vm/vm_object.c:768 > #9 0xffffffff80dfd0f8 in vm_object_deallocate (object=0x0) > at /usr/src/sys/vm/vm_object.c:677 > #10 0xffffffff80df3189 in _vm_map_unlock (map=, > file=, line=) > at /usr/src/sys/vm/vm_map.c:2939 > #11 0xffffffff80df7be2 in vm_map_remove (map=0xfffff80018673000, > start=4096, > end=140737488351232) at /usr/src/sys/vm/vm_map.c:3137 > #12 0xffffffff80df2e49 in vmspace_exit (td=0xfffff80039ec0620) > at /usr/src/sys/vm/vm_map.c:337 > #13 0xffffffff80ab72b9 in exit1 (td=0xfffff80039ec0620, > rval=, signo=) > at /usr/src/sys/kern/kern_exit.c:401 > #14 0xffffffff80ab6ced in sys_sys_exit (td=, > uap=) at /usr/src/sys/kern/kern_exit.c:180 > #15 0xffffffff80f7d1d8 in amd64_syscall (td=0xfffff80039ec0620, traced=0) > at subr_syscall.c:132 > #16 0xffffffff80f5c5ad in fast_syscall_common () > at /usr/src/sys/amd64/amd64/exception.S:494 > #17 0x00000008028d034a in ?? () > Previous frame inner to this frame (corrupt stack?) > Current language: auto; currently minimal > (kgdb) > > ------------------------------------------------------------------------ > Panic while only running my single thread python script > > #0 doadump (textdump=) at pcpu.h:230 > 230 pcpu.h: No such file or directory. > in pcpu.h > (kgdb) #0 doadump (textdump=) at pcpu.h:230 > #1 0xffffffff80afa5fb in kern_reboot (howto=260) > at /usr/src/sys/kern/kern_shutdown.c:383 > #2 0xffffffff80afaa21 in vpanic (fmt=, > ap=) at /usr/src/sys/kern/kern_shutdown.c:776 > #3 0xffffffff80afa863 in panic (fmt=) > at /usr/src/sys/kern/kern_shutdown.c:707 > #4 0xffffffff80f7c14f in trap_fatal (frame=0xfffffe081f635ec0, eva=952) > at /usr/src/sys/amd64/amd64/trap.c:877 > #5 0xffffffff80f7c1a9 in trap_pfault (frame=0xfffffe081f635ec0, > usermode=0) > at pcpu.h:230 > #6 0xffffffff80f7b984 in trap (frame=0xfffffe081f635ec0) > at /usr/src/sys/amd64/amd64/trap.c:415 > #7 0xffffffff80f5bccc in calltrap () > at /usr/src/sys/amd64/amd64/exception.S:231 > #8 0xffffffff80af57ad in __rw_wlock_hard (c=0xfffff80016f8f798, > v=) at /usr/src/sys/kern/kern_rwlock.c:977 > #9 0xffffffff80bbca92 in bufobj_invalbuf (bo=, > flags=1, > slpflag=1017770744, slptimeo=) > at /usr/src/sys/kern/vfs_subr.c:1609 > #10 0xffffffff80bbf8be in vgonel (vp=0xfffff8053ca9f1d8) > at /usr/src/sys/kern/vfs_subr.c:1655 > #11 0xffffffff80bbbcc4 in vnlru_free_locked (count=1, mnt_op=0x0) > at /usr/src/sys/kern/vfs_subr.c:1227 > #12 0xffffffff80bbbe14 in getnewvnode_reserve (count=1) > at /usr/src/sys/kern/vfs_subr.c:1287 > #13 0xffffffff82327fb4 in zfs_zget (zfsvfs=0xfffff80076574000, > obj_num=34941, > zpp=0xfffffe081f6362a8) > at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/ > zfs_znode.c:1122 > #14 0xffffffff823421ad in zfs_dirent_lookup (dzp=0xfffff804ff94e420, > name=0xfffffe081f6363e0 "filename.ext", zpp=0xfffffe081f6362a8, flag=2) > at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/ > zfs_dir.c:187 > #15 0xffffffff82342267 in zfs_dirlook (dzp=0xfffff804ff94e420, > name=, zpp=0xfffffe081f636360) > at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/ > zfs_dir.c:238 > #16 0xffffffff8235a4ef in zfs_lookup () > at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/ > zfs_vnops.c:1658 > #17 0xffffffff8235ac1e in zfs_freebsd_lookup (ap=0xfffffe081f636548) > at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/ > zfs_vnops.c:4956 > #18 0xffffffff810fe89c in VOP_CACHEDLOOKUP_APV (vop=, > a=0xfffffe081f636548) at vnode_if.c:195 > #19 0xffffffff80ba8d56 in vfs_cache_lookup (ap=) > at vnode_if.h:80 > #20 0xffffffff810fe77c in VOP_LOOKUP_APV (vop=, > a=0xfffffe081f636610) at vnode_if.c:127 > #21 0xffffffff80bb2761 in lookup (ndp=0xfffffe081f636748) at vnode_if.h:54 > #22 0xffffffff80bb1c29 in namei (ndp=0xfffffe081f636748) > at /usr/src/sys/kern/vfs_lookup.c:448 > #23 0xffffffff80bc8238 in kern_statat (td=0xfffff8013ba1b620, > flag=, fd=-100, > path=0x80332c910
, > pathseg=UIO_USERSPACE, sbp=0xfffffe081f636900, hook=0) > at /usr/src/sys/kern/vfs_syscalls.c:2023 > #24 0xffffffff80bc817d in sys_stat (td=, > uap=0xfffff8013ba1bb58) at /usr/src/sys/kern/vfs_syscalls.c:1978 > #25 0xffffffff80f7d1d8 in amd64_syscall (td=0xfffff8013ba1b620, traced=0) > at subr_syscall.c:132 > #26 0xffffffff80f5c5ad in fast_syscall_common () > at /usr/src/sys/amd64/amd64/exception.S:494 > #27 0x0000000801a5b9ca in ?? () > Previous frame inner to this frame (corrupt stack?) > Current language: auto; currently minimal > (kgdb) > > ------------------------------------------------------------------------ > Panic while using mplayer > > #0 doadump (textdump=) at pcpu.h:230 > 230 pcpu.h: No such file or directory. > in pcpu.h > (kgdb) #0 doadump (textdump=) at pcpu.h:230 > #1 0xffffffff80af91cb in kern_reboot (howto=260) > at /usr/src/sys/kern/kern_shutdown.c:383 > #2 0xffffffff80af95f1 in vpanic (fmt=, > ap=) at /usr/src/sys/kern/kern_shutdown.c:776 > #3 0xffffffff80af9433 in panic (fmt=) > at /usr/src/sys/kern/kern_shutdown.c:707 > #4 0xffffffff80f7a13f in trap_fatal (frame=0xfffffe081f70d380, eva=0) > at /usr/src/sys/amd64/amd64/trap.c:877 > #5 0xffffffff80f7a199 in trap_pfault (frame=0xfffffe081f70d380, > usermode=0) > at pcpu.h:230 > #6 0xffffffff80f79974 in trap (frame=0xfffffe081f70d380) > at /usr/src/sys/amd64/amd64/trap.c:415 > #7 0xffffffff80f5a00c in calltrap () > at /usr/src/sys/amd64/amd64/exception.S:231 > #8 0xffffffff8088c030 in hdac_stream_start (dev=, > child=, dir=0, stream=1, buf=1889533952, > blksz=2048, > blkcnt=2) at /usr/src/sys/dev/sound/pci/hda/hdac.c:1927 > #9 0xffffffff8088437d in hdaa_channel_start (ch=) > at hdac_if.h:84 > #10 0xffffffff80887e0d in hdaa_channel_trigger (obj=, > data=0xfffff8007102c480, go=1) > at /usr/src/sys/dev/sound/pci/hda/hdaa.c:2161 > #11 0xffffffff80893b8e in chn_trigger (c=0xfffff80071058400, go=1) > at channel_if.h:131 > #12 0xffffffff8089751b in chn_notify (c=0xfffff80071058400, > flags=) at /usr/src/sys/dev/sound/pcm/ > channel.c:2281 > #13 0xffffffff808b697f in vchan_trigger (obj=, > data=, go=1) > at /usr/src/sys/dev/sound/pcm/vchan.c:171 > #14 0xffffffff80893b8e in chn_trigger (c=0xfffff80071057c00, go=1) > at channel_if.h:131 > #15 0xffffffff8089de10 in dsp_ioctl (i_dev=, > cmd=, arg=0xfffffe081f70d8d0 "\003", > mode=, td=) > at /usr/src/sys/dev/sound/pcm/dsp.c:1733 > #16 0xffffffff809c5b38 in devfs_ioctl_f (fp=0xfffff802c5563c80, > com=2147766288, data=0xfffffe081f70d8d0, cred=0xfffff8004c482500, > td=0xfffff802f24ac000) at /usr/src/sys/fs/devfs/devfs_vnops.c:791 > #17 0xffffffff80b5c00d in kern_ioctl (td=0xfffff802f24ac000, fd=51, > com=2147766288, data=) at file.h:323 > #18 0xffffffff80b5bd2c in sys_ioctl (td=0xfffff802f24ac000, > uap=0xfffff802f24ac538) at /usr/src/sys/kern/sys_generic.c:745 > #19 0xffffffff80f7b1c8 in amd64_syscall (td=0xfffff802f24ac000, traced=0) > at subr_syscall.c:132 > #20 0xffffffff80f5a8ed in fast_syscall_common () > at /usr/src/sys/amd64/amd64/exception.S:494 > #21 0x0000000801fb94aa in ?? () > Previous frame inner to this frame (corrupt stack?) > Current language: auto; currently minimal > (kgdb) > > ------------------------------------------------------------------------ > Panic while ilde, seems like cronjobs triggered ZFS ARC cleanup. > > #0 doadump (textdump=) at pcpu.h:230 > 230 pcpu.h: No such file or directory. > in pcpu.h > (kgdb) #0 doadump (textdump=) at pcpu.h:230 > #1 0xffffffff80af95fb in kern_reboot (howto=260) > at /usr/src/sys/kern/kern_shutdown.c:383 > #2 0xffffffff80af9a21 in vpanic (fmt=, > ap=) at /usr/src/sys/kern/kern_shutdown.c:776 > #3 0xffffffff80af9863 in panic (fmt=) > at /usr/src/sys/kern/kern_shutdown.c:707 > #4 0xffffffff80f7b13f in trap_fatal (frame=0xfffffe081ee186e0, > eva=201697507) > at /usr/src/sys/amd64/amd64/trap.c:877 > #5 0xffffffff80f7b199 in trap_pfault (frame=0xfffffe081ee186e0, > usermode=0) > at pcpu.h:230 > #6 0xffffffff80f7a974 in trap (frame=0xfffffe081ee186e0) > at /usr/src/sys/amd64/amd64/trap.c:415 > #7 0xffffffff80f5a5bc in calltrap () > at /usr/src/sys/amd64/amd64/exception.S:231 > #8 0xffffffff80ad596e in free (addr=0xfffff802472af200, > mtp=0xffffffff825bfc00) at /usr/src/sys/kern/kern_malloc.c:583 > #9 0xffffffff8232a667 in zfs_inactive (vp=, > cr=, ct=) > at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/ > zfs_vnops.c:4333 > #10 0xffffffff82332a1d in zfs_freebsd_inactive (ap=) > at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/ > zfs_vnops.c:5364 > #11 0xffffffff810ff6b2 in VOP_INACTIVE_APV (vop=, > a=0xfffffe081ee18858) at vnode_if.c:1955 > #12 0xffffffff80bbd7bc in vinactive (vp=0xfffff803ae8b3760, > td=0xfffff803ae23b620) at vnode_if.h:807 > #13 0xffffffff80bbdcc7 in vputx (vp=0xfffff803ae8b3760, func=1) > at /usr/src/sys/kern/vfs_subr.c:2688 > #14 0xffffffff80bc5180 in sys_fchdir (td=0xfffff803ae23b620, > uap=) at /usr/src/sys/kern/vfs_syscalls.c:724 > #15 0xffffffff80f7c1c8 in amd64_syscall (td=0xfffff803ae23b620, traced=0) > at subr_syscall.c:132 > #16 0xffffffff80f5ae9d in fast_syscall_common () > at /usr/src/sys/amd64/amd64/exception.S:494 > #17 0x00000008008a99aa in ?? () > Previous frame inner to this frame (corrupt stack?) > Current language: auto; currently minimal > (kgdb) > _______________________________________________ > 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 Mon Aug 27 09:55: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 AC0E4108288B; Mon, 27 Aug 2018 09:55:25 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from dnvrco-cmomta01.email.rr.com (dnvrco-outbound-snat.email.rr.com [107.14.73.229]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3D7A487103; Mon, 27 Aug 2018 09:55:24 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from localhost ([96.28.161.151]) by cmsmtp with ESMTP id uDuLf7V3cceP9uDuNfG61E; Mon, 27 Aug 2018 09:34:04 +0000 Date: Mon, 27 Aug 2018 09:32:15 +0000 From: "Thomas Mueller" To: freebsd-stable@freebsd.org CC: freebsd-current@freebsd.org Subject: Re: drm / drm2 removal in 12 References: <20180824215302.ivfna55jtrtc5trg@freebsd480.station> <86k1oepbdr.fsf@next.des.no> <180f8f99-5fa1-1411-59e6-856e3ebc370c@cameron.net> X-CMAE-Envelope: MS4wfF6aVO1HgAf5t8DXtTaAww4r+H0PebOJqBfSNMljwDHdL8e7JIC13j2X29zaf/3zHnq5ZRWkOXEouAIreaD3JoXtUmi0fUThJ0M4nybdTXDWUBQwBBB5 PfA7+A2oF6+fRAmE/8usGwfPMPLcxyMwjfUOw2OeqT5+86lJA2RDM4Q5HZpgEmxXcgQBFDDirmASwtQdOTxA2b612w7eDSdL8WQ= 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, 27 Aug 2018 09:55:25 -0000 Excerpt from Oliver Pinter: > Let's do some more step backwards, and see how the graphics driver > developments works from the corporation side. > They not bother about any of the BSDs, they focus only to Windows and > Linux. If you want to use a recent (haha recent, something after 2014) you > are forced to use new drivers from linux. > The fore/advantage on the Linux side are the zillions of corporately paid > kernel developers. > They can just focus on a new hw supports, on freebsd side, there are no > corporately paid drm driver developer. Sadly. > In linux word their internal KPI (try a Google for a "stable API nonsense" > words) moves so fastly, that porting of these drivers gets non trivial > without a dedicated paid team. > If you want to change on this situation, try to learn for you could help or > send directed donations to freebsd foundation. ;) Linux and FreeBSD are not the only open-source OSes. There is also (Net, Open, DragonFly)BSD, Haiku, OpenIndiana and others. Maybe better would be for the hardware manufacturers to release more general specifications that could be adapted to any OS, by the NetBSD developers, Haiku developers, etc. Certainly not to ignore Linux. Tom From owner-freebsd-stable@freebsd.org Mon Aug 27 11:29: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 B45911085376; Mon, 27 Aug 2018 11:29:09 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-wr1-x433.google.com (mail-wr1-x433.google.com [IPv6:2a00:1450:4864:20::433]) (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 25CD78B020; Mon, 27 Aug 2018 11:29:09 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-wr1-x433.google.com with SMTP id g33-v6so13287554wrd.1; Mon, 27 Aug 2018 04:29:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :mime-version:content-transfer-encoding; bh=hQ77OWRHSl94iINyQOigBQKRUtmzaGVEgeJn+/7HZmk=; b=mrxrvZM+6lbOf2q4G+RIqTksWDLQ8wP281rLkYT9zctjxznbp+a3EnZuEBEy/6SHHZ U9sz4IzCIiyGNqlcio9I9aQjmwhTm7DnHbLDu9DkYG+ByGdFDhqAfRafB+C3pHUnD1nd wuY7/e1VADqotzfkmJT41a71FkXwYrABKqoGy6vVMo5v6af5TGyFNOnmAUMO6+fBR7Hk KyPF4niFDlAxifu5cN5scQ38iItybiRH7Da4iqMQoqjFE8xCNYprxR0ryVqWn4TPsGkH 0Q5XApG67O/uAXBpbgXHasYDm062kGFHHO6c0Jb8T8vFCsCM9ybbCW7jlcDya+xnYoP9 3k4A== 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:cc:subject:message-id:in-reply-to :references:reply-to:mime-version:content-transfer-encoding; bh=hQ77OWRHSl94iINyQOigBQKRUtmzaGVEgeJn+/7HZmk=; b=H5g56M42ELSywSkYpfDCsXIhvP5NwQUq/9S4WmKR5L/b7M1nafrADZcHYV5SnD56Af NLuRsUePeXU8g8+NRK3lvijiK4vNX1pYM0rexEmFlNhTkb1u94o3tMMn4SRaV3any/H0 17+iu8IamncfPQcoK+Sq3SsGhaWAjKpRR7GXjTHj7jgnseIZaLa8ZdQGUllu0C44uyxk FvqtQqdWrxy1v+2TcXMnzxzMiVRTPL8jyhg9uQXgnQw3KwqxIQfCG5HLZxaMosS5kzPo b1xK1rQ30hqqd0okaA8f7Txyjh1bS82H6nM3zYbD0lHP63NTK26CE2VbaD49XS8YT2/C aFkA== X-Gm-Message-State: APzg51B4Ez1L+GYNouAaysQxaS5XZHlFbCw6CNHFUGz0AdqNEt1DP427 4nfmIi3tGO8B8LUVdKKE/qk= X-Google-Smtp-Source: ANB0VdY4pH0ivcU1OkD9S5J+9U/L4CAgLyvASaqU0WyYuaTEFg2vjeyb02DEoYwWvFx+bUJPMlb32w== X-Received: by 2002:adf:f906:: with SMTP id b6-v6mr7974552wrr.28.1535369348131; Mon, 27 Aug 2018 04:29:08 -0700 (PDT) Received: from ernst.home (pD9E23C49.dip0.t-ipconnect.de. [217.226.60.73]) by smtp.gmail.com with ESMTPSA id h82-v6sm7932892wme.11.2018.08.27.04.29.06 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 27 Aug 2018 04:29:07 -0700 (PDT) Date: Mon, 27 Aug 2018 13:29:05 +0200 From: Gary Jennejohn To: Phil Norman Cc: Meowthink , freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Help diagnose my Ryzen build problem Message-ID: <20180827132905.191dbd8c@ernst.home> In-Reply-To: References: Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII 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: Mon, 27 Aug 2018 11:29:10 -0000 On Mon, 27 Aug 2018 10:13:10 +0200 Phil Norman wrote: > Hi. > > I have a similar setup: Ryzen 3 and Fatal1ty X370 mini-ITX. I had some > trouble with instability, although my problems weren't panics, but rather > two issues. One was random lockups (with no evidence left in logs), but I > *think* this was down to an inadequately cooled graphics card. > I had instability problems with my Ryzen 5 - lockups for no apparent reason. The only recourse waas a hard reset. It turned out that there were two causes 1) old CPU microcode 2) unhandled errate in the CPU I installed the /usr/ports/sysutils/devcpu-data port, which allowed me to install the latest microcode using cpucontrol(8). I also used a shell script called amd_errata.sh provided by one of the FreeBSD committers. To my shame I can't remember exactly who. Note that the errata fixups are now part of the kernel in FreeBSD 12. After taking these steps about two months ago I have had no more lockups and the machine runs very stabily. [big snip] -- Gary Jennejohn From owner-freebsd-stable@freebsd.org Mon Aug 27 11:55:31 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 1654E10860F5 for ; Mon, 27 Aug 2018 11:55:31 +0000 (UTC) (envelope-from jmaloney@ixsystems.com) Received: from mail-ed1-x530.google.com (mail-ed1-x530.google.com [IPv6:2a00:1450:4864:20::530]) (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 823938C162 for ; Mon, 27 Aug 2018 11:55:29 +0000 (UTC) (envelope-from jmaloney@ixsystems.com) Received: by mail-ed1-x530.google.com with SMTP id h1-v6so10253557eds.1 for ; Mon, 27 Aug 2018 04:55:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ixsystems-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=hPdQhq+FF2lTz+1lMwErRGQbnMeXGkYiJL0QsESWJlg=; b=aL6XttlvLLOal9sfrPGPn82yE+TEKzC97OgQcQDRGsPiaUlL3v02wSpLtoWR+mjeO7 BNOS6+4NoY/ItJvEm7s5ZXj93psz+OSSBoBeNtcY9B4yM0ibZWuzCwhMZOOelGxIt3w0 dr4rP06S9DruuK8HS6wqfBiFsC1LVmW24WP3BTDkga0Qrn9F/KwnVT5CBTqKX6Aw/EIh 95Uoa88TM/Pu4adSX4jy0QkciG17pNFYz+BgMQbTQWiJYV6F5snWHxNBjYzvvw4VwFVY aOnDVgkHjBtSW/nRNfL3lL9p8eQGPmAVG/fpHHYRLe3Rm6KiFBmiZFeXIxPGe/3kzK6W DJaQ== 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=hPdQhq+FF2lTz+1lMwErRGQbnMeXGkYiJL0QsESWJlg=; b=eukCDNuPWiL5/H7R8CCyNx86Uh+wKT1VZzt1nWWS2X+7+iGFlINrRszfJezQBvSVOL hUPwR5sdTXP1ZDRIBhFjcqMwq/8iQDy9XiWbRvxBQGI8WFXZmrAXAChlAKUUTbEB+SZH uUfxIGsVYMJdC0SqXt9+DMT9RNOyU+lyhdjKaz02/L4ZG1ApL9asXnyGLeNFH6X97mcy KXblPg3NisgT7Vvvx8mjP2EgA/kN5m1TNIRHlJTvyXPxMCUG0oaT/VL85dmvAZbuuopz VE9Imf9BSbwaqSEkSHYru8ka8rqYUfulSRcHqf/swR5AUWfWBAzRbd8H12ImberKTAP/ psKA== X-Gm-Message-State: APzg51BdSM223Nx53cmEJ1a1tgsymVPtqAZdCasjMgyQRCkBV76f3ySJ qSy8VOJss4aNCk5ajxk6dJBgSf/VeLY6uX5p8Tl6DA== X-Google-Smtp-Source: ANB0VdZuBbX4KtoJgQFPdcYMGJY5dNbyxshw0Lptm1Eo03DGZ2/35g7hhntsBTnZqvl5QacNmZ58uishT9FWtUmXWkk= X-Received: by 2002:a50:b7db:: with SMTP id i27-v6mr17132591ede.284.1535370928562; Mon, 27 Aug 2018 04:55:28 -0700 (PDT) MIME-Version: 1.0 References: <20180824215302.ivfna55jtrtc5trg@freebsd480.station> <86k1oepbdr.fsf@next.des.no> <180f8f99-5fa1-1411-59e6-856e3ebc370c@cameron.net> <5b83cb32.1c69fb81.ee07c.812eSMTPIN_ADDED_MISSING@mx.google.com> In-Reply-To: <5b83cb32.1c69fb81.ee07c.812eSMTPIN_ADDED_MISSING@mx.google.com> From: Joe Maloney Date: Mon, 27 Aug 2018 07:55:16 -0400 Message-ID: Subject: Re: drm / drm2 removal in 12 To: mueller6722@twc.com Cc: freebsd-stable@freebsd.org, freebsd-current 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, 27 Aug 2018 11:55:31 -0000 Thanks for the drm-next efforts. I could not, and would not be using FreeBSD without it. Joe Maloney On Mon, Aug 27, 2018 at 5:58 AM Thomas Mueller wrote: > Excerpt from Oliver Pinter: > > > Let's do some more step backwards, and see how the graphics driver > > developments works from the corporation side. > > They not bother about any of the BSDs, they focus only to Windows and > > Linux. If you want to use a recent (haha recent, something after 2014) > you > > are forced to use new drivers from linux. > > The fore/advantage on the Linux side are the zillions of corporately paid > > kernel developers. > > They can just focus on a new hw supports, on freebsd side, there are no > > corporately paid drm driver developer. Sadly. > > In linux word their internal KPI (try a Google for a "stable API > nonsense" > > words) moves so fastly, that porting of these drivers gets non trivial > > without a dedicated paid team. > > > If you want to change on this situation, try to learn for you could help > or > > send directed donations to freebsd foundation. ;) > > Linux and FreeBSD are not the only open-source OSes. > > There is also (Net, Open, DragonFly)BSD, Haiku, OpenIndiana and others. > > Maybe better would be for the hardware manufacturers to release more > general specifications that could be adapted to any OS, by the NetBSD > developers, Haiku developers, etc. Certainly not to ignore Linux. > > Tom > > _______________________________________________ > 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 Mon Aug 27 12:18:48 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 A3B9510877EA; Mon, 27 Aug 2018 12:18:48 +0000 (UTC) (envelope-from meowthink@gmail.com) Received: from mail-oi0-x22f.google.com (mail-oi0-x22f.google.com [IPv6:2607:f8b0:4003:c06::22f]) (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 42A198D409; Mon, 27 Aug 2018 12:18:48 +0000 (UTC) (envelope-from meowthink@gmail.com) Received: by mail-oi0-x22f.google.com with SMTP id p84-v6so26849230oic.4; Mon, 27 Aug 2018 05:18:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=VZ5Gi/lOxPRe7k2qxPxDchYAPQ6GxDP3w/jNHlovBdI=; b=m1LN+GPP1rimYfXSnxJIMAmSI01quK7V8WANQJlZaNA8r4k1cXjfiXWoa8whJ7Ug/r qy8MU5OslbTYpXBxlNSN9Z14NyI/JtSeSmXx8HBMNXB58cwdfJJt953LqJOYcivJbPzn QqC066bLudpzZLZQONN/9a5zTSn7FEpVmdngDpzqWn1V5VsMINhv5MhkBhjWFiS386X9 MSH4FAY6ibzj2y5JH9dhpVxXGtFicnd01mGR403NXciNIhJzhITGlVV1/Fv55sftNkGH kg9gIb5KCcspPa15ol8zmhte8zr2Bs6pOU8pGKaAZ0pioC81MJk9i4ybPi3YekQKPl9N /LHw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=VZ5Gi/lOxPRe7k2qxPxDchYAPQ6GxDP3w/jNHlovBdI=; b=BEGRqr4/Y3Fgs2stxBsqWGAQDLyTpUrEAKEWMjo+PGxx/3W2T5PKnjwI1aLyAz4L8Q B7h5BYU/u6dASil1dzMRSnB1ZVU5/XpWm3GWhfyq8+Zyql/Tg/l9t9cuGP3jQ+BG6Jn9 RrBa5TdG6S19bX+Cow1driQ168ooC3u5J+RF8YUbTtud3a96zckdC5wO5yaLH1fS+Eo5 NMlsRVj9fR+YzNRtzc/Vay4rIhtvbMf+IFxt+SkSKrr6q0f0wX20doYz99vKepiSq7du 6FDWP638pYD6oRNGQZr8/ejq3ncE15qxt86zM4gZmBOoksMZGcPU+yV8PAZNzBxxaSlo zBvA== X-Gm-Message-State: APzg51BGXGJybYr7qlbo2sV+68O7f1w/yzFSvLvW+jJqH064mb/+3ANg EDtEioV3KBe81wOJhtorWza+ZMnZDi+TWknObRI= X-Google-Smtp-Source: ANB0VdbxEhAccjQjMEIQt27Vf43BtYaeSN1LeJUZ8QDPsP/VrjhNLhQO9WZQNsdE2R/9mz1UgBJfWD+q9kcsESLBG98= X-Received: by 2002:aca:c2c1:: with SMTP id s184-v6mr11554339oif.117.1535372327455; Mon, 27 Aug 2018 05:18:47 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:ac9:5ac4:0:0:0:0:0 with HTTP; Mon, 27 Aug 2018 05:18:46 -0700 (PDT) In-Reply-To: <20180827132905.191dbd8c@ernst.home> References: <20180827132905.191dbd8c@ernst.home> From: Meowthink Date: Mon, 27 Aug 2018 20:18:46 +0800 Message-ID: Subject: Re: Help diagnose my Ryzen build problem To: gljennjohn@gmail.com Cc: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" 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, 27 Aug 2018 12:18:48 -0000 Hi Gary, On 8/27/18, Gary Jennejohn wrote: > On Mon, 27 Aug 2018 10:13:10 +0200 > Phil Norman wrote: > >> Hi. >> >> I have a similar setup: Ryzen 3 and Fatal1ty X370 mini-ITX. I had some >> trouble with instability, although my problems weren't panics, but rather >> two issues. One was random lockups (with no evidence left in logs), but I >> *think* this was down to an inadequately cooled graphics card. >> > > I had instability problems with my Ryzen 5 - lockups for no > apparent reason. The only recourse waas a hard reset. > > It turned out that there were two causes > 1) old CPU microcode > 2) unhandled errate in the CPU > > I installed the /usr/ports/sysutils/devcpu-data port, which > allowed me to install the latest microcode using cpucontrol(8). > > I also used a shell script called amd_errata.sh provided by one of > the FreeBSD committers. To my shame I can't remember exactly > who. Note that the errata fixups are now part of the kernel in > FreeBSD 12. That's kib, who has committed things in that script to both 12 [1] and stable/11 [2]. Unfortunately, that's for Ryzens family 17h model 00h-0fh, whereas my Ryzen 5 2400G's model is 11h. On the microcode. It shall be updated through UEFI/BIOS updates. I think mine is now PinnaclePI-AM4_1.0.0.4 with microcode patchlevel 0x810100b. Seems like ... the only thing I can do is sit down and wait? > > After taking these steps about two months ago I have had no more > lockups and the machine runs very stabily. > > [big snip] > > -- > Gary Jennejohn > [1] https://svnweb.freebsd.org/base?view=revision&revision=336763 [2] https://svnweb.freebsd.org/base?view=revision&revision=337235 From owner-freebsd-stable@freebsd.org Mon Aug 27 12:37:00 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 5BE9310883A0 for ; Mon, 27 Aug 2018 12:37:00 +0000 (UTC) (envelope-from mitchell@wyatt672earp.force9.co.uk) Received: from avasout06.plus.net (avasout06.plus.net [212.159.14.18]) (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 CECBA8E153 for ; Mon, 27 Aug 2018 12:36:59 +0000 (UTC) (envelope-from mitchell@wyatt672earp.force9.co.uk) Received: from [192.168.1.64] ([146.90.233.111]) by smtp with ESMTPA id uGdxfTGNYWLW2uGdyfacK7; Mon, 27 Aug 2018 13:29:19 +0100 X-CM-Score: 0.00 X-CNFS-Analysis: v=2.3 cv=fJUXI6Se c=1 sm=1 tr=0 a=DmGL1Jmrymuc02ZlcP2exw==:117 a=DmGL1Jmrymuc02ZlcP2exw==:17 a=IkcTkHD0fZMA:10 a=pGLkceISAAAA:8 a=waDbaBDWxNZZftWFd3gA:9 a=QEXdDO2ut3YA:10 X-AUTH: wyatt672earp@:2501 Subject: Ryzen Build Problem To: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org References: From: Mitchell Message-ID: <32e008cf-93d3-944d-9b11-e56f1bb425ef@wyatt672earp.force9.co.uk> Date: Mon, 27 Aug 2018 13:28:07 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 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-CMAE-Envelope: MS4wfPKOm9vFqyk4eCNNBpC8gkfvEmgRsRb0+kkEFGKHRv8QciQLb223GOzgbXXmDu7Pq2GgeiC/qXDCq/6DdenNIjUHqCARgPkuNSRiJXTG/4iCxroZPA2+ s8U5r1QatzsLoo/Ml4C4oVI5x1/sDXba7/KVxIGEhr6sF4rVfQ12S2e/r79sgaCxVo0deGk80ST9ig== 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, 27 Aug 2018 12:37:00 -0000 Hi Meowthink: I'm planning a Home Build, and I came across an issue which might apply to your design. Some AMD CPUs are designed for Over-Clocking automatically. But when I investigated Memory Compatibility I saw that some Memory wasn't. The "AMD Ryzen 5 2400G" looks like it can Over-Clock itself when it feels safe to do so. But the "Crucial 16GB DDR4-2400 EUDIMM CL17" seems to be classified as Server Memory, which could mean it's designed for a single speed. I couldn't find more details about Crucial Memory Over-Clocking. The Crucial Web Pages do feature a Help Facility which might enable you to check further if you input all your system details. I'm no expert here. This will be my first Home Build attempt and I haven't even started yet. You probably need a 2nd and 3rd opinion on this topic. I'm just hoping my contribution will prompt further comments from FreeBSD people with more know-how than I've got. Yours truly: Frank Mitchell On 27/08/18 09:13, Phil Norman wrote: > Hi. > > I have a similar setup: Ryzen 3 and Fatal1ty X370 mini-ITX. I had some > trouble with instability, although my problems weren't panics, but rather > two issues. One was random lockups (with no evidence left in logs), but I > *think* this was down to an inadequately cooled graphics card. > > The other problem I had was with USB. I got quite a spam of log messages > about the USB reinitialisation. However, eventually I figured out that the > problem didn't occur if I booted the system from a completely powered-down > state. That is, use the physical switch on the PSU to cut power entirely, > re-enable, then boot from that state. Since then I've had 67 days of > uninterrupted uptime, with no USB issues at all. > > It sounds like your problem is different, but trying a boot-from-cold might > be worthwhile, just in case ASRock have a consistent problem in this regard. > > Cheers, > Phil > > On 26 August 2018 at 13:20, Meowthink wrote: > >> Hello all, >> >> Recently I tried to build up a Ryzen system and run FreeBSD on it. >> CPU: AMD Ryzen 5 2400G with Radeon Vega Graphics (0x810f10) >> Mobo: Asrock Fatal1ty AB350 Gaming-ITX/ac ( with up-to-date BIOS with >> PinnaclePI-AM4_1.0.0.4, microcode 0x810100b ) >> Mem: 2x Crucial 16GB DDR4-2400 EUDIMM CL17 ( ECC Unregistered but ECC >> actually won't work :( ) >> >> But the system is unstable - it can't last few days even is nearly >> idle. System panics even at midnight. It almost panic while or after I >> built something large. Surprisly I didn't encourage a user program >> fault, bad binaries built etc., panics only. >> >> Then I tried lots of BIOS settings e.g. SMT, C6 idle current, >> underclock RAM, but none seems effect. >> It could pass memtest86 V7.5 without error, or various benchmarks >> under Windows. thus I think the problem is not in the hardware but >> software. >> >> In the mean time, I realized that the rate of irqs from xhci0 are too >> high - it's about 1998/s. I found [1] and tried to MFC r331665. It >> didn't fix the problem though, but disabling that bluetooth module >> stops the irq storm, after all. >> >> Then the system lasts much longer before panic. It eventually can >> compile ports tree, build the world, scrub the zpool, all done without >> annoying reboots. >> Then I assume this is [2] related? So I also tried cpuctl, bounding >> all processes to 2-7. >> But the problem is still there, only the chance become very low. It >> still panics occasionally, idling a week or stressing few hours - >> Stress seems to rise the chance of panic, but differently by types. >> Things like llvm will always build, but gcc will cause a panic per few >> passes. >> >> The system was 11.2 but then moved on to stable/11 (r337906 >> currently). I've got last 10 coredumps saved but my kernel isn't >> compile as debug. So I'll put some backtrace from core.txt.? in the >> end. >> >> Indeed I want to eliminate this problem. Could someone guide me how to >> figure out the problem? What should I try next? >> >> Best regards, >> Meowthink >> From owner-freebsd-stable@freebsd.org Mon Aug 27 12:57:26 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 1673D1088A19; Mon, 27 Aug 2018 12:57:25 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (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 2752D8EB42; Mon, 27 Aug 2018 12:57:24 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wm0-x22c.google.com with SMTP id b19-v6so8012716wme.3; Mon, 27 Aug 2018 05:57:24 -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=PrB/yn1UqKp2E6EZS/zCu2T/S8JDKrmCSLBA3n32Sns=; b=SKiaKjLpqCMj3HcMY52afiClwCMj60qCEoCw0AxzorMp/uROIkTUduOPCB725PCf8m WaBoNe5OoFaamb8M/uOyI+mwk1+4JjayIrPZyl6uih+0QtIaU+QFH5yHehlaCi3dhl0z VBJjliQ0+XIkbWrjcijR5TxUL7GxdWIytO0BRhQQ67l2VD/NesXtpTMiW9yt3DAon943 ldWx9hYvAoyfa4BInTnPqsZh6EWOB83Zd0/OD9L5FOVnK7bDZkhiZE00C+98oXBqkmP0 KLYVziatCwXXUSEmm+mht/I4ePAVGQG2Elwyb4lNkVBqkxqGDkr2WQI28etZlyKLHK7V Q6Pw== 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=PrB/yn1UqKp2E6EZS/zCu2T/S8JDKrmCSLBA3n32Sns=; b=ihd5AbJjKdRDW8GSAPwvpc7sirNrsa8lpbGhzrgIH7nh7AAYc8kKVO/Y/83KiXR2jP XSrdlpwxzciPRwrjxJtahrrQNNo0KnmqXLlLXG4b6KJZWInmMfL2zb4GMIQWv0V3Xlju kPX2RFNPPvITaAg6rSg4yvbTr2UBN+RyICtwf5DYze/GF849uiINfjS02X3W0bRstQUe yZ1YXf4REwRaYIlvjcKL6MPlfPfBNvmc57ijlRZ4JReNhxHxH64VpOAeWUE6gX/SPHTe U7P1tTPqt4AbV8TYuoDTwi9hsjgvpTSLgeRqhzsDXvIts8WoN/PIPXEB55RAV+PIbDaC c8ig== X-Gm-Message-State: APzg51CezcaEEmGA8tEpG4hrkL7C7Ajz1WbEwHC+G0pCS9DX8Oxbux8q foyNdjn5zz7JqJwZtNyYOjadjSezSwd09Ga4EXU= X-Google-Smtp-Source: ANB0VdZP18u5mCq+g54E4amPFmo0/4UxbwihtP3Wr6G8TxvWIEI/sFxW798mSy3meTKG14pFtBRmaYl9j8XCQd9lLKY= X-Received: by 2002:a1c:2351:: with SMTP id j78-v6mr5672606wmj.68.1535374642535; Mon, 27 Aug 2018 05:57:22 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Johannes Lundberg Date: Mon, 27 Aug 2018 14:56:45 +0200 Message-ID: Subject: Re: Help diagnose my Ryzen build problem To: Meowthink Cc: Freebsd hackers list , freebsd-stable@freebsd.org X-Mailman-Approved-At: Mon, 27 Aug 2018 13:00:30 +0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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, 27 Aug 2018 12:57:26 -0000 On Sun, Aug 26, 2018 at 1:27 PM Meowthink wrote: > Hello all, > > Recently I tried to build up a Ryzen system and run FreeBSD on it. > CPU: AMD Ryzen 5 2400G with Radeon Vega Graphics (0x810f10) > Mobo: Asrock Fatal1ty AB350 Gaming-ITX/ac ( with up-to-date BIOS with > PinnaclePI-AM4_1.0.0.4, microcode 0x810100b ) > Mem: 2x Crucial 16GB DDR4-2400 EUDIMM CL17 ( ECC Unregistered but ECC > actually won't work :( ) > > But the system is unstable - it can't last few days even is nearly > idle. System panics even at midnight. It almost panic while or after I > built something large. Surprisly I didn't encourage a user program > fault, bad binaries built etc., panics only. > > Then I tried lots of BIOS settings e.g. SMT, C6 idle current, > underclock RAM, but none seems effect. > It could pass memtest86 V7.5 without error, or various benchmarks > under Windows. thus I think the problem is not in the hardware but > software. > > In the mean time, I realized that the rate of irqs from xhci0 are too > high - it's about 1998/s. I found [1] and tried to MFC r331665. It > didn't fix the problem though, but disabling that bluetooth module > stops the irq storm, after all. > > Then the system lasts much longer before panic. It eventually can > compile ports tree, build the world, scrub the zpool, all done without > annoying reboots. > Then I assume this is [2] related? So I also tried cpuctl, bounding > all processes to 2-7. > But the problem is still there, only the chance become very low. It > still panics occasionally, idling a week or stressing few hours - > Stress seems to rise the chance of panic, but differently by types. > Things like llvm will always build, but gcc will cause a panic per few > passes. > > The system was 11.2 but then moved on to stable/11 (r337906 > currently). I've got last 10 coredumps saved but my kernel isn't > compile as debug. So I'll put some backtrace from core.txt.? in the > end. > > Indeed I want to eliminate this problem. Could someone guide me how to > figure out the problem? What should I try next? > > Best regards, > Meowthink > Hi I have a similar setup and also experience random hard resets without a kernel dump. FreeBSD usually can run days, Windows 10 (fresh install I think) doesn=E2=80=99t last more than a few minutes before BSOD. Windows 10 came with the thing when I bought it. I can't run windows update or anything since it hangs so soon. The box came with an earlier mobo+cpu that I replaced with a ASRock+Ryzen. The earlier AMD Kaveri was stable in both Windows (I think) and FreeBSD. On occasion I get kernel panic directly in early boot. See attached image. I am running cpu microcode update in rc.conf. > > [1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224886 > [2] https://reviews.freebsd.org/D11780 > > Backtraces newer - older: > ------------------------------------------------------------------------ > Panic while compiling gcc: > > #0 doadump (textdump=3D) at pcpu.h:230 > 230 pcpu.h: No such file or directory. > in pcpu.h > (kgdb) #0 doadump (textdump=3D) at pcpu.h:230 > #1 0xffffffff80afa5fb in kern_reboot (howto=3D260) > at /usr/src/sys/kern/kern_shutdown.c:383 > #2 0xffffffff80afaa21 in vpanic (fmt=3D, > ap=3D) at /usr/src/sys/kern/kern_shutdown.c:776 > #3 0xffffffff80afa863 in panic (fmt=3D) > at /usr/src/sys/kern/kern_shutdown.c:707 > #4 0xffffffff80f7c14f in trap_fatal (frame=3D0xfffffe081e962790, > eva=3D18446735309538549504) at /usr/src/sys/amd64/amd64/trap.c:877 > #5 0xffffffff80f7c1a9 in trap_pfault (frame=3D0xfffffe081e962790, > usermode=3D0) > at pcpu.h:230 > #6 0xffffffff80f7b984 in trap (frame=3D0xfffffe081e962790) > at /usr/src/sys/amd64/amd64/trap.c:415 > #7 0xffffffff80f5bccc in calltrap () > at /usr/src/sys/amd64/amd64/exception.S:231 > #8 0xffffffff822950a8 in arc_change_state () > at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c:1800 > #9 0xffffffff8229328b in arc_access () at time.h:145 > #10 0xffffffff82296232 in arc_write_done (zio=3D0xfffff8065f886410) > at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c:6169 > #11 0xffffffff82334cbe in zio_done (zio=3D) > at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:4032 > #12 0xffffffff8233070c in zio_execute (zio=3D0xfffff8065f886410) > at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:1768 > #13 0xffffffff80b52cc4 in taskqueue_run_locked (queue=3D0xfffff8000d9e6e0= 0) > at /usr/src/sys/kern/subr_taskqueue.c:463 > #14 0xffffffff80b53e28 in taskqueue_thread_loop (arg=3D) > at /usr/src/sys/kern/subr_taskqueue.c:755 > #15 0xffffffff80abd813 in fork_exit ( > callout=3D0xffffffff80b53d90 , > arg=3D0xfffff8000d967030, frame=3D0xfffffe081e962ac0) > at /usr/src/sys/kern/kern_fork.c:1072 > #16 0xffffffff80f5cc7e in fork_trampoline () > at /usr/src/sys/amd64/amd64/exception.S:972 > #17 0x0000000000000000 in ?? () > Current language: auto; currently minimal > (kgdb) > > ------------------------------------------------------------------------ > backtrace panic when shuting down: > > #0 doadump (textdump=3D) at pcpu.h:230 > 230 pcpu.h: No such file or directory. > in pcpu.h > (kgdb) #0 doadump (textdump=3D) at pcpu.h:230 > #1 0xffffffff80afa5fb in kern_reboot (howto=3D260) > at /usr/src/sys/kern/kern_shutdown.c:383 > #2 0xffffffff80afaa21 in vpanic (fmt=3D, > ap=3D) at /usr/src/sys/kern/kern_shutdown.c:776 > #3 0xffffffff80afa863 in panic (fmt=3D) > at /usr/src/sys/kern/kern_shutdown.c:707 > #4 0xffffffff80f7c14f in trap_fatal (frame=3D0xfffffe081ed30700, eva=3D0= ) > at /usr/src/sys/amd64/amd64/trap.c:877 > #5 0xffffffff80f7c1a9 in trap_pfault (frame=3D0xfffffe081ed30700, > usermode=3D0) > at pcpu.h:230 > #6 0xffffffff80f7b984 in trap (frame=3D0xfffffe081ed30700) > at /usr/src/sys/amd64/amd64/trap.c:415 > #7 0xffffffff80f5bccc in calltrap () > at /usr/src/sys/amd64/amd64/exception.S:231 > #8 0xffffffff80dfe4ad in vm_object_terminate (object=3D0xfffff805bf66d5a= 0) > at /usr/src/sys/vm/vm_object.c:768 > #9 0xffffffff80dfd0f8 in vm_object_deallocate (object=3D0x0) > at /usr/src/sys/vm/vm_object.c:677 > #10 0xffffffff80df3189 in _vm_map_unlock (map=3D, > file=3D, line=3D) > at /usr/src/sys/vm/vm_map.c:2939 > #11 0xffffffff80df7be2 in vm_map_remove (map=3D0xfffff80018673000, > start=3D4096, > end=3D140737488351232) at /usr/src/sys/vm/vm_map.c:3137 > #12 0xffffffff80df2e49 in vmspace_exit (td=3D0xfffff80039ec0620) > at /usr/src/sys/vm/vm_map.c:337 > #13 0xffffffff80ab72b9 in exit1 (td=3D0xfffff80039ec0620, > rval=3D, signo=3D) > at /usr/src/sys/kern/kern_exit.c:401 > #14 0xffffffff80ab6ced in sys_sys_exit (td=3D, > uap=3D) at /usr/src/sys/kern/kern_exit.c:180 > #15 0xffffffff80f7d1d8 in amd64_syscall (td=3D0xfffff80039ec0620, traced= =3D0) > at subr_syscall.c:132 > #16 0xffffffff80f5c5ad in fast_syscall_common () > at /usr/src/sys/amd64/amd64/exception.S:494 > #17 0x00000008028d034a in ?? () > Previous frame inner to this frame (corrupt stack?) > Current language: auto; currently minimal > (kgdb) > > ------------------------------------------------------------------------ > Panic while only running my single thread python script > > #0 doadump (textdump=3D) at pcpu.h:230 > 230 pcpu.h: No such file or directory. > in pcpu.h > (kgdb) #0 doadump (textdump=3D) at pcpu.h:230 > #1 0xffffffff80afa5fb in kern_reboot (howto=3D260) > at /usr/src/sys/kern/kern_shutdown.c:383 > #2 0xffffffff80afaa21 in vpanic (fmt=3D, > ap=3D) at /usr/src/sys/kern/kern_shutdown.c:776 > #3 0xffffffff80afa863 in panic (fmt=3D) > at /usr/src/sys/kern/kern_shutdown.c:707 > #4 0xffffffff80f7c14f in trap_fatal (frame=3D0xfffffe081f635ec0, eva=3D9= 52) > at /usr/src/sys/amd64/amd64/trap.c:877 > #5 0xffffffff80f7c1a9 in trap_pfault (frame=3D0xfffffe081f635ec0, > usermode=3D0) > at pcpu.h:230 > #6 0xffffffff80f7b984 in trap (frame=3D0xfffffe081f635ec0) > at /usr/src/sys/amd64/amd64/trap.c:415 > #7 0xffffffff80f5bccc in calltrap () > at /usr/src/sys/amd64/amd64/exception.S:231 > #8 0xffffffff80af57ad in __rw_wlock_hard (c=3D0xfffff80016f8f798, > v=3D) at /usr/src/sys/kern/kern_rwlock.c:977 > #9 0xffffffff80bbca92 in bufobj_invalbuf (bo=3D, > flags=3D1, > slpflag=3D1017770744, slptimeo=3D) > at /usr/src/sys/kern/vfs_subr.c:1609 > #10 0xffffffff80bbf8be in vgonel (vp=3D0xfffff8053ca9f1d8) > at /usr/src/sys/kern/vfs_subr.c:1655 > #11 0xffffffff80bbbcc4 in vnlru_free_locked (count=3D1, mnt_op=3D0x0) > at /usr/src/sys/kern/vfs_subr.c:1227 > #12 0xffffffff80bbbe14 in getnewvnode_reserve (count=3D1) > at /usr/src/sys/kern/vfs_subr.c:1287 > #13 0xffffffff82327fb4 in zfs_zget (zfsvfs=3D0xfffff80076574000, > obj_num=3D34941, > zpp=3D0xfffffe081f6362a8) > at > /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_znode.c:1122 > #14 0xffffffff823421ad in zfs_dirent_lookup (dzp=3D0xfffff804ff94e420, > name=3D0xfffffe081f6363e0 "filename.ext", zpp=3D0xfffffe081f6362a8, f= lag=3D2) > at > /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_dir.c:187 > #15 0xffffffff82342267 in zfs_dirlook (dzp=3D0xfffff804ff94e420, > name=3D, zpp=3D0xfffffe081f636360) > at > /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_dir.c:238 > #16 0xffffffff8235a4ef in zfs_lookup () > at > /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c:1658 > #17 0xffffffff8235ac1e in zfs_freebsd_lookup (ap=3D0xfffffe081f636548) > at > /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c:4956 > #18 0xffffffff810fe89c in VOP_CACHEDLOOKUP_APV (vop=3D, > a=3D0xfffffe081f636548) at vnode_if.c:195 > #19 0xffffffff80ba8d56 in vfs_cache_lookup (ap=3D) > at vnode_if.h:80 > #20 0xffffffff810fe77c in VOP_LOOKUP_APV (vop=3D, > a=3D0xfffffe081f636610) at vnode_if.c:127 > #21 0xffffffff80bb2761 in lookup (ndp=3D0xfffffe081f636748) at vnode_if.h= :54 > #22 0xffffffff80bb1c29 in namei (ndp=3D0xfffffe081f636748) > at /usr/src/sys/kern/vfs_lookup.c:448 > #23 0xffffffff80bc8238 in kern_statat (td=3D0xfffff8013ba1b620, > flag=3D, fd=3D-100, > path=3D0x80332c910
, > pathseg=3DUIO_USERSPACE, sbp=3D0xfffffe081f636900, hook=3D0) > at /usr/src/sys/kern/vfs_syscalls.c:2023 > #24 0xffffffff80bc817d in sys_stat (td=3D, > uap=3D0xfffff8013ba1bb58) at /usr/src/sys/kern/vfs_syscalls.c:1978 > #25 0xffffffff80f7d1d8 in amd64_syscall (td=3D0xfffff8013ba1b620, traced= =3D0) > at subr_syscall.c:132 > #26 0xffffffff80f5c5ad in fast_syscall_common () > at /usr/src/sys/amd64/amd64/exception.S:494 > #27 0x0000000801a5b9ca in ?? () > Previous frame inner to this frame (corrupt stack?) > Current language: auto; currently minimal > (kgdb) > > ------------------------------------------------------------------------ > Panic while using mplayer > > #0 doadump (textdump=3D) at pcpu.h:230 > 230 pcpu.h: No such file or directory. > in pcpu.h > (kgdb) #0 doadump (textdump=3D) at pcpu.h:230 > #1 0xffffffff80af91cb in kern_reboot (howto=3D260) > at /usr/src/sys/kern/kern_shutdown.c:383 > #2 0xffffffff80af95f1 in vpanic (fmt=3D, > ap=3D) at /usr/src/sys/kern/kern_shutdown.c:776 > #3 0xffffffff80af9433 in panic (fmt=3D) > at /usr/src/sys/kern/kern_shutdown.c:707 > #4 0xffffffff80f7a13f in trap_fatal (frame=3D0xfffffe081f70d380, eva=3D0= ) > at /usr/src/sys/amd64/amd64/trap.c:877 > #5 0xffffffff80f7a199 in trap_pfault (frame=3D0xfffffe081f70d380, > usermode=3D0) > at pcpu.h:230 > #6 0xffffffff80f79974 in trap (frame=3D0xfffffe081f70d380) > at /usr/src/sys/amd64/amd64/trap.c:415 > #7 0xffffffff80f5a00c in calltrap () > at /usr/src/sys/amd64/amd64/exception.S:231 > #8 0xffffffff8088c030 in hdac_stream_start (dev=3D, > child=3D, dir=3D0, stream=3D1, buf=3D1889533952, > blksz=3D2048, > blkcnt=3D2) at /usr/src/sys/dev/sound/pci/hda/hdac.c:1927 > #9 0xffffffff8088437d in hdaa_channel_start (ch=3D) > at hdac_if.h:84 > #10 0xffffffff80887e0d in hdaa_channel_trigger (obj=3D, > data=3D0xfffff8007102c480, go=3D1) > at /usr/src/sys/dev/sound/pci/hda/hdaa.c:2161 > #11 0xffffffff80893b8e in chn_trigger (c=3D0xfffff80071058400, go=3D1) > at channel_if.h:131 > #12 0xffffffff8089751b in chn_notify (c=3D0xfffff80071058400, > flags=3D) at > /usr/src/sys/dev/sound/pcm/channel.c:2281 > #13 0xffffffff808b697f in vchan_trigger (obj=3D, > data=3D, go=3D1) > at /usr/src/sys/dev/sound/pcm/vchan.c:171 > #14 0xffffffff80893b8e in chn_trigger (c=3D0xfffff80071057c00, go=3D1) > at channel_if.h:131 > #15 0xffffffff8089de10 in dsp_ioctl (i_dev=3D, > cmd=3D, arg=3D0xfffffe081f70d8d0 "\003", > mode=3D, td=3D) > at /usr/src/sys/dev/sound/pcm/dsp.c:1733 > #16 0xffffffff809c5b38 in devfs_ioctl_f (fp=3D0xfffff802c5563c80, > com=3D2147766288, data=3D0xfffffe081f70d8d0, cred=3D0xfffff8004c48250= 0, > td=3D0xfffff802f24ac000) at /usr/src/sys/fs/devfs/devfs_vnops.c:791 > #17 0xffffffff80b5c00d in kern_ioctl (td=3D0xfffff802f24ac000, fd=3D51, > com=3D2147766288, data=3D) at file.h:323 > #18 0xffffffff80b5bd2c in sys_ioctl (td=3D0xfffff802f24ac000, > uap=3D0xfffff802f24ac538) at /usr/src/sys/kern/sys_generic.c:745 > #19 0xffffffff80f7b1c8 in amd64_syscall (td=3D0xfffff802f24ac000, traced= =3D0) > at subr_syscall.c:132 > #20 0xffffffff80f5a8ed in fast_syscall_common () > at /usr/src/sys/amd64/amd64/exception.S:494 > #21 0x0000000801fb94aa in ?? () > Previous frame inner to this frame (corrupt stack?) > Current language: auto; currently minimal > (kgdb) > > ------------------------------------------------------------------------ > Panic while ilde, seems like cronjobs triggered ZFS ARC cleanup. > > #0 doadump (textdump=3D) at pcpu.h:230 > 230 pcpu.h: No such file or directory. > in pcpu.h > (kgdb) #0 doadump (textdump=3D) at pcpu.h:230 > #1 0xffffffff80af95fb in kern_reboot (howto=3D260) > at /usr/src/sys/kern/kern_shutdown.c:383 > #2 0xffffffff80af9a21 in vpanic (fmt=3D, > ap=3D) at /usr/src/sys/kern/kern_shutdown.c:776 > #3 0xffffffff80af9863 in panic (fmt=3D) > at /usr/src/sys/kern/kern_shutdown.c:707 > #4 0xffffffff80f7b13f in trap_fatal (frame=3D0xfffffe081ee186e0, > eva=3D201697507) > at /usr/src/sys/amd64/amd64/trap.c:877 > #5 0xffffffff80f7b199 in trap_pfault (frame=3D0xfffffe081ee186e0, > usermode=3D0) > at pcpu.h:230 > #6 0xffffffff80f7a974 in trap (frame=3D0xfffffe081ee186e0) > at /usr/src/sys/amd64/amd64/trap.c:415 > #7 0xffffffff80f5a5bc in calltrap () > at /usr/src/sys/amd64/amd64/exception.S:231 > #8 0xffffffff80ad596e in free (addr=3D0xfffff802472af200, > mtp=3D0xffffffff825bfc00) at /usr/src/sys/kern/kern_malloc.c:583 > #9 0xffffffff8232a667 in zfs_inactive (vp=3D, > cr=3D, ct=3D) > at > /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c:4333 > #10 0xffffffff82332a1d in zfs_freebsd_inactive (ap=3D) > at > /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c:5364 > #11 0xffffffff810ff6b2 in VOP_INACTIVE_APV (vop=3D, > a=3D0xfffffe081ee18858) at vnode_if.c:1955 > #12 0xffffffff80bbd7bc in vinactive (vp=3D0xfffff803ae8b3760, > td=3D0xfffff803ae23b620) at vnode_if.h:807 > #13 0xffffffff80bbdcc7 in vputx (vp=3D0xfffff803ae8b3760, func=3D1) > at /usr/src/sys/kern/vfs_subr.c:2688 > #14 0xffffffff80bc5180 in sys_fchdir (td=3D0xfffff803ae23b620, > uap=3D) at /usr/src/sys/kern/vfs_syscalls.c:724 > #15 0xffffffff80f7c1c8 in amd64_syscall (td=3D0xfffff803ae23b620, traced= =3D0) > at subr_syscall.c:132 > #16 0xffffffff80f5ae9d in fast_syscall_common () > at /usr/src/sys/amd64/amd64/exception.S:494 > #17 0x00000008008a99aa in ?? () > Previous frame inner to this frame (corrupt stack?) > Current language: auto; currently minimal > (kgdb) > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org= " > From owner-freebsd-stable@freebsd.org Mon Aug 27 13:17:00 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 4972A108947F; Mon, 27 Aug 2018 13:17:00 +0000 (UTC) (envelope-from karu.pruun@gmail.com) Received: from mail-oi0-x22c.google.com (mail-oi0-x22c.google.com [IPv6:2607:f8b0:4003:c06::22c]) (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 D1AB88FB4A; Mon, 27 Aug 2018 13:16:59 +0000 (UTC) (envelope-from karu.pruun@gmail.com) Received: by mail-oi0-x22c.google.com with SMTP id b15-v6so27128750oib.10; Mon, 27 Aug 2018 06:16:59 -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=kCE+z+wA0AQ6kkp7Mvfiz76YsFwiWyfUDPHk8NVPNq8=; b=KI8RCpruxuvoezNKLI20dcmqvNc2dFKuXB9SxEo8/Zx1ToL3+FuQbd1H3y6VxvzMeQ F80uEqO7z4b6SV4KaNEjJlF/TIqgaf9q4SzxS7ZuXJn4nybfRNGvssK61gAN6XWN4vnp 4ackoWQpEHfE1hISa5+pvGYxHjGVrjT0vIre3D3hsbEXyR0nr08HWYT/OSzwaGJEe4E/ MXEdnULQvHShalHN/bbZQfKR/UnG9AM8G3/svJuOvHpx/JpsI1BDH4+BxZpdUiZYDJYC sHvZCASTlUQVouKONZPf2v7nKuO6bPGR/RwBnQ0f9dzpNE2Xo/HZ0Is10FsHd00LjMca QNOQ== 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=kCE+z+wA0AQ6kkp7Mvfiz76YsFwiWyfUDPHk8NVPNq8=; b=Iff+3uflCqORgDJb3eLQgYoQgRT2GQtnOH82DkmhR6CImohpCcBU6dtvvKyuFkk/ZE 50y/acAPzJglkIWok6ZqLObA4Lrzr9K1Ki5jmROpK52OB3/WctG3LpBVKJbUZ0/YX+jH wFPmDAOY53FFjvFPecxi3wH6Cj8a4skhZWROhh8y/I9fELfCafWieSp+p/XUYIHkHu2/ L3ReYvzU6Wo7tuSmfzZpiNDyPXNyfabu2yrQIESxgvyMvd3dbaivk34XOlM7+I+AuBam H7dZFhWbS8POI6o1K7atoIXZbs74ygGbz/ruVzE5Bg1B/dOuohN3o7s7TQwxzxC5hKQ3 un3g== X-Gm-Message-State: APzg51Dqr9EP5VTYer5kTx0Ni5FbLaA1K6MxFFBg/tkaZOKH7dxePssm oFQpz+gBkumbsKbQN0nPIW+GE2cK4hCNHv+0LRSA0Sfi X-Google-Smtp-Source: ANB0VdZgpkiC8Wg3qiobUuI/cJ+V23h3arfrBA60BAx+zlDoMSF8zQ+nheeSGBa/jaXGrWqbpiOzwk/kCjd0tf9KxgA= X-Received: by 2002:aca:d098:: with SMTP id j24-v6mr12814944oiy.72.1535375819193; Mon, 27 Aug 2018 06:16:59 -0700 (PDT) MIME-Version: 1.0 References: <20180827132905.191dbd8c@ernst.home> In-Reply-To: From: "karu.pruun" Date: Mon, 27 Aug 2018 16:16:47 +0300 Message-ID: Subject: Re: Help diagnose my Ryzen build problem To: meowthink@gmail.com Cc: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" 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, 27 Aug 2018 13:17:00 -0000 On Mon, Aug 27, 2018 at 3:21 PM Meowthink wrote: > That's kib, who has committed things in that script to both 12 [1] and > stable/11 [2]. > > Unfortunately, that's for Ryzens family 17h model 00h-0fh, whereas my > Ryzen 5 2400G's model is 11h. > > On the microcode. It shall be updated through UEFI/BIOS updates. I > think mine is now PinnaclePI-AM4_1.0.0.4 with microcode patchlevel > 0x810100b. > > Seems like ... the only thing I can do is sit down and wait? The revision https://svnweb.freebsd.org/base/head/sys/x86/x86/cpu_machdep.c?r1=336763&r2=336762&pathrev=336763 works around the mwait issue, i.e. it sets sysctl machdep.idle_mwait=0 sysctl machdep.idle=hlt Now it may or may not relate to your problem, but it appears that Ryzen 2400G also has another issue with HLT, see the DragonFly bug report https://bugs.dragonflybsd.org/issues/3131 which AMD is aware of and is possibly working on, but it may not have appeared in the errata yet. The bug report says that until this is fixed, the workaround is to also disable HLT in cpu_idle. I am not sure what is the correct value for the sysctl on FreeBSD, perhaps sysctl machdep.idle=0 or some other value? Cheers Peeter -- From owner-freebsd-stable@freebsd.org Mon Aug 27 14:13: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 672FB108B1FD; Mon, 27 Aug 2018 14:13:17 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (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 D4456720F4; Mon, 27 Aug 2018 14:13:16 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-wm0-x236.google.com with SMTP id i134-v6so10100217wmf.0; Mon, 27 Aug 2018 07:13:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :mime-version:content-transfer-encoding; bh=6FYv7XY/tmWnAIQOwTLCG09MRYbGUysfCqS0rp7gq90=; b=dEtHicpkN8UqzTLDj3o+zUrYbHYE0y8uKK3+gIRPnYxRGWTYfHEvUBOH5ZrpMhV0eE 85iJdCzlnJ8Ft1HlSqjQz3T0IaLUBgC38MyvR6YFLW5FQ+po1+9+L9jBduY8Z7rpX0O4 Kat4ggo/LywCLCN2oqp/cuWp0FWpaOKHASZHqhlo6S5/kt+pitt7Atvd7jKbiuKbBREt JAInK/KPUATyhyqo1WgitN2lYEDbKR39ecmtVF6HSwWsm+Nal7h0MRykoRd5jEf3P7Nu uGLA4ublll753qFelVs6hjGP+k4qCEx4W0xRJA3xmvVrS6UByFSRePsgL9fWevkWbggw +ADA== 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:cc:subject:message-id:in-reply-to :references:reply-to:mime-version:content-transfer-encoding; bh=6FYv7XY/tmWnAIQOwTLCG09MRYbGUysfCqS0rp7gq90=; b=D0LFkRttp/SfruDQUvmF/prENA/pVi+UrT2fEWCgdBFCMbp8GYxskQorWsYH2Z9r+S jMa3fH/BHCRZ9O3h3YQTXZv8WSHt7WE+LNFeHHY9b1n4O7blagueN9UJr4VMZF8JW/Sl LNUgwBOJprkAyDzcYqlqlWHBSjoNHHDAfrqoxX2J01eJY6XILcRkC8NYswSTrDWAfa4M x1/tA40qnSf7YJB5wo9AnRRCyia/sm0c5ZIEFVnkF8UmCj1ld00Nk/yN1gCo3zWQc4GX wOrqkAM3VBoQaLdjAHwCdskE4PsNQuYFAz3Amhq3qDZ1MyhuKj2qeTD0Y9WVeRWQXZcB +S9w== X-Gm-Message-State: APzg51DNzWNKMWOTKxM4T51JlN0cpSzlHZkPQQXvfxpH5mKSy/kJZ+wP MyEthaS2I7JllDYnueyGLOWGEUj6 X-Google-Smtp-Source: ANB0VdbIZOKNMq6LR4kyCz/VVwbRsbdLYlOTNs+pxLVrpw/xXmT5GtyV8l+cX63/EaXBoQgiN058lQ== X-Received: by 2002:a1c:4887:: with SMTP id v129-v6mr5415044wma.129.1535379195877; Mon, 27 Aug 2018 07:13:15 -0700 (PDT) Received: from ernst.home (pD9E23C49.dip0.t-ipconnect.de. [217.226.60.73]) by smtp.gmail.com with ESMTPSA id p89-v6sm30962597wrc.97.2018.08.27.07.13.14 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 27 Aug 2018 07:13:14 -0700 (PDT) Date: Mon, 27 Aug 2018 16:13:13 +0200 From: Gary Jennejohn To: Meowthink Cc: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Help diagnose my Ryzen build problem Message-ID: <20180827161313.291d24b7@ernst.home> In-Reply-To: References: <20180827132905.191dbd8c@ernst.home> Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII 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: Mon, 27 Aug 2018 14:13:17 -0000 On Mon, 27 Aug 2018 20:18:46 +0800 Meowthink wrote: > Hi Gary, > > On 8/27/18, Gary Jennejohn wrote: > > On Mon, 27 Aug 2018 10:13:10 +0200 > > Phil Norman wrote: > > > >> Hi. > >> > >> I have a similar setup: Ryzen 3 and Fatal1ty X370 mini-ITX. I had some > >> trouble with instability, although my problems weren't panics, but rather > >> two issues. One was random lockups (with no evidence left in logs), but I > >> *think* this was down to an inadequately cooled graphics card. > >> > > > > I had instability problems with my Ryzen 5 - lockups for no > > apparent reason. The only recourse waas a hard reset. > > > > It turned out that there were two causes > > 1) old CPU microcode > > 2) unhandled errate in the CPU > > > > I installed the /usr/ports/sysutils/devcpu-data port, which > > allowed me to install the latest microcode using cpucontrol(8). > > > > I also used a shell script called amd_errata.sh provided by one of > > the FreeBSD committers. To my shame I can't remember exactly > > who. Note that the errata fixups are now part of the kernel in > > FreeBSD 12. > > That's kib, who has committed things in that script to both 12 [1] and > stable/11 [2]. > > Unfortunately, that's for Ryzens family 17h model 00h-0fh, whereas my > Ryzen 5 2400G's model is 11h. > AMD has also relased a Revision Guide for Family 11h. Lots of errata listed there, but I didn't look at it closely enough to say whether any are relevant to lockups. > On the microcode. It shall be updated through UEFI/BIOS updates. I > think mine is now PinnaclePI-AM4_1.0.0.4 with microcode patchlevel > 0x810100b. > Well, I installed the latest BIOS for my ASUS B350M-A also, but it was no help. The lockups disappear only after I installed the latest microde using the port. > Seems like ... the only thing I can do is sit down and wait? > > > > > After taking these steps about two months ago I have had no more > > lockups and the machine runs very stabily. > > > > [big snip] > > > > -- > > Gary Jennejohn > > > > [1] https://svnweb.freebsd.org/base?view=revision&revision=336763 > [2] https://svnweb.freebsd.org/base?view=revision&revision=337235 -- Gary Jennejohn From owner-freebsd-stable@freebsd.org Mon Aug 27 14:25:41 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 665E3108BB8C; Mon, 27 Aug 2018 14:25:41 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (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 D215572DCA; Mon, 27 Aug 2018 14:25:40 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-wm0-x236.google.com with SMTP id c14-v6so8295594wmb.4; Mon, 27 Aug 2018 07:25:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :mime-version:content-transfer-encoding; bh=gUAwE9OkPs4raYQQb/+DcgilMSgaOFRqz73uFgYKp+s=; b=tSE6AG7bOAt98N7Mal8yoZFna0uXsYgOuel6n3e9EKAdpszGHwP7HRlto+IgLLsaPb sUrgJeuYKvZ5sIqE1pP222LQ4ECY1zkjkoSzYD5SlYk20BkgO9JpyAp+xvVzQ1qT6oZk BGvWwNNJ2wO0RmGS9L7I5Ii8yFLTL1sKG5TEt9Ussav9kKOf+8tYA+AB10QkC61eEX7J oKTMVkbOB2XzBjd+WkRDyZrkTM1p0yj/rwWeE7WEukBU/RgcT0bY7tDB/z3mmvLKrBvu rLcFhScWf1rELt+eWDaofieq378rhBAXgwRtTiSBXN19nOIEeEvQZhy7LZlB7Ze2pYtV iHJQ== 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:cc:subject:message-id:in-reply-to :references:reply-to:mime-version:content-transfer-encoding; bh=gUAwE9OkPs4raYQQb/+DcgilMSgaOFRqz73uFgYKp+s=; b=OoR9D5+WY/uBltgFu/WLkY6CcbFGI3HeeA1LvcVucjoVuknmp+lGNF1omhfVJmyLSw JXtgbdcF+mWYMbDgkmWpxRG0DxObyoElXjYZ0WdxImNPkf/XxH3NDsmJD6YJ8m0US6HE Mghi8Q+GFDZ72Y0r7O2JGmKfBhGxBSXn7CFyPWu5aHpndeaJRAOwVEaRORZad8kqllbX AOrWH5Setw3lfStbhPffW9vHBDKcqxbPPG/Eg17hO793T50/RCVJpJR6Npe3fR9G3bNz BLE8L/4uS/zlluPx3feOVJ97kAyzWLXZcKgTBXjkYE2XfcCePlC83h0awOcvNaVxMPjj qe1A== X-Gm-Message-State: APzg51Di1b0zD5ZpaGOTxTTxAyAy+D6mqCtGQzn6HsxBEYrQGn0zc4si QFI/gBYJIRCwANSnFQzv8GI= X-Google-Smtp-Source: ANB0VdZBgxRFMy8Pv97mnox9UuR0cbOH8JhMK8fZZZMbHFj2T8AdKBVKK3arfkVKldlBZFity+0c6Q== X-Received: by 2002:a1c:87c9:: with SMTP id j192-v6mr5413177wmd.71.1535379939877; Mon, 27 Aug 2018 07:25:39 -0700 (PDT) Received: from ernst.home (pD9E23C49.dip0.t-ipconnect.de. [217.226.60.73]) by smtp.gmail.com with ESMTPSA id v6-v6sm10953787wro.66.2018.08.27.07.25.38 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 27 Aug 2018 07:25:39 -0700 (PDT) Date: Mon, 27 Aug 2018 16:25:37 +0200 From: Gary Jennejohn To: "karu.pruun" Cc: meowthink@gmail.com, freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Help diagnose my Ryzen build problem Message-ID: <20180827162537.05f9b576@ernst.home> In-Reply-To: References: <20180827132905.191dbd8c@ernst.home> Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII 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: Mon, 27 Aug 2018 14:25:41 -0000 On Mon, 27 Aug 2018 16:16:47 +0300 "karu.pruun" wrote: > On Mon, Aug 27, 2018 at 3:21 PM Meowthink wrote: > > That's kib, who has committed things in that script to both 12 [1] and > > stable/11 [2]. > > > > Unfortunately, that's for Ryzens family 17h model 00h-0fh, whereas my > > Ryzen 5 2400G's model is 11h. > > > > On the microcode. It shall be updated through UEFI/BIOS updates. I > > think mine is now PinnaclePI-AM4_1.0.0.4 with microcode patchlevel > > 0x810100b. > > > > Seems like ... the only thing I can do is sit down and wait? > > The revision > > https://svnweb.freebsd.org/base/head/sys/x86/x86/cpu_machdep.c?r1=336763&r2=336762&pathrev=336763 > > works around the mwait issue, i.e. it sets > > sysctl machdep.idle_mwait=0 > sysctl machdep.idle=hlt > > Now it may or may not relate to your problem, but it appears that > Ryzen 2400G also has another issue with HLT, see the DragonFly bug > report > > https://bugs.dragonflybsd.org/issues/3131 > > which AMD is aware of and is possibly working on, but it may not have > appeared in the errata yet. The bug report says that until this is > fixed, the workaround is to also disable HLT in cpu_idle. I am not > sure what is the correct value for the sysctl on FreeBSD, perhaps > > sysctl machdep.idle=0 > > or some other value? > It is in the latest errata and there are no plans to fix it. Based on the detailed description, this is a problem only in a hypervisor. AMD has a suggested workaround for it. -- Gary Jennejohn From owner-freebsd-stable@freebsd.org Mon Aug 27 15: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 D9E44108D32D; Mon, 27 Aug 2018 15:07:29 +0000 (UTC) (envelope-from meowthink@gmail.com) Received: from mail-oi0-x22c.google.com (mail-oi0-x22c.google.com [IPv6:2607:f8b0:4003:c06::22c]) (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 6A4C374ABD; Mon, 27 Aug 2018 15:07:29 +0000 (UTC) (envelope-from meowthink@gmail.com) Received: by mail-oi0-x22c.google.com with SMTP id m11-v6so27879763oic.2; Mon, 27 Aug 2018 08:07:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ppoamd3JBEGM1cHjn7e6F/AhHW1rzyopnaokDm1OZdo=; b=ICBGAR9g/s4IIz4QqLLgJaagulC2N3GcsYoicCeTkXMAypMAcLStN7NJ3qciiTZUnI boxJYu16zTuLUvVBcb3MEl3HUL28UKx6/3gXlLy32REqGfbCpg57kadsOI1jEBl+zMPI lm/75aK5J1WE0G3eSVkosfmHP+YKXtoj47UG3AZ/TB7jz43m1B54jzDIkRzj5fl0wEi9 8JYouPT1a3g6WVlGRjZVjLUTareLcx60J31S+xhibx5jOLaLvCb5mc7hx3Rk3+ohrcqn Buk+mJ/Hp4wwhovJW+z9wWDOB1W1w+x97zP5cIl3XbTdnDe5jJXYm2WJXGLbh5maYdq2 5GAw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ppoamd3JBEGM1cHjn7e6F/AhHW1rzyopnaokDm1OZdo=; b=CoC7be+6BbzQThz1EbBz1+/RV3vHgxpYTRTtfHZs7FypL1WHPju5AfGmOz1nR893Rf VA/zNfdiNJTmqBTD0CQoQLT6UtI7Xr0q2YFGdeWSs9wh7tYbQvpTF1Xb3Qm8vg0URMid SRTEYePoRavPV5z/jYkhx5ElRWnh4DbHV9S/wIFbaa60HyQ1fRihvPVlRoejFhEE+ZeF VI0d6rYXnNk5c0Ral16pdDXOG+poRS/EGeJWNUvP1pjm521DoTQhpv+eGNHz1LkQ9RC1 oZJ244rfSh3VCleIAKr9cxluNoc0A0+Tw+XY8FZ7s4V8C8wHKpyrrk4p/Ls2CsuvLvTT 8EtQ== X-Gm-Message-State: APzg51CoQXf4vx2AlJDVT1QZXb6idpMBK6f7xqRnLIp+dkH7FME0q3Ip BVbxpK0dsR4xfkVzx8JP97qkKbC8j8lOWf879gI= X-Google-Smtp-Source: ANB0VdYnKXI4HHN+ZR+WnHE8cuYAHDyzEJlwbN0xfNW62c6A9HSecBKcaiD7r4qq41IRfmMncXKQyKPBdLIfInB/ORU= X-Received: by 2002:aca:4802:: with SMTP id v2-v6mr13339208oia.259.1535382448704; Mon, 27 Aug 2018 08:07:28 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a8a:a54:0:0:0:0:0 with HTTP; Mon, 27 Aug 2018 08:07:28 -0700 (PDT) In-Reply-To: References: <20180827132905.191dbd8c@ernst.home> From: Meowthink Date: Mon, 27 Aug 2018 23:07:28 +0800 Message-ID: Subject: Re: Help diagnose my Ryzen build problem To: "karu.pruun" Cc: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" 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, 27 Aug 2018 15:07:30 -0000 Hi peeter, On 8/27/18, karu.pruun wrote: > On Mon, Aug 27, 2018 at 3:21 PM Meowthink wrote: >> That's kib, who has committed things in that script to both 12 [1] and >> stable/11 [2]. >> >> Unfortunately, that's for Ryzens family 17h model 00h-0fh, whereas my >> Ryzen 5 2400G's model is 11h. >> >> On the microcode. It shall be updated through UEFI/BIOS updates. I >> think mine is now PinnaclePI-AM4_1.0.0.4 with microcode patchlevel >> 0x810100b. >> >> Seems like ... the only thing I can do is sit down and wait? > > The revision > > https://svnweb.freebsd.org/base/head/sys/x86/x86/cpu_machdep.c?r1=336763&r2=336762&pathrev=336763 > > works around the mwait issue, i.e. it sets > > sysctl machdep.idle_mwait=0 > sysctl machdep.idle=hlt > I think that shall not apply to 2400G, which is model 11h not 1h. Here're what I have now: machdep.idle: acpi machdep.idle_available: spin, mwait, hlt, acpi machdep.idle_apl31: 0 machdep.idle_mwait: 1 > Now it may or may not relate to your problem, but it appears that > Ryzen 2400G also has another issue with HLT, see the DragonFly bug > report > > https://bugs.dragonflybsd.org/issues/3131 > Thanks a lot for that info. It's much easier to prove your problem, since it's reproducible. But mine was so random to catch... Anyway, it seems like the IRET issue [1] is still not fixed? I'm highly doubt that my issue is this related because my system became significantly more stable since I stop that irq storm from bluetooth module - Though it still panics occasionally. So could anybody tell, what's the difference between FreeBSD workaround [2] and the DragonflyBSD one? > which AMD is aware of and is possibly working on, but it may not have > appeared in the errata yet. The bug report says that until this is > fixed, the workaround is to also disable HLT in cpu_idle. I am not > sure what is the correct value for the sysctl on FreeBSD, perhaps > > sysctl machdep.idle=0 > > or some other value? In the meantime, I have this microcode # cpucontrol -m 0x8b /dev/cpuctl0 MSR 0x8b: 0x00000000 0x0810100b Hence I should use mwait? Still don't know what should I set. Any idea? > > Cheers > > Peeter > > -- > Thank you for your direction. Cheers, meowthink [1] http://lists.dragonflybsd.org/pipermail/commits/2017-August/626190.html [2] https://reviews.freebsd.org/D11780 From owner-freebsd-stable@freebsd.org Mon Aug 27 15:56:53 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 C7F74108EAAC for ; Mon, 27 Aug 2018 15:56:53 +0000 (UTC) (envelope-from pi@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 667E476AEC for ; Mon, 27 Aug 2018 15:56:53 +0000 (UTC) (envelope-from pi@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 2BCC0108EAAA; Mon, 27 Aug 2018 15:56:53 +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 1A7CC108EAA9 for ; Mon, 27 Aug 2018 15:56:53 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9939F76AEB for ; Mon, 27 Aug 2018 15:56:52 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from pi by home.opsec.eu with local (Exim 4.91 (FreeBSD)) (envelope-from ) id 1fuJsp-000363-DP; Mon, 27 Aug 2018 17:56:51 +0200 Date: Mon, 27 Aug 2018 17:56:51 +0200 From: Kurt Jaeger To: rmacklem@uoguelph.ca, stable@freebsd.org Subject: NFS via IPv6 between 11.2-REL amd64 and larger (>45 files) directories? Message-ID: <20180827155651.GW2118@home.opsec.eu> 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: Mon, 27 Aug 2018 15:56:54 -0000 Hi! I've seen a strange effect: NFS via IPv6 between 11.2-REL amd64 boxes failed for directories with more than 45 files or directories. Small directories worked. It seems to be an issue with ipv6 fragmentation (?), as can be seen by tcpdump: 17:54:16.855978 IP6 nfs-serv > nfs-client frag (0|1448) 2049 > 709: NFS reply xid 1536109002 reply ok 1440 readdir 17:54:16.855979 IP6 nfs-serv > nfs-client frag (1448|36) As soon as the NFS request is sent with fragments, it stalls. Is this a known issue ? -- pi@FreeBSD.org +49 171 3101372 2 years to go ! From owner-freebsd-stable@freebsd.org Tue Aug 28 07:54:29 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 B70AF1083182; Tue, 28 Aug 2018 07:54:29 +0000 (UTC) (envelope-from karu.pruun@gmail.com) Received: from mail-oi0-x230.google.com (mail-oi0-x230.google.com [IPv6:2607:f8b0:4003:c06::230]) (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 49C9D77E03; Tue, 28 Aug 2018 07:54:29 +0000 (UTC) (envelope-from karu.pruun@gmail.com) Received: by mail-oi0-x230.google.com with SMTP id m11-v6so1243326oic.2; Tue, 28 Aug 2018 00:54:29 -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=eAcgzY1NIaxtckyR7cbFcoGaCaI+5moTYcJs2FjUVuo=; b=mdatqCzHN8VNUWWXrqyEE6bj5OEpRiX0Fy1C8X5oWZ+BYXe+kYAcy3F+iSghmwAMjk PKHr1SUNtBGaThvcJijXGyRJi9Hfz4AtcHfoKrtVHA7XBj/WFFUer+vlmI4CiJNvucyd /Ovvfi70TFt4A7VNz2dEovlvfmSsLsVIOIA9/K6QFfRpaK31Rtu4qrKeqywQVMf3wb0N sCXlalwqXJzNaYTD5sHVQDgdjrOORFb+TEw/LrDtXwuhRFAHYt6kYVlQyhyqR6eTobsB 9DHOimYu/Yd+AAqh5D/GqX3hm85SCpJYp/whxosY3CM/PDidRIYUxfZRGi/gxpU0dsgA EHhw== 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=eAcgzY1NIaxtckyR7cbFcoGaCaI+5moTYcJs2FjUVuo=; b=oPMA6TcG3m65SzzcMqZvZm08KoAUPf8w+12jxpln44dNq+V6uAJKxYw+oh7l+Q9oMX JGB+3ej3no3V08fOFupQWP9VPQK9zcaUJF3wEAIr5FDuYuT9IWjkO8GULtpB0bJ9Z5Rs a7yYGFDMZ92HPvhQ9ZbQvNQaWhuaKVI4YAFgOlaZP+o4FApKsgLjJaVIyuTAJ4OVcdyG DMIlxvxw/yMokem9z+SozmOc9qgOeVnMCn4Gs0+zuCcUxGjLg7yaEutxOnkXe5N8ikM6 UZkGQ7U+4pC7QeF61amesotRMnuvDUi/Zk2JHlx+kAn6MyTfFFlOBvJ5Q9CSGJHIK/cN 6tFw== X-Gm-Message-State: APzg51CWmVgimPdlypOM34IWkLRWRFB31XY2NcoVt4dJhSFWw6Xv5niW kYfOmsn3Qs1KZOY2/BfxrNAKNkO4N6m4Lj7aPVUZNTUT X-Google-Smtp-Source: ANB0VdZM9jQ+0ivEdpETv6TMBivVynQBhrl1W2Zl71o2k3f+bKFIs6Dhd6s7xNrGqsB0tNbxaHcusAabGDNQRIuvDKM= X-Received: by 2002:aca:5c85:: with SMTP id q127-v6mr333957oib.127.1535442868629; Tue, 28 Aug 2018 00:54:28 -0700 (PDT) MIME-Version: 1.0 References: <20180827132905.191dbd8c@ernst.home> In-Reply-To: From: "karu.pruun" Date: Tue, 28 Aug 2018 10:54:17 +0300 Message-ID: Subject: Re: Help diagnose my Ryzen build problem To: Si Miao Cc: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" 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, 28 Aug 2018 07:54:30 -0000 On Mon, Aug 27, 2018 at 6:07 PM Meowthink wrote: > >> Unfortunately, that's for Ryzens family 17h model 00h-0fh, whereas my > >> Ryzen 5 2400G's model is 11h. > >> > >> On the microcode. It shall be updated through UEFI/BIOS updates. I > >> think mine is now PinnaclePI-AM4_1.0.0.4 with microcode patchlevel > >> 0x810100b. > >> > >> Seems like ... the only thing I can do is sit down and wait? > > > > The revision > > > > https://svnweb.freebsd.org/base/head/sys/x86/x86/cpu_machdep.c?r1=336763&r2=336762&pathrev=336763 > > > > works around the mwait issue, i.e. it sets > > > > sysctl machdep.idle_mwait=0 > > sysctl machdep.idle=hlt > > > > I think that shall not apply to 2400G, which is model 11h not 1h. > Here're what I have now: > > machdep.idle: acpi > machdep.idle_available: spin, mwait, hlt, acpi > machdep.idle_apl31: 0 > machdep.idle_mwait: 1 > > > Now it may or may not relate to your problem, but it appears that > > Ryzen 2400G also has another issue with HLT, see the DragonFly bug > > report > > > > https://bugs.dragonflybsd.org/issues/3131 > > > > Thanks a lot for that info. > It's much easier to prove your problem, since it's reproducible. But > mine was so random to catch... > Anyway, it seems like the IRET issue [1] is still not fixed? I'm > highly doubt that my issue is this related because my system became > significantly more stable since I stop that irq storm from bluetooth > module - Though it still panics occasionally. > So could anybody tell, what's the difference between FreeBSD > workaround [2] and the DragonflyBSD one? > > > which AMD is aware of and is possibly working on, but it may not have > > appeared in the errata yet. The bug report says that until this is > > fixed, the workaround is to also disable HLT in cpu_idle. I am not > > sure what is the correct value for the sysctl on FreeBSD, perhaps > > > > sysctl machdep.idle=0 > > > > or some other value? > > In the meantime, I have this microcode > > # cpucontrol -m 0x8b /dev/cpuctl0 > MSR 0x8b: 0x00000000 0x0810100b > > Hence I should use mwait? > Still don't know what should I set. Any idea? If I was you, I'd play around with the sysctls mentioned above and see if it helps. Start with disabling both mwait and hlt, perhaps machdep.idle=spin machdep.idle_mwait=0 (assuming that 'spin' means hlt will not used) and then if that does not lead to a panic, try enabling mwait. I can't test 2400G since I don't have it any more. I booted FreeBSD a couple of times but did not run it over long periods of time. Cheers Peeter -- From owner-freebsd-stable@freebsd.org Tue Aug 28 07:56:13 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 ACBDE1083306; Tue, 28 Aug 2018 07:56:13 +0000 (UTC) (envelope-from des@des.no) Received: from smtp.des.no (smtp.des.no [194.63.250.102]) by mx1.freebsd.org (Postfix) with ESMTP id 4720578057; Tue, 28 Aug 2018 07:56:13 +0000 (UTC) (envelope-from des@des.no) Received: from next.des.no (smtp.des.no [194.63.250.102]) by smtp.des.no (Postfix) with ESMTP id CF1588C01; Tue, 28 Aug 2018 07:56:05 +0000 (UTC) Received: by next.des.no (Postfix, from userid 1001) id AE0F18CDF; Tue, 28 Aug 2018 09:56:05 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: blubee blubeeme Cc: Hans Petter Selasky , pmcnary@cameron.net, Johannes Lundberg , freebsd-stable@freebsd.org, mmacy@freebsd.org, Ali Abdallah , FreeBSD current Subject: Re: drm / drm2 removal in 12 In-Reply-To: (blubee blubeeme's message of "Mon, 27 Aug 2018 06:21:57 +0800") References: <20180824215302.ivfna55jtrtc5trg@freebsd480.station> <86k1oepbdr.fsf@next.des.no> <180f8f99-5fa1-1411-59e6-856e3ebc370c@cameron.net> <86d0u5otu4.fsf@next.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (berkeley-unix) Date: Tue, 28 Aug 2018 09:56:05 +0200 Message-ID: <868t4qudpm.fsf@next.des.no> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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, 28 Aug 2018 07:56:13 -0000 blubee blubeeme writes: > You seem to miss the point where the you avoid breaking the system for > any users not on the bleeding edge. You seem to miss the point where nobody is interested in anything you have to say any more. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-stable@freebsd.org Tue Aug 28 15:47:22 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 8C76F108FEF5; Tue, 28 Aug 2018 15:47:22 +0000 (UTC) (envelope-from meowthink@gmail.com) Received: from mail-oi0-x241.google.com (mail-oi0-x241.google.com [IPv6:2607:f8b0:4003:c06::241]) (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 1E25A8A7DC; Tue, 28 Aug 2018 15:47:22 +0000 (UTC) (envelope-from meowthink@gmail.com) Received: by mail-oi0-x241.google.com with SMTP id m11-v6so3707949oic.2; Tue, 28 Aug 2018 08:47:22 -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:cc; bh=qXyAvNjumhujN3WX0qEB6idGe6QmP0AiZO0Bkfb0+Gg=; b=uB8Xfrf0TW3b60TdeXe9W+MR44PCoNT7PvmnVozjh24mxFpZhYHmHnqx5+8fPaU5I0 CzDBYrWuTmOOq7ZarZruSyNT3Qu8vg18DAQvH7q1PchEt8cd8GGOaY3CfzrWf34p/D6p hcuappI2CqlbA9RtwK5fG+z/ihJzW/bWCDRpR2JSDFuPPILTjCbSmparxsBZU29wHGA1 VgYSEsKpeQYm9EFBO8jIX5iOrw+uym3v3wEMMKQLsq0qX9oFKLXJpBkldaOKMqglZkA+ WO7KBA7N5ISut5XdTb9iRaiMhOLjUb9Gi8JwXgb6WQo7ilM4ahA5Xbvh55QbfK7/2UCa kFTg== 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:cc; bh=qXyAvNjumhujN3WX0qEB6idGe6QmP0AiZO0Bkfb0+Gg=; b=ez+wStvih7XCPuxdoN9rRwC657l8ClD0W5+fdW4hepgduHvHGqlMASE8sXL9KcAKk+ q4oNrXqIngwT0CZJXmRmxHXiYZdJllncxCNzH/pgptdvCFjh3X7EX7nuIXw1HItkaIXF 19Tf4BIL7dqSenjJttozI8cmao5MmJhaIt+2RrsupeD/fHEq7kDHgMOyWzLQ9uKm9ftO l5i76dqeeDVIoqTLppSWnJ50UER+wrsQYVyKCz+2WfEHG5a6jP4KNHGXJbo1p47ESj6x 3yoa7tlZXUhpeYovPdaZzMREyfafLWc+ppqa8aur2lx7g9QwiZXoCTrx+Cuwhkj+eGo+ qc+g== X-Gm-Message-State: APzg51DHeOkSH5DGUUlKF5rWHbZuNeWiLuLdvxm/T0OxatemTDSi9PBa yn6IrvsdpU/ETyruQ25ML1VLKORm6RnCUZrBtZA= X-Google-Smtp-Source: ANB0VdZEGQXLFqeWgykXke6mXTZ1kQ7wLpdovAqm3jYSzN4p9/w84RW3HRz3Y0HFyconwrGM+7ZcMLcuef4NTYBSWuU= X-Received: by 2002:aca:4802:: with SMTP id v2-v6mr1841203oia.259.1535471241321; Tue, 28 Aug 2018 08:47:21 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a8a:a54:0:0:0:0:0 with HTTP; Tue, 28 Aug 2018 08:47:20 -0700 (PDT) From: Meowthink Date: Tue, 28 Aug 2018 23:47:20 +0800 Message-ID: Subject: Re: Help diagnose my Ryzen build problem (in progress) To: "karu.pruun" Cc: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" 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, 28 Aug 2018 15:47:22 -0000 Hi Peeter, On 8/28/18, karu.pruun wrote: > On Mon, Aug 27, 2018 at 6:07 PM Meowthink wrote: > >> >> Unfortunately, that's for Ryzens family 17h model 00h-0fh, whereas my >> >> Ryzen 5 2400G's model is 11h. >> >> >> >> On the microcode. It shall be updated through UEFI/BIOS updates. I >> >> think mine is now PinnaclePI-AM4_1.0.0.4 with microcode patchlevel >> >> 0x810100b. >> >> >> >> Seems like ... the only thing I can do is sit down and wait? >> > >> > The revision >> > >> > https://svnweb.freebsd.org/base/head/sys/x86/x86/cpu_machdep.c?r1=336763&r2=336762&pathrev=336763 >> > >> > works around the mwait issue, i.e. it sets >> > >> > sysctl machdep.idle_mwait=0 >> > sysctl machdep.idle=hlt >> > >> >> I think that shall not apply to 2400G, which is model 11h not 1h. >> Here're what I have now: >> >> machdep.idle: acpi >> machdep.idle_available: spin, mwait, hlt, acpi >> machdep.idle_apl31: 0 >> machdep.idle_mwait: 1 >> >> > Now it may or may not relate to your problem, but it appears that >> > Ryzen 2400G also has another issue with HLT, see the DragonFly bug >> > report >> > >> > https://bugs.dragonflybsd.org/issues/3131 >> > >> >> Thanks a lot for that info. >> It's much easier to prove your problem, since it's reproducible. But >> mine was so random to catch... >> Anyway, it seems like the IRET issue [1] is still not fixed? I'm >> highly doubt that my issue is this related because my system became >> significantly more stable since I stop that irq storm from bluetooth >> module - Though it still panics occasionally. >> So could anybody tell, what's the difference between FreeBSD >> workaround [2] and the DragonflyBSD one? >> >> > which AMD is aware of and is possibly working on, but it may not have >> > appeared in the errata yet. The bug report says that until this is >> > fixed, the workaround is to also disable HLT in cpu_idle. I am not >> > sure what is the correct value for the sysctl on FreeBSD, perhaps >> > >> > sysctl machdep.idle=0 >> > >> > or some other value? >> >> In the meantime, I have this microcode >> >> # cpucontrol -m 0x8b /dev/cpuctl0 >> MSR 0x8b: 0x00000000 0x0810100b >> >> Hence I should use mwait? >> Still don't know what should I set. Any idea? > > > If I was you, I'd play around with the sysctls mentioned above and see > if it helps. Start with disabling both mwait and hlt, perhaps > > machdep.idle=spin > machdep.idle_mwait=0 > > (assuming that 'spin' means hlt will not used) and then if that does > not lead to a panic, try enabling mwait. I can't test 2400G since I > don't have it any more. I booted FreeBSD a couple of times but did not > run it over long periods of time. It works! After hours and hours of different stressing. I got 8 copies of gcc built without any problem. But it costs lots of power and the fan will become very annoying. As so, I don't think I'll test long term stability with this state. machdep.idle: acpi -> spin - will add ~5W, maybe some deeper C states disabled? machdep.idle_mwait: 1 -> 0 - will add another ~50W, CPUs are working insomniac. I tried to set machdep.idle_mwait to 1, or machdep.idle to mwait. Both failed with panics when I start building gcc pass by pass. I'm pretty sure mwait will cause problem, as once I experienced a panic immediately after I issued the sysctl command (the 2nd dump info followed) So my next step will be hlt. Still need some time, though. > > Cheers > > Peeter > > -- > Cheers, meowthink ------------------------------------------------------------------------ machdep.idle=mwait panic: ffs_syncvnode: syncing truncated data. cpuid = 7 KDB: stack backtrace: #0 0xffffffff80b414b7 at kdb_backtrace+0x67 #1 0xffffffff80afa9e7 at vpanic+0x177 #2 0xffffffff80afa863 at panic+0x43 #3 0xffffffff80dcddc4 at ffs_syncvnode+0x5a4 #4 0xffffffff80dcc915 at ffs_fsync+0x25 #5 0xffffffff810ffcb2 at VOP_FSYNC_APV+0x82 #6 0xffffffff80bc3a62 at sched_sync+0x412 #7 0xffffffff80abd813 at fork_exit+0x83 #8 0xffffffff80f5cc7e at fork_trampoline+0xe ------------------------------------------------------------------------ machdep.idle_mwait=1 Fatal trap 9: general protection fault while in kernel mode cpuid = 7; apic id = 07 instruction pointer = 0x20:0xffffffff80e094fe stack pointer = 0x0:0xfffffe081e5df9e0 frame pointer = 0x0:0xfffffe081e5dfa50 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 17 (dom0) trap number = 9 panic: general protection fault cpuid = 7 KDB: stack backtrace: #0 0xffffffff80b414b7 at kdb_backtrace+0x67 #1 0xffffffff80afa9e7 at vpanic+0x177 #2 0xffffffff80afa863 at panic+0x43 #3 0xffffffff80f7c14f at trap_fatal+0x35f #4 0xffffffff80f7b70e at trap+0x5e #5 0xffffffff80f5bccc at calltrap+0x8 #6 0xffffffff80e07a17 at vm_pageout+0x87 #7 0xffffffff80abd813 at fork_exit+0x83 #8 0xffffffff80f5cc7e at fork_trampoline+0xe From owner-freebsd-stable@freebsd.org Tue Aug 28 17:58:36 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 B94C31092CF6 for ; Tue, 28 Aug 2018 17:58:36 +0000 (UTC) (envelope-from andrie.rowe@callflexnet.com) Received: from mail-it0-x248.google.com (mail-it0-x248.google.com [IPv6:2607:f8b0:4001:c0b::248]) (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 574F18EC1F for ; Tue, 28 Aug 2018 17:58:36 +0000 (UTC) (envelope-from andrie.rowe@callflexnet.com) Received: by mail-it0-x248.google.com with SMTP id m185-v6so2399990itm.1 for ; Tue, 28 Aug 2018 10:58:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=callflexnet.com; s=google; h=mime-version:message-id:date:subject:from:to :content-transfer-encoding; bh=rP9ElSV3t/1vNOjKbiAJRpLucLk+0pPfKX/xdgOwGg8=; b=FJbBmQ9MlNjqfXSsxCsNK9m+QkQjWx4pMJr6gKg7scapIvipg0WjlfivTW3/SMxD9u D9YOxUqdWDb08zfLWEd/8saMTmYZon214HaZzhnrojUWCVHV1yTpPHI1f0oQpmm00lY+ TjE63T04XZeywhQFD3ZNs8TmHR5wnheH4JvzT0PGlM0SDTmV00RARnLomcfd+zgDmrJc Ly/ia4gKSgUxrRu7qJg+Y5i4PFZ7q2Bz22Kji/2pNllBVvn3ll0LHadszej9TrU2wGjG Fs2Xo1M/mvT2A2zsJ4KIqD7em/fNYqWVXvozc1eh8r4wMdUfvB4/kWGuqLJvrKBauyAA C/GA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:message-id:date:subject:from:to :content-transfer-encoding; bh=rP9ElSV3t/1vNOjKbiAJRpLucLk+0pPfKX/xdgOwGg8=; b=lP4UOE4bi3j4Npch8ehEliUJnTGeaTRJNt2R4BfSyYNLxPMM13Zoh4laZbTsHvIRTW IyzAgB04FUqDqWW5o1MH8PsItUx73jdzQgsZtMQpvZyG/u2e3nx3ivSbvKCLgsb8C4d/ Etay2X9HTJ71Os+YBOhEML8SRw1lSL1Lk2wtk5pioPh6Fu461e3gVe0x/+cW88uINzhf VE5od6HIN/u5w2Cr1LkuPOaxxVE+En1aJS9UiJgcs0nY3mjD1nYdPnCPWa24JCTxvzN0 rnjkaMRxFK40A9U798z2vQUN3HUaGigWjkld/G3hC8hXDY4/rTLUOwXWhNPO6h33jxka 8CvQ== X-Gm-Message-State: APzg51DncslbdAVsF1IPAqOxue1f4XcF41mtTarsoyJhWhEd7OY/8NFm PNtptV4CkSLHPeBsnyWol2yo+Q7b2Wfe X-Google-Smtp-Source: ANB0VdbSXuNivnzEgSXwkJ+3IKhYyTJCcw5Wpzn+rF8beUSvgKfDGKqhFT/Tqm6Ngzq1uQBFjN2EslNwOw== MIME-Version: 1.0 X-Received: by 2002:a6b:4919:: with SMTP id u25-v6mr1115502iob.0.1535479115637; Tue, 28 Aug 2018 10:58:35 -0700 (PDT) Message-ID: <0000000000003f6d7b0574829749@google.com> Date: Tue, 28 Aug 2018 17:58:35 +0000 Subject: Managed Service Providers (MSPs) From: andrie.rowe@callflexnet.com To: freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8"; format=flowed; delsp=yes Content-Transfer-Encoding: base64 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, 28 Aug 2018 17:58:36 -0000 SGksDQpJIGp1c3Qgd2FudGVkIHRvIGNoZWNrIGlmIHlvdSB3b3VsZCBiZSBpbnRlcmVzdGVkIGlu IGEgbGlzdCBvZiBNYW5hZ2VkICANClNlcnZpY2UgUHJvdmlkZXJzIChNU1BzKSBhbmQgTWFuYWdl ZCBTZWN1cml0eSBTZXJ2aWNlIFByb3ZpZGVycyAoTVNTUHMpPw0KDQpXZSBhbHNvIGhhdmUgdGhl IGRhdGEgaW50ZWxsaWdlbmNlIG9mOg0K4oCiICAgICAgIE1hbmFnZWQgU2VydmljZSBQcm92aWRl cnMgKE1TUOKAmXMpDQrigKIgICAgICAgTWFuYWdlZCBTZWN1cml0eSBTZXJ2aWNlIFByb3ZpZGVy cyAoTVNTUOKAmXMNCuKAoiAgICAgICBJVCBEZWNpc2lvbiBNYWtlcnMg4oCTIDZtaWxsaW9uIGFj cm9zcyBhbGwgaW5kdXN0cnkNCuKAoiAgICAgICBCdXNpbmVzcyBEZWNpc2lvbiBNYWtlcnMg4oCT IDEwIG1pbGxpb24gYWNyb3NzIGFsbCBpbmR1c3RyeQ0K4oCiICAgICAgIFZhbHVlIEFkZGVkIFJl c2VsbGVycy0gVkFScw0K4oCiICAgICAgIEluZGVwZW5kZW50IFNvZnR3YXJlIFZlbmRvcnMtIElT VnMNCuKAoiAgICAgICBTeXN0ZW0gSW50ZWdyYXRvcnMtIFNJcw0K4oCiICAgICAgIFZvSVAgU2Vy dmljZSBQcm92aWRlcnMuDQrigKIgICAgICAgVGVsZWNvbW11bmljYXRpb25zIFNlcnZpY2UgUHJv dmlkZXJzIChUU1BzKQ0K4oCiICAgICAgIEFwcGxpY2F0aW9uIFNlcnZpY2UgUHJvdmlkZXJzIChB U1BzKQ0K4oCiICAgICAgIElUIE1hbmFnZWQgU2VydmljZXMgUHJvdmlkZXJzIChJVE1TUCkNCuKA oiAgICAgICBTdG9yYWdlIFNlcnZpY2UgUHJvdmlkZXJzIChTU1BzKQ0KDQpLaW5kbHkgcmV2aWV3 IGFuZCBsZXQgbWUga25vdyBpZiBJIGNhbiBzaGFyZSBtb3JlIGluZm9ybWF0aW9uIG9uIHRoaXMu DQpJIGxvb2sgZm9yd2FyZCB0byBoZWFyaW5nIGZyb20geW91Lg0KDQpSZWdhcmRzLA0KQW5kcmll DQpNYXJrZXRpbmcgU3BlY2lhbGlzdA0KDQpJZiB5b3UgZG9uJ3Qgd2FudCB0byBpbmNsdWRlIHlv dXJzZWxmIGluIG91ciBtYWlsaW5nIGxpc3QsIHBsZWFzZSByZXBseSAgDQpiYWNrIOKAnExlYXZl IE91dCIiIGluIGEgc3ViamVjdCBsaW5lDQo= From owner-freebsd-stable@freebsd.org Wed Aug 29 02:28:53 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 2445E109E65D; Wed, 29 Aug 2018 02:28:53 +0000 (UTC) (envelope-from meowthink@gmail.com) Received: from mail-oi0-x241.google.com (mail-oi0-x241.google.com [IPv6:2607:f8b0:4003:c06::241]) (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 95C9D778DC; Wed, 29 Aug 2018 02:28:52 +0000 (UTC) (envelope-from meowthink@gmail.com) Received: by mail-oi0-x241.google.com with SMTP id l202-v6so6498663oig.7; Tue, 28 Aug 2018 19:28:52 -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=lWmdyp8DhnDp22oaEuQ0u67p+c1T3HQRt6arR6PMxlg=; b=eQsWrGMA94Gww9M8JeJTNt4gAJ0r/Hyg154PTe+x9zVwytS94HMshb7wpmwspyQttK CWYlQkXMGsf+XLN9goOYfm8isbwpOJ+z/VTMINov6XFz1lKM5TluriocNB64IsQYgf3t uMiE3k25Fine9+Q4YIkc+Y5n5jjt92fqJ//LznBEWhy4q8eQP0TMb/rCoXpyLKYEd8o5 TOyEPR6rUqg+wkskIW42mkLG4eLl/plBRnqHe13B+7mBZJg2tle+/skkEFtoMknzlLtx FFaNUpYrQnx5HHqkp7GLqyj5kXkqbmu2Av2cHAXz0UutKUooq7a4hcIltDLDkrLCgWjP 12jg== 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=lWmdyp8DhnDp22oaEuQ0u67p+c1T3HQRt6arR6PMxlg=; b=gTAWuYivSB3lHw6TTqwchh0YMfqO4Ec7gzgNU+n9jD299M2do2+07t8pQz8vUGEcSn RqyKgvX9QR7hciUWW5lBhZrdjFt4AaQwsJsAxfH1Bo0oQEuBBzSoBCW0tl3sRMt0zZ2b f/923Quo8Ex4QhwToCNjY43CchCQpaj4INPuqMx9dl31i6n96GuZw812Rp/xezyJoGTR XBMieuhtwX4OTkJcw3grql1FT4d2d/32n1ZpenUKKW4fkkrQJgRn+vAjjs388ILXXuzg 1vCgm052nJESoo+VDsR2hkMA+nOVW/MqJ3CTC5DoXw1TUKyJ3qNMc0ePv+XlzIAXXTV1 RaIg== X-Gm-Message-State: APzg51CvO2SV/frbn+fS0D3UXSBS8mRfQzod7xp3ImiYWa2cq4sTODml oLytol6Etjn2P576hvyS1RGg3BSUMa9O0giPtAQ= X-Google-Smtp-Source: ANB0VdZJK3iZOJd1qAcWuqS2ciqb88xgGuEIDGUYs2h2okSQcu3UIIEGHBGhDnZVtSRg/DGnLgxHysj/Nlo7gSuXepU= X-Received: by 2002:aca:4802:: with SMTP id v2-v6mr805832oia.259.1535509731816; Tue, 28 Aug 2018 19:28:51 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Meowthink Date: Wed, 29 Aug 2018 10:28:40 +0800 Message-ID: Subject: Re: Help diagnose my Ryzen build problem (in progress) To: "karu.pruun" Cc: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" 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, 29 Aug 2018 02:28:53 -0000 Update: machdep.idle = hlt and machdep.idle_mwait = 0 failed also. It can't last even longer than machdep.idle = mwait, which could normally panic after a few passes of building gcc. I tried hlt twice, both not longer than half hour. Now, as another round of building 4 gccs in parallel is going to finish, with machdep.idle = spin and machdep.idle_mwait = 0. Can I say Ryzen 2400G probably have issues with both mwait and hlt? Regards, meowthink Fatal trap 12: page fault while in user mode cpuid = 6; apic id = 06 fault virtual address = 0x819cd0000 fault code = user write data, reserved bits in PTE instruction pointer = 0x43:0x80195de26 stack pointer = 0x3b:0x7fffffffb0b8 frame pointer = 0x3b:0x7fffffffb100 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 3, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 17888 (ld) trap number = 12 panic: page fault cpuid = 6 KDB: stack backtrace: #0 0xffffffff80b414b7 at kdb_backtrace+0x67 #1 0xffffffff80afa9e7 at vpanic+0x177 #2 0xffffffff80afa863 at panic+0x43 #3 0xffffffff80f7c14f at trap_fatal+0x35f #4 0xffffffff80f7c1a9 at trap_pfault+0x49 #5 0xffffffff80f7ba10 at trap+0x360 #6 0xffffffff80f5bccc at calltrap+0x8 On Tue, Aug 28, 2018 at 11:47 PM Meowthink wrote: > > Hi Peeter, > > On 8/28/18, karu.pruun wrote: > > On Mon, Aug 27, 2018 at 6:07 PM Meowthink wrote: > > > >> >> Unfortunately, that's for Ryzens family 17h model 00h-0fh, whereas my > >> >> Ryzen 5 2400G's model is 11h. > >> >> > >> >> On the microcode. It shall be updated through UEFI/BIOS updates. I > >> >> think mine is now PinnaclePI-AM4_1.0.0.4 with microcode patchlevel > >> >> 0x810100b. > >> >> > >> >> Seems like ... the only thing I can do is sit down and wait? > >> > > >> > The revision > >> > > >> > https://svnweb.freebsd.org/base/head/sys/x86/x86/cpu_machdep.c?r1=336763&r2=336762&pathrev=336763 > >> > > >> > works around the mwait issue, i.e. it sets > >> > > >> > sysctl machdep.idle_mwait=0 > >> > sysctl machdep.idle=hlt > >> > > >> > >> I think that shall not apply to 2400G, which is model 11h not 1h. > >> Here're what I have now: > >> > >> machdep.idle: acpi > >> machdep.idle_available: spin, mwait, hlt, acpi > >> machdep.idle_apl31: 0 > >> machdep.idle_mwait: 1 > >> > >> > Now it may or may not relate to your problem, but it appears that > >> > Ryzen 2400G also has another issue with HLT, see the DragonFly bug > >> > report > >> > > >> > https://bugs.dragonflybsd.org/issues/3131 > >> > > >> > >> Thanks a lot for that info. > >> It's much easier to prove your problem, since it's reproducible. But > >> mine was so random to catch... > >> Anyway, it seems like the IRET issue [1] is still not fixed? I'm > >> highly doubt that my issue is this related because my system became > >> significantly more stable since I stop that irq storm from bluetooth > >> module - Though it still panics occasionally. > >> So could anybody tell, what's the difference between FreeBSD > >> workaround [2] and the DragonflyBSD one? > >> > >> > which AMD is aware of and is possibly working on, but it may not have > >> > appeared in the errata yet. The bug report says that until this is > >> > fixed, the workaround is to also disable HLT in cpu_idle. I am not > >> > sure what is the correct value for the sysctl on FreeBSD, perhaps > >> > > >> > sysctl machdep.idle=0 > >> > > >> > or some other value? > >> > >> In the meantime, I have this microcode > >> > >> # cpucontrol -m 0x8b /dev/cpuctl0 > >> MSR 0x8b: 0x00000000 0x0810100b > >> > >> Hence I should use mwait? > >> Still don't know what should I set. Any idea? > > > > > > If I was you, I'd play around with the sysctls mentioned above and see > > if it helps. Start with disabling both mwait and hlt, perhaps > > > > machdep.idle=spin > > machdep.idle_mwait=0 > > > > (assuming that 'spin' means hlt will not used) and then if that does > > not lead to a panic, try enabling mwait. I can't test 2400G since I > > don't have it any more. I booted FreeBSD a couple of times but did not > > run it over long periods of time. > > It works! > After hours and hours of different stressing. I got 8 copies of gcc > built without any problem. > > But it costs lots of power and the fan will become very annoying. As > so, I don't think I'll test long term stability with this state. > > machdep.idle: acpi -> spin > - will add ~5W, maybe some deeper C states disabled? > machdep.idle_mwait: 1 -> 0 > - will add another ~50W, CPUs are working insomniac. > > I tried to set machdep.idle_mwait to 1, or machdep.idle to mwait. Both > failed with panics when I start building gcc pass by pass. > > I'm pretty sure mwait will cause problem, as once I experienced a > panic immediately after I issued the sysctl command (the 2nd dump info > followed) > > So my next step will be hlt. Still need some time, though. > > > > > Cheers > > > > Peeter > > > > -- > > > > Cheers, > meowthink > > ------------------------------------------------------------------------ > machdep.idle=mwait > > panic: ffs_syncvnode: syncing truncated data. > cpuid = 7 > KDB: stack backtrace: > #0 0xffffffff80b414b7 at kdb_backtrace+0x67 > #1 0xffffffff80afa9e7 at vpanic+0x177 > #2 0xffffffff80afa863 at panic+0x43 > #3 0xffffffff80dcddc4 at ffs_syncvnode+0x5a4 > #4 0xffffffff80dcc915 at ffs_fsync+0x25 > #5 0xffffffff810ffcb2 at VOP_FSYNC_APV+0x82 > #6 0xffffffff80bc3a62 at sched_sync+0x412 > #7 0xffffffff80abd813 at fork_exit+0x83 > #8 0xffffffff80f5cc7e at fork_trampoline+0xe > > ------------------------------------------------------------------------ > machdep.idle_mwait=1 > > Fatal trap 9: general protection fault while in kernel mode > cpuid = 7; apic id = 07 > instruction pointer = 0x20:0xffffffff80e094fe > stack pointer = 0x0:0xfffffe081e5df9e0 > frame pointer = 0x0:0xfffffe081e5dfa50 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 17 (dom0) > trap number = 9 > panic: general protection fault > cpuid = 7 > KDB: stack backtrace: > #0 0xffffffff80b414b7 at kdb_backtrace+0x67 > #1 0xffffffff80afa9e7 at vpanic+0x177 > #2 0xffffffff80afa863 at panic+0x43 > #3 0xffffffff80f7c14f at trap_fatal+0x35f > #4 0xffffffff80f7b70e at trap+0x5e > #5 0xffffffff80f5bccc at calltrap+0x8 > #6 0xffffffff80e07a17 at vm_pageout+0x87 > #7 0xffffffff80abd813 at fork_exit+0x83 > #8 0xffffffff80f5cc7e at fork_trampoline+0xe From owner-freebsd-stable@freebsd.org Wed Aug 29 08:11:36 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 82FBD1080DE7; Wed, 29 Aug 2018 08:11:36 +0000 (UTC) (envelope-from karu.pruun@gmail.com) Received: from mail-oi0-x22e.google.com (mail-oi0-x22e.google.com [IPv6:2607:f8b0:4003:c06::22e]) (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 1F7E681B27; Wed, 29 Aug 2018 08:11:36 +0000 (UTC) (envelope-from karu.pruun@gmail.com) Received: by mail-oi0-x22e.google.com with SMTP id k12-v6so7622763oiw.8; Wed, 29 Aug 2018 01:11:36 -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=5nbQfoZPfL3RocRjqN2W0Hs9Tah2+3TNWtWblMla8QY=; b=MWioYp1b57fCfy4WVAUj9HgxG9Aptmah23PJ2EdZf8FO/npv+/s5KHtXQAj8PkVwvv 40iK/NiPYL16jpN47YsNgYQ19i4+Nv9VbGK9C8YSKrxVEo4NmZFFtcTWSNjG0v3naA7p KaadQnJMNV02pg8W7VY+c0G2xIDsbA0t5qW3b5C9K8PLjm+RGuO8nY6vxsZ28WwJfg/O yJVIUiIP0LFhX21d9vZ76sWlvWuRLiLYrqtAT81miX6M1DCXdIjJrJ1ZiRLqSLDYyIH8 Wq+EfCuxFcsDeoCHOpqx0eqpZrLEkMXEoL1Nbo/npGrMW0zttsngJqwcqt9dtGtpa0gL F+GQ== 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=5nbQfoZPfL3RocRjqN2W0Hs9Tah2+3TNWtWblMla8QY=; b=AzJUOYbje3LhRv2ixB96xzUQLApbL2VjtgJfRuMwuavsBt4bqUkhAk/TQVnIG3YUAS jdpmH9oLPDKkPxmjHPBBhoFNQCRnt3hd9rVUqeCMaes3cgtZvGBEDf4bePjXmt+nWmru 9nOmLvjCZHpo/YOoC2TPqUjUmyXlY3HoyM7rU5jTN6EX4srQmLl3rEefFCbFZmO0CsDx mn9fqGuLHAxp3Zzqey+xOv0T+gQlz3rfmq8KJfL55DrDF/ComJ12ZklVdvVIz1VfH/XI aqw5AXOaL7UKneH7MKuh8ov9HXWnBClxEaUdVenYbVtd5oEzWgat3xEytHt4I8kI1v0t 4wBg== X-Gm-Message-State: APzg51BMckyEQexHtEhHPsCYM671ZJCstQLfZ2bKzrTWGe8G3H29n6hz 1zH3e17DHC8QtV5wHN0c/JAP8APcb2K7MOHCjCM= X-Google-Smtp-Source: ANB0VdaZPdnDT3zX8vf24tG1jU7z+epH8FJ4JNjAqcGQJAJ5/ht/EwHShVzrssFnoUminYpdmp5aucsXb93/oEK5XKI= X-Received: by 2002:aca:b1c1:: with SMTP id a184-v6mr1549838oif.182.1535530295134; Wed, 29 Aug 2018 01:11:35 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: "karu.pruun" Date: Wed, 29 Aug 2018 11:11:24 +0300 Message-ID: Subject: Re: Help diagnose my Ryzen build problem (in progress) To: Si Miao Cc: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" 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, 29 Aug 2018 08:11:36 -0000 On Wed, Aug 29, 2018 at 5:28 AM Meowthink wrote: > > Update: > > machdep.idle = hlt and machdep.idle_mwait = 0 failed also. It can't > last even longer than machdep.idle = mwait, which could normally panic > after a few passes of building gcc. I tried hlt twice, both not longer > than half hour. > > Now, as another round of building 4 gccs in parallel is going to finish, with > machdep.idle = spin and machdep.idle_mwait = 0. > Can I say Ryzen 2400G probably have issues with both mwait and hlt? I suppose we can conclude that HLT is a culprit as it causes issues both on FreeBSD and DragonFly. On DragonFly it occurs in an isolated case where I had to run java. Otherwise the desktop would last for 3 - 4 weeks with no problems (and I only had to reboot since I built a new kernel). Also, when I finished running java, I switched on HLT again to get better power saving. But that said, yes, Ryzen 2400G has an issue with HLT in general. This has not been mentioned in the Revision guide for family 17h, and the latter does not explicitly include 2400G, which is model 11h as you said. https://support.amd.com/TechDocs/55449_Fam_17h_M_00h-0Fh_Rev_Guide.pdf Regarding MWAIT, the DragonFly bug report says that the microcode update 0x0810100B fixes this. But I can't comment since I did not touch that at all. Cheers Peeter -- From owner-freebsd-stable@freebsd.org Wed Aug 29 19:01:07 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 A8D6010929E0 for ; Wed, 29 Aug 2018 19:01:07 +0000 (UTC) (envelope-from michael.foster@crmdatalead.com) Received: from a2nlsmtp01-05.prod.iad2.secureserver.net (a2nlsmtp01-05.prod.iad2.secureserver.net [198.71.225.49]) (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 5A7F47A5FD for ; Wed, 29 Aug 2018 19:01:07 +0000 (UTC) (envelope-from michael.foster@crmdatalead.com) Received: from a2plcpnl0534.prod.iad2.secureserver.net ([198.71.236.26]) by : HOSTING RELAY : with SMTP id v5hEfh5M1C7rkv5hEfVGvb; Wed, 29 Aug 2018 12:00:04 -0700 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=crmdatalead.com; s=default; h=Content-Type:MIME-Version:Message-ID:Date: Subject:To:From:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=qFtewvbBsfMTl0VbMZ18J332iTf94X26pdyU1tX6QQQ=; b=dWeYTCRJmfSLbiVU3URADTCnjz MTdGkCCQrWXp/829bEl4c2YgJAKi9GaWKbjcXMslUzK9tW9j5D/Tsljf0suWVTWlczGueMSoO0LzV vAAUyWhpBkVuomzs6A4JvCNHncsfBuUl2DY2NSmVkU5IbDHB9ew4AukpaGN3oS9T3GFSBcPGZoLkL qj3rJr1C9CdYPE0OX2uOeq2shNghz0rIgQvJw7IQsXm7A5uQ9u1Nz/Dnqn6OHzARdmh4GXIJe6TJy wx7eZ4QBpa/ENqDInvWu579+T9JBqouRwBM8gpVmfQo01mKY3EaH7+5Q595tlb/mP/OWX0hxEdWlD Fr7NhwuQ==; Received: from [171.48.20.190] (port=60009 helo=AdminPC) by a2plcpnl0534.prod.iad2.secureserver.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.91) (envelope-from ) id 1fv5DZ-00B9Va-21 for freebsd-stable@freebsd.org; Wed, 29 Aug 2018 11:29:26 -0700 From: "Michael Foster" To: Subject: Attendees list of Educause - 2018 Date: Wed, 29 Aug 2018 14:25:46 -0400 Message-ID: MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AdQ/xYKwaKyA/mi9TfWqZSa9XywPZw== Content-Language: en-us X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - a2plcpnl0534.prod.iad2.secureserver.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - crmdatalead.com X-Get-Message-Sender-Via: a2plcpnl0534.prod.iad2.secureserver.net: authenticated_id: michael.foster@crmdatalead.com X-Authenticated-Sender: a2plcpnl0534.prod.iad2.secureserver.net: michael.foster@crmdatalead.com X-Source: X-Source-Args: X-Source-Dir: X-CMAE-Envelope: MS4wfLMf6R2ZxMuhboSTi3Y3ubUPtQMXhez1xxGL5P9ZJy+S5q/ZalFhkl1xo/uuJ81ClDOWsqjJ2AZZyTpl93kq02v+oBuZ0hTJQZIDwwKDK/3rok08UdcX zNuHJmkVarTboQXjY8suSCN4tlv6rPfG7qcHHvpigc2uaXTVJPI/yjzQfpp1r732noXhrvzfzMSwrDRoaEbyPOLkXfzMT45FRBTsgCXfpeFWfQ1uNhb8WEoT Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 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: Wed, 29 Aug 2018 19:01:07 -0000 Hi, Hope this mail finds you well. Would you be interested in Attendees list of Educause - 2018? We follow a stringent process in creating Attendee database with all the necessary information that you would need for an organized marketing campaign. List Contains: Contact Name, Company's Name, Phone Number, Title, Email address, Complete Mailing Address, Web address etc. Please let me know your interest to send you the number of attendees and cost. Thank you and I Looking forward to hear from you soon. Kind regards, Michael Foster , Business Coordinator If you do not wish to receive future emails from us, please reply as 'leave out' From owner-freebsd-stable@freebsd.org Fri Aug 31 16:12:39 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 D3416FCF64C for ; Fri, 31 Aug 2018 16:12:39 +0000 (UTC) (envelope-from cyschow@shaw.ca) 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 9644F79F23 for ; Fri, 31 Aug 2018 16:12:39 +0000 (UTC) (envelope-from cyschow@shaw.ca) Received: by mailman.ysv.freebsd.org (Postfix) id 56449FCF64B; Fri, 31 Aug 2018 16:12:39 +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 4519EFCF64A for ; Fri, 31 Aug 2018 16:12:39 +0000 (UTC) (envelope-from cyschow@shaw.ca) Received: from smtp-out-so.shaw.ca (smtp-out-so.shaw.ca [64.59.136.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0239979F21 for ; Fri, 31 Aug 2018 16:12:38 +0000 (UTC) (envelope-from cyschow@shaw.ca) Received: from mail.intranet.peyto.ca ([24.64.227.31]) by shaw.ca with ESMTP id vm2Bfh3UewyxUvm2CfNsgR; Fri, 31 Aug 2018 10:12:32 -0600 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=shaw.ca; s=s20180605; t=1535731952; bh=OvQg7XJRZNDLrp8E4DCuqvRwjvHw98OZWVjEUuzNOYU=; h=To:From:Subject:Date; b=hc/SOolAeU1t7708D5fljjlB9Z7/ZJAIQW3NaibVNRLqb3mtBlL33Y27mpXG3vNXM jzyorPmKXpNpWnarQHtBFvp4Q32ExxFeaJ2sCRIaIY4RH1bRGcObtRLTPJvgvomC+A Bj3fLoLGitUWcCCZ1XYULsb72jtGfumShnduJPCM1tD57SS8AR7XEiaCIf9ZiHwFiQ I6EXH2Q3+kiXmHYz9XMEu02RXlpnDQP/QBqNtnMM4XRlHaFaPMPG5aAw9mBYOtCx1+ YJ3aHMuXUhDF918AGYinDGamPDVfP51zKWDOXcrzF8xYUGe/IFq/kOMTNV3hg8FbU8 05Vb+HsH3jy3g== X-Authority-Analysis: v=2.3 cv=NPJhBHyg c=1 sm=1 tr=0 a=EzZWVta4pqxsgR2mpKnCwA==:117 a=EzZWVta4pqxsgR2mpKnCwA==:17 a=IkcTkHD0fZMA:10 a=O76VCmqbo-wA:10 a=x7bEGLp0ZPQA:10 a=dapMudl6Dx4A:10 a=ELOxpg8rFSLf5YKSA_wA:9 a=QEXdDO2ut3YA:10 a=Bl1bqend9reKY-4Nh7dc:22 a=HH7FIXwXL_sUf1zzYxQd:22 Received: from [192.168.4.6] (unknown [192.168.4.6]) by mail.intranet.peyto.ca (Postfix) with ESMTPSA id BFEB812FCB6 for ; Fri, 31 Aug 2018 10:08:38 -0600 (MDT) To: stable@freebsd.org From: Samuel Chow Subject: Cannot setup dumpdev on glabel disk Message-ID: <19f80f48-5fea-e105-18b2-1a64e06acc79@shaw.ca> Date: Fri, 31 Aug 2018 10:08:20 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Peyto-MailScanner-Information: Please contact the ISP for more information X-Peyto-MailScanner-ID: BFEB812FCB6.A5C6F X-Peyto-MailScanner: Found to be clean X-Peyto-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-1, required 6, autolearn=disabled, ALL_TRUSTED -1.00) X-Peyto-MailScanner-From: cyschow@shaw.ca X-Spam-Status: No X-CMAE-Envelope: MS4wfL23XXB972TwdPlxZTEW7icPpUfYIDG5pf6DXlkXIjgM+neI7Jb7KW52capzNPu0VkUWf94dEgPvcLed3fiot5BHJvi/hime4JKsxEpTQdkCYYlcoQpA +lslEbpPri+jTwR51sJoeWw95pHmScFAkUB59AW0nj776AWyxcBjttiz 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, 31 Aug 2018 16:12:40 -0000 I am running 11-STABLE, and I am experiencing kernel panics when I am destroying a VIMAGE-based jail. Naturally, I flipped to the chapter about 'Kernel Debugging' to learn about 'Obtaining a Kernel Crash Dump'. However, I am finding that my permanently glabel'ed disk partition cannot be used as dumpdev. Is that true, and why not? I mean, swap can use it just fine. I am unable to find this restriction in the documentation. # grep swap /etc/fstab /dev/label/boot01b      none         swap       sw      0 0 # swapinfo Device          1K-blocks     Used    Avail Capacity /dev/label/boot01b  41943040        0 41943040     0% # glabel status | grep boot   label/boot01     N/A  ada4s1   label/boot02     N/A  ada5s1 # dumpon /dev/label/boot01b dumpon: ioctl(DIOCSKERNELDUMP): Operation not supported by device From owner-freebsd-stable@freebsd.org Fri Aug 31 19:04: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 59DCEFD5363 for ; Fri, 31 Aug 2018 19:04:54 +0000 (UTC) (envelope-from markjdb@gmail.com) 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 D48EE80DFC for ; Fri, 31 Aug 2018 19:04:53 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 9624CFD5362; Fri, 31 Aug 2018 19:04:53 +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 74407FD5361 for ; Fri, 31 Aug 2018 19:04:53 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-pl1-x62e.google.com (mail-pl1-x62e.google.com [IPv6:2607:f8b0:4864:20::62e]) (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 D2D2B80DFB for ; Fri, 31 Aug 2018 19:04:52 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-pl1-x62e.google.com with SMTP id j8-v6so5850702pll.12 for ; Fri, 31 Aug 2018 12:04:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=GxdtAv4wqZhONVvz+ofR2iFSWm55DLuVEo5tijHRmjw=; b=IpAl1ehc2tRr8aVd+RH795GcOaG/CYh9Np45aQlbKLld2M0k4G2OhjrNGwvUheEcYy RzN+jSQ2dLZ4WzSbpLSQm8tzgiJAv4Hz53fWl+8mQ5MbaxRSUEQYn/+ieSiY73F0aX6x pgvgLuRndF/PlaWDqd79ykdEnrlx8ECiLvh6/Zbta3ENqXzt/MwkbyPfM3c5g3sS7v35 flhjrbIKVRcib3YQyxcO5cWQ9WbQv0ERMoHnXBbsmRZri83iLMRarPeB494zkvfIKrfN cjfJioUQQx80/KXg7lm7joohRAFUXn5MomUI4dr4FpSH9yyEamZHI0BXur4bUV0lYTu2 cL5w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=GxdtAv4wqZhONVvz+ofR2iFSWm55DLuVEo5tijHRmjw=; b=AoFgx1Yl2qV7SKSaNVAl7JmSxNmUz68o6ASKRL2EZ0gQWR2vSnwzmgE+NjV2lOibeV LZjU+hL2Elu/W3SQJvN5oUCVXnpcj1govfuWziMU8Pal8Z4jpiUD0bV3jmleaP5LdmRs Iof1mIBkxIpIhfqvzm3+Oy+Eh2PQHAhsxM2CoH7HNOjHcsQZQLlUM7UWisRXTgctO1F0 Txp9hiK03XDa09c+7mVfPOrPB7U1EiLAwUBLoOCWuxEm7VVYMEtVISEkjHYrh0UQi+wG qt6wfRsVmh4kDpHniKwwUcVDrnPniMPsftN2NWd38TJFmHrGVxtMIKyNWCywgjE1Pgb0 IfOg== X-Gm-Message-State: APzg51C5/kKSoALZDwYh5136dAGnkTxcGZnYYYbaU9+ACmeDCp1mpef5 wCiCZ6lEfTaMSJ9xq4+0I3w= X-Google-Smtp-Source: ANB0VdbyBJELvBpWGARuIZGh1fWRJlw//ycM1HGsB3QmqUoTf9/BXpn5tyxUAtMyDo/uLyn/4aM3hA== X-Received: by 2002:a17:902:d917:: with SMTP id c23-v6mr16755352plz.65.1535742291735; Fri, 31 Aug 2018 12:04:51 -0700 (PDT) Received: from raichu (toroon0560w-lp130-09-70-52-224-239.dsl.bell.ca. [70.52.224.239]) by smtp.gmail.com with ESMTPSA id l79-v6sm17428235pfi.172.2018.08.31.12.04.50 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 31 Aug 2018 12:04:50 -0700 (PDT) Sender: Mark Johnston Date: Fri, 31 Aug 2018 15:04:48 -0400 From: Mark Johnston To: Samuel Chow Cc: stable@freebsd.org Subject: Re: Cannot setup dumpdev on glabel disk Message-ID: <20180831190448.GB54904@raichu> References: <19f80f48-5fea-e105-18b2-1a64e06acc79@shaw.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <19f80f48-5fea-e105-18b2-1a64e06acc79@shaw.ca> 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: Fri, 31 Aug 2018 19:04:54 -0000 On Fri, Aug 31, 2018 at 10:08:20AM -0600, Samuel Chow wrote: > I am running 11-STABLE, and I am experiencing kernel panics when I am > destroying a VIMAGE-based jail. Naturally, I flipped to the chapter > about 'Kernel Debugging' to learn about 'Obtaining a Kernel Crash Dump'. > > However, I am finding that my permanently glabel'ed disk partition > cannot be used as dumpdev. Is that true, and why not? I mean, swap can > use it just fine. I am unable to find this restriction in the documentation. I don't think that there is a real reason for this restriction; the glabel GEOM class simply doesn't implement the required support. Do you mind submitting a PR for this at https://bugs.freebsd.org/bugzilla/ ? I will try and get that fixed soon if no one else beats me to it. > # grep swap /etc/fstab > /dev/label/boot01b none swap sw 0 0 > # swapinfo > Device 1K-blocks Used Avail Capacity > /dev/label/boot01b 41943040 0 41943040 0% > # glabel status | grep boot > label/boot01 N/A ada4s1 > label/boot02 N/A ada5s1 > # dumpon /dev/label/boot01b > dumpon: ioctl(DIOCSKERNELDUMP): Operation not supported by device > > _______________________________________________ > 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 Fri Aug 31 19:09:28 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 7C6BBFD5580 for ; Fri, 31 Aug 2018 19:09:28 +0000 (UTC) (envelope-from eugen@grosbein.net) 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 1AD5680F84 for ; Fri, 31 Aug 2018 19:09:28 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: by mailman.ysv.freebsd.org (Postfix) id D169DFD557E; Fri, 31 Aug 2018 19:09:27 +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 BFD23FD557C for ; Fri, 31 Aug 2018 19:09:27 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [IPv6:2a01:4f8:d12:604::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 48B3F80F83 for ; Fri, 31 Aug 2018 19:09:27 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (eg.sd.rdtc.ru [IPv6:2a03:3100:c:13:0:0:0:5]) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id w7VJ9Kuu038061 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 31 Aug 2018 21:09:21 +0200 (CEST) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: cyschow@shaw.ca Received: from [10.58.0.4] ([10.58.0.4]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTPS id w7VJ9Hmt034458 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sat, 1 Sep 2018 02:09:17 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: Cannot setup dumpdev on glabel disk To: Samuel Chow , stable@freebsd.org References: <19f80f48-5fea-e105-18b2-1a64e06acc79@shaw.ca> From: Eugene Grosbein Message-ID: <6f6685d0-08c6-dbe2-62b5-3628f91917d9@grosbein.net> Date: Sat, 1 Sep 2018 02:09:12 +0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <19f80f48-5fea-e105-18b2-1a64e06acc79@shaw.ca> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=0.3 required=5.0 tests=BAYES_00,LOCAL_FROM,SPF_PASS autolearn=no autolearn_force=no version=3.4.1 X-Spam-Report: * -0.0 SPF_PASS SPF: sender matches SPF record * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 2.6 LOCAL_FROM From my domains X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net 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, 31 Aug 2018 19:09:28 -0000 31.08.2018 23:08, Samuel Chow wrote: > I am running 11-STABLE, and I am experiencing kernel panics when I am destroying a VIMAGE-based jail. Naturally, I flipped to the chapter about 'Kernel Debugging' to learn about 'Obtaining a Kernel Crash Dump'. > > However, I am finding that my permanently glabel'ed disk partition cannot be used as dumpdev. Is that true, and why not? I mean, swap can use it just fine. I am unable to find this restriction in the documentation. > > > # grep swap /etc/fstab > /dev/label/boot01b none swap sw 0 0 > # swapinfo > Device 1K-blocks Used Avail Capacity > /dev/label/boot01b 41943040 0 41943040 0% > # glabel status | grep boot > label/boot01 N/A ada4s1 > label/boot02 N/A ada5s1 > # dumpon /dev/label/boot01b > dumpon: ioctl(DIOCSKERNELDUMP): Operation not supported by device That's not about label but underlying device that seems to be GEOM_PART_MBR and it allows kernel dumps only if slice (MBR partition) type is 0xa5 for "freebsd" or 0x82 ("linux swap"). Please show output of the command "gpart show ada4". From owner-freebsd-stable@freebsd.org Fri Aug 31 19:21:10 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 CC7F0FD5BF2 for ; Fri, 31 Aug 2018 19:21:09 +0000 (UTC) (envelope-from markjdb@gmail.com) 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 647C88165B for ; Fri, 31 Aug 2018 19:21:09 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 2A985FD5BF0; Fri, 31 Aug 2018 19:21:09 +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 08D2BFD5BEE for ; Fri, 31 Aug 2018 19:21:09 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-pg1-x542.google.com (mail-pg1-x542.google.com [IPv6:2607:f8b0:4864:20::542]) (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 7C8A881656 for ; Fri, 31 Aug 2018 19:21:08 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-pg1-x542.google.com with SMTP id d19-v6so5872326pgv.1 for ; Fri, 31 Aug 2018 12:21:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=9cRMAkHMWg96Pn3TnpKuqgm/MU3j+6djZrgByauhdEo=; b=Z06tCuX/e7u7I/rvuMcdnDOIHFNOZHGQuUOsYRX3Y0HfPNUeqtAxzh0xk7geyjD348 4AvqHOjHkNO85m4JIP5aa74PIT7LncxJpDy9hlpal1faVYp0/x2U6Sy9KQRWqlQX7gsO nWC2vBw4AUac7zdStA5ABEhMld/G//QzAWWzaQCgCS+LIsdQGBGvqfefmRwdjcwAtc9j Jee5jwwQmHwV4aSD8T7gGQrllmA5o2VqlJSm/OIcA2q4fSdCBXvwO8xZLEu4sBM787yY YKPP5dQ05XTFgFgxLNAEsmhcJU6Ggc+ViXdmyWY4EuHeyPtbGJf3k8QErPbuB8L/u77M 1jGQ== 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:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=9cRMAkHMWg96Pn3TnpKuqgm/MU3j+6djZrgByauhdEo=; b=pYuqP8uo+R7mM0ZNOmGEg9LZxzbh20MkdVgTeRF7yVQP6RDOgs2VlSPP5LWiM+HpeF 4edWfiM3LOBVdHSPAbN+xVWnSP0od6/zTDFiYdR7gXOJuLSKd5PexevCdqgZpnZqOQBq jo4KPUg5KzGs/rtZqaDfTv4e2eepNyOeivjR2UmhlIN9tWBm4YaPCVc2mjd4cmbbo2o4 Awl+QPAyi8JKvHC4nfjEN8jzf3JNBxL93VuUDFlEF86/hE7CZirP7FHF8EIRPqzVyS5i kUnRz7afS4IK9fJK830qCo96tx9zqAazLJPfOJE5A/fsRX/4kvTRLpw145WatKbsMK7e 6OSg== X-Gm-Message-State: APzg51CCIVyvB+hGuNlloCPthuFXxLZdGR3Y9/2Qdmnch0YpOdIO72nD kz6GDu0a4tTXtds3JFYTJswgoMzA X-Google-Smtp-Source: ANB0Vdax8nAo63mnbxhejuv2r8SctH5tekW25Ze80QwavSVnUBZaASlrejZ08WCLrdXkVgk0vtRcgA== X-Received: by 2002:a63:c20:: with SMTP id b32-v6mr2612406pgl.400.1535743267523; Fri, 31 Aug 2018 12:21:07 -0700 (PDT) Received: from raichu (toroon0560w-lp130-09-70-52-224-239.dsl.bell.ca. [70.52.224.239]) by smtp.gmail.com with ESMTPSA id g5-v6sm16874780pfc.77.2018.08.31.12.21.06 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 31 Aug 2018 12:21:06 -0700 (PDT) Date: Fri, 31 Aug 2018 15:21:03 -0400 From: Mark Johnston To: Eugene Grosbein Cc: Samuel Chow , stable@freebsd.org Subject: Re: Cannot setup dumpdev on glabel disk Message-ID: <20180831192103.GC54904@raichu> References: <19f80f48-5fea-e105-18b2-1a64e06acc79@shaw.ca> <6f6685d0-08c6-dbe2-62b5-3628f91917d9@grosbein.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6f6685d0-08c6-dbe2-62b5-3628f91917d9@grosbein.net> 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: Fri, 31 Aug 2018 19:21:10 -0000 On Sat, Sep 01, 2018 at 02:09:12AM +0700, Eugene Grosbein wrote: > 31.08.2018 23:08, Samuel Chow wrote: > > > I am running 11-STABLE, and I am experiencing kernel panics when I am destroying a VIMAGE-based jail. Naturally, I flipped to the chapter about 'Kernel Debugging' to learn about 'Obtaining a Kernel Crash Dump'. > > > > However, I am finding that my permanently glabel'ed disk partition cannot be used as dumpdev. Is that true, and why not? I mean, swap can use it just fine. I am unable to find this restriction in the documentation. > > > > > > # grep swap /etc/fstab > > /dev/label/boot01b none swap sw 0 0 > > # swapinfo > > Device 1K-blocks Used Avail Capacity > > /dev/label/boot01b 41943040 0 41943040 0% > > # glabel status | grep boot > > label/boot01 N/A ada4s1 > > label/boot02 N/A ada5s1 > > # dumpon /dev/label/boot01b > > dumpon: ioctl(DIOCSKERNELDUMP): Operation not supported by device > > That's not about label but underlying device that seems to be GEOM_PART_MBR > and it allows kernel dumps only if slice (MBR partition) type is 0xa5 for "freebsd" > or 0x82 ("linux swap"). Please show output of the command "gpart show ada4". Ah, right, please ignore my other reply. When I actually test it myself, dumpon /dev/label/foo seems to work; I assumed the lack of handling for GEOM::kerneldump in the glabel code was a problem. Sorry for the noise. From owner-freebsd-stable@freebsd.org Fri Aug 31 19:27: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 A7ACDFD5F4E for ; Fri, 31 Aug 2018 19:27:42 +0000 (UTC) (envelope-from cyschow@shaw.ca) 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 40DDA81BA8 for ; Fri, 31 Aug 2018 19:27:42 +0000 (UTC) (envelope-from cyschow@shaw.ca) Received: by mailman.ysv.freebsd.org (Postfix) id 03B51FD5F4D; Fri, 31 Aug 2018 19:27:42 +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 BD68EFD5F4C for ; Fri, 31 Aug 2018 19:27:41 +0000 (UTC) (envelope-from cyschow@shaw.ca) Received: from smtp-out-so.shaw.ca (smtp-out-so.shaw.ca [64.59.136.138]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4E35381BA7 for ; Fri, 31 Aug 2018 19:27:41 +0000 (UTC) (envelope-from cyschow@shaw.ca) Received: from mail.intranet.peyto.ca ([24.64.227.31]) by shaw.ca with ESMTP id vp4tfNSOa5Hxqvp4uf32fj; Fri, 31 Aug 2018 13:27:33 -0600 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=shaw.ca; s=s20180605; t=1535743653; bh=3sB/Mh/k1VNkkq04oZQ+YPcB3illTm1yUBwfrcjeg0g=; h=Subject:To:References:From:Date:In-Reply-To; b=QxljqnE7U4qMnq/H3N2tQwRa1OiwFoSXNWiDLfaDRkt7B16a0T0W+QW205xDvqJIQ M4HRKNbJobn83pzYhP2cWEcNFy730JHs8VfcfVEhoxGM0EVrvwhWhfjvQcRCPFdEh7 xzp81vlPVFa8ij4O948A//gdNHdoZz/kz1M44T6GkVeQx/28UQjhjhobM5wa81PW60 AbeJ9W2dMfZH+dNsGr10puLL9MznnxKpSrgR7FkZeY2ZB+/OYJdYGNrDSFSpinX55u K8mjqp4p1f/4FKjKMC1lHF0XmI44NXbAsjy/duoy8yjosX1i/QX1OZXIwemXMfGmTd jguchmlaG2WrQ== X-Authority-Analysis: v=2.3 cv=BMcHU2YG c=1 sm=1 tr=0 a=EzZWVta4pqxsgR2mpKnCwA==:117 a=EzZWVta4pqxsgR2mpKnCwA==:17 a=IkcTkHD0fZMA:10 a=O76VCmqbo-wA:10 a=x7bEGLp0ZPQA:10 a=dapMudl6Dx4A:10 a=7EE6V-E_1K-UHgQHroEA:9 a=QEXdDO2ut3YA:10 a=Bl1bqend9reKY-4Nh7dc:22 a=HH7FIXwXL_sUf1zzYxQd:22 Received: from [192.168.4.6] (unknown [192.168.4.6]) by mail.intranet.peyto.ca (Postfix) with ESMTPSA id AE97B131802; Fri, 31 Aug 2018 13:25:04 -0600 (MDT) Subject: Re: Cannot setup dumpdev on glabel disk To: Eugene Grosbein , stable@freebsd.org References: <19f80f48-5fea-e105-18b2-1a64e06acc79@shaw.ca> <6f6685d0-08c6-dbe2-62b5-3628f91917d9@grosbein.net> From: Samuel Chow Message-ID: Date: Fri, 31 Aug 2018 13:25:02 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <6f6685d0-08c6-dbe2-62b5-3628f91917d9@grosbein.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Peyto-MailScanner-Information: Please contact the ISP for more information X-Peyto-MailScanner-ID: AE97B131802.AEFBA X-Peyto-MailScanner: Found to be clean X-Peyto-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-1, required 6, autolearn=disabled, ALL_TRUSTED -1.00) X-Peyto-MailScanner-From: cyschow@shaw.ca X-Spam-Status: No X-CMAE-Envelope: MS4wfAgYHUNV/ygRJyisHUIbiHkXeG6oaW2IWc1mxUT2E/rZFJwWheIuWtqlMq3c8rzeCYGMLInWghZPZJAHNM+6RlD2tQsma90aQg5uglgbz/mxnxOEzg1s nVPGkFnL41/GU672KpnJNN5ICuQ8m2Y+UOtflKGAuF4M28pRlY7dQ2RkFjUY//t/7/K/wk+jL4SAFtMbv+tdkNqSYXmpmt3f8wo= 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, 31 Aug 2018 19:27:42 -0000 On 8/31/2018 1:09 PM, Eugene Grosbein wrote: > 31.08.2018 23:08, Samuel Chow wrote: > >> I am running 11-STABLE, and I am experiencing kernel panics when I am destroying a VIMAGE-based jail. Naturally, I flipped to the chapter about 'Kernel Debugging' to learn about 'Obtaining a Kernel Crash Dump'. >> >> However, I am finding that my permanently glabel'ed disk partition cannot be used as dumpdev. Is that true, and why not? I mean, swap can use it just fine. I am unable to find this restriction in the documentation. >> >> >> # grep swap /etc/fstab >> /dev/label/boot01b none swap sw 0 0 >> # swapinfo >> Device 1K-blocks Used Avail Capacity >> /dev/label/boot01b 41943040 0 41943040 0% >> # glabel status | grep boot >> label/boot01 N/A ada4s1 >> label/boot02 N/A ada5s1 >> # dumpon /dev/label/boot01b >> dumpon: ioctl(DIOCSKERNELDUMP): Operation not supported by device > That's not about label but underlying device that seems to be GEOM_PART_MBR > and it allows kernel dumps only if slice (MBR partition) type is 0xa5 for "freebsd" > or 0x82 ("linux swap"). Please show output of the command "gpart show ada4". > > I do have "freebsd" (0xa5) type configured on the MBR partition. # gpart show ada4 =>       63  937703025  ada4  MBR  (447G)          63  937703025     1  freebsd  [active]  (447G) # gpart show -r ada4 =>       63  937703025  ada4  MBR  (447G)          63  937703025     1  165  [active]  (447G) From owner-freebsd-stable@freebsd.org Fri Aug 31 19:47:34 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 48771FDA6CB for ; Fri, 31 Aug 2018 19:47:34 +0000 (UTC) (envelope-from cyschow@shaw.ca) 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 D45C282682 for ; Fri, 31 Aug 2018 19:47:33 +0000 (UTC) (envelope-from cyschow@shaw.ca) Received: by mailman.ysv.freebsd.org (Postfix) id 990A9FDA6C2; Fri, 31 Aug 2018 19:47:33 +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 76FEFFDA6C0 for ; Fri, 31 Aug 2018 19:47:33 +0000 (UTC) (envelope-from cyschow@shaw.ca) Received: from smtp-out-so.shaw.ca (smtp-out-so.shaw.ca [64.59.136.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 00CC68267F for ; Fri, 31 Aug 2018 19:47:32 +0000 (UTC) (envelope-from cyschow@shaw.ca) Received: from mail.intranet.peyto.ca ([24.64.227.31]) by shaw.ca with ESMTP id vpOEfNZ2Z5HxqvpOGf36mP; Fri, 31 Aug 2018 13:47:32 -0600 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=shaw.ca; s=s20180605; t=1535744852; bh=UkoHnGBgW469Gbru0+thQ0YMQkKzM6zJeYOoaeo662c=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=Uf1VxQYdVDMmCnFWFVJsJ4VKdRN8OZQ9/9E33Ib/6ao9zbw9Cna3OPvt+hWLq/pWN 3ovVMnfeTNEerKpOOI/mvvT3LD8xOqs/zlL7avTQKjfGOuwzBHai8tuB5j+B68mF5Z TbFfpfg6WdXRXGCDa+hiV3fe1Z4YYPQGA2qIrZU8EHZJgP5aFLMaufvgmvKNcxjETn HpqzNdGBBaBM8Ag58OIhvvXkR4kVLXb0LU9U9gDBn/YJTMi3j6kltibt8Oc+gdIV9i OogTkABv3fHO2bwaicnd3MsUEend/1kOScEy/zUBJc8CDRjPLjP35KprKfJ8CRfPX+ nEUcFAQ5zsaag== X-Authority-Analysis: v=2.3 cv=BMcHU2YG c=1 sm=1 tr=0 a=EzZWVta4pqxsgR2mpKnCwA==:117 a=EzZWVta4pqxsgR2mpKnCwA==:17 a=IkcTkHD0fZMA:10 a=O76VCmqbo-wA:10 a=x7bEGLp0ZPQA:10 a=dapMudl6Dx4A:10 a=-gKsbuZ1JRK-9DhMoacA:9 a=QEXdDO2ut3YA:10 a=Bl1bqend9reKY-4Nh7dc:22 a=HH7FIXwXL_sUf1zzYxQd:22 Received: from [192.168.4.6] (unknown [192.168.4.6]) by mail.intranet.peyto.ca (Postfix) with ESMTPSA id AB5681318DF; Fri, 31 Aug 2018 13:46:10 -0600 (MDT) Subject: Re: Cannot setup dumpdev on glabel disk To: Mark Johnston , Eugene Grosbein Cc: stable@freebsd.org References: <19f80f48-5fea-e105-18b2-1a64e06acc79@shaw.ca> <6f6685d0-08c6-dbe2-62b5-3628f91917d9@grosbein.net> <20180831192103.GC54904@raichu> From: Samuel Chow Message-ID: Date: Fri, 31 Aug 2018 13:46:08 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <20180831192103.GC54904@raichu> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Peyto-MailScanner-Information: Please contact the ISP for more information X-Peyto-MailScanner-ID: AB5681318DF.A322A X-Peyto-MailScanner: Found to be clean X-Peyto-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-1, required 6, autolearn=disabled, ALL_TRUSTED -1.00) X-Peyto-MailScanner-From: cyschow@shaw.ca X-Spam-Status: No X-CMAE-Envelope: MS4wfGLqOgS+IlXlvxDdc7h+NF2JKv0LEWWugGhI8EA6QlNb6YRlZudOgMJz8hcKoc6inezj+xalWczaELlxw8ljfLrxtks/SQ9+WOdoJCQnqxFeSzNIqCG5 OiH9XJry/rok3/jpFtqp2ERKTqNJ+zYEO8TKz6dLftrkbkvzYTfSqooNlqlaVbDlegEv0ijcHEwKWHQAX4eJGkJljHYJ1Dv6mz/z7iViIb8niTy/8fBstbFZ 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, 31 Aug 2018 19:47:34 -0000 On 8/31/2018 1:21 PM, Mark Johnston wrote: > On Sat, Sep 01, 2018 at 02:09:12AM +0700, Eugene Grosbein wrote: >> 31.08.2018 23:08, Samuel Chow wrote: >> >>> I am running 11-STABLE, and I am experiencing kernel panics when I am destroying a VIMAGE-based jail. Naturally, I flipped to the chapter about 'Kernel Debugging' to learn about 'Obtaining a Kernel Crash Dump'. >>> >>> However, I am finding that my permanently glabel'ed disk partition cannot be used as dumpdev. Is that true, and why not? I mean, swap can use it just fine. I am unable to find this restriction in the documentation. >>> >>> >>> # grep swap /etc/fstab >>> /dev/label/boot01b none swap sw 0 0 >>> # swapinfo >>> Device 1K-blocks Used Avail Capacity >>> /dev/label/boot01b 41943040 0 41943040 0% >>> # glabel status | grep boot >>> label/boot01 N/A ada4s1 >>> label/boot02 N/A ada5s1 >>> # dumpon /dev/label/boot01b >>> dumpon: ioctl(DIOCSKERNELDUMP): Operation not supported by device >> That's not about label but underlying device that seems to be GEOM_PART_MBR >> and it allows kernel dumps only if slice (MBR partition) type is 0xa5 for "freebsd" >> or 0x82 ("linux swap"). Please show output of the command "gpart show ada4". > Ah, right, please ignore my other reply. When I actually test it > myself, dumpon /dev/label/foo seems to work; I assumed the lack of > handling for GEOM::kerneldump in the glabel code was a problem. Sorry > for the noise. I wonder if you are testing the same thing as I am? It looks like you are dumping to a glabel'ed device directly, whereas I am dumping to the b partition of my glabel'ed disk. From owner-freebsd-stable@freebsd.org Fri Aug 31 20:00:10 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 0251AFDADC6 for ; Fri, 31 Aug 2018 20:00:10 +0000 (UTC) (envelope-from cyschow@shaw.ca) 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 8BD8F82D43 for ; Fri, 31 Aug 2018 20:00:09 +0000 (UTC) (envelope-from cyschow@shaw.ca) Received: by mailman.ysv.freebsd.org (Postfix) id 50BC9FDADC5; Fri, 31 Aug 2018 20:00:09 +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 2EA8FFDADC4 for ; Fri, 31 Aug 2018 20:00:09 +0000 (UTC) (envelope-from cyschow@shaw.ca) Received: from smtp-out-so.shaw.ca (smtp-out-so.shaw.ca [64.59.136.138]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B127E82D42 for ; Fri, 31 Aug 2018 20:00:08 +0000 (UTC) (envelope-from cyschow@shaw.ca) Received: from mail.intranet.peyto.ca ([24.64.227.31]) by shaw.ca with ESMTP id vpXvfNcGr5HxqvpXwf38qc; Fri, 31 Aug 2018 13:57:32 -0600 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=shaw.ca; s=s20180605; t=1535745452; bh=1deJ9cv/eMmpg6/vOIqIvHGBENuZKMpJiCTHIx9gRj4=; h=Subject:From:To:Cc:References:Date:In-Reply-To; b=vzdQT+/cIpE/CvBuuxRYtfo7BfO9L3IpixbVqEE8I2BJ8h5jXpZ3qFt64wQ9pQr50 7PWgIDqD0t/VcX6K6rPTb3hBLuemFh69wdnUecOel14F+2nSk9s9COEZEgEBXwlAla HJDh98RSO/LrxOoH1c5rOg2OioUjPwa0ldDmbwXjtVUMzuik3SHaHs0HvskPnUL3NK 5srLPaYGsctGiVZOgWV7u2pkUH5ZctCSJbnegX4FvDO+qvYtqiUqDq2cCSnYxUD+vK PiIe04T0AgEZtSgfbIG3ra+egeJkbK+MZNP3UojcLFuj3HzEqNaV6aLnGdVTn/cQe8 XwdaqWATtuxVw== X-Authority-Analysis: v=2.3 cv=BMcHU2YG c=1 sm=1 tr=0 a=EzZWVta4pqxsgR2mpKnCwA==:117 a=EzZWVta4pqxsgR2mpKnCwA==:17 a=IkcTkHD0fZMA:10 a=O76VCmqbo-wA:10 a=x7bEGLp0ZPQA:10 a=dapMudl6Dx4A:10 a=QflKmDSXG6m2nMxF8PUA:9 a=QEXdDO2ut3YA:10 a=Bl1bqend9reKY-4Nh7dc:22 a=HH7FIXwXL_sUf1zzYxQd:22 Received: from [192.168.4.6] (unknown [192.168.4.6]) by mail.intranet.peyto.ca (Postfix) with ESMTPSA id E4540131951; Fri, 31 Aug 2018 13:52:29 -0600 (MDT) Subject: Re: Cannot setup dumpdev on glabel disk From: Samuel Chow To: Mark Johnston , Eugene Grosbein Cc: stable@freebsd.org References: <19f80f48-5fea-e105-18b2-1a64e06acc79@shaw.ca> <6f6685d0-08c6-dbe2-62b5-3628f91917d9@grosbein.net> <20180831192103.GC54904@raichu> Message-ID: Date: Fri, 31 Aug 2018 13:52:27 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Peyto-MailScanner-Information: Please contact the ISP for more information X-Peyto-MailScanner-ID: E4540131951.AF53E X-Peyto-MailScanner: Found to be clean X-Peyto-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-1, required 6, autolearn=disabled, ALL_TRUSTED -1.00) X-Peyto-MailScanner-From: cyschow@shaw.ca X-Spam-Status: No X-CMAE-Envelope: MS4wfKupv5rOhhLjIpRW0O8qVjwE8FKoG3RUouPlyyDLQ5IRSuU80YV/G6ab2zPb4vP1+riRLfvS7TxAhw1x+b4XiZTvkvjUkoiuESqLKffkiu6CACA2nPFD 9qX/mku0KrU8zXk8192mk8AlvUTpKHMsgsNC66yaBD6Pt0UZzesIseuHFk6VgPD6+9wOfFcHjmC3azIvkJnVc6yqboG0dZKd6zdQjASpaOaKWzXLVQHI/N21 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, 31 Aug 2018 20:00:10 -0000 On 8/31/2018 1:46 PM, Samuel Chow wrote: > On 8/31/2018 1:21 PM, Mark Johnston wrote: >> On Sat, Sep 01, 2018 at 02:09:12AM +0700, Eugene Grosbein wrote: >>> 31.08.2018 23:08, Samuel Chow wrote: >>> >>>> I am running 11-STABLE, and I am experiencing kernel panics when I >>>> am destroying a VIMAGE-based jail. Naturally, I flipped to the >>>> chapter about 'Kernel Debugging' to learn about 'Obtaining a Kernel >>>> Crash Dump'. >>>> >>>> However, I am finding that my permanently glabel'ed disk partition >>>> cannot be used as dumpdev. Is that true, and why not? I mean, swap >>>> can use it just fine. I am unable to find this restriction in the >>>> documentation. >>>> >>>> >>>> # grep swap /etc/fstab >>>> /dev/label/boot01b      none         swap       sw      0 0 >>>> # swapinfo >>>> Device          1K-blocks     Used    Avail Capacity >>>> /dev/label/boot01b  41943040        0 41943040     0% >>>> # glabel status | grep boot >>>>    label/boot01     N/A  ada4s1 >>>>    label/boot02     N/A  ada5s1 >>>> # dumpon /dev/label/boot01b >>>> dumpon: ioctl(DIOCSKERNELDUMP): Operation not supported by device >>> That's not about label but underlying device that seems to be >>> GEOM_PART_MBR >>> and it allows kernel dumps only if slice (MBR partition) type is >>> 0xa5 for "freebsd" >>> or 0x82 ("linux swap"). Please show output of the command "gpart >>> show ada4". >> Ah, right, please ignore my other reply.  When I actually test it >> myself, dumpon /dev/label/foo seems to work; I assumed the lack of >> handling for GEOM::kerneldump in the glabel code was a problem. Sorry >> for the noise. > > I wonder if you are testing the same thing as I am? It looks like you > are dumping to a glabel'ed device directly, whereas I am dumping to > the b partition of my glabel'ed disk. > > Wait.  Maybe my problem is because I did not setup the b partition correctly with fstype swap. I will check it out later. # bsdlabel /dev/label/boot01 # /dev/label/boot01: 8 partitions: #          size     offset    fstype   [fsize bsize bps/cpg]   a:   10485760          1    4.2BSD        0     0     0   b:   83886080   10485761    4.2BSD        0     0     0   c:  937703024          0    unused        0     0     # "raw" part, don't edit   d:   41943040   94371841    4.2BSD        0     0     0   e:   20971520  136314881    4.2BSD        0     0     0   f:   83886080  157286401    4.2BSD        0     0     0   g:  696530536  241172481       ZFS From owner-freebsd-stable@freebsd.org Fri Aug 31 20:22:41 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 47DBDFDB972 for ; Fri, 31 Aug 2018 20:22:41 +0000 (UTC) (envelope-from cyschow@shaw.ca) 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 BE9BB83D8A for ; Fri, 31 Aug 2018 20:22:40 +0000 (UTC) (envelope-from cyschow@shaw.ca) Received: by mailman.ysv.freebsd.org (Postfix) id 87962FDB971; Fri, 31 Aug 2018 20:22:40 +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 65B73FDB96F for ; Fri, 31 Aug 2018 20:22:40 +0000 (UTC) (envelope-from cyschow@shaw.ca) Received: from smtp-out-no.shaw.ca (smtp-out-no.shaw.ca [64.59.134.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E752483D88 for ; Fri, 31 Aug 2018 20:22:39 +0000 (UTC) (envelope-from cyschow@shaw.ca) Received: from mail.intranet.peyto.ca ([24.64.227.31]) by shaw.ca with ESMTP id vpw6fyKyfWppDvpw7f2GA9; Fri, 31 Aug 2018 14:22:32 -0600 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=shaw.ca; s=s20180605; t=1535746952; bh=RXiLfgfBv8burP40JzCoodbmFvci3sa8V8u1XpwSZtQ=; h=Subject:From:To:Cc:References:Date:In-Reply-To; b=UTCJ46s2tgEiyjqcKNI+ZQZPNLTzLbPB5uvZReAlaRinagczzlH6+rE2rmyDnFhmX ngeBMh49nZJjXBNJO13B6V3SQF2u3r3EtnYsS2Pbi5Dp3eTqHwYoEXghSXVJ6b3IpX B+VtIJR4yx/8Wnh+/vJop17TzeVrUrfLddN42n2c4aBvGSAkJuX2cNbTETAbgHnz0U wdGf4os7TDgoz+LHUvwASa7YwQ6NZA3nfDP7+rAPfymHnqaZqTEtEm9lM1rjPv/vXr RMofcXcumSwgOovub6EK+WzmgSsVFx755+t4wnCcbvkXRYDenkKwuJNJ/bswOXXEy7 hES04RIIXcmKw== X-Authority-Analysis: v=2.3 cv=YIcrNiOx c=1 sm=1 tr=0 a=EzZWVta4pqxsgR2mpKnCwA==:117 a=EzZWVta4pqxsgR2mpKnCwA==:17 a=IkcTkHD0fZMA:10 a=O76VCmqbo-wA:10 a=x7bEGLp0ZPQA:10 a=dapMudl6Dx4A:10 a=jS6kb-GYMDKg-IXleX4A:9 a=QEXdDO2ut3YA:10 a=Bl1bqend9reKY-4Nh7dc:22 a=HH7FIXwXL_sUf1zzYxQd:22 Received: from [192.168.4.6] (unknown [192.168.4.6]) by mail.intranet.peyto.ca (Postfix) with ESMTPSA id 5513C131B0C; Fri, 31 Aug 2018 14:22:19 -0600 (MDT) Subject: Re: Cannot setup dumpdev on glabel disk From: Samuel Chow To: Mark Johnston , Eugene Grosbein Cc: stable@freebsd.org References: <19f80f48-5fea-e105-18b2-1a64e06acc79@shaw.ca> <6f6685d0-08c6-dbe2-62b5-3628f91917d9@grosbein.net> <20180831192103.GC54904@raichu> Message-ID: <1a12cc03-8ffe-319e-96cf-8056cf80dec5@shaw.ca> Date: Fri, 31 Aug 2018 14:22:16 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Peyto-MailScanner-Information: Please contact the ISP for more information X-Peyto-MailScanner-ID: 5513C131B0C.A23BE X-Peyto-MailScanner: Found to be clean X-Peyto-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-1, required 6, autolearn=disabled, ALL_TRUSTED -1.00) X-Peyto-MailScanner-From: cyschow@shaw.ca X-Spam-Status: No X-CMAE-Envelope: MS4wfGuvPXSWAwTIALRLkVoNT9/wq3IUO8+6C2TZ+cAyC7lHst+HTuCaXdnU/EvLPFVZxGzEW7uVHhWi2I8aobX9A40u8HYpPbnEpRQVwzoaZCSjWSAecjeT euu/f5XC9v2Qz4WqetjdRHwASji6XVbgxaF5May6sY0eNlh9JM+RIN/wHOLtggLmBjbfxR/s6vtjj6N0AxYq6GzKUjTvup/dTW7GE8Oqdq+RT41mrbp+PjMi KjzVbxbVCCcAqabPtgM2bA== 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, 31 Aug 2018 20:22:41 -0000 On 8/31/2018 1:52 PM, Samuel Chow wrote: > On 8/31/2018 1:46 PM, Samuel Chow wrote: >> On 8/31/2018 1:21 PM, Mark Johnston wrote: >>> On Sat, Sep 01, 2018 at 02:09:12AM +0700, Eugene Grosbein wrote: >>>> 31.08.2018 23:08, Samuel Chow wrote: >>>> >>>>> I am running 11-STABLE, and I am experiencing kernel panics when I >>>>> am destroying a VIMAGE-based jail. Naturally, I flipped to the >>>>> chapter about 'Kernel Debugging' to learn about 'Obtaining a >>>>> Kernel Crash Dump'. >>>>> >>>>> However, I am finding that my permanently glabel'ed disk partition >>>>> cannot be used as dumpdev. Is that true, and why not? I mean, swap >>>>> can use it just fine. I am unable to find this restriction in the >>>>> documentation. >>>>> >>>>> >>>>> # grep swap /etc/fstab >>>>> /dev/label/boot01b      none         swap       sw      0 0 >>>>> # swapinfo >>>>> Device          1K-blocks     Used    Avail Capacity >>>>> /dev/label/boot01b  41943040        0 41943040     0% >>>>> # glabel status | grep boot >>>>>    label/boot01     N/A  ada4s1 >>>>>    label/boot02     N/A  ada5s1 >>>>> # dumpon /dev/label/boot01b >>>>> dumpon: ioctl(DIOCSKERNELDUMP): Operation not supported by device >>>> That's not about label but underlying device that seems to be >>>> GEOM_PART_MBR >>>> and it allows kernel dumps only if slice (MBR partition) type is >>>> 0xa5 for "freebsd" >>>> or 0x82 ("linux swap"). Please show output of the command "gpart >>>> show ada4". >>> Ah, right, please ignore my other reply.  When I actually test it >>> myself, dumpon /dev/label/foo seems to work; I assumed the lack of >>> handling for GEOM::kerneldump in the glabel code was a problem. Sorry >>> for the noise. >> >> I wonder if you are testing the same thing as I am? It looks like you >> are dumping to a glabel'ed device directly, whereas I am dumping to >> the b partition of my glabel'ed disk. >> >> > > Wait.  Maybe my problem is because I did not setup the b partition > correctly with fstype swap. I will check it out later. > > # bsdlabel /dev/label/boot01 > # /dev/label/boot01: > 8 partitions: > #          size     offset    fstype   [fsize bsize bps/cpg] >   a:   10485760          1    4.2BSD        0     0     0 >   b:   83886080   10485761    4.2BSD        0     0     0 >   c:  937703024          0    unused        0     0     # "raw" part, > don't edit >   d:   41943040   94371841    4.2BSD        0     0     0 >   e:   20971520  136314881    4.2BSD        0     0     0 >   f:   83886080  157286401    4.2BSD        0     0     0 >   g:  696530536  241172481       ZFS > That was indeed the problem. It is working now. Sorry for the noise. From owner-freebsd-stable@freebsd.org Fri Aug 31 22:32: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 AAEEAFCCADF for ; Fri, 31 Aug 2018 22:32:18 +0000 (UTC) (envelope-from longwitz@incore.de) Received: from dss.incore.de (dss.incore.de [195.145.1.138]) (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 3558188BFF for ; Fri, 31 Aug 2018 22:32:17 +0000 (UTC) (envelope-from longwitz@incore.de) Received: from inetmail.dmz (inetmail.dmz [10.3.0.3]) by dss.incore.de (Postfix) with ESMTP id D6E7351F for ; Sat, 1 Sep 2018 00:32:09 +0200 (CEST) X-Virus-Scanned: amavisd-new at incore.de Received: from dss.incore.de ([10.3.0.3]) by inetmail.dmz (inetmail.dmz [10.3.0.3]) (amavisd-new, port 10024) with LMTP id MPGWolQxnlM3 for ; Sat, 1 Sep 2018 00:32:08 +0200 (CEST) Received: from mail.local.incore (fwintern.dmz [10.0.0.253]) by dss.incore.de (Postfix) with ESMTP id 352F6269 for ; Sat, 1 Sep 2018 00:32:08 +0200 (CEST) Received: from bsdmhs.longwitz (unknown [192.168.99.6]) by mail.local.incore (Postfix) with ESMTP id EBB6FA5 for ; Sat, 1 Sep 2018 00:32:07 +0200 (CEST) Message-ID: <5B89C1E7.4090002@incore.de> Date: Sat, 01 Sep 2018 00:32:07 +0200 From: Andreas Longwitz User-Agent: Thunderbird 2.0.0.19 (X11/20090113) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Constraints in libmap(32).conf do not work as expected, possible bug in rtld-elf Content-Type: text/plain; charset=ISO-8859-15 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: Fri, 31 Aug 2018 22:32:18 -0000 On a FreeBSD 10.4-STABLE r337823 (amd64) server I have to run some old php52 scripts from an FreeBSD 8.4-STABLE r284383 (i386) server. I have copied the old php software to /usr/local/php52, installed the ports misc/compat8x and misc/compat9x and have copied all missing 32-bit libraries from the old machine to /usr/local/lib32. With the following libmap32.conf everything works fine: ## php52 /usr/local/lib /usr/local/lib32 /usr/local/lib/mysql /usr/local/lib32/mysql Two examples: -> ldd /usr/local/php52/bin/php /usr/local/php52/bin/php: libcrypt.so.5 => /usr/lib32/libcrypt.so.5 (0x28273000) librt.so.1 => /usr/lib32/librt.so.1 (0x28292000) libm.so.5 => /usr/lib32/libm.so.5 (0x28298000) libxml2.so.5 => /usr/local/lib32/libxml2.so.5 (0x282c2000) libz.so.5 => /usr/local/lib32/compat/libz.so.5 (0x283ec000) libiconv.so.3 => /usr/local/lib32/libiconv.so.3 (0x283fe000) libc.so.7 => /usr/lib32/libc.so.7 (0x284f2000) libthr.so.3 => /usr/lib32/libthr.so.3 (0x2866c000) -> ldd /usr/local/php52/lib/php/20060613/mysql.so /usr/local/php52/lib/php/20060613/mysql.so: libmysqlclient.so.16 => /usr/local/lib32/mysql/libmysqlclient.so.16 (0x28206000) libc.so.7 => /usr/lib32/libc.so.7 (0x28070000) libcrypt.so.5 => /usr/lib32/libcrypt.so.5 (0x2835e000) libm.so.5 => /usr/lib32/libm.so.5 (0x2837d000) libz.so.5 => /usr/local/lib32/compat/libz.so.5 (0x283a7000) librt.so.1 => /usr/lib32/librt.so.1 (0x283b9000) libthr.so.3 => /usr/lib32/libthr.so.3 (0x283bf000) Because I like to use constraints in libmap32.conf I chenged the file to ## php52 [/usr/local/php52/] /usr/local/lib /usr/local/lib32 [/usr/local/php52/lib/php/20060613/mysql.so] /usr/local/lib/mysql /usr/local/lib32/mysql The same examples as above shows that libmap does not work anymore: -> ldd /usr/local/php52/bin/php /usr/local/php52/bin/php: libcrypt.so.5 => /usr/lib32/libcrypt.so.5 (0x28273000) librt.so.1 => /usr/lib32/librt.so.1 (0x28292000) libm.so.5 => /usr/lib32/libm.so.5 (0x28298000) libxml2.so.5 => not found (0) libz.so.5 => /usr/local/lib32/compat/libz.so.5 (0x282c2000) libiconv.so.3 => not found (0) libc.so.7 => /usr/lib32/libc.so.7 (0x282d4000) libthr.so.3 => /usr/lib32/libthr.so.3 (0x2844e000) -> ldd /usr/local/php52/lib/php/20060613/mysql.so /usr/local/php52/lib/php/20060613/mysql.so: libmysqlclient.so.16 => not found (0) libc.so.7 => /usr/lib32/libc.so.7 (0x28070000) The constraints in libmap.conf are handled in rtld-elf with the help of contexts, and especially a "$DEFAULT$" context is used for all entries in libmap.conf before the first constraint statement. Now when rtld-elf loads a program the mapping rules from libmap.conf are applied. In a first step rtld-elf does a direct mapping using the correct context. But in a second step called "Searching for ..." rtld-elf uses always the "$DEFAULT$" context, which in the last example is empty. Therfore rtld-elf does never find a library in his searching step and cannot load programs where searching for libraries is necessary. I cannot see any reason why rtld-elf should change the context between step1 and step2, The following patch provokes that rtld-elf uses the context from step1 in step2 too: --- rtld.c.orig 2018-03-20 16:56:48.000000000 +0100 +++ rtld.c 2018-08-31 23:17:18.051206000 +0200 @@ -186,6 +186,7 @@ static Obj_Entry obj_rtld; /* The dynamic linker shared object */ static unsigned int obj_count; /* Number of objects in obj_list */ static unsigned int obj_loads; /* Number of loads of objects (gen count) */ +static char *save_refobj_path; static Objlist list_global = /* Objects dlopened with RTLD_GLOBAL */ STAILQ_HEAD_INITIALIZER(list_global); @@ -1499,6 +1500,7 @@ if (libmap_disable || !objgiven || (name = lm_find(refobj->path, xname)) == NULL) name = (char *)xname; + save_refobj_path = refobj->path; dbg(" Searching for \"%s\"", name); @@ -2831,7 +2833,7 @@ char *res; len = strcspn(path, ":;"); - trans = lm_findn(NULL, path, len); + trans = lm_findn(save_refobj_path, path, len); if (trans) res = callback(trans, strlen(trans), arg); else This patch solves the described problem for me. Andreas Longwitz From owner-freebsd-stable@freebsd.org Fri Aug 31 22:46:19 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 D500EFCCF0D; Fri, 31 Aug 2018 22:46:19 +0000 (UTC) (envelope-from tomek.cedro@gmail.com) Received: from mail-ua1-f47.google.com (mail-ua1-f47.google.com [209.85.222.47]) (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 7618E893BE; Fri, 31 Aug 2018 22:46:19 +0000 (UTC) (envelope-from tomek.cedro@gmail.com) Received: by mail-ua1-f47.google.com with SMTP id i4-v6so9365582uak.0; Fri, 31 Aug 2018 15:46:19 -0700 (PDT) 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=5O2ke7r9vyeQLT/fNvTYsNc+35LgOSSB+wIfWMtQ/5o=; b=E7bwIg4mh5shyu3eycK1G5YxxhHxPWHePUa08qq4pKjBbgPm8PVtgQDE/GweMuAqHD HSgBPiSQxqAQNaMiFwuhZ4vnt3zQX+cgfS/APcdg8KoYcYyXCtoZkDsEGJwD3+qjdMD2 aPBYopzJyTIoKl8HEAF1cVCSh5m1P+fHRLWcVK4G+mLqZloKexmDPla0/rEPMDXutE0u MloD5TO9fgA9FRwBXXKS7ZwczII6h9g/x99QfjsL5RpdBBYHK7V6UtFDqo/KgoNpjc/Q A7KAY5TCAKWBMgqzIyU5cIdPy++qZV3xmQWTs3UwizrgC7rcvl54Vz3CHEnNm9OvSdxv k2kQ== X-Gm-Message-State: APzg51AvOiOMeJFaXNn5WdwB/SpfOJ5WOUck/It5titAys4LiqypQKmT EqFlmRFqNMObGyfLadnisyxymvJG9hFICSnx5bBlpQiS X-Google-Smtp-Source: ANB0VdYQX3pNhLhUP1n6SRBqAGe9cdFoxpvenAD8SKiYf6eXFpIYavzwrLhcHtvedrkZq7+5YVkIoz319ZZaJygsj00= X-Received: by 2002:ab0:1a10:: with SMTP id a16-v6mr10773370uai.110.1535754031549; Fri, 31 Aug 2018 15:20:31 -0700 (PDT) MIME-Version: 1.0 From: CeDeROM Date: Sat, 1 Sep 2018 00:20:17 +0200 Message-ID: Subject: FreeBSD OpenCL/CUDA nVidia To: FreeBSD Questions Mailing List , FreeBSD Stable Content-Type: text/plain; charset="UTF-8" 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, 31 Aug 2018 22:46:20 -0000 Hello world, Is nVidia OpenCL/CUDA supported on FreeBSD? I have GF1030GT on 11.2-RELEASE AMD64 using 390.77 nvidia driver. CLINFO shows 0 number of platforms :-( Any hints welcome :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info From owner-freebsd-stable@freebsd.org Sat Sep 1 08:20:46 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 ADCC1FCC52F; Sat, 1 Sep 2018 08:20:46 +0000 (UTC) (envelope-from tommi.pernila@gmail.com) Received: from mail-qt0-f169.google.com (mail-qt0-f169.google.com [209.85.216.169]) (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 579C97FB90; Sat, 1 Sep 2018 08:20:46 +0000 (UTC) (envelope-from tommi.pernila@gmail.com) Received: by mail-qt0-f169.google.com with SMTP id z8-v6so17066102qto.9; Sat, 01 Sep 2018 01:20:46 -0700 (PDT) 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=mi/ymWd5W9hZLA8aWxXr7knsyteb6HyIXrp/XRyAjOs=; b=VBwKIVpILSXK0oynVvde4mubfZGFscLwsfbY9QmIYdy1ti3j/J0MPz3dlWSiNW+Qxr /8XJYnfBXzNwgN2rJqNftB1aw9xKtu8gr9KV4Dp0k74ij99mqZYlWPa+HB9vsP5VRSLx UvnONLy13TmlrDy7SU7lNwLfp+QYWWo7iBp6nE4NTKZXZsdo4dBcuAm8irL12oecn8eq yu6Ps5KQRxozZT+rFwhpJzQ3ay/R5c6+ZhPgAYTHIIPLaGrHKm0WP8gGI5YABOsAJ8jX pri/zsAErAv1p9lismJMzkEkLKpXyPRfZA3Yt6lLNqfeTCXnxIqPQ8qImMId8Z0ovPKu mfDw== X-Gm-Message-State: APzg51BVJRYYe5kFAyVI5MxkPDElRnVTM/kK2LVXbyDgi/h3bvKG+FRg kgRx1q2/8Kjt8k7+polRJ39fupvI364tPEoESYE= X-Google-Smtp-Source: ANB0Vdb3pmoWR8WuxjGdIgu9QHF9Af8A2WxZdzZV+X6YIYfgsj7RCaQbcKNtPi5rJPvSAfzQ+i2kRDDPKfrn+gNPgs4= X-Received: by 2002:aed:3bc5:: with SMTP id s5-v6mr18994600qte.207.1535788537070; Sat, 01 Sep 2018 00:55:37 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Tommi Pernila Date: Sat, 1 Sep 2018 10:55:26 +0300 Message-ID: Subject: Re: FreeBSD OpenCL/CUDA nVidia To: CeDeROM Cc: FreeBSD Questions Mailing List , FreeBSD Stable 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: Sat, 01 Sep 2018 08:20:47 -0000 Hi, Nvidia doesn't provide native CUDA drivers. There might be an option on trying to run the driver through the linuxulator, but it looks like it there are some issue with it. this thread has a bit more information: https://forums.freebsd.org/threads/linux-binary-compatibility-nvidia-drivers-and-cuda-for-blender.65065/ So it looks like FreeBSD is not the platform for CUDA. OpenCL with AMD and Intel should be working with FreeBSD. -T On Sat, 1 Sep 2018 at 1.55, CeDeROM wrote: > Hello world, > > Is nVidia OpenCL/CUDA supported on FreeBSD? > > I have GF1030GT on 11.2-RELEASE AMD64 using 390.77 nvidia driver. > CLINFO shows 0 number of platforms :-( > > Any hints welcome :-) > Tomek > > -- > CeDeROM, SQ7MHZ, http://www.tomek.cedro.info > _______________________________________________ > 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 Sat Sep 1 10:39:01 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 D74FAFEA3B2; Sat, 1 Sep 2018 10:39:01 +0000 (UTC) (envelope-from tomek.cedro@gmail.com) Received: from mail-ua1-f52.google.com (mail-ua1-f52.google.com [209.85.222.52]) (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 80DD284CB5; Sat, 1 Sep 2018 10:39:01 +0000 (UTC) (envelope-from tomek.cedro@gmail.com) Received: by mail-ua1-f52.google.com with SMTP id m11-v6so10011173uao.11; Sat, 01 Sep 2018 03:39:01 -0700 (PDT) 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=eRNPphLWcN+pR16j5TAv5MJt3OFgmUPPYP5kjnqzTK8=; b=Mb5SuvW6HxEVUiN0xZdJ3IzXHvRQyAw2OLtNfzfGLDCs9u3NySG5wcpB0zC8zMJrcA bC3quKVqBcFSjUtIH3qAp3lrmIQOIN/sePdXidOITnKBIhCR1+z2OiLV/l+9n1h2I89v HcrhVHsYeCFgw0IGCgIjQhJYTTD2gdlQ9iI2h+Gy8DL9Ylo7a/Il0OurvHfjsk1RBaWO mhY8RGTpRmaGGSQunT94gZP8jqJVeYRyv/QoOjpQ4NGJ6eZXBNaa7m3lYXoeiqZlxcPQ Fsheh5N1kwApJJm/Xuif5dCKOCh5h1pGGjPSQmuV55In7qGk6W6hE6E6uFZVvso42h4X PCXg== X-Gm-Message-State: APzg51CUZzmxiwEIxRBzjiHSPFcCJfgBFxWYg2X4gX5g+961O/59Eder l2phZ6CE6L1R0oUxSBAmQFWup5UuJW4KJDNyxK0= X-Google-Smtp-Source: ANB0VdbKZHy5AKIfsMUeL9Tm04YZKM7ow4V9+w3ggs4jW+P2ZghYxVKU1jbhZkq6Rzw4uo1yblXL2BQxDMy2hGJp4uU= X-Received: by 2002:ab0:1544:: with SMTP id p4-v6mr11531905uae.81.1535795054225; Sat, 01 Sep 2018 02:44:14 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: CeDeROM Date: Sat, 1 Sep 2018 11:44:02 +0200 Message-ID: Subject: Re: FreeBSD OpenCL/CUDA nVidia To: tommi.pernila@iki.fi Cc: FreeBSD Questions Mailing List , FreeBSD Stable , nvidia-bug-report@nvidia.com Content-Type: text/plain; charset="UTF-8" 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, 01 Sep 2018 10:39:02 -0000 Thank you Tommy.. bad news.. how did that happen for nVidia to become worst GPU driver provider to FreeBSD lagging even behind ATI/AMD and Intel.. I guess these are closed-source drivers so we have nothing to do here.. I was always buying nVidia only because of trust in their best drivers.. but that needs to be revised I see :-( -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info From owner-freebsd-stable@freebsd.org Sat Sep 1 17:09:49 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 86D71FF5158 for ; Sat, 1 Sep 2018 17:09:49 +0000 (UTC) (envelope-from randy@psg.com) Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 3B75E73C70 for ; Sat, 1 Sep 2018 17:09:49 +0000 (UTC) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from ) id 1fw9P9-0006bY-HP; Sat, 01 Sep 2018 17:09:47 +0000 Date: Sat, 01 Sep 2018 10:09:46 -0700 Message-ID: From: Randy Bush To: Pete Wright Cc: freebsd-stable@freebsd.org Subject: Re: bad hash in repo In-Reply-To: References: <40cbc4e4-c0c8-e9f7-ba88-48dc226b032a@nomadlogic.org> User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/25.3 Mule/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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, 01 Sep 2018 17:09:49 -0000 >>>> seeing a lot of these >>>>=20 >>>> Looking up update.FreeBSD.org mirrors... 2 mirrors found. >>>> Fetching metadata signature for 11.1-RELEASE from update4.freebsd.org.= .. done. >>>> Fetching metadata index... done. >>>> Inspecting system... done. >>>> Preparing to download files... done. >>>> Fetching 2 patches.. done. >>>> Applying patches... done. >>>> Fetching 2 files... 104969ef03336523729ea1df2547267441a13cb040c778e971= b74103e88dbc77 has incorrect hash. >>> these continue; like for a week. for multiple servers, all on the >>> global internet no filters other than samba etc. >>=20 >> have you forced pulling down metadata from the pkg servers?=A0 i have >> gotten into this state in the past and a "pkg update -f" would get me >> out of that scenario. >=20 > # pkg update -f > Updating FreeBSD repository catalogue... > Fetching meta.txz: 100% 944 B 0.9kB/s 00:01 =20 > Fetching packagesite.txz: 100% 6 MiB 2.2MB/s 00:03 =20 > Processing entries: 100% > FreeBSD repository update completed. 32029 packages processed. > All repositories are up to date. > # freebsd-update fetch > Looking up update.FreeBSD.org mirrors... 2 mirrors found. > Fetching metadata signature for 11.1-RELEASE from update5.freebsd.org... = done. > Fetching metadata index... done. > Inspecting system... done. > Preparing to download files... done. > Fetching 2 patches.. done. > Applying patches... done. > Fetching 2 files... 104969ef03336523729ea1df2547267441a13cb040c778e971b74= 103e88dbc77 has incorrect hash. this is now over two weeks. still multiple systems on public net, v4 and dual stack. randy From owner-freebsd-stable@freebsd.org Sat Sep 1 17:45:56 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 CFF54FF5F4C for ; Sat, 1 Sep 2018 17:45:55 +0000 (UTC) (envelope-from alex.mckeever@sbcglobal.net) Received: from sonic308-12.consmr.mail.gq1.yahoo.com (sonic308-12.consmr.mail.gq1.yahoo.com [98.137.68.36]) (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 5FA4274CF7 for ; Sat, 1 Sep 2018 17:45:55 +0000 (UTC) (envelope-from alex.mckeever@sbcglobal.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sbcglobal.net; s=s2048; t=1535823954; bh=WNlTApB1r49XQ8Q5dofSTDB7TdhfToZa/kGIq8ctnjk=; h=Date:From:To:Subject:References:From:Subject; b=gkaRQf+iZXUONu+rjpN2tS8vo21asAhUaGttuRrqTzNlTmUu66XtEFf1f8PHvaY7t+arFDuN9nphFf26xtDtlQh4UhKRv8aOxNhM28LGaa0kk2kJAc+kVfcpmgTXwxhnwSx9gcDJyEhRTuGKALnp8KIYQZtYA++RryXFRTRElNNspKnWEaYfTj9rhjiLidQftD6Vyrfa6Bm4B5Kswb4ip8tUhSZTtprNHKnyxITHRpBy0iJvTEkqJsNTlKDErOmPXMvNRmKK3CKdl6IUW2HiBur5vh3qX4Lx4GRTVmbAnmgfQrp10Z2UEr4vAHMm98EctowJCYndrB0B+HA6JuGojg== X-YMail-OSG: WGNR8lUVM1kDryf.spk.3kM3xUQlxdVgfw1Rb1hEBDlwsDHA6tW93u0Hy.74eWf RGC9vEcH7iBc9xapHlWD_Ag55wOy5CZCaINxYJ8JnZSklx8Vk6yb_PJL9EX4XazmOc189k4myBoC VAwVDaUVQnnZW2UO37mVwjb9sg5dRkfCdqV5.f0S1cpNZYrYC1ZC5eMCzYP79xqAfQOVUrS2nEpC u6oO34wsSu9UuOiiMPKA4EEsZF3r0lgHm7CDfj6K6mw.EBquTml.giItCZqkT3DGGn5axoSbSd.S zZWkEP6AJUg8JHbDJbRGYbHHAQ.HDvggSEl5ZfVOFIW27.yEr53uCFqAlk7ukCTRVUvfyN.pUJRB xF3qyFSFJmsqqQmv5X00myxBVTov1FeOxKk1V5EK96NNZ5sv.SExF1Xvv1uavoM11iEFCLaPgmV_ lf2HcfQZUgemDT6MF9d.qyT1kE7IDvFxIgMWsg.1FXhJ3uwIaOW7nCTW7046B.9vjUGFxGnJgWUs WyWRqAbLOwfe8fGzrTsqwEd_X0sZHLai3CIdolGJX2_o0ao9HMTjwW5vZ5INUghLvO8G9Wg9ohj7 nETb_NIw0eUbReDsT.vLoO0D2v.VOXg0nnzF0X9.oH2tKii0HScO9oa3zaN0Ki.oWu5iN0gxZbsU OEEWZLwW8CFlMGTYyds.suX6bksnmhjbsxme1ZPBK29P48a03klEbUkOlhNrgWgeLH_ucnpZzT3S zV4Rh9YAaOo_dG3Wlxh2UOGhuihT7Q0WAIKEP_y61_uSSclU_RW_ZhivRarU_.vMW0fYWm4YSXi3 jy5.pKHDNRHNDOKDTDB5s1749vMkvdwnVXCsWQB9Ji_sdOEGhrJzKKaJyO1pS7D74cTbKP.2v8w9 LllhH9ULnhlI6f5G_v5Ou4QF.X9D.NkOZMuGTnl8aCcPt3SyG4eh81GejGq6Ilnjf7jaHyTl_U4u FJvKBpNM3YooaCBN6IDOFSXIKkMESTVa4KEaxl7ZDLgNPhERQkz8- Received: from sonic.gate.mail.ne1.yahoo.com by sonic308.consmr.mail.gq1.yahoo.com with HTTP; Sat, 1 Sep 2018 17:45:54 +0000 Date: Sat, 1 Sep 2018 17:25:34 +0000 (UTC) From: Alex McKeever To: FreeBSD Stable , FreeBSD Current Message-ID: <826294696.2192772.1535822734294@mail.yahoo.com> Subject: Failing to retrieve source tarballs for anything. MIME-Version: 1.0 References: <826294696.2192772.1535822734294.ref@mail.yahoo.com> X-Mailer: WebService/1.1.12337 YahooMailIosMobile Raven/42997 CFNetwork/902.2 Darwin/17.7.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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: Sat, 01 Sep 2018 17:45:56 -0000 After compiling PKG, when I go to ports to compile anything (my eMac can ru= n FreeBSD but not modern Linux due to the version of the Radeon GPU) it fai= ls to retrieve any of the source tarballs for any of the software, desktop = environments etc. I would like help to fix this, as I=E2=80=99d like to run= something current. Sent from Yahoo Mail for iPhone From owner-freebsd-stable@freebsd.org Sat Sep 1 18:18:28 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 BAF25FF6ACB for ; Sat, 1 Sep 2018 18:18:28 +0000 (UTC) (envelope-from spork@bway.net) Received: from smtp1.bway.net (smtp1.v6.bway.net [IPv6:2607:d300:1::27]) (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 7722575C45 for ; Sat, 1 Sep 2018 18:18:28 +0000 (UTC) (envelope-from spork@bway.net) Received: from frankentosh.sporklab.com (pool-108-53-194-153.nwrknj.fios.verizon.net [108.53.194.153]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: spork@bway.net) by smtp1.bway.net (Postfix) with ESMTPSA id 9299695853; Sat, 1 Sep 2018 14:18:16 -0400 (EDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: bad hash in repo From: Charles Sprickman In-Reply-To: Date: Sat, 1 Sep 2018 14:18:15 -0400 Cc: Pete Wright , freebsd-stable@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <8C150C27-844D-4F32-907B-8ABD7D711846@bway.net> References: <40cbc4e4-c0c8-e9f7-ba88-48dc226b032a@nomadlogic.org> To: Randy Bush X-Mailer: Apple Mail (2.3273) 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, 01 Sep 2018 18:18:28 -0000 > On Sep 1, 2018, at 1:09 PM, Randy Bush wrote: >=20 >>>>> seeing a lot of these >>>>>=20 >>>>> Looking up update.FreeBSD.org mirrors... 2 mirrors found. >>>>> Fetching metadata signature for 11.1-RELEASE from = update4.freebsd.org... done. >>>>> Fetching metadata index... done. >>>>> Inspecting system... done. >>>>> Preparing to download files... done. >>>>> Fetching 2 patches.. done. >>>>> Applying patches... done. >>>>> Fetching 2 files... = 104969ef03336523729ea1df2547267441a13cb040c778e971b74103e88dbc77 has = incorrect hash. >>>> these continue; like for a week. for multiple servers, all on the >>>> global internet no filters other than samba etc. >>>=20 >>> have you forced pulling down metadata from the pkg servers? i have >>> gotten into this state in the past and a "pkg update -f" would get = me >>> out of that scenario. >>=20 >> # pkg update -f >> Updating FreeBSD repository catalogue... >> Fetching meta.txz: 100% 944 B 0.9kB/s 00:01 =20 >> Fetching packagesite.txz: 100% 6 MiB 2.2MB/s 00:03 =20 >> Processing entries: 100% >> FreeBSD repository update completed. 32029 packages processed. >> All repositories are up to date. >> # freebsd-update fetch >> Looking up update.FreeBSD.org mirrors... 2 mirrors found. >> Fetching metadata signature for 11.1-RELEASE from = update5.freebsd.org... done. >> Fetching metadata index... done. >> Inspecting system... done. >> Preparing to download files... done. >> Fetching 2 patches.. done. >> Applying patches... done. >> Fetching 2 files... = 104969ef03336523729ea1df2547267441a13cb040c778e971b74103e88dbc77 has = incorrect hash. >=20 > this is now over two weeks. still multiple systems on public net, v4 > and dual stack. The other brute-force approach is: rm -rf /var/db/freebsd-update/* Also, is it always fetching from "update5.freebsd.org=E2=80=9D? Charles >=20 > randy > _______________________________________________ > 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 Sat Sep 1 19:58:19 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 17A4CFF8F62 for ; Sat, 1 Sep 2018 19:58:19 +0000 (UTC) (envelope-from jonc@chen.org.nz) Received: from mail-oi0-x242.google.com (mail-oi0-x242.google.com [IPv6:2607:f8b0:4003:c06::242]) (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 9088679263 for ; Sat, 1 Sep 2018 19:58:17 +0000 (UTC) (envelope-from jonc@chen.org.nz) Received: by mail-oi0-x242.google.com with SMTP id 13-v6so27505751ois.1 for ; Sat, 01 Sep 2018 12:58:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chen-org-nz.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=sZYkZ5Q5G+fOTMc6RbJWCAbQ4XOTsVdrB7m8l47rlzY=; b=uox3u6gHpmd/warz6Ot4X9wnua/tO1P4Wrfx1owsApNc1X4HS/87F9xK0FQnkCR0gR bgNYEh9mNncikHRDRZ72Me3CJzcz+EsEOTCcBQIZ3owPi+M5n/m3GZUwExjNnHRyHrzm 0M/gnGF+Dkik34Wgv06ChqcRph4BAc7mXGj+8rsxOI3eOml/SO2UZGyaoq55a60S/tOQ 759SUX29x2eMxqo9HDp0+AQWEv3eE20lrz51yOQ5z7lSpvYz90Jwx4x+MBhiegW+m7US O+nNnfW6bsAwuiasq2jyybkNnXP3kCy7ethjfptWDFj1JAip187ikqYL+ZBzUxS196bo jUsw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=sZYkZ5Q5G+fOTMc6RbJWCAbQ4XOTsVdrB7m8l47rlzY=; b=uk63+/Xi+26Fru8siJ5FyWqWezgCrQqYJwx7QGTr/C0JU1FXMD2+MmdB0RaSYJO38W 9NWe4tR09yPdNsEZ0mdbBB6OJQ7X2fxy0GMjvpwUf8Fz8gGhH7wNPHzsIAdmBg5sJUYl 5CVJFeup9F18NTFAqUN9EBiZ2n/uxAdYSaNwskZeW2dGdzEZ0ohrvC1YXZjbBsxIrfJp 30dp8zhQ124aKSmJdlb76IBi7CZUWvIQ+qmF/Gok+ZyoNgRi+rbOCmsXFhFB7/N6Xmog TEK5vXs2pxY65Zi4Zoca7SOs1DnNKKzng/1LIOItKh2l8aAfgTQw/bl3OY/srYA2xHSu KnSA== X-Gm-Message-State: APzg51CCQ/W+Ea2gNAfYTc8AmvrAhMuMCQ+AyUSPw2RvarALUKdyimBx zgGNbjooeM6G5PAyOeVYv23DzsV9UZWaTW+bq/daJw== X-Google-Smtp-Source: ANB0VdaBGN9XwZfWiST2ce25A454xMHdICRc7PWVs73jstrmpBxv35prDoI3vuoBY7lXCNip1xy6ImUPkB1MUG4auFE= X-Received: by 2002:aca:90d:: with SMTP id 13-v6mr11977958oij.300.1535831897051; Sat, 01 Sep 2018 12:58:17 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a9d:28d:0:0:0:0:0 with HTTP; Sat, 1 Sep 2018 12:58:16 -0700 (PDT) X-Originating-IP: [203.97.70.34] In-Reply-To: <826294696.2192772.1535822734294@mail.yahoo.com> References: <826294696.2192772.1535822734294.ref@mail.yahoo.com> <826294696.2192772.1535822734294@mail.yahoo.com> From: Jonathan Chen Date: Sun, 2 Sep 2018 07:58:16 +1200 Message-ID: Subject: Re: Failing to retrieve source tarballs for anything. To: Alex McKeever Cc: FreeBSD Stable , FreeBSD Current Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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, 01 Sep 2018 19:58:19 -0000 On 2 September 2018 at 05:25, Alex McKeever w= rote: > After compiling PKG, when I go to ports to compile anything (my eMac can = run FreeBSD but not modern Linux due to the version of the Radeon GPU) it f= ails to retrieve any of the source tarballs for any of the software, deskto= p environments etc. I would like help to fix this, as I=E2=80=99d like to r= un something current. > How old is your ports tree? It it up to date? What sort of problems are you seeing in fetching the port sources? Since no one else has reported any problems, it is most likely something to do with your local environment. Cheers. --=20 Jonathan Chen From owner-freebsd-stable@freebsd.org Sat Sep 1 20:57: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 39C65FFA614; Sat, 1 Sep 2018 20:57:06 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp-relay-int.realworks.nl (smtp-relay-int.realworks.nl [194.109.157.20]) (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 C8EA07B352; Sat, 1 Sep 2018 20:57:05 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Date: Sat, 1 Sep 2018 22:56:56 +0200 (CEST) From: Ronald Klop To: Alex McKeever , FreeBSD Stable , FreeBSD Current Message-ID: <1591692302.38239.1535835416316@localhost> In-Reply-To: <826294696.2192772.1535822734294@mail.yahoo.com> Subject: Re: Failing to retrieve source tarballs for anything. MIME-Version: 1.0 X-Mailer: Realworks (422.9-265200) Importance: Normal X-Priority: 3 (Normal) Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable 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: Sat, 01 Sep 2018 20:57:06 -0000 It helps a lot of you send the exact command you run with the error message= . Or all the significant output. Regards, Ronald Van: Alex McKeever Datum: 01 september 2018 19:50 Aan: FreeBSD Stable , FreeBSD Current Onderwerp: Failing to retrieve source tarballs for anything. >=20 >=20 > After compiling PKG, when I go to ports to compile anything (my eMac can = run FreeBSD but not modern Linux due to the version of the Radeon GPU) it f= ails to retrieve any of the source tarballs for any of the software, deskto= p environments etc. I would like help to fix this, as I=E2=80=99d like to r= un something current. >=20 >=20 > Sent from Yahoo Mail for iPhone > _______________________________________________ > 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" >=20 >=20 From owner-freebsd-stable@freebsd.org Sat Sep 1 21:06: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 8D95FFFAAA8 for ; Sat, 1 Sep 2018 21:06:45 +0000 (UTC) (envelope-from alex.mckeever@sbcglobal.net) Received: from sonic308-12.consmr.mail.gq1.yahoo.com (sonic308-12.consmr.mail.gq1.yahoo.com [98.137.68.36]) (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 13B0D7B956 for ; Sat, 1 Sep 2018 21:06:44 +0000 (UTC) (envelope-from alex.mckeever@sbcglobal.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sbcglobal.net; s=s2048; t=1535836003; bh=Php/OhSHyR9u0a83sNJOH/YNGZ7T5t8jJMO56AXA+GU=; h=Date:From:To:In-Reply-To:References:Subject:From:Subject; b=CLDEVBLPrFU3d0mIK9g2UQCe5w8uUOi3KP7Tz76+K9Srsuo5HDkSz9dcXLNeQxsURbhSPcPe4yYdS3xpkkmQus7aIKlG8gUmI5Yr2zUX8kQfLnz0/z6rzuhZQYjK49Rq74CzjazlHEyiYk2gVN94tCIR+eQvzLK5P3Uzs3jML6X73dEhsnVtZ7T2+fLaCfeDjlliNsxC0Bu38sMr2v5RWrYfVGpjyUPHlS5CnqhEd71C9f/qQ4NKrPe5LUyD3Jc6oX8V5HSbtLVJl5PjZlSnbwnpx6uJXJYX3hM/uXPt1JlXg9MrH62G9giKXQpaGR78c9m2JdGh2otyuCkTHfsZTg== X-YMail-OSG: XMhZOyEVM1mjN2mVUIXtBcOo9g0W4Xj2mGJuuXAhHfTYfPRAw6gD8QR3qupCsKq h4vFJDswkQyPYnjFNTO2hfT09sa8kF8Oa31hw6MlUuRdZLQjmZaFVA.aPxGwSVK2ymsljHPVld2o 2TvlCLftI9MOZSyPGI77k.K6c4qi6pjp9DsQ_fdLhm4PFCx.WxypJQJtaitMlhMpEOx4Cm1BHfbn SMOiKn2zLT8eqo2Q051C61Qmd55vj_Zf7.qU47nVKaZ.m59E1OL6HaDEfSIqeN4.1W2fQ6prZdgI ANon9ElSy44WOolorkREwbBRf8eRspXLpKNMYCti9lUbhx_WALF55Ks0DvsTV_fggduIhsL5ioyj u6wbQzLkfXVps47ghu.sRJs_cnhFFbcaNj0cIqicn6LIN96LqbcUDKzz1OLyHBV3CMSMK1uEnV27 hSITLQKdj615LX0QqMR8TF7xu31qXiCj1en95iciGox4jHab2BbUgIAe3K8yw5.4dEvHh1URTprH JCx28T.gEkOXgQ1jvmj8JrHCVABBkyWh6i5ctfCJwMAf3MhzgQF_Lws80sbxtt_PUBiV3Z2Ne5ts VHRfaMI.FMPJwfsXNgHZSthGi5KDyVw2gd7ylYL7AbS86PP_3aYw_i1xhdgHAJj0sY2fTm0Q0f2T nWmJNVP7FEBMIsrYO9h7DM83hBHbwVgMsQIrFHqMPyXVo82d5c_AtXdZmBH7lMm6SJF8dbsOqnzD oMDj8K9DpZebQ2jEzC1Vv2VDPF9YCI57cok9Nh8f3N7URBuWrP66tcIffQmKwTCL5NypLD9nTuRq n3xwzU9eo4uuyqwMDxq5qS8bPy8n5pyOigJPR8AayV3qpTj6_cCivEsc6Za7aq.XiUzYyfeLql8C 6lU.GUaUnNuyinCsnT6L_YuXHN0R5dCEofsu93ogFUZSH0AzgAR29i3kDel39FxrvlwQcY0mcN2m 3BrIOs9mX1ViD4TvtLaAvtRUeWU9W.Agdm3hxyMd.E1NKejKQiH0- Received: from sonic.gate.mail.ne1.yahoo.com by sonic308.consmr.mail.gq1.yahoo.com with HTTP; Sat, 1 Sep 2018 21:06:43 +0000 Date: Sat, 1 Sep 2018 21:06:36 +0000 (UTC) From: Alex McKeever To: Ronald Klop , FreeBSD Stable , FreeBSD Current Message-ID: <294624069.2289978.1535835996261@mail.yahoo.com> In-Reply-To: <1591692302.38239.1535835416316@localhost> References: <826294696.2192772.1535822734294@mail.yahoo.com> <1591692302.38239.1535835416316@localhost> Subject: Re: Failing to retrieve source tarballs for anything. MIME-Version: 1.0 X-Mailer: WebService/1.1.12337 YahooMailIosMobile Raven/42997 CFNetwork/902.2 Darwin/17.7.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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: Sat, 01 Sep 2018 21:06:45 -0000 I simply changed directory to which thing I want to compile in /ports, run = the command make install, and after a short while it fails to retrieve the = source archive (.tar.gz) Sent from Yahoo Mail for iPhone On Saturday, September 1, 2018, 4:56 PM, Ronald Klop = wrote: It helps a lot of you send the exact command you run with the error message= . Or all the significant output. Regards,Ronald Van: Alex McKeever Datum: 01 september 2018 19:50 Aan: FreeBSD Stable , FreeBSD Current Onderwerp: Failing to retrieve source tarballs for anything. After compiling PKG, when I go to ports to compile anything (my eMac can ru= n FreeBSD but not modern Linux due to the version of the Radeon GPU) it fai= ls to retrieve any of the source tarballs for any of the software, desktop = environments etc. I would like help to fix this, as I=E2=80=99d like to run= something current. Sent from Yahoo Mail for iPhone _______________________________________________ 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 Sat Sep 1 22:49:04 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 8E856FCDEFE for ; Sat, 1 Sep 2018 22:49:04 +0000 (UTC) (envelope-from randy@psg.com) Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 326117E4E3 for ; Sat, 1 Sep 2018 22:49:04 +0000 (UTC) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from ) id 1fwEhR-0007ED-3V; Sat, 01 Sep 2018 22:49:01 +0000 Date: Sat, 01 Sep 2018 15:48:59 -0700 Message-ID: From: Randy Bush To: Charles Sprickman Cc: Pete Wright , freebsd-stable@freebsd.org Subject: Re: bad hash in repo In-Reply-To: <8C150C27-844D-4F32-907B-8ABD7D711846@bway.net> References: <40cbc4e4-c0c8-e9f7-ba88-48dc226b032a@nomadlogic.org> <8C150C27-844D-4F32-907B-8ABD7D711846@bway.net> User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/25.3 Mule/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII 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, 01 Sep 2018 22:49:04 -0000 >>> # pkg update -f >>> Updating FreeBSD repository catalogue... >>> Fetching meta.txz: 100% 944 B 0.9kB/s 00:01 >>> Fetching packagesite.txz: 100% 6 MiB 2.2MB/s 00:03 >>> Processing entries: 100% >>> FreeBSD repository update completed. 32029 packages processed. >>> All repositories are up to date. >>> # freebsd-update fetch >>> Looking up update.FreeBSD.org mirrors... 2 mirrors found. >>> Fetching metadata signature for 11.1-RELEASE from update5.freebsd.org... done. >>> Fetching metadata index... done. >>> Inspecting system... done. >>> Preparing to download files... done. >>> Fetching 2 patches.. done. >>> Applying patches... done. >>> Fetching 2 files... 104969ef03336523729ea1df2547267441a13cb040c778e971b74103e88dbc77 has incorrect hash. >> >> this is now over two weeks. still multiple systems on public net, v4 >> and dual stack. > > The other brute-force approach is: > > rm -rf /var/db/freebsd-update/* work0.psg.com:/root# rm -rf /var/db/freebsd-update/* work0.psg.com:/root# freebsd-update --not-running-from-cron fetch Looking up update.FreeBSD.org mirrors... 2 mirrors found. Fetching public key from update5.freebsd.org... done. Fetching metadata signature for 11.1-RELEASE from update5.freebsd.org... done. Fetching metadata index... done. Fetching 2 metadata files... done. Inspecting system... done. Preparing to download files... done. Fetching 66 patches.....10....20....30....40....50....60... done. Applying patches... done. Fetching 3 files... 104969ef03336523729ea1df2547267441a13cb040c778e971b74103e88dbc77 has incorrect hash.