Date: Fri, 27 Nov 2020 16:34:24 +0100 (CET) From: Ronald Klop <ronald-lists@klop.ws> To: freebsd-current@freebsd.org Subject: Re: possible usb3-connected hard drive spin down causing lag Message-ID: <1299467375.48.1606491264664@localhost> In-Reply-To: <X8Bxd7jNbaWNKmMM@rpi4.local> References: <X77ygGTS09S91bTC@rpi4.local> <X8Bxd7jNbaWNKmMM@rpi4.local>
next in thread | previous in thread | raw e-mail | index | archive | help
Van: tech-lists <tech-lists@zyxst.net> Datum: vrijdag, 27 november 2020 04:24 Aan: freebsd-current@freebsd.org Onderwerp: Re: possible usb3-connected hard drive spin down causing lag > > Hi, > > It seems the issue wasn't with the hardware or the connection. > I use mutt and it's the program that was slowing everything down, > and that was down to me using new mutt with my old config. The whole > pause for 5 seconds thing was due to it scanning gigabytes of email each time it woke up. The fix was to review the config and change a couple of settings. Now there's no delay (well there is a bit but only because it's scanning the folders it's told to for new mail). > > But looking at a hardware cause wasn't in vain. On the way to the solution, found a few tips through here that sped up the system generally, and learned a bit. So now I have a *really quick* raspberry pi4 which is rock-solid stable, so thanks :D > > -- > J. > Mind to share these tips, so I can use them on my RPI4? ;-) From owner-freebsd-current@freebsd.org Fri Nov 27 17:09:32 2020 Return-Path: <owner-freebsd-current@freebsd.org> Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 6F4F64ACB16 for <freebsd-current@mailman.nyi.freebsd.org>; Fri, 27 Nov 2020 17:09:32 +0000 (UTC) (envelope-from rebecca@bsdio.com) Received: from out02.mta.xmission.com (out02.mta.xmission.com [166.70.13.232]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4CjLhX22Cxz3mCs; Fri, 27 Nov 2020 17:09:32 +0000 (UTC) (envelope-from rebecca@bsdio.com) Received: from in01.mta.xmission.com ([166.70.13.51]) by out02.mta.xmission.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.93) (envelope-from <rebecca@bsdio.com>) id 1kihFR-00EAAX-S0; Fri, 27 Nov 2020 10:09:29 -0700 Received: from mta4.zcs.xmission.com ([166.70.13.68]) by in01.mta.xmission.com with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.87) (envelope-from <rebecca@bsdio.com>) id 1kihFR-0001Gi-Cq; Fri, 27 Nov 2020 10:09:29 -0700 Received: from localhost (localhost [127.0.0.1]) by mta4.zcs.xmission.com (Postfix) with ESMTP id 34A6E50030C; Fri, 27 Nov 2020 10:09:29 -0700 (MST) X-Amavis-Modified: Mail body modified (using disclaimer) - mta4.zcs.xmission.com Received: from mta4.zcs.xmission.com ([127.0.0.1]) by localhost (mta4.zcs.xmission.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 04fujQjnuS4v; Fri, 27 Nov 2020 10:09:29 -0700 (MST) Received: from [10.0.10.142] (c-174-52-16-57.hsd1.ut.comcast.net [174.52.16.57]) by mta4.zcs.xmission.com (Postfix) with ESMTPSA id 007915006B2; Fri, 27 Nov 2020 10:09:28 -0700 (MST) To: Hans Petter Selasky <hps@selasky.org>, freebsd-current@freebsd.org Cc: kib@freebsd.org References: <2a0f9031-a96d-2989-4d6c-a7691c451b74@bsdio.com> <d19ff5d6-65a8-251a-693b-3ff42b60a252@selasky.org> From: Rebecca Cran <rebecca@bsdio.com> Message-ID: <40ac5686-aa96-f9e4-7c9c-5dbe628af49a@bsdio.com> Date: Fri, 27 Nov 2020 10:09:20 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.4.3 MIME-Version: 1.0 In-Reply-To: <d19ff5d6-65a8-251a-693b-3ff42b60a252@selasky.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-XM-SPF: eid=1kihFR-0001Gi-Cq; ; ; mid=<40ac5686-aa96-f9e4-7c9c-5dbe628af49a@bsdio.com>; ; ; hst=in01.mta.xmission.com; ; ; ip=166.70.13.68; ; ; frm=rebecca@bsdio.com; ; ; spf=none X-SA-Exim-Connect-IP: 166.70.13.68 X-SA-Exim-Mail-From: rebecca@bsdio.com X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on sa08.xmission.com X-Spam-Level: ** X-Spam-Status: No, score=2.0 required=8.0 tests=ALL_TRUSTED,BAYES_50, DCC_CHECK_NEGATIVE,LotsOfNums_01,NICE_REPLY_A,T_TM2_M_HEADER_IN_MSG, TooManyTo_001,XMSubLong,XM_B_Unicode autolearn=disabled version=3.4.2 X-Spam-Report: * -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP * 0.8 BAYES_50 BODY: Bayes spam probability is 40 to 60% * [score: 0.5011] * 0.7 XMSubLong Long Subject * 0.3 TooManyTo_001 Multiple "To" Header Recipients 2x (uncommon) * 0.0 XM_B_Unicode BODY: Testing for specific types of unicode * 1.2 LotsOfNums_01 BODY: Lots of long strings of numbers * 0.0 T_TM2_M_HEADER_IN_MSG BODY: No description available. * -0.0 DCC_CHECK_NEGATIVE Not listed in DCC * [sa08 1397; IP=ok Body=1 Fuz1=1] [Fuz2=1] * -0.0 NICE_REPLY_A Looks like a legit reply (A) X-Spam-DCC: XMission; sa08 1397; IP=ok Body=1 Fuz1=1 Fuz2=1 X-Spam-Combo: **;Hans Petter Selasky <hps@selasky.org>, freebsd-current@freebsd.org X-Spam-Relay-Country: X-Spam-Timing: total 297 ms - load_scoreonly_sql: 0.06 (0.0%), signal_user_changed: 15 (5.0%), b_tie_ro: 12 (4.1%), parse: 1.39 (0.5%), extract_message_metadata: 6 (1.9%), get_uri_detail_list: 0.79 (0.3%), tests_pri_-1000: 3.9 (1.3%), tests_pri_-950: 2.2 (0.7%), tests_pri_-900: 1.83 (0.6%), tests_pri_-90: 98 (32.9%), check_bayes: 96 (32.2%), b_tokenize: 7 (2.4%), b_tok_get_all: 7 (2.2%), b_comp_prob: 2.2 (0.8%), b_tok_touch_all: 75 (25.2%), b_finish: 1.22 (0.4%), tests_pri_0: 156 (52.7%), check_dkim_signature: 0.49 (0.2%), check_dkim_adsp: 40 (13.5%), poll_dns_idle: 34 (11.4%), tests_pri_10: 2.1 (0.7%), tests_pri_500: 7 (2.4%), rewrite_mail: 0.00 (0.0%) Subject: Re: panic shortly after boot when amdgpu.ko is loaded (fpu?) X-Spam-Flag: No X-SA-Exim-Version: 4.2.1 (built Thu, 05 May 2016 13:38:54 -0600) X-SA-Exim-Scanned: Yes (on in01.mta.xmission.com) X-Rspamd-Queue-Id: 4CjLhX22Cxz3mCs X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current <freebsd-current.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>; List-Post: <mailto:freebsd-current@freebsd.org> List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 27 Nov 2020 17:09:32 -0000 On 11/27/20 4:29 AM, Hans Petter Selasky wrote: > > Is the problem always triggered by hald? If you disable hald in > rc.conf, does the system run for a longer period of time? It turns out that disabling ntpd let the system run for a longer period of time - until I ran "sysctl sys" at which point I got a panic. And this time the panic actually implicates amdgpu.ko, which is an improvement: #9 0x0000000000000000 in ?? () #10 0xffffffff82a14c4e in amdgpu_device_get_pcie_replay_count () from /boot/modules/amdgpu.ko #11 0xffffffff82a14b80 in sysctl_handle_attr () from /boot/modules/amdgpu.ko #12 0xffffffff80c06cc1 in sysctl_root_handler_locked (oid=0xfffffe02133ff000, arg1=0xfffffe016e360980, arg2=-8724518803888, req=0xfffffe016e360980, tracker=0xfffff81099af6280) at /usr/src/sys/kern/kern_sysctl.c:184 #13 0xffffffff80c0610c in sysctl_root (oidp=<optimized out>, arg1=0xfffff810aa27e650, arg2=-2100190360, req=0xfffffe016e360980) at /usr/src/sys/kern/kern_sysctl.c:2211 Since it _is_ a problem in amdgpu, I'll stop this thread and re-post on freebsd-x11. -- Rebecca Cran
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1299467375.48.1606491264664>