Bug 744221 - Kernel is constantly tracebacking in console an dlog files.
Summary: Kernel is constantly tracebacking in console an dlog files.
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-07 14:10 UTC by Daniel Walsh
Modified: 2011-12-06 20:45 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-06 20:45:08 UTC
Type: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Daniel Walsh 2011-10-07 14:10:48 UTC 
Description of problem:
[20734.109233] Call Trace:
[20734.109242]  [<ffffffff8104f6b5>] __might_sleep+0x103/0x108
[20734.109249]  [<ffffffff8150363e>] mutex_lock_nested+0x25/0x45
[20734.109260]  [<ffffffffa023b8f7>] e1000_acquire_swflag_ich8lan+0x26/0x136 [e1000e]
[20734.109271]  [<ffffffffa024a3af>] e1000e_update_stats+0x156/0x73e [e1000e]
[20734.109275]  [<ffffffff81504561>] ? _raw_spin_lock+0x71/0x79
[20734.109285]  [<ffffffffa024e658>] ? e1000_watchdog_task+0x3b1/0x5de [e1000e]
[20734.109294]  [<ffffffffa024e660>] e1000_watchdog_task+0x3b9/0x5de [e1000e]
[20734.109303]  [<ffffffffa024e2a7>] ? e1000_update_mng_vlan+0x68/0x68 [e1000e]
[20734.109307]  [<ffffffff81075b21>] process_one_work+0x205/0x3e7
[20734.109310]  [<ffffffff81075a69>] ? process_one_work+0x14d/0x3e7
[20734.109315]  [<ffffffff8108cf0f>] ? lock_acquired+0x210/0x243
[20734.109320]  [<ffffffff810767cf>] worker_thread+0xda/0x15d
[20734.109323]  [<ffffffff810766f5>] ? manage_workers+0x176/0x176
[20734.109327]  [<ffffffff8107a195>] kthread+0xa8/0xb0
[20734.109332]  [<ffffffff8150dec4>] kernel_thread_helper+0x4/0x10
[20734.109336]  [<ffffffff81505334>] ? retint_restore_args+0x13/0x13
[20734.109340]  [<ffffffff8107a0ed>] ? __init_kthread_worker+0x5a/0x5a
[20734.109344]  [<ffffffff8150dec0>] ? gs_change+0x13/0x13
[20736.106653] BUG: sleeping function called from invalid context at kernel/mutex.c:271
[20736.106658] in_atomic(): 1, irqs_disabled(): 0, pid: 18071, name: kworker/0:1
[20736.106661] INFO: lockdep is turned off.
[20736.106664] Pid: 18071, comm: kworker/0:1 Not tainted 3.1.0-0.rc9.git0.0.fc17.x86_64 #1
[20736.106667] Call Trace:
[20736.106675]  [<ffffffff8104f6b5>] __might_sleep+0x103/0x108
[20736.106682]  [<ffffffff8150363e>] mutex_lock_nested+0x25/0x45
[20736.106693]  [<ffffffffa023b8f7>] e1000_acquire_swflag_ich8lan+0x26/0x136 [e1000e]
[20736.106705]  [<ffffffffa024a3af>] e1000e_update_stats+0x156/0x73e [e1000e]
[20736.106709]  [<ffffffff81504561>] ? _raw_spin_lock+0x71/0x79
[20736.106719]  [<ffffffffa024e658>] ? e1000_watchdog_task+0x3b1/0x5de [e1000e]
[20736.106728]  [<ffffffffa024e660>] e1000_watchdog_task+0x3b9/0x5de [e1000e]
[20736.106737]  [<ffffffffa024e2a7>] ? e1000_update_mng_vlan+0x68/0x68 [e1000e]
[20736.106741]  [<ffffffff81075b21>] process_one_work+0x205/0x3e7
[20736.106744]  [<ffffffff81075a69>] ? process_one_work+0x14d/0x3e7
[20736.106749]  [<ffffffff8108cf0f>] ? lock_acquired+0x210/0x243
[20736.106754]  [<ffffffff810767cf>] worker_thread+0xda/0x15d
[20736.106757]  [<ffffffff810766f5>] ? manage_workers+0x176/0x176
[20736.106761]  [<ffffffff8107a195>] kthread+0xa8/0xb0
[20736.106767]  [<ffffffff8150dec4>] kernel_thread_helper+0x4/0x10
[20736.106771]  [<ffffffff81505334>] ? retint_restore_args+0x13/0x13
[20736.106775]  [<ffffffff8107a0ed>] ? __init_kthread_worker+0x5a/0x5a
[20736.106779]  [<ffffffff8150dec0>] ? gs_change+0x13/0x13
[20738.104064] BUG: sleeping function called from invalid context at kernel/mutex.c:271
[20738.104070] in_atomic(): 1, irqs_disabled(): 0, pid: 18071, name: kworker/0:1
[20738.104073] INFO: lockdep is turned off.
[20738.104077] Pid: 18071, comm: kworker/0:1 Not tainted 3.1.0-0.rc9.git0.0.fc17.x86_64 #1
[20738.104079] Call Trace:
[20738.104088]  [<ffffffff8104f6b5>] __might_sleep+0x103/0x108
[20738.104096]  [<ffffffff8150363e>] mutex_lock_nested+0x25/0x45
[20738.104107]  [<ffffffffa023b8f7>] e1000_acquire_swflag_ich8lan+0x26/0x136 [e1000e]
[20738.104118]  [<ffffffffa024a3af>] e1000e_update_stats+0x156/0x73e [e1000e]
[20738.104123]  [<ffffffff81504561>] ? _raw_spin_lock+0x71/0x79
[20738.104133]  [<ffffffffa024e658>] ? e1000_watchdog_task+0x3b1/0x5de [e1000e]
[20738.104142]  [<ffffffffa024e660>] e1000_watchdog_task+0x3b9/0x5de [e1000e]
[20738.104151]  [<ffffffffa024e2a7>] ? e1000_update_mng_vlan+0x68/0x68 [e1000e]
[20738.104155]  [<ffffffff81075b21>] process_one_work+0x205/0x3e7
[20738.104158]  [<ffffffff81075a69>] ? process_one_work+0x14d/0x3e7
[20738.104162]  [<ffffffff8108cf0f>] ? lock_acquired+0x210/0x243
[20738.104167]  [<ffffffff810767cf>] worker_thread+0xda/0x15d
[20738.104170]  [<ffffffff810766f5>] ? manage_workers+0x176/0x176
[20738.104175]  [<ffffffff8107a195>] kthread+0xa8/0xb0
[20738.104180]  [<ffffffff8150dec4>] kernel_thread_helper+0x4/0x10
[20738.104184]  [<ffffffff81505334>] ? retint_restore_args+0x13/0x13
[20738.104188]  [<ffffffff8107a0ed>] ? __init_kthread_worker+0x5a/0x5a
[20738.104192]  [<ffffffff8150dec0>] ? gs_change+0x13/0x13



On my x220 ThinnkPad.
Comment 1 Daniel Walsh 2011-10-07 14:11:23 UTC 
 uname -r
3.1.0-0.rc9.git0.0.fc17.x86_64

But this has been happening the last few kernels.
Comment 2 Dave Jones 2011-10-07 16:13:26 UTC 
thanks. Just reported this to netdev.
Comment 3 Chuck Ebbert 2011-10-18 03:44:13 UTC 
Fix:
http://git.kernel.org/?p=linux/kernel/git/jkirsher/net-next.git;a=commitdiff;h=a90b412cb8c7ccc1689f9ea130883d00a1f0a5bb

It says this only happens on half-duplex connections. Is that what you have?
Comment 4 Daniel Walsh 2011-10-18 15:10:29 UTC 
Not sure, how do I check?
Comment 5 Dave Jones 2011-12-06 17:49:02 UTC 
ethtool eth0 (or whatever the interface is named).

Is it still happening with current rawhide ? (that patch is included in current builds).
Comment 6 Daniel Walsh 2011-12-06 20:45:08 UTC 
I have not seen this for a while.
Note You need to log in before you can comment on or make changes to this bug.