https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204521
--- Comment #231 from Gary Jennejohn <[email protected]> --- (In reply to unitrunker from comment #228) This is pretty weird. Looking at my kernel. which has the same address for mmc_go_discovery() as your kernel, the panic is happening in a call to memset() in the first call to mmc_send_app_op_cond(). Apparently the compiler has optimized mmc_go_discovery() by inlining mmc_send_app_op_cond(), since that function is only used in mc_go_discovery(). This conclusion is supported by the fact that there is no entry for mmc_send_app_op_cond in the ELF header. The really strange thing is that memset() is being called to zero out a struct mmc_command cmd which is on the kernel stack. That should bever raise an error. It should also never result in a calltrap, because this is an in-kernel call. I must admit that I can see no way that this error could happen. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "[email protected]"
