February 2014 - Alsa-devel - mailman.alsa-project.org

Re: [alsa-devel] linux-next: Tree for Feb 3 (sound/soc/soc-io.c)
by Randy Dunlap 03 Feb '14

03 Feb '14

On 02/02/2014 07:16 PM, Stephen Rothwell wrote: > Hi all, > > This tree fails (more than usual) the powerpc allyesconfig build. > > Changes since 20140131: > on i386: when CONFIG_REGMAP_I2C=m: sound/built-in.o: In function `snd_soc_codec_set_cache_io': (.text+0x29555): undefined reference to `regmap_init_i2c' Full randconfig file is attached. -- ~Randy

1 0

[alsa-devel] compress: adding support for hardware dependent params
by Banajit Goswami 03 Feb '14

03 Feb '14

Hi, We have a requirement, where we need to set a number of hardware specific parameters for compressed offload use-cases, before starting a stream. As these parameters need to be set once for the entire session, we would like to explore the best way to set these additional parameters somewhere before calling trigger() function. Below are few of the proposed solutions that we could think of at this point for getting this done- 1. Adding new IOCTL call: Add a new ioctl control in compress-offload.c file to handle hardware specific parameters setting. This new ioctl control will call into soc-compress.c and eventually call into platform driver ioctl to set those hardware specific parameters. In this case, we will add a new structure, let's say "snd_compr_hw_ctrl_params", with the same fields as "snd_compr_metadata" struct. 2. Adding a function hw_dependant_hw_params(), which will be called after hw_params() and before prepare() function. The new function will eventually call into the platform driver to get the hardware specific parameters set. Once implemented, this would look something like- hw_params(); hw_dependant_hw_params(); prepare(); 3. Add a function "hw_dependant_hw_params()", as _part_ of the hw_params() function. This new function will be called after the (existing) generic parameters are set. So once implemented, the proposed function calls would look like- hw_params() { generic_hw_params(); hw_dependant_hw_params(); } prepare(); We would like to get feedback on these proposed solutions and get a discussion going to see how best these requirements can be fitted in the current Compressed ALSA framework (for mainlining). Thanks and Regards, Banajit Goswami The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation

2 1

[alsa-devel] [PATCH v3 0/6] ASoC: tlv320aic32x4: DT support
by Markus Pargmann 03 Feb '14

03 Feb '14

Hi, The series adds basic DT support for the TI tlv320aic32x4 codec. Patch 3 ("ASoC: tlv320aic32x4: Use signed int mixer controls") depends on series "[PATCH 0/2] ASoC: core: volume control using signed register values". I added the remaining two patches of the "ASoC: tlv320aic32x4 bugfixes" series to the beginning of this series to have all tlv320aic32x4 patches in one series. Regards, Markus Changes in v3: - Rename property gpio-reset to reset-gpios - Use negative constants as minimum volume instead of casting to negative integers Changes in v2: - Regulator support - Fix documentation for gpio property Markus Pargmann (6): ASoC: tlv320aic32x4: Fix mono playback ASoC: tlv320aic32x4: Fix MICPGA input configuration ASoC: tlv320aic32x4: Use signed int mixer controls ASoC: tlv320aic32x4: DT support ASoC: tlv320aic32x4: Support for master clock ASoC: tlv320aic32x4: Support for regulators .../devicetree/bindings/sound/tlv320aic32x4.txt | 28 ++++ sound/soc/codecs/tlv320aic32x4.c | 154 ++++++++++++++++++--- sound/soc/codecs/tlv320aic32x4.h | 3 + 3 files changed, 164 insertions(+), 21 deletions(-) create mode 100644 Documentation/devicetree/bindings/sound/tlv320aic32x4.txt -- 1.8.5.2

3 16

[alsa-devel] [PATCH 0/4] ASoC: davinci-mcasp: Fix master mode capture (w/o playback)
by Peter Ujfalusi 03 Feb '14

03 Feb '14

Hi, When McASP is master the TX clocks are used for capture clocking as well. Other parts of the code already does the configuration for both tx and rx - for different bits in xxFMT/xxFMCT registers we should do the same in other places. Along with this fix I have added three cleanup patch which came along when I was debugging the issue. Regards, Peter --- Peter Ujfalusi (4): ASoC: davinci-mcasp: Harmonize the sub hw_params function names ASoC: davinci-mcasp: Configure xxTDM, xxFMT and xxFMCT registers synchronously ASoC: davinci-mcasp: Return value handling cleanup for mcasp_common_hw_param() ASoC: davinci-mcasp: Code cleanup in davinci_mcasp_hw_params() sound/soc/davinci/davinci-mcasp.c | 81 +++++++++++++++++++-------------------- 1 file changed, 39 insertions(+), 42 deletions(-) -- 1.8.5.3

2 9

Re: [alsa-devel] Got headphone out working via hda-verb setting on MacPro1, 1
by Takashi Iwai 03 Feb '14

