On Tue, 3 Jun 2014, 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 ou
On Tue, Nov 5, 2013 at 11:44 AM, Bjorn Helgaas wrote:
> On Tue, Nov 5, 2013 at 6:06 AM, Jiri Kosina 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 http
On Tue, Nov 5, 2013 at 6:06 AM, Jiri Kosina 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
>> issue
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.
>
> > Pleas
On Wed, Oct 30, 2013 at 4:27 AM, Jiri Kosina 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 le
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
> >
On Fri, Sep 6, 2013 at 4:47 PM, Bjorn Helgaas wrote:
> On Fri, Sep 6, 2013 at 3:51 AM, 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
On Fri, Sep 6, 2013 at 3:51 AM, Jiri Kosina 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 when
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 di
[+cc another email addr for Adam from git logs]
On Wed, Aug 28, 2013 at 9:46 AM, Jiri Kosina 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 MSIs
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 d
[ 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
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 respon
13 matches
Mail list logo
