Bug 912120

Summary:

[abrt] transmission-gtk-2.76-1.fc18: __lll_lock_wait: Process /usr/bin/transmission-gtk was killed by signal 4 (SIGILL)

Product:

[Fedora] Fedora

Reporter:

jan p. springer <jsd>

Component:

transmission

Assignee:

Rahul Sundaram <metherid>

Status:

CLOSED WONTFIX

QA Contact:

Fedora Extras Quality Assurance <extras-qa>

Severity:

unspecified

Docs Contact:

Priority:

unspecified

Version:

CC:

abdulkarimmemon, charles, jspaleta, kumarpraveen.nitdgp, metherid, raghusiddarth, sanjay.ankur

Target Milestone:

---

Target Release:

---

Hardware:

x86_64

OS:

Unspecified

Whiteboard:

abrt_hash:4f929de3774d82a9402a21b25207af5e63361b0b

Fixed In Version:

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2014-02-05 19:14:45 UTC

Type:

---

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

---

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Embargoed:

Attachments:

Description	Flags
File: backtrace	none
File: cgroup	none
File: core_backtrace	none
File: dso_list	none
File: environ	none
File: limits	none
File: maps	none
File: open_fds	none
File: proc_pid_status	none
File: var_log_messages	none

Description jan p. springer 2013-02-17 18:48:55 UTC

Description of problem:
transmission-gtk consistently hangs at startup in futex_wait_queue_me. i used kill -ILL to get a stacktrace and report via abrt

Version-Release number of selected component:
transmission-gtk-2.76-1.fc18

Additional info:
backtrace_rating: 4
cmdline:        transmission-gtk
crash_function: __lll_lock_wait
executable:     /usr/bin/transmission-gtk
kernel:         3.7.7-201.fc18.x86_64
remote_result:  NOTFOUND
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 __lll_lock_wait at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135
 #1 _L_lock_885 at /lib64/libpthread.so.0
 #2 __pthread_mutex_lock at pthread_mutex_lock.c:85
 #3 tr_lockLock at platform.c:200
 #4 tr_sessionLock at session.c:1047
 #5 tr_torrentLock at torrent.h:305
 #6 tr_torrentStat at torrent.c:1191
 #7 update_foreach at tr-core.c:1423
 #8 gtr_core_update at tr-core.c:1475
 #9 update_model_once at main.c:1276

Comment 1 jan p. springer 2013-02-17 18:48:59 UTC

Created attachment 698589 [details]
File: backtrace

Comment 2 jan p. springer 2013-02-17 18:49:05 UTC

Created attachment 698590 [details]
File: cgroup

Comment 3 jan p. springer 2013-02-17 18:49:10 UTC

Created attachment 698591 [details]
File: core_backtrace

Comment 4 jan p. springer 2013-02-17 18:49:13 UTC

Created attachment 698592 [details]
File: dso_list

Comment 5 jan p. springer 2013-02-17 18:49:15 UTC

Created attachment 698593 [details]
File: environ

Comment 6 jan p. springer 2013-02-17 18:49:18 UTC

Created attachment 698594 [details]
File: limits

Comment 7 jan p. springer 2013-02-17 18:49:23 UTC

Created attachment 698595 [details]
File: maps

Comment 8 jan p. springer 2013-02-17 18:49:36 UTC

Created attachment 698596 [details]
File: open_fds

Comment 9 jan p. springer 2013-02-17 18:49:38 UTC

Created attachment 698597 [details]
File: proc_pid_status

Comment 10 jan p. springer 2013-02-17 18:49:49 UTC

Created attachment 698598 [details]
File: var_log_messages

Comment 11 jan p. springer 2013-03-03 12:18:53 UTC

running transmission-gtk in gdb also works. could this be timing-dependent locking problem?

Comment 12 jan p. springer 2013-03-03 12:44:26 UTC

oops, running in gdb also crashes w/ SIGPIPE:

Program received signal SIGPIPE, Broken pipe.
[Switching to Thread 0x7ffff5e1e700 (LWP 11203)]
0x0000003e30ceb1f1 in __libc_writev (fd=<optimized out>, vector=<optimized out>, count=<optimized out>)
    at ../sysdeps/unix/sysv/linux/writev.c:55
55	      result = INLINE_SYSCALL (writev, 3, fd, CHECK_N (vector, count), count);

#0  0x0000003e30ceb1f1 in __libc_writev (fd=<optimized out>, vector=<optimized out>, count=<optimized out>)
    at ../sysdeps/unix/sysv/linux/writev.c:55
#1  0x0000003e394146bf in evbuffer_write_iovec (fd=51, howmuch=-1, howmuch@entry=289, buffer=<optimized out>, 
    buffer=<optimized out>) at buffer.c:2275
#2  0x0000003e39417a95 in evbuffer_write_atmost (buffer=0x7fffec010da0, fd=fd@entry=51, howmuch=howmuch@entry=289)
    at buffer.c:2359
#3  0x000000000044d026 in tr_evbuffer_write (io=io@entry=0x7fffec0c0780, fd=51, howmuch=289) at peer-io.c:317
#4  0x000000000044d206 in tr_peerIoTryWrite (io=io@entry=0x7fffec0c0780, howmuch=<optimized out>, howmuch@entry=3000)
    at peer-io.c:1286