03 Feb '14

At Fri, 31 Jan 2014 18:50:11 +0100, Nicolai Beuermann wrote: > > Am 22.01.2014 11:29, schrieb Takashi Iwai: > > At Tue, 21 Jan 2014 01:13:03 +0100, > > Nicolai Beuermann wrote: > >> > >> Hello, > >> hda-analyzer told me to write a note to this list when settings are > >> successful. > >> > >> My setup: > >> MacPro 1,1 > >> Kernel 3.10.17 (gentoo sources) > >> ALSA k3.10.17 > >> > >> Had to set > >> /usr/bin/hda-verb /dev/snd/hwC0D0 0x18 SET_PIN_WIDGET_CONTROL 0xc1 > >> to get the headphone out at the front working. > >> > >> Wrote a bit (in german) about it: > >> http://www.nico-beuermann.de/blogging/archives/117-Hier-gibt-es-was-auf-die… > > > > Could you check whether 3.13 still has the same problem? > > If yes, please give alsa-info.sh output. Better to run it with > > --no-upload and attach the output. > > 3.13 still has the same problem. > alsa-infos's output has been attached. Thanks. Could you try the patch below with 3.14-rc1? 3.13.1 still doesn't contain the fix for MBA 1,1 (which will be merged to stable kernel soon later). Alternatively, you can cherry-pick the commit e7729a415315fcd9516912050d85d5aaebcededc ALSA: hda - Fix silent output on MacBook Air 1,1 from Linus tree, and apply the patch below on its top. Takashi -- 8< -- From: Takashi Iwai <tiwai(a)suse.de> Subject: [PATCH] ALSA: hda - Fix missing VREF setup for Mac Pro 1,1 Mac Pro 1,1 with ALC889A codec needs the VREF setup on NID 0x18 to VREF50, in order to make the speaker working. The same fixup was already needed for MacBook Air 1,1, so we can reuse it. Reported-by: Nicolai Beuermann <mail(a)nico-beuermann.de> Cc: <stable(a)vger.kernel.org> Signed-off-by: Takashi Iwai <tiwai(a)suse.de> --- sound/pci/hda/patch_realtek.c | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c index cbeb67d98852..af7a0c372292 100644 --- a/sound/pci/hda/patch_realtek.c +++ b/sound/pci/hda/patch_realtek.c @@ -1821,6 +1821,7 @@ enum { ALC889_FIXUP_IMAC91_VREF, ALC889_FIXUP_MBA11_VREF, ALC889_FIXUP_MBA21_VREF, + ALC889_FIXUP_MP11_VREF, ALC882_FIXUP_INV_DMIC, ALC882_FIXUP_NO_PRIMARY_HP, ALC887_FIXUP_ASUS_BASS, @@ -2190,6 +2191,12 @@ static const struct hda_fixup alc882_fixups[] = { .chained = true, .chain_id = ALC889_FIXUP_MBP_VREF, }, + [ALC889_FIXUP_MP11_VREF] = { + .type = HDA_FIXUP_FUNC, + .v.func = alc889_fixup_mba11_vref, + .chained = true, + .chain_id = ALC885_FIXUP_MACPRO_GPIO, + }, [ALC882_FIXUP_INV_DMIC] = { .type = HDA_FIXUP_FUNC, .v.func = alc_fixup_inv_dmic_0x12, @@ -2253,7 +2260,7 @@ static const struct snd_pci_quirk alc882_fixup_tbl[] = { SND_PCI_QUIRK(0x106b, 0x00a0, "MacBookPro 3,1", ALC889_FIXUP_MBP_VREF), SND_PCI_QUIRK(0x106b, 0x00a1, "Macbook", ALC889_FIXUP_MBP_VREF), SND_PCI_QUIRK(0x106b, 0x00a4, "MacbookPro 4,1", ALC889_FIXUP_MBP_VREF), - SND_PCI_QUIRK(0x106b, 0x0c00, "Mac Pro", ALC885_FIXUP_MACPRO_GPIO), + SND_PCI_QUIRK(0x106b, 0x0c00, "Mac Pro", ALC889_FIXUP_MP11_VREF), SND_PCI_QUIRK(0x106b, 0x1000, "iMac 24", ALC885_FIXUP_MACPRO_GPIO), SND_PCI_QUIRK(0x106b, 0x2800, "AppleTV", ALC885_FIXUP_MACPRO_GPIO), SND_PCI_QUIRK(0x106b, 0x2c00, "MacbookPro rev3", ALC889_FIXUP_MBP_VREF), -- 1.8.5.2

1 0

[alsa-devel] mentoring for open sound hardware project?
by Hubert Denkmair 03 Feb '14

03 Feb '14

