-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Panic with drm-next on Thinkpad T460s (Skylake, Intel HD Graphics 520) when undocking from Lenovo docking station #159
Comments
There's this code from pfs_add_node() at
I wonder whether that has a bearing on the problem ? The GENERIC conf enables INVARIANTS. |
This resolves two 'zfs recv' issues. First, when receiving into an existing filesystem, a snapshot created during the receive process is not added to the guid->dataset map for the stream, resulting in failed lookups for deduped streams when a WRITE_BYREF record refers to a snapshot received earlier in the stream. Second, the newly created snapshot was also not set properly, referencing the snapshot before the new receiving dataset rather than the existing filesystem. Closes #159 Reviewed by: Matthew Ahrens <[email protected]> Reviewed by: Dan Kimmel <[email protected]> Author: Chris Williamson <[email protected]> openzfs/openzfs@b09697c
You can try |
@myfreeweb Thanks. I commented out the code block referenced above and haven't had panics any more. Agree that a proper fix is preferable. I'll keep this open for the moment. |
Hi.
I experience this panic frequently when undocking my Thinkpad T460s from it's Lenovo docking station. Prior to the undock I was using xrandr to get video output to an external monitor connected to the dock.
Relevant details are as under.
Output of
uname -a
:FreeBSD gene 12.0-CURRENT FreeBSD 12.0-CURRENT #2 ff9c7fc1f1a(drm-next)-dirty: Fri Jul 14 21:29:44 BST 2017 robin@gene:/usr/obj/usr/src/sys/GENERIC amd64
The kernel is drm-next as of yesterday built with the bog standard GENERIC configuration. The dirty indication is because I have the following patch in place which was needed in order for suspend-resume to work correctly as reported here:
Please let me know if any other details would help. Any help/guidance graciously appreciated.
Cheers.
The text was updated successfully, but these errors were encountered: