http://bugzilla.kernel.org/show_bug.cgi?id=13536 Roland Kletzing <devzero@xxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |devzero@xxxxxx --- Comment #11 from Roland Kletzing <devzero@xxxxxx> 2009-08-11 14:33:00 --- >However finding the kernel module that causes the crash by binary search is >almost impossible since there is no crash as soon as all requests can be >satisfied from the cache so, for each iteration you will need a reboot before, right ? but, what`s the problem with that ? ;) i`d go this way: 1. make a list of all modules you want to unload. 2. name that file however you want 3. do "cat file.list |while read module;do modprobe -r $module;done" 4. test 5. after the next crash, cut that file into 2 parts and repeat 3+4 6. in theory, one of the file should contain the "bad" module. name that file appropriately (.good / .bad) 7. take the .bad file and repeat the steps until bisection results with a file containing a single module -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. -- To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
