Bisecting failed as expected :-(
I tried to follow the git-bisect manpage (and have successfully used
bisect in the past a few times), but I think ~5700 revisions between
2.6.24 and 2.6.25 are just too much fuzz. The bisect logs so far, with
my comments inbetween:
git-bisect start
# 2.6.25-rc4, known to be bad:
# bad: [84c6f6046c5a2189160a8f0dca8b90427bf690ea] x86_64: make ptrace always sign-extend orig_ax to 64 bits
git-bisect bad 84c6f6046c5a2189160a8f0dca8b90427bf690ea
# 2.6.24, good:
# good: [49914084e797530d9baaf51df9eda77babc98fa8] Linux 2.6.24
git-bisect good 49914084e797530d9baaf51df9eda77babc98fa8
# 2.6.24, hard lockup during boot, bad:
# bad: [bd45ac0c5daae35e7c71138172e63df5cf644cf6] Merge branch 'linux-2.6'
git-bisect bad bd45ac0c5daae35e7c71138172e63df5cf644cf6
I marked the last one bad, because I could not boot any more. As it's a
headless box, I could not get more details. It did not even respond so
sysrq-b. After marking this bad, I compiled and booted again - same
result, hard lockup. So I tried again:
git bisect reset
git-bisect start
# 2.6.25-rc4, known to be bad:
# bad: [84c6f6046c5a2189160a8f0dca8b90427bf690ea] x86_64: make ptrace always sign-extend orig_ax to 64 bits
git-bisect bad 84c6f6046c5a2189160a8f0dca8b90427bf690ea
# 2.6.24, good:
# good: [49914084e797530d9baaf51df9eda77babc98fa8] Linux 2.6.24
git-bisect good 49914084e797530d9baaf51df9eda77babc98fa8
# 2.6.24, hard lockup during boot, marking good anyway:
# good: [bd45ac0c5daae35e7c71138172e63df5cf644cf6] Merge branch 'linux-2.6'
git-bisect good bd45ac0c5daae35e7c71138172e63df5cf644cf6
# lockup
# bad: [f0f1b3364ae7f48084bdf2837fb979ff59622523] Merge branch 'release' of git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6
git-bisect bad f0f1b3364ae7f48084bdf2837fb979ff59622523
Although I could not boot with bd45ac0c5daae35e7c71138172e63df5cf644cf6, I
marked it "good", as the lockup is totally unrelated to my problem.
However, the box locks up as soon as I'm using the device-mapper. This
time it does respond to sysrq-b.
But still: I'm unable to diagnose the system hang [0] and I fear that
2.6.25 is released and for the first time since ages I'd have to skip a release...
Help!
Christian.
[0] http://lkml.org/lkml/2008/3/7/308
--
BOFH excuse #288:
Hard drive sleeping. Let it wake up on it's own...
--
