[Bug 227654] [panic] repeatable crash with lagg+vlan+em

2018-10-21 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227654

Kubilay Kocak  changed:

   What|Removed |Added

   Severity|Affects Only Me |Affects Some People
 CC|sta...@freebsd.org  |

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 227654] [panic] repeatable crash with lagg+vlan+em

2018-10-20 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227654

--- Comment #5 from Eugene Grosbein  ---
I've added additional printf's to sys/net/if_ethersubr.c and found that it
panices within ether_output_frame() function.

I've added this just before PFIL_HOOKED(&V_link_pfil_hook) check:

if (ifp->if_index == 6) printf(""ether_output_frame: checking curvnet=%p\n",
curvnet);
if (ifp->if_index == 6) printf(""ether_output_frame: V_link_pfil_hook=%p\n",
V_link_pfil_hook);

And last lines of dmesg buffer after panic are:

ether_output_frame: checking curvnet=0
panic: vm_fault_hold: fault on nofault entry, addr: 0

So, curvnet is NULL here, hence the panic.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 227654] [panic] repeatable crash with lagg+vlan+em

2018-10-20 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227654

Eugene Grosbein  changed:

   What|Removed |Added

Version|11.1-STABLE |CURRENT

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 227654] [panic] repeatable crash with lagg+vlan+em

2018-10-20 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227654

--- Comment #4 from Eugene Grosbein  ---
This is 100% repeatable using same command sequence under 12.0-BETA1/i386
installed with all defaults inside VirtualBox VM.

This time it says:

panic: vm_fault_hold: fault on nofault entry, addr: 0

It generates nice crashdump and reboots.
I've uploaded kernel.debug (stock one from 12.0-BETA1/i386 installation image,
18M compressed) and vmcore.0.xz (9.2MB compressed) here:
http://www.grosbein.net/freebsd/crash/20181021/

Here comes kgdb script:

Script started on Sun Oct 21 02:31:58 2018
Command: kgdb kernel.debug /var/crash/vmcore.0
GNU gdb (GDB) 8.2 [GDB v8.2 for FreeBSD]
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "i386-portbld-freebsd12.0".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from kernel.debug...done.

Unread portion of the kernel message buffer:
<6>em0: link state changed to DOWN
<6>vlan61: link state changed to DOWN
panic: vm_fault_hold: fault on nofault entry, addr: 0
cpuid = 0
time = 1540062884
KDB: stack backtrace:
#0 0x112d01f at kdb_backtrace+0x4f
#1 0x10e03f7 at vpanic+0x147
#2 0x10e02ab at panic+0x1b
#3 0x14289c5 at vm_fault_hold+0x2a45
#4 0x1425f2e at vm_fault+0x5e
#5 0x16b6ef7 at trap_pfault+0xc7
#6 0x16b64af at trap+0x3cf
#7 0xffc0315d at PTDpde+0x4165
#8 0x11e0122 at ether_output+0x6a2
#9 0x124887d at arprequest+0x44d
#10 0x12493f9 at arp_ifinit+0x59
#11 0x124c5bb at arp_handle_ifllchange+0x3b
#12 0x11db275 at if_setlladdr+0x275
#13 0x11eb900 at vlan_lladdr_fn+0x30
#14 0x113eba9 at taskqueue_run_locked+0x189
#15 0x113fd57 at taskqueue_thread_loop+0x97
#16 0x10a1af1 at fork_exit+0x71
#17 0xffc033ba at PTDpde+0x43c2
Uptime: 7m21s
Physical memory: 2019 MB
Dumping 84 MB: 69 53 37 21 5

__curthread () at ./machine/pcpu.h:226
226 ./machine/pcpu.h: No such file or directory.
(kgdb) add-kld if_tap.ko
add symbol table from file "if_tap.ko.debug" at
.rodata_addr = 0x18c0c134
set_sysctl_set_addr = 0x18c0c4e0
set_modmetadata_set_addr = 0x18c0c4f8
.note.gnu.build-id_addr = 0x18c0c500
.dynsym_addr = 0x18c0c548
.gnu.hash_addr = 0x18c0cb18
.hash_addr = 0x18c0cb58
.dynstr_addr = 0x18c0ce48
.rel.dyn_addr = 0x18c0d348
.text_addr = 0x18c0f000
.data_addr = 0x18c12000
set_sysinit_set_addr = 0x18c12270
set_sysuninit_set_addr = 0x18c12278
.dynamic_addr = 0x18c13000
.bss_addr = 0x18c14000
(y or n) y
Reading symbols from if_tap.ko.debug...done.
(kgdb) add-kld if_lagg.ko
add symbol table from file "if_lagg.ko.debug" at
.rodata_addr = 0x18c15138
set_sysctl_set_addr = 0x18c16038
set_modmetadata_set_addr = 0x18c16054
.note.gnu.build-id_addr = 0x18c16060
.dynsym_addr = 0x18c160a8
.gnu.hash_addr = 0x18c16798
.hash_addr = 0x18c167e8
.dynstr_addr = 0x18c16b68
.rel.dyn_addr = 0x18c171e8
.text_addr = 0x18c1a000
.data_addr = 0x18c24000
set_vnet_addr = 0x18c24270
set_sysinit_set_addr = 0x18c242a0
set_sysuninit_set_addr = 0x18c242ac
.dynamic_addr = 0x18c25000
.bss_addr = 0x18c26000
(y or n) y
Reading symbols from if_lagg.ko.debug...done.
(kgdb) bt full
#0  __curthread () at ./machine/pcpu.h:226
td = 
#1  doadump (textdump=) at /usr/src/sys/kern/kern_shutdown.c:366
error = 
coredump = 
#2  0x010e0073 in kern_reboot (howto=260)
at /usr/src/sys/kern/kern_shutdown.c:446
once = 
#3  0x010e0444 in vpanic (
fmt=0x179ab2c "%s: fault on nofault entry, addr: %#lx", 
ap=0x16a1462c "U\327p\001") at /usr/src/sys/kern/kern_shutdown.c:872
buf = "vm_fault_hold: fault on nofault entry, addr: 0", '\000' 
td = 0x7369700
newpanic = 
bootopt = 260
other_cpus = 
#4  0x010e02ab in panic (
fmt=0x179ab2c "%s: fault on nofault entry, addr: %#lx")
at /usr/src/sys/kern/kern_shutdown.c:799
ap = 
--Type  for more, q to quit, c to continue without paging--c
#5  0x014289c5 in vm_fault_hold (map=0x2bd5000, vaddr=0, fault_type=, fault_flags=0, m_hold=0x0) at /usr/src/sys/vm/vm_fault.c:586
hardfault = 
nera = 
faultcount = 
wired = 0
prot = 7 '\a'
result = 0
rv = 
behind = 
ahead = 
error = 
locked = 
vp = 
fs =

[Bug 227654] [panic] repeatable crash with lagg+vlan+em

2018-04-21 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227654

Eugene Grosbein  changed:

   What|Removed |Added

Summary|[panic] repeatable crash|[panic] repeatable crash
   |with IPv6+lagg+vlan+em  |with lagg+vlan+em

--- Comment #3 from Eugene Grosbein  ---
It seems IPv6 has nothing to do with the problem as it is reproduceable with
INET4-only kernel too.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"