All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Lee Howard <lee.howard@mainpine.com>
Cc: linux-serial@vger.kernel.org
Subject: Re: Mainpine IQ Express Rev3 problems beginning 2.6.36
Date: Sun, 12 Dec 2010 08:52:01 -0800	[thread overview]
Message-ID: <20101212165201.GB14184@kroah.com> (raw)
In-Reply-To: <9BEA64D1D71A4BCFA22E0ECE7A4B3A01@callisto>

On Sat, Dec 11, 2010 at 04:36:07PM -0800, Lee Howard wrote:
> > What type of device is this?  A pci card or something else?
> 
> The Mainpine IQ Express cards are multiport PCIe cards with modems attached
> to the serial ports.
> 
> > What driver controls it?
> 
> 8250
> 
> > Also, the best thing to do would be if you could run 'git 
> > bisect' to narrow the problem down to the specific patch that 
> > caused the problem.
> > Any chance you could do that?
> 
> I've been at that for three days now.  It's very tedious and cumbersome
> because, even starting with 'git bisect start -- drivers/serial' which
> narrows-down the anticipated number of runs to 6, it's very difficult to do
> because most of the kernel revisions that are being tested have some bug in
> them (they don't build at all, they have oopses, etc.) and I find myself
> spending a lot of time only to have to do a 'git bisect skip' if I don't
> want to try to work-around those problems.  Eventually I found myself simply
> disabling modules in the build that I don't need to perform the test... And
> that worked better until I started running into other problems in the test
> that were not the same as the one I was having before... So when I'm doing
> 'git bisect' and come across a revision that doesn't work but doesn't have
> the same problems as the target problem, what do I do?  Should I mark it
> "bad" or "skip" it?

Don't limit yourself to changes in drivers/serial as there are lots of
tty fixes in other parts of the kernel that could have caused issues
with this.

As for build issues, try to make a minimal working config for your
system, using 'make localmodconfig'.  That will speed up your build time
immensely as well as reduce your chances of build and runtime problems
with the intermediate kernels.

best of luck,

greg k-h

  reply	other threads:[~2010-12-12 16:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-08 23:55 Mainpine IQ Express Rev3 problems beginning 2.6.36 Lee Howard
2010-12-09  6:42 ` Greg KH
2010-12-12  0:36   ` Lee Howard
2010-12-12 16:52     ` Greg KH [this message]
2010-12-14 19:49       ` Lee Howard
2010-12-17 13:25         ` Lee Howard
2011-01-11  0:02           ` Greg KH
2011-01-11 19:16             ` Lee Howard
2011-01-11 23:03               ` Greg KH
2011-01-25 15:57                 ` Lee Howard

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=20101212165201.GB14184@kroah.com \
    --to=greg@kroah.com \
    --cc=lee.howard@mainpine.com \
    --cc=linux-serial@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.