Bug 994438
| Summary: | [abrt] WARNING: at drivers/pci/pci.c:1393 pci_disable_device+0x85/0x90() | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Fidel Leon <fidelleon> | ||||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 19 | CC: | apodtele, gansalmon, habibshana, itamar, jdayer, jonathan, kernel-maint, madhu.chinakonda, me, michele, michele, moromario, netbug73, tpeplt | ||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||
| Target Release: | --- | ||||||||
| Hardware: | i686 | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | abrt_hash:a2d3bbb5586023df908cb8ee42e4ce7bb5658368 | ||||||||
| Fixed In Version: | kernel-3.13.5-101.fc19 | Doc Type: | Bug Fix | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | |||||||||
| : | 1033420 (view as bug list) | Environment: | |||||||
| Last Closed: | 2014-02-28 18:35:27 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
Fidel Leon
2013-08-07 09:58:36 UTC
Created attachment 783779 [details]
File: dmesg
Description of problem: Dell Dimension Desktop E510 waking up from suspend Additional info: reporter: libreport-2.1.6 cmdline: BOOT_IMAGE=/vmlinuz-3.10.9-200.fc19.x86_64 root=/dev/mapper/fedora_prosha-root ro rd.lvm.lv=fedora_prosha/swap rd.md=0 rd.dm=0 rd.luks=0 vconsole.keymap=us rd.lvm.lv=fedora_prosha/root rhgb quiet runlevel: N 5 type: Kerneloops Truncated backtrace: WARNING: at drivers/pci/pci.c:1393 pci_disable_device+0x84/0x90() Device e100 disabling already-disabled device Modules linked in: rfcomm bnep bluetooth rfkill nf_conntrack_netbios_ns nf_conntrack_broadcast ipt_MASQUERADE ip6table_nat nf_nat_ipv6 ip6table_mangle ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 iptable_nat nf_nat_ipv4 nf_nat iptable_mangle nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ebtable_filter ebtables ip6table_filter ip6_tables acpi_cpufreq mperf kvm_intel kvm snd_hda_codec_hdmi snd_hda_codec_idt snd_hda_intel snd_hda_codec snd_usb_audio snd_usbmidi_lib iTCO_wdt iTCO_vendor_support uvcvideo snd_rawmidi snd_hwdep snd_seq snd_seq_device snd_pcm videobuf2_vmalloc videobuf2_memops videobuf2_core videodev media snd_page_alloc snd_timer snd soundcore dcdbas serio_raw lpc_ich i2c_i801 microcode mfd_core e100 mii joydev uinput radeon i2c_algo_bit drm_kms_helper ttm drm i2c_core CPU: 1 PID: 17243 Comm: kworker/u8:4 Not tainted 3.10.5-201.fc19.x86_64 #1 Hardware name: Dell Inc. Dell DM051 /0HJ054, BIOS A07 01/08/2007 Workqueue: events_unbound async_run_entry_fn 0000000000000009 ffff8800a638dbf0 ffffffff81638f56 ffff8800a638dc28 ffffffff8105c211 ffff8800bac56000 ffff8800bac56000 ffff8800a638dce7 ffff8800372c4800 ffffffff81a31144 ffff8800a638dc88 ffffffff8105c27c Call Trace: [<ffffffff81638f56>] dump_stack+0x19/0x1b [<ffffffff8105c211>] warn_slowpath_common+0x61/0x80 [<ffffffff8105c27c>] warn_slowpath_fmt+0x4c/0x50 [<ffffffff813109d7>] ? pci_find_capability+0x47/0x50 [<ffffffff81312894>] pci_disable_device+0x84/0x90 [<ffffffffa0166c5e>] __e100_shutdown+0x8e/0x120 [e100] [<ffffffffa0166d5a>] e100_suspend+0x1a/0x30 [e100] [<ffffffff81313c98>] pci_legacy_suspend+0x38/0xc0 [<ffffffff81314f0d>] pci_pm_suspend+0xed/0x150 [<ffffffff81314e20>] ? pci_pm_freeze+0xc0/0xc0 [<ffffffff813e3294>] dpm_run_callback+0x44/0x90 [<ffffffff813e368b>] __device_suspend+0xdb/0x270 [<ffffffff813e383f>] async_suspend+0x1f/0xa0 [<ffffffff81087579>] async_run_entry_fn+0x39/0x120 [<ffffffff81079b95>] process_one_work+0x175/0x420 [<ffffffff8107a7ab>] worker_thread+0x11b/0x3a0 [<ffffffff8107a690>] ? rescuer_thread+0x340/0x340 [<ffffffff81080b00>] kthread+0xc0/0xd0 [<ffffffff81080a40>] ? insert_kthread_work+0x40/0x40 [<ffffffff816474ac>] ret_from_fork+0x7c/0xb0 [<ffffffff81080a40>] ? insert_kthread_work+0x40/0x40 *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs. Fedora 19 has now been rebased to 3.11.1-200.fc19. Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those. This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously. This problem continues with kernel version 3.11.6-201.fc19.i686. Please let me know what additional information is needed to help diagnose this problem. Also, does this report need to be cloned in order to re-open it? This problem continues with kernel version 3.11.7-200.fc19.i686. (In reply to Josh Boyer from comment #4) > This bug is being closed with INSUFFICIENT_DATA as there has not been a > response in 2 weeks. If you are still experiencing this issue, please reopen > and attach the relevant data from the latest kernel you are running and any > data that might have been requested previously. This problem continues with kernel version 3.11.8-200.fc19.i686. *** Bug 1033420 has been marked as a duplicate of this bug. *** Reopening as people are still seeing this Hi, I've brought this up on the intel driver ML. I will update here if there is any response hth, Michele This problem continues with kernel version 3.11.9-200.fc19.i686. This problem continues with kernel version 3.11.10-200.fc19.i686. Yes there are no changes for e100 in 3.11.X nor in 3.12.X. No comments from upstream on the report yet: https://www.mail-archive.com/e1000-devel@lists.sourceforge.net/msg08497.html I've opened https://sourceforge.net/p/e1000/bugs/387/ hth, Michele So that bug got closed as intel does not support e100. It is in community maintenance mode only.
Maybe something along the following could work:
diff --git a/drivers/net/ethernet/intel/e100.c b/drivers/net/ethernet/intel/e100.c
index cbaba44..bf7a01e 100644
--- a/drivers/net/ethernet/intel/e100.c
+++ b/drivers/net/ethernet/intel/e100.c
@@ -3034,7 +3034,7 @@ static void __e100_shutdown(struct pci_dev *pdev, bool *enable_wake)
*enable_wake = false;
}
- pci_disable_device(pdev);
+ pci_clear_master(pdev);
}
static int __e100_power_off(struct pci_dev *pdev, bool wake)
Mark, Fidel, can you reproduce this problem pretty quickly? Would you be able to test the patch above or do you need a pre-built kernel? regards, Michele If it is possible to get a pre-built kernel, that would be better so that I do not introduce any other errors into this problem. (Sorry for the delayed reply.) The problem continues pretty regularly with resuming from suspend, including kernel 3.12.6-200.fc19.i686. Similar problem here with 3.12.6-300.fc20.x86_64 echo OFF > /sys/kernel/debug/vgaswitcheroo/switch triggers a kernel panic with reason "WARNING: CPU: 0 PID: 2602 at drivers/pci/pci.c:1430 pci_disable_device+0x84/0x90()". I will attach the abrt stuff. Maybe this is related to https://bugzilla.redhat.com/show_bug.cgi?id=1045766 Created attachment 848252 [details]
kernel panic (abrt stuff)
(In reply to Michele Baldessari from comment #15) This problem continues in kernel 3.12.7-200.fc19.i686. > > Would you be able to test the patch above or do you need a pre-built kernel? > Would prefer a pre-built kernel so that another variable (improperly-built kernel) is not introduced. JannikV, please open a separate BZ for your issue (yours is sound driver related, here we track the network e100 driver) Mark, I'll spin a kernel this weekend and pass it along for testing Hi Mark, here we go: http://koji.fedoraproject.org/koji/taskinfo?taskID=6430954 kind regards, Michele *** Bug 1055245 has been marked as a duplicate of this bug. *** (In reply to Michele Baldessari from comment #21 > > here we go: http://koji.fedoraproject.org/koji/taskinfo?taskID=6430954 > Thank you. Unless I'm mistaken, these are all Fedora 20 kernels. Do you anticipate an incompatibilities, or can these RPMs be installed on Fedora 19? Hi Mark, it should be ok. But just in case I've spun a f19 build: http://koji.fedoraproject.org/koji/taskinfo?taskID=6436640 Michele (In reply to Michele Baldessari from comment #24) > > it should be ok. But just in case I've spun a f19 build: > http://koji.fedoraproject.org/koji/taskinfo?taskID=6436640 > Thank you. Installed new kernel and rebooted. Will check it for several days to see whether the problem recurs. Installed with: $ sudo yum install \ http://kojipkgs.fedoraproject.org/work/tasks/6643/6436643/kernel-3.12.8-300.bz994438.fc19.i686.rpm \ http://kojipkgs.fedoraproject.org/work/tasks/6643/6436643/kernel-headers-3.12.8-300.bz994438.fc19.i686.rpm \ http://kojipkgs.fedoraproject.org/work/tasks/6643/6436643/kernel-modules-extra-3.12.8-300.bz994438.fc19.i686.rpm (In reply to Michele Baldessari from comment #2) > > it should be ok. But just in case I've spun a f19 build: > http://koji.fedoraproject.org/koji/taskinfo?taskID=6436640 > After having this kernel installed for a week, I have not had a single instance of the error occurring. I rebooted with the previous kernel (version 3.12.7-200), and the problem still occurs. The fix that you have provided appears to work. Thank you. Patch posted to e1000-devel and netdev Patch has been committed upstream in the net tree via: commit 2b6e0ca175fe4a20f21ba82b1e7ccc71029c4dd4 Author: Michele Baldessari <michele> Date: Thu Jan 30 10:51:04 2014 +0000 Thanks again Mark for testing Description of problem: It happen when I re-started the computer, it was on sleep mode. When I re-started the warning showed. Version-Release number of selected component: kernel Additional info: reporter: libreport-2.1.11 cmdline: BOOT_IMAGE=/vmlinuz-3.12.9-301.fc20.i686+PAE root=UUID=996cc74b-23ae-478b-82be-5a3459cd53c2 ro vconsole.font=latarcyrheb-sun16 rhgb quiet LANG=en_US.UTF-8 kernel: 3.12.9-301.fc20.i686+PAE runlevel: N 5 type: Kerneloops Truncated backtrace: WARNING: CPU: 1 PID: 5392 at drivers/pci/pci.c:1430 pci_disable_device+0x85/0x90() Device e100 disabling already-disabled device Modules linked in: vfat fat usb_storage rfcomm ip6t_rpfilter ip6t_REJECT xt_conntrack ebtable_nat ebtable_broute bridge stp llc ebtable_filter ebtables ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw ip6table_filter ip6_tables iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw bnep coretemp kvm_intel kvm joydev btusb bluetooth microcode arc4 snd_hda_codec_conexant snd_hda_intel snd_hda_codec snd_hwdep snd_seq iwl3945 iwlegacy snd_seq_device snd_pcm iTCO_wdt iTCO_vendor_support hp_wmi sparse_keymap sdhci_pci serio_raw i2c_i801 e100 sdhci mii mac80211 r592 mmc_core snd_page_alloc memstick snd_timer lpc_ich cfg80211 rfkill snd mfd_core soundcore wmi acpi_cpufreq nfsd auth_rpcgss nfs_acl lockd sunrpc i915 firewire_ohci firewire_core ata_generic i2c_algo_bit pata_acpi drm_kms_helper crc_itu_t drm i2c_core video CPU: 1 PID: 5392 Comm: kworker/u4:3 Not tainted 3.12.9-301.fc20.i686+PAE #1 Hardware name: Hewlett-Packard HP Pavilion dv1000 (EX002LA#ABM) /30A0, BIOS F.09 02/16/2006 Workqueue: events_unbound async_run_entry_fn 00000000 00000000 d2409d88 c09b03d2 d2409dc8 d2409db8 c045572e c0b899c0 d2409de4 00001510 c0bb49f5 00000596 c06c5265 c06c5265 f5d9a000 f5d9a000 d2409e17 d2409dd0 c0455783 00000009 d2409dc8 c0b899c0 d2409de4 d2409dec Call Trace: [<c09b03d2>] dump_stack+0x41/0x52 [<c045572e>] warn_slowpath_common+0x7e/0xa0 [<c06c5265>] ? pci_disable_device+0x85/0x90 [<c06c5265>] ? pci_disable_device+0x85/0x90 [<c0455783>] warn_slowpath_fmt+0x33/0x40 [<c06c5265>] pci_disable_device+0x85/0x90 [<f85d7730>] __e100_shutdown+0x80/0x120 [e100] [<c0484e8d>] ? __enqueue_entity+0x6d/0x80 [<f85d7826>] e100_suspend+0x16/0x30 [e100] [<c06c67ab>] pci_legacy_suspend+0x2b/0xb0 [<c06c780c>] pci_pm_suspend+0xcc/0x120 [<c09b4aef>] ? wait_for_completion+0x1f/0xd0 [<c048a479>] ? enqueue_task_fair+0x559/0x760 [<c06c7740>] ? pci_pm_freeze+0xb0/0xb0 [<c078deba>] dpm_run_callback+0x3a/0x90 [<c078e222>] __device_suspend+0xb2/0x1f0 [<c078e37f>] async_suspend+0x1f/0x90 [<c04790b5>] async_run_entry_fn+0x35/0x140 [<c048125f>] ? wake_up_process+0x1f/0x40 [<c046c4f5>] process_one_work+0x115/0x380 [<c046a685>] ? start_worker+0x25/0x30 [<c046ce35>] ? manage_workers.isra.28+0x1a5/0x250 [<c046cfde>] worker_thread+0xfe/0x330 [<c046cee0>] ? manage_workers.isra.28+0x250/0x250 [<c0472734>] kthread+0x94/0xa0 [<c09bd437>] ret_from_kernel_thread+0x1b/0x28 [<c04726a0>] ? insert_kthread_work+0x30/0x30 Description of problem: Awaking from hibernation Version-Release number of selected component: kernel Additional info: reporter: libreport-2.1.12 cmdline: BOOT_IMAGE=/vmlinuz-3.13.3-201.fc20.i686+PAE root=/dev/mapper/luks-010f4c02-33b6-44ce-a4f0-63925cea74ea ro rd.luks.uuid=luks-010f4c02-33b6-44ce-a4f0-63925cea74ea vconsole.font=latarcyrheb-sun16 rd.luks.uuid=luks-075be9c3-0630-47b5-bc59-76a2c93f0c26 rhgb quiet LANG=en_US.UTF-8 kernel: 3.13.3-201.fc20.i686+PAE runlevel: N 5 type: Kerneloops Truncated backtrace: WARNING: CPU: 1 PID: 28806 at drivers/pci/pci.c:1431 pci_disable_device+0x97/0xa0() e100 0000:06:08.0: disabling already-disabled device Modules linked in: xfs btrfs raid6_pq libcrc32c xor nls_utf8 isofs usb_storage fuse ccm ip6t_rpfilter ip6t_REJECT xt_conntrack ebtable_nat ebtable_broute bridge stp llc ebtable_filter ebtables ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw ip6table_filter ip6_tables iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw bnep rt2800usb rt2x00usb arc4 iwl3945 rt2800lib iwlegacy rt2x00lib mac80211 coretemp crc_ccitt kvm_intel kvm iTCO_wdt iTCO_vendor_support cfg80211 btusb bluetooth rfkill microcode serio_raw i2c_i801 e100 mii sdhci_pci sdhci mmc_core lpc_ich mfd_core lm63 video acpi_cpufreq nfsd auth_rpcgss nfs_acl lockd sunrpc dm_crypt radeon firewire_ohci i2c_algo_bit ata_generic drm_kms_helper pata_acpi ttm firewire_core drm crc_itu_t i2c_core CPU: 1 PID: 28806 Comm: kworker/u4:6 Not tainted 3.13.3-201.fc20.i686+PAE #1 Hardware name: PACKARD BELL BV EasyNote MV85 /EasyNote MV85 , BIOS R1.15 09/11/2006 Workqueue: events_unbound async_run_entry_fn 00000000 00000000 e158bd98 c09c3036 e158bdd8 e158bdc8 c04560ce c0b9f898 e158bdf4 00007086 c0bcaec4 00000597 c06d0c57 c06d0c57 f51ac000 f5184bb0 e158be2f e158bde0 c0456123 00000009 e158bdd8 c0b9f898 e158bdf4 e158be04 Call Trace: [<c09c3036>] dump_stack+0x41/0x52 [<c04560ce>] warn_slowpath_common+0x7e/0xa0 [<c06d0c57>] ? pci_disable_device+0x97/0xa0 [<c06d0c57>] ? pci_disable_device+0x97/0xa0 [<c0456123>] warn_slowpath_fmt+0x33/0x40 [<c06d0c57>] pci_disable_device+0x97/0xa0 [<f82cc730>] __e100_shutdown+0x80/0x120 [e100] [<f82cc826>] e100_suspend+0x16/0x30 [e100] [<c06d21cb>] pci_legacy_suspend+0x2b/0xb0 [<c04891e5>] ? put_prev_task_fair+0x55/0x4a0 [<c09c6c6f>] ? wait_for_completion+0x1f/0xd0 [<c06d2fd0>] ? pci_pm_poweroff+0xc0/0xc0 [<c06d3074>] pci_pm_freeze+0xa4/0xb0 [<c06d2fd0>] ? pci_pm_poweroff+0xc0/0xc0 [<c079a9ba>] dpm_run_callback+0x3a/0x90 [<c079ad22>] __device_suspend+0xb2/0x1f0 [<c079ae7f>] async_suspend+0x1f/0x90 [<c0478df5>] async_run_entry_fn+0x35/0x140 [<c048100f>] ? wake_up_process+0x1f/0x40 [<c046cfe5>] process_one_work+0x115/0x380 [<c046b275>] ? start_worker+0x25/0x30 [<c046d935>] ? manage_workers.isra.28+0x1a5/0x250 [<c046dade>] worker_thread+0xfe/0x330 [<c046d9e0>] ? manage_workers.isra.28+0x250/0x250 [<c0473271>] kthread+0xa1/0xc0 [<c09d01b7>] ret_from_kernel_thread+0x1b/0x28 [<c04731d0>] ? insert_kthread_work+0x30/0x30 git tag --contains 2b6e0ca175fe4a20f21ba82b1e7ccc71029c4dd4 v3.14-rc3 I'll let Josh decide if it makes sense to pull it in before 3.14 hits Fedora or not Sure, we'll grab that. Sorry for not doing it sooner. Applied in git. Thanks again! kernel-3.13.5-200.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/kernel-3.13.5-200.fc20 kernel-3.13.5-101.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/FEDORA-2014-2887/kernel-3.13.5-101.fc19 Package kernel-3.13.5-200.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing kernel-3.13.5-200.fc20' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-3094/kernel-3.13.5-200.fc20 then log in and leave karma (feedback). (In reply to Fedora Update System from comment #36) > Package kernel-3.13.5-200.fc20: > * should fix your issue, > * was pushed to the Fedora 20 testing repository, > * should be available at your local mirror within two days. > Update it with: > # su -c 'yum update --enablerepo=updates-testing kernel-3.13.5-200.fc20' > as soon as you are able to, then reboot. > Please go to the following url: > https://admin.fedoraproject.org/updates/FEDORA-2014-3094/kernel-3.13.5-200. > fc20 > then log in and leave karma (feedback). Installed 'kernel' and 'kernel-modules-extra' for FC19 using yum update --enablerepo=updates-testing kernel-3.13.5-101.fc19 Will test for several days and report back. kernel-3.13.5-200.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report. kernel-3.13.5-101.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. |