From: "Олег Мороз" <oleg.moroz@mcc.vniiem.ru>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: PCI device driver broken between 4.2 and 4.3
Date: Sun, 24 Jan 2016 16:50:08 +0300 [thread overview]
Message-ID: <56A4D690.1020804@mcc.vniiem.ru> (raw)
In-Reply-To: <CAErSpo6MtFSxnH8uSqeLiJVR3P-R5DUX2Furw3yw8JiMN29H0A@mail.gmail.com>
Okay. I've sent logs (dmesg and lspci) from both 4.2 and 4.3 to bugzilla
23.01.2016 17:54, Bjorn Helgaas пишет:
> [+cc linux-kernel]
>
> Hi Олег,
>
> On Sat, Jan 23, 2016 at 1:08 AM, Олег Мороз <oleg.moroz@mcc.vniiem.ru> wrote:
>> Hello. I've got a device driver for MIL-1553b card called TA1-PCI, which
>> could be found at
>> https://github.com/qmor/elcus-1553-driver-linux
>> Card is using PLX_PCI9030 PCI controller.
>> Today i've found that this driver compiles, installes, but is not working as
>> it should.
>> Looks like it not receives any interrupts from PCI. I've test it again with
>> kernel
>> 4.2 and it works okay. What changes was made in PCI subsystem from 4.2 to
>> 4.3
>> which could have impact this driver work.
> Thank you very much for this problem report. There were many PCI
> changes between v4.2 and v4.3, and without more information, I can't
> guess what might be causing this problem.
>
> I opened a bug report at https://bugzilla.kernel.org/show_bug.cgi?id=111211
>
> Please attach complete dmesg logs for both v4.2 and v4.3 to that bug
> report. Also, please attach the complete "lspci -vv" output (as
> root).
>
> Thanks!
>
> Bjorn
next prev parent reply other threads:[~2016-01-24 13:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-23 7:08 PCI device driver broken between 4.2 and 4.3 Олег Мороз
2016-01-23 14:54 ` Bjorn Helgaas
2016-01-24 13:50 ` Олег Мороз [this message]
2016-01-25 21:52 ` Bjorn Helgaas
2016-01-26 15:32 ` Bjorn Helgaas
2016-01-26 19:05 ` Олег Мороз
2016-01-27 9:38 ` Мороз Олег
2016-01-27 13:22 ` Bjorn Helgaas
2016-02-05 17:40 ` Bjorn Helgaas
-- strict thread matches above, loose matches on Subject: below --
2016-01-28 19:28 Мороз Олег
2016-01-28 19:28 ` Мороз Олег
2016-01-28 19:28 Мороз Олег
2016-01-29 16:31 ` Bjorn Helgaas
2016-01-30 6:15 ` Yinghai Lu
2016-02-01 5:18 ` Олег Мороз
2016-02-01 21:08 ` Bjorn Helgaas
2016-02-02 5:04 ` Олег Мороз
2016-02-02 16:13 ` Bjorn Helgaas
2016-02-02 16:17 ` Олег Мороз
2016-02-05 14:29 ` Bjorn Helgaas
2016-01-22 19:09 Олег Мороз
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=56A4D690.1020804@mcc.vniiem.ru \
--to=oleg.moroz@mcc.vniiem.ru \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@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 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.