Login
[x]
Log in using an account from:
Fedora Account System
Red Hat Associate
Red Hat Customer
Or login using a Red Hat Bugzilla account
Forgot Password
Login:
Hide Forgot
Create an Account
Red Hat Bugzilla – Attachment 299656 Details for
Bug 438529
NM crashes on shutdown
[?]
New
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
|
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh83 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
This site requires JavaScript to be enabled to function correctly, please enable it.
st-NetworkManager-stop-erasedpackage.txt
st-NetworkManager-stop-erasedpackage.txt (text/plain), 5.23 KB, created by
Andrew Farris
on 2008-03-31 01:50:48 UTC
(
hide
)
Description:
st-NetworkManager-stop-erasedpackage.txt
Filename:
MIME Type:
Creator:
Andrew Farris
Created:
2008-03-31 01:50:48 UTC
Size:
5.23 KB
patch
obsolete
>Mar 30 17:42:10 localhost NetworkManager: <WARN> nm_signal_handler(): Caught signal 15, shutting down normally. >Mar 30 17:42:10 localhost NetworkManager: <info> Bringing down device eth1 >Mar 30 17:42:10 localhost NetworkManager: <info> Deactivating device eth1. >Mar 30 17:42:10 localhost NetworkManager: <info> eth1: canceled DHCP transaction, dhclient pid 10986 >Mar 30 17:42:11 localhost NetworkManager: <info> Deactivating device eth1. >Mar 30 17:42:11 localhost NetworkManager: <info> Bringing down device eth0 >Mar 30 17:42:11 localhost kernel: > >======================================================= >[ INFO: possible circular locking dependency detected ] >2.6.25-0.121.rc5.git4.fc9 #1 >------------------------------------------------------- >NetworkManager/2336 is trying to acquire lock: > (events){--..}, at: [<c0436d9e>] flush_workqueue+0x0/0x85 > >but task is already holding lock: > (rtnl_mutex){--..}, at: [<c05cd164>] rtnetlink_rcv+0x12/0x26 > >which lock already depends on the new lock. > > >the existing dependency chain (in reverse order) is: > >-> #2 (rtnl_mutex){--..}: > [<c0445774>] __lock_acquire+0xa99/0xc11 > [<c0445956>] lock_acquire+0x6a/0x90 > [<c0637e09>] mutex_lock_nested+0xdb/0x271 > [<c05cd150>] rtnl_lock+0xf/0x11 > [<c05cdee5>] linkwatch_event+0x8/0x22 > [<c0436560>] run_workqueue+0xd3/0x1a1 > [<c04366e4>] worker_thread+0xb6/0xc2 > [<c04392e6>] kthread+0x3b/0x61 > [<c04069ef>] kernel_thread_helper+0x7/0x10 > [<ffffffff>] 0xffffffff > >-> #1 ((linkwatch_work).work){--..}: > [<c0445774>] __lock_acquire+0xa99/0xc11 > [<c0445956>] lock_acquire+0x6a/0x90 > [<c043655a>] run_workqueue+0xcd/0x1a1 > [<c04366e4>] worker_thread+0xb6/0xc2 > [<c04392e6>] kthread+0x3b/0x61 > [<c04069ef>] kernel_thread_helper+0x7/0x10 > [<ffffffff>] 0xffffffff > >-> #0 (events){--..}: > [<c0445693>] __lock_acquire+0x9b8/0xc11 > [<c0445956>] lock_acquire+0x6a/0x90 > [<c0436de2>] flush_workqueue+0x44/0x85 > [<c0436e30>] flush_scheduled_work+0xd/0xf > [<f8f7680a>] tulip_down+0x20/0x1a3 [tulip] > [<f8f772b5>] tulip_close+0x24/0xd6 [tulip] > [<c05c5a11>] dev_close+0x52/0x6f > [<c05c5768>] dev_change_flags+0x9f/0x152 > [<c05cc2eb>] do_setlink+0x24a/0x2fc > [<c05cc47f>] rtnl_setlink+0xe2/0xe6 > [<c05cd31a>] rtnetlink_rcv_msg+0x1a2/0x1bc > [<c05da486>] netlink_rcv_skb+0x30/0x86 > [<c05cd170>] rtnetlink_rcv+0x1e/0x26 > [<c05d9faa>] netlink_unicast+0x1b7/0x215 > [<c05da260>] netlink_sendmsg+0x258/0x265 > [<c05ba4e9>] sock_sendmsg+0xde/0xf9 > [<c05ba643>] sys_sendmsg+0x13f/0x192 > [<c05bb577>] sys_socketcall+0x16b/0x188 > [<c0405d12>] syscall_call+0x7/0xb > [<ffffffff>] 0xffffffff > >other info that might help us debug this: > >1 lock held by NetworkManager/2336: > #0: (rtnl_mutex){--..}, at: [<c05cd164>] rtnetlink_rcv+0x12/0x26 > >stack backtrace: >Pid: 2336, comm: NetworkManager Not tainted 2.6.25-0.121.rc5.git4.fc9 #1 > [<c0444ac5>] print_circular_bug_tail+0x5b/0x66 > [<c0444938>] ? print_circular_bug_entry+0x39/0x43 > [<c0445693>] __lock_acquire+0x9b8/0xc11 > [<c063945b>] ? _spin_unlock_irq+0x22/0x2f > [<c0445956>] lock_acquire+0x6a/0x90 > [<c0436d9e>] ? flush_workqueue+0x0/0x85 > [<c0436de2>] flush_workqueue+0x44/0x85 > [<c0436d9e>] ? flush_workqueue+0x0/0x85 > [<c0436e30>] flush_scheduled_work+0xd/0xf > [<f8f7680a>] tulip_down+0x20/0x1a3 [tulip] > [<c04447bb>] ? trace_hardirqs_on+0xe9/0x10a > [<c05d38bf>] ? dev_deactivate+0xb1/0xde > [<f8f772b5>] tulip_close+0x24/0xd6 [tulip] > [<c05c5a11>] dev_close+0x52/0x6f > [<c05c5768>] dev_change_flags+0x9f/0x152 > [<c05cc2eb>] do_setlink+0x24a/0x2fc > [<c063940e>] ? _read_unlock+0x1d/0x20 > [<c05cc47f>] rtnl_setlink+0xe2/0xe6 > [<c05cc39d>] ? rtnl_setlink+0x0/0xe6 > [<c05cd31a>] rtnetlink_rcv_msg+0x1a2/0x1bc > [<c05cd178>] ? rtnetlink_rcv_msg+0x0/0x1bc > [<c05da486>] netlink_rcv_skb+0x30/0x86 > [<c05cd170>] rtnetlink_rcv+0x1e/0x26 > [<c05d9faa>] netlink_unicast+0x1b7/0x215 > [<c05da260>] netlink_sendmsg+0x258/0x265 > [<c05ba4e9>] sock_sendmsg+0xde/0xf9 > [<c0439537>] ? autoremove_wake_function+0x0/0x33 > [<c040a2f4>] ? native_sched_clock+0xb5/0xd1 > [<c040a026>] ? sched_clock+0x8/0xb > [<c0442ffd>] ? lock_release_holdtime+0x1a/0x115 > [<c0489012>] ? fget_light+0x8e/0xb9 > [<c04fdab4>] ? copy_from_user+0x39/0x121 > [<c05c0ef5>] ? verify_iovec+0x40/0x6f > [<c05ba643>] sys_sendmsg+0x13f/0x192 > [<c05bb0cb>] ? sys_recvmsg+0x16e/0x17b > [<c040a2f4>] ? native_sched_clock+0xb5/0xd1 > [<c0442ffd>] ? lock_release_holdtime+0x1a/0x115 > [<c06394a8>] ? _spin_unlock_irqrestore+0x40/0x50 > [<c04447bb>] ? trace_hardirqs_on+0xe9/0x10a > [<c04255a3>] ? hrtick_set+0x80/0xe5 > [<c05bb577>] sys_socketcall+0x16b/0x188 > [<c0405d12>] syscall_call+0x7/0xb > ======================= >0000:02:0a.0: tulip_stop_rxtx() failed (CSR5 0xfc06c012 CSR6 0xff970111) >Mar 30 17:42:11 localhost NetworkManager: <info> Deactivating device eth0. >Mar 30 17:42:11 localhost NetworkManager: <info> Bringing down device wlan0 >Mar 30 17:42:11 localhost NetworkManager: <info> Deactivating device wlan0. >Mar 30 17:42:11 localhost NetworkManager: <WARN> nm_device_802_11_wireless_disable_encryption(): error setting key for device wlan0: No such file or directory > >The tulip_stop_rxtx is a problem reported in bug# 431038 and is not specific to this NetworkManager problem.
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 438529
:
298789
|
298797
|
298888
| 299656