https://github.com/torvalds/linux
Revision 53e1719f3da0f095b8db1461bd12dd79f3246b84 authored by Ondrej Zary on 20 August 2012, 19:50:13 UTC, committed by Takashi Iwai on 21 August 2012, 05:29:40 UTC
snd_card_als100_probe() does not set pcm field in struct snd_sb.
As a result, PCM is not suspended and applications don't know that they need
to resume the playback.

Tested with Labway A381-F20 card (ALS120).

Signed-off-by: Ondrej Zary <linux@rainbow-software.org>
Signed-off-by: Takashi Iwai <tiwai@suse.de>
1 parent 535b6c5
Raw File
Tip revision: 53e1719f3da0f095b8db1461bd12dd79f3246b84 authored by Ondrej Zary on 20 August 2012, 19:50:13 UTC
ALSA: snd-als100: fix suspend/resume
Tip revision: 53e1719
bad_memory.txt
March 2008
Jan-Simon Moeller, dl9pf@gmx.de


How to deal with bad memory e.g. reported by memtest86+ ?
#########################################################

There are three possibilities I know of:

1) Reinsert/swap the memory modules

2) Buy new modules (best!) or try to exchange the memory
   if you have spare-parts

3) Use BadRAM or memmap

This Howto is about number 3) .


BadRAM
######
BadRAM is the actively developed and available as kernel-patch
here:  http://rick.vanrein.org/linux/badram/

For more details see the BadRAM documentation.

memmap
######

memmap is already in the kernel and usable as kernel-parameter at
boot-time.  Its syntax is slightly strange and you may need to
calculate the values by yourself!

Syntax to exclude a memory area (see kernel-parameters.txt for details):
memmap=<size>$<address>

Example: memtest86+ reported here errors at address 0x18691458, 0x18698424 and
         some others. All had 0x1869xxxx in common, so I chose a pattern of
         0x18690000,0xffff0000.

With the numbers of the example above:
memmap=64K$0x18690000
 or
memmap=0x10000$0x18690000

back to top