#5  0x000000000044effd in tr_peerIoFlush (io=0x7fffec0c0780, dir=dir@entry=TR_CLIENT_TO_PEER, limit=limit@entry=3000)
    at peer-io.c:1320
#6  0x000000000046d62f in phaseOne (peerArray=peerArray@entry=0x7ffff5e1da50, dir=dir@entry=TR_CLIENT_TO_PEER)
    at bandwidth.c:219
#7  0x000000000046db44 in tr_bandwidthAllocate (b=b@entry=0xa58420, dir=dir@entry=TR_CLIENT_TO_PEER, 
    period_msec=period_msec@entry=500) at bandwidth.c:271
#8  0x0000000000476d0a in bandwidthPulse (foo=<optimized out>, bar=<optimized out>, vmgr=0x7fffec001d10) at peer-mgr.c:3615
#9  0x0000003e394100e2 in event_process_active_single_queue (activeq=<optimized out>, base=<optimized out>) at event.c:1340
#10 event_process_active (base=<optimized out>) at event.c:1407
#11 event_base_loop (base=base@entry=0x7fffec0008f0, flags=flags@entry=0) at event.c:1604
#12 0x0000003e39411177 in event_base_dispatch (event_base=event_base@entry=0x7fffec0008f0) at event.c:1435
#13 0x00000000004633b0 in libeventThreadFunc (veh=0xa4e570) at trevent.c:248
#14 0x000000000044f09a in ThreadFunc (_t=0xa52fb0) at platform.c:118
#15 0x0000003e31807d15 in start_thread (arg=0x7ffff5e1e700) at pthread_create.c:308
#16 0x0000003e30cf246d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:114

how can i create an abrt-like report by hand for this?

Comment 13 jan p. springer 2013-03-03 12:45:33 UTC

oops, running in gdb also crashes w/ SIGPIPE:

Program received signal SIGPIPE, Broken pipe.
[Switching to Thread 0x7ffff5e1e700 (LWP 11203)]
0x0000003e30ceb1f1 in __libc_writev (fd=<optimized out>, vector=<optimized out>, count=<optimized out>)
    at ../sysdeps/unix/sysv/linux/writev.c:55
55	      result = INLINE_SYSCALL (writev, 3, fd, CHECK_N (vector, count), count);

#0  0x0000003e30ceb1f1 in __libc_writev (fd=<optimized out>, vector=<optimized out>, count=<optimized out>)
    at ../sysdeps/unix/sysv/linux/writev.c:55
#1  0x0000003e394146bf in evbuffer_write_iovec (fd=51, howmuch=-1, howmuch@entry=289, buffer=<optimized out>, 
    buffer=<optimized out>) at buffer.c:2275
#2  0x0000003e39417a95 in evbuffer_write_atmost (buffer=0x7fffec010da0, fd=fd@entry=51, howmuch=howmuch@entry=289)
    at buffer.c:2359
#3  0x000000000044d026 in tr_evbuffer_write (io=io@entry=0x7fffec0c0780, fd=51, howmuch=289) at peer-io.c:317
#4  0x000000000044d206 in tr_peerIoTryWrite (io=io@entry=0x7fffec0c0780, howmuch=<optimized out>, howmuch@entry=3000)
    at peer-io.c:1286
#5  0x000000000044effd in tr_peerIoFlush (io=0x7fffec0c0780, dir=dir@entry=TR_CLIENT_TO_PEER, limit=limit@entry=3000)
    at peer-io.c:1320
#6  0x000000000046d62f in phaseOne (peerArray=peerArray@entry=0x7ffff5e1da50, dir=dir@entry=TR_CLIENT_TO_PEER)
    at bandwidth.c:219
#7  0x000000000046db44 in tr_bandwidthAllocate (b=b@entry=0xa58420, dir=dir@entry=TR_CLIENT_TO_PEER, 
    period_msec=period_msec@entry=500) at bandwidth.c:271
#8  0x0000000000476d0a in bandwidthPulse (foo=<optimized out>, bar=<optimized out>, vmgr=0x7fffec001d10) at peer-mgr.c:3615
#9  0x0000003e394100e2 in event_process_active_single_queue (activeq=<optimized out>, base=<optimized out>) at event.c:1340
#10 event_process_active (base=<optimized out>) at event.c:1407
#11 event_base_loop (base=base@entry=0x7fffec0008f0, flags=flags@entry=0) at event.c:1604
#12 0x0000003e39411177 in event_base_dispatch (event_base=event_base@entry=0x7fffec0008f0) at event.c:1435
#13 0x00000000004633b0 in libeventThreadFunc (veh=0xa4e570) at trevent.c:248
#14 0x000000000044f09a in ThreadFunc (_t=0xa52fb0) at platform.c:118
#15 0x0000003e31807d15 in start_thread (arg=0x7ffff5e1e700) at pthread_create.c:308
#16 0x0000003e30cf246d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:114

how can i create an abrt-like report by hand for this?

Comment 14 jan p. springer 2013-03-03 12:52:47 UTC

just saw 2.77 being available in the update-testing repository. unfortunately, after installation, it exhibits the same problem as 2.76.

Comment 15 Fedora End Of Life 2013-12-21 11:29:14 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 16 Fedora End Of Life 2014-02-05 19:14:45 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.