Ok, I finished an other bisect, this time the result is a bit different because I skipped more revision (sometimes I could not compile them) but the last bad version is included as possible bad.
This is the message I got:
There are only 'skip'ped commit left to test.
The first bad commit could be any of:
1a750e0cd7a30c478723ecfa1df685efcdd38a90
7dbceaf9bb68919651901b101f44edd5391ee489
437a0a54eea7b101e8a5b70688009956f6522ed0
5136dea5734cfddbc6d7ccb7ead85a3ac7ce3de2
6924d1ab8b7bbe5ab416713f5701b3316b2df85b
We cannot bisect more!
The last one is the one I got the last time.
I hope this will be my last bisect for a while.... :-)
Leann Ogasawara , how can you extract the kernel version from the sha1 hash?
I ask you this because when I compile the revision (using make-kpkg) the resulting kernel version when the problem arise is the 2.6.26-rc9 and not the 2.6.27-rc1.
Ok, I finished an other bisect, this time the result is a bit different because I skipped more revision (sometimes I could not compile them) but the last bad version is included as possible bad.
This is the message I got:
There are only 'skip'ped commit left to test. 78723ecfa1df685 efcdd38a90 651901b101f44ed d5391ee489 1e8a5b706880099 56f6522ed0 bc6d7ccb7ead85a 3ac7ce3de2 ab416713f5701b3 316b2df85b
The first bad commit could be any of:
1a750e0cd7a30c4
7dbceaf9bb68919
437a0a54eea7b10
5136dea5734cfdd
6924d1ab8b7bbe5
We cannot bisect more!
The last one is the one I got the last time.
I hope this will be my last bisect for a while.... :-)
Leann Ogasawara , how can you extract the kernel version from the sha1 hash?
I ask you this because when I compile the revision (using make-kpkg) the resulting kernel version when the problem arise is the 2.6.26-rc9 and not the 2.6.27-rc1.
Thanks, I hope in a fast bug solving.