FreeBSD 13.2-stable crash in /usr/src/sys/amd64/include/pcpu_aux.h:55

only thing that was occurring which is not a normal thing for me to is I was moving TB's worth of data between directly attached two zpools. Regards, Michael Jung

witness_lock_list_get: witness exhausted

without adding the sysctl knobs I do that also - I am not kernel savvy. I will make sure and test an updated patch should one be made available or advise whether to increment these values or ignore the warnings. Regards, Michael Jung CONFIDENTIALITY NOTE: This message is intended onl

RE: Chasing OOM Issues - good sysctl metrics to use?

Hi: I guess I'm kind of high jacking this thread but I think what I'm going to ask is close enough to the topic at hand to ask instead of starting a new thread and referencing this one. I use sysutils/monit to what running processes and then restart them I as I want. I use protect(1) to make su

RE: New panic in main-n253273-a52d8d4a6c6:

, February 21, 2022 9:30 PM To: Michael Jung Cc: Hans Petter Selasky ; freebsd-current Subject: Re: New panic in main-n253273-a52d8d4a6c6: The previous attached patch should work for testing purposes, but it's incorrect if an error occurs. The fhold() should be below FILEDESC_SUNLOCK(),

RE: New panic in main-n253273-a52d8d4a6c6:

From: Michael Jung Sent: Monday, February 21, 2022 9:06 PM To: 'Hans Petter Selasky' ; freebsd-current Subject: RE: New panic in main-n253273-a52d8d4a6c6: From: Hans Petter Selasky [mailto:h...@selasky.org] Sent: Monday, February 21, 2022 8:34 PM To: Michael Jung

RE: New panic in main-n253273-a52d8d4a6c6:

From: Hans Petter Selasky [mailto:h...@selasky.org] Sent: Monday, February 21, 2022 8:34 PM To: Michael Jung ; freebsd-current Subject: Re: New panic in main-n253273-a52d8d4a6c6: On 2/22/22 00:42, Michael Jung wrote: > Hi: > > I was trying to remember what I did that was odd when t

RE: New panic in main-n253273-a52d8d4a6c6:

com/info.1 http://mail.mikej.com/vmcore.1 --mikej -Original Message----- From: Michael Jung Sent: Monday, February 21, 2022 6:22 PM To: 'Hans Petter Selasky' ; freebsd-current Subject: RE: New panic in main-n253273-a52d8d4a6c6: -Original Message- From: Hans Pett

RE: New panic in main-n253273-a52d8d4a6c6:

-Original Message- From: Hans Petter Selasky [mailto:h...@selasky.org] Sent: Monday, February 21, 2022 8:53 AM To: Michael Jung ; freebsd-current Subject: Re: New panic in main-n253273-a52d8d4a6c6: On 2/21/22 14:07, Michael Jung wrote: > (kgdb) fram 16 > #16 0x80bad

RE: New panic in main-n253273-a52d8d4a6c6:

-Original Message- From: owner-freebsd-curr...@freebsd.org [mailto:owner-freebsd-curr...@freebsd.org] On Behalf Of Hans Petter Selasky Sent: Monday, February 21, 2022 2:48 AM To: Michael Jung ; freebsd-current Subject: Re: New panic in main-n253273-a52d8d4a6c6: On 2/20/22 21:53

New panic in main-n253273-a52d8d4a6c6:

Hi! The box was quite busy at the time. The only odd thing I am aware of and which I do not think is related is I have not been able to expand one of my zpool's. ZFS sees my added draid2:2d:10c:0s vdev but I can't seem to force zpool's expansion - my bet this is somehow related to the mirrore

FW: pciconf -lbvV crashes kernel main-8d72c409c - 2022-02-07

Hi: Here are the kernel.full files some of you asked for. Let me know what else may be helpful to test. Thanks! Michael Jung Notes below * (UPDATED) * Started fresh Installed FreeBSD-14.0-CURRENT-amd64-20220113-0910a41ef3b-252413-disc1.iso with its accompany source tree. Built

pciconf -lbvV crashes kernel main-8d72c409c

Dump header from device: /dev/ada0p2 Architecture: amd64 Architecture Version: 2 Dump Length: 900231168 Blocksize: 512 Compression: none Dumptime: 2022-02-04 15:48:08 -0500 Hostname: draid.mikej.com Magic: FreeBSD Kernel Dump Version String: FreeBSD 14.0-CURRENT #1 main-8d72c409c:

13.0-CURRENT #22 r369328 - possible deadlock detected

Hi: So I've had a crash - below is the relevant information. FreeBSD firewall.mikej.com 13.0-CURRENT FreeBSD 13.0-CURRENT #22 r369328: Sun Feb 21 09:26:46 EST 2021 mi...@firewall.mikej.com:/usr/obj/usr/src/amd64.amd64/sys/GENERIC

Re: GELI attach issue from r326073 -> r334996

