From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jon Hunter Subject: Re: [GIT PULL 9/9] ARM: tegra: Default configuration updates for v4.3-rc1 Date: Fri, 11 Sep 2015 12:04:59 +0100 Message-ID: <55F2B55B.5020004@nvidia.com> References: <1439563720-13189-1-git-send-email-thierry.reding@gmail.com> <1439563720-13189-10-git-send-email-thierry.reding@gmail.com> <20150819091358.GA26627@ulmo> <1439977724.4135.90.camel@collabora.co.uk> <20150819103305.GF26627@ulmo> <55F2AF45.5040706@nvidia.com> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <55F2AF45.5040706-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org> Sender: linux-tegra-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Kevin Hilman , Tyler Baker , Thierry Reding Cc: Sjoerd Simons , "arm-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org" , linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Alexandre Courbot , linux-arm-kernel , Stephen Warren , Kevin Hilman , Olof Johansson List-Id: linux-tegra@vger.kernel.org On 11/09/15 11:39, Jon Hunter wrote: > Hi Kevin, > > On 10/09/15 22:29, Kevin Hilman wrote: > > [snip] > >> Since there is no movement on this, and jetson hasn't been boot for >> multi_v7_defconfig for a while[1], I think it's time to undo the >> option causing this problem[2] so that v4.3 will actually boot on the >> jetson. >> >> Unless I hear a good reason otherwise, I'll be posting a patch to >> disable the HDA related options in multi_v7_defconfig. > > So curiosity got the better of this cat, as to why we are not seeing > this ;-) > > The main difference I see between the tegra_defconfig and > multi_v7_defconfig is all the sound drivers are modules (including > this one). > > So trying a quick modprobe of the hda-tegra driver I do see it hang ... > > / # modprobe snd-hda-tegra > [ 625.213864] snd_hda_tegra: Unknown symbol azx_probe_codecs (err 0) > [ 625.220215] snd_hda_tegra: Unknown symbol azx_init_streams (err 0) > [ 625.226480] snd_hda_tegra: Unknown symbol azx_stop_all_streams (err 0) > [ 625.233168] snd_hda_tegra: Unknown symbol azx_bus_init (err 0) > [ 625.239062] snd_hda_tegra: Unknown symbol azx_free_streams (err 0) > [ 625.245314] snd_hda_tegra: Unknown symbol azx_init_chip (err 0) > [ 625.251321] snd_hda_tegra: Unknown symbol snd_hda_set_power_save (err 0) > [ 625.258081] snd_hda_tegra: Unknown symbol azx_stop_chip (err 0) > [ 625.264078] snd_hda_tegra: Unknown symbol azx_codec_configure (err 0) > [ 625.270607] snd_hda_tegra: Unknown symbol azx_interrupt (err 0) > [ 840.117528] INFO: task modprobe:137 blocked for more than 120 seconds. > [ 840.124192] Not tainted 4.2.0-next-20150909-40826-gb799053 #1 > [ 840.130584] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. > [ 840.138540] modprobe D c09ac3a4 0 137 82 0x00000000 > [ 840.145123] [] (__schedule) from [] (schedule+0x34/0x98) > [ 840.152310] [] (schedule) from [] (schedule_preempt_disabled+0xc/0x10) > [ 840.160734] [] (schedule_preempt_disabled) from [] (__mutex_lock_slowpath+0x9c/0x150) > [ 840.170458] [] (__mutex_lock_slowpath) from [] (mutex_lock+0x4c/0x50) > [ 840.178807] [] (mutex_lock) from [] (__driver_attach+0x44/0x90) > [ 840.186627] [] (__driver_attach) from [] (bus_for_each_dev+0x54/0x88) > [ 840.194966] [] (bus_for_each_dev) from [] (bus_add_driver+0xe4/0x1f0) > [ 840.203305] [] (bus_add_driver) from [] (driver_register+0x78/0xf4) > [ 840.211475] [] (driver_register) from [] (do_one_initcall+0x80/0x1d0) > [ 840.219818] [] (do_one_initcall) from [] (do_init_module+0x58/0x354) > [ 840.228081] [] (do_init_module) from [] (load_module+0x17e0/0x1d8c) > [ 840.236258] [] (load_module) from [] (SyS_init_module+0xd8/0x138) > [ 840.244260] [] (SyS_init_module) from [] (ret_fast_syscall+0x0/0x3c) > > Adding some debug it appears to hang on snd-hda-codec-hdmi (the following show > the order in which modules are being loaded) ... > > / # modprobe snd-hda-tegra > [ 22.450276] snd_hda_tegra: err = -2 > [ 22.484535] soundcore: err = 0 > [ 22.488964] snd: err = 0 > [ 22.493242] snd_timer: err = 0 > [ 22.498380] snd_pcm: err = 0 > [ 22.502479] snd_hda_core: err = 0 > [ 22.508337] snd_hda_codec: err = 0 > [ 22.513386] snd_hda_tegra: err = 0 > [ 22.740216] snd_hda_codec_hdmi: err = 0 Ftrace shows a similar thing ... / # cat /debug/tracing/trace # tracer: nop # # entries-in-buffer/entries-written: 8/8 #P:4 # # _-----=> irqs-off # / _----=> need-resched # | / _---=> hardirq/softirq # || / _--=> preempt-depth # ||| / delay # TASK-PID CPU# |||| TIMESTAMP FUNCTION # | | | |||| | | modprobe-110 [000] .... 46.095279: module_load: soundcore modprobe-110 [000] .n.. 46.096443: module_load: snd modprobe-110 [000] .n.. 46.097719: module_load: snd_timer modprobe-110 [000] .... 46.099242: module_load: snd_pcm modprobe-110 [000] .... 46.100231: module_load: snd_hda_core modprobe-110 [000] .... 46.102418: module_load: snd_hda_codec modprobe-110 [000] .... 46.102915: module_load: snd_hda_tegra modprobe-122 [000] .... 46.341224: module_load: snd_hda_codec_hdmi However, would imply that snd-hda-codec-hdmi is loaded ok and the hang occurs afterwards as the trace message is printed once the module has been loaded. Jon