[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux1394-user
Subject:    system reboots when powering on Edirol FA-101 audio interface
From:       Steve Morris <morris () buinea ! com>
Date:       2020-03-09 16:10:22
Message-ID: 20200309161022.GA2557 () buinea ! com
[Download RAW message or body]

Hello,

I am having a problem with recent kernels where the system hangs and
then reboots when I power up my Edirol FA-101 audio interface. This began with kernel
5.5. Kernel versions up until then worked properly.

Here is the suggested system information:

I am running an up to date Arch linux system on a Gigabyte  X570 GAMING
X motherboard with version F11 bios and an AMD Ryzen 7 3800X 8-Core
Processor. The bios has AMD AGESA 1.0.0.4 B.


current kernel is :
Linux 5.5.8-arch1-1 #1 SMP PREEMPT Fri, 06 Mar 2020 00:57:33 +0000 x86_64 GNU/Linux

output of lsmod | grep -e 1394 -e firewire:
firewire_ohci          49152  0
firewire_core          81920  1 firewire_ohci
crc_itu_t              16384  1 firewire_core

libraw1394 is version 2.1.2-2

output of lspci:

00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy \
Host Bridge 00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse \
GPP Bridge 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse \
GPP Bridge 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse \
PCIe Dummy Host Bridge 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] \
Starship/Matisse PCIe Dummy Host Bridge 00:03.1 PCI bridge: Advanced Micro Devices, \
Inc. [AMD] Starship/Matisse GPP Bridge 00:04.0 Host bridge: Advanced Micro Devices, \
Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:05.0 Host bridge: Advanced \
Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:07.0 Host \
bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge \
00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe \
GPP Bridge 0 to bus[E:B] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] \
Starship/Matisse PCIe Dummy Host Bridge 00:08.1 PCI bridge: Advanced Micro Devices, \
Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] 00:08.2 PCI \
bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge \
0 to bus[E:B] 00:08.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse \
Internal PCIe GPP Bridge 0 to bus[E:B] 00:14.0 SMBus: Advanced Micro Devices, Inc. \
[AMD] FCH SMBus Controller (rev 61) 00:14.3 ISA bridge: Advanced Micro Devices, Inc. \
[AMD] FCH LPC Bridge (rev 51) 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] \
Matisse Device 24: Function 0 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] \
Matisse Device 24: Function 1 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] \
Matisse Device 24: Function 2 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] \
Matisse Device 24: Function 3 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] \
Matisse Device 24: Function 4 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] \
Matisse Device 24: Function 5 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] \
Matisse Device 24: Function 6 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] \
Matisse Device 24: Function 7 01:00.0 Non-Volatile memory controller: Realtek \
Semiconductor Co., Ltd. Device 5762 (rev 01) 02:00.0 PCI bridge: Advanced Micro \
Devices, Inc. [AMD] Matisse Switch Upstream 03:03.0 PCI bridge: Advanced Micro \
Devices, Inc. [AMD] Matisse PCIe GPP Bridge 03:04.0 PCI bridge: Advanced Micro \
Devices, Inc. [AMD] Matisse PCIe GPP Bridge 03:08.0 PCI bridge: Advanced Micro \
Devices, Inc. [AMD] Matisse PCIe GPP Bridge 03:09.0 PCI bridge: Advanced Micro \
Devices, Inc. [AMD] Matisse PCIe GPP Bridge 03:0a.0 PCI bridge: Advanced Micro \
Devices, Inc. [AMD] Matisse PCIe GPP Bridge 04:00.0 PCI bridge: ASMedia Technology \
Inc. ASM1083/1085 PCIe to PCI Bridge (rev 04) 05:00.0 FireWire (IEEE 1394): VIA \
Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller (rev 80) 06:00.0 \
Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express \
Gigabit Ethernet Controller (rev 16) 07:00.0 Non-Essential Instrumentation [1300]: \
Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP 07:00.1 USB \
controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller \
07:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host \
Controller 08:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA \
Controller [AHCI mode] (rev 51) 09:00.0 SATA controller: Advanced Micro Devices, Inc. \
[AMD] FCH SATA Controller [AHCI mode] (rev 51) 0a:00.0 PCI bridge: Advanced Micro \
Devices, Inc. [AMD/ATI] Navi 10 XL Upstream Port of PCI Express Switch (rev c1) \
0b:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Downstream Port \
of PCI Express Switch 0c:00.0 VGA compatible controller: Advanced Micro Devices, Inc. \
[AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] (rev c1) 0c:00.1 Audio \
device: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 HDMI Audio 0d:00.0 \
Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] \
Starship/Matisse PCIe Dummy Function 0e:00.0 Non-Essential Instrumentation [1300]: \
Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP 0e:00.1 Encryption \
controller: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic \
Coprocessor PSPCPP 0e:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse \
USB 3.0 Host Controller 0e:00.4 Audio device: Advanced Micro Devices, Inc. [AMD] \
Starship/Matisse HD Audio Controller 0f:00.0 SATA controller: Advanced Micro Devices, \
Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) 10:00.0 SATA controller: Advanced \
Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)


1394 related output of lspci -v:
05:00.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE \
1394 OHCI Controller (re v 80) (prog-if 10 [OHCI])
        Subsystem: VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI \
Controller  Flags: bus master, stepping, medium devsel, latency 32, IRQ 54
        Memory at fc700000 (32-bit, non-prefetchable) [size=2K]
        I/O ports at e000 [size=128]
        Capabilities: [50] Power Management version 2
        Kernel driver in use: firewire_ohci
        Kernel modules: firewire_ohci