On 2018-06-13 15:27, Ian Lepore wrote: On Wed, 2018-06-13 at 14:29 -0400, Michael Jung wrote: Hi! I just tried updating current from r326073 -> r334996 and when I try 'geli attach' I get the following error: # geli attach -p -k mykey.key /dev/gpt/da14 geli: Missing keyno argument

GELI attach issue from r326073 -> r334996

Hi! I just tried updating current from r326073 -> r334996 and when I try 'geli attach' I get the following error: # geli attach -p -k mykey.key /dev/gpt/da14 geli: Missing keyno argument # If I boot the old kernel GELI attaches just fine. I ran into this once before but can not find the thread

Re: witness_lock_list_get: witness exhausted

On 2018-01-08 13:39, John Baldwin wrote: On Tuesday, November 28, 2017 02:46:03 PM Michael Jung wrote: Hi! I've recently up'd my processor count on our poudriere box and have started noticing the error "witness_lock_list_get: witness exhausted" on the console. The kernel

witness_lock_list_get: witness exhausted

Hi! I've recently up'd my processor count on our poudriere box and have started noticing the error "witness_lock_list_get: witness exhausted" on the console. The kernel *DOES NOT* crash but I thought the report may be useful to someone. $ uname -a FreeBSD poudriere 12.0-CURRENT FreeBSD 12.0-

fatal error: 'wmmintrin.h' file not found

I have started having problem building current more recent versions of current. I am currently running FreeBSD bsd11 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r320869: Mon Jul 10 13:57:55 UTC 2017 r...@releng3.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 I have tried nuking /usr/src a

Re: r320358 panics immediately on boot / AMD64-GENERIC kernel

On 2017-06-27 12:16, Eric van Gyzen wrote: On 06/27/2017 11:09, Michael Jung wrote: Screen image with backtrace https://pasteboard.co/dZRVG5Uo.jpg After upgrading from 318959 to 320358 I immediately get the attached panic. This is AMD64 / GENERIC kernel. /boot/loader.conf is empty. The

r320358 panics immediately on boot / AMD64-GENERIC kernel

After upgrading from 318959 to 320358 I immediately get the attached panic. This is AMD64 / GENERIC kernel. /boot/loader.conf is empty. The system boots off a UFS2 partition. This is a virtual guest and I do currently have a serial cable. Short of figuring out how to virtualize a serial c

r320358 panics immediately on boot / AMD64-GENERIC kernel

Screen image with backtrace https://pasteboard.co/dZRVG5Uo.jpg After upgrading from 318959 to 320358 I immediately get the attached panic. This is AMD64 / GENERIC kernel. /boot/loader.conf is empty. The system boots off a UFS2 partition. This is a virtual guest and I do currently have a s

Re: Panic String: solaris assert: (lsize != psize) implies ((flags & ZIO_FLAG_RAW) != 0), file: /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c, line: 631

On 2017-04-28 17:42, Andriy Gapon wrote: On 28/04/2017 14:56, Michael Jung wrote: I have mad the requested change.. [root@bsd11 /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs]# diff zio.c ~mikej/zio.c.orig 965c965 < size, NULL, NULL, ZIO_TYPE_FREE, ZIO_PRIORITY_

Re: Panic String: solaris assert: (lsize != psize) implies ((flags & ZIO_FLAG_RAW) != 0), file: /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c, line: 631

On 2017-04-27 17:57, Andriy Gapon wrote: On 27/04/2017 18:52, Michael Jung wrote: Hi: Recently upgraded from r315905 to r317435 and during a poudriere run got this panic which I have not seen before. https://charon.gopai.com/core.txt.1 https://charon.gopai.com/info.1 Let me know what

Panic String: solaris assert: (lsize != psize) implies ((flags & ZIO_FLAG_RAW) != 0), file: /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c, line: 631

Hi: Recently upgraded from r315905 to r317435 and during a poudriere run got this panic which I have not seen before. https://charon.gopai.com/core.txt.1 https://charon.gopai.com/info.1 Let me know what additional information I might supply. --mikej panic: solaris assert: (lsize != psize) i

Re: head r30140 - Panic String: _mtx_lock_sleep: recursed on non-recursive mutex vm page @ /usr/src/sys/vm/vm_page.c:774

On 2016-06-02 18:17, Ngie Cooper wrote: On Thu, Jun 2, 2016 at 3:05 PM, Michael Jung wrote: On 2016-06-01 12:37, Michael Jung wrote: Since upgrading to head r301040 I have started to get the above panic while running poudriere while building packages for 10.3-STABLE r301107. Unfortuately I

Re: head r30140 - Panic String: _mtx_lock_sleep: recursed on non-recursive mutex vm page @ /usr/src/sys/vm/vm_page.c:774

On 2016-06-01 12:37, Michael Jung wrote: Since upgrading to head r301040 I have started to get the above panic while running poudriere while building packages for 10.3-STABLE r301107. Unfortuately I can't tell you the previous version of head but it was from some months ago.

head r30140 - Panic String: _mtx_lock_sleep: recursed on non-recursive mutex vm page @ /usr/src/sys/vm/vm_page.c:774

