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=-3.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no 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 47EFAC48BDF for ; Sun, 13 Jun 2021 06:32:38 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 1E0AB61078 for ; Sun, 13 Jun 2021 06:32:38 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230295AbhFMGc5 (ORCPT ); Sun, 13 Jun 2021 02:32:57 -0400 Received: from mail-ej1-f46.google.com ([209.85.218.46]:44693 "EHLO mail-ej1-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230201AbhFMGc4 (ORCPT ); Sun, 13 Jun 2021 02:32:56 -0400 Received: by mail-ej1-f46.google.com with SMTP id c10so10956768eja.11 for ; Sat, 12 Jun 2021 23:30:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to; bh=nownNaLyh+w2Hh2hW4XMdkpyjXZowhZ5hjX6G051lLE=; b=lwzDq4P822FD7x7i1tDBpyVYCy/giWAHWZxhe3KDt4Og2Ld+UYFPvzQJYbufImNACE MbeMajFChJylYVz2YzhzmJmMZsH5yMaNgMYmNVLfDBsNtKkRtzGaKNp1kU4hqNETa6LK mice6EaId4gnYzYXacc5bAec3HAT03HlN39y0nQw4YxL5/wBc4t/OeKZft/m9BK7d4At 8TRpiRrAUWyFoMYP83wNu19oga0SgH6TzsC0k0cFD0fFbbsZpbZb9gRAUYo+JQNj1W4R zd9vPqZ3/POWxNWhTSJr5vQnXr12VTGp3B06uaGX+t+mYUHgZP3IRXNGr+poq8D6bTtS UU+A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition :content-transfer-encoding:in-reply-to; bh=nownNaLyh+w2Hh2hW4XMdkpyjXZowhZ5hjX6G051lLE=; b=KLBy4H1B2WDgRtUpAIrDeau1J3hoQXFac1fcMkLNqGL8ZCy0cxjXfF9MWoIXkpHPI0 +Bot+z8+NalrPb4YHYjJO1HM17ZAEeCEWhx8wm4CFpuq5a6dn1rVTNns07euNsBBUBmx LQ6+DBC8zD1mRrYNGhqZZeY04j5ysADCX1jGcPGWgPU4LfnAOZDOLFJQUxC85NVVp6x1 TbB18O38u6AA568DJ/FPNP6hdJZt/8nXHFdw69/AWc+TUkSPzS/8bYlJtwcKW2vAuByn Gj7JQO2pVAfJa67SBhUd3UGFWujG7f4kMFXHO4qeIpREPNZPziLJjQdmeQVa+LEiIfYL SUnw== X-Gm-Message-State: AOAM5334ImuXM3mV92X553SdBSjx30JHSLVEmTYMMy8JAPJgxImuYH0z elLiGfamKGStdSAOuSuYwf+5RVZ/4VBF7w== X-Google-Smtp-Source: ABdhPJyCZLvVBZwnmjVV9bW3wGTKBQLXrnDE4vdwzq3ihX/PNWK29zGPP6lAzW4+QKO3OLlfuXpc4Q== X-Received: by 2002:a17:906:4e91:: with SMTP id v17mr10641608eju.119.1623565795327; Sat, 12 Jun 2021 23:29:55 -0700 (PDT) Received: from eldamar (80-218-24-251.dclient.hispeed.ch. [80.218.24.251]) by smtp.gmail.com with ESMTPSA id bh2sm4076028ejb.80.2021.06.12.23.29.53 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 12 Jun 2021 23:29:54 -0700 (PDT) Sender: Salvatore Bonaccorso Date: Sun, 13 Jun 2021 08:29:53 +0200 From: Salvatore Bonaccorso To: =?utf-8?B?5bCP5aSq?= , Jianxiong Gao , Christoph Hellwig , Konrad Rzeszutek Wilk , linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org, Marek Szyprowski , Robin Murphy , xen-devel@lists.xenproject.org Cc: 989778-maintonly@bugs.debian.org Subject: Regression in at least 5.10.y and mainline: Firewire audio interface fails to work properly (when booted under Xen) Message-ID: References: <162352833546.2353.230557992597997974.reportbug@home.kota.moe> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <162352833546.2353.230557992597997974.reportbug@home.kota.moe> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On Sun, Jun 13, 2021 at 06:05:37AM +1000, 小太 wrote: > Package: src:linux > Version: 5.10.40-1 > Severity: normal > Tags: upstream > X-Debbugs-Cc: nospam@kota.moe > > After updating from linux-image-5.10.0-6-amd64, jackd now fails to sync to my > DICE-compatible firewire audio interface (Profire 610), with the following > error messages (full log attached): > > > $ jackd -d firewire -v > > jackdmp 1.9.12 > > ...snip... > > 00301056761: Warning (StreamProcessorManager.cpp)[ 913] alignReceivedStreams: > xrun while aligning streams... > > 00301056793: Error (StreamProcessorManager.cpp)[ 877] syncStartAll: Could not > align streams... > > 00301056829: Fatal (StreamProcessorManager.cpp)[1025] start: Could not > syncStartAll... > > 00301400626: Warning (TimestampedBuffer.cpp)[ 248] calculateRate: (0x1fa5a20) > rate ( 708.18713) more that 10% off nominal (rate= 512.00000, diff= > 5665.497, update_period=8) > > 00301416642: Warning (TimestampedBuffer.cpp)[ 248] calculateRate: (0x1fa5a20) > rate ( 686.49011) more that 10% off nominal (rate= 512.00000, diff= > 5491.921, update_period=8) > > 00301416925: Warning (devicemanager.cpp)[ 925] startStreaming: Failed to > start SPM! > > firewire ERR: Could not start streaming threads > > Cannot start driver > > JackServer::Start() failed with -1 > > 00301424329: Warning (ieee1394service.cpp)[1509] freeIsoChannel: Channel 1 > not registered > > 00301424360: Error (dice_avdevice.cpp)[1440] startstopStreamByIndex: Could > not deallocate iso channel for SP 1 (ARX 0) > > 00301424397: Warning (devicemanager.cpp)[ 959] stopStreamingOnDevice: Could > not stop stream 1 of device 0x1f6e600 > > 00301424406: Warning (devicemanager.cpp)[ 931] startStreaming: Could not stop > streaming on device 0x1f6e600! > > 00301424429: Fatal (ffado.cpp)[ 220] ffado_streaming_start: Could not start > the streaming system > > Failed to start server > > no message buffer overruns > > Additionally, I also tried using the snd-dice driver to expose the audio > interface directly in ALSA. While the interface did appear and was usable > there, all inputs came out of my speakers highly distorted, with channels > bleeding into each other - practically unusable. > > I've reproduced the issue on upstream kernel version v5.13-rc5+ > (ad347abe4a9876b1f65f408ab467137e88f77eb4), and bisected the first bad commit > down to 85a5a6875ca93dc4efbf20df942ba41d27a917e3. > > To double check commit 85a5a6875ca93dc4efbf20df942ba41d27a917e3 was indeed the > issue, I built the latest v5.10 kernel v5.10.43 with the commit reverted, and > indeed the issue went away. > Unfortunately, the reverse patch would not apply to v5.13-rc5+, since it seems > like the file has changed too much. A user in Debian reported the above issue, which was reproducible with 5.13-rc5 and 5.10.y as packaged in Debian and found that 85a5a6875ca9 ("swiotlb: don't modify orig_addr in swiotlb_tbl_sync_single") that introduced the issue. The full bug log is at https://bugs.debian.org/989778 I'm CC'ing as well the xen-devel list, as it appears from https://bugs.debian.org/989778#10 that the issue is only exposed when booting under Xen. Any ideas? Regards, Salvatore