From: Martin Mokrejs <mmokrejs@fold.natur.cuni.cz>
To: Alan Stern <stern@rowland.harvard.edu>,
Martin Mokrejs <mmokrejs@fold.natur.cuni.cz>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Yinghai Lu <yinghai@kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Sarah Sharp <sarah.a.sharp@linux.intel.com>
Subject: Re: Dell Vostro 3550: pci_hotplug+acpiphp require 'pcie_aspm=force' on kernel command-line for hotplug to work
Date: Mon, 11 Mar 2013 16:56:24 +0100 [thread overview]
Message-ID: <513DFEA8.2080203@fold.natur.cuni.cz> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1303111101090.2246-100000@iolanthe.rowland.org>
Alan Stern wrote:
> On Mon, 11 Mar 2013, Martin Mokrejs wrote:
>
>>> I thought the only card with a problem was the USB3.0 card. But here
>>> you suggest that there *is* a problem with the SATA and Firewire
>>> cards. Can you describe that problem in one sentence?
>>
>> One sentence? No. ;-)
>>
>> None of the cards works when 'nousb' and while are disabled USB
>> devices in BIOS (which can be altered at all, don't know whether that really
>> disables all USB in BIOS or not, hence I used the 'nousb' to be sure).
>
> Martin:
>
> I don't know about Bjorn, but I find it very difficult to work on more
> than one bug at a time. Since your low-level PCI hotplug problems
> seem to be more fundamental than the USB problems, I'll wait until the
> PCI part is under control before trying to contribute.
Alan, for me it is even more difficult because I really do not know what
are the hardware details about nor what is an OS kernel. I really wanted
you pickup anything you see broken in the collected data and we work on
those bug separately. But I am not able to judge what if broken and what
is not.
But I believe you could always say: Hey, if the eSATA or Firewire is
USB-based (unlike PCIe based) it would have to use usb-storage and blah.
I think you can try to come up with answer why USB-related changes disable
PCI Express Root port or whether that was the 'nousb' outcome. I doubt
PCI people will dive into that area. ;)
But thank you for your time on this.
Martin
next prev parent reply other threads:[~2013-03-11 15:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-09 23:10 Dell Vostro 3550: pci_hotplug+acpiphp require 'pcie_aspm=force' on kernel command-line for hotplug to work Martin Mokrejs
2013-01-10 0:40 ` Yinghai Lu
2013-01-10 2:04 ` Martin Mokrejs
2013-01-11 21:11 ` Rafael J. Wysocki
2013-03-06 10:32 ` Martin Mokrejs
2013-03-06 4:09 ` Bjorn Helgaas
2013-03-06 10:30 ` Martin Mokrejs
2013-03-06 21:32 ` Bjorn Helgaas
2013-03-08 1:47 ` Martin Mokrejs
2013-03-09 3:51 ` Bjorn Helgaas
2013-03-11 1:01 ` Martin Mokrejs
2013-03-11 15:03 ` Alan Stern
2013-03-11 15:56 ` Martin Mokrejs [this message]
2013-03-11 16:14 ` Alan Stern
2013-03-12 16:35 ` Martin Mokrejs
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=513DFEA8.2080203@fold.natur.cuni.cz \
--to=mmokrejs@fold.natur.cuni.cz \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=sarah.a.sharp@linux.intel.com \
--cc=stern@rowland.harvard.edu \
--cc=yinghai@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.