kern/176335: ses driver (scsi_enc) conflicts with enc device in module name (enc)
Rolf Grossmann
rg at progtech.net
Thu Feb 21 21:50:01 UTC 2013
>Number: 176335
>Category: kern
>Synopsis: ses driver (scsi_enc) conflicts with enc device in module name (enc)
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Thu Feb 21 21:50:00 UTC 2013
>Closed-Date:
>Last-Modified:
>Originator: Rolf Grossmann
>Release: 9.1-CURRENT
>Organization:
PROGTECH GmbH
>Environment:
FreeBSD vdev-test.progtech.net 9.1-STABLE FreeBSD 9.1-STABLE #0 r246991M: Thu Feb 21 22:37:40 CET 2013 grossman at vdev-test.progtech.net:/sys/amd64/compile/IPSEC amd64
>Description:
I'm building a kernel (based on GENERIC, adding device enc) using this config file:
include GENERIC
ident IPSEC
options IPSEC
device crypto
device enc
After booting the resulting kernel I'm missing the enc device:
% ifconfig enc0
ifconfig: interface enc0 does not exist
dmesg shows this error message:
module_register: module enc already exists!
Module enc failed to register: 17
What's worse, if I'm actually setting up a tunnel, the kernel panics from trying to record stats on the missing enc device (null pointer dereference).
>How-To-Repeat:
see above.
>Fix:
Not a fix, but a workaround (since I don't need ses):
Add the following to the config file:
nodevice ses
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-bugs
mailing list