On 16/11/06, Lennart Sorensen <[EMAIL PROTECTED]> wrote:
On Thu, Nov 16, 2006 at 09:49:06PM +0100, Jesper Juhl wrote:
...
> - You could also try kdb (http://oss.sgi.com/projects/kdb/) or kgdb
> (http://kgdb.linsyssoft.com/). That might help you pinpoint the
> failure.
Can I run that remotely somehow? I never really looked at kdb or kgdb
before.
Yes you can. kgdb is run on a separate machine from the one you are debugging.
> - If you have (or can identify) an older, working, kernel version and
> you are confident that you can reproduce the problem reliably, then
> doing a git bisection search starting with your newest "known good"
> and oldest "known bad" kernel versions, should help you pinpoint the
> commit causing the breakage.
I don't know of a good version yet. I so far don't know if there ever
was one. This could even be a bug in the PCI hardware, or the way the
BIOS on this system on a board configured the PCI controller. Maybe I
should go back and try a 2.4 kernel.
Or just try a few random older 2.6 kernels like 2.6.14, 2.6.9,
2.6.whatever (of course it needs to be a version that git knows
about).
--
Jesper Juhl <[EMAIL PROTECTED]>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
