Bug 165488 - [ppp] [panic] Fatal trap 12 jails and ppp , kernel with vimage, altq, pf
Summary: [ppp] [panic] Fatal trap 12 jails and ppp , kernel with vimage, altq, pf
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 9.0-RELEASE
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-net (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-26 16:10 UTC by Nikolay
Modified: 2018-10-19 21:05 UTC (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nikolay 2012-02-26 16:10:00 UTC
FreeBSD going to Fatal trap 12 when ppp start and one or more jails is work.
I test this on other computer - problems is repeated.
If all jails is stop and ppp start system not go to Fatal trap 12. (kernel compile with vimage, altq, pf). If start any jail and start ppp system go fatal trap.
If kernel compile without pf and altq then ppp and jails work.

hell dumped core - see /var/crash/vmcore.27

Sun Feb 26 19:09:18 YEKT 2012

FreeBSD hell 9.0-RELEASE FreeBSD 9.0-RELEASE #5: Mon Feb 20 09:40:42 YEKT 2012     root@hell:/usr/obj/usr/src/sys/VNETGEN  i386

panic: page fault

GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-marcel-freebsd"...

Unread portion of the kernel message buffer:


Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address   = 0x18
fault code              = supervisor read, page not present
instruction pointer     = 0x20:0xc0b08b36
stack pointer           = 0x28:0xd670097c
frame pointer           = 0x28:0xd6700994
code segment            = base rx0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, def32 1, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 51915 (ppp)
trap number             = 12
panic: page fault
cpuid = 0
KDB: stack backtrace:
#0 0xc0a8c2b7 at kdb_backtrace+0x47
#1 0xc0a595e7 at panic+0x117
#2 0xc0da5733 at trap_fatal+0x323
#3 0xc0da57ed at trap_pfault+0xad
#4 0xc0da6575 at trap+0x465
#5 0xc0d8f4cc at calltrap+0x6
#6 0xc0b0df88 at if_alloc+0xb8
#7 0xc0b1e8ec at tuncreate+0x11c
#8 0xc0b2071a at tunopen+0x2a
#9 0xc0970ae8 at devfs_open+0x128
#10 0xc0dc5b22 at VOP_OPEN_APV+0x42
#11 0xc0af9fc1 at vn_open_cred+0x541
#12 0xc0afa12b at vn_open+0x3b
#13 0xc0af159c at kern_openat+0x1ec
#14 0xc0af19c5 at kern_open+0x35
#15 0xc0af1a00 at sys_open+0x30
#16 0xc0da5d55 at syscall+0x355
#17 0xc0d8f531 at Xint0x80_syscall+0x21
Uptime: 1h30m38s
Physical memory: 491 MB
Dumping 173 MB: 158 142 126 110 94 78 62 46 30 14

How-To-Repeat: 1) compile kernel with altq,vimage,pf
#############################
options         VIMAGE
device          epair
device          if_bridge
device          pf
device          pflog
device          pfsync
options         ALTQ
options         ALTQ_CBQ                
options         ALTQ_RED                
options         ALTQ_RIO                
options         ALTQ_HFSC               
options         ALTQ_PRIQ               
options         ALTQ_NOPCC              
#############################

2)Create and start jail with use vimage
3)Start ppp
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2012-02-27 01:21:42 UTC
Responsible Changed
From-To: freebsd-bugs->freebsd-net

Over to maintainer(s).
Comment 2 Eitan Adler freebsd_committer freebsd_triage 2018-05-28 19:47:54 UTC
batch change:

For bugs that match the following
-  Status Is In progress 
AND
- Untouched since 2018-01-01.
AND
- Affects Base System OR Documentation

DO:

Reset to open status.


Note:
I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed.
Comment 3 Kristof Provost freebsd_committer freebsd_triage 2018-10-19 21:05:13 UTC
vnet is now supported in 12.0 (but not in earlier releases).
This problem should be fixed. Please re-open it if you're still having issues on 12 or later.