Running the first set of example commands from the pair(4) man page
crashes the kernel on at least sparc64 and octeon.
# ifconfig pair1 rdomain 1 10.1.1.1/24 up
# ifconfig pair2 rdomain 2 10.1.1.2/24 up
# ifconfig pair1 patch pair2
# route -T 1 exec ping
On Sun, Mar 18, 2018 at 07:46:03PM -0600, Karl Williamson wrote:
> On this system:
>
> $ uname -a
> OpenBSD cjg-openbsd6 6.2 GENERIC#132 amd64
>
>
> compiling and running the attached file yields buggy results.
>
> setlocale(LC_ALL, "C") returned 'C'
> setlocale(LC_CTYPE, "cguevara_and_khw") re
The following will trigger "panic: rw_enter: netlock locking against myself":
# cat /etc/vm.conf
vm "debian" {
memory 2G
disk "/home/vm/debian.img"
cdrom "/home/vm/debian-9.4.0-amd64-netinst.iso"
local interface
}
# rcctl enable vmd
# rcctl start vmd
# vmctl status
On Mon, Mar 19, 2018 at 04:23:30PM +0100, Martin Pieuchot wrote:
> On 19/03/18(Mon) 15:58, Stefan Sperling wrote:
> > The following will trigger "panic: rw_enter: netlock locking against
> > myself":
>
> The solution is to call bpfdetach() outside of the NET_
On Tue, Mar 20, 2018 at 02:42:31AM +0100, Ingo Schwarze wrote:
> So here is a rewrite of our setlocale(3) manual page. No idea why
> i didn't do that earlier, there are lots of obvious issues with that
> manual page.
Thanks, I've read through it and it looks good.
I think we explicitly allow LC_
Booting 6.3 kernels (either GENERIC or GENERIC.MP) on a T5220 results
in a panic when com0 is attached:
Boot device: /pci@0/pci@0/pci@2/scsi@0/disk@0 File and args: sr0a:/bsd.mp.63
OpenBSD IEEE 1275 Bootblock 1.4
>> OpenBSD BOOT 1.9
ERROR: /iscsi-hba: No iscsi-network-bootpath property
Can't read
On Mon, Apr 02, 2018 at 10:08:09AM +0300, Denis wrote:
> I installed OpenBSD 6.3amd64 from latest snapshot two days ago. The
> panic is a bit different with run(4) driver and RT3070 USB dongle than
> on 6.3amd64. The testing machine is a bit different and its dmesg is
> listed after panic info.
It
On Thu, Apr 05, 2018 at 05:30:25PM +0300, Denis wrote:
> 1. AR9271 USB stick has been connected to OpenBSD 6.3 amd64
> 2. # fw_update
> 3. # ls /etc/firmware | grep athn
> athn-ar7010
> athn-ar7010-11
> athn-ar9271
> athn-license
> athn-open-ar7010
> athn-open-ar9271
> athn-open-license
>
> After
On Wed, Apr 04, 2018 at 04:32:21PM +0300, Manolis Tzanidakis wrote:
> >Synopsis:wol does not wake on re(4)
> >Category:sys
> >Environment:
> System : OpenBSD 6.3
> Details : OpenBSD 6.3 (GENERIC.MP) #107: Sat Mar 24 14:21:59 MDT
> 2018
>
> dera.
On Sat, Apr 07, 2018 at 06:10:06PM +0200, Josef Boehm wrote:
> HiI installed version 6.3 on a DELL laptop (Intel wifi card). Previously
> the installed version was 6.2, and earlier ones before that, always
> without issues. With 6.3 (iwn0) I cannot connect to the wifi router
> anymore. Ifconfig giv
On Mon, Apr 09, 2018 at 12:56:04AM +0200, Klemens Nanni wrote:
> Following the EXAMPLES section in ldomctl(8) to the letter, ldomctl
> dumps core when issuing the `init-system' command for an already
> existing logical domain configuration.
>
> How to reproduce on a T5220 running latest snapshots
On Wed, Apr 11, 2018 at 10:47:33AM -0300, Elias M. Mariani wrote:
> >Synopsis: athn: device timeout on Atheros AR9227
> >Category: system
> >Environment:
> System : OpenBSD 6.3
> Details : OpenBSD 6.3 (GENERIC.MP) #107: Sat Mar 24 14:21:59 MDT 2018
> dera...@amd64.openbsd.org:/usr/src/sys/
On Sun, Apr 15, 2018 at 11:48:53AM +0300, Denis wrote:
> For test I've just updated OpenBSD from 6.2amd64 to 6.3amd64 on Intel
> based machine (shortened dmesg is listed below) and there is no 'athn0:
> could not load firmware' error appears after upgrade. On Intel's
> platform AR9271 works as expe
On Wed, Apr 18, 2018 at 10:27:44PM +1000, Jonathan Matthew wrote:
> On Sat, Apr 14, 2018 at 06:54:35AM +0200, p...@ex.com.pl wrote:
> > >Synopsis: page fault trap when removing urtwn Wifi adapter from the port
> > >Category: kernel
> > >Environment:
> > System : OpenBSD 6.3
> > Detai
On Fri, Apr 20, 2018 at 09:59:34AM +, david.dahlb...@fkie.fraunhofer.de
wrote:
> When using vether(4) in a bridge(4), unicast packets directed to the
> vether are not received. I do not even see them at all in tcpdump. Neither
> on the vether, the bridge, nor any of the physical devices. Othe
On Fri, May 25, 2018 at 03:20:50PM +0200, Alexander Bluhm wrote:
> On Tue, May 22, 2018 at 07:32:29AM +0200, Harald Dunkel wrote:
> > Do you think this is worth a syspatch?
>
> You are asking this question for three times. The answer is no.
>
> Errata and syspatch are for security issues that ca
On Sat, Feb 24, 2018 at 08:54:47PM -0500, trondd wrote:
> 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 an
On Fri, Jun 22, 2018 at 03:30:03PM +0200, Paul de Weerd wrote:
> Hi all,
>
> Yesterday, I upgraded my GPD Win to the latest snap. I'm pretty sure
> I booted into it successfully, but can't be sure now that I'm running
> into this weird issue.
>
> Kernel starts booting, gives the 'root on sd0a (8
On Fri, Jun 22, 2018 at 03:51:54PM +0200, Stefan Sperling wrote:
> You could try chasing the problem into bwfm_attachhook() (if_bwfm_pci.c).
Clarification: The attachhook function is in dev/ic/bwfm.c, but the
flow will end up somewhere in bwfm_pci_preinit() in dev/pci/if_bwfm_pci.c
On Tue, Jul 03, 2018 at 12:47:20PM +0200, david+bsd@dahlberg.cologne wrote:
> >Synopsis: iked installs ipsec flow which prevents inet6 communication
> >Category: system
> >Environment:
> System : OpenBSD 6.3
> Details : OpenBSD 6.3-current (GENERIC.MP) #80: Sun Ju
On Tue, Jul 03, 2018 at 01:34:09PM +0200, David Dahlberg wrote:
> Am Tuesday, den 03.07.2018, 13:29 +0200 schrieb Stefan Sperling:
> > Not a bug. This behaviour is intentional and avoids VPN traffic
> > leakage.
> > See RFC 7359 and the iked(8) man page. Use the -6 opti
On Tue, Jul 03, 2018 at 12:54:36PM +0100, Stuart Henderson wrote:
> On 2018/07/03 13:42, Stefan Sperling wrote:
> > On Tue, Jul 03, 2018 at 01:34:09PM +0200, David Dahlberg wrote:
> > > Am Tuesday, den 03.07.2018, 13:29 +0200 schrieb Stefan Sperling:
> > > >
On Tue, Jul 03, 2018 at 02:39:10PM +0200, David Dahlberg wrote:
> Am Tuesday, den 03.07.2018, 13:42 +0200 schrieb Stefan Sperling:
> > Would you be able to send a patch for the iked man page which
> > explicitly mentions VPN traffic leakage and RFC 7359 (in the
> > STAND
On Tue, Jul 03, 2018 at 02:57:40PM +0200, Stefan Sperling wrote:
> Apart from the above points, this change looks like an improvement to me.
> Could you send a fixed version?
A new patch was provided off-list by David and I have just committed it.
Thanks!
While iwm is associated and IPv6 autoconf addresses have been
configured by slaacd, this command can panic the kernel:
ifconfig iwm0 down delete -inet6
It doesn't trigger every time, but after a few attempts I see:
(manually transcribed from laptop screen)
panic: ni_pledge
Stopped at db_
On Fri, Jul 20, 2018 at 05:38:56PM -0300, Martin Pieuchot wrote:
> On 20/07/18(Fri) 14:32, Theo de Raadt wrote:
> > Martin Pieuchot wrote:
> >
> > > On 20/07/18(Fri) 03:12, Mike Larkin wrote:
> > > > On Wed, Jul 18, 2018 at 11:34:41PM +, Romain wrote:
> > > > > > I'm wondering if this is due
On Fri, Aug 10, 2018 at 04:51:23PM +, Romain wrote:
> Hi Mike,
>
> Sorry for the delay.
>
> Here is a reproducible scenario (kernel panic probability > 66%):
> >Environment:
> System : OpenBSD 6.3
> Details : OpenBSD 6.3 (GENERIC.MP) #8: Sat Aug 4 16:56:56 CEST 201
Thank you for taking care of axen(4).
The problems with this driver have been known for some time.
On Tue, Aug 07, 2018 at 02:04:24PM +, sc.dy...@gmail.com wrote:
> - header: fix comments
> - header: fix unused L3 type mask definition
> - rxeof: Avoid allocating mbuf if checksum errors are
On Sun, Aug 19, 2018 at 09:56:33AM +0200, Remi Locherer wrote:
> It would help if you could send a clean version that applies to -current.
One of the attachments was in fact clean but yes, this
thread has been much too noisy to follow easily.
Try this.
Index: if_axen.c
==
On Sun, Aug 19, 2018 at 11:05:04AM +0200, Stefan Sperling wrote:
> On Sun, Aug 19, 2018 at 09:56:33AM +0200, Remi Locherer wrote:
> > It would help if you could send a clean version that applies to -current.
>
> One of the attachments was in fact clean but yes, this
> thread
On Wed, Sep 05, 2018 at 11:46:41AM +0100, Russell Nathan Hyer wrote:
> I thought I should mention this issue as it may cause unknown side effects in
> other packages or components that depend on C++.
Thanks for letting us know. But it seems unlikely that anything would be
done about this kind of
On Thu, Sep 13, 2018 at 08:44:05AM -0400, Xavier Guerin wrote:
> >Synopsis:Kernel crash in IWM driver after resume from sleep
> >Category:kernel
> >Environment:
> System : OpenBSD 6.4
> Details : OpenBSD 6.4-beta (GENERIC.MP) #292: Mon Sep 10
> 18:26:22 MDT 2018
>
On Mon, Sep 17, 2018 at 10:23:14AM -0400, "Xavier R. Guérin" wrote:
> > On Sep 14, 2018, at 11:16 AM, Xavier Guerin wrote:
> > I'm running the patched kernel since yesterday and the issue has not
> > shown up yet even after a whole bunch of sleep/resume cycles of various
> > duration.
> >
> > I'l
On Sat, Sep 22, 2018 at 04:25:03PM +0200, Gregor Best wrote:
>
> Hi,
>
> iwm0 at pci2 dev 0 function 0 "Intel Dual Band Wireless AC 8260" rev 0x3a,
> msi
> iwm0: hw rev 0x200, fw ver 16.242414.0, address e4:a4:71:e1:45:79
>
> this patch seems to have caused increased error rates (IERRS in s
On Sat, Feb 01, 2020 at 11:19:21AM +, Stuart Henderson wrote:
> Currently known libressl problems:
>
>
> #1: https://bitbucket.org https://mirror.vdms.com https://ftp.postgresql.org
> fail with:
>
> Error: error:14FFF3E7:SSL routines:(UNKNOWN)SSL_internal:unknown failure
> occurred
This a
This is likely now fixed in -current.
See https://marc.info/?l=openbsd-cvs&m=158201459403461&w=2
On Thu, Mar 21, 2019 at 11:45:22AM +0100, Stefan Sperling wrote:
> On Thu, Mar 21, 2019 at 11:38:44AM +0100, Stefan Sperling wrote:
> > On Thu, Mar 21, 2019 at 10:21:37AM +, Kev
Fixed in -current.
See https://marc.info/?l=openbsd-cvs&m=158201459403461&w=2
On Wed, May 29, 2019 at 08:53:37PM +0300, Antonis Psaras wrote:
> Hello
>
>
>
> I have a crash when I start Atheros as hotspot.
>
>
>
> Platform used is APU4C4 with WLE200NX Atheros mini PCI-E Card
>
>
>
>
This has been fixed in -current.
See https://marc.info/?l=openbsd-cvs&m=158201459403461&w=2
On Sat, Jan 12, 2019 at 03:59:55AM -0700, martian67 wrote:
> >Synopsis: athn in hostap mode causes kernel panic upon 802.11n client
> >association
> >Category: wireless
> >Environment:
>
On Mon, Mar 02, 2020 at 04:04:46PM +0100, David Demelier wrote:
> >Synopsis:cdce0 unable to acquire a lease if laptop boots docked to
> >station
> >Category:kernel
> >Environment:
> System : OpenBSD 6.6
> Details : OpenBSD 6.6 (GENERIC.MP) #5: Sun Feb 16 01:56:1
On Thu, Mar 12, 2020 at 10:15:47PM +, Stuart Henderson wrote:
> On 2020/03/12 15:35, Timothée FAURE wrote:
> > Hello !!
> > (I'm French, so, if I don't speak English very well, please, don't kill me
> > 😉)
> >
> > I've tried to install OpenBSD on my computer, but, the Wifi don't run...
> > I
On Sat, Mar 14, 2020 at 05:36:46PM +0100, Otto Moerbeek wrote:
> Looking a the diff, I do see a use-after-free.
The problem is the use of TAILQ_FOREACH(wn, ...) instead of
TAILQ_FOREACH_SAFE(wn, ...) in combination with free(wn), correct?
On Fri, Mar 20, 2020 at 01:50:42AM +, Tom Smyth wrote:
> >Synopsis:
> >Category:
> >Environment:
> System : OpenBSD 6.6
> Details : OpenBSD 6.6 (GENERIC.MP) #7: Thu Mar 12 11:55:22 MDT 2020
> r...@syspatch-66-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
>
> Architect
On Mon, Mar 23, 2020 at 10:04:13AM +, Kevin Chadwick wrote:
> On 2020-03-21 13:07, Kevin Chadwick wrote:
> > iwn seems to connect first time now with the last ? number of snapshots :)
> >
> > However, I have to run ifconfig iwn0 -joinlist first.
>
> You can close this bug now. It seems vi mig
On Mon, Mar 23, 2020 at 10:34:45AM +, Kevin Chadwick wrote:
> On 2020-03-23 10:12, Stefan Sperling wrote:
> > You should see "!wpakey" in 'ifconfig iwn0' if you keep trying to
> > connect with a bad key.
> >
> > And message 2/4 failing almost
On Sat, Mar 28, 2020 at 12:56:00AM -0400, a...@200013.net wrote:
> >Synopsis:
> >Category:
> >Environment:
> System : OpenBSD 6.6
> Details : OpenBSD 6.6 (GENERIC.MP) #6: Tue Mar 10 01:55:59 MDT 2020
>
> r...@syspatch-66-amd64.openbsd.org:
On Sun, Mar 29, 2020 at 01:15:37PM +0100, Raf Czlonka wrote:
> >Synopsis:"splassert: ieee80211_free_node: want 7 have 4" followed by
> >"zyd0: device timeout"
> >Category:kernel
> >Environment:
> System : OpenBSD 6.6
> Details : OpenBSD 6.6-current (GENERIC.MP) #86: Sa
On Thu, Apr 02, 2020 at 11:43:34AM +0100, Raf Czlonka wrote:
> I've just tested it but, whilst I don't get a panic when I *un*plug
> the USB NIC, I *do* get the same panic when I *plug* it back in :^(
Insufficient detail. Please show the panic.
We need to know what you are actually seeing, not yo
On Thu, Apr 02, 2020 at 12:40:46PM +0100, Raf Czlonka wrote:
> On Thu, Apr 02, 2020 at 12:30:15PM BST, Stefan Sperling wrote:
> > On Thu, Apr 02, 2020 at 11:43:34AM +0100, Raf Czlonka wrote:
> > > I've just tested it but, whilst I don't get a panic when I *un*plug
>
On Thu, Apr 02, 2020 at 06:21:27PM +0100, Raf Czlonka wrote:
> On Thu, Apr 02, 2020 at 12:51:45PM BST, Stefan Sperling wrote:
> Hi Stefan,
>
> After I got it to timeout, I ran /etc/netstart and unplugged it,
> then plugged it again - no panic. I had to poke it a bit to get it
>
On Thu, May 07, 2020 at 05:12:04PM +0800, Mark Novem Grisola wrote:
> I have tried to install(CD installer) OpenBSD6.6 on our server(IBM xSeries
> 336) but i've got errors. We will be using OpenBSD as our web server OS and
> soon to our other windows based server also. Please help us solve these
>
On Tue, May 19, 2020 at 11:12:01PM +0200, stolen data wrote:
> trying to transfer the same 440 MiB file but on 802.11n
> ===
>
> the machine's network freezes repeatedly, and ping(8) outputs lots of:
>
> ping: sendmsg: No buffer space available
On Wed, May 20, 2020 at 09:35:12AM +0200, Joachim Schipper wrote:
> On Tue, May 19, 2020 at 10:30:41PM +0200, Theo Buehler wrote:
> > Hi,
> >
> > Thanks for the detailed report.
> >
> > > iwm0: sending assoc_req to 18:e8:29:11:2b:2f on channel 6 mode 11g
> > > iwm0: association failed (status
On Wed, May 20, 2020 at 12:20:45PM +0200, stolen data wrote:
> The antennas are just fine - as I mentioned, when rebooting the PC into
> Linux (same hardware, same wireless access point etc.) this WiFi card
> performs perfectly, with no packet loss, low latencies, and maxes out
> transfers at about
On Thu, May 21, 2020 at 01:04:36AM +0200, stolen data wrote:
> I know the antennas are fine because I've already inspected both of
> them, along with the male SMC connectors on the card, the solder
> joints tying them to PCB, and even doing a continuity test with a
> multimeter to test connectivity
On Fri, May 22, 2020 at 05:12:23PM +0200, stolen data wrote:
> On Thu, May 21, 2020 at 9:11 AM Stefan Sperling wrote:
>
> > On Thu, May 21, 2020 at 01:04:36AM +0200, stolen data wrote:
> >
> > ...
> >
>
> > > > You can try MCS1, MCS2, ..., all the
On Sun, May 24, 2020 at 03:08:09PM +0200, Hendrik Meyburgh wrote:
> >Synopsis:ral interface is not working
> >Category:system
> >Environment:
> System : OpenBSD 6.7
> Details : OpenBSD 6.7-current (GENERIC.MP) #207: Fri May 22
> 01:31:04 MDT 2020
>
On Mon, May 25, 2020 at 11:46:22PM +0200, stolen data wrote:
> On Sat, May 23, 2020 at 9:57 AM Stefan Sperling wrote:
>
> > On Fri, May 22, 2020 at 05:12:23PM +0200, stolen data wrote:
> > > On Thu, May 21, 2020 at 9:11 AM Stefan Sperling wrote:
> > >
> > &g
On Mon, May 25, 2020 at 01:04:33AM -0700, bsah...@sbcglobal.net wrote:
> >Synopsis:
> >Category:
> >Environment:
> System : OpenBSD 6.7
> Details : OpenBSD 6.7-current (GENERIC.MP) #213: Sat May 23
> 20:38:40 MDT 2020
>
> dera...@amd64.openbsd.o
On Tue, May 26, 2020 at 07:33:07AM +, Mikolaj Kucharski wrote:
> >Synopsis:panic: ieee80211_encrypt: key unset for sw crypto: 0
> >Category:kernel
> >Environment:
> System : OpenBSD 6.7
> Details : OpenBSD 6.7-current (GENERIC.MP) #217: Sun May 24
> 21:53:33 MDT 20
On Tue, May 26, 2020 at 08:08:08AM +, Mikolaj Kucharski wrote:
> On Tue, May 26, 2020 at 09:56:02AM +0200, Stefan Sperling wrote:
> > On Tue, May 26, 2020 at 07:33:07AM +, Mikolaj Kucharski wrote:
> > > >Synopsis:panic: ieee80211_encrypt: key unset for sw cryp
On Tue, May 26, 2020 at 01:45:13PM +, Mikolaj Kucharski wrote:
> On Tue, May 26, 2020 at 11:16:30AM +, Mikolaj Kucharski wrote:
> > On Tue, May 26, 2020 at 10:37:09AM +0200, Stefan Sperling wrote:
> > >
> > > I don't yet have a definite idea what could
On Wed, May 27, 2020 at 01:02:18AM -0700, Brandon Sahlin wrote:
> > > iwm0: received msg 1/4 of the 4-way handshake from 38:3b:c8:21:5d:fa
> > > iwm0: sending msg 2/4 of the 4-way handshake to 38:3b:c8:21:5d:fa
> >
> > If the handshake fails like this, that usually means the key is wrong.
> >
On Thu, May 28, 2020 at 04:40:43AM -0700, Brandon Sahlin wrote:
> After some trial and error, I found the problem. My rather crufty
> /etc/hostname.iwm0 file set the mode to 11n. This worked with
> OpenBSD 6.6 with the problematic access point, but not with OpenBSD 6.7.
> Commenting out the mod
On Thu, May 28, 2020 at 08:36:08PM +, Mikolaj Kucharski wrote:
> On Wed, May 27, 2020 at 07:54:32AM +, Mikolaj Kucharski wrote:
> > On Wed, May 27, 2020 at 09:31:00AM +0200, Stefan Sperling wrote:
> > > > Uptime of 3h37m with following two entries (from dmesg):
> &
On Thu, May 28, 2020 at 02:12:44PM +0200, Stefan Sperling wrote:
> On Thu, May 28, 2020 at 04:40:43AM -0700, Brandon Sahlin wrote:
> > After some trial and error, I found the problem. My rather crufty
> > /etc/hostname.iwm0 file set the mode to 11n. This worked with
> >
On Sat, May 30, 2020 at 03:49:24PM +, Mikolaj Kucharski wrote:
> I see. While I was looking around I found that in function
> ieee80211_node_leave_rsn() there seems to be dead code
> assignment of ni->ni_rsn_state. With below change kernel
> compiles and I'm running it on athn access point and
On Sun, May 31, 2020 at 10:58:19AM +0200, Stefan Sperling wrote:
> On Sat, May 30, 2020 at 03:49:24PM +, Mikolaj Kucharski wrote:
> > I see. While I was looking around I found that in function
> > ieee80211_node_leave_rsn() there seems to be dead code
> > assignment of n
On Thu, Jun 11, 2020 at 10:14:34AM -0500, Tim Chase wrote:
> On booting 6.7 I see
>
> -
> athn0: no link
> athn0: no link... got link
> athn0: no link... sleeping
> -
>
> which is not a surprise having seen the "no network" in the if
On Thu, Jun 11, 2020 at 06:08:31PM -0500, Tim Chase wrote:
> and it works fine there. The big distinction is that after
>
> sending msg 4/4 of the 4-way handshake
>
> my `ifconfig athn0 debug` output is giving me these two lines in the
> 6.6 bsd.rd:
>
> received msg 1/2 of the group key ha
On Fri, Jun 12, 2020 at 07:13:39AM -0500, Tim Chase wrote:
> On 2020-06-12 09:19, Stefan Sperling wrote:
> > Can you please boot into 6.7, let it fail to connect, and then get
> > the output of the following command and show it to me?
> >
> > netstat -W athn0
>
On Wed, Jul 01, 2020 at 06:14:50PM -0500, Tim Chase wrote:
> Just wanted to check back in if there's anything else I can get you
> to help diagnose this.
Please try this patch. It fixes the issue for me.
It looks like my CCMP offload patch for athn(4) broke client mode,
even though it would occas
On Sat, Jul 04, 2020 at 04:34:23PM +0200, bw-open...@gmx.de wrote:
> I can easily reproduce this panic by doing enough on the network:
> Cloning a big git repository (which is
> what I did for the panic text above) or doing a 'sysupgrade -s' often
> is enough to reach the limits.
>
>
On Mon, Jul 06, 2020 at 03:27:37PM -0500, Tim Chase wrote:
> On 2020-07-03 20:33, Stefan Sperling wrote:
> > On Wed, Jul 01, 2020 at 06:14:50PM -0500, Tim Chase wrote:
> > > Just wanted to check back in if there's anything else I can get
> > > you to help diagnose
On Tue, Jul 07, 2020 at 06:38:46AM -0400, Jeremy O'Brien wrote:
> >Synopsis:iwm crash shortly after boot
> >Category:kernel
> >Environment:
> System : OpenBSD 6.7
> Details : OpenBSD 6.7-current (GENERIC) #321: Mon Jul 6 14:49:38
> MDT 2020
>
>
On Tue, Jul 07, 2020 at 07:05:33AM -0400, Jeremy O'Brien wrote:
> On Tue, Jul 7, 2020, at 06:50, Stefan Sperling wrote:
> >
> > Can you reproduce this with a freshly compiled kernel clean -current
> > sources?
> >
> > It looks like a problem in the Tx aggre
On Tue, Jul 07, 2020 at 11:31:08AM -0500, Tim Chase wrote:
> On 2020-07-07 08:50, Stefan Sperling wrote:
> > The diff has since been committed. Could you try a snapshot just
> > to see if that works?
>
> I pulled down the latest snap (#290 Jul 6 15:31:39 according to
>
On Wed, Jul 08, 2020 at 06:37:31PM -0500, Tim Chase wrote:
> > Are you able to run tcpdump on the AP itself or on the network
> > behind the AP? Do you see DHCP requests from the athn client
> > arriving there?
>
> The wireless router (also serving DHCP/DNS) is ISP-provided hardware.
> I put Wire
On Sat, Jul 11, 2020 at 10:22:10AM -0500, Tim Chase wrote:
> On 2020-07-11 10:34, Stefan Sperling wrote:
> > On Fri, Jul 10, 2020 at 10:20:07AM -0500, Tim Chase wrote:
> > > On 2020-07-10 09:58, Stefan Sperling wrote:
> > > > Does it work if you elimin
On Sun, Jul 12, 2020 at 08:25:43AM -0500, Tim Chase wrote:
> That said, I haven't yet applied your patch below (the second patch
> you sent me) since everything was working with the first one. Would
> you still like me to apply that patch and test too? Or are you
> satisfied with the patch you se
On Wed, Sep 16, 2020 at 08:39:19PM +, Mikolaj Kucharski wrote:
> This one seems random, on that machine I see it first time. CVS checkout
> is basically the build time as I first do cvs up and then make.
We have seen this before, haven't we?
This means another race condition exists.
Are you s
On Fri, Oct 09, 2020 at 12:21:13AM -0500, flint pyrite wrote:
> Update: I replaced my netgear N600 wifi router with a netgear ac1750.
> It has been a few days and I have not had the issue yet. I am thinking
> it was a router problem disconnecting and then ifconfig getting stuck
> in an uninteruptab
On Thu, Oct 08, 2020 at 05:05:29PM +0200, nicola.dellu...@delluomo-morettin.com
wrote:
> >Synopsis:after upgrade to latest snapshot iwx driver is not working at
> >all.
> >Category:system
> >Environment:
> System : OpenBSD 6.8
> Details : OpenBSD 6.8-current (GE
On Fri, Oct 09, 2020 at 11:26:11AM +0100, Jason McIntyre wrote:
> On Fri, Oct 09, 2020 at 11:24:17AM +0200, Stefan Sperling wrote:
> > On Thu, Oct 08, 2020 at 05:05:29PM +0200,
> > nicola.dellu...@delluomo-morettin.com wrote:
> > > >Synopsis:after upgrade to la
On Sat, Oct 10, 2020 at 11:58:57AM +0200, avv. Nicola Dell'Uomo wrote:
> If I can do something to help, please let me know.
Does this change the error reported by firmware in response to
the driver's "mac context removal" command?
diff 97da2ad2205f020c8bd54c846ec35e7fc8c6fe75 /usr/src
blob - 0482
On Sat, Oct 10, 2020 at 08:07:09PM +0200, avv. Nicola Dell'Uomo wrote:
> Hi,
>
> I applied the patch and - at the moment - the driver works without errors.
>
> I'll report if new errors arise.
>
> Thank you, let me know if you need diagnostic datas of some kind!
Could you please check if the pr
On Sat, Oct 10, 2020 at 08:47:18PM +0200, avv. Nicola Dell'Uomo wrote:
>
> Do you mean by restoring GENERIC #103 or by compiling from latest src
> without your patch?
>
> On 10/10/20 20:20, Stefan Sperling wrote:
> > On Sat, Oct 10, 2020 at 08:07:09PM +0200, avv. Nicola
On Sat, Oct 24, 2020 at 03:10:05PM +0200, Filippo Valsorda wrote:
> >Synopsis:kernel page fault in "sddetach -> bufq_destroy" during "bioctl
> >-d"
> >Category:kernel
> >Environment:
> System : OpenBSD 6.8
> Details : OpenBSD 6.8 (GENERIC.MP) #98: Sun Oct 4 18:13:26 M
On Sat, Oct 24, 2020 at 04:11:00PM +0200, Filippo Valsorda wrote:
> Fair enough, but "there's no auto-assembly and it's inefficient and
> nothing stops you from messing with the intermediate discipline" is a
> different kind of not supported than "you should expect kernel panics".
>
> If the latte
On Sun, Oct 25, 2020 at 09:02:35PM +, l...@bandarra.pt wrote:
> >Synopsis:Panic when writing with nvim C program to use sockets
> >Category:user amd64
> >Environment:
> System : OpenBSD 6.8
> Details : OpenBSD 6.8 (GENERIC.MP) #98: Sun Oct 4 18:13:26 MDT 2020
>
On Sun, Nov 15, 2020 at 10:52:28AM +, henkjan gersen wrote:
> >Synopsis: BackSpace does not delete some symbols typed with AltGr on the
> >console/terminal
> >Category: user
> >Environment:
> System : OpenBSD 6.8
> Details : OpenBSD 6.8 (GENERIC) #97: Sun Oct 4 18:00:46 MDT 2
On Mon, Nov 16, 2020 at 10:59:45AM +, Mikolaj Kucharski wrote:
> It happened again. This time on current. I was on Android phone using
> Signal and other laptop on urwn(4) was fetching newest packages snapshot.
>
> In this email thread it's different physical hardware, but I think
> it's same
On Tue, Nov 17, 2020 at 11:40:44PM -0500, Ashton Fagg wrote:
> >Synopsis: Wifi gives out sporadically, unclear why
> I really can't say how to replicate it reliably as it appears
> random. It doesn't even occur at a regular cadence - sometimes
> it happens multiple times in
On Wed, Nov 18, 2020 at 01:30:47PM +0100, Stefan Sperling wrote:
> Is the problem related to raoming, as in, if your AP offers the same ESSID
> on multiple channels, does it "help" if you configure a unique ESSID per
> frequency band/channel?
A simpler way to check this might
On Wed, Nov 18, 2020 at 01:36:48PM -0500, Ashton Fagg wrote:
> However, for a day or so I was running with only a single AP and I was
> experiencing this problem. I now have 2 of the same APs, and it appears
> to happen no matter which one I'm connected to (APs are Ruckus R310).
If the output of '
On Thu, Dec 10, 2020 at 03:29:39PM +0800, zxystd wrote:
> The input packet shall be a mbuf chain so we should not only free the single
> mbuf.
> Alought it is a error path we should not go to.
> ---
> sys/net80211/ieee80211_crypto.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Yes, thi
On Thu, Jan 21, 2021 at 12:47:25AM +, James Cook wrote:
> >Synopsis:iwx0 repeatedly goes offline with "unhandled firmware response
> >0x3fd"
> >Category:kernel
> >Environment:
> System : OpenBSD 6.8
> Details : OpenBSD 6.8-current (GENERIC.MP) #284: Wed Jan 20
> 0
On Fri, Jan 22, 2021 at 01:51:28AM +, James Cook wrote:
> On Thu, Jan 21, 2021 at 02:22:40PM +0100, Stefan Sperling wrote:
> > On Thu, Jan 21, 2021 at 12:47:25AM +, James Cook wrote:
> > > >Synopsis:iwx0 repeatedly goes offline with "unhandled firmw
On Fri, Jan 22, 2021 at 12:23:28PM +0100, Stefan Sperling wrote:
> On Fri, Jan 22, 2021 at 01:51:28AM +, James Cook wrote:
> > Here's a censored excerpt from output of tshark -r (the output of
> > tcpdump). IntelCor_AA:AA:AA is moth and HitronTe_BB:BB:BB is my router
>
On Fri, Jan 22, 2021 at 01:51:28AM +, James Cook wrote:
> On Thu, Jan 21, 2021 at 02:22:40PM +0100, Stefan Sperling wrote:
> > On Thu, Jan 21, 2021 at 12:47:25AM +, James Cook wrote:
> > > Jan 21 00:36:13 moth /bsd: iwx0: unhandled firmware response
> > > 0x3
On Mon, Jan 25, 2021 at 11:48:14PM +, James Cook wrote:
> > Switching to channel 9 or 5GHz channel 153 seems to help: after a few
> > minutes of use (mostly on 153) I haven't observed the problem again.
> >
> > However this raises another question.
> >
> > In fact my AP has a 2.4GHz network a
1 - 100 of 487 matches
Mail list logo
