Date: Sat, 11 Aug 2018 19:30:53 +0400 From: Roman Bogorodskiy <novel@freebsd.org> To: Hans Petter Selasky <hps@selasky.org> Cc: Matthew Macy <mmacy@freebsd.org>, freebsd-current@freebsd.org Subject: Re: panic after ifioctl/if_clone_destroy Message-ID: <20180811153052.GB6299@kloomba> In-Reply-To: <983b03f2-928d-852e-325e-1d03b394e591@selasky.org> References: <20180805153556.GA1957@kloomba> <CAPrugNqVUoP0V8%2ByKTbCZgMoDu22xvCfUuga2LbKabjyi_=__A@mail.gmail.com> <a03803e6-5f1e-1960-c6a1-c7477f0ac9d4@selasky.org> <8acc8f27-29f2-d4c1-7473-f7053b14e7ad@selasky.org> <911d520a-4eb5-02b4-a119-3663a7537e6a@selasky.org> <CAPrugNoivMkazen1R_5DkODaCYbL1dRoM9m1VEEmVDvMTW4Kmg@mail.gmail.com> <24743f03-8af2-4106-653d-3bfd13d910c9@selasky.org> <20180811074407.GA6299@kloomba> <983b03f2-928d-852e-325e-1d03b394e591@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--OwLcNYc0lM97+oe1 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hans Petter Selasky wrote: > On 8/11/18 9:44 AM, Roman Bogorodskiy wrote: > > Hans Petter Selasky wrote: > >=20 > >> On 08/06/18 21:43, Matthew Macy wrote: > >>> The struct thread is typesafe. The problem is that the link is no lon= ger > >>> typesafe now that it=E2=80=99s not part of the thread. Thanks for poi= nting this > >>> out. I=E2=80=99ll commit a fix later today. > >>> > >> > >> Is there a patch yet? > >> > >> --HPS > >> > >=20 > > This was committed in: > >=20 > > https://svnweb.freebsd.org/changeset/base/337525 > >=20 > > However, I've just updated to r337595, and it still panics. Not sure if > > that's related to the original issue though: > >=20 > > (kgdb) #0 doadump (textdump=3D0) at pcpu.h:230 > > #1 0xffffffff8043ddfb in db_dump (dummy=3D<value optimized out>, > > dummy2=3D<value optimized out>, dummy3=3D<value optimized out>, > > dummy4=3D<value optimized out>) at /usr/src/sys/ddb/db_command.c:5= 74 > > #2 0xffffffff8043dbc9 in db_command (cmd_table=3D<value optimized out>) > > at /usr/src/sys/ddb/db_command.c:481 > > #3 0xffffffff8043d944 in db_command_loop () > > at /usr/src/sys/ddb/db_command.c:534 > > #4 0xffffffff80440b6f in db_trap (type=3D<value optimized out>, > > code=3D<value optimized out>) at /usr/src/sys/ddb/db_main.c:252 > > #5 0xffffffff80bdef83 in kdb_trap (type=3D9, code=3D0, tf=3D<value opt= imized out>) > > at /usr/src/sys/kern/subr_kdb.c:693 > > #6 0xffffffff8107aee1 in trap_fatal (frame=3D0xfffffe00760dc8a0, eva= =3D0) > > at /usr/src/sys/amd64/amd64/trap.c:906 > > #7 0xffffffff8107a3bd in trap (frame=3D0xfffffe00760dc8a0) at counter.= h:87 > > #8 0xffffffff81054d05 in calltrap () > > at /usr/src/sys/amd64/amd64/exception.S:232 > > #9 0xffffffff80ded513 in inp_gcmoptions (ctx=3D0xfffff80003079f20) > > at epoch_private.h:188 > > #10 0xffffffff80bd9cba in epoch_call_task (arg=3D<value optimized out>) > > at /usr/src/sys/kern/subr_epoch.c:507 > > #11 0xffffffff80bdd0a9 in gtaskqueue_run_locked (queue=3D0xfffff800035b= e900) > > at /usr/src/sys/kern/subr_gtaskqueue.c:332 > > #12 0xffffffff80bdce28 in gtaskqueue_thread_loop (arg=3D<value optimize= d out>) > > at /usr/src/sys/kern/subr_gtaskqueue.c:507 > > #13 0xffffffff80b530c4 in fork_exit ( > > callout=3D0xffffffff80bdcda0 <gtaskqueue_thread_loop>, > > arg=3D0xfffffe00061a4038, frame=3D0xfffffe00760dcac0) > > at /usr/src/sys/kern/kern_fork.c:1057 > > #14 0xffffffff81055cde in fork_trampoline () > > at /usr/src/sys/amd64/amd64/exception.S:990 > > #15 0x0000000000000000 in ?? () > > Current language: auto; currently minimal > > (kgdb) > >=20 > > Full core.txt is here: https://people.freebsd.org/~novel/misc/core.2018= 0811.txt > >=20 > > Roman Bogorodskiy > >=20 >=20 > What is the full panic message? Are you loading // unloading any network= =20 > modules? >=20 > --HPS Fatal trap 9: general protection fault while in kernel mode cpuid =3D 2; apic id =3D 04 instruction pointer =3D 0x20:0xffffffff80ded513 stack pointer =3D 0x28:0xfffffe00760dc960 frame pointer =3D 0x28:0xfffffe00760dc9a0 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 0 (softirq_2) (more details in https://people.freebsd.org/~novel/misc/core.20180811.txt) Panic happens right after boot. I do have: if_tap_load=3D"YES" if_bridge_load=3D"YES" in /boot/loader.conf. Just as before, panic happens after creating/renaming bridge and tap interfaces. Last few lines before panic (as could be seen in core.20180811.txt linked above): bridge0: Ethernet address: 02:af:41:48:c7:00 bridge0: changing name to 'virbr0' tap0: Ethernet address: 00:bd:95:08:f7:00 tap0: link state changed to UP tap0: changing name to 'virbr0-nic' virbr0-nic: promiscuous mode enabled virbr0: link state changed to UP virbr0-nic: link state changed to DOWN virbr0: link state changed to DOWN bridge0: Ethernet address: 02:af:41:48:c7:00 bridge0: changing name to 'virbr-hostnet' tap0: Ethernet address: 00:bd:e5:0b:f7:00 tap0: link state changed to UP tap0: changing name to 'virbr-honet-nic' virbr-honet-nic: promiscuous mode enabled virbr-hostnet: link state changed to UP Roman Bogorodskiy --OwLcNYc0lM97+oe1 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJbbwEsAAoJEMltX/4IwiJq5IIIAIPpq+uxomYRtneZypZyfsfa K35rmBh+lldMjwIobvZiupczVpPGf0KrWA3A1gTqsgs3Uu7dO/bNg3HGQq5OEZiv dLzoMEW0bJ0jNTsMVHJCCUxOKnKX3okeqGVmdiH/Vr/CHzX/ycykZohls+NW0pIa wLv4XiQkO8Jm3cCrby69dFlVsmv/ie5K+3WnYQFsUtrzH9VpE890F8VGZd3uH+Cp 7ZsKPR/Z9dkAajsyOX/8E4H7mg5QLg154bOMVBu1YYJY3Akdy3xQI1uEWDOnbTZM nfeEReFPZVjzNhXzZ15905dzXze/WCM45ocnW4iI4Yj42cCxkP+ngX+MRl1q5qU= =Dvn3 -----END PGP SIGNATURE----- --OwLcNYc0lM97+oe1--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180811153052.GB6299>