Hello list, I'm currently pushing a project for free audio hardware (basically a digital audio interface / mixer with attached linux system). The details are not final yet, but the design involves a FPGA for audio routing and a ARM SoC board for recording, playback etc. Plan is to support quite a few channels on the linux side, say 20 in, 20 out at 96kHz/24bit. Of course, this needs a Alsa driver. My question is: Is there a "best way" to do the FPGA<->Linux connection? Using the linux GPMC system for communication is the best thing we came up with until now. Are there already drivers doing something alike that we could build upon? Since there is no kernel developer in our team (yet), is someone on this list willing to mentor our driver development? Greetings, Hubert Denkmair

1 0

[alsa-devel] [RFC][PATCH 0/8] A new driver for OXFW970/971 based devices
by Takashi Sakamoto 03 Feb '14

03 Feb '14

This series of patch is based on my previous series below: http://mailman.alsa-project.org/pipermail/alsa-devel/2013-December/070424.h… This series of patch add a new driver, snd-oxfw, for OXFW970/971 based devices. These chipsets are already supported by snd-firewire-speakers but this new driver aim to support recording equipment. Current supported devices: * Behringer F-Control Audio 202 * Mackie Onyx-i series (former model) * Mackie Onyx Satellite Devices possible to be supported if identifying IDs: * Mackie, d.2 pro * Mackie, d.4 pro * Mackie, U.420 * Mackie, U.420d * Mackie, Tapco Link.Firewire I worked with Behringer F-Control Audio 202. So I want someone to test with the other devices, especially about some quirks. Clemens, would you gime me your opinions about issues below? And if you know something about this chipset, would you share the information? 1.snd-firewire-speakers and snd-oxfw With this series of patches, ALSA has two drivers for the same chipsets. Merging these two drivers is a bit difficult because: - snd-firewire-speakers has control interface but snd-oxfw don't - snd-firewire-speakers don't support in-stream but snd-oxfw supports 2.currently snd-oxfw works with streams in SYT-Match Due to invalid sequence of 'presentation timestamp' in transmitted packets. In detail, please see 4th patch. 3.assumption of channnel formation Some commands may not be implemented. In detail, please see 3rd patch. 4.don't check source of clock All of supported devices (including can be) don't have the functionality to switch source of clock. So I want to omit this. For issue 3 and 4, Descriptor mechanism in 'Enhancements to the AV/C General Specification 3.0 Version 1.1' may be a best solution but it costs much to implement against the number of available devices. I want to avoid this huge mechanism if possible. Regards Takashi Sakamoto Takashi Sakamoto (8): oxfw: Add skelton for OXFW970/971 based devices oxfw: Read firmware version to name card oxfw: Add some AV/C commands for channel formation of AMDTP stream oxfw: Add connections and streams management oxfw: Add proc interface for debugging purpose oxfw: Add MIDI interface oxfw: Add PCM interface oxfw: Add hwdep interface include/uapi/sound/asound.h | 3 +- include/uapi/sound/firewire.h | 3 +- sound/firewire/Kconfig | 17 + sound/firewire/Makefile | 1 + sound/firewire/oxfw/Makefile | 3 + sound/firewire/oxfw/oxfw.c | 243 ++++++++++++++ sound/firewire/oxfw/oxfw.h | 140 ++++++++ sound/firewire/oxfw/oxfw_command.c | 161 ++++++++++ sound/firewire/oxfw/oxfw_hwdep.c | 197 ++++++++++++ sound/firewire/oxfw/oxfw_midi.c | 156 +++++++++ sound/firewire/oxfw/oxfw_pcm.c | 421 ++++++++++++++++++++++++ sound/firewire/oxfw/oxfw_proc.c | 61 ++++ sound/firewire/oxfw/oxfw_stream.c | 639 +++++++++++++++++++++++++++++++++++++ 13 files changed, 2043 insertions(+), 2 deletions(-) create mode 100644 sound/firewire/oxfw/Makefile create mode 100644 sound/firewire/oxfw/oxfw.c create mode 100644 sound/firewire/oxfw/oxfw.h create mode 100644 sound/firewire/oxfw/oxfw_command.c create mode 100644 sound/firewire/oxfw/oxfw_hwdep.c create mode 100644 sound/firewire/oxfw/oxfw_midi.c create mode 100644 sound/firewire/oxfw/oxfw_pcm.c create mode 100644 sound/firewire/oxfw/oxfw_proc.c create mode 100644 sound/firewire/oxfw/oxfw_stream.c -- 1.8.3.2

4 37

[alsa-devel] Audio artefacts but no xruns
by Mark Hills 02 Feb '14

02 Feb '14

