Comment 6 for bug 1007841
Revision history for this message
| mlx (myxal-mxl) wrote Re: sky2 driver (Marvell Ethernet devices) problem after resume | #6 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
Hello again. After doing my first bisection, I found the offending commit to be:
commit 7afe1845dd1e7c9
Author: Sameer Nanda <email address hidden>
Date: Mon Jul 25 17:13:29 2011 -0700
>init: skip calibration delay if previously done
>
>For each CPU, do the calibration delay only once. For subsequent calls,
>use the cached per-CPU value of loops_per_jiffy.
>
>This saves about 200ms of resume time on dual core Intel Atom N5xx based
>systems. This helps bring down the kernel resume time on such systems
>from about 500ms to about 300ms.
Now, not being familiar with ubuntu's (or anyone's) development process, I'm a bit confused as to which kernel version this occurred in. Before I tried bisect, I just compiled a few of the tagged revisions and concluded the faulty patch was committed sometime in October or November in kernel version 3.1.0-1.1, after 3.1.0-1.0. Then when I performed the bisection, the kernel version according to Makefile was 3.0.0, and the commits were dated around July.
Is the commit number applicable to mainline git repository (the bisection was done on a clone of ubuntu-precise repo), or do I need a translation to mainline git commit numbers?