[Kernel-packages] [Bug 1755326] Re: Periodic glitch in sound with Firewire and snd-dice
Please refer to my report in upstream: http://mailman.alsa-project.org/pipermail/alsa-devel/2016-May/107715.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755326 Title: Periodic glitch in sound with Firewire and snd-dice Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: I have a fresh installation of Ubuntu 17.10 with almost nothing extra installed yet besides Bitwig Studio, Cadence and a few other things from the KX Studio repositories. But I also tried the bug after a fresh install with nothing else than Bitwig Studio installed, it's the same. Not sure if this information can be added afterwards: but I installed the 3.19.8 low latency kernel, and the problem disappeared. On 17.1 I can't use the current low latency kernel because the system becomes very unresponsive to the point of being hard to even log in. So I'm not sure if this is just a matter of difference between the low latency and regular kernels. I have a TC Electronics Impact Twin Firewire audio interface. It is connected to a Iocrest SY-PEX30016 PCI-E card, which has a Texas Instruments XIO2213BZAY chipset. The ALSA snd-dice drivers work, but with glitches. There is a periodic, glitch in the sound that sounds like a part of the stream is missing, or something. It is steady in timing, nothing seems to have an effect on it. Recording seems to work. All outputs and inputs, also the ADAT outputs seem to work, altough I could not test if the ADAT outputs feature the glitch too. Seemingly randomly there might be a short maybe around 0.3 second total break in the sound. I'm not getting xruns at all. I tried also Ubuntu Studio live USB, it has the exact same glitch. I also tried a Native Instruments Audio2DJ USB interface, with that there is no problem with the sound on my computer. I tried also with Carla and ZynAddSubFx, and also with the live USB of Linux Mint (current version), and the same glitch is present. I tried also another Firewire controller card with a XIO2200A Texas Instruments chip, it features the same glitch, but running a different speed. I had a KX Studio 14.x installation a few years ago, where the interface was working without a hitch. But then I was running with FFADO. So to me it seems that the kernel integration of snd-dice has some problem with timing with a TC Electronics interface? I could not get FFADO to run with Jack now so I can't say if the FFADO implementation would work. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3.1 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC4D0c: kim3563 F...m jackdbus /dev/snd/pcmC4D0p: kim3563 F...m jackdbus /dev/snd/controlC4: kim3563 F jackdbus CurrentDesktop: ubuntu:GNOME Date: Tue Mar 13 02:11:51 2018 InstallationDate: Installed on 2018-03-12 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 EVO R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2603:bd02/12/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97EVOR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/hwC3D0', '/dev/snd/midiC3D0', '/dev/snd/pcmC3D0c', '/dev/snd/pcmC3D0p', '/dev/snd/controlC3', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/midiC2D0', '/dev/snd/controlC2', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=2446385e-9b65-4ff6-8ca1-9
[Kernel-packages] [Bug 1755326] Re: Periodic glitch in sound with Firewire and snd-dice
Please refer to my report in upstream: http://mailman.alsa-project.org/pipermail/alsa-devel/2016-May/107715.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755326 Title: Periodic glitch in sound with Firewire and snd-dice Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: I have a fresh installation of Ubuntu 17.10 with almost nothing extra installed yet besides Bitwig Studio, Cadence and a few other things from the KX Studio repositories. But I also tried the bug after a fresh install with nothing else than Bitwig Studio installed, it's the same. Not sure if this information can be added afterwards: but I installed the 3.19.8 low latency kernel, and the problem disappeared. On 17.1 I can't use the current low latency kernel because the system becomes very unresponsive to the point of being hard to even log in. So I'm not sure if this is just a matter of difference between the low latency and regular kernels. I have a TC Electronics Impact Twin Firewire audio interface. It is connected to a Iocrest SY-PEX30016 PCI-E card, which has a Texas Instruments XIO2213BZAY chipset. The ALSA snd-dice drivers work, but with glitches. There is a periodic, glitch in the sound that sounds like a part of the stream is missing, or something. It is steady in timing, nothing seems to have an effect on it. Recording seems to work. All outputs and inputs, also the ADAT outputs seem to work, altough I could not test if the ADAT outputs feature the glitch too. Seemingly randomly there might be a short maybe around 0.3 second total break in the sound. I'm not getting xruns at all. I tried also Ubuntu Studio live USB, it has the exact same glitch. I also tried a Native Instruments Audio2DJ USB interface, with that there is no problem with the sound on my computer. I tried also with Carla and ZynAddSubFx, and also with the live USB of Linux Mint (current version), and the same glitch is present. I tried also another Firewire controller card with a XIO2200A Texas Instruments chip, it features the same glitch, but running a different speed. I had a KX Studio 14.x installation a few years ago, where the interface was working without a hitch. But then I was running with FFADO. So to me it seems that the kernel integration of snd-dice has some problem with timing with a TC Electronics interface? I could not get FFADO to run with Jack now so I can't say if the FFADO implementation would work. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3.1 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC4D0c: kim3563 F...m jackdbus /dev/snd/pcmC4D0p: kim3563 F...m jackdbus /dev/snd/controlC4: kim3563 F jackdbus CurrentDesktop: ubuntu:GNOME Date: Tue Mar 13 02:11:51 2018 InstallationDate: Installed on 2018-03-12 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 EVO R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2603:bd02/12/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97EVOR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/hwC3D0', '/dev/snd/midiC3D0', '/dev/snd/pcmC3D0c', '/dev/snd/pcmC3D0p', '/dev/snd/controlC3', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/midiC2D0', '/dev/snd/controlC2', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=2446385e-9b65-4ff6-8ca1-9
[Kernel-packages] [Bug 2043905] Re: VT6307 IEEE1394 card causes reboot loop
Hi, The change for 1394 OHCI driver, aimed at suppressing the unexpected system reboot in AMD Ryzen machine[1], has been merged into Linux kernel v6.7[2]. It has also been applied to the following releases of stable and longterm kernels. * 6.6.11[3] * 6.1.72[4] * 5.15.147[5] * 5.10.208[6] * 5.4.267[7] * 4.19.305[8] * 4.14.336[9] Once the downstream distribution project provides the corresponding kernel packages, you should no longer encounter the unexpected system reboot. Note that the following combination of hardware is not necessarily suitable, depending on your use case: * Any type of AMD Ryzen machine * 1394 OHCI hardware consists of: * Asmedia ASM1083/1085 * VIA VT6306/6307/6308 When working with time-aware protocol, such as audio sample processing, it is advisable to avoid the combination. The change accompanies a functional limitation that the software stack does not provides precise hardware time in this case. If you choose to continue using AMD Ryzen machine, the recommendation is to replace the 1394 OHCI hardware with another one. Conversely, if you choose to continue using the 1394 OHCI hardware, the recommendation is to use the machine provided by vendors other than AMD. Thanks for your report and long patience. [1] https://git.kernel.org/torvalds/linux/c/ac9184fbb847 [2] https://lore.kernel.org/lkml/CAHk-=widprp4xohucsde7e16yzjlyjwra-dk0he1mnfpmf6...@mail.gmail.com/ [3] https://lore.kernel.org/lkml/2024011058-sheep-thrower-d2f8@gregkh/ [4] https://lore.kernel.org/lkml/2024011052-unsightly-bronze-e628@gregkh/ [5] https://lore.kernel.org/lkml/2024011541-defective-scuff-c55e@gregkh/ [6] https://lore.kernel.org/lkml/2024011532-lustiness-hybrid-fc72@gregkh/ [7] https://lore.kernel.org/lkml/2024011519-mating-tag-1f62@gregkh/ [8] https://lore.kernel.org/lkml/2024011508-shakiness-resonant-f15e@gregkh/ [9] https://lore.kernel.org/lkml/2024011046-ecology-tiptoeing-ce50@gregkh/ Thanks Takashi Sakamoto ** Changed in: linux (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2043905 Title: VT6307 IEEE1394 card causes reboot loop Status in Linux: In Progress Status in linux package in Ubuntu: Fix Committed Bug description: used the live USB for Kubuntu and UbuntuStudio 23.10 as well as upgraded to Mantic 6.5.0-10-generic from a Lunar 6.2.0-36 that works... all of the 6.5.0 64 bit kernel versions do a reboot loop prior to the splash screen display. Processor is an AMD Ryzen 5600X, MSI MPG B550 GAMING PLUS Motherboard with 64 gig 3200 ddr4 ram. AMD Radeon RX6600 graphics... latest BIOS firmware is installed, "fwupdmrg refresh --force && fwupdmrg update" in root terminal reports no available updates. in the advanced options of grub I can boot into mantic with the lunar 6.2.0-36 kernel. Cell phone video capture of the bad boot included... Further testing found that a Mantic beta July 3rd build will boot (6.3 kernel) booting to the current live Kubuntu USB with the 6.5.0-9 kernel and removing hardware 1 piece at a time then replacing if the loop occurred found that as soon as a VT6307 PCIe card is removed the 6.5.0-9 and 6.5.0-10 kernels will boot properly. as soon as the card is reinstalled the panic reboot loop starts up again... If there was a log generated from the loop I have been unable to find one in the /var/log directory... I have been unable to get kdump to work... To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2043905/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2043905] Re: VT6307 IEEE1394 card causes reboot loop
Hi Bevil, I'm a maintainer of Linux FireWire subsystem, and I apologize to trouble you. Indeed, we can see unexpected system reboot in the following combination: * Linux kernel version 6.5 or later * Any kind of AMD Ryzen machines * A kind of IEEE 1394 host controller which consists of: ** Asmedia ASM1083 (PCI/PCIe bridge) ** VIA VT6306/6307/6308 (1394 OHCI host controller) You can see my short description about the issue in my PR to Linus for version 6.7 kernel. * https://lore.kernel.org/all/20231105144852.GA165906@workstation.local/ The host controller card brings some kind of hardware trouble to the machine of AMD Ryzen architecture as a result of change added to 1394 OHCI driver (firewire-ohci), while I never figure out the mechanism yet, since the system reboots without any kind of information in console output. I continue to investigate further by every single way I can think of... At present, no workaround found. I confirm that some portion to exclude the above condition enable system work again; e.g. usage of IEEE 1394 host controller with VIA6315 or VIA6305 connected with PCI bus without the bridge chip. Regards -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2043905 Title: VT6307 IEEE1394 card causes reboot loop Status in Linux: In Progress Status in linux package in Ubuntu: New Bug description: used the live USB for Kubuntu and UbuntuStudio 23.10 as well as upgraded to Mantic 6.5.0-10-generic from a Lunar 6.2.0-36 that works... all of the 6.5.0 64 bit kernel versions do a reboot loop prior to the splash screen display. Processor is an AMD Ryzen 5600X, MSI MPG B550 GAMING PLUS Motherboard with 64 gig 3200 ddr4 ram. AMD Radeon RX6600 graphics... latest BIOS firmware is installed, "fwupdmrg refresh --force && fwupdmrg update" in root terminal reports no available updates. in the advanced options of grub I can boot into mantic with the lunar 6.2.0-36 kernel. Cell phone video capture of the bad boot included... Further testing found that a Mantic beta July 3rd build will boot (6.3 kernel) booting to the current live Kubuntu USB with the 6.5.0-9 kernel and removing hardware 1 piece at a time then replacing if the loop occurred found that as soon as a VT6307 PCIe card is removed the 6.5.0-9 and 6.5.0-10 kernels will boot properly. as soon as the card is reinstalled the panic reboot loop starts up again... If there was a log generated from the loop I have been unable to find one in the /var/log directory... I have been unable to get kdump to work... To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2043905/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2043905] Re: VT6307 IEEE1394 card causes reboot loop
Hi Beyil, > I do have an old system (Phenom 1090T CPU) on a motherboard that has a > 1394a controller built in that the 6.5.0-10 kernel works properly on... Indeed. I also own AMD 880G chipset machine with AMD Sempron 145 CPU. It works well even if using the issued version of kernel. Furthermore, VIA VT6307 card without ASM1083 also works well in the machine. > would some sort of system report from that machine help in tracking down > the issue? or even a report from the system with the issue with an > earlier kernel (6.2.0-36) with the card installed?? I know the phenom > is a pre-ryzen so it may be totally missing a CPU command structure that > is possibly effected, and the Lunar kernel which isn't effected may also > be missing something even though the rest of the system is with the up > to date 23.10 build.. would be interesting if somehow could run a 6.5 kernel under the 6.2 kernel to get a log of some sort. Thanks for your suggestion, while the problem occurs due to operations which is not so special, at least, it is not unique instructions supported by AMD Ryzen CPU. The cause is to access to registers by the way of standard PCI express way in some situations. > I have VirtualBox installed but that provides its own "box" and doesn't > really use the current hardware... In the case that we utilize PCI passthrough to bind the issued 1394 OHCI card to guest system, I note that the guest system can bring the system reboot to host system, if the guest system run with v6.5 kernel or later. > also my motherboard has 2 PCIe slots, one connected directly to the > CPU and another connected through the B550 chipset the reboot loop > happens regardless of which slot is used. I mainly use the one through > the B550 chipset to not restrict airflow into the GPU. Indeed. I also experienced that changing PCIe slot is helpless to solve the issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2043905 Title: VT6307 IEEE1394 card causes reboot loop Status in Linux: In Progress Status in linux package in Ubuntu: New Bug description: used the live USB for Kubuntu and UbuntuStudio 23.10 as well as upgraded to Mantic 6.5.0-10-generic from a Lunar 6.2.0-36 that works... all of the 6.5.0 64 bit kernel versions do a reboot loop prior to the splash screen display. Processor is an AMD Ryzen 5600X, MSI MPG B550 GAMING PLUS Motherboard with 64 gig 3200 ddr4 ram. AMD Radeon RX6600 graphics... latest BIOS firmware is installed, "fwupdmrg refresh --force && fwupdmrg update" in root terminal reports no available updates. in the advanced options of grub I can boot into mantic with the lunar 6.2.0-36 kernel. Cell phone video capture of the bad boot included... Further testing found that a Mantic beta July 3rd build will boot (6.3 kernel) booting to the current live Kubuntu USB with the 6.5.0-9 kernel and removing hardware 1 piece at a time then replacing if the loop occurred found that as soon as a VT6307 PCIe card is removed the 6.5.0-9 and 6.5.0-10 kernels will boot properly. as soon as the card is reinstalled the panic reboot loop starts up again... If there was a log generated from the loop I have been unable to find one in the /var/log directory... I have been unable to get kdump to work... To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2043905/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
