Received: by 10.223.185.116 with SMTP id b49csp1110501wrg; Wed, 14 Feb 2018 11:48:37 -0800 (PST) X-Google-Smtp-Source: AH8x2245QqyW33rm9pyGWXvdWnfEiDXyQmpwYpVW/GQWoSGoiL226V0YqxG+XxgnfLUQZBvCEvZh X-Received: by 10.98.60.5 with SMTP id j5mr158230pfa.217.1518637717549; Wed, 14 Feb 2018 11:48:37 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1518637717; cv=none; d=google.com; s=arc-20160816; b=zgXW7Zqxrr/Slp5u2tkRL/PDVSGB+mp0pVPbsc/Z+AnhIjJXvcH20DmjKrCX65OUGi fQCMTZ0kBLs59fHr5H0frS5Qa8P++Nc/o1CWMlHhydV68m9CSiUXdDGRd5mrRfMTEm+V KHuunPg33aGt8lshpLLjhMCElQ5HTeK2MPtXiYyAnygpDfdk8UGEBGCCjUIJeMgrbz91 sSvacs7PW59XTDpw9InadDrHkFKDKzQUBi/6cYy2unD/qD+LAnMMq96aZ1muNXICMHym 0Nte8MV5rOVC1/icmtFJbPobXPfkvnvqUkugTsDyFiNlic5rtAxYUy6f0bz0buFVGETr FuYA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date :arc-authentication-results; bh=8Lz1WkdbEYnTxRY8eTuuhIXybG64cAvYWxZvg2lZgkU=; b=1KFgY6eT17emleakz7zFxX4hkAKnXULJ5iU+6BWtwe38QtSQpmQ44lnBoMMuxhiPUo kLubOczuWkH5Dta9oub23uMt5/xCLNyaotyWibN54vQkZaox84HeLjI1hH73LPMChNhj e9iJm3mjI/1sZQsHUBLmlkg5vFLiHvl0WA6OVGB7yjnPVGu2Ybw+p7MZO6s9fEB8odfi dhWMHwedZXRaxc8gmR6et0EtNZbo3kUZXBBabWCp0lfYosrRcoGp4lVIDhCVH83wfGPE 1KZrA2KelVEXH7pdAku+YYNqJ7CtrFto9vjbJasrgitr9zO7SdJUJhrrt919LKor5oHr FapQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id a3-v6si3963573plc.552.2018.02.14.11.48.22; Wed, 14 Feb 2018 11:48:37 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1163070AbeBNTrl (ORCPT + 99 others); Wed, 14 Feb 2018 14:47:41 -0500 Received: from mx2.suse.de ([195.135.220.15]:56915 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1162873AbeBNTrj (ORCPT ); Wed, 14 Feb 2018 14:47:39 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay1.suse.de (charybdis-ext.suse.de [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 8F21EAC71; Wed, 14 Feb 2018 19:47:36 +0000 (UTC) Date: Wed, 14 Feb 2018 20:47:33 +0100 From: Michal =?UTF-8?B?U3VjaMOhbmVr?= To: Florian Fainelli Cc: Michal Suchanek , Ulf Hansson , Ray Jui , Scott Branden , bcm-kernel-feedback-list@broadcom.com, Eric Anholt , Stefan Wahren , Gerd Hoffmann , "Gustavo A. R. Silva" , Julia Lawall , linux-mmc@vger.kernel.org, linux-rpi-kernel@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 2/2] mmc: bcm2835: print some informational messages during reset Message-ID: <20180214204733.7987d16c@naga.suse.cz> In-Reply-To: References: <97593d6e1a41af1baff61f7d9e6e68a450fc9da6.1518619058.git.msuchanek@suse.de> <97593d6e1a41af1baff61f7d9e6e68a450fc9da6.1518619058.git.msuchanek@suse.de> <57ff1e429a7fc12300a3cca0c5e9a637beed0d3a.1518619058.git.msuchanek@suse.de> X-Mailer: Claws Mail 3.15.1-dirty (GTK+ 2.24.31; x86_64-suse-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 14 Feb 2018 08:50:16 -0800 Florian Fainelli wrote: > On February 14, 2018 6:38:58 AM PST, Michal Suchanek > wrote: > >The previous patch does reset during hardware error so make the reset > >progress more visible. > > Based on your previous email it looks like this can happen quite > frequently so we might be spamming the kernel log with such reset > messages. Turning this into a debug print would not be great either, > how about a custom sysfs attribute counting the number of times a > reset was done? Since every such message happens when the system stalls for like half a minute I don't think there will be that many until somebody notices something is amiss. It might be also helpful in diagnosing if other cards lock up in different way - for me the DMA shutdown is short so I guess it's the mmc host that is locked up and the DMA engine is fine. It might look differently on different systems, though. I understand that adding messages it somewhat controversial so I added them in separate patch. Thanks Michal