glxgears: Abort trap (core dumped)

> Synopsis: glxgears cores > Category: system > Environment: System : OpenBSD 6.0 Details : OpenBSD 6.0-beta (GENERIC.MP) #2198: Sun Jun 19 11:58:45 MDT 2016 r...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP Archit

Re: glxgears: Abort trap (core dumped)

On 06/20/16 13:06, Stuart Henderson wrote: > On 2016/06/20 13:01, RD Thrush wrote: >>> Synopsis: glxgears cores >>> Category: system >>> Environment: >> System : OpenBSD 6.0 >> Details : OpenBSD 6.0-beta (GENERIC.M

Re: glxgears: Abort trap (core dumped)

On 06/20/16 13:08, Matthieu Herrb wrote: > On Mon, Jun 20, 2016 at 01:01:42PM -0400, RD Thrush wrote: >>> Synopsis: glxgears cores >>> Category: system >>> Environment: >> System : OpenBSD 6.0 >> Details : OpenBSD 6.0-beta (GENERIC.M

Upgrade generates extra "dmesg: sysctl: KERN_MSGBUF: Cannot allocate memory"

> Synopsis: upgrade (actually autoinstall) via bsd.rd yielded new messages > today. > Category: system > Environment: System : OpenBSD 6.0 Details : OpenBSD 6.0-beta (GENERIC.MP) #2211: Thu Jun 23 07:24:18 MDT 2016 dera...@amd64.openbsd

Re: Upgrade generates extra "dmesg: sysctl: KERN_MSGBUF: Cannot allocate memory"

FWIW, the extra message is absent from the current snapshot: OpenBSD 6.0-beta (RAMDISK_CD) #1997: Fri Jun 24 06:29:46 MDT 2016 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD On 06/24/16 07:11, r...@obsd64.thrush.com wrote: >> Synopsis:upgrade (actually autoinstall) vi

nfs client uvm_fault

Resending since earlier report missing after successful delivery to 192.43.244.163. > Synopsis: nfs client results in kernel trap when mount parameters are > altered during xfer > Category: kernel > Environment: System : OpenBSD 6.0 Details : OpenBSD 6.0-beta (GE

perl IO::Socket::IP Argument "1.38_01" isn't numeric in numeric lt ...

Resending this report since it hasn't appeared on bugs nor marc.info. Apologies if it emerges from a queue. >Synopsis: Diagnostic warning appeared after amd64 -current Sat Jul 16 >11:37:22 MDT 2016 >Category: system >Environment: System : OpenBSD 6.0 Details :

install: Can't umount $ROOTDEV!

>Synopsis: Both upgrade and autoinstall fail w/ "Can't umount /dev/sd0a!" >Category: system >Environment: System : OpenBSD 6.0 Details : OpenBSD 6.0-current (GENERIC.MP) #2458: Thu Sep 15 23:24:57 MDT 2016 dera...@amd64.openbsd.org:/usr/

splassert report

Resending since earlier report is missing after successful delivery to 192.43.244.163. >Synopsis: Diagnostic report >Category: kernel >Environment: System : OpenBSD 6.0 Details : OpenBSD 6.0-current (GENERIC.MP) #65: Wed Dec 21 19:09:13 MST 2016

nfs client hangs

>Synopsis: client hangs accessing nfs server >Category: kernel >Environment: System : OpenBSD 5.9 Details : OpenBSD 5.9-current (GENERIC.MP) #1969: Sun Mar 27 20:58:42 MDT 2016 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GE

/usr read-only conflicts w/ anti-ROP mechanism

>Synopsis: A read-only /usr filesystem is incompatible w/ libc.so runtime >rebuild >Category: system >Environment: System : OpenBSD 5.9 Details : OpenBSD 5.9-current (GENERIC.MP) #1999: Thu Apr 28 19:22:08 MDT 2016 dera...@amd64.openbsd

panic: pool_do_get: mcl8k free list modified using re(4)

>Synopsis: Repeatable panic w/ re0 in an updated network >Category: kernel >Environment: System : OpenBSD 5.7 Details : OpenBSD 5.7-current (GENERIC.MP) #987: Sun May 17 20:42:55 MDT 2015 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64

panic: no appropriate pool

>Synopsis: panic in sys/net/pf_lb.c >Category: kernel >Environment: System : OpenBSD 5.8 Details : OpenBSD 5.8 (GENERIC) #1047: Thu Jul 30 23:24:48 MDT 2015 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC Architec

Re: panic: no appropriate pool

the Jun 22 and Jul 28 snapshots. If necessary, I can provide them privately. On 07/31/15 11:22, Mike Belopuhov wrote: > On Fri, Jul 31, 2015 at 10:57 -0400, RD Thrush wrote: >>> Synopsis: panic in sys/net/pf_lb.c >>> Category: kernel >>> Environment: >

Re: panic: no appropriate pool

On 07/31/15 11:22, Mike Belopuhov wrote: > On Fri, Jul 31, 2015 at 10:57 -0400, RD Thrush wrote: >>> Synopsis: panic in sys/net/pf_lb.c >>> Category: kernel >>> Environment: >> System : OpenBSD 5.8 >> Details : OpenBSD 5.8 (GE

Re: panic: no appropriate pool

On 08/01/15 14:46, Mike Belopuhov wrote: > On 1 August 2015 at 19:20, RD Thrush wrote: >> >> The patch ran without panic for 20+ hours. >> > > Thanks for testing! > >> I wondered about the removal of the panic() statement so I tried >> another kernel

Re: panic: no appropriate pool

On 08/01/15 19:31, Jonathan Gray wrote: > On Sat, Aug 01, 2015 at 08:46:00PM +0200, Mike Belopuhov wrote: >> [... snip ...] >> You're slightly overanalyzing here: panic has caught the unhandled >> case, but it's not needed per se. >> > > The code directly after the panic assumes rpool is set. >

Re: panic: no appropriate pool

On 08/02/15 13:37, Mike Belopuhov wrote: > On 2 August 2015 at 15:28, RD Thrush wrote: >> On 08/01/15 19:31, Jonathan Gray wrote: >>> On Sat, Aug 01, 2015 at 08:46:00PM +0200, Mike Belopuhov wrote: >>>> [... snip ...] >>>> You're slightly ove

pledge: smtpd(various): syscall 97 gdb backtrace

I used both the Oct 15 and Oct 16 snaps to upgrade this vm and am seeing repeated messages like the subject. With current sources I added the "abort" tag to all pledge calls in the usr.sbin/smtpd hierarchy and built w/ debug symbols. I've appended some dmesg complaints as well as the full dmesg.

Re: pledge: smtpd(various): syscall 97 gdb backtrace

On 10/17/15 12:29, Sunil Nimmagadda wrote: > It is now fixed in CVS with smtpd.c r1.250, thanks. > >> [snip] I confirm that installing from a current cvs build eliminates this problem. Thanks.

Re: bsd.rd hangs "iwm0: could not read firmware iwm-7265-16 (error 2)"

On 10/20/17 1:07 PM, Stefan Sperling wrote: > On Fri, Oct 20, 2017 at 11:08:07AM -0400, open...@st.thrush.com wrote: >>> Synopsis: bsd.rd hangs "iwm0: could not read firmware iwm-7265-16 (error >>> 2)" >>> Category: kernel >>> Environment: >> System : OpenBSD 6.2 >> Details

Re: bsd.rd hangs "iwm0: could not read firmware iwm-7265-16 (error 2)"

On 10/20/17 1:07 PM, Stefan Sperling wrote: > On Fri, Oct 20, 2017 at 11:08:07AM -0400, open...@st.thrush.com wrote: >>> Synopsis: bsd.rd hangs "iwm0: could not read firmware iwm-7265-16 (error >>> 2)" >>> Category: kernel >>> Environment: >> System : OpenBSD 6.2 >> Details

Re: bsd.rd hangs "iwm0: could not read firmware iwm-7265-16 (error 2)"

On 10/21/17 6:41 AM, Stefan Sperling wrote: > On Sat, Oct 21, 2017 at 05:48:30AM -0400, RD Thrush wrote: >> On 10/20/17 1:07 PM, Stefan Sperling wrote: >>> On Fri, Oct 20, 2017 at 11:08:07AM -0400, open...@st.thrush.com wrote: >>>>> Synopsis: bsd.rd hangs "iwm

Re: Crash and reboot w/out panic message or ddb prompt

On 1/22/18 3:01 PM, RD Thrush wrote: >> Synopsis:kernel reboots w/ out dropping into ddb >> Category:kernel >> Environment: > System : OpenBSD 6.2 > Details : OpenBSD 6.2-current (GENERIC.MP) #380: Sun Jan 21 > 08:53:11 MST 2018 >

Re: kernel: page fault trap, code=0 after upgrade to amd64 May 2 -current

On 05/03/14 19:48, Philip Guenther wrote: > On Sat, 3 May 2014, Fritjof Bornebusch wrote: >> On Sat, 3 May 2014 19:02:41 +0400 >> Loganaden Velvindron wrote: >>> On Sat, May 3, 2014 at 6:25 PM, RD Thrush > ... > > Thank you for the reports; the issue w

Re: uvm_fault(0xd0b8b8e0, 0xefffe000, 0, 1) -> d unp_disconnect

On 05/12/14 14:01, Philip Guenther wrote: > > On Sun, 11 May 2014, RD Thrush wrote: >> login: atascsi_passthru_done, timeout >> stopping package daemons: apcupsd dbus_daemon. >> uvm_fault(0xd0b8b8e0, 0xefffe000, 0, 1) -> d > > Weird: that's an EACCES erro

Re: uvm_fault(0xd0b8b8e0, 0xefffe000, 0, 1) -> d unp_disconnect

On 05/12/14 19:25, Philip Guenther wrote: > On Mon, 12 May 2014, RD Thrush wrote: >> I use this box mostly w/amd64 -current. I boot in i386 appx. weekly to >> do a partial dpb bulk build. I don't use tmpfs (or mfs) in i386 mode. >> I do the dpb builds (both i386 and

i386 panic: double pool_put: 0xd91d2600

>Synopsis: kernel panics while scanning PKG_PATH w/ perl script >Category: kernel >Environment: System : OpenBSD 5.5 Details : OpenBSD 5.5-current (GENERIC.MP) #231: Fri Jul 11 03:48:27 MDT 2014 t...@i386.openbsd.org:/usr/src/sys/arch/i3

vi -r Segmentation fault

> Synopsis: vi fails trying to recover a file > Category: user > Environment: System : OpenBSD 5.6 Details : OpenBSD 5.6-current (GENERIC.MP) #364: Thu Sep 4 02:57:22 MDT 2014 t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC

usb3 flash drive not detected in blue port w/XHCI_DEBUG

>Synopsis: usb3 flash drive not detected in blue port >Category: kernel >Environment: System : OpenBSD 5.6 Details : OpenBSD 5.6-current (XHCI.MP) #1: Wed Nov 19 09:58:52 EST 2014 r...@a8v.thrush.com:/usr/src/sys/arch/amd64/compile/XHCI.

Re: usb3 flash drive not detected in blue port w/XHCI_DEBUG

On 11/20/14 04:33, Peter Hessler wrote: > On 2014 Nov 19 (Wed) at 23:00:30 -0500 (-0500), Ted Unangst wrote: > :On Wed, Nov 19, 2014 at 12:56, RD Thrush wrote: > :>>Synopsis: usb3 flash drive not detected in blue port > :>>Category: kernel > :>>Environmen

usbd_new_device failed, error=SHORT_XFER - usb storage on virtualbox

>Synopsis: Unable to attach a usb storage device to virtualbox vm >Category: kernel >Environment: System : OpenBSD 5.6 Details : OpenBSD 5.6-current (VBOXUSB) #0: Thu Dec 18 14:04:55 EST 2014 r...@a8v.thrush.com:/usr/src/sys/arch/amd64/c

undefined symbol 'Perl_xs_apiversion_bootcheck' ... ld.so: perl: lazy binding failed!

>Synopsis: perl v5.24.1 failures >Category: system >Environment: System : OpenBSD 6.0 Details : OpenBSD 6.0-current (GENERIC.MP) #162: Sat Feb 4 19:08:50 MST 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP

reorder_kernel requires writable /usr/share

>Synopsis: reorder_kernel requires writable /usr/share >Category: system >Environment: System : OpenBSD 6.1 Details : OpenBSD 6.1-current (GENERIC.MP) #73: Sat Jul 1 10:53:54 MDT 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/co

Re: reorder_kernel requires writable /usr/share

On 7/2/17 12:53 PM, Robert Peichaer wrote: > On Sun, Jul 02, 2017 at 12:50:36PM -0400, RD Thrush wrote: >>> Synopsis: reorder_kernel requires writable /usr/share >>> Category: system >>> Environment: >> System : OpenBSD 6.1 >> Details

Re: reorder_kernel requires writable /usr/share

On 7/2/17 1:38 PM, Theo de Raadt wrote: > Remounting a filesystem? > > I don't agree with that approach. It adds way too much complexity. It's similar to the remount when /usr/lib is on a read-only partition as in _reorder_libs(): arp42:build/packages 504>grep -n -A8 'read-write' /etc/rc 182:

libtls.so is missing from base61.tgz set

>Synopsis: libtls.so is missing from base61.tgz set >Category: system >Environment: System : OpenBSD 6.1 Details : OpenBSD 6.1-current (GENERIC.MP) #93: Thu Jul 6 15:41:21 MDT 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compi

Re: QEMU + snapshots - pvclock0: unstable result on stable clock

On 12/3/18 5:00 AM, Reyk Floeter wrote: > Hi, > > thanks for the report. > > We’re going to disable pvclock until I found a solution. It seems that old > KVMs or KVM on old CPUs report stable support incorrectly. > > Do you have a dmesg? I've attached the serial console output from an older pr

Re: Suspend/resume crash with Yubikey

On 10/13/13 10:03, Martin Pieuchot wrote: > Hi Peter, > > Thanks for the bug report. > > On 13/10/13(Sun) 16:24, Peter Kane wrote: >> What is the current expectation for plugging/unplugging USB keyboards? > > This is obviously not the expected behavior, it should not crash your > system ;) > >>

panic: timeout_add: to_ticks (-1) < 0

>Synopsis: Firewall panic with Nov 10 snapshot >Category: kernel >Environment: System : OpenBSD 5.4 Details : OpenBSD 5.4-current (GENERIC) #142: Sun Nov 10 22:52:49 MST 2013 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERI

Re: panic: timeout_add: to_ticks (-1) < 0

On 11/22/13 12:03, Stuart Henderson wrote: > On 2013/11/22 08:47, RD Thrush wrote: >> On 11/11/13 11:22, Stuart Henderson wrote: >>> On 2013/11/11 09:53, RD Thrush wrote: >>>>> Synopsis: Firewall panic with Nov 10 snapshot >>>>> Category: kernel >

Re: panic: timeout_add: to_ticks (-1) < 0

On 11/29/13 17:03, Ted Unangst wrote: > On Fri, Nov 29, 2013 at 21:17, Stuart Henderson wrote: >> On 2013/11/29 14:34, Ted Unangst wrote: >>> On Fri, Nov 29, 2013 at 13:31, RD Thrush wrote: >>>> I've tried -current (Nov 28) on two real machines (soekris and am

Re: panic: timeout_add: to_ticks (-1) < 0

On 11/29/13 17:41, Ted Unangst wrote: > On Fri, Nov 29, 2013 at 17:23, RD Thrush wrote: > >> With the above patch, the reboot hung, no kbd (caps/scroll/num lock echo) >> and no >> response to the ddb interrupt. I had to do a hardware reset. Here's the last &g

Re: panic: timeout_add: to_ticks (-1) < 0

On 11/29/13 17:23, RD Thrush wrote: > On 11/29/13 17:03, Ted Unangst wrote: >> On Fri, Nov 29, 2013 at 21:17, Stuart Henderson wrote: >>> On 2013/11/29 14:34, Ted Unangst wrote: >>>> On Fri, Nov 29, 2013 at 13:31, RD Thrush wrote: >>>>> I've tri

Re: panic: timeout_add: to_ticks (-1) < 0

On 11/29/13 17:03, Ted Unangst wrote: > On Fri, Nov 29, 2013 at 21:17, Stuart Henderson wrote: >> On 2013/11/29 14:34, Ted Unangst wrote: >>> On Fri, Nov 29, 2013 at 13:31, RD Thrush wrote: >>>> I've tried -current (Nov 28) on two real machines (soekris and am

Re: panic: timeout_add: to_ticks (-1) < 0

On 11/22/13 12:03, Stuart Henderson wrote: > On 2013/11/22 08:47, RD Thrush wrote: >> On 11/11/13 11:22, Stuart Henderson wrote: >>> On 2013/11/11 09:53, RD Thrush wrote: >>>>> Synopsis: Firewall panic with Nov 10 snapshot >>>>> Category: kernel >

Re: panic: timeout_add: to_ticks (-1) < 0

On 11/22/13 12:03, Stuart Henderson wrote: > On 2013/11/22 08:47, RD Thrush wrote: >> On 11/11/13 11:22, Stuart Henderson wrote: >>> On 2013/11/11 09:53, RD Thrush wrote: >>>>> Synopsis: Firewall panic with Nov 10 snapshot >>>>> Category: kernel >

Re: panic: timeout_add: to_ticks (-1) < 0

On 12/17/13 20:01, Kenneth R Westerback wrote: > On Tue, Dec 17, 2013 at 07:32:02PM -0500, RD Thrush wrote: >> On 11/22/13 12:03, Stuart Henderson wrote: >>> On 2013/11/22 08:47, RD Thrush wrote: >>>> On 11/11/13 11:22, Stuart Henderson wrote: >>>

Re: panic: timeout_add: to_ticks (-1) < 0

On 12/17/13 20:42, RD Thrush wrote: > On 12/17/13 20:01, Kenneth R Westerback wrote: >> On Tue, Dec 17, 2013 at 07:32:02PM -0500, RD Thrush wrote: >>> On 11/22/13 12:03, Stuart Henderson wrote: >>>> On 2013/11/22 08:47, RD Thrush wrote: >>>>> On 11/1

uvm_fault(nfs_reply) during shutdown after nfs hang

>Synopsis: uvm_fault(0xfe8420a7c648, 0x10, 0, 1) -> e >Category: kernel >Environment: System : OpenBSD 5.5 Details : OpenBSD 5.5-current (GENERIC) #5: Sat Mar 8 05:13:55 EST 2014 r...@a8v.thrush.com:/usr/src/sys/arch/amd64/compile/

Re: kernel/6434: system hangs with ACPI enabled.

The following reply was made to PR kernel/6434; it has been noted by GNATS. From: RD Thrush To: Theo de Raadt Cc: gnats-openbsd Subject: Re: kernel/6434: system hangs with ACPI enabled. Date: Sat, 24 Jul 2010 16:09:40 -0400 On 07/24/10 14:59, RD Thrush wrote: > On 07/24/10 14:09, Theo

kernel/6590: uvm_fault: fatal page fault in supervisor mode

>Number: 6590 >Category: kernel >Synopsis: bsd.rd panics as virtualbox guest >Confidential: yes >Severity: serious >Priority: medium >Responsible:bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-I

Re: kernel/6590: uvm_fault: fatal page fault in supervisor mode

On 04/21/11 03:10, David Gwynne wrote: hey, could you try booting a GENERIC kernel instead of a ramdisk kernel and get me a backtrace from ddb? cheers, dlg I noticed your patch and successfully booted the associated GENERIC.MP kernel. I've appended the information you requested in case you

Re: kernel/6621: hang during shutdown

On 06/02/11 05:56, Mark Kettenis wrote: The only useful information in your report is that .xz file. Next time, use something in base to compress it. Sorry, I'll be sure to do that in the future. That ddb info (~3mb uncompressed) is now also in gzip form at [1]. [1]

Re: kernel/6621: hang during shutdown

The following reply was made to PR kernel/6621; it has been noted by GNATS. From: RD Thrush To: Mark Kettenis Cc: gn...@openbsd.org, b...@cvs.openbsd.org, r...@x2.thrush.com Subject: Re: kernel/6621: hang during shutdown Date: Thu, 02 Jun 2011 07:01:03 -0400 On 06/02/11 05:56, Mark Kettenis

Re: kernel/6621

On 06/24/11 00:00, dera...@cvs.openbsd.org wrote: Synopsis: hang during /sbin/oreboot State-Changed-From-To: open->closed State-Changed-By: deraadt State-Changed-When: Thu Jun 23 22:00:19 MDT 2011 State-Changed-Why: no such command "oreboot". we don't know what you did. "oreboot" has been de

Re: kernel/6621

On 06/24/11 07:47, Theo de Raadt wrote: You are missing the point. Your bug report is huge, but we have no idea what went wrong. I attempted to install a new snapshot via the faq procedure. The system hung doing the "oreboot" step. This is near the beginning of the raw serial console trans

Hang: radeondrm0: wait for fifo failed status

Since the bug tracker is broken, I'm sending sendbug info to misc and bugs... >Synopsis: The system hung hard while using xenocara> >Category: kernel System : OpenBSD 5.0 Details : OpenBSD 5.0-beta (GENERIC.MP) #34: Tue Jul 19 20:07:26 MDT 2011 dera...@amd64.openb