Attempting to Play Audio through sgtl5000 Causes Kernel Panic

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Attempting to Play Audio through sgtl5000 Causes Kernel Panic

Jump to solution
848 Views
alexct
Contributor I

I am running into a wall with this issue and I was hoping maybe someone could offer some insight.  Every time I try to test the audio card with, let’s say the command “aplay somewavefile.wav”, the Kernel Oopses and then Panics with the error message included below.

We are using the freescale sabre kernel (3.0.35-1) in a heavily modified core-x11 image.   The Kernel source has also been patched to include our board file in arch/arm/mach-mx6/ (this is a custom board we designed in house which uses the iMX6Q).  The wireless, bluetooth, hdmi display all work based on our IOMux settings and when the kernel boots up it states that the sgtl5000 is initialized.  Also, I have confirmed that alsamixer shows controls available for the sgtl5000.  When I attempt to instead play audio through the HDMI it doesn’t crash but it doesn’t output anything either.  Furthermore, ldd on aplay and all the libraries it depends on shows that all the needed libraries are found.

Thank you for your consideration.

Kernel Boot sgtl5000 messages:

sgtl5000 0-000a: Failed to get supply 'VDDD': -19

sgtl5000 0-000a: sgtl5000 revision 17

asoc: sgtl5000 <-> imx-ssi.1 mapping ok

  #0: sgtl5000-audio

Kernel Panic:

Unable to handle kernel paging request at virtual address ff9fa002

pgd = bb38c000

[ff9fa002] *pgd=4fe46811, *pte=00000000, *ppte=00000000

Internal error: Oops: 7 [#1] PREEMPT SMP

Entering kdb (current=0xba18cfe0, pid 729) on processor 0 Oops: (null)

due to oops @ 0x80317350

Pid: 729, comm: aplay

CPU: 0 Tainted: G        W (3.0.35-Connecttech-1.0+gbdde708 #66)

PC is at mxc_sdma_handle_channel+0xe4/0x134

LR is at _raw_spin_unlock_irqrestore+0x38/0x58

pc : [<80317350>]    lr : [<805f3c9c>] psr: 60000193

sp : ba10fab0  ip : ba10fa70  fp : ba10facc

r10: 00000000  r9 : 00000000  r8 : 00000114

r7 : 00000001  r6 : 00000001 r5 : 00000003  r4 : bfa88120

r3 : ff9fa000  r2 : ba10fa70  r1 : ff9fa000  r0 : 00000001

Flags: nZCv  IRQs off FIQs on  Mode SVC_32  ISA ARM  Segment user

Control: 10c53c7d  Table: 4b38c04a  DAC: 00000015

[<800458a0>] (show_regs+0x0/0x50) from [<805e9d70>] (kdb_dumpregs+0x38/0x58)

r4:81041d08 r3:00000001

[<805e9d38>] (kdb_dumpregs+0x0/0x58) from [<800d4fe0>] (kdb_main_loop+0x634/0x7d4)

r6:00000004 r5:ba10fa68 r4:00000005 r3:00000000

[<800d49ac>] (kdb_main_loop+0x0/0x7d4) from [<800d78fc>] (kdb_stub+0x1f8/0x45c)

[<800d7704>] (kdb_stub+0x0/0x45c) from [<800cdb14>] (kgdb_cpu_enter+0x400/0x6c8)

[<800cd714>] (kgdb_cpu_enter+0x0/0x6c8) from [<800cdfa0>] (kgdb_handle_exception+0x8c/0x190)

[<800cdf14>] (kgdb_handle_exception+0x0/0x190) from [<8004b614>] (kgdb_notify+0x2c/0x44)

r7:ba10f834 r6:00000000 r5:00000000 r4:20000193

Labels (2)
0 Kudos
1 Solution
548 Views
igorpadykov
NXP Employee
NXP Employee

Hi alexct

regarding "Kernel Boot sgtl5000 messages: sgtl5000 0-000a: Failed to get supply 'VDDD': -19"

it may be useful to check ER1 Internal VDDD regulator does not start up

SGTL5000ER

Also I would recommend to validate hardware with i.MX 6Series Platform SDK .

Best regards

igor

View solution in original post

0 Kudos
2 Replies
549 Views
igorpadykov
NXP Employee
NXP Employee

Hi alexct

regarding "Kernel Boot sgtl5000 messages: sgtl5000 0-000a: Failed to get supply 'VDDD': -19"

it may be useful to check ER1 Internal VDDD regulator does not start up

SGTL5000ER

Also I would recommend to validate hardware with i.MX 6Series Platform SDK .

Best regards

igor

0 Kudos
548 Views
alexct
Contributor I

Thanks, your feedback was right on the mark.  I disabled the internal VDD regulator and no more Kernel-Panic.  I just have to fix a library issue with ALSA (aplay: unable to install hw params) and hopefully then the sound will be good to go.

0 Kudos