| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 7 Mar 2007 12:09:09 -0800 (PST) From: Linus Torvalds <torvalds@...ux-foundation.org> To: Mws <mws@...sted-brains.org> cc: linux-kernel@...r.kernel.org Subject: Re: irq nobody cared issue on 2.6.2x On Wed, 7 Mar 2007, Mws wrote: > > if you would be so kind to provide me some infos, > > how i would be able to track the problem down _and_ maybe how to fix it. The first step is to figure out as exactly as possible _when_ it started happening. > please find two snippets of dmesg after booting 2.6.21-rc3-git > (2.6.20-1 has got the same results) 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists