From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.2 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 17712C5ACC4 for ; Thu, 20 Feb 2020 01:58:34 +0000 (UTC) Received: from alsa0.perex.cz (alsa0.perex.cz [77.48.224.243]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 9687C24656 for ; Thu, 20 Feb 2020 01:58:33 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=alsa-project.org header.i=@alsa-project.org header.b="lDrXzoX8"; dkim=fail reason="signature verification failed" (2048-bit key) header.d=sakamocchi.jp header.i=@sakamocchi.jp header.b="0cL/kWKS"; dkim=fail reason="signature verification failed" (2048-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b="16cWLyRI" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 9687C24656 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=sakamocchi.jp Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=alsa-devel-bounces@alsa-project.org Received: from alsa1.perex.cz (alsa1.perex.cz [207.180.221.201]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by alsa0.perex.cz (Postfix) with ESMTPS id E91251695; Thu, 20 Feb 2020 02:57:41 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz E91251695 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1582163912; bh=npucFiLOc2vVewoUr95sFdq43BXDV6BqLyy7LdBixaE=; h=Date:From:To:Subject:References:In-Reply-To:Cc:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From; b=lDrXzoX8IEa97fVChtjvuCHYi+j7wWXssXmSS3PzuNaED56X+7UCfLY0vdYmdPxPh osPn01kCtQnalG0cnQW5iuhvnVtm4d/rzkgtOgf0nNUriLSzRWP6C6GvCTAPPDfJy4 +hM5rxmf14x8lR6w+mpdHxshKMq8WfdOltQPkgoU= Received: from alsa1.perex.cz (localhost.localdomain [127.0.0.1]) by alsa1.perex.cz (Postfix) with ESMTP id 7ADE3F801F5; Thu, 20 Feb 2020 02:57:41 +0100 (CET) Received: by alsa1.perex.cz (Postfix, from userid 50401) id 9ECB9F80273; Thu, 20 Feb 2020 02:57:39 +0100 (CET) Received: from wout3-smtp.messagingengine.com (wout3-smtp.messagingengine.com [64.147.123.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by alsa1.perex.cz (Postfix) with ESMTPS id 3F665F801F5 for ; Thu, 20 Feb 2020 02:57:34 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz 3F665F801F5 Authentication-Results: alsa1.perex.cz; dkim=pass (2048-bit key) header.d=sakamocchi.jp header.i=@sakamocchi.jp header.b="0cL/kWKS"; dkim=pass (2048-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b="16cWLyRI" Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id A776F6C7; Wed, 19 Feb 2020 20:57:31 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Wed, 19 Feb 2020 20:57:31 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sakamocchi.jp; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm3; bh=Ug60JBQBRNYbiA/ryIWOlfzVieF t9+a03PW6eV0kNWw=; b=0cL/kWKSBaOM6IiO18PrF7dvNe5EOcqkjq0ExKJUPAH EXNZXdozjEGfKN1F4af7O6a1+s1gY819DCfwUbtr6frLcxN3Zf4SeuuQwWncowmo I5LUQQsWoVxTfIk9wmL30EYJKHDCVBzgo40SwNSXOmaYxyY7zk8g0U+OS9Kw7fsM hP8xG8H3640z5aKfg7lP8ODQ+as24Y1EMaC/HxJnx7Lq4l+04zFQgd2HgtERCYbM /TvFdTb83SlEsYcYbFGsVHKvQFuQlvORvCzQYfCDe9VNOkaDSHoziIf3z+T0QiQF yKokepjJrkVAbW3K/JZoOqgS3d4Z5Kd8CNSERydlnEw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=Ug60JB QBRNYbiA/ryIWOlfzVieFt9+a03PW6eV0kNWw=; b=16cWLyRIplwhbdvkcxUjM4 6DGsZ03J1qOmEMSKyY/GE2o7jBC2rydNGtga76z4Op1iSEl1kO44nYIScxFP6s8J SJcFBhuA1ofz+SKRSXgP7UoRhHtrbKz5BXHEbCCUHIG8crca8pngwhBiOmhIzwSZ qlnhq4zJyHBqub8LEE1Mqd7ECskJ6+zkwQJIFOsK5r/u8Wb24ZfSDkTQgF7WmJO4 btfi+7QckJOc7yYAGy/UKgH1mu5XCGrVd7xQOWxXfwVq33WRmyTQseRjKSG2Ta9s LiiFKI0U8UOjImolh/lwc5nDbNRYM5ReAGXWi8NI8RWgkLEOvM295n19atkKo/nw == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrkedugdegudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpeffhffvuffkfhggtggujggfsehttdertddtredvnecuhfhrohhmpefvrghkrghs hhhiucfurghkrghmohhtohcuoehoqdhtrghkrghshhhisehsrghkrghmohgttghhihdrjh hpqeenucffohhmrghinhepkhgvrhhnvghlrdhorhhgpdhusghunhhtuhdrtghomhenucfk phepudegrdefrdejgedrudeikeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmh epmhgrihhlfhhrohhmpehoqdhtrghkrghshhhisehsrghkrghmohgttghhihdrjhhp X-ME-Proxy: Received: from workstation (ae074168.dynamic.ppp.asahi-net.or.jp [14.3.74.168]) by mail.messagingengine.com (Postfix) with ESMTPA id C499B328005D; Wed, 19 Feb 2020 20:57:29 -0500 (EST) Date: Thu, 20 Feb 2020 10:57:27 +0900 From: Takashi Sakamoto To: Steve Morris Subject: Re: sytem reboots when initializing Edirol FA-101 firewire audio interface Message-ID: <20200220015726.GA3578@workstation> Mail-Followup-To: Steve Morris , alsa-devel@alsa-project.org, iommu@lists.linux-foundation.org, linux1394-devel@lists.sourceforge.net References: <20200219141956.GA14216@buinea.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200219141956.GA14216@buinea.com> User-Agent: Mutt/1.10.1 (2018-07-13) Cc: alsa-devel@alsa-project.org, linux1394-devel@lists.sourceforge.net, iommu@lists.linux-foundation.org X-BeenThere: alsa-devel@alsa-project.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Alsa-devel mailing list for ALSA developers - http://www.alsa-project.org" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: "Alsa-devel" Hi, On Wed, Feb 19, 2020 at 06:19:56AM -0800, Steve Morris wrote: > I'm running Arch Linux x86_64 > > My system consistently reboots when I power on my FA-101 when running > kernels 5.5.1-4. Downgrading to 5.4.15 allows everything to work > properly. > > Here's the outpu of: > journalctl | grep -E 'Reboot|firewire|fw|bebob|alsa|jack' > > This is a good init under 5.4.15: > -- Reboot -- > powered on interface while running 5.4.15, initialized properly > Feb 18 18:35:37 hostname kernel: firewire_ohci 0000:05:00.0: enabling device (0080 -> 0083) > Feb 18 18:35:37 hostname kernel: firewire_ohci 0000:05:00.0: added OHCI v1.10 device as card 0, 4 IR + 8 IT contexts, quirks 0x11 > Feb 18 18:35:37 hostname kernel: firewire_core 0000:05:00.0: created device fw0: GUID 0011223333666677, S400 > Feb 18 18:35:37 hostname systemd-udevd[541]: controlC0: Process '/usr/bin/alsactl restore 0' failed with exit code 99. > Feb 18 18:35:37 hostname systemd-udevd[541]: controlC1: Process '/usr/bin/alsactl restore 1' failed with exit code 99. > Feb 18 18:35:38 hostname kernel: amdgpu: [powerplay] smu driver if version = 0x00000033, smu fw if version = 0x00000035, smu fw version = 0x002a3200 (42.50.0) > Feb 18 18:36:08 hostname kernel: firewire_ohci 0000:05:00.0: isochronous cycle inconsistent > Feb 18 18:36:08 hostname kernel: firewire_core 0000:05:00.0: created device fw1: GUID 0040ab0000c20bc1, S400 > Feb 18 18:36:08 hostname kernel: firewire_core 0000:05:00.0: phy config: new root=ffc1, gap_count=5 > Feb 18 18:36:10 hostname kernel: firewire_core 0000:05:00.0: BM lock failed (timeout), making local node (ffc0) root > Feb 18 18:36:10 hostname kernel: firewire_core 0000:05:00.0: phy config: new root=ffc0, gap_count=5 > Feb 18 18:36:12 hostname systemd-udevd[1532]: controlC2: Process '/usr/bin/alsactl restore 2' failed with exit code 99. > Feb 18 18:36:15 hostname kernel: snd-bebob fw1.0: transaction failed: no ack > Feb 18 18:36:15 hostname kernel: snd-bebob fw1.0: fail to get an input for MSU in plug 7: -5 > Feb 18 18:36:15 hostname kernel: snd-bebob fw1.0: transaction failed: no ack > Feb 18 18:36:15 hostname kernel: snd-bebob fw1.0: fail to get an input for MSU in plug 7: -5 > > This is a bad init under 5.5.4: > -- Reboot -- > Powered on interface when machine was running. > Feb 18 18:13:37 hostname kernel: firewire_ohci 0000:05:00.0: enabling device (0080 -> 0083) > Feb 18 18:13:37 hostname kernel: firewire_ohci 0000:05:00.0: added OHCI v1.10 device as card 0, 4 IR + 8 IT contexts, quirks 0x11 > Feb 18 18:13:37 hostname kernel: firewire_core 0000:05:00.0: created device fw0: GUID 0011223333666677, S400 > Feb 18 18:13:37 hostname kernel: audit: type=1130 audit(1582078417.360:3): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=ufw comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' > Feb 18 18:13:37 hostname audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=ufw comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' > Feb 18 18:13:37 hostname systemd-udevd[539]: controlC0: Process '/usr/bin/alsactl restore 0' failed with exit code 99. > Feb 18 18:13:37 hostname systemd-udevd[530]: controlC1: Process '/usr/bin/alsactl restore 1' failed with exit code 99. > Feb 18 18:13:38 hostname kernel: amdgpu: [powerplay] smu driver if version = 0x00000033, smu fw if version = 0x00000035, smu fw version = 0x002a3200 (42.50.0) > Feb 18 18:19:45 hostname kernel: firewire_core 0000:05:00.0: phy config: new root=ffc1, gap_count=5 > Feb 18 18:19:48 hostname kernel: firewire_core 0000:05:00.0: phy config: new root=ffc1, gap_count=5 > Feb 18 18:19:48 hostname kernel: firewire_core 0000:05:00.0: created device fw1: GUID 0040ab0000c20bc1, S400 > Feb 18 18:19:52 hostname systemd-udevd[1682]: controlC2: Process '/usr/bin/alsactl restore 2' failed with exit code 99. > Feb 18 18:20:08 hostname kernel: snd-bebob fw1.0: transaction failed: no ack > Feb 18 18:20:08 hostname kernel: snd-bebob fw1.0: fail to get an input for MSU in plug 7: -5 > Feb 18 18:20:08 hostname kernel: snd-bebob fw1.0: transaction failed: no ack > Feb 18 18:20:08 hostname kernel: snd-bebob fw1.0: fail to get an input for MSU in plug 7: -5 > Feb 18 18:20:12 hostname kernel: firewire_core 0000:05:00.0: phy config: new root=ffc1, gap_count=5 > Feb 18 18:21:24 hostname kernel: firewire_ohci 0000:05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0001 address=0xd5080000 flags=0x0000] > Followed by 125 more O_PAGE_FAULT and then the reboot, > > I'll be happy to provide additional information if needed. Hm. I think your system rushed into too complicated issue, At least, three software stacks are related to your issue: - ALSA bebob driver(snd-bebob) and helper module(snd-firewire-lib) - Linux firewire core(firewire-core) and 1394 OHCI controller driver (firewire-ohci) - Driver stack for AMD IOMMU >From the log, ALSA bebob driver takes your unit to generate bus reset on IEEE 1394 bus. We can see 1394 OHCI controller handles the bus reset and the corresponding driver takes Linux firewire core to process the event. Your unit's generation of bus reset is responsible for ALSA bebob driver, and this situation is quite similar to what I reported in this patch[1]. However, the system reboot itself is not responsible for ALSA bebob driver since it is just an application of kernel API of Linux firewire application and sound subsystem (ALSA). I don't know exactly yet but something happened between 1394 OHCI controller driver and AMD IOMMU. It's probably that the cause is in more platform-specific domain. I'm sorry not to help you. For developers information, I C.C.ed this issue to iommu@lists.linux-foundation.org and linux1394-devel@lists.sourceforge.net. If you can get some responses from the others, please follow their instruction. But in advance it's better for you to open information about your kernel configuration and hardware, especially for the version of AMD AGESA for your CPU, like: * AMD Ryzen 5 2400G with Radeon Vega Graphics (family: 0x17, model: 0x11, stepping: 0x0) * Gigabyte Technology Co., Ltd. AX370-Gaming 5/AX370-Gaming 5 * BIOS F42b 08/01/2019 (=AGESA 1.0.0.3 ABB, perhaps) * kernel configuration can be retrieved from Ubuntu package repository[2] The above is a sample from my development environment. I think it would be possible to regenerate the issue if you give your kernel configuration, however I'm on vacation till the beginning of March. So I cannot practice it now, sorry. [1] d3eabe939aee ("ALSA: bebob: expand sleep just after breaking connections for protocol version 1") https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/sound/firewire/bebob?id=d3eabe939aee [2] https://packages.ubuntu.com/eoan/kernel/linux-image-5.3.0-40-generic Regards Takashi Sakamoto