From nobody Sat Nov 06 10:58:34 2021 X-Original-To: arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 64AA4184C1AC for ; Sat, 6 Nov 2021 10:58:38 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HmZ9p25gwz3KjK for ; Sat, 6 Nov 2021 10:58:38 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from [192.168.0.88] (unknown [195.64.148.76]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: avg/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id DDE94215CA for ; Sat, 6 Nov 2021 10:58:37 +0000 (UTC) (envelope-from avg@FreeBSD.org) To: arm@FreeBSD.org From: Andriy Gapon Subject: huge emmc speed regression Message-ID: <812ab31a-ce6e-d8ac-3539-39e6b20a01df@FreeBSD.org> Date: Sat, 6 Nov 2021 12:58:34 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Firefox/78.0 Thunderbird/78.14.0 List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-ThisMailContainsUnwantedMimeParts: N Upfront, I haven't tested the latest main / current yet. I should really test it but that's porbably for the next weekend. I see a huge emmc speed difference between the current from April 2021 and September 2021 (commit 5e79bba562bc303eed669dbd0d391b6c6a9c289b) on Orange Pi PC Plus using on-board eMMC card. I use MMCCAM in both cases. In the old environment I see expected read speeds (with sequential dd) of around 40 MB/s. In the new environment the speeds are around 300 KB/s (like a very good floppy disk of old). Some info from the old environment: # camcontrol mmcsdcmd 2:0:0 -I Host controller information Host OCR: 0x300000 Min frequency: 400 KHz Max frequency: 52 MHz Supported bus width: 4 bit 8 bit Supported operating modes: Can do High Speed transfers Supported VCCQ voltages: 3.3V Current settings: Bus width: 8 bit Freq: 52.000 MHz (high-speed timing) VCCQ: 1.2V Same command in the new environment looks a bit strange: # camcontrol mmcsdcmd 2:0:0 -I Host controller information Host OCR: 0x300000 Min frequency: 400 KHz Max frequency: 0 MHz Supported bus width: 4 bit 8 bit Supported operating modes: Can do High Speed transfers Supported VCCQ voltages: 3.3V Current settings: Bus width: 8 bit Freq: 0.000 MHz VCCQ: 1.2V Also, in the old dmesg I see: aw_mmc2: mem 0x1c11000-0x1c11fff irq 12 on simplebus0 aw_mmc2: vmmc-supply regulator found aw_mmc2: Non-removable media aw_mmc2: Clock => 0 aw_mmc2: VDD => 21 aw_mmc2: CS => 0 aw_mmc2: Bus width => 0 aw_mmc2: Power mode => 1 aw_mmc2: Bus mode => 1 aw_mmc2: Powering up sd/mmc aw_mmc2: Clock => 400000 aw_mmc2: Timing => 0 aw_mmc2: CS => 1 aw_mmc2: Bus mode => 2 aw_mmc2: Timing => 1 aw_mmc2: Clock => 52000000 aw_mmc2: Bus width => 3 While in the new: aw_mmc2: mem 0x1c11000-0x1c11fff irq 12 on simplebus0 aw_mmc2: vmmc-supply regulator found aw_mmc2: Non-removable media aw_mmc2: Power mode => 0 aw_mmc2: Powering down sd/mmc aw_mmc2: Clock => 0 aw_mmc2: VDD => 21 aw_mmc2: CS => 0 aw_mmc2: Bus width => 0 aw_mmc2: Power mode => 1 aw_mmc2: Bus mode => 1 aw_mmc2: Powering up sd/mmc aw_mmc2: Clock => 400000 aw_mmc2: Power mode => 2 aw_mmc2: Timing => 0 aw_mmc2: CS => 1 aw_mmc2: Bus mode => 2 aw_mmc2: Clock => 0 aw_mmc2: Bus width => 3 So, at the end of the sequence we have Clock => 0 instead of Clock => 52000000 and Timing => 1 is missing... -- Andriy Gapon