public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <lkml@rtr.ca>
To: kristen.c.accardi@intel.com,
	pcihpd-discuss@lists.sourceforge.net,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: PCIe Hotplug:  NFG unless I boot with card already inserted.
Date: Tue, 16 Oct 2007 11:21:36 -0400	[thread overview]
Message-ID: <4714D700.7060008@rtr.ca> (raw)
In-Reply-To: <4714C0A6.1030204@rtr.ca>

Mark Lord wrote:
> I have a Dell notebook with an PCIe ExpressCard slot.
> I also have a PCIe ExpressCard SATA controller (uses sata_sil24 driver).
> 
> I would like to be able to hot plug/unplug the controller card at will.
> But alas, Linux doesn't cope with it *unless* I boot the kernel with
> the card initially inserted.
> 
> 1. Booting Linux kernel (latest 2.6.23) without the card inserted
> means that the card will never be detected, regardless of how many
> times subsequently the card is inserted/removed/whatever.
> 
> 2. Booting Linux kernel *with* the card inserted means that it is
> detected and used, and can be unplugged/replugged as I please,
> with intervening suspend/resume (RAM or disk) cycles not interfering.
> 
> 3. Booting Linux kernel without the card inserted, and then doing
> a suspend-to-disk poweroff, inserting the card, and powering on again,
> the card's BIOS extension runs as normal.  But on resume from the
> suspend-to-disk, the running kernel again never sees the card,
> even after removing/reinserting/whatever.
> 
> 4. All of this leads me to believe that the kernel must be doing some
> kind of once-only scan of hardware at boot time, and never repeating
> it afterwards.  Loading/unloading all of the PCI/PCIe hotplug stuff
> has no effect on this, so it must be broken elsewhere.
> 
> 5. It is not likely to be a BIOS thing, because it still fails on
> power-on (with card inserted) after a suspend-to-disk, which appears
> to the BIOS exactly the same as any other power-on.
> 
> 6. But it's probably a "kernel relies on BIOS data structure read
> at boot time" issue, based on the observations above.

Actually, I must now take back some of that.

Most of these tests were done a month or two ago.
With 2.6.23.1 running, I just now redid all of the tests.

Now it seems that pciehp fails to notice a newly inserted card
only after a suspend/resume cycle with the slot empty.

I can now get it to work again by just doing:
	1. remove the card, so the slot is empty.
	2. rmmod pciehp; modprobe pciehp
	3. insert the card again -- it works!

So we just need to fix an issue or two with suspend/resume (RAM) in pciehp.

Cheers

  reply	other threads:[~2007-10-16 15:21 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-16 13:46 PCIe Hotplug: NFG unless I boot with card already inserted Mark Lord
2007-10-16 15:21 ` Mark Lord [this message]
2007-10-16 15:46   ` Kristen Carlson Accardi
2007-10-16 18:39     ` Mark Lord
2007-10-16 18:43       ` Kristen Carlson Accardi
2007-10-16 18:57         ` Mark Lord
2007-10-16 18:59           ` Mark Lord
2007-10-16 19:31             ` Mark Lord
2007-10-16 19:51               ` Kristen Carlson Accardi
2007-10-16 20:07               ` Kristen Carlson Accardi
2007-10-16 20:39                 ` Mark Lord
2007-10-16 21:01                   ` Kristen Carlson Accardi
2007-10-16 22:33                     ` Theodore Tso
2007-10-16 21:41                   ` [Pcihpd-discuss] " Greg KH
2007-10-16 21:57                     ` [PATCH] Fix PCIe hotplug for Dell notebook ExpressCard slots Mark Lord
2007-10-16 22:03                       ` Greg KH
2007-10-16 22:19                         ` Mark Lord
2007-10-16 22:41                         ` [Pcihpd-discuss] " Kristen Carlson Accardi
2007-10-16 22:04                       ` Kristen Carlson Accardi
2007-10-16 22:17                         ` Mark Lord
2007-10-17  1:53                       ` [PATCH 0/4] Fix PCIe hotplug for non-ACPI ExpressCard slots (version 2) Mark Lord
2007-10-17  1:54                         ` [PATCH 1/4] " Mark Lord
2007-10-17  1:54                           ` [PATCH 2/4] " Mark Lord
2007-10-17  1:55                             ` [PATCH 3/4] " Mark Lord
2007-10-17  1:55                               ` [PATCH 4/4] " Mark Lord
2007-10-18  0:01                                 ` Kristen Carlson Accardi
2007-10-18  2:28                                   ` Mark Lord
2007-10-17  3:31                             ` [Pcihpd-discuss] [PATCH 2/4] " Matthew Wilcox
2007-10-17 23:54                             ` Kristen Carlson Accardi
2007-10-18  2:25                               ` Mark Lord
2007-10-17  3:29                           ` [Pcihpd-discuss] [PATCH 1/4] " Matthew Wilcox
2007-10-17 13:09                             ` Mark Lord
2007-10-17 14:02                               ` Matthew Wilcox
2007-10-17 14:33                                 ` Mark Lord
2007-10-17 22:02                         ` [PATCH 0/4] " Andrew Morton
2007-10-17 22:59                           ` Mark Lord
2007-10-17 23:25                             ` Andrew Morton
2007-10-16 20:29       ` PCIe Hotplug: NFG unless I boot with card already inserted Kristen Carlson Accardi
2007-10-16 20:41         ` Mark Lord

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=4714D700.7060008@rtr.ca \
    --to=lkml@rtr.ca \
    --cc=kristen.c.accardi@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pcihpd-discuss@lists.sourceforge.net \
    /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