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

Issue 901745 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

audio_AudioBasicHeadphone: Unhandled AttributeError: 'NoneType' object has no attribute 'get_audio_bus'

Project Member Reported by yuhsuan@chromium.org, Nov 5

Issue description

These are two different boards
coral - chromeos15-row13a-rack4-host3
daisy - chromeos15-row14a-rack9-host4

We'll check on these test beds and update this bug.
Cc: matthewjoseph@chromium.org pgangishetty@chromium.org sontis@chromium.org
For coral - chromeos15-row13a-rack4-host3 filed lab bug @ http://b/118887792 and unplug, plug the audio cable didn't help.  Only tests passed once on build R72-11228.0.0 and started failing again. 
It seems the problem is between chameleon and audio board. So unplug and plug audio cable between chameleon and DUT might not help. Please check connection in chameleon or just replace the new one. Thanks!

Here is a method to check if chameleon has connected to audio board.
1. Read /var/log/chameleond in chameleon
2. Check whether there are some messages like "INFO Disconnect Cros device headphone as signal source from audio bus 1"
3. If yes, the audio board has connected successfully.

Status: Assigned (was: Untriaged)
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.

Sign in to add a comment