Bug 1921485 - sysfs: cannot create duplicate filename '/bus/nvmem/devices/module-vpd' (and others)
Summary: sysfs: cannot create duplicate filename '/bus/nvmem/devices/module-vpd' (and ...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 33
Hardware: ppc64le
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: PPCTracker 1927627
TreeView+ depends on / blocked
 
Reported: 2021-01-28 04:01 UTC by Cameron Kaiser
Modified: 2022-03-26 12:53 UTC (History)
22 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1927627 (view as bug list)
Environment:
Last Closed: 2021-11-30 19:03:00 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Cameron Kaiser 2021-01-28 04:01:30 UTC
1. Please describe the problem:

Multiple warnings with sysfs creating duplicate nodes on ppc64le (also might be occuring with s390x). Typical appearance in dmesg is

[   10.839513] sysfs: cannot create duplicate filename '/bus/nvmem/devices/module-vpd'
[   10.843750] CPU: 29 PID: 1089 Comm: systemd-udevd Not tainted 5.10.9-201.fc33.ppc64le #1
[   10.843752] Call Trace:
[   10.843757] [c0002000110970a0] [c000000000acfb00] dump_stack+0xc4/0x114 (unreliable)
[   10.855893] [c0002000110970f0] [c0000000006b8768] sysfs_warn_dup+0x88/0xc0
[   10.855897] [c000200011097170] [c0000000006b8cdc] sysfs_create_link+0x18c/0x1b0
[   10.855900] [c0002000110971b0] [c000000000c8cc24] bus_add_device+0x94/0x1e0
[   10.855903] [c000200011097230] [c000000000c85734] device_add+0x434/0xc10
[   10.855906] [c000200011097300] [c000000000fc2aa8] nvmem_register+0x1f8/0x1030
[   10.855909] [c000200011097400] [c000000000fc3944] devm_nvmem_register+0x64/0xd0
[   10.855917] [c000200011097440] [c0080000090e0dec] at24_probe+0x694/0x920 [at24]
[   10.855925] [c0002000110976a0] [c008000007282064] i2c_device_probe+0x18c/0x630 [i2c_core]
[   10.855927] [c000200011097740] [c000000000c8e8c4] really_probe+0x134/0x7d0
[   10.855930] [c0002000110977f0] [c000000000c8f59c] driver_probe_device+0x14c/0x1f0
[   10.855932] [c000200011097870] [c000000000c8fbb8] __driver_attach+0x1f8/0x2d0
[   10.855936] [c0002000110978f0] [c000000000c8adac] bus_for_each_dev+0x9c/0xf0
[   10.855938] [c000200011097940] [c000000000c8dd64] driver_attach+0x34/0x50
[   10.855941] [c000200011097960] [c000000000c8d2a8] bus_add_driver+0x1d8/0x2f0
[   10.855944] [c0002000110979f0] [c000000000c911e4] driver_register+0xb4/0x1c0
[   10.855949] [c000200011097a60] [c00800000728339c] i2c_register_driver+0x74/0x120 [i2c_core]
[   10.855953] [c000200011097ae0] [c0080000090e1244] at24_init+0x6c/0x88 [at24]
[   10.855955] [c000200011097b40] [c000000000011fe0] do_one_initcall+0x60/0x2c0
[   10.855958] [c000200011097c10] [c0000000002935dc] do_init_module+0x7c/0x300
[   10.855961] [c000200011097ca0] [c000000000298040] __do_sys_init_module+0x200/0x250
[   10.855963] [c000200011097dc0] [c000000000034254] system_call_exception+0xe4/0x1c0

This may be the same as this upstream report: https://bugzilla.kernel.org/show_bug.cgi?id=210749

2. What is the Version-Release number of the kernel:

Linux censored.floodgap.com 5.10.9-201.fc33.ppc64le #1 SMP Wed Jan 20 16:40:55 UTC 2021 ppc64le ppc64le ppc64le GNU/Linux

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :

First appeared in 5.10.

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:

Reproduces readily on every boot.

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:

Yes, occurs with 5.11-rc.

6. Are you running any modules that not shipped with directly Fedora's kernel?:

No.

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.

Relevant portion quoted above, advise if more examples requested.

Comment 1 Dan Horák 2021-01-28 07:46:37 UTC
pasting output from 5.10.8-100.fc32.ppc64le with a slightly more context

[   11.888316] EXT4-fs (dm-0): re-mounted. Opts: (null)
[   12.011054] systemd-journald[1293]: Received client request to flush runtime journal.
[   13.878757] IPMI message handler: version 39.2
[   14.040237] ipmi device interface
[   14.111474] ses 8:3:123:0: Attached Enclosure device
[   14.126773] rtc-opal opal-rtc: registered as rtc0
[   14.131875] ipmi-powernv ibm,opal:ipmi: IPMI message handler: Found new BMC (man_id: 0x00cb06, prod_id: 0x0001, dev_id: 0x00)
[   14.142375] at24 8-0050: supply vcc not found, using dummy regulator
[   14.143208] at24 8-0050: 65536 byte 24c512 EEPROM, writable, 1 bytes/write
[   14.143255] at24 9-0050: supply vcc not found, using dummy regulator
[   14.143312] sysfs: cannot create duplicate filename '/bus/nvmem/devices/module-vpd'
[   14.143317] CPU: 43 PID: 1372 Comm: systemd-udevd Not tainted 5.10.8-100.fc32.ppc64le #1
[   14.143320] Call Trace:
[   14.143328] [c0002000262c30a0] [c000000000acf260] dump_stack+0xc4/0x114 (unreliable)
[   14.143336] [c0002000262c30f0] [c0000000006b8428] sysfs_warn_dup+0x88/0xc0
[   14.143340] [c0002000262c3170] [c0000000006b899c] sysfs_create_link+0x18c/0x1b0
[   14.143345] [c0002000262c31b0] [c000000000c8c384] bus_add_device+0x94/0x1e0
[   14.143350] [c0002000262c3230] [c000000000c84e94] device_add+0x434/0xc10
[   14.143355] [c0002000262c3300] [c000000000fc2128] nvmem_register+0x1f8/0x1030
[   14.143359] [c0002000262c3400] [c000000000fc2fc4] devm_nvmem_register+0x64/0xd0
[   14.143366] [c0002000262c3440] [c008000007640dec] at24_probe+0x694/0x920 [at24]
[   14.143373] [c0002000262c36a0] [c008000006ee2064] i2c_device_probe+0x18c/0x630 [i2c_core]
[   14.143377] [c0002000262c3740] [c000000000c8e024] really_probe+0x134/0x7d0
[   14.143380] [c0002000262c37f0] [c000000000c8ecfc] driver_probe_device+0x14c/0x1f0
[   14.143384] [c0002000262c3870] [c000000000c8f318] __driver_attach+0x1f8/0x2d0
[   14.143389] [c0002000262c38f0] [c000000000c8a50c] bus_for_each_dev+0x9c/0xf0
[   14.143392] [c0002000262c3940] [c000000000c8d4c4] driver_attach+0x34/0x50
[   14.143396] [c0002000262c3960] [c000000000c8ca08] bus_add_driver+0x1d8/0x2f0
[   14.143400] [c0002000262c39f0] [c000000000c90944] driver_register+0xb4/0x1c0
[   14.143406] [c0002000262c3a60] [c008000006ee339c] i2c_register_driver+0x74/0x120 [i2c_core]
[   14.143411] [c0002000262c3ae0] [c008000007641244] at24_init+0x6c/0x88 [at24]
[   14.143416] [c0002000262c3b40] [c000000000011fe0] do_one_initcall+0x60/0x2c0
[   14.143421] [c0002000262c3c10] [c0000000002935bc] do_init_module+0x7c/0x300
[   14.143425] [c0002000262c3ca0] [c000000000298020] __do_sys_init_module+0x200/0x250
[   14.143429] [c0002000262c3dc0] [c000000000034254] system_call_exception+0xe4/0x1c0
[   14.143433] [c0002000262c3e20] [c00000000000d260] system_call_common+0xf0/0x27c
[   14.143516] at24: probe of 9-0050 failed with error -17
[   14.143537] at24 10-0050: supply vcc not found, using dummy regulator
[   14.143589] sysfs: cannot create duplicate filename '/bus/nvmem/devices/module-vpd'
[   14.143592] CPU: 43 PID: 1372 Comm: systemd-udevd Not tainted 5.10.8-100.fc32.ppc64le #1
[   14.143594] Call Trace:
[   14.143598] [c0002000262c30a0] [c000000000acf260] dump_stack+0xc4/0x114 (unreliable)
[   14.143603] [c0002000262c30f0] [c0000000006b8428] sysfs_warn_dup+0x88/0xc0
[   14.143607] [c0002000262c3170] [c0000000006b899c] sysfs_create_link+0x18c/0x1b0
[   14.143611] [c0002000262c31b0] [c000000000c8c384] bus_add_device+0x94/0x1e0
[   14.143615] [c0002000262c3230] [c000000000c84e94] device_add+0x434/0xc10
[   14.143619] [c0002000262c3300] [c000000000fc2128] nvmem_register+0x1f8/0x1030
[   14.143623] [c0002000262c3400] [c000000000fc2fc4] devm_nvmem_register+0x64/0xd0
[   14.143628] [c0002000262c3440] [c008000007640dec] at24_probe+0x694/0x920 [at24]
[   14.143634] [c0002000262c36a0] [c008000006ee2064] i2c_device_probe+0x18c/0x630 [i2c_core]
[   14.143638] [c0002000262c3740] [c000000000c8e024] really_probe+0x134/0x7d0

Comment 2 Dan Horák 2021-08-02 15:59:19 UTC
seems it went away with kernel-5.14.0-0.rc3.29.fc35.ppc64le, but was still there with kernel-5.14.0-0.rc2.23.fc35.ppc64le

Comment 3 Ben Cotton 2021-11-04 13:49:12 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Ben Cotton 2021-11-04 14:18:35 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Ben Cotton 2021-11-04 15:16:18 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Ben Cotton 2021-11-30 19:03:00 UTC
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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