https://bugzilla.kernel.org/show_bug.cgi?id=16376
--- Comment #35 from Martin Steigerwald <mar...@lichtvoll.de> 2010-08-26
19:18:39 ---
So I am indeed bisecting this, but it is slow - cause last time just after 5
reboots and hours of testing the kernel froze after I marked it as good and
started compiling the next one and since I did not find a git bisect undo to do
git bisect bad after it, I used git bisect reset and git bisect start from that
commit as bad to v2.6.33 as good - and how I am stuck:
mar...@shambhala:~/Computer/Shambhala/Kernel/2.6.33-2.6.34-bisect/linux-2.6>
git bisect log
# bad: [64ba9926759792cf7b95f823402e2781edd1b5d4] Merge branch 'for-linus' of
git://git.open-osd.org/linux-open-osd
# good: [60b341b778cc2929df16c0a504c91621b3c6a4ad] Linux 2.6.33
git bisect start '64ba9926759792cf7b95f823402e2781edd1b5d4' 'v2.6.33'
# skip: [d3ae8562d43fe2b97d605dd67dc67bf8fa9b956a] usb: host: ehci: fix missing
kfree in remove path also
git bisect skip d3ae8562d43fe2b97d605dd67dc67bf8fa9b956a
# good: [8bd93a2c5d4cab2ae17d06350daa7dbf546a4634] rcu: Accelerate grace period
if last non-dynticked CPU
git bisect good 8bd93a2c5d4cab2ae17d06350daa7dbf546a4634
# skip: [5be796f0b842c5852d7397a82f8ebd6be8451872] USB: ch341: use
get_unaligned_le16 in break_ctl
git bisect skip 5be796f0b842c5852d7397a82f8ebd6be8451872
I ran into a non booting kernel with d3ae8562d43fe2b97d605dd67dc67bf8fa9b956a,
it oopsed with a backtrace in ext4 and readahead I don't want to think about
deeply, so I skipped it. Then it put me just a few revisions after 2.6.33, a
kernel that didn't make much sense for me to test - I did nonetheless, it was
good as expected. Then it took me just a few revision after the non working
kernel. Consequently this one didn't boot as well and I skipped it. After that
git bisect took me prior to 2.6.33, git log from
5be796f0b842c5852d7397a82f8ebd6be8451872 gives me
296 commit 6b7b284958d47b77d06745b36bc7f36dab769d9b
297 Author: Linus Torvalds <torva...@linux-foundation.org>
298 Date: Thu Dec 24 13:09:41 2009 -0800
299
300 Linux 2.6.33-rc2
on line 300. But I told git that v2.6.33 was good. It can't be serious about
asking me to test a kernel *prior* to 2.6.33!
Testing is really slow as as it seems even after the fifth reboot and some
hours of uptime it can still freeze. So I need about half a day to be quite
sure that a kernel is good. I won't waste my time going prior to 2.6.33 which
is known good to make this experience even more painful that it was already.
So I ask for advice on how to proceed.
Well at least its clear now, that the freeze was introduced way prior to
2.6.34-rc1. I would have liked it the other way around.
According to git its still
mar...@shambhala:~/Computer/Shambhala/Kernel/2.6.33-2.6.34-bisect/linux-2.6>
git bisect skip
Bisecting: 2518 revisions left to test after this (roughly 11 steps)
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users
worldwide. Take advantage of special opportunities to increase revenue and
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
