aplay lets angstrom kernel crash

Hi,
I put alsa-utils-aplay onto the board and started it with no arguments.

The result is a kernel oops.

The kernel in use is:
2.6.25+2.6.26-rc9+r43+git7786cd7a00ae0b18923185789380a88052f4eee7-r43

Error message below:

root@beagleboard:~# Unable to handle kernel NULL pointer dereference at
virtual address 00000000
pgd = c70a4000
[00000000] *pgd=8711a031, *pte=00000000, *ppte=00000000
Internal error: Oops: 17 [#1]
Modules linked in: ipv6
CPU: 0 Not tainted (2.6.26-rc9-omap1 #1)
PC is at __wake_up_common+0x20/0x80
LR is at complete+0x3c/0x48
pc : [<c004c4e4>] lr : [<c004c5e0>] psr: 40000193
sp : c712dbd0 ip : c712dc00 fp : c712dbfc
r10: c03a8e52 r9 : 00000003 r8 : c0429308
r7 : 0000003e r6 : 00000001 r5 : 00000000 r4 : fffffff4
r3 : 00000000 r2 : 00000001 r1 : 00000003 r0 : 00000000
Flags: nZcv IRQs off FIQs on Mode SVC_32 ISA ARM Segment user
Control: 00c5387f Table: 870a4018 DAC: 00000015
Process aplay (pid: 1474, stack limit = 0xc712c2e8)
Stack: (0xc712dbd0 to 0xc712e000)
dbc0: 00000000 40000113 00000000
00000000

[removed stack values for mail]

Backtrace:
[<c004c4c4>] (__wake_up_common+0x0/0x80) from [<c004c5e0>]
(complete+0x3c/0x48)
[<c004c5a4>] (complete+0x0/0x48) from [<c004a728>]
(omap_mcbsp_tx_irq_handler+0x14/0x1c)
r4:c7c9e7e0
[<c004a714>] (omap_mcbsp_tx_irq_handler+0x0/0x1c) from [<c0079bec>]
(handle_IRQ_event+0x3c/0x74)
[<c0079bb0>] (handle_IRQ_event+0x0/0x74) from [<c007b4bc>]
(handle_level_irq+0xd4/0xf0)
r7:c7c9e7e0 r6:00000000 r5:0000003e r4:c0408c64
[<c007b3e8>] (handle_level_irq+0x0/0xf0) from [<c0033048>]
(__exception_text_start+0x48/0x64)
r5:c0408c64 r4:0000003e
[<c0033000>] (__exception_text_start+0x0/0x64) from [<c00336b0>]
(__irq_svc+0x30/0x80)
Exception stack(0xc712dc88 to 0xc712dcd0)
dc80: 00000000 c03feaf0 000000a8 00000000 c0408c64
40000013
dca0: 0000003e c7c9e7e0 00000000 c04292dc c03a8e52 c712dcf4 c712dc98
c712dcd0
dcc0: c003c060 c007a450 60000013 ffffffff

r7:c7c9e7e0 r6:0000003e r5:d8200000 r4:ffffffff
[<c007a2a8>] (setup_irq+0x0/0x200) from [<c007a53c>] (request_irq+0x94/0xbc)
r9:c04292dc r8:00000000 r7:c004a714 r6:00000000 r5:0000003e
r4:c7c9e7e0
[<c007a4a8>] (request_irq+0x0/0xbc) from [<c004b264>]
(omap_mcbsp_request+0xf0/0x1cc)
[<c004b174>] (omap_mcbsp_request+0x0/0x1cc) from [<c025ec08>]
(omap_mcbsp_dai_startup+0x34/0x38)
r8:c0421f90 r7:c7c85700 r6:c0421e88 r5:c70b1000 r4:c0421d58
[<c025ebd4>] (omap_mcbsp_dai_startup+0x0/0x38) from [<c025b2f0>]
(soc_pcm_open+0x50/0x354)
[<c025b2a0>] (soc_pcm_open+0x0/0x354) from [<c023e604>]
(snd_pcm_open_substream+0x5c/0xa4)
[<c023e5a8>] (snd_pcm_open_substream+0x0/0xa4) from [<c023e708>]
(snd_pcm_open+0xbc/0x1bc)
r5:c7c8d000 r4:00000000
[<c023e64c>] (snd_pcm_open+0x0/0x1bc) from [<c023e9e8>]
(snd_pcm_playback_open+0x34/0x38)
r8:c709a580 r7:00000000 r6:c70e4218 r5:c709a580 r4:c709a580
[<c023e9b4>] (snd_pcm_playback_open+0x0/0x38) from [<c0232aa8>]
(snd_open+0xfc/0x18c)
r5:c709a580 r4:c03358d4
[<c02329ac>] (snd_open+0x0/0x18c) from [<c00a39ac>]
(chrdev_open+0x13c/0x15c)
r7:00000000 r6:c70e4218 r5:c7cbd3c0 r4:00000000
[<c00a3870>] (chrdev_open+0x0/0x15c) from [<c009f204>]
(__dentry_open+0x138/0x250)
r8:c7dad280 r7:00000000 r6:c00a3870 r5:c70e4218 r4:c709a580
[<c009f0cc>] (__dentry_open+0x0/0x250) from [<c009f354>]
(nameidata_to_filp+0x38/0x50)
[<c009f31c>] (nameidata_to_filp+0x0/0x50) from [<c00abf98>]
(do_filp_open+0x340/0x6f8)
r4:00000000
[<c00abc58>] (do_filp_open+0x0/0x6f8) from [<c009efcc>]
(do_sys_open+0x58/0xe8)
[<c009ef74>] (do_sys_open+0x0/0xe8) from [<c009f094>] (sys_open+0x24/0x28)
r8:c0033c84 r7:00000005 r6:00000001 r5:400de430 r4:00000000
[<c009f070>] (sys_open+0x0/0x28) from [<c0033b00>]
(ret_fast_syscall+0x0/0x2c)
Code: e5900000 e1a09001 e240400c e1a06002 (e594100c)
Kernel panic - not syncing: Fatal exception in interrupt

Regards
Robert

Robert Schuster wrote:

Hi,
I put alsa-utils-aplay onto the board and started it with no arguments.

The result is a kernel oops.

For kernel issues most probably not related to local Beagle patches I propose to send them to OMAP list [1] CCing Beagle list.

Same for

http://code.google.com/p/beagleboard/issues/detail?id=25

Cheers

Dirk

[1] http://vger.kernel.org/vger-lists.html#linux-omap