From: Tushar Dave <tushar.n.dave@oracle.com>
To: Fengguang Wu <fengguang.wu@intel.com>, intel-wired-lan@lists.osuosl.org
Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
"David S. Miller" <davem@davemloft.net>,
Sasha Neftin <sasha.neftin@intel.com>,
Dima Ruinskiy <dima.ruinskiy@intel.com>,
Raanan Avargil <raanan.avargil@intel.com>,
Jacob Keller <jacob.e.keller@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Konstantin Khlebnikov <khlebnikov@yandex-team.ru>,
Bernd Faust <berndfaust@gmail.com>,
stephen hemminger <stephen@networkplumber.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org, lkp@01.org
Subject: Re: [e1000_shutdown] e1000 0000:00:03.0: disabling already-disabled device
Date: Wed, 22 Nov 2017 03:40:52 +0530 [thread overview]
Message-ID: <7fe10136-8f99-c0e8-2a3a-93c34915a95a@oracle.com> (raw)
In-Reply-To: <20171121124148.poknfqmuef32tbdn@wfg-t540p.sh.intel.com>
On 11/21/2017 06:11 PM, Fengguang Wu wrote:
> Hello,
>
> FYI this happens in mainline kernel 4.14.0-01330-g3c07399.
> It happens since 4.13 .
>
> It occurs in 3 out of 162 boots.
>
>
> [ 44.637743] advantechwdt: Unexpected close, not stopping watchdog!
> [ 44.997548] input: ImExPS/2 Generic Explorer Mouse as /devices/platform/i8042/serio1/input/input6
> [ 45.013419] e1000 0000:00:03.0: disabling already-disabled device
> [ 45.013447] ------------[ cut here ]------------
> [ 45.014868] WARNING: CPU: 1 PID: 71 at drivers/pci/pci.c:1641 pci_disable_device+0xa1/0x105:
> pci_disable_device at drivers/pci/pci.c:1640
> [ 45.016171] CPU: 1 PID: 71 Comm: rcu_perf_shutdo Not tainted 4.14.0-01330-g3c07399 #1
> [ 45.017197] task: ffff88011bee9e40 task.stack: ffffc90000860000
> [ 45.017987] RIP: 0010:pci_disable_device+0xa1/0x105:
> pci_disable_device at drivers/pci/pci.c:1640
> [ 45.018603] RSP: 0000:ffffc90000863e30 EFLAGS: 00010286
> [ 45.019282] RAX: 0000000000000035 RBX: ffff88013a230008 RCX: 0000000000000000
> [ 45.020182] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000203
> [ 45.021084] RBP: ffff88013a3f31e8 R08: 0000000000000001 R09: 0000000000000000
> [ 45.021986] R10: ffffffff827ec29c R11: 0000000000000002 R12: 0000000000000001
> [ 45.022946] R13: ffff88013a230008 R14: ffff880117802b20 R15: ffffc90000863e8f
> [ 45.023842] FS: 0000000000000000(0000) GS:ffff88013fd00000(0000) knlGS:0000000000000000
> [ 45.024863] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [ 45.025583] CR2: ffffc900006d4000 CR3: 000000000220f000 CR4: 00000000000006a0
> [ 45.026478] Call Trace:
> [ 45.026811] __e1000_shutdown+0x1d4/0x1e2:
> __e1000_shutdown at drivers/net/ethernet/intel/e1000/e1000_main.c:5162
> [ 45.027344] ? rcu_perf_cleanup+0x2a1/0x2a1:
> rcu_perf_shutdown at kernel/rcu/rcuperf.c:627
> [ 45.027883] e1000_shutdown+0x14/0x3a:
> e1000_shutdown at drivers/net/ethernet/intel/e1000/e1000_main.c:5235
> [ 45.028351] device_shutdown+0x110/0x1aa:
> device_shutdown at drivers/base/core.c:2807
> [ 45.028858] kernel_power_off+0x31/0x64:
> kernel_power_off at kernel/reboot.c:260
> [ 45.029343] rcu_perf_shutdown+0x9b/0xa7:
> rcu_perf_shutdown at kernel/rcu/rcuperf.c:637
> [ 45.029852] ? __wake_up_common_lock+0xa2/0xa2:
> autoremove_wake_function at kernel/sched/wait.c:376
> [ 45.030414] kthread+0x126/0x12e:
> kthread at kernel/kthread.c:233
> [ 45.030834] ? __kthread_bind_mask+0x8e/0x8e:
> kthread at kernel/kthread.c:190
> [ 45.031399] ? ret_from_fork+0x1f/0x30:
> ret_from_fork at arch/x86/entry/entry_64.S:443
> [ 45.031883] ? kernel_init+0xa/0xf5:
> kernel_init at init/main.c:997
> [ 45.032325] ret_from_fork+0x1f/0x30:
> ret_from_fork at arch/x86/entry/entry_64.S:443
> [ 45.032777] Code: 00 48 85 ed 75 07 48 8b ab a8 00 00 00 48 8d bb 98 00 00 00 e8 aa d1 11 00 48 89 ea 48 89 c6 48 c7 c7 d8 e4 0b 82 e8 55 7d da ff <0f> ff b9 01 00 00 00 31 d2 be 01 00 00 00 48 c7 c7 f0 b1 61 82
> [ 45.035222] ---[ end trace c257137b1b1976ef ]---
> [ 45.037838] ACPI: Preparing to enter system sleep state S5
>
> Attached the full dmesg, kconfig and reproduce scripts.
Looks like e1000 pci/pxi-x device is already suspended. And therefore
call to e1000_suspend() -> __e1000_shutdown() -> pci_disable_device()
already had disabled the device.
Disabling device again by e1000_shutdown handler during system shutdown
causes warning at drivers/pci/pci.c:1641.
I think function __e1000_shutdown should just return if device is
already suspended!
I don't have e1000 hardware to test right now. So if this seems logical
to others I will send a patch.
-Tushar
>
> Thanks,
> Fengguang
>
next prev parent reply other threads:[~2017-11-21 22:11 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-21 9:05 active bugs in the first week of 4.15 merge window Fengguang Wu
2017-11-21 10:04 ` [test_abba] WARNING: possible circular locking dependency detected Fengguang Wu
2017-11-21 10:54 ` [ata_port_detach] WARNING: CPU: 0 PID: 1 at drivers/ata/libata-core.c:6613 ata_port_detach+0x9b/0x180 Fengguang Wu
2017-11-21 11:30 ` Arnd Bergmann
2017-11-21 11:07 ` [tracer_init_tracefs] watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [swapper/0:1] Fengguang Wu
2017-11-21 12:27 ` Fengguang Wu
2017-11-21 13:55 ` Thomas Gleixner
2017-11-21 11:10 ` [rbtree_test_init] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper:1] Fengguang Wu
2017-11-21 21:59 ` Andrew Morton
2017-11-22 2:15 ` Fengguang Wu
2017-11-21 11:19 ` [rht_deferred_worker] BUG: workqueue lockup - pool cpus=0 node=0 flags=0x0 nice=0 stuck for 62s! Fengguang Wu
2017-11-21 11:52 ` [test_rht_init] INFO: task swapper/0:1 blocked for more than 120 seconds Fengguang Wu
2017-11-27 21:34 ` Linus Torvalds
2017-11-27 21:32 ` [rht_deferred_worker] BUG: workqueue lockup - pool cpus=0 node=0 flags=0x0 nice=0 stuck for 62s! Linus Torvalds
2017-11-21 11:53 ` [vga_arb_device_init] WARNING: possible circular locking dependency detected Fengguang Wu
2017-11-21 16:52 ` Lukas Wunner
2017-11-22 9:07 ` Daniel Vetter
2017-11-21 17:08 ` [char-misc] " Daniel Vetter
2017-11-21 12:04 ` [migration_cpu_stop] WARNING: CPU: 0 PID: 11 at kernel/sched/core.c:1187 set_task_cpu+0x257/0x6b6 Fengguang Wu
2017-11-21 13:34 ` Peter Zijlstra
2017-11-21 13:51 ` Fengguang Wu
2017-11-21 16:13 ` Paul E. McKenney
2017-11-22 12:18 ` Fengguang Wu
2017-11-21 14:01 ` Rafael J. Wysocki
2017-11-21 12:09 ` [ata_port_probe] BUG: unable to handle kernel NULL pointer dereference at 0000000000000350 Fengguang Wu
2017-11-21 12:19 ` Fengguang Wu
2017-11-21 12:54 ` Arnd Bergmann
2017-11-21 14:57 ` Tejun Heo
2017-11-21 15:30 ` Arnd Bergmann
2017-11-21 12:33 ` [serial8250_interrupt] RIP: 0010:arch_local_irq_restore+0x2/0x8 Fengguang Wu
2017-11-21 13:31 ` Fengguang Wu
2017-11-21 14:39 ` Andy Shevchenko
2017-11-21 21:14 ` Andy Shevchenko
2017-11-22 23:36 ` Fengguang Wu
2017-11-22 23:43 ` Fengguang Wu
2017-11-21 12:41 ` [e1000_shutdown] e1000 0000:00:03.0: disabling already-disabled device Fengguang Wu
2017-11-21 22:10 ` Tushar Dave [this message]
2017-11-22 23:13 ` Fengguang Wu
2017-11-27 19:31 ` Tushar Dave
2017-12-04 11:33 ` Fengguang Wu
2017-12-05 19:19 ` Tushar Dave
2017-11-21 12:50 ` [test_cycle_work] WARNING: possible circular locking dependency detected Fengguang Wu
2017-11-21 13:01 ` [hrtimer_active] INFO: trying to register non-static key Fengguang Wu
2017-11-22 14:37 ` [hrtimer_active ^W ata_port_wait_eh] " Thomas Gleixner
2017-11-24 12:49 ` Tejun Heo
2017-11-24 13:41 ` Fengguang Wu
[not found] ` <20171121121233.3pvkb34tci47n634@wfg-t540p.sh.intel.com>
2017-11-21 13:28 ` [RING_BUFFER_BENCHMARK] INFO: task rb_producer:73 blocked for more than 120 seconds Fengguang Wu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7fe10136-8f99-c0e8-2a3a-93c34915a95a@oracle.com \
--to=tushar.n.dave@oracle.com \
--cc=berndfaust@gmail.com \
--cc=davem@davemloft.net \
--cc=dima.ruinskiy@intel.com \
--cc=fengguang.wu@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jacob.e.keller@intel.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=khlebnikov@yandex-team.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=netdev@vger.kernel.org \
--cc=raanan.avargil@intel.com \
--cc=sasha.neftin@intel.com \
--cc=stephen@networkplumber.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®