dmesg has no relevant information as the system reboots after powering
on the FA-101.  Here is the output of 
grep -E 'Reboot|firewire|fw|bebob|alsa':

-- Reboot --
Mar 09 07:28:29 xxx kernel: firewire_ohci 0000:05:00.0: enabling device (0080 -> \
                0083)
Mar 09 07:28:29 xxx kernel: firewire_ohci 0000:05:00.0: added OHCI v1.10 device as \
                card 0, 4 IR + 8 IT contexts, quirks 0x11
Mar 09 07:28:29 xxx kernel: firewire_core 0000:05:00.0: created device fw0: GUID \
                0011223333666677, S400
Mar 09 07:28:29 xxx systemd-udevd[546]: controlC0: Process '/usr/bin/alsactl restore \
                0' failed with exit code 99.
Mar 09 07:28:29 xxx systemd-udevd[567]: controlC1: Process '/usr/bin/alsactl restore \
                1' failed with exit code 99.
Mar 09 07:28:30 xxx kernel: amdgpu: [powerplay] smu driver if version = 0x00000033, \
                smu fw if version = 0x00000035, smu fw version = 0x002a3200 (42.5
Mar 09 07:57:11 xxx kernel: firewire_ohci 0000:05:00.0: isochronous cycle \
                inconsistent
Mar 09 07:57:12 xxx kernel: firewire_core 0000:05:00.0: created device fw1: GUID \
                0040ab0000c20bc1, S400
Mar 09 07:57:12 xxx kernel: firewire_core 0000:05:00.0: phy config: new root=ffc1, \
                gap_count=5
Mar 09 07:57:14 xxx kernel: firewire_core 0000:05:00.0: BM lock failed (timeout), \
                making local node (ffc0) root
Mar 09 07:57:14 xxx kernel: firewire_core 0000:05:00.0: phy config: new root=ffc0, \
                gap_count=5
Mar 09 07:57:16 xxx systemd-udevd[2323]: controlC2: Process '/usr/bin/alsactl restore \
                2' failed with exit code 99.
-- Reboot --

Here's the same output with Arch kernel 5.4.24-1-lts which initializes properly.

Reboot
Mar 09 07:58:15 xxx kernel: firewire_ohci 0000:05:00.0: enabling device (0080 -> \
                0083)
Mar 09 07:58:15 xxx kernel: firewire_ohci 0000:05:00.0: added OHCI v1.10 device as \
                card 0, 4 IR + 8 IT contexts, quirks 0x11
Mar 09 07:58:15 xxx kernel: firewire_core 0000:05:00.0: created device fw0: GUID \
                0011223333666677, S400
Mar 09 07:58:16 xxx systemd-udevd[527]: controlC0: Process '/usr/bin/alsactl restore \
                0' failed with exit code 99.
Mar 09 07:58:17 xxx systemd-udevd[510]: controlC1: Process '/usr/bin/alsactl restore \
                1' failed with exit code 99.
Mar 09 07:58:17 xxx kernel: amdgpu: [powerplay] smu driver if version = 0x00000033, \
                smu fw if version = 0x00000035, smu fw version = 0x002a3200 (42.50.0)
Mar 09 08:04:37 xxx kernel: firewire_core 0000:05:00.0: phy config: new root=ffc1, \
                gap_count=5
Mar 09 08:04:41 xxx kernel: firewire_core 0000:05:00.0: phy config: new root=ffc1, \
                gap_count=5
Mar 09 08:04:41 xxx kernel: firewire_core 0000:05:00.0: created device fw1: GUID \
                0040ab0000c20bc1, S400
Mar 09 08:04:44 xxx systemd-udevd[1651]: controlC2: Process '/usr/bin/alsactl restore \
                2' failed with exit code 99.
Mar 09 08:04:46 xxx kernel: snd-bebob fw1.0: transaction failed: no ack
Mar 09 08:04:46 xxx kernel: snd-bebob fw1.0: fail to get an input for MSU in plug 7: \
                -5
Mar 09 08:04:46 xxx kernel: snd-bebob fw1.0: transaction failed: no ack
Mar 09 08:04:46 xxx kernel: snd-bebob fw1.0: fail to get an input for MSU in plug 7: \
                -5
Mar 09 08:04:50 xxx kernel: firewire_core 0000:05:00.0: phy config: new root=ffc1, \
gap_count=5


This is relevant dmesg output from properly initialized unit under
kernel 5.4.24:
Mar 9 08:04] firewire_core 0000:05:00.0: phy config: new root=ffc1, gap_count=5
[  +3.467324] firewire_core 0000:05:00.0: phy config: new root=ffc1, gap_count=5
[  +0.065647] firewire_core 0000:05:00.0: created device fw1: GUID 0040ab0000c20bc1, \
S400 [  +5.576497] snd-bebob fw1.0: transaction failed: no ack
[  +0.000005] snd-bebob fw1.0: fail to get an input for MSU in plug 7: -5
[  +0.080014] snd-bebob fw1.0: transaction failed: no ack
[  +0.000006] snd-bebob fw1.0: fail to get an input for MSU in plug 7: -5
[  +3.874852] firewire_core 0000:05:00.0: phy config: new root=ffc1, gap_count=5

Please let me know if I can offer additional information.

Steve


_______________________________________________
mailing list Linux1394-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux1394-user


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic