Bug 1443678 - sysfs: cannot create duplicate filename
Summary: sysfs: cannot create duplicate filename
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 25
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-19 17:29 UTC by Braxton Huggins
Modified: 2019-01-26 03:10 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-12 10:15:41 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
section from dmesg with the bug (3.11 KB, text/plain)
2017-04-19 17:29 UTC, Braxton Huggins
no flags Details

Description Braxton Huggins 2017-04-19 17:29:29 UTC
Created attachment 1272688 [details]
section from dmesg with the bug

Description of problem:

When scanning for hardware to load drivers and things, I get an error:
  sysfs: cannot create duplicate filename '/devices/pci0000:00/0000:00:02.0/0000:01:00.0/0000:02:00.0/0000:03:00.0/0000:04:02.0/revision'
As far as I can tell that's my SAS controller. That 

Version-Release number of selected component (if applicable):
4.10.10-200.fc25.x86_64
also with
4.10.9-200.fc25.x86_64
4.10.8-200.fc25.x86_64
seems to work fine with
4.9.x

How reproducible:
Happens every time I boot the machine

Steps to Reproduce:
1. Upgrade kernel to 4.10.x
2. Reboot
3. no SAS

Actual results:

Only my SATA drives show up

Expected results:

All of my drives get detected

Additional info:

After the sysfs error I get:
  [    4.822796] aic94xx: probe of 0000:04:02.0 failed with error -17

Comment 1 Fedora End Of Life 2017-11-16 19:00:50 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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 '25'.

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 25 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 2 Fedora End Of Life 2017-12-12 10:15:41 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.

Comment 3 bugsredhat 2017-12-20 03:32:47 UTC
We have the same bug on another distribution, Proxmox 5, with kernel 4.13.x! With kernel 4.4.x all works well.

It seems to be a kernel bug with aic94xx which is still not fixed?!

We are forced to run an old 4.4.x kernel until this problem is fixed as our system disks are SAS disk connected to an aic9xx (it's the AIC-9410W SAS/SATA Host Adapter).

Any news? Whom to contact?

Comment 4 Pablo Ruiz García 2019-01-26 03:10:31 UTC
Hi,

I've stumbled upon this very same issue, and have created a github repo with a fix for the actual issue (see git commit's description for bug details).

https://github.com/pruiz/aic94xx-hotfix

Hope it helps someone.

Best Regards


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