From: David Miller <davem@davemloft.net>
To: mikpe@it.uu.se
Cc: linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org
Subject: Re: [2.6.35-rc1 regression] sysfs: cannot create duplicate filename ... XVR-600 related?
Date: Tue, 01 Jun 2010 15:31:05 -0700 (PDT) [thread overview]
Message-ID: <20100601.153105.90813554.davem@davemloft.net> (raw)
In-Reply-To: <19461.26166.427857.612983@pilspetsen.it.uu.se>
From: Mikael Pettersson <mikpe@it.uu.se>
Date: Tue, 1 Jun 2010 21:57:42 +0200
> Booting 2.6.35-rc1 on a Sun Blade 2500 Red, I'm greeted with:
I know about the problem and will look at it soon hopefully, I see it
on some of my sparc64 boxes too.
You'll also have better luck reporting this to the proper mailing
list, which is sparclinux@vger.kernel.org, added to the CC:
> ------------[ cut here ]------------
> WARNING: at fs/sysfs/dir.c:451 sysfs_add_one+0x74/0x90()
> sysfs: cannot create duplicate filename '/devices/root/f0079a58/pci0003:00/0003:00:02.0/slot'
> Modules linked in:
> Call Trace:
> [0000000000458e20] warn_slowpath_fmt+0x2c/0x3c
> [0000000000501dac] sysfs_add_one+0x74/0x90
> [0000000000502cd4] sysfs_do_create_link+0xf0/0x184
> [000000000055a62c] pci_create_sysfs_dev_files+0x304/0x428
> [000000000074c6f8] pci_sysfs_init+0x20/0x6c
> [0000000000426acc] do_one_initcall+0x44/0x164
> [000000000073a32c] kernel_init+0x1a0/0x238
> [000000000042aea4] kernel_thread+0x30/0x48
> [0000000000640efc] rest_init+0x18/0x88
> ---[ end trace 8093a3146373dac8 ]---
>
> (There are no interesting messages before or after this one.)
>
> The device at 003:00:02.0 is a Sun XVR-600 graphics card, driven by
> drivers/video/sunxvr500.c. There was no such warning in 2.6.34 or
> earlier kernels.
next prev parent reply other threads:[~2010-06-01 22:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-01 19:57 [2.6.35-rc1 regression] sysfs: cannot create duplicate filename ... XVR-600 related? Mikael Pettersson
2010-06-01 20:06 ` Brian Bloniarz
2010-06-01 22:31 ` David Miller [this message]
2010-06-01 22:51 ` Mikael Pettersson
2010-06-02 3:09 ` Alex Chiang
2010-06-02 3:53 ` Alex Chiang
2010-06-02 9:08 ` David Miller
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=20100601.153105.90813554.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
--cc=sparclinux@vger.kernel.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