Bug 1414656
Summary: | [abrt] WARNING: CPU: 0 PID: 687 at fs/sysfs/dir.c:31 sysfs_warn_dup+0x62/0x80 | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Dan Loomis <danloomis47> | ||||||
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: | 25 | CC: | aurelien, bughunt, cz172638, gansalmon, ichavero, itamar, james, jforbes, jonathan, kernel-maint, madhu.chinakonda, mchehab, mikhail.v.gavrilov | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | x86_64 | ||||||||
OS: | Unspecified | ||||||||
URL: | https://retrace.fedoraproject.org/faf/reports/bthash/1687d9b35372099c02d867be97f04727d003f8e2 | ||||||||
Whiteboard: | abrt_hash:a9db939cb9bacea8d5a9f20dbec9e2825b46c715;VARIANT_ID=workstation; | ||||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2017-04-13 14:44:38 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
Dan Loomis
2017-01-19 07:22:43 UTC
Created attachment 1242386 [details]
File: dmesg
Getting this on my trusty Fedora 24 since Jan 24 (so some upgrade prior to this introduced a problem) during boot, Not otherwise a problem (I think) In the kernel log: parport_pc 00:08: reported by Plug and Play ACPI parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE,EPP] md: raid1 personality registered for level 1 acpi_cpufreq: P-state transition latency capped at 20 uS md/raid1:md127: active with 2 out of 2 mirrors created bitmap (8 pages) for device md127 md127: bitmap initialized from disk: read 1 pages, set 0 of 14718 bits ppdev: user-space parallel port driver iTCO_vendor_support: vendor-support=0 iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11 iTCO_wdt: Found a ICH10R TCO device (Version=2, TCOBASE=0x1060) iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) md127: detected capacity change from 0 to 987708260352 ------------[ cut here ]------------ WARNING: CPU: 7 PID: 557 at fs/sysfs/dir.c:31 sysfs_warn_dup+0x62/0x80 sysfs: cannot create duplicate filename '/devices/pnp0/00:08/ppdev/parport0' Modules linked in: irqbypass iTCO_wdt iTCO_vendor_support intel_cstate ppdev intel_uncore tpm_infineon(+) acpi_cpufreq raid1 i2c_i801 i2c_smbus lpc_ich snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hda_core CPU: 7 PID: 557 Comm: systemd-udevd Tainted: G I 4.9.4-100.fc24.x86_64 #1 Hardware name: FUJITSU D2778-C1 /D2778-C1, BIOS 6.00 R1.22.2778.C1 12/19/2011 ffffaeca044f7698 ffffffff903f3ddd ffffaeca044f76e8 0000000000000000 ffffaeca044f76d8 ffffffff900a202b 0000001fff55b000 ffff9930ff55b000 ffff9930fe9f8730 ffff9931024e9f78 ffff9930fe900400 0000000006300000 Call Trace: [<ffffffff903f3ddd>] dump_stack+0x63/0x86 [<ffffffff900a202b>] __warn+0xcb/0xf0 [<ffffffff900a20af>] warn_slowpath_fmt+0x5f/0x80 [<ffffffff902de9df>] ? kernfs_path_from_node+0x4f/0x60 [<ffffffff902e21c2>] sysfs_warn_dup+0x62/0x80 [<ffffffff902e22a7>] sysfs_create_dir_ns+0x77/0x90 [<ffffffff903f671b>] kobject_add_internal+0x9b/0x320 [<ffffffff9040057a>] ? vsnprintf+0x20a/0x500 [<ffffffff903f6ec5>] kobject_add+0x75/0xd0 [<ffffffff90547d73>] ? device_private_init+0x23/0x70 [<ffffffff90819ce2>] ? mutex_lock+0x12/0x30 [<ffffffff90547f11>] device_add+0x151/0x630 [<ffffffff905485e0>] device_create_groups_vargs+0xe0/0xf0 [<ffffffffc0650060>] ? dead_read+0x10/0x10 [parport] [<ffffffff90548661>] device_create+0x51/0x70 [<ffffffff9080e901>] ? klist_next+0x21/0xf0 [<ffffffffc024b0b2>] pp_attach+0x32/0x40 [ppdev] [<ffffffffc0650077>] driver_check+0x17/0x20 [parport] [<ffffffff90549207>] bus_for_each_drv+0x67/0xb0 [<ffffffffc0650329>] attach_driver_chain+0x59/0x60 [parport] [<ffffffffc06503e9>] parport_announce_port+0xb9/0x100 [parport] [<ffffffffc0575fbb>] parport_pc_probe_port+0x72b/0xcc0 [parport_pc] [<ffffffff905472ac>] ? __dev_printk+0x3c/0x80 [<ffffffff905477bc>] ? _dev_info+0x6c/0x90 [<ffffffffc0576903>] parport_pc_pnp_probe+0x143/0x1e0 [parport_pc] [<ffffffffc05767c0>] ? parport_pc_pci_probe+0x270/0x270 [parport_pc] [<ffffffff904c4b15>] pnp_device_probe+0x65/0xc0 [<ffffffff9054b743>] driver_probe_device+0x223/0x430 [<ffffffff9054ba2f>] __driver_attach+0xdf/0xf0 [<ffffffff9054b950>] ? driver_probe_device+0x430/0x430 [<ffffffff9054912c>] bus_for_each_dev+0x6c/0xc0 [<ffffffff9054ae8e>] driver_attach+0x1e/0x20 [<ffffffff9054a8c0>] bus_add_driver+0x170/0x270 [<ffffffff9054c350>] driver_register+0x60/0xe0 [<ffffffff904c4950>] pnp_register_driver+0x20/0x30 [<ffffffffc057d3a3>] parport_pc_init+0x2c6/0xf23 [parport_pc] [<ffffffffc057d0dd>] ? parport_parse_param.constprop.14+0xdd/0xdd [parport_pc] [<ffffffff90002190>] do_one_initcall+0x50/0x180 [<ffffffff9022f2b9>] ? kmem_cache_alloc_trace+0x159/0x1b0 [<ffffffff901c017a>] ? do_init_module+0x27/0x1ef [<ffffffff901c01b2>] do_init_module+0x5f/0x1ef [<ffffffff9012fe01>] load_module+0x25b1/0x2980 [<ffffffff9012c6e0>] ? __symbol_put+0x60/0x60 [<ffffffff90130343>] SYSC_init_module+0x173/0x190 [<ffffffff9013047e>] SyS_init_module+0xe/0x10 [<ffffffff90003c17>] do_syscall_64+0x67/0x180 [<ffffffff9081cd2b>] entry_SYSCALL64_slow_path+0x25/0x25 ---[ end trace 64ac09bf34fc473d ]--- ------------[ cut here ]------------ WARNING: CPU: 7 PID: 557 at lib/kobject.c:240 kobject_add_internal+0x2b6/0x320 kobject_add_internal failed for parport0 with -EEXIST, don't try to register things with the same name in the same directory. Modules linked in: irqbypass iTCO_wdt iTCO_vendor_support intel_cstate ppdev intel_uncore tpm_infineon(+) acpi_cpufreq raid1 i2c_i801 i2c_smbus lpc_ich snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hda_core CPU: 7 PID: 557 Comm: systemd-udevd Tainted: G W I 4.9.4-100.fc24.x86_64 #1 Hardware name: FUJITSU D2778-C1 /D2778-C1, BIOS 6.00 R1.22.2778.C1 12/19/2011 ffffaeca044f76e8 ffffffff903f3ddd ffffaeca044f7738 0000000000000000 ffffaeca044f7728 ffffffff900a202b 000000f0044f7750 ffff9930fe900410 0000000000000000 ffff993102ac90c0 00000000ffffffef 0000000006300000 Call Trace: [<ffffffff903f3ddd>] dump_stack+0x63/0x86 [<ffffffff900a202b>] __warn+0xcb/0xf0 [<ffffffff900a20af>] warn_slowpath_fmt+0x5f/0x80 [<ffffffff902e21ca>] ? sysfs_warn_dup+0x6a/0x80 [<ffffffff903f6936>] kobject_add_internal+0x2b6/0x320 [<ffffffff9040057a>] ? vsnprintf+0x20a/0x500 [<ffffffff903f6ec5>] kobject_add+0x75/0xd0 [<ffffffff90547d73>] ? device_private_init+0x23/0x70 [<ffffffff90819ce2>] ? mutex_lock+0x12/0x30 [<ffffffff90547f11>] device_add+0x151/0x630 [<ffffffff905485e0>] device_create_groups_vargs+0xe0/0xf0 [<ffffffffc0650060>] ? dead_read+0x10/0x10 [parport] [<ffffffff90548661>] device_create+0x51/0x70 [<ffffffff9080e901>] ? klist_next+0x21/0xf0 [<ffffffffc024b0b2>] pp_attach+0x32/0x40 [ppdev] [<ffffffffc0650077>] driver_check+0x17/0x20 [parport] [<ffffffff90549207>] bus_for_each_drv+0x67/0xb0 [<ffffffffc0650329>] attach_driver_chain+0x59/0x60 [parport] [<ffffffffc06503e9>] parport_announce_port+0xb9/0x100 [parport] [<ffffffffc0575fbb>] parport_pc_probe_port+0x72b/0xcc0 [parport_pc] [<ffffffff905472ac>] ? __dev_printk+0x3c/0x80 [<ffffffff905477bc>] ? _dev_info+0x6c/0x90 [<ffffffffc0576903>] parport_pc_pnp_probe+0x143/0x1e0 [parport_pc] [<ffffffffc05767c0>] ? parport_pc_pci_probe+0x270/0x270 [parport_pc] [<ffffffff904c4b15>] pnp_device_probe+0x65/0xc0 [<ffffffff9054b743>] driver_probe_device+0x223/0x430 [<ffffffff9054ba2f>] __driver_attach+0xdf/0xf0 [<ffffffff9054b950>] ? driver_probe_device+0x430/0x430 [<ffffffff9054912c>] bus_for_each_dev+0x6c/0xc0 [<ffffffff9054ae8e>] driver_attach+0x1e/0x20 [<ffffffff9054a8c0>] bus_add_driver+0x170/0x270 [<ffffffff9054c350>] driver_register+0x60/0xe0 [<ffffffff904c4950>] pnp_register_driver+0x20/0x30 [<ffffffffc057d3a3>] parport_pc_init+0x2c6/0xf23 [parport_pc] [<ffffffffc057d0dd>] ? parport_parse_param.constprop.14+0xdd/0xdd [parport_pc] [<ffffffff90002190>] do_one_initcall+0x50/0x180 [<ffffffff9022f2b9>] ? kmem_cache_alloc_trace+0x159/0x1b0 [<ffffffff901c017a>] ? do_init_module+0x27/0x1ef [<ffffffff901c01b2>] do_init_module+0x5f/0x1ef [<ffffffff9012fe01>] load_module+0x25b1/0x2980 [<ffffffff9012c6e0>] ? __symbol_put+0x60/0x60 [<ffffffff90130343>] SYSC_init_module+0x173/0x190 [<ffffffff9013047e>] SyS_init_module+0xe/0x10 [<ffffffff90003c17>] do_syscall_64+0x67/0x180 [<ffffffff9081cd2b>] entry_SYSCALL64_slow_path+0x25/0x25 ---[ end trace 64ac09bf34fc473e ]--- The bug is fixed with the commit dd5c472a60e43549d789a17a8444513eec64bd7e in the upstream kernel. Thanks Aurelien $ uname -r 4.9.12-200.fc25.x86_64+debug still observed this problem with latest debug kernel Same error seen with Arch Linux kernels, since 4.9-1, and into 4.10.1-1, on an Asustek P5W DH Deluxe, Intel Core2. Clearly, the referenced commit does not fix the problem, which persists: commit dd5c472a60e43549d789a17a8444513eec64bd7e Author: Sudip Mukherjee <sudipm.mukherjee> Date: Sat Nov 12 21:22:12 2016 +0000 ppdev: check before attaching port Sudip has provided a patch for the kernel warning, and this will be applied to both 4.10 and 4.9 LTS. For anyone who cannot wait, the patch is attached. Created attachment 1260561 [details]
kernel warning patch to ppdev.c and parport/share.c
The patch did not go into 4.10.2 or 4.9.14. GKH has added the patch set to his "char-misc git tree which can be found at git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git in the char-misc-linus branch." The parport and ppdev printing patches have been applied at linux 4.10.7. The parport patch has been applied at 4.9.19, but the ppdev patch for 4.9.19 needed modification to accomodate changes in ppdev.c, and still waits. GKH has also applied the parport patch to 4.4.58, though I don't know how that works without also applying the ppdev.c patch there. *********** 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 25 kernel bugs. Fedora 25 has now been rebased to 4.10.9-200.fc25. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26. If you experience different issues, please open a new bug report for those. The ppdev patch has now been applied in 4.9.22. This issue has been fixed upstream, from 4.10.7 and from 4.9.22. |