Re: Since if_iwm.c r1.224 iwm constantly reports fatal firmware error

On Sat, February 24, 2018 4:05 pm, Stefan Sperling wrote: > On Sat, Feb 24, 2018 at 03:21:14PM -0500, trondd wrote: >> Went back to HEAD and reporduced the problem immediatly. Applied the >> patch and >> that seems to fix it. Running the patch without IWM_DEBUG for now to >> verify >> stability.

panic: kernel diagnostic assertion "skrev->reverse == NULL"

hello, trying to connect to my gateway today I found the following panic. This is 100% reproducible anytime I connect via openvpn and then generate traffic. This first happened on the Feb 7th snap, I updated and it happens on the latest snap as well. For completeness sake, here is first all the

Fwd: bug report

hey i found a bug on ur http://www.openbsd.org/ webste its clickjacking bug here is screenshort of bug

Re: Since if_iwm.c r1.224 iwm constantly reports fatal firmware error

On Sat, Feb 24, 2018 at 03:21:14PM -0500, trondd wrote: > Went back to HEAD and reporduced the problem immediatly. Applied the patch > and > that seems to fix it. Running the patch without IWM_DEBUG for now to verify > stability. > Feb 24 14:42:07 portabsd /bsd: iwm0: 001C | hcmd This

Re: Since if_iwm.c r1.224 iwm constantly reports fatal firmware error

On Sat, Feb 24, 2018 at 10:42:40AM -0500, trondd wrote: > Stefan Sperling wrote: > > > On Fri, Feb 23, 2018 at 12:16:54AM -0500, trondd wrote: > > > >Synopsis:Since if_iwm.c r1.224 iwm constantly reports fatal > > > >firmware error > > > >Category:kernel > > >

Re: Since if_iwm.c r1.224 iwm constantly reports fatal firmware error

Stefan Sperling wrote: > On Fri, Feb 23, 2018 at 12:16:54AM -0500, trondd wrote: > > >Synopsis: Since if_iwm.c r1.224 iwm constantly reports fatal firmware > > >error > > >Category: kernel > > >Environment: > > System : OpenBSD 6.2 > > Details : OpenBSD

Re: llvm issue

I think you're on to something.  I just noticed that there is a clang++.core file that is 1,621,798,448 bytes. I have never looked at the login.conf file (or really, that whole part of bsd) before.  What exactly am I going to change?  Under the 'default:' section, I changed both datasize

Re: llvm issue

On 02/24/2018 04:00 AM, Stuart Henderson wrote: No crash here, but it does use 1.6GB during compile. Try raising memory limits in login.conf (you'll need a new login session, which might mean restarting X). Or try restricting with ulimit to see if you can trigger the crash on other OS. The

acme-client races

I'm seeing some "write: cert: Broken pipe" from my acme-client cron jobs, it looks like there's a race somewhere: acme-client: /etc/ssl/private/symphytum.spacehopper.org.key: loaded RSA domain key acme-client: /etc/acme/letsencrypt-privkey.pem: loaded RSA account key acme-client:

Re: Since if_iwm.c r1.224 iwm constantly reports fatal firmware error

On Fri, Feb 23, 2018 at 12:16:54AM -0500, trondd wrote: > >Synopsis:Since if_iwm.c r1.224 iwm constantly reports fatal firmware > >error > >Category:kernel > >Environment: > System : OpenBSD 6.2 > Details : OpenBSD 6.2-current (GENERIC.MP) #1: Tue Jan 23 20:28:22 >

Re: llvm issue

On 2018/02/23 17:21, Jordon wrote: > I am running the latest snapshot (Feb 21) and discovered that some changes I > made to my hobby project this evening make clang++ crash.  It builds find on > linux with clang 3.8 and a High Sierra machine running whatever version > Apple ships with that. No