Bug 902049 - TASCAM US-122L jackd segfault
Summary: TASCAM US-122L jackd segfault
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: alsa-plugins
Version: 18
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Jaroslav Kysela
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-20 16:15 UTC by oleg
Modified: 2014-02-05 15:24 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 15:24:13 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
commands launched and output (2.19 KB, application/octet-stream)
2013-01-20 16:15 UTC, oleg
no flags Details

Description oleg 2013-01-20 16:15:41 UTC
Created attachment 683660 [details]
commands launched and output

Description of problem: 


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. plug TASCAM US-122L usb soundcard
2. start jackd

  
Actual results:
ALSA/USX2Y: mmap: Bad address
ALSA: cannot set hardware parameters for capture
ALSA: cannot configure capture channel
Segmentation fault (core dumped)

segfault at 13 ip 00007f0232694867 sp 00007fff888cc160 error 4 in libasound_module_pcm_usb_stream.so


Expected results: worked well in previous fedora releases


Additional info:  
any help appreciated :)

Oleg.

Comment 1 Antanas 2013-01-21 20:15:52 UTC
I'm getting the same error using TASCAM US-122L after updating archlinux to kernel 3.7.3 


Mon Jan 21 22:10:36 2013: Starting jack server...
Mon Jan 21 22:10:36 2013: JACK server starting in realtime mode with priority 10
Mon Jan 21 22:10:36 2013: Acquired audio card Audio1
Mon Jan 21 22:10:36 2013: creating alsa driver ... usb_stream:US122L|usb_stream:US122L|256|2|48000|0|0|nomon|swmeter|-|32bit
Mon Jan 21 22:10:36 2013: configuring for 48000Hz, period = 256 frames (5.3 ms), buffer = 2 periods
Mon Jan 21 22:10:36 2013: ALSA: final selected sample format for capture: 24bit little-endian
Mon Jan 21 22:10:36 2013: ALSA: use 2 periods for capture
Mon Jan 21 22:10:36 2013: ERROR: ALSA: cannot set hardware parameters for capture
Mon Jan 21 22:10:36 2013: ERROR: ALSA: cannot configure capture channel
Mon Jan 21 22:10:36 2013: ERROR: Segmentation Fault!
Mon Jan 21 22:10:36 2013: ERROR: info.si_signo = 11
Mon Jan 21 22:10:36 2013: ERROR: info.si_errno = 0
Mon Jan 21 22:10:36 2013: ERROR: info.si_code  = 1 (SEGV_MAPERR)
Mon Jan 21 22:10:36 2013: ERROR: info.si_addr  = 0x13
Mon Jan 21 22:10:36 2013: ERROR: reg[00]       = 0x00007f22f80362c0
Mon Jan 21 22:10:36 2013: ERROR: reg[01]       = 0x0000000000000812
Mon Jan 21 22:10:36 2013: ERROR: reg[02]       = 0x00000000000001ff
Mon Jan 21 22:10:36 2013: ERROR: reg[03]       = 0x0000000000000246
Mon Jan 21 22:10:36 2013: ERROR: reg[04]       = 0x0000000000000000
Mon Jan 21 22:10:36 2013: ERROR: reg[05]       = 0x0000000000000002
Mon Jan 21 22:10:36 2013: ERROR: reg[06]       = 0x0000000000000000
Mon Jan 21 22:10:36 2013: ERROR: reg[07]       = 0x0000000001d843e0
Mon Jan 21 22:10:36 2013: ERROR: reg[08]       = 0x0000000001df5200
Mon Jan 21 22:10:36 2013: ERROR: reg[09]       = 0x0000000000000000
Mon Jan 21 22:10:36 2013: ERROR: reg[10]       = 0x0000000001df5b40
Mon Jan 21 22:10:36 2013: ERROR: reg[11]       = 0x0000000001df5140
Mon Jan 21 22:10:36 2013: ERROR: reg[12]       = 0x00007f22f80362e8
Mon Jan 21 22:10:36 2013: ERROR: reg[13]       = 0xffffffffffffffff
Mon Jan 21 22:10:36 2013: ERROR: reg[14]       = 0x0000000001df5200
Mon Jan 21 22:10:36 2013: ERROR: reg[15]       = 0x00007fffdbaa8eb0
Mon Jan 21 22:10:36 2013: ERROR: reg[16]       = 0x00007f22f7e34887
Mon Jan 21 22:10:36 2013: ERROR: reg[17]       = 0x0000000000010286
Mon Jan 21 22:10:36 2013: ERROR: reg[18]       = 0x0000000000000033
Mon Jan 21 22:10:36 2013: ERROR: reg[19]       = 0x0000000000000004
Mon Jan 21 22:10:36 2013: ERROR: reg[20]       = 0x000000000000000e
Mon Jan 21 22:10:36 2013: ERROR: reg[21]       = 0x0000000000005a07
Mon Jan 21 22:10:36 2013: ERROR: reg[22]       = 0x0000000000000013
Mon Jan 21 22:10:36 2013: ERROR: Stack trace:
Mon Jan 21 22:10:36 2013: ERROR:  1: 0x7f22f7e34887 <(null)+4158867591> (/usr/lib/alsa-lib/libasound_module_pcm_usb_stream.so)
Mon Jan 21 22:10:36 2013: ERROR: End of stack trace
Mon Jan 21 22:10:36 2013: ------------------
Mon Jan 21 22:10:36 2013: Controller activated. Version 1.9.9.5 (unknown) built on Mon Dec 10 23:10:29 2012
Mon Jan 21 22:10:36 2013: Loading settings from "/home/antanas/.config/jack/conf.xml" using expat_2.1.0 ...
Mon Jan 21 22:10:36 2013: setting parameter 'engine':'driver':'(null)' to value "alsa"
Mon Jan 21 22:10:36 2013: setting parameter 'engine':'client-timeout':'(null)' to value "500"
Mon Jan 21 22:10:36 2013: setting parameter 'drivers':'alsa':'device' to value "usb_stream:US122L"
Mon Jan 21 22:10:36 2013: setting parameter 'drivers':'alsa':'rate' to value "48000"
Mon Jan 21 22:10:36 2013: setting parameter 'drivers':'alsa':'period' to value "256"
Mon Jan 21 22:10:36 2013: setting parameter 'drivers':'alsa':'dither' to value "s"
Mon Jan 21 22:10:36 2013: Listening for D-Bus messages

