Logs can be found here: https://pantheon.corp.google.com/storage/browser/chromiumos-test-logs/bugfiles/cr/734229/

Hi pgangishetty, could you please also provide the audio_diagnostics result ?

I need to compare the log between:

1. Play audio and grab the log by audio_diagnostics > /tmp/bad
2. Unplug and plug headphone (while audio is still playing) and grab the log by audio_diagnostics > /tmp/good

I will request one setzer to debug. But hopefully I can find some controls were setting wrong by comparing the logs.

Thanks!

@cychiang, audio_diagnostics logs have been attached here:

https://pantheon.corp.google.com/storage/browser/chromiumos-test-logs/bugfiles/cr/734229/

Hi Dylan, I guess this might be the same issue you fixed on buddy ?
setzer and buddy both use RT5650.
https://chromium-review.googlesource.com/#/c/538097/


Hi pgangishetty, thank you for the logs.
I compared the controls between good and bad, and they are the same.
So CRAS set the control right but the control did not take effect.
It looks like the same issue on buddy.
So I uploaded a CL https://chromium-review.googlesource.com/540978 to do the same fix.

Could you please test the CL for me ?
You will need to put first remove rootfs verification on the DUT:
# /usr/share/vboot/bin/make_dev_ssd.sh --remove_rootfs_verification --partitions 2
# /usr/share/vboot/bin/make_dev_ssd.sh --remove_rootfs_verification --partitions 4
Then reboot
# reboot

After that, you can place the attached HiFi.conf under
/usr/share/alsa/ucm/chtrt5650/

Then, you can sync and reboot and test audio.

# sync; reboot;

Thanks!

Deleted: HiFi.conf 3.8 KB

HiFi.conf 3.8 KB Download

Sorry, I missed one step in #7.
Before moving the HiFi.conf into /usr/share/alsa/ucm/chtrt5650/, you need to run

# mount -o remount,rw /

to remount rootfs as RW.

If this command fails with

"mount: cannot remount /dev/dm-0 read-write, is write-protected"

That means the remove_rootfs_verification step was not done yet.

Thanks!

1) Tested the CL with the instructions above in comment #7 & #8 and I see no issues now.  Audio can be heard from 3.5mm after reboot. 

2) In the process of reboot, I see few crashes that are copied below and the stack trace:   Not sure if its related. 


0x000076ff8ad92eb2	(libc-2.23.so -raise.c:54 )	raise
0x000076ff8ad94cd5	(libc-2.23.so -abort.c:89 )	abort
0x000076ff8b786b34	(libbase-core-395517.so -debugger_posix.cc:249 )	base::debug::BreakDebugger()
0x000076ff8b79ed4d	(libbase-core-395517.so -logging.cc:755 )	logging::LogMessage::~LogMessage()
0x000059014026b813	(arc-networkd -arc_ip_config.cc:246 )	arc_networkd::ArcIpConfig::Set(in6_addr const&, int, in6_addr const&, std::string const&)
0x000059014026f75e	(arc-networkd -ip_helper.cc:121 )	arc_networkd::IpHelper::HandleCommand()
0x000059014026f3d2	(arc-networkd -ip_helper.cc:66 )	arc_networkd::IpHelper::InitialSetup()
0x000059014026fda7	(arc-networkd -bind_internal.h:186 )	base::internal::Invoker<base::IndexSequence<0ul>, base::internal::BindState<base::internal::RunnableAdapter<void (arc_networkd::IpHelper::*)()>, void (arc_networkd::IpHelper*), base::WeakPtr<arc_networkd::IpHelper> >, base::internal::InvokeHelper<true, void, base::internal::RunnableAdapter<void (arc_networkd::IpHelper::*)()> >, void ()>::Run(base::internal::BindStateBase*)
0x000076ff8b788748	(libbase-core-395517.so -callback.h:397 )	base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask const&)
0x000076ff8b7a529c	(libbase-core-395517.so -message_loop.cc:478 )	base::MessageLoop::RunTask(base::PendingTask const&)
0x000076ff8b7a55ba	(libbase-core-395517.so -message_loop.cc:487 )	base::MessageLoop::DeferOrRunPendingTask(base::PendingTask const&)
0x000076ff8b7a5ab7	(libbase-core-395517.so -message_loop.cc:642 )	base::MessageLoop::DoDelayedWork(base::TimeTicks*)
0x000076ff8b7a80ac	(libbase-core-395517.so -message_pump_libevent.cc:229 )	base::MessagePumpLibevent::Run(base::MessagePump::Delegate*)
0x000076ff8b7cb344	(libbase-core-395517.so -run_loop.cc:35 )	base::RunLoop::Run()
0x000076ff8b8642b5	(libbrillo-core-395517.so -base_message_loop.cc:212 )	brillo::BaseMessageLoop::Run()
0x000076ff8b85cee5	(libbrillo-core-395517.so -daemon.cc:29 )	brillo::Daemon::Run()
0x00005901402704dd	(arc-networkd -main.cc:47 )	main
0x000076ff8ad7f815	(libc-2.23.so -libc-start.c:289 )	__libc_start_main
0x0000590140267bb8	(arc-networkd + 0x00008bb8 )	_start
0x00007ffc67ab3927		
0x0000590140267b8f	(arc-networkd + 0x00008b8f )

2017-06-21T10:06:53.570297-07:00 NOTICE crash_sender[6220]: Crash report receipt ID 03a25aa408000000 
2017-06-21T10:07:04.992298-07:00 NOTICE crash_sender[6331]: Crash report receipt ID dbbe1aa408000000 
2017-06-21T10:08:35.362837-07:00 NOTICE crash_sender[6701]: Crash report receipt ID ce811aa408000000 
2017-06-21T10:09:16.797079-07:00 NOTICE crash_sender[6934]: Crash report receipt ID f484daa408000000 
2017-06-21T10:09:23.242502-07:00 NOTICE crash_sender[7061]: Crash report receipt ID c572eaa408000000 
2017-06-21T11:19:40.515833-07:00 NOTICE crash_sender[4169]: Crash report receipt ID ff2f07a408000000 
2017-06-21T11:19:42.247156-07:00 NOTICE crash_sender[4305]: Crash report receipt ID 4c18fba408000000 
2017-06-21T11:19:44.097599-07:00 NOTICE crash_sender[4440]: Crash report receipt ID eb9b961e40000000
	
 

Hi pgangishetty, thank you for the testing.
Chinyue has posted the CL to fix this on all boards using RT5650 codec.
So we can close this.
The stack trace you posted was not related.
Thanks!