On Tue, Nov 5, 2013 at 11:44 AM, Bjorn Helgaas bhelg...@google.com wrote:
On Tue, Nov 5, 2013 at 6:06 AM, Jiri Kosina jkos...@suse.cz wrote:
On Thu, 31 Oct 2013, Bjorn Helgaas wrote:
Attached is dmesg output leading to timeouts (that are cured by my
original patch in this thread) and lspci.
On Thu, 31 Oct 2013, Bjorn Helgaas wrote:
Attached is dmesg output leading to timeouts (that are cured by my
original patch in this thread) and lspci.
I opened https://bugzilla.kernel.org/show_bug.cgi?id=64141 for this
issue and attached your dmesg log and lspci output.
Please let me
On Tue, Nov 5, 2013 at 6:06 AM, Jiri Kosina jkos...@suse.cz wrote:
On Thu, 31 Oct 2013, Bjorn Helgaas wrote:
Attached is dmesg output leading to timeouts (that are cured by my
original patch in this thread) and lspci.
I opened https://bugzilla.kernel.org/show_bug.cgi?id=64141 for this
On Wed, Oct 30, 2013 at 4:27 AM, Jiri Kosina jkos...@suse.cz wrote:
Attached is dmesg output leading to timeouts (that are cured by my
original patch in this thread) and lspci.
I opened https://bugzilla.kernel.org/show_bug.cgi?id=64141 for this
issue and attached your dmesg log and lspci
On Fri, 6 Sep 2013, Bjorn Helgaas wrote:
Commit d5dea7d95 (PCI: msi: Disable msi interrupts when we
initialize a
pci device) makes MSIs be forcibly disabled at boot time.
It turns out that this breaks 3ware controller -- if MSIs are disabled
during PCI discovery of this
On Fri, Sep 6, 2013 at 4:47 PM, Bjorn Helgaas bhelg...@google.com wrote:
On Fri, Sep 6, 2013 at 3:51 AM, Jiri Kosina jkos...@suse.cz wrote:
Commit d5dea7d95 (PCI: msi: Disable msi interrupts when we initialize
a
pci device) makes MSIs be forcibly disabled at boot time.
It turns
On Wed, 28 Aug 2013, Bjorn Helgaas wrote:
[+cc another email addr for Adam from git logs]
Thanks. Adam, would you happen to have any possible explanation /
background?
Commit d5dea7d95 (PCI: msi: Disable msi interrupts when we initialize a
pci device) makes MSIs be forcibly disabled at
On Fri, Sep 6, 2013 at 3:51 AM, Jiri Kosina jkos...@suse.cz wrote:
On Wed, 28 Aug 2013, Bjorn Helgaas wrote:
[+cc another email addr for Adam from git logs]
Thanks. Adam, would you happen to have any possible explanation /
background?
Commit d5dea7d95 (PCI: msi: Disable msi interrupts
On Tue, 27 Aug 2013, Jiri Kosina wrote:
On Tue, 27 Aug 2013, Jiri Kosina wrote:
Commit d5dea7d95 (PCI: msi: Disable msi interrupts when we initialize a
pci device) makes MSIs be forcibly disabled at boot time.
It turns out that this breaks 3ware controller -- if MSIs are disabled
[+cc another email addr for Adam from git logs]
On Wed, Aug 28, 2013 at 9:46 AM, Jiri Kosina jkos...@suse.cz wrote:
On Tue, 27 Aug 2013, Jiri Kosina wrote:
On Tue, 27 Aug 2013, Jiri Kosina wrote:
Commit d5dea7d95 (PCI: msi: Disable msi interrupts when we initialize a
pci device) makes
Commit d5dea7d95 (PCI: msi: Disable msi interrupts when we initialize a
pci device) makes MSIs be forcibly disabled at boot time.
It turns out that this breaks 3ware controller -- if MSIs are disabled
during PCI discovery of this controller, the device doesn't work properly
(it doesn't respond
[ adding Bjorn and Eric to CC, sorry for omitting you originally ]
On Tue, 27 Aug 2013, Jiri Kosina wrote:
Commit d5dea7d95 (PCI: msi: Disable msi interrupts when we initialize a
pci device) makes MSIs be forcibly disabled at boot time.
It turns out that this breaks 3ware controller -- if
12 matches
Mail list logo