Hi, I have several applications for realtime processing of audio in/out, using small buffer sizes. I often find that I can get audible time-based distoritions, yet no xrun is reported, and the application is unaware. This problem is something I have, for a long time, taken for granted with ALSA. But it doesn't seem right and I would like to understand what's going on here. I am testing using different USB audio devices; snd-usb-audio and snd-usb-caiaq. Often using plughw or hw. Is this some fundamental limitation of USB, that it is unaware of problems nearer to the hardware? Or is this some bug where it's worth me narrowing down a specific test case and trying to fix it? Or some limitation of the use of intermediate processing like plughw? The effects range from occasional subtle clicks through ringing or noticable gaps in the audio, on record or playback. At very least I would like to guarantee a notification in userland that the integrity of the recording or playback is affected. This is particularly prevalent on, eg. Raspberry Pi. My other tests are on x86 platforms. Thanks -- Mark

1 0

Re: [alsa-devel] [FFADO-devel] Call for testing: ALSA driver for Fireworks/BeBoB based devices
by Maximilian Engelhardt 02 Feb '14

02 Feb '14

On Monday 14 October 2013 12:17:31 Takashi Sakamoto wrote: > Hi all, > > This is a call for testing my ALSA driver for Fireworks/BeBoB based devices. > > Please test 'snd-fireworks' for Fireworks and 'snd-bebob' for BeBoB if > you have some devices listed in the end of this mail. > > Status: > - still under development > - Without snd-dice and Clemens' development (I must do this later) > > Functionality: > - playback/capturing (full duplex) with PCM/MIDI interface > - hardware metering for some devices with CONTROL interface > - switching clock source/digital interface/digital mode with CONTROL > interface > - print hardware status with PROC interface > > Note: > - Don't use simultaneously 'ALSA PCM/MIDI playback/capture' and 'jackd > with Firewire (FFADO) backend'. Both of them try connecting to the > device when another is running. > - I add much modification into snd-firewire-lib for full duplex > synchronization of receive/transmit AMDTP stream. > > Requirement: > - Linux kernel 3.11 or later because of Juju (nickname of Firewire > stack) changing its API. > - Dynamic Kernel Module Support (DKMS) is reccomended for safely > installing/uninstalling > (I work with Ubuntu 13.10) > > Bug report: > - report with /proc/asound/cardX/#XXX > - please send your experiences to me with the output > > How to install (DKMS): > 1. $ git clone https://github.com/takaswie/snd-firewire-improve.git > 2. $ ln -s $(pwd)/snd-firewire-improve/ /usr/src/alsa-firewire-3.11 > (superuser) > 3. $ dkms install snd-firewire/3.11 (superuser) > > How to uninstall (DKMS): > 1. $ modprobe -r snd-bebob snd-fireworks snd-firewire-lib (superuser) > 2. $ dkms remove ans-firewire/3.11 --all (superuser) > 3. $ rm /usr/src/alsa-firewire-3.11 (superuser) > 4. $ rm snd-firewire-improve > > How to install (Manual): > 1. $ git clone https://github.com/takaswie/snd-firewire-improve.git > 2. $ cd snd-firewire-improve > 3. $ make > 4, backup system snd-firewire-lib/snd-firewire-speakers/snd-isight > (superuser) > 5. install > snd-firewire-lib/snd-firewire-speakers/snd-isight/snd-fireworks/snd-bebob > (superuser) 6. depmod -a (superuser) > > How to uninstall (Manual) > 1. modprobe -r snd-firewire-lib snd-firewire-speakers snd-isight > snd-fireworks snd-bebob (superuser) > 2. remove > snd-firewire-lib/snd-firewire-speakers/snd-isight/snd-fireworks/snd-bebob > (superuser) 3. recover snd-firewire-lib/snd-firewire-speakers/snd-isight > (superuser) 4. depmod -a (superuser) > > Confirmed to work: > - AudioFire4 > - AudioFirePre8 > - Ozonic > - Firewire Solo > - Firewire Audiophile > - Firewire 410 > > == Fireworks based devices > [Echo Audio] > AudioFire2 > AudioFire4 > AudioFirePre8 > AudioFire8 (till 2009) > AudioFire8 (since 2009) > AudioFire12 > > [Gibson] > RIP > > [Mackie] > Onyx 400F > Onyx 1200F > > == BeBoB based devices > [Yamaha] > GO44 > GO46 > > [M-Audio] > (to control mixer channels please use FFADO upstream) > Ozonic > Firewire 410 > Firewire Audiophile > Firewire Solo > NRV10 > ProFireLightbridge > > [Focusrite] > SaffirePro 26 I/O > SaffirePro 10 I/O > Saffire(LE) > > [Edirol] > FA-66 > FA-101 > > [TerraTecElectronic GmbH] > Phase88FW > PhaseX24FW > > [PreSonus] > FireBox > FirePod > > [Mackie] > OnyxFirewire > > [Tascam] > IF-FW/DM > > [Behringer] > X32 > > [ApogeeElectronics] > Rosetta200 > > [ESI] > Quatafire610 > > > Regards > > Takashi Sakamoto > o-takashi(a)sakamocchi.jp > > ---------------------------------------------------------------------------- > -- October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most > from the latest Intel processors and coprocessors. See abstracts and > register > > http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk > _______________________________________________ > FFADO-devel mailing list > FFADO-devel(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/ffado-devel Hi Takashi, Today I finally had some time to try your patches. I have a Terratec Phase 24FW Card. I did use the latest version (as of today) from https://github.com/takaswie/snd-firewire-improve.git on a Debian testing system. I did not use dkms but loaded the driver manually: $ cd sound/firewire $ modprobe -r snd-firewire-lib $ insmod ./snd-firewire-lib.ko $ insmod ./bebob/snd-bebob.ko First I have to say the driver does work and I can play music through the device, so thanks for your work. Unfortunately I managed to crash my system with it. I was using mplayer2 to play sound files and it seems that if I let mplayer2 play multiple files the system crashed somewhere between the end of the last file and the start of the new file (probably a race or something). I only did some quick testes because I hat to reboot after every crash (even sysrq doesn't work anymore), but I think the crash doesn't happen every time mplayer2 switches to the next file, but most of the time. If I let it play only one file I didn't observe any crashes. Here is the mplayer2 command I did use for testing: $ mplayer -ao alsa:device=hw=1 <some files> And here the output of /proc/asound/cardX/#XXX $ cat /proc/asound/card1/#clock Sampling rate: 48000 Clock Source: Internal $ cat /proc/asound/card1/#firmware Manufacturer: bridgeCo Protocol Ver: 1 Build Ver: 0 GUID: 0x000AAC04005F9C07 Model ID: 0x04 Model Rev: 1 Firmware Date: 20060420 Firmware Time: 105241 Firmware ID: 0x4 Firmware Ver: 18681119 Base Addr: 0x20080000 Max Size: 1572864 Loader Date: 20040719 Loader Time: 134002 $ cat /proc/asound/card1/#formation Output Stream from device: Rate PCM MIDI 22050 0 0 24000 0 0 32000 4 1 44100 4 1 48000 4 1 88200 4 1 96000 4 1 176400 0 0 192000 4 1 Input Stream to device: Rate PCM MIDI 22050 0 0 24000 0 0 32000 6 1 44100 6 1 48000 6 1 88200 6 1 96000 6 1 176400 0 0 192000 6 1 Attached is the crash log as far as I could obtain it. pulseaudio[4885]: [pulseaudio] module-alsa-card.c: Failed to find a working profile. pulseaudio[4885]: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="1" name="firewire-0x000aac04005f9c07" card_name="alsa_card.firewire-0x000aac04005f9c07" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties="module-udev-detect.discovered=1""): initialization failed. kernel: [ 334.172898] BUG: unable to handle kernel paging request at ffffffffffffffff kernel: [ 334.172934] IP: [<ffffffffa0154670>] fw_iso_context_queue_flush+0x10/0x10 [firewire_core] kernel: [ 334.172977] PGD 180f067 PUD 1811067 PMD 0 kernel: [ 334.172998] Oops: 0000 [#1] SMP kernel: [ 334.173015] Modules linked in: snd_bebob(O) snd_firewire_lib(O) sit ebtable_nat tunnel4 ip_tunnel ebtables cpufreq_stats cpufreq_userspace cpufreq_conservative parport_pc cpufreq_powersave ppdev lp ip6table_raw parport nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables xt_REDIRECT iptable_nat nf_nat_ipv4 nf_nat xt_CT iptable_raw ipt_REJECT xt_LOG xt_limit xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack iptable_filter ip_tables x_tables binfmt_misc deflate ctr twofish_generic twofish_avx_x86_64 twofish_x86_64_3way twofish_x86_64 twofish_common camellia_generic camellia_x86_64 serpent_avx_x86_64 serpent_sse2_x86_64 serpent_generic xts blowfish_generic blowfish_x86_64 blowfish_common cast5_generic cast_common des_generic cbc cmac xcbc rmd160 sha512_generic sha256_generic crypto_null af_key xfrm_algo arc4 ecb md4 hmac nls_utf8 cifs rpcsec_gss_krb5 nfsv4 dns_resolver nfsd auth_rpcgss oid_registry nfs_acl nfs lockd fscache sunrpc w83627ehf hwmon_vid loop fuse ecryptfs isl6423 stv6110x stv090x snd_hda_codec_hdmi snd_hda_codec_realtek iTCO_wdt iTCO_vendor_support stv0299 rc_hauppauge mxm_wmi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 ablk_helper cryptd lrw gf128mul glue_helper psmouse snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_page_alloc snd_seq_midi snd_seq_midi_event pcspkr snd_rawmidi budget budget_ci serio_raw budget_core ttpci_eeprom snd_seq i2c_i801 saa7146 snd_seq_device snd_timer rc_core dvb_core lpc_ich mfd_core snd soundcore evdev i915 drm_kms_helper wmi drm i2c_algo_bit i2c_core video button processor mei_me mei ext4 crc16 mbcache jbd2 btrfs xor raid6_pq crc32c libcrc32c dm_mod raid1 md_mod sg sd_mod sr_mod cdrom crc_t10dif crct10dif_common hid_generic usbhid hid ahci firewire_ohci libahci firewire_core crc_itu_t libata scsi_mod ehci_pci ehci_hcd e1000e xhci_hcd ptp pps_core usbcore usb_common thermal fan thermal_sys kernel: [ 334.173881] CPU: 0 PID: 5343 Comm: mplayer Tainted: G O 3.12-1-amd64 #1 Debian 3.12.6-2 kernel: [ 334.173913] Hardware name: /DZ77BH-55K, BIOS BHZ7710H.86A.0100.2013.0517.0942 05/17/2013 kernel: [ 334.173947] task: ffff88040da7a0c0 ti: ffff8803da2e4000 task.ti: ffff8803da2e4000 kernel: [ 334.173973] RIP: 0010:[<ffffffffa0154670>] [<ffffffffa0154670>] fw_iso_context_queue_flush+0x10/0x10 [firewire_core] kernel: [ 334.174015] RSP: 0018:ffff8803da2e5d70 EFLAGS: 00010002 kernel: [ 334.174035] RAX: ffffffffa0acd040 RBX: ffff8800c99c95c8 RCX: 0000000000001c2c kernel: [ 334.174060] RDX: ffff88040dcff000 RSI: 0000000000000000 RDI: ffffffffffffffff kernel: [ 334.174086] RBP: ffff8803da2e5de8 R08: 0000000000000000 R09: 00000000000031a1 kernel: [ 334.174111] R10: 0000000052ed7c8e R11: 0000000000000246 R12: 00007fffa996f808 kernel: [ 334.174137] R13: 00007fffa996f808 R14: 0000000000000000 R15: ffff8803f70a8c00 kernel: [ 334.174162] FS: 00007f286ae957c0(0000) GS:ffff88041f200000(0000) knlGS:0000000000000000 kernel: [ 334.174190] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 kernel: [ 334.174211] CR2: ffffffffffffffff CR3: 000000040c1d3000 CR4: 00000000001407f0 kernel: [ 334.174236] Stack: kernel: [ 334.174245] ffffffffa0abbca9 ffff8803da3a7000 ffffffffa0569bc4 0000000000000000 kernel: [ 334.174277] 0000000c00000000 0000000081019435 0000000000000097 ffffffffa03e321b kernel: [ 334.174309] ffff8803edca3558 ffff8803edca3530 ffff8803f70a8c00 00007fffa996f808 kernel: [ 334.174340] Call Trace: kernel: [ 334.174352] [<ffffffffa0abbca9>] ? amdtp_stream_pcm_pointer+0x29/0x40 [snd_firewire_lib] kernel: [ 334.174388] [<ffffffffa0569bc4>] ? snd_pcm_update_hw_ptr0+0x34/0x3a0 [snd_pcm] kernel: [ 334.174419] [<ffffffffa03e321b>] ? snd_timer_notify+0x6b/0x150 [snd_timer] kernel: [ 334.174448] [<ffffffffa056363a>] ? snd_pcm_delay+0x5a/0x140 [snd_pcm] kernel: [ 334.174476] [<ffffffffa0565623>] ? snd_pcm_common_ioctl1+0x5f3/0xc90 [snd_pcm] kernel: [ 334.174506] [<ffffffffa056a5f3>] ? snd_pcm_lib_write1+0x3a3/0x3f0 [snd_pcm] kernel: [ 334.174536] [<ffffffffa0567b80>] ? pcm_chmap_ctl_private_free+0x30/0x30 [snd_pcm] kernel: [ 334.174567] [<ffffffffa0565db0>] ? snd_pcm_playback_ioctl1+0xf0/0x240 [snd_pcm] kernel: [ 334.174597] [<ffffffffa0565f26>] ? snd_pcm_playback_ioctl+0x26/0x30 [snd_pcm] kernel: [ 334.174625] [<ffffffff81184d94>] ? do_vfs_ioctl+0x2d4/0x4b0 kernel: [ 334.174648] [<ffffffff81184ff0>] ? SyS_ioctl+0x80/0xa0 kernel: [ 334.174669] [<ffffffff81499b39>] ? system_call_fastpath+0x16/0x1b kernel: [ 334.174691] Code: 00 48 8b 40 60 ff e0 0f 1f 40 00 48 8b 07 48 8b 00 48 8b 40 70 ff e0 0f 1f 40 00 48 8b 07 48 8b 00 48 8b 40 78 ff e0 0f 1f 40 00 <48> 8b 07 48 8b 00 48 8b 80 80 00 00 00 ff e0 90 48 8b 07 48 8b kernel: [ 334.174857] RIP [<ffffffffa0154670>] fw_iso_context_queue_flush+0x10/0x10 [firewire_core] kernel: [ 334.174893] RSP <ffff8803da2e5d70> kernel: [ 334.174906] CR2: ffffffffffffffff kernel: [ 334.184706] ---[ end trace 4fd37a42001c8a5d ]--- kernel: [ 355.198207] INFO: rcu_sched detected stalls on CPUs/tasks: { 0} (detected by 2, t=5252 jiffies, g=3743, c=3742, q=2720) kernel: [ 355.198212] sending NMI to all CPUs: kernel: [ 355.198213] NMI backtrace for cpu 2 kernel: [ 355.198215] CPU: 2 PID: 3929 Comm: collectd Tainted: G D O 3.12-1-amd64 #1 Debian 3.12.6-2 kernel: [ 355.198216] Hardware name: /DZ77BH-55K, BIOS BHZ7710H.86A.0100.2013.0517.0942 05/17/2013 kernel: [ 355.198226] task: ffff88040bcad0c0 ti: ffff88040bf76000 task.ti: ffff88040bf76000 kernel: [ 355.198227] RIP: 0010:[<ffffffff81275bdd>] [<ffffffff81275bdd>] find_next_bit+0x4d/0xd0 kernel: [ 355.198231] RSP: 0018:ffff88041f303df0 EFLAGS: 00000046 kernel: [ 355.198231] RAX: 0000000000000000 RBX: ffff88041f30de00 RCX: 0000000000000001 kernel: [ 355.198232] RDX: ffff88041f30de38 RSI: 0000000000000080 RDI: 0000000000000180 kernel: [ 355.198233] RBP: ffff88041f20de40 R08: ffff88041f30de08 R09: 0000000000000008 kernel: [ 355.198234] R10: 0000000000000000 R11: ffff88041f303bb6 R12: 000000000000de80 kernel: [ 355.198234] R13: 0000000000080000 R14: 0000000000000055 R15: 0000000000000002 kernel: [ 355.198235] FS: 00007f8149847700(0000) GS:ffff88041f300000(0000) knlGS:0000000000000000 kernel: [ 355.198236] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 kernel: [ 355.198237] CR2: 00007f8157da9000 CR3: 000000040d165000 CR4: 00000000001407e0 kernel: [ 355.198238] Stack: kernel: [ 355.198239] ffffffff81043637 0000000000000008 000000000000de40 0000000200000002 kernel: [ 355.198241] 0000000000000082 0000000000002710 ffffffff818419c0 ffffffff818419c0 kernel: [ 355.198242] ffff88040bf76000 0000000000000aa0 ffff88041f30ed80 ffffffff8103f88e kernel: [ 355.198243] Call Trace: kernel: [ 355.198244] <IRQ> kernel: [ 355.198245] [<ffffffff81043637>] ? __x2apic_send_IPI_mask+0xb7/0x190 kernel: [ 355.198251] [<ffffffff8103f88e>] ? arch_trigger_all_cpu_backtrace+0x4e/0x80 kernel: [ 355.198253] [<ffffffff810e1b48>] ? rcu_check_callbacks+0x5b8/0x600 kernel: [ 355.198256] [<ffffffff810b4c30>] ? tick_sched_handle.isra.15+0x60/0x60 kernel: [ 355.198258] [<ffffffff8106881b>] ? update_process_times+0x3b/0x70 kernel: [ 355.198259] [<ffffffff810b4beb>] ? tick_sched_handle.isra.15+0x1b/0x60 kernel: [ 355.198260] [<ffffffff810b4c67>] ? tick_sched_timer+0x37/0x60 kernel: [ 355.198263] [<ffffffff8107ea22>] ? __run_hrtimer+0x62/0x1b0 kernel: [ 355.198264] [<ffffffff8107f1c9>] ? hrtimer_interrupt+0xe9/0x220 kernel: [ 355.198266] [<ffffffff8103deb6>] ? smp_apic_timer_interrupt+0x36/0x50 kernel: [ 355.198269] [<ffffffff8149a71d>] ? apic_timer_interrupt+0x6d/0x80 kernel: [ 355.198269] <EOI> kernel: [ 355.198270] [<ffffffff810ba548>] ? generic_exec_single+0x68/0x90 kernel: [ 355.198273] [<ffffffff810ba564>] ? generic_exec_single+0x84/0x90 kernel: [ 355.198275] [<ffffffff81287cb0>] ? ucs2_strncmp+0x60/0x60 kernel: [ 355.198277] [<ffffffff810ba655>] ? smp_call_function_single+0xe5/0x190 kernel: [ 355.198278] [<ffffffff81287cb0>] ? ucs2_strncmp+0x60/0x60 kernel: [ 355.198280] [<ffffffff81287dd6>] ? rdmsr_on_cpu+0x46/0x60 kernel: [ 355.198295] [<ffffffffa06561f3>] ? show_temp+0x93/0xd0 [coretemp] kernel: [ 355.198298] [<ffffffff81342157>] ? dev_attr_show+0x17/0x50 kernel: [ 355.198300] [<ffffffff811decc9>] ? sysfs_read_file+0x99/0x170 kernel: [ 355.198302] [<ffffffff81172f94>] ? vfs_read+0x94/0x160 kernel: [ 355.198304] [<ffffffff81173a83>] ? SyS_read+0x43/0xa0 kernel: [ 355.198306] [<ffffffff81499b39>] ? system_call_fastpath+0x16/0x1b kernel: [ 355.198306] Code: 3f 75 6b 48 f7 c6 c0 ff ff ff 0f 84 93 00 00 00 49 8b 00 49 8d 50 08 48 85 c0 74 0f eb 3f 48 83 c2 08 48 8b 42 f8 48 85 c0 75 32 <48> 83 ee 40 48 83 c7 40 48 f7 c6 c0 ff ff ff 75 e2 48 85 f6 48 kernel: [ 355.198321] NMI backtrace for cpu 0 kernel: [ 355.198324] CPU: 0 PID: 5343 Comm: mplayer Tainted: G D O 3.12-1-amd64 #1 Debian 3.12.6-2 kernel: [ 355.198324] Hardware name: /DZ77BH-55K, BIOS BHZ7710H.86A.0100.2013.0517.0942 05/17/2013 kernel: [ 355.198325] task: ffff88040da7a0c0 ti: ffff8803da2e4000 task.ti: ffff8803da2e4000 kernel: [ 355.198326] RIP: 0010:[<ffffffff81492083>] [<ffffffff81492083>] _raw_spin_lock+0x23/0x30 kernel: [ 355.198329] RSP: 0018:ffff8803da2e5a30 EFLAGS: 00000097 kernel: [ 355.198330] RAX: 0000000000001c2c RBX: ffff8803f70a8c00 RCX: 0000000000001c2d kernel: [ 355.198331] RDX: 0000000000001c2d RSI: ffff88040b1b5580 RDI: ffff8803f70a8d70 kernel: [ 355.198331] RBP: ffff8803da3a7000 R08: 0000000000000000 R09: 0000000000000000 kernel: [ 355.198332] R10: ffff88040b1b5590 R11: 0000000000000117 R12: ffff88040b1b5580 kernel: [ 355.198333] R13: ffff88040dca7e40 R14: ffff88040b029d98 R15: ffff8803d9156330 kernel: [ 355.198334] FS: 0000000000000000(0000) GS:ffff88041f200000(0000) knlGS:0000000000000000 kernel: [ 355.198335] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 kernel: [ 355.198335] CR2: ffffffffffffffff CR3: 000000000180c000 CR4: 00000000001407f0 kernel: [ 355.198336] Stack: kernel: [ 355.198337] ffffffffa0563cb8 ffff8803f70a8c00 ffff88040b029c00 ffffffffa0563d2a kernel: [ 355.198338] ffff8803f70a8c00 ffff88040b029c00 ffffffffa0563e68 ffff88040b1b5580 kernel: [ 355.198340] 0000000000000008 ffff8803d9156330 ffff8803d3d7e780 ffff88040e6656e0 kernel: [ 355.198341] Call Trace: kernel: [ 355.198351] [<ffffffffa0563cb8>] ? snd_pcm_drop+0x48/0xb0 [snd_pcm] kernel: [ 355.198355] [<ffffffffa0563d2a>] ? snd_pcm_release_substream.part.29+0xa/0x90 [snd_pcm] kernel: [ 355.198359] [<ffffffffa0563e68>] ? snd_pcm_release+0x98/0xb0 [snd_pcm] kernel: [ 355.198361] [<ffffffff81174a9a>] ? __fput+0xca/0x220 kernel: [ 355.198363] [<ffffffff81078904>] ? task_work_run+0xb4/0xd0 kernel: [ 355.198365] [<ffffffff8105d8c3>] ? do_exit+0x2b3/0xa40 kernel: [ 355.198367] [<ffffffff814932b8>] ? oops_end+0x98/0xe0 kernel: [ 355.198369] [<ffffffff81489540>] ? no_context+0x26a/0x276 kernel: [ 355.198371] [<ffffffff81495a0e>] ? __do_page_fault+0x2fe/0x500 kernel: [ 355.198373] [<ffffffff8111abea>] ? __alloc_pages_nodemask+0x14a/0xa30 kernel: [ 355.198376] [<ffffffff81127fcb>] ? shmem_find_get_pages_and_swap.part.18+0xcb/0x120 [some part missing...] Greetings, Maxi

1 0

[alsa-devel] unsubscribe
by animan9＠gmail.com 01 Feb '14

01 Feb '14

unsubscribe Sent from Windows Mail

1 0