On Wed, 7 Mar 2007, Mws wrote:The first step is to figure out as exactly as possible _when_ it started happening. So is 2.6.19 good? 2.6.20-rc1? -rc2? If you're a git user (or even just marginally interested in learning), the best thing to do is to find some good kernel (the more recent, the better, but the keyword is *some* kernel that works well), and a bad kernel (the older the better, just to avoid unnecessary work, but again, you can just take the most recent too), and then just use "git bisect". If you bisect it down to one particular commit, that will help us a lot, but even if you only bisect it down by booting a handful of kernels (say, 5-6), it will already have cut things down a lot, and probably more easily and efficiently than if you just downloaded daily snapshots and tried to narrow it down that way. Linus -
| Hiten Pandya | Re: up? (emacs docbook xml ide) |
| Greg Kroah-Hartman | [PATCH 004/196] Chinese: add translation of SubmittingPatches |
| debian developer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Jan Engelhardt | intel iommu (Re: -mm merge plans for 2.6.23) |
git: | |
| Gerrit Renker | [PATCH 03/37] dccp: List management for new feature negotiation |
| Ingo Molnar | iwlwifi: fix build bug in "iwlwifi: fix LED stall" |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
