https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191468
--- Comment #4 from [email protected] --- (In reply to Kurt Jaeger from comment #3) > Can you test if this still happens with the upcoming 9.3-release ? Sorry. Unfortunately I don't happen to have any suitable FreeBSD-GENERIC build lying around. Best I can do is put it on my list (sorry, very busy), and try to get round to it eventually. Maybe in a few weeks time. In an ideal circumstance, we would: * Rebuild for this kernel config in a 9.2-GENERIC VM. * Reproduce panic. [Y/N] * Then freebsd-update to 9.3 RELEASE (since 9.3 will be released by that time). * Rebuild for this kernel config in a 9.3-GENERIC VM. * Reproduce panic. [Y/N] * Then freebsd-update to 10.0 RELEASE. * Rebuild for this kernel config in a 10.0-GENERIC VM. * Reproduce panic. [Y/N] However the situation is complicated by the fact we don't know exactly which other modules VIMAGE is conflicting with. So in reality, we need to also be: * Rebuild for this kernel config in a 9.2-GENERIC VM. * Reproduce panic. [Y/N] * <edit kernel config> * add or remove a suspected module * Reproduce panic. [Y/N] * <edit kernel config> * add or remove a suspected module * Reproduce panic. [Y/N] * <edit kernel config> * add or remove a suspected module Etc. etc. Which take a lot of time. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "[email protected]"