Since upgrading to head r301040 I have started to get the above panic while running poudriere while building packages for 10.3-STABLE r301107. Unfortuately I can't tell you the previous version of head but it was from some months ago. https://charon.gopai.com/core.txt.7 https://charon.gopai

Re: Call for testing: Using ELF Tool Chain elfcopy as objcopy

th WITH_ELFCOPY_AS_OBJCOPY=yes in /etc/src.conf has built 1400+ ports, via poudriere working without build errors, applications like chrome, libre office, eclipse, xfce4 seem to run fine. These tests are all in a VM under Esxi 6 using Xming as the X server. Thanks

r291494 PANIC mtx_lock() of spin mutex @ /usr/src/sys/kern/vfs_subr.c:512

Since upgrading to r291494 from r290716 my system reliably panics when running poudriere. Dump header from device: /dev/da2p1 Architecture: amd64 Architecture Version: 2 Dump Length: 4301131776 Blocksize: 512 Dumptime: Wed Dec 2 12:10:06 2015 Hostname: bsd11 Magic: FreeBSD Kernel

two different solaris asserts in r288019

This is my poudriere build box that has been running current for a very long time. It was recently upgraded to r288019 and since then I have been getting these panics. One panic I could not find reported, maybe additional information here. I followed the thread here http://lists.freebsd.org/

Re: pkg 1.4.0.alpha3 - pkg: pkg_repo_fetch_remote_mmap(cannot mmap fetched): Invalid argument / Assertion failed: (curvar != NULL), function pkg_solve_add_request_rule, file pkg_solve.c, line 537.

On 2014-10-30 13:10, Baptiste Daroussin wrote: On Thu, Oct 30, 2014 at 12:53:29PM -0400, Michael Jung wrote: Hello: Errors shown toward end of email. Note this is a cleanly installed jail but an previously built repository from an older version of head. I can nuke the head repository and

pkg 1.4.0.alpha3 - pkg: pkg_repo_fetch_remote_mmap(cannot mmap fetched): Invalid argument / Assertion failed: (curvar != NULL), function pkg_solve_add_request_rule, file pkg_solve.c, line 537.

Hello: Errors shown toward end of email. Note this is a cleanly installed jail but an previously built repository from an older version of head. I can nuke the head repository and rebuild from scratch but I wanted to present these errors first. --mikej FreeBSD bsd11 11.0-CURRENT FreeBSD 1

Re: Resizing a zpool as a VMware ESXi guest ...

On 2014-10-16 04:17, Garrett Cooper wrote: On Oct 16, 2014, at 1:10, Edward Tomasz Napierała wrote: "camcontrol rescan" does not force fetching the updated disk size. AFAIK there is no way to do that. However, this should happen automatically, if the "other side" properly sends proper Unit

Re: Gallium debugging and crash dumps

On , Jean-Sébastien Pédron wrote: On 15.05.2014 15:59, Michael Jung wrote: I've started playing with VT and gallium. I boot on ZFS but have a UFS drive and swap partition. Anyone with idea's why I'm not getting any crash info? Were you able to get a kernel core dump? Or is yo

Re: Gallium debugging and crash dumps

On , Michael Jung wrote: On , Michael Jung wrote: Hi: If there is a better list to post this to please let me know. I've started playing with VT and gallium. I boot on ZFS but have a UFS drive and swap partition. Anyone with idea's why I'm not getting any crash info? I am

Re: Gallium debugging and crash dumps

On , Michael Jung wrote: Hi: If there is a better list to post this to please let me know. I've started playing with VT and gallium. I boot on ZFS but have a UFS drive and swap partition. Anyone with idea's why I'm not getting any crash info? I am guessing it is because the

Gallium debugging and crash dumps

Hi: If there is a better list to post this to please let me know. I've started playing with VT and gallium. I boot on ZFS but have a UFS drive and swap partition. Anyone with idea's why I'm not getting any crash info? I am guessing it is because the machine is not rebooting but locks up ha

Re: unknown mtx_assert at /usr/src/sys/x86/x86/io_apic.c:161

On 1/14/11 8:55 PM, "Michael Jung" wrote: > John: > > Thanks, I actually didn¹t see the MCA errors on the screen as the system has > reloaded but noted them in the ddb.txt file last night. > > The Motherboard, CPU, Memory and PS were replaced today. I¹ll po

Re: unknown mtx_assert at /usr/src/sys/x86/x86/io_apic.c:161

hardware was defective. This machine was remote and I found the fan in the power supply not working, so I¹m suspecting that the CPU was or other logic was damaged. Thanks for your reply. --mikej On 1/14/11 4:13 PM, "John Baldwin" wrote: > On Thursday, January 13, 2011 11:26:

unknown mtx_assert at /usr/src/sys/x86/x86/io_apic.c:161

Links to crash info below. http://216.26.153.6/bounds http://216.26.153.6/config.txt http://216.26.153.6/ddb.txt http://216.26.153.6/info.1 http://216.26.153.6/msgbuf.txt http://216.26.153.6/panic.txt http://216.26.153.6/ version.txt