panic on epair destroy in current as of r349853, jail related
Hi,
I updated from r347365 to r349853. Now I get a panic on epair destroy
(one end needs to be in a jail, and inside the jail an IP address
needs to be assigned to the epair. If no ifconfig is used inside the
jail, there is no panic.
Another user reported something similar (but for him it was enough to
list the interfaces inside the jail with ifconfig) in PR 234985:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234985
Backtrace (here I also renamed the interface before attaching it to
the jail, as I detected the issue with interfaces which are renamed):
Fatal trap 9: general protection fault while in kernel mode
cpuid = 13; apic id = 33
instruction pointer = 0x20:0x805f2045
stack pointer = 0x28:0xfe0159822880
frame pointer = 0x28:0xfe0159822880
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 43334 (ifconfig)
trap number = 9
panic: general protection fault
cpuid = 13
time = 1562695289
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe0159822590
vpanic() at vpanic+0x19d/frame 0xfe01598225e0
panic() at panic+0x43/frame 0xfe0159822640
trap_fatal() at trap_fatal+0x39c/frame 0xfe01598226a0
trap() at trap+0x6c/frame 0xfe01598227b0
calltrap() at calltrap+0x8/frame 0xfe01598227b0
--- trap 0x9, rip = 0x805f2045, rsp = 0xfe0159822880, rbp
= 0xfe0159822880 ---
strncmp() at strncmp+0x15/frame 0xfe0159822880
ifunit_ref() at ifunit_ref+0x51/frame 0xfe01598228c0
ifioctl() at ifioctl+0x508/frame 0xfe0159822990
kern_ioctl() at kern_ioctl+0x26d/frame 0xfe0159822a00
sys_ioctl() at sys_ioctl+0x15d/frame 0xfe0159822ad0
amd64_syscall() at amd64_syscall+0x23a/frame 0xfe0159822bf0
fast_syscall_common() at fast_syscall_common+0x101/frame 0xfe0159822bf0
--- syscall (54, FreeBSD ELF64, sys_ioctl), rip = 0x8004690da, rsp =
0x7fffe448, rbp = 0x7fffe4b0 ---
Uptime: 3h34m59s
Dumping 5294 out of 61352 MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91%
__curthread () at /space/system/usr_src/sys/amd64/include/pcpu.h:246
246 __asm("movq %%gs:%P1,%0" : "=r" (td) : "n"
(OFFSETOF_CURTHREAD));
(kgdb) #0 __curthread () at
/space/system/usr_src/sys/amd64/include/pcpu.h:246
#1 doadump (textdump=1) at /space/system/usr_src/sys/kern/kern_shutdown.c:392
#2 0x8050cf70 in kern_reboot (howto=260)
at /space/system/usr_src/sys/kern/kern_shutdown.c:479
#3 0x8050d3e9 in vpanic (fmt=, ap=)
at /space/system/usr_src/sys/kern/kern_shutdown.c:905
#4 0x8050d123 in panic (fmt=)
at /space/system/usr_src/sys/kern/kern_shutdown.c:832
#5 0x807e758c in trap_fatal (frame=0xfe01598227c0, eva=0)
at /space/system/usr_src/sys/amd64/amd64/trap.c:943
#6 0x807e698c in trap (frame=0xfe01598227c0)
at /space/system/usr_src/sys/amd64/amd64/trap.c:221
#7
#8 0x805f2045 in strncmp (s1=, s2=,
n=) at /space/system/usr_src/sys/libkern/strncmp.c:44
#9 0x80605d31 in ifunit_ref (name=0xfe0159822a20 "panic_test1b")
at /space/system/usr_src/sys/net/if.c:2434
#10 0x80607ef8 in ifioctl (so=0xf809a1afd368, cmd=3223349536,
data=0xfe0159822a20 "panic_test1b", td=0xf8014c83e5a0)
at /space/system/usr_src/sys/net/if.c:3093
#11 0x8057658d in fo_ioctl (fp=, com=3223349536,
data=0xf800020e2180, active_cred=0x0, td=0xf8014c83e5a0)
at /space/system/usr_src/sys/sys/file.h:333
#12 kern_ioctl (td=0xf8014c83e5a0, fd=3, com=3223349536,
data=0xf800020e2180 "")
at /space/system/usr_src/sys/kern/sys_generic.c:800
#13 0x805762ad in sys_ioctl (td=0xf8014c83e5a0,
uap=0xf8014c83e968) at
/space/system/usr_src/sys/kern/sys_generic.c:712
#14 0x807e801a in syscallenter (td=0xf8014c83e5a0)
at /space/system/usr_src/sys/amd64/amd64/../../kern/subr_syscall.c:135
#15 amd64_syscall (td=0xf8014c83e5a0, traced=0)
at /space/system/usr_src/sys/amd64/amd64/trap.c:1181
#16
#17 0x0008004690da in ?? ()
Backtrace stopped: Cannot access memory at address 0x7fffe448
Bye,
Alexander.
--
http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.orgnetch...@freebsd.org : PGP 0x8F31830F9F2772BF
pgpifEi5uMzgA.pgp
Description: Digitale PGP-Signatur
Re: vm_page_hold() and drm-legacy-kmod
On Mon, Jul 08, 2019 at 10:57:41PM -0700, Steve Kargl wrote: > On Tue, Jul 09, 2019 at 01:43:42AM -0400, Mark Johnston wrote: > > On Mon, Jul 08, 2019 at 10:04:00PM -0700, Steve Kargl wrote: > > > > > > This was broken by r349846 committed by markj. > > > > Please try this patch. If it works for you I will submit a pull request > > to the drm-legacy repo. > > Thanks for the quick reply. I've managed to get my /usr/include > in an inconsistent state in trying to back out 349846. Currently, > rebuilding the kernel after a 'make includes'. I'll try your > patch and get back to you. > Mark, your patch fixes the problem. Thanks again for quick response. After commenting out the line containing iicbus_set_nonstop(), the port builds and works. -- Steve ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Someone broke USB
On Tue, Jul 09, 2019 at 10:19:55AM +0200, Niclas Zeising wrote: > On 2019-07-09 06:33, Steve Kargl wrote: > > On Mon, Jul 08, 2019 at 10:54:24PM +0200, Hans Petter Selasky wrote: > >> On 2019-07-08 22:08, Steve Kargl wrote: > >>> On Mon, Jul 08, 2019 at 09:08:17PM +0200, Hans Petter Selasky wrote: > Hi Steve, > > Can you revert all prior patches and try this one instead. > > >>> > >>> With the new patch, none of the USB devices are found. > >>> I'll be away from the laptop for a few hours. > >>> > >> > >> I've put the USB ACPI code into an own module, which is not enabled by > >> default. So USB should be back to normal for now. > >> > >> https://svnweb.freebsd.org/changeset/base/349851 > >> > > > > Thanks! Unfortunately, things have gone left. To update > > /usr/src to get your change, I pulled in some vm changes, > > which break the graphics/drm-legacy-kmod port. > > > Can you report this, including the failure you're seeing, to > x...@freebsd.org or as an issue on the FreeBSDDesktop github? > Thanks! > Regards Mark's patch to deal with the removed vm_page_unhold() has gotten me past that problem. One none hits ===> Building for drm-legacy-kmod-g20190523 ===> drm (all) ===> drm/drm (all) ===> drm/mach64 (all) ===> drm/mga (all) ===> drm/r128 (all) ===> drm/savage (all) ===> drm/sis (all) ===> drm/tdfx (all) ===> drm/via (all) ===> drm2 (all) ===> drm2/drm2 (all) ===> drm2/i915kms (all) cc -O2 -pipe -march=core2 -fno-strict-aliasing -march=core2 -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/ck/include -fno-common -fdebug-prefix-map=./machine=/usr/src/sys/i386/include -fdebug-prefix-map=./x86=/usr/src/sys/x86/include -MD -MF.depend.intel_iic.o -MTintel_iic.o -mno-mmx -mno-sse -msoft-float -ffreestanding -fwrapv -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wcast-qual -Wundef -Wno-pointer-sign -D__printf__=__freebsd_kprintf__ -Wmissing-include-dirs -fdiagnostics-show-option -Wno-unknown-pragmas -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -Wno-error-unused-function -Wno-error-pointer-sign -Wno-error-shift-negative-value -Wno-address-of-packed-member -mno-aes -mno-avx -std=iso9899:1999 -I/usr/ports/graphics/drm-legacy-kmod/work/drm-legacy-12bd551/drm2/../src/ -c /usr/ports/graphics/drm-legacy-kmod/work/drm-lega cy-12bd551/src/dev/drm2/i915/intel_iic.c -o intel_iic.o /usr/ports/graphics/drm-legacy-kmod/work/drm-legacy-12bd551/src/dev/drm2/i915/intel_iic.c:570:2: error: implicit declaration of function 'iicbus_set_nostop' is invalid in C99 [-Werror,-Wimplicit-function-declaration] iicbus_set_nostop(idev, true); ^ /usr/ports/graphics/drm-legacy-kmod/work/drm-legacy-12bd551/src/dev/drm2/i915/intel_iic.c:570:2: error: this function declaration is not a prototype [-Werror,-Wstrict-prototypes] 2 errors generated. *** Error code 1 Stop. make[4]: stopped in /usr/ports/graphics/drm-legacy-kmod/work/drm-legacy-12bd551/drm2/i915kms *** Error code 1 Stop. make[3]: stopped in /usr/ports/graphics/drm-legacy-kmod/work/drm-legacy-12bd551/drm2 *** Error code 1 Stop. make[2]: stopped in /usr/ports/graphics/drm-legacy-kmod/work/drm-legacy-12bd551 *** Error code 1 Stop. make[1]: stopped in /usr/ports/graphics/drm-legacy-kmod *** Error code 1 Stop. make: stopped in /usr/ports/graphics/drm-legacy-kmod -- Steve ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Someone broke USB
On Tue, Jul 09, 2019 at 10:19:55AM +0200, Niclas Zeising wrote: > On 2019-07-09 06:33, Steve Kargl wrote: > > On Mon, Jul 08, 2019 at 10:54:24PM +0200, Hans Petter Selasky wrote: > >> On 2019-07-08 22:08, Steve Kargl wrote: > >>> On Mon, Jul 08, 2019 at 09:08:17PM +0200, Hans Petter Selasky wrote: > Hi Steve, > > Can you revert all prior patches and try this one instead. > > >>> > >>> With the new patch, none of the USB devices are found. > >>> I'll be away from the laptop for a few hours. > >>> > >> > >> I've put the USB ACPI code into an own module, which is not enabled by > >> default. So USB should be back to normal for now. > >> > >> https://svnweb.freebsd.org/changeset/base/349851 > >> > > > > Thanks! Unfortunately, things have gone left. To update > > /usr/src to get your change, I pulled in some vm changes, > > which break the graphics/drm-legacy-kmod port. > > > Can you report this, including the failure you're seeing, to > x...@freebsd.org or as an issue on the FreeBSDDesktop github? I submitted a PR: https://github.com/FreeBSDDesktop/drm-legacy/pull/12 ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: New format for binaries?
On Tue, 2019-07-09 at 10:51 +0400, Gleb Popov wrote: > On Tue, Jul 9, 2019 at 1:33 AM Unidef wrote: > > > Instead of just cc files*c -o file > > > > We can do > > > > cc files*. -o file.c > > > > And cpp file*cpp -o file.cpp > > > > We can hook it up to a MySQL or a neural database? A neural > > database is a > > multi dimensional multi directional binary tree with a master > > function with > > a character array and a (double long *) malloc(double long * > > NEURAL_SIZE); > > index variable, and there’s a search function that searches by > > character > > array > > > > Hopefully this doesn’t sound like spam so don’t yell at me.. <0 (dr > > evil > > emote) > > > > Unidef > > > > This does look like a spam generated using some AI algorithm. The > first > part is probably written by hand, and other one is generated. I just > wondering what's the point of this. > > For everyone else, message looking much like this was sent to llvm- > dev@ > mail list too. > > Everything posted from that mail address has been very obvious straight-up trolling. So obvious, I'm amazed anyone has replied at all. -- Ian ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Someone broke USB
On 2019-07-09 06:33, Steve Kargl wrote: On Mon, Jul 08, 2019 at 10:54:24PM +0200, Hans Petter Selasky wrote: On 2019-07-08 22:08, Steve Kargl wrote: On Mon, Jul 08, 2019 at 09:08:17PM +0200, Hans Petter Selasky wrote: Hi Steve, Can you revert all prior patches and try this one instead. With the new patch, none of the USB devices are found. I'll be away from the laptop for a few hours. I've put the USB ACPI code into an own module, which is not enabled by default. So USB should be back to normal for now. https://svnweb.freebsd.org/changeset/base/349851 Thanks! Unfortunately, things have gone left. To update /usr/src to get your change, I pulled in some vm changes, which break the graphics/drm-legacy-kmod port. Can you report this, including the failure you're seeing, to x...@freebsd.org or as an issue on the FreeBSDDesktop github? Thanks! Regards -- Niclas Zeising ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: New format for binaries?
On Tue, Jul 9, 2019 at 1:33 AM Unidef wrote: > Instead of just cc files*c -o file > > We can do > > cc files*. -o file.c > > And cpp file*cpp -o file.cpp > > We can hook it up to a MySQL or a neural database? A neural database is a > multi dimensional multi directional binary tree with a master function with > a character array and a (double long *) malloc(double long * NEURAL_SIZE); > index variable, and there’s a search function that searches by character > array > > Hopefully this doesn’t sound like spam so don’t yell at me.. <0 (dr evil > emote) > > Unidef > This does look like a spam generated using some AI algorithm. The first part is probably written by hand, and other one is generated. I just wondering what's the point of this. For everyone else, message looking much like this was sent to llvm-dev@ mail list too. > Sent from my iPhone > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: vm_page_hold() and drm-legacy-kmod
On Tue, Jul 09, 2019 at 01:43:42AM -0400, Mark Johnston wrote: > On Mon, Jul 08, 2019 at 10:04:00PM -0700, Steve Kargl wrote: > > > > This was broken by r349846 committed by markj. > > Please try this patch. If it works for you I will submit a pull request > to the drm-legacy repo. Thanks for the quick reply. I've managed to get my /usr/include in an inconsistent state in trying to back out 349846. Currently, rebuilding the kernel after a 'make includes'. I'll try your patch and get back to you. -- Steve ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
