http://bugzilla.kernel.org/show_bug.cgi?id=13536 --- Comment #8 from Elmar Stellnberger <estellnb@xxxxxxxxx> 2009-06-18 13:53:02 --- Lately I tried to infringe the problem by unloading all possibly unloadable kernel modules (up to 9) and see it suddenly worked without any problem. Unexpectedly the vmware&virualbox modules did not harm. 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 memory. Nonetheless I can provide a minimal module list the script has been working with and a maximal module list that is sure to cause a crash. I wonder if there is any way to forge ahead to a backtrace/core file. At FreeBSD there is always a core-dump hanging around after a crash. -- 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
