public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Chiang <achiang@canonical.com>
To: David Miller <davem@davemloft.net>
Cc: mikpe@it.uu.se, 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, 1 Jun 2010 21:09:25 -0600	[thread overview]
Message-ID: <20100602030925.GA3402@canonical.com> (raw)
In-Reply-To: <20100601.153105.90813554.davem@davemloft.net>

* David Miller <davem@davemloft.net>:
> 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.
 
I haven't been able to reproduce this yet (trying with kvm, not
successful with bare metal), but one thing I've noticed is that
it occurs when either a PCI hotplug driver or the ACPI PCI slot
detection driver is loaded.

It's obviously because we have both

drivers/pci/pci-sysfs.c: pci_create_slot_links()

and

drivers/pci/slot.c: create_sysfs_files()

But what I'm trying to figure out is why I'm not seeing this on
x86 bare metal (although it does supposedly reproduce in x86
kvm).

Does sparc64 load any PCI hotplug drivers?

Thanks,
/ac

  parent reply	other threads:[~2010-06-02  3:09 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
2010-06-01 22:51   ` Mikael Pettersson
2010-06-02  3:09   ` Alex Chiang [this message]
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=20100602030925.GA3402@canonical.com \
    --to=achiang@canonical.com \
    --cc=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