Bug 710841 - Random softlockups with Realtek 8169 adapter (driver r8169)
Summary: Random softlockups with Realtek 8169 adapter (driver r8169)
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 15
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:66966a9f174308a832ec9de64c1...
: 710990 711352 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-05 08:10 UTC by Trever Adams
Modified: 2011-09-26 18:58 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-09-26 18:58:54 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Trever Adams 2011-06-05 08:10:13 UTC
abrt version: 2.0.1
architecture:   x86_64
cmdline:        ro root=/dev/mapper/vg_forbiddencity-lv_root rd_LVM_LV=vg_forbiddencity/lv_root rd_LVM_LV=vg_forbiddencity/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet
comment:        Amandabackup amdump running.
component:      kernel
kernel:         2.6.38.6-27.fc15.x86_64
os_release:     Fedora release 15 (Lovelock)
package:        kernel
reason:         BUG: soft lockup - CPU#1 stuck for 67s! [kworker/1:2:53]
reported_to:    kerneloops: URL=http://submit.kerneloops.org/submitoops.php
time:           Sun May 29 00:20:43 2011

backtrace:
:BUG: soft lockup - CPU#1 stuck for 67s! [kworker/1:2:53]
:Modules linked in: cpufreq_ondemand powernow_k8 freq_table mperf ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 ts_kmp ip6table_filter nf_conntrack_amanda ip6_tables raid456 async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy async_tx eeepc_wmi sparse_keymap snd_hda_codec_realtek rfkill snd_hda_codec_hdmi snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device snd_pcm r8169 mii sp5100_tco i2c_piix4 snd_timer k10temp snd soundcore wmi snd_page_alloc ipv6 radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core [last unloaded: scsi_wait_scan]
:CPU 1 
:Modules linked in: cpufreq_ondemand powernow_k8 freq_table mperf ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 ts_kmp ip6table_filter nf_conntrack_amanda ip6_tables raid456 async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy async_tx eeepc_wmi sparse_keymap snd_hda_codec_realtek rfkill snd_hda_codec_hdmi snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device snd_pcm r8169 mii sp5100_tco i2c_piix4 snd_timer k10temp snd soundcore wmi snd_page_alloc ipv6 radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core [last unloaded: scsi_wait_scan]
:Pid: 53, comm: kworker/1:2 Not tainted 2.6.38.6-27.fc15.x86_64 #1 System manufacturer System Product Name/E35M1-M PRO
:RIP: 0010:[<ffffffff8123cee0>]  [<ffffffff8123cee0>] swiotlb_bounce+0x27/0x2b
:RSP: 0000:ffff8800b7903d20  EFLAGS: 00000286
:RAX: ffff8800b3b3c000 RBX: ffff880180000000 RCX: 00000000000005e2
:RDX: 00000000000005ea RSI: ffff8800b3b3c008 RDI: ffff88011a0cc008
:RBP: ffff8800b7903d20 R08: ffff88011a0cc000 R09: ffff8800b7b89000
:R10: ffffffff81b40d00 R11: ffffffff81b40d00 R12: ffffffff8100a593
:R13: ffff8800b7903c98 R14: 00000000b3b3c000 R15: ffff880127eee090
:FS:  00007fa3213b37e0(0000) GS:ffff8800b7900000(0000) knlGS:0000000000000000
:CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
:CR2: 000000000063d000 CR3: 00000001199a1000 CR4: 00000000000006e0
:DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
:DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
:Process kworker/1:2 (pid: 53, threadinfo ffff880124598000, task ffff8801244cdc80)
:Stack:
: ffff8800b7903d30 ffffffff8123cf3d ffff8800b7903d70 ffffffff8123d44f
: ffff88003783ecb0 ffff880100000000 ffffffff00000002 00000000000005ea
: ffff8801251c0000 ffff8801251c06c0 ffff8800b7903d80 ffffffff8123d520
:Call Trace:

Comment 1 Trever Adams 2011-07-05 19:44:33 UTC
I switched Realtek 8169 to Intel e100e PCIe card. I have not been able to duplicate any of these problems since, even under very heavy load. The process is also much more idle (nearly completely used w/ 8169 and about 30-70% idle most of the time, more than 50 quite often, with the later card).

I do not know if the 8169 chipset is just broken or if the driver is, but the problem lies with one of the two.

Comment 2 Chuck Ebbert 2011-07-19 12:47:02 UTC
*** Bug 710990 has been marked as a duplicate of this bug. ***

Comment 3 Chuck Ebbert 2011-07-19 12:47:15 UTC
*** Bug 711352 has been marked as a duplicate of this bug. ***

Comment 4 Josh Boyer 2011-09-26 17:56:08 UTC
Have you tried this card with the latest 2.6.40 kernel in F15?

Comment 5 Trever Adams 2011-09-26 18:46:13 UTC
I have not. I am afraid this is a production AMANDA backup server and I have switched to the Intel card as stated. I cannot take this machine down to do testing. I am sorry.

Comment 6 Josh Boyer 2011-09-26 18:58:54 UTC
Ok, that is perfectly understandable.  I'm going to close this bug out as insufficient data.  We haven't seen many other reports of it and we'd need it to happen on a fresh kernel anyway.  Thank you for taking the time to report.


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