Summary: | Pager change (r365488) makes vboxdrv panic | ||
---|---|---|---|
Product: | Base System | Reporter: | Adriaan de Groot <adridg> |
Component: | kern | Assignee: | Kubilay Kocak <koobs> |
Status: | Closed DUPLICATE | ||
Severity: | Affects Some People | CC: | emaste, groenveld, lwhsu, markj, vbox |
Priority: | --- | ||
Version: | 12.1-STABLE | ||
Hardware: | Any | ||
OS: | Any |
Description
Adriaan de Groot
![]() ![]() (In reply to Adriaan de Groot from comment #0) Any reason we cant re-classify bug 249326 ? (In reply to Kubilay Kocak from comment #1) No, there isn't. I'm not used to kernel-crash reporting though, and am not sure what to do with a "here is a 100% reproducible, user-facing, kernel panic that has been MFH'ed". The patch posted for the virtualbox port in bug 249326 is sufficient in my testing. No kernel changes are required. I'm inclined to think that the stable/12 kernel revision which triggered the problem should be reverted, but the virtualbox-ose-kmod patch should be applied regardless. Thanks Adriaan :) *** This bug has been marked as a duplicate of bug 249326 *** |