Comment 2 Antanas 2013-01-21 20:23:58 UTC
Forgot to say that I'm using this .asoundrc config file:

pcm.!usb_stream {
        @args [ CARD ]
        @args.CARD {
                type string
                default "1"
        }

        type usb_stream

        card $CARD
}

ctl.!usb_stream {
        @args [ CARD ]
        @args.CARD {
                type string
                default "1"
        }

        type hw

        card $CARD
}

Comment 3 oleg 2013-01-21 22:22:15 UTC
good hint :) , I did a fresh install on another workstation and :

- it works with kernel-3.6.10-4.fc18.x86_64  ( FC18 image)
- it fails with kernel-3.7.2.204.fc18.x86_64 ( yum update kernel)

I'll try to downgrade the kernel and see when it works or not...

Comment 4 Antanas 2013-02-18 10:57:18 UTC
ALSA/USX2Y: mmap: Bad address

snd-usb-usx2y module is for Tascam US-122, but newer soundcard version Tascam US-122L used to be using snd-usb-us122l, so maybe this has something to do here?

Comment 5 spraytan 2013-03-24 17:03:06 UTC
Compiled kernnel 3.9-rc2 and tried it with the same result. ALSA/USX2Y: mmap: Bad address Has anyone tried a later kernel? Is it something that can be done about this issue, other than using kernels older than 3.7? What change caused this problem between kernel 3.6 and 3.7? I have used this card with Linux since 2009.

Comment 6 oleg 2013-06-08 14:47:23 UTC
same problem with kernel 3.9.4-300.fc19.x86_64

Comment 7 Fedora End Of Life 2013-12-21 10:36:39 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 8 Fedora End Of Life 2014-02-05 15:24:16 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.