From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: EC seen at boot doesn't unplug
Date: Sun, 05 Jun 2011 05:42:45 +0000 [thread overview]
Message-ID: <20110605054245.GA11876@kroah.com> (raw)
In-Reply-To: <BANLkTik4-LrnWKqa5bB2dN_hHvKxswseNQ@mail.gmail.com>
On Sat, Jun 04, 2011 at 10:07:25PM -0500, Carl Karsten wrote:
> On Sat, Jun 4, 2011 at 8:41 PM, Greg KH <greg@kroah.com> wrote:
> > On Sat, Jun 04, 2011 at 10:26:27AM -0500, Carl Karsten wrote:
> >> I am wondering why I see a difference between 2 similar setups:
> >> ubuntu 2.6.39-3-generic
> >> EC card (many firewire cards)
> >>
> >> I have 2 laptops. 2.6.39-3-generic on both.
> >>
> >> HP EliteBook 8530w (KS051UA#ABA)
> >> HP Pavilion dv6700 Notebook PC (KC300UA#ABA)
> >>
> >> On the EliteBook, hotplug works: lspci entries come and go, modules
> >> un/load, udev reports add/remove. good.
> >>
> >> On the Pavilion, if I load acpiphp (via /etc/modules), hotplug works.
> >> If I don't load any additional modules hotplug does not work: insert
> >> card - nothing in syslog, lspci, udev. If a card is in the slot when
> >> the kernel loads, it shows in syslog, lscpi and the drivers get
> >> loaded. If I pull it out, nothing changes: still listed in lspci,
> >> modules still loaded, dev nodes still around.
> >
> > Try pciehp instead of acpiphp, that's usually used for "newer" systems.
> >
> > Let us know if that works or not.
> >
>
> Dose not work: It's included in the kernel.
>
> [ 0.560605] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Ok, try posting this on the linux-pci@vger.kernel.org list, that's where
the PCI hotplug people are at, not here.
good luck,
greg k-h
prev parent reply other threads:[~2011-06-05 5:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-04 15:26 EC seen at boot doesn't unplug Carl Karsten
2011-06-05 1:41 ` Greg KH
2011-06-05 3:07 ` Carl Karsten
2011-06-05 3:28 ` Carl Karsten
2011-06-05 5:42 ` Greg KH [this message]
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=20110605054245.GA11876@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).