kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Did PCI/IRQ allocation change significantly after 4.2 kernel?
Date: Tue, 29 Mar 2016 07:43:14 -0700	[thread overview]
Message-ID: <20160329144314.GA24237@kroah.com> (raw)
In-Reply-To: <20160329144244.GA24067@kroah.com>

On Tue, Mar 29, 2016 at 07:42:44AM -0700, Greg KH wrote:
> On Tue, Mar 29, 2016 at 02:15:23PM +0000, Rob Groner wrote:
> > I?m investigating why our drivers no longer work correctly after the 4.2
> > kernel.  I have verified that in the 4.4 kernel, interrupts no longer work for
> > us as they did before.  Here are the symptoms:
> 
> What drivers are these?  Do you have a pointer to the source for them?
> 
> And what platform are you having these problems on, x86, arm64,
> something else?

Also, can you use 'git bisect' to find the problem commit?  That might
be the easiest way forward.

thanks,

greg k-h

  reply	other threads:[~2016-03-29 14:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-29 14:15 Did PCI/IRQ allocation change significantly after 4.2 kernel? Rob Groner
2016-03-29 14:42 ` Greg KH
2016-03-29 14:43   ` Greg KH [this message]
2016-03-29 15:27     ` Rob Groner
2016-03-29 15:43       ` Greg KH
2016-03-29 18:27         ` Rob Groner
2016-03-29 18:38           ` Greg KH
2016-03-29 19:11             ` Rob Groner
2016-03-29 19:18               ` Greg KH
2016-03-29 19:22                 ` Greg KH
2016-03-29 20:11                   ` Rob Groner
2016-03-30  0:57                     ` Greg KH
2016-03-30 15:51                       ` Rob Groner
2016-04-02 22:26                         ` Greg KH
2016-03-30 21:24                       ` Rob Groner
2016-03-30 21:52                         ` Greg KH

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=20160329144314.GA24237@kroah.com \
    --to=greg@kroah.com \
    --cc=kernelnewbies@lists.kernelnewbies.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).