All of lore.kernel.org
 help / color / mirror / Atom feed
From: "\"Timo T.Hyrsylä\"" <timo.hyrsyla@cc-systems.com>
To: alsa-devel@alsa-project.org
Subject: Re: Bad page state in process 'rmmod' cs4281
Date: Wed, 18 Mar 2009 11:01:36 +0200	[thread overview]
Message-ID: <49C0B870.9040901@cc-systems.com> (raw)
In-Reply-To: <s5hsklhn0ou.wl%tiwai@suse.de>

On 13.3.2009 13:04, Takashi Iwai wrote:
> At Mon, 09 Mar 2009 12:24:51 +0100,
>  wrote:
>> At Mon, 09 Mar 2009 10:32:02 +0200,
>> Timo T.Hyrsylä wrote:
>>> Trying to make Alsa work on our embedded arm system with ixdp425 and CS4281.
>>>
>>> kernel is 2.6.20.3 and the Alsas (driver+lib+utils) latest 1.0.19
>>>
>>> Other than the two below errors, the system seems to work ok.
>>>
>>> When removing the snd_cs4281 module, dmesg reports multiple errors about 
>>> bad page
>>>
>>> <0>Bad page state in process 'rmmod'
>>> <0>page:c4007300 flags:0x00004000 mapping:00000000 mapcount:0 count:0
>>> <0>Trying to fix it up, but a reboot is needed
>>> <0>Backtrace:
>>> <0>Bad page state in process 'rmmod'
>>> <0>page:c4007320 flags:0x00004000 mapping:00000000 mapcount:0 count:0
>>> <0>Trying to fix it up, but a reboot is needed
>>> <0>Backtrace:
>>>
>>> I've managed to track down the error upto dma_free_coherent.
>>>
>>> snd_pcm_free > snd_pcm_lib_preallocate_free_for_all > 
>>> snd_pcm_lib_preallocate_free > snd_pcm_lib_preallocate_dma_free > 
>>> snd_dma_free_pages > snd_free_dev_pages > dma_free_coherent
>>>
>>>
>>> Another issue, possibly related, is that when running aplay with --mmap 
>>> it will crash with:
>>>
>>> Internal error: Oops: f3 [#1]
>>> PC is at snd_pcm_mmap_data_nopage+0x10c/0x148 [snd_pcm]
>>> LR is at __handle_mm_fault+0x16c/0x8ac
>> This is likely the problem with dma_alloc_coherent() and mmap on
>> a non-coherent architecture.  I have patches for these, but only for
>> recent kernels.  The patches are found in test/dma-fix branch of sound
>> git tree:
>>   git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-2.6.git test/dma-fix
> 
> Alternatively, an easier "fix" would be simply disable mmap support.
> Remove SNDRV_PCM_INFO_MMAP* from snd_pcm_hardware definitions.
> 
> This may disable the conversion plugin usage in the earlier alsa-lib
> versions, though.
> 
> 
> Takashi


Tried to apply the patch changes into my version, but it did not affect 
the unloading 'bad page' problem at all. Instead it did make all play 
attempts (even non MMAP) to crash. (no crash details available since I 
desided to forget about it for now, working on unrelated issues for awhile)

I did disable the MMAP so that player wont crash when requesting MMAP.

System still dumps the bad pages at unload, play and capture seem to 
work OK, not tested extensively thou.

-- 
Timo
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

      parent reply	other threads:[~2009-03-18  9:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-09  8:32 Bad page state in process 'rmmod' cs4281 "Timo T.Hyrsylä"
2009-03-09 11:24 ` Takashi Iwai
     [not found]   ` <s5hsklhn0ou.wl%tiwai@suse.de>
2009-03-18  9:01     ` "Timo T.Hyrsylä" [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49C0B870.9040901@cc-systems.com \
    --to=timo.hyrsyla@cc-systems.com \
    --cc=alsa-devel@alsa-project.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.