Bug 580056 - [abrt] crash in lirc-0.8.6-6.fc13 in uirt2_getversion: signal 11 (SIGSEGV)
Summary: [abrt] crash in lirc-0.8.6-6.fc13 in uirt2_getversion: signal 11 (SIGSEGV)
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: lirc
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jarod Wilson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:8ea0069d9b5a764b8882cddb1e2...
: 572843 585796 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-07 11:56 UTC by Martin Ebourne
Modified: 2011-06-27 15:26 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-27 15:26:53 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (4.19 KB, text/plain)
2010-04-07 11:56 UTC, Martin Ebourne
no flags Details

Description Martin Ebourne 2010-04-07 11:56:31 UTC
abrt 1.0.8 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/sbin/lircd --driver=usb_uirt_raw --device=/dev/serial/by-id/usb-FTDI_USB-UIRT-if00-port0
component: lirc
executable: /usr/sbin/lircd
kernel: 2.6.33.1-19.fc13.x86_64
package: lirc-0.8.6-5.fc13
rating: 4
reason: Process /usr/sbin/lircd was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

Comment 1 Martin Ebourne 2010-04-07 11:56:33 UTC
Created attachment 404924 [details]
File: backtrace

Comment 2 Jarod Wilson 2010-04-23 19:42:55 UTC
libftdi was updated recently, with abi changes but no soname bump, resulting in breaking a few other apps that use libftdi. I suspect that's what happened here, and lirc-0.8.6-6.fc13 should remedy the problem, once I actually tell it to build...

Comment 3 Fedora Update System 2010-04-23 19:50:38 UTC
lirc-0.8.6-6.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/lirc-0.8.6-6.fc13

