linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-ide@vger.kernel.org
Subject: [Bug 216982] sound hit
Date: Tue, 31 Jan 2023 23:47:40 +0000	[thread overview]
Message-ID: <bug-216982-11633-98NdIsT2rr@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216982-11633@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=216982

--- Comment #1 from damien.lemoal@opensource.wdc.com ---
On 2023/02/01 1:59, bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=216982
> 
>             Bug ID: 216982
>            Summary: sound hit
>            Product: IO/Storage
>            Version: 2.5
>     Kernel Version: 6.1.8
>           Hardware: All
>                 OS: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: normal
>           Priority: P1
>          Component: IDE
>           Assignee: io_ide@kernel-bugs.osdl.org
>           Reporter: kirill-s-0801@yandex.ru
>         Regression: No
> 
> The sound disappeared on the ASUS Vivobook. When I plugged in the headphones,
> the sound disappeared, after removing the headphones, the sound did not work.
> Switched cores, there is no sound. When there should be the intended sound,
> there is a crackling in the headphones. And everything works on the Windows.
> (fedora 37)
> 

Why is this addressed to linux-ide ? This problem has nothing to do with libata
& ata drivers.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2023-01-31 23:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-31 16:59 [Bug 216982] New: sound hit bugzilla-daemon
2023-01-31 23:47 ` Damien Le Moal
2023-01-31 23:47 ` bugzilla-daemon [this message]
2023-02-01 12:21 ` [Bug 216982] " bugzilla-daemon
2023-02-01 14:24 ` bugzilla-daemon
2023-02-01 21:02 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-216982-11633-98NdIsT2rr@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-ide@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).