From nobody Wed Jan 10 03:38:17 2024 X-Original-To: freebsd-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 4T8tn36zgyz55WsR for ; Wed, 10 Jan 2024 03:38:31 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ej1-x635.google.com (mail-ej1-x635.google.com [IPv6:2a00:1450:4864:20::635]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4T8tn35DbPz42F7 for ; Wed, 10 Jan 2024 03:38:31 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x635.google.com with SMTP id a640c23a62f3a-a2a17f3217aso398025266b.2 for ; Tue, 09 Jan 2024 19:38:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1704857909; x=1705462709; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=WaVB/wzB9Mxfj0KTLlYVmFZm7kW2gJqpLwDqpXanY2k=; b=frQASToArjm7rhRMkSueitSEqHpuez9kEoDfOAbvQrN5qv/qo7PdWVdcwGWIwJ1idY VtZ7wYxvRJHcxsU1YS7+aKEMj//qX/pS7MEodL1sBkCulEMXcc9eIwkv9fRdzQvA6vCI FqO0iXUY0+1++ud2yZIFFNXzCjiIfRK4GUylp3WtTZ3YROszLP453UrKbU6gJXP65jM2 Clag0qj7StX9mwpYqwMyv0wI6/0e/FOspaPyJXSLZ2G5nsc5t87wARj6+JdPQOCW/Ta/ fxpWvAbcOnWN5UMzcsKbIs5CWWwe6yI4TKK8d7JkgJ+v7dTn8nvRL6EGUFRe9a3LpWff AM/A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1704857909; x=1705462709; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=WaVB/wzB9Mxfj0KTLlYVmFZm7kW2gJqpLwDqpXanY2k=; b=oAym4RTZI3ZG+Ij1kzfehG7IkkHZ2qfktEXxSYoPMV1l3liH6HFOUnN5pU4Wr4aDN+ bkTFsGMLst1xWx/vSGoK0hwpAsaBMrRUiYQGGMFb24A2Qwlq3BiBvL+ArJvg+BM69VRG PQUpq0Nuqi02ZaNH/ZpM9Vy7aUQbBZrlXuZAHybXqDvniu2ctE8nJvHRj2727WPd5pp/ /by9j6bG3Fkdi0TN466hZ9oMwma7i9ixdlVcH2i+Kgai2LDY34deQ8Hw2x42Wv7+0Qnf vu8aEy7u697PN5JnKsOthG5Z6MUor20LXiZ+xO/zXQFDxMvfEo7GFPi85spZFkwLJ65l SHsg== X-Gm-Message-State: AOJu0YwPf+WKZs566LksiJ8zrV+dqWmHgVZa74/Wpkrs8MsPXi3sqJPx cw7Hln9NNQ3mQeihTO1HfIartPQ8Xepp/GZfTQ10cRwt+YB15A== X-Google-Smtp-Source: AGHT+IHN4hKKK0NtBkE8gTlii0c8/PWMLaHFGdVHTglqLVKophEZ930/wPIEDAhLz3qdyVxESH2V1ccNMA99Z6STRPA= X-Received: by 2002:a17:906:a99:b0:a28:220f:4271 with SMTP id y25-20020a1709060a9900b00a28220f4271mr255859ejf.29.1704857908741; Tue, 09 Jan 2024 19:38:28 -0800 (PST) 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 References: <49DE81A1-7DF5-48BF-A334-961A73B91E53@gmail.com> <20240109114822.522d91fea8cf170af4d895b7@bidouilliste.com> <5299p2p7-4r17-7o65-3569-o4pn3pq8r597@yvfgf.mnoonqbm.arg> <084r150q-076r-9rpn-89p2-87osq1p82orp@yvfgf.mnoonqbm.arg> <4759s3r7-4no5-777q-8r01-4192909p2sp4@yvfgf.mnoonqbm.arg> In-Reply-To: <4759s3r7-4no5-777q-8r01-4192909p2sp4@yvfgf.mnoonqbm.arg> From: Warner Losh Date: Tue, 9 Jan 2024 20:38:17 -0700 Message-ID: Subject: Re: MMCCAM hang To: "Bjoern A. Zeeb" Cc: Emmanuel Vadot , =?UTF-8?Q?S=C3=B8ren_Schmidt?= , "freebsd-arm@freebsd.org" Content-Type: multipart/alternative; boundary="0000000000000b1825060e8f2a10" X-Rspamd-Queue-Id: 4T8tn35DbPz42F7 X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_RCPT(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] --0000000000000b1825060e8f2a10 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable That makes sense. The threads you posted showed several blocked on IO while sdhci was resetting. That's going to keep any I/O from happening. I guess I'm not surprised it's the wrong quirks... Many years ago when I was playing with a new, somewhat buggy SDHCI PCIe add-in card having the wrong quirks would cause super weird behavior. In my case, it was an infinite stream of interrupts... You should be able to disable the FreeBSD device like any other FreeBSD device hint.sdhci.0.disabled=3D1 we'll probe the device (which for FDT checks the compat settings) and then never call attach, but instead print a message saying it is disabled. One can also create an overlay that sets its status to something other than okay, but that's quite a bit trickier and can't be done on the fly from the boot loader. Warner On Tue, Jan 9, 2024, 1:57=E2=80=AFPM Bjoern A. Zeeb wrote: > On Tue, 9 Jan 2024, Bjoern A. Zeeb wrote: > > Problem was in sdhci for the specific chipset; wrong quirk/errata > information. > > I'll put a patch up in Phab the next days. > > -- > Bjoern A. Zeeb r15:7 > --0000000000000b1825060e8f2a10 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
That makes sense. The threads you posted= showed several blocked on IO while sdhci was resetting. That's going t= o keep any I/O from happening. I guess I'm not surprised it's the w= rong quirks... Many years ago when I was playing with a new, somewhat buggy= SDHCI PCIe add-in card having the wrong quirks would cause super weird beh= avior. In my case, it was an infinite stream of interrupts...

You should be able to disable the Fre= eBSD device like any other FreeBSD device

=
hint.sdhci.0.disabled=3D1

we'll probe the= device (which for FDT checks the compat settings) and then never call atta= ch, but instead print a message saying it is disabled.

=
One can also create an overlay that sets its status to something other= than okay, but that's quite a bit trickier and can't be done on th= e fly from the boot loader.

Warner
=

= On Tue, Jan 9, 2024, 1:57=E2=80=AFPM Bjoern A. Zeeb <bzeeb-lists@lists.zabbadoz= .net> wrote:
On Tue, 9 Jan 2024, Bjoern A. Zeeb wrote:

Problem was in sdhci for the specific chipset; wrong quirk/errata informati= on.

I'll put a patch up in Phab the next days.

--
Bjoern A. Zeeb=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0r15:7
--0000000000000b1825060e8f2a10--