New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 898290 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug

Blocking:
issue 778802



Sign in to add a comment

eve: Headphones plugged into 3.5mm jack not detected reliably

Project Member Reported by kbr@chromium.org, Oct 23

Issue description

Google Chrome	71.0.3578.8 (Official Build) dev (64-bit)
Revision	a2c2b8f674ee3b7372bc87891e04a14a0e51e812-refs/branch-heads/3578@{#14}
Platform	11151.4.0 (Official Build) dev-channel eve

What steps will reproduce the problem?
(1) Plug headphones in to 3.5mm jack
(2) Navigate to site using audio

What is the expected result?

Expect sound to come out the headphones.


What happens instead?

Occasionally, the device (eve, Pixelbook) fails to detect the presence of the headphones, and the sound continues to come out the internal speakers.

Rebooting the device causes the headphones to start being detected again.

This happens after ~1 day of uptime and multiple suspends / resumes, as well as potentially after using and unplugging a headset which includes a microphone. I can't reproduce it on demand.

Are there any system logs I can extract which would help diagnosis of this?

Linking to related  Issue 778802 , which looked more reliably reproducible and which had an associated fix. However, this is happening again intermittently, at least on Dev Channel.

 
Labels: -Pri-2 Pri-1
Happened again just now. This is unacceptably flaky behavior for a consumer product. Who can triage this and tell me what logs to gather to diagnose?

Owner: yuhsuan@chromium.org
Hi kbr@, thanks for filing the bug.
Could you please send a feedback report with alt+shift+i ?
To get proper debug information, the feedback report should be generated at the time while headphone is plugged but not detected.

You can mention the bug number 898290 in the feedback report so we can locate it.

Thanks!
It just happened again and I've submitted feedback via this method, referring to this bug. It seems to happen after multiple suspends/resumes of the laptop. I just rebooted yesterday to fix this issue and it's already happening again.

Cc: dgreid@chromium.org
Components: OS>Kernel>Audio
Labels: M-72
Status: Assigned (was: Untriaged)
I've seen this periodically on eve over the period of many months as well. I've filed a feedback report at https://listnr.corp.google.com/report/85809935389.
Summary: eve: Headphones plugged into 3.5mm jack not detected reliably (was: Headphones plugged into 3.5mm jack not detected reliably)
Unfortunately, there is no suspicious log in #4.
Headphone and mic are not detected.
No error message from rt5663 headset codec.

Based on observation in #3, we setup a test on eve to run
suspend_stress_test
and check audio jack status.
Once the issue is reproduced, we can dump the register map and check whether there is any register not in the right place.

We will see if we can have more solid repro step, and ask for realtek's help for debugging.

Just happened again and submitted another feedback report via alt-shift-i. The machine was rebooted as recently as yesterday, so it should be easy to manually reproduce this - just suspend/resume the machine a few times and try plugging in and unplugging the headphones. (Mine are a headset with integrated microphone.)

I can't reproduce it even if I suspend and resume for more than 1000 times. Do I need to play music when I suspend? Or do you have any other suggestion to trigger it? Thanks.
All I did the last time was use my machine normally, without headphones, for several hours - including several suspends/resumes - and then when I plugged in the headset, it wasn't detected.

Is there any more detailed logging I can provide from my system? Could some daemon process be dying, and would that be evidenced anywhere? Can I probe the state of registers on any chip that controls the audio input?

You can try it to read regmap (Need root permission)

echo 1> /sys/kernel/debug/regmap/i2c-10EC5663\:00/cache_bypass  (do not use cache)
cat /sys/kernel/debug/regmap/i2c-10EC5663\:00/registers


Could you give a pointer to instructions on how exactly to set up my system to be able to run these commands? Enabling developer mode, opening the alternate console, etc.? Thanks.

P.S. I have the Crostini environment installed but obviously these registers aren't exposed to that environment.

Yes, you need to enable developer mode to get root permission.
1. Recovery mode: Esc + Reload held while pressing Power
2. Developer mode: Enter recovery mode and press ctrl+d
But this movement will clean all your data.

After entering developer mode, you can type ctrl+alt+t on browser to open terminal. Then type shell to get shell. Switch root by "sudo -i" or "sudo su". Password is "test0000". Thanks.
Sigh. Is there any way to back up and restore the Crostini environment so I don't have to rebuild this machine from scratch?

Sign in to add a comment