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 -- To unsubscribe from this list: send the line "unsubscribe linux-serial" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