Comment 4 Alex Lancaster 2010-04-25 04:33:42 UTC
(In reply to comment #2)
> libftdi was updated recently, with abi changes but no soname bump, resulting in
> breaking a few other apps that use libftdi. I suspect that's what happened
> here, and lirc-0.8.6-6.fc13 should remedy the problem, once I actually tell it
> to build...    

Also don't forget a build in rawhide/F-14 for a clean upgrade path, currently devel/ branch is 0.8.6-4 < 0.8.6-6 (F-13 branch).

Comment 5 Fedora Update System 2010-04-25 13:57:16 UTC
lirc-0.8.6-6.fc13 has been pushed to the Fedora 13 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update lirc'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/lirc-0.8.6-6.fc13

Comment 6 Martin Ebourne 2010-04-26 04:47:56 UTC
*** Bug 572843 has been marked as a duplicate of this bug. ***

Comment 7 Martin Ebourne 2010-04-26 04:48:38 UTC
*** Bug 585796 has been marked as a duplicate of this bug. ***

Comment 8 Martin Ebourne 2010-04-26 05:07:02 UTC
As per bug 585796 this still happens with
lirc-0.8.6-6.fc13.x86_64
libftdi-0.17-3.fc13.x86_64
kernel-2.6.33.2-57.fc13.x86_64

It's quite reproducable (every time I boot my mytv frontend). When started by /etc/init.d/lirc then lircd fails to open the USB IR device every time. When the lircd command run from that script is started manually by root then it fails the first time and works the second time. Disabling selinux didn't help. This was fine on prior Fedora, breaks on F13.

Relevant lines from syslog showing the three start attempts. Note there is also a kerneloops (reported) on boot that might be part of the problem.

Apr 26 13:34:30 gliadin kernel: usb 1-1.4: new full speed USB device using ehci_hcd and address 5
Apr 26 13:34:30 gliadin kernel: usb 1-1.4: New USB device found, idVendor=0403, idProduct=f850
Apr 26 13:34:30 gliadin kernel: usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Apr 26 13:34:30 gliadin kernel: usb 1-1.4: Product: USB-UIRT
Apr 26 13:34:30 gliadin kernel: usb 1-1.4: Manufacturer: FTDI
Apr 26 13:34:30 gliadin kernel: USB Serial support registered for FTDI USB Serial Device
Apr 26 13:34:30 gliadin kernel: ftdi_sio 1-1.4:1.0: FTDI USB Serial Device converter detected
Apr 26 13:34:30 gliadin kernel: usb 1-1.4: Detected FT232BM
Apr 26 13:34:30 gliadin kernel: usb 1-1.4: Number of endpoints 2
Apr 26 13:34:30 gliadin kernel: usb 1-1.4: Endpoint 1 MaxPacketSize 64
Apr 26 13:34:30 gliadin kernel: usb 1-1.4: Endpoint 2 MaxPacketSize 64
Apr 26 13:34:30 gliadin kernel: usb 1-1.4: Setting MaxPacketSize 64
Apr 26 13:34:30 gliadin kernel: ------------[ cut here ]------------
Apr 26 13:34:30 gliadin kernel: WARNING: at lib/dma-debug.c:866 check_for_stack+0x9a/0xc3()
Apr 26 13:34:30 gliadin kernel: Hardware name: TA780G M2+
Apr 26 13:34:30 gliadin kernel: ehci_hcd 0000:00:12.2: DMA-API: device driver maps memory fromstack [addr=ffff8801191a99d6]
Apr 26 13:34:30 gliadin kernel: Modules linked in: ftdi_sio(+) snd_rawmidi ch341 snd_seq_device usbserial microcode shpchp snd i2c_piix4 k8temp hwmon soundcore edac_mce_amd nbd ata_generic pata_acpi pata_atiixp r8169 mii radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core [last unloaded: scsi_wait_scan]
Apr 26 13:34:30 gliadin kernel: Pid: 700, comm: modprobe Not tainted 2.6.33.2-57.fc13.x86_64 #1
Apr 26 13:34:30 gliadin kernel: Call Trace:
Apr 26 13:34:30 gliadin kernel: [<ffffffff8105134c>] warn_slowpath_common+0x7c/0x94
Apr 26 13:34:30 gliadin kernel: [<ffffffff810513bb>] warn_slowpath_fmt+0x41/0x43
Apr 26 13:34:30 gliadin kernel: [<ffffffff8123d80c>] check_for_stack+0x9a/0xc3
Apr 26 13:34:30 gliadin kernel: [<ffffffff8123e49e>] debug_dma_map_page+0xfd/0x126
Apr 26 13:34:30 gliadin kernel: [<ffffffff8134958a>] dma_map_single_attrs.clone.2+0xbc/0xcf
Apr 26 13:34:30 gliadin kernel: [<ffffffff81349716>] usb_hcd_submit_urb+0x179/0x935
Apr 26 13:34:30 gliadin kernel: [<ffffffff8107e1c8>] ? trace_hardirqs_on_caller+0x111/0x135
Apr 26 13:34:30 gliadin kernel: [<ffffffff8134a5f0>] usb_submit_urb+0x26f/0x2ec
Apr 26 13:34:30 gliadin kernel: [<ffffffff8106cdac>] ? __init_waitqueue_head+0x3a/0x4e
Apr 26 13:34:30 gliadin kernel: [<ffffffff8134b68f>] usb_start_wait_urb+0x71/0x1d4
Apr 26 13:34:30 gliadin kernel: [<ffffffff81113a6e>] ? __kmalloc+0x14b/0x193
Apr 26 13:34:30 gliadin kernel: [<ffffffff8134aa40>] ? usb_alloc_urb+0x1e/0x46
Apr 26 13:34:30 gliadin kernel: [<ffffffff8134ba29>] usb_control_msg+0xf2/0x116
Apr 26 13:34:30 gliadin kernel: [<ffffffffa01a6c96>] ftdi_sio_port_probe+0x53c/0x60e [ftdi_sio]
Apr 26 13:34:30 gliadin kernel: [<ffffffff81478d8c>] ? mutex_unlock+0xe/0x10
Apr 26 13:34:30 gliadin kernel: [<ffffffffa017a7d6>] usb_serial_device_probe+0x58/0xf5 [usbserial]
Apr 26 13:34:30 gliadin kernel: [<ffffffff812eeb93>] ? driver_sysfs_add+0x4c/0x71
Apr 26 13:34:30 gliadin kernel: [<ffffffff812eed6b>] driver_probe_device+0xed/0x21a
Apr 26 13:34:30 gliadin kernel: [<ffffffff812eef53>] __device_attach+0x3a/0x3f
Apr 26 13:34:30 gliadin kernel: [<ffffffff812eef19>] ? __device_attach+0x0/0x3f
Apr 26 13:34:30 gliadin kernel: [<ffffffff812ede5f>] bus_for_each_drv+0x59/0x90
Apr 26 13:34:30 gliadin kernel: [<ffffffff812eeff3>] device_attach+0x6c/0x90
Apr 26 13:34:30 gliadin kernel: [<ffffffff812edc73>] bus_probe_device+0x27/0x3e
Apr 26 13:34:30 gliadin kernel: [<ffffffff812ec2c0>] device_add+0x3c2/0x59e
Apr 26 13:34:30 gliadin kernel: [<ffffffffa01794d5>] usb_serial_probe+0x1022/0x10d5 [usbserial]
Apr 26 13:34:30 gliadin kernel: [<ffffffff8107ca78>] ? trace_hardirqs_off+0xd/0xf
Apr 26 13:34:30 gliadin kernel: [<ffffffff81072258>] ? cpu_clock+0x43/0x5e
Apr 26 13:34:30 gliadin kernel: [<ffffffff8134da39>] ? usb_autopm_do_device+0x2e/0xde
Apr 26 13:34:30 gliadin kernel: [<ffffffff8107caae>] ? lock_release_holdtime+0x34/0xe3
Apr 26 13:34:30 gliadin kernel: [<ffffffff81478d6c>] ? __mutex_unlock_slowpath+0x120/0x132
Apr 26 13:34:30 gliadin kernel: [<ffffffff8107e1c8>] ? trace_hardirqs_on_caller+0x111/0x135
Apr 26 13:34:30 gliadin kernel: [<ffffffff8107e1f9>] ? trace_hardirqs_on+0xd/0xf
Apr 26 13:34:30 gliadin kernel: [<ffffffff81478d8c>] ? mutex_unlock+0xe/0x10
Apr 26 13:34:30 gliadin kernel: [<ffffffff8134dadb>] ? usb_autopm_do_device+0xd0/0xde
Apr 26 13:34:30 gliadin kernel: [<ffffffff8134e646>] usb_probe_interface+0x155/0x20d
Apr 26 13:34:30 gliadin kernel: [<ffffffff812eed6b>] driver_probe_device+0xed/0x21a
Apr 26 13:34:30 gliadin kernel: [<ffffffff812eeef5>] __driver_attach+0x5d/0x81
Apr 26 13:34:30 gliadin kernel: [<ffffffff812eee98>] ? __driver_attach+0x0/0x81
Apr 26 13:34:30 gliadin kernel: [<ffffffff812ee14f>] bus_for_each_dev+0x59/0x8e
Apr 26 13:34:30 gliadin kernel: [<ffffffff812eeaf2>] driver_attach+0x1e/0x20
Apr 26 13:34:30 gliadin kernel: [<ffffffff812ee456>] bus_add_driver+0x120/0x288
Apr 26 13:34:30 gliadin kernel: [<ffffffff812ef1fc>] driver_register+0x9e/0x10f
Apr 26 13:34:30 gliadin kernel: [<ffffffff8134e334>] usb_register_driver+0xb7/0x178
Apr 26 13:34:30 gliadin kernel: [<ffffffffa01af0a8>] ftdi_init+0xa8/0xd1 [ftdi_sio]
Apr 26 13:34:30 gliadin kernel: [<ffffffffa01af000>] ? ftdi_init+0x0/0xd1 [ftdi_sio]
Apr 26 13:34:30 gliadin kernel: [<ffffffff8100207d>] do_one_initcall+0x72/0x18a
Apr 26 13:34:30 gliadin kernel: [<ffffffff8108c496>] sys_init_module+0xd8/0x23a
Apr 26 13:34:30 gliadin kernel: [<ffffffff81009c72>] system_call_fastpath+0x16/0x1b
Apr 26 13:34:30 gliadin kernel: ---[ end trace 3842ea80b722d677 ]---
Apr 26 13:34:30 gliadin kernel: usb 1-1.4: FTDI USB Serial Device converter now attached to ttyUSB1
Apr 26 13:34:30 gliadin kernel: usbcore: registered new interface driver ftdi_sio
Apr 26 13:34:30 gliadin kernel: ftdi_sio: v1.5.0:USB FTDI Serial Converters Driver
Apr 26 13:34:40 gliadin lircd-0.8.6[1206]: lircd(usb_uirt_raw) ready, using /var/run/lirc/lircd
Apr 26 13:36:40 gliadin lircd-0.8.6[1206]: accepted new client on /var/run/lirc/lircd
Apr 26 13:36:40 gliadin lircd-0.8.6[1206]: uirt2_raw: could not open /dev/serial/by-id/usb-FTDI_USB-UIRT-if00-port0
Apr 26 13:36:40 gliadin lircd-0.8.6[1206]: Failed to initialize hardware
Apr 26 13:36:49 gliadin lircd-0.8.6[1206]: caught signal
Apr 26 13:36:49 gliadin kernel: lircd[1206]: segfault at 8 ip 000000000042120b sp 00007ffff0dd7c40 error 4 in lircd[400000+2c000]
Apr 26 13:36:50 gliadin lircd-0.8.6[1915]: lircd(usb_uirt_raw) ready, using /var/run/lirc/lircd
Apr 26 13:36:51 gliadin lircd-0.8.6[1915]: accepted new client on /var/run/lirc/lircd
Apr 26 13:36:51 gliadin lircd-0.8.6[1915]: uirt2_raw: could not open /dev/serial/by-id/usb-FTDI_USB-UIRT-if00-port0
Apr 26 13:36:51 gliadin lircd-0.8.6[1915]: Failed to initialize hardware
Apr 26 13:37:15 gliadin lircd-0.8.6[1915]: caught signal
Apr 26 13:37:15 gliadin kernel: lircd[1915]: segfault at 8 ip 000000000042120b sp 00007fff9bdfbf20 error 4 in lircd[400000+2c000]
Apr 26 13:37:20 gliadin lircd-0.8.6[1982]: lircd(usb_uirt_raw) ready, using /var/run/lirc/lircd
Apr 26 13:37:21 gliadin lircd-0.8.6[1982]: accepted new client on /var/run/lirc/lircd
Apr 26 13:37:23 gliadin lircd-0.8.6[1982]: uirt2_raw: did not receive results
Apr 26 13:37:24 gliadin lircd-0.8.6[1982]: uirt2_raw: did not receive results
Apr 26 13:37:24 gliadin lircd-0.8.6[1982]: uirt2_raw: No UIRT2 device found at /dev/serial/by-id/usb-FTDI_USB-UIRT-if00-port0
Apr 26 13:37:24 gliadin lircd-0.8.6[1982]: Failed to initialize hardware
Apr 26 13:37:24 gliadin lircd-0.8.6[1982]: select() failed
Apr 26 13:37:24 gliadin lircd-0.8.6[1982]: Bad file descriptor
Apr 26 13:37:24 gliadin lircd-0.8.6[1982]: removed client
Apr 26 13:37:24 gliadin kernel: lircd[1982]: segfault at 8 ip 000000000042120b sp 00007fffd25c65c0 error 4 in lircd[400000+2c000]
Apr 26 13:37:37 gliadin lircd-0.8.6[1997]: lircd(usb_uirt_raw) ready, using /var/run/lirc/lircd
Apr 26 13:37:38 gliadin lircd-0.8.6[1997]: accepted new client on /var/run/lirc/lircd
Apr 26 13:37:38 gliadin lircd-0.8.6[1997]: uirt2_raw: checksum error
Apr 26 13:37:38 gliadin lircd-0.8.6[1997]: uirt2_raw: UIRT version 0905 ok

The manual command is:
/usr/sbin/lircd --driver=usb_uirt_raw --device=/dev/serial/by-id/usb-FTDI_USB-UIRT-if00-port0

Comment 9 Jarod Wilson 2010-04-26 13:52:42 UTC
Damn. Well, I've got usb-uirt hardware around here somewhere, I'll dig it out and hook it up to one of my F13 boxes and see what I can see.

Comment 10 Steven Adeff 2010-06-04 22:54:01 UTC
I'm having this exact same issue. Anything I can provide to help fix it?

Comment 11 Bug Zapper 2011-06-02 15:38:01 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  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 '13'.

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 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 12 Bug Zapper 2011-06-27 15:26:53 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.

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.