Date: Sat, 21 Jul 2018 18:39:07 +0000 From: bugzilla-noreply@freebsd.org To: scsi@FreeBSD.org Subject: [Bug 219857] panic in scsi_cd code Message-ID: <bug-219857-5313-8YpOZHo7aR@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-219857-5313@https.bugs.freebsd.org/bugzilla/> References: <bug-219857-5313@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219857 --- Comment #18 from Kenneth D. Merry <ken@FreeBSD.org> --- Ok, there is likely a bug in the patch, we'll just have to track it down. Here are a few things to try that may help get to the bottom of it. First, make sure you're running with WITNESS and INVARIANTS enabled, since those may catch locking or other issues that are causing problems. 1. In the situation that hangs (Windows Server 2012, UP, no ISO in the dri= ve), when the OS hangs, break into the debugger and run "ps" and "alltrace" and = send the output. You can break into the debugger normally by sending a "break", = but you can also configure ALT_BREAK_TO_DEBUGGER in the kernel config file. He= re is what sys/conf/NOTES says about triggering the debugger: # Solaris implements a new BREAK which is initiated by a character # sequence CR ~ ^b which is similar to a familiar pattern used on # Sun servers by the Remote Console. There are FreeBSD extensions: # CR ~ ^p requests force panic and CR ~ ^r requests a clean reboot. 2. Run the VM under Windows Server 2012 in SMP mode with no ISO in the dri= ve, run these commands and send the output: camcontrol cmd cd0 -v -c "1e 0 0 0 1 0" camcontrol readcap cd0 -v camcontrol cmd cd0 -v -t 60 -c "28 0 0 0 0 0 0 0 1 0" -i 2048 - | hd The first is Prevent Media Removal, the second is Read Capacity, the third = is a standard 10 byte read of one sector only. My assumption is that there should be no difference in the behavior of the emulated CD device between SMP and UP mode, and we're just avoiding the pro= blem in SMP mode due to timing. I have tested in UP and SMP, and haven't seen this particular problem, but = it could be that the emulated CD driver on Windows Server 2012 is responding i= n a way I didn't expect or the timing is just right in UP mode to trigger the b= ug. Let me know what you figure out. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-219857-5313-8YpOZHo7aR>