Summary: | [vm] [panic] DEBUG_MEMGUARD with vm.memguard.desc="devbuf" panics the kernel | ||
---|---|---|---|
Product: | Base System | Reporter: | Eugene M. Kim <20080111.FreeBSD.org> |
Component: | kern | Assignee: | freebsd-bugs (Nobody) <bugs> |
Status: | Closed Feedback Timeout | ||
Severity: | Affects Only Me | CC: | markj |
Priority: | Normal | ||
Version: | 7.1-RELEASE | ||
Hardware: | Any | ||
OS: | Any |
Description
Eugene M. Kim
2009-04-02 00:50:01 UTC
Based on the stack trace it looks like mgfifo is NULL (the lines are off by one, it appears, but that's the only reasonable place to dereference 0x8). This did not repro on a virtual machine for me. However, there is a new memguard implementation in -current now. I am unable to determine conclusively from just the stack whether this is a bug in memguard or if memguard found a bug in the use of M_DEVBUF but didn't print an error in a friendly format. Would it be possible to re-try this on the same hardware, but using CURRENT? If not, I hope to backport the memguard changes in a few weeks to stable/8 and stable/7. Thanks, matthew For bugs matching the following criteria: Status: In Progress Changed: (is less than) 2014-06-01 Reset to default assignee and clear in-progress tags. Mail being skipped |