On Sun, Apr 28, 2024 at 01:46:22PM +0200, BESSOT Jean-Michel wrote:
> Hello
>
> qwx does not work after the last snapshot.
>
> There is an error message in dmesg that I send.
>
> If you need more information feel free to ask.
>
> bye
> qwx0: could not allocate DP SRNG DMA memory
Does this
On Sun, Apr 21, 2024 at 06:31:39PM +0200, Kirill A. Korinsky wrote:
> Greeting,
>
> finally I've catch something. I not sure is it the same error or not, but it
> seems right to share anyway.
>
> It was get from snapshot which was installed about 3 days ago.
>
> Apr 21 10:59:40 matebook /bsd:
On Mon, Apr 22, 2024 at 10:46:50AM +0200, Peter J. Philipp wrote:
> Hi,
>
> I have a shortage of RJ45 adapters so I had to expose one host on wifi, for
> this I set up an access point of type "AVM Fritz!Box 7390" with latest
> firmware
> from last year.
>
> Soon I started facing deauth
On Wed, Mar 27, 2024 at 02:08:27PM +0100, Stefan Sperling wrote:
> On Tue, Mar 26, 2024 at 11:05:49PM +0100, Patrick Wildt wrote:
> > On Fri, Mar 01, 2024 at 12:00:29AM +0100, Alexander Bluhm wrote:
> > > Hi,
> > >
> > > When doing flood ping transm
On Tue, Mar 26, 2024 at 11:05:49PM +0100, Patrick Wildt wrote:
> On Fri, Mar 01, 2024 at 12:00:29AM +0100, Alexander Bluhm wrote:
> > Hi,
> >
> > When doing flood ping transmit from a machine and simultaneously
> > ifconfig down/up in a loop, dwqe(4) interface driver crashes.
> * Don't run
On Fri, Mar 22, 2024 at 01:30:26PM +0100, be...@stuerz.xyz wrote:
> >Synopsis:urndis driver doesn't work on Thinkpad T21 (i386)
> >Category:i386
> >Environment:
> System : OpenBSD 7.4
> Details : OpenBSD 7.4 (GENERIC) #2: Fri Dec 8 15:41:12 MST 2023
>
On Wed, Mar 13, 2024 at 12:05:59AM +0100, Kirill A. Korinsky wrote:
> On Tue, 27 Feb 2024 08:45:44 +0100,
> Stefan Sperling wrote:
> >
> > > Anyway, I'll keep debug enabled for the case if frimeware error happens.
> >
> > Yes, that would still be interesting, tha
On Mon, Feb 26, 2024 at 10:17:20PM +0100, Kirill A. Korinsky wrote:
> On Mon, 26 Feb 2024 12:39:12 +0100,
> Stefan Sperling wrote:
> >
> > On Mon, Feb 26, 2024 at 11:40:35AM +0100, Kirill A. Korinsky wrote:
> > > all of this seems like a strong indicator that the iss
On Mon, Feb 26, 2024 at 11:40:35AM +0100, Kirill A. Korinsky wrote:
> all of this seems like a strong indicator that the issue is inside iwx
You don't need to try hard to convince me that there could be
a bug in iwx. Yes, there will always be bugs in iwx. Many have
been fixed already but there
On Sun, Feb 25, 2024 at 10:17:37PM +0100, Kirill A. Korinsky wrote:
> On Sun, 25 Feb 2024 17:32:46 +0100,
> Stefan Sperling wrote:
> >
> > I have less than 2ms ping latency to my 5 GHz AP over iwx.
> > So this is probably not an issue in iwx but something else.
&
On Sun, Feb 25, 2024 at 05:19:33PM +0100, Kirill A. Korinsky wrote:
> Well,
>
> I just rebooted to a new snapshot, and WiFi has been future degradated.
>
> I do run a MPD sync in background which downloads some files via HTTP,
> but I may run before, and it never creates an issue.
>
> Meanwhile
On Sun, Feb 18, 2024 at 11:21:15AM -1000, Todd Carson wrote:
>
> Thanks for the pointers; updated diff below to set the MAC in
> bwfm_init() if preinit has already run.
>
> Works on boot with "lladdr random" as the first line in hostname.bwfm0,
> and also changing the lladdr after boot with
On Sat, Feb 17, 2024 at 06:27:40PM -1000, Todd Carson wrote:
>
> On a Raspberry Pi 4 running a recent snapshot, I found that the built-in
> bwfm interface would fail to receive non-broadcast traffic after
> changing the MAC address with ifconfig (for example by having
> "lladdr random" in
On Fri, Feb 16, 2024 at 11:25:51AM +, Stuart Henderson wrote:
> Also: regardless of whether it really makes sense for a given network,
> sometimes a network operator will do this anyway and as a user you have
> no control over it - and based on Kirill's description this seems a
> regression
On Fri, Feb 16, 2024 at 11:45:30AM +0100, Kirill A. Korinsky wrote:
> Stefan,
>
> On Fri, 16 Feb 2024 10:13:50 +0100,
> Stefan Sperling wrote:
> >
> > If your AP still announces 6M even while you've disabled this rate in
> > settings,
> > then the AP is broke
On Fri, Feb 16, 2024 at 03:22:07AM +0100, Kirill A. Korinsky wrote:
> Thus, disabling 5Ghz does help. that lead me to dig an issue on network
> settings
> side. After poking around I've discovered that settings which triggers an
> issue
> is "Minimum Data Rate Control" inside Unifi UI. It has
On Tue, Jan 16, 2024 at 02:38:58PM +0800, Kevin Lo wrote:
> The below diff fixes clang warning about possible unaligned access.
> With that fixed, iwm(4) works as expected on my Rock 3A.
>
> iwm0 at pci1 dev 0 function 0 "Intel Dual Band Wireless-AC 9260" rev 0x29,
> msix
> iwm0: hw rev 0x320,
On Wed, Dec 20, 2023 at 02:00:36PM -0800, Greg Steuck wrote:
> I'm sending this with the subject of the bug reported before in hope it will
> join
> the thread even though I'm seeing this with an iwm(4) interface. I'm
> running a Nov 3 snap of -current.
>
> The messages seem mostly harmless as
On Wed, Dec 13, 2023 at 12:10:25PM +0100, Gabriel Brito wrote:
> Hello,
>
> I just upgraded to current (7.4 GENERIC.MP#1485 amd64) and can no longer
> connect to a wireless networks using iwx - I tried with two different
> networks.
>
> Sorry for the lack of further information - don't know what
On Sat, Nov 25, 2023 at 08:20:47AM -0700, Theo de Raadt wrote:
> What you are asking for is too difficult to do.
>
> netstart is a shell script. shell script arguments are not 8 bit clean,
> because the the sh language has many meta & escape characters.
>
> Your configuration exceeds what can
On Thu, Nov 23, 2023 at 08:26:32PM +, Stuart Henderson wrote:
> On 2023/11/23 19:38, Stefan Sperling wrote:
> > It is possible that our driver is trying to use an incompatible
> > firmware image on this particular device. Which firmware file name
> > is loaded by the iwlwi
On Thu, Nov 23, 2023 at 12:46:24PM +, Stuart Henderson wrote:
> and here are kernel messages with IWX_DEBUG defined
>
> iwx0: L1 Disabled - LTR Enabled
> iwx0: ucode type 0 section 0
> iwx0: ucode type 0 section 1
> iwx0: ucode type 0 section 2
> iwx0: ucode type 0 section 3
> iwx0: ucode
On Fri, Aug 25, 2023 at 12:14:45AM -0600, Matthew Webb wrote:
> Thank you Stefan for the discussion.
>
> FWIW, I have now installed another operating system (Arch Linux) on my
> computer alongside OpenBSD 7.3, and the wireless network adapter works
> correctly and without issue, so it appears
On Wed, Aug 23, 2023 at 07:25:48PM -0600, Matthew Webb wrote:
> I configured debug to dump the driver status, shown in messages attached.
> I've also included the pcidump for the network adapter.
Thanks.
> I found a potentially related discussion about the iwx driver:
>
On Wed, Jul 26, 2023 at 02:45:29PM +, Miguel Landaeta wrote:
> >Synopsis:iwx: Firmware for Intel Wi-Fi 6 AX211 couldn't be loaded
> iwx0: using firmware iwx-so-a0-gf-a0-77
Can you tell me which firmware image the Linux kernel is loading for
your device?
Perhaps OpenBSD is misdetecting
On Thu, Jun 29, 2023 at 11:31:33AM +0200, Martin Pieuchot wrote:
> On 29/06/23(Thu) 11:17, Stefan Sperling wrote:
> >
> > iwm_intr already runs at IPL_NET. What else would be required?
>
> Are we sure all accesses to `ic_tree' are run under KERNEL_LOCK()+splnet()?
A quick
On Thu, Jun 29, 2023 at 10:59:32AM +0200, Martin Pieuchot wrote:
> On 28/06/23(Wed) 15:47, Moritz Buhl wrote:
> > Dear bugs@,
> >
> > with the following snapshot I had two panics on my x270 recently.
>
> This is a bug in iwm(4) suggesting a missing SPL protection.
>
> > sysctl kern.version
> >
On Mon, Apr 03, 2023 at 06:24:38PM +, miko...@kucharski.name wrote:
> Apr 3 16:42:56 x1c /bsd: iwx0: begin background scan
> Apr 3 16:42:57 x1c /bsd: iwx0: Start UMAC Error Log Dump:
> Apr 3 16:42:57 x1c /bsd: iwx0: Status: 0x239, count: 7
> Apr 3 16:42:57 x1c /bsd: iwx0: 0x20002806 |
On Sat, Feb 11, 2023 at 06:32:31PM +0300, Vitaliy Makkoveev wrote:
> Unfortunately the diff doesn't help. I attached photos with debug
> information and panic report.
Based on the command code in the firmware trace the error seems to be
caused by the driver sending this command:
#define
On Sat, Feb 11, 2023 at 03:40:48PM +0300, Vitaliy Makkoveev wrote:
> >Synopsis:iwx(4) panic on resume after hibernation
> >Category:hibernate/resume
> >Environment:
> System : OpenBSD 7.2
> Details : OpenBSD 7.2-current (GENERIC.MP) #1021: Sun Feb 5
> 09:52:50 MST
On Sun, Jan 01, 2023 at 05:54:55PM -0800, Epix Gamor wrote:
> # ISSUE
> OpenBSD crashes when I try to do my WiFi.
>
> # WHAT I DID TO GET THE ISSUE
> I installed a fresh copy of OpenBSD on my machine and the first thing
> I did was to permit doas and then I want to set up my WiFi.
> I’m setting
On Tue, Dec 27, 2022 at 06:50:55PM +, Jeremy Potter wrote:
> One clue that I do have is that every time I restarted my Wi-Fi, the kernel
> log
> printed something along the lines of:
>
> iwx0: unhandled firmware response 0x5f4/0x200c
Response 0x5f4 is a "monitor notification" sent by
On Tue, Nov 15, 2022 at 03:07:05PM +0100, Leah Neukirchen wrote:
>
> I hit the same issue on a 7.2-RELEASE system, which was idle and had
> roughly 3 weeks of uptime.
>
> Stopped at rt_ifa_del+0x39: movb 0x1b6(%rax),%bl
> Same backtrace as in parent message.
>
> The system is virtualized on
On Fri, Nov 11, 2022 at 06:46:31PM +, Andrew Grillet wrote:
> I was unable to compile and test the diff - compile times exceeded a week
> on a T1000, and
> then I took ill.
>
> I now confirm that this problems is present on 7.2 and appears to affect my
> T5120 as well.
> I can create configs
On Fri, Sep 16, 2022 at 09:58:44AM +0200, Adam Szewczyk wrote:
> My mistake in creating a bug for wireless it should be iwm (copied wrong
> file name in a hurry). Is that are you wrote about iwx also true for iwm?
At this low level the drivers are equivalent.
> Sorry for the trouble. I just want
On Fri, Sep 16, 2022 at 08:27:59AM +0200, Adam Szewczyk wrote:
> Checked on actual hardware it seems to work fine. So I report it also to
> Qubes and Xen Project, but marmarek (head of qubes development team)
> suggest that it can be a problem with driver itself:
> "I'm not sure if that's
On Sun, Sep 04, 2022 at 07:34:04PM +0300, Vitaliy Makkoveev wrote:
> I suspect missing netlock in the config path or within timeout handler,
> but exclusive netlock assertion makes sense.
>
> Also, we could have "double protection" here, like we have for
> `if_list'. I mean we hold both kernel
On Sat, Aug 27, 2022 at 11:32:24PM +0300, Vitaliy Makkoveev wrote:
> > On 27 Aug 2022, at 22:03, Alexander Bluhm wrote:
> >
> > On Sat, Aug 27, 2022 at 03:14:15AM +0300, Vitaliy Makkoveev wrote:
> >>> On 27 Aug 2022, at 00:04, Alexander Bluhm wrote:
> >>>
> >>> Anyone willing to test or ok
On Wed, Aug 24, 2022 at 03:14:35PM +0200, Alexander Bluhm wrote:
> What are you doing with the machine? Forwarding, IPv6, Stress test?
> Do you have network interfaces with multiple network queues?
It is a build box, which also serves snapshots over http. I am the only
user of the httpd server
On Tue, Aug 23, 2022 at 02:16:27PM +0200, Alexander Bluhm wrote:
> On Tue, Aug 23, 2022 at 12:23:05PM +0200, Stefan Sperling wrote:
> > On Tue, Aug 23, 2022 at 11:43:22AM +0200, Alexander Bluhm wrote:
> > > On Tue, Aug 23, 2022 at 10:15:22AM +0200, Stefan Sperling wrote:
> &g
On Tue, Aug 23, 2022 at 11:43:22AM +0200, Alexander Bluhm wrote:
> On Tue, Aug 23, 2022 at 10:15:22AM +0200, Stefan Sperling wrote:
> > I found one of my amd64 systems running -current, built on 12th of
> > August, has crashed as follows.
>
> I there any chance that the kerne
I found one of my amd64 systems running -current, built on 12th of
August, has crashed as follows.
I am not sure if this is still relevant; please excuse the noise if
this has already been found and fixed.
kernel: protection fault trap, code=0
Stopped at rt_ifa_del+0x39:movb
On Fri, Jul 22, 2022 at 10:25:47PM +0300, Mikhail wrote:
> Moving to bugs@, hoping to get some attention.
Fixed in-tree now, thank you.
I've also fixed another instance of the same i + j mistake in the PMKID loop.
On Tue, Jul 19, 2022 at 05:01:48PM +0200, Patrick Wildt wrote:
> No, it's not inverted. If bwfm_pci_send_mb_data() fails we want to
> re-init the device, that's what both Linux and OpenBSD are doing.
Right. I came to the same conclusion while taking a brief look.
> Better questions are: why is
On Sat, Jul 09, 2022 at 10:14:38AM -0400, jdp_ man wrote:
> I recently discovered OpenBSD and eventually tried it in a physical PC.
> The PC is an Optiplex 790 with an add-in WiFi card. i5 2400 w/o GPU.
> The card internally is a Atheros AR9300, and it seems support is gone,
> as of this commit
On Sun, Jun 19, 2022 at 02:43:20PM +, Lucas wrote:
> Hello,
>
> As the subject reads, yesterday I update my Lenovos T420 and X230.
> During sysupgrade autoupgrade and afterwards I started getting firmware
> errors and wifi became unusable. I reached stsp@ off-list to know how to
> provide the
On Thu, Apr 21, 2022 at 10:31:46PM +0200, Stefan Sperling wrote:
> On Thu, Apr 21, 2022 at 09:15:57PM +0200, Stefan Sperling wrote:
> > On Thu, Apr 21, 2022 at 08:58:48PM +0200, Sven Wolf wrote:
> > > But when I build a new kernel with the sources from 2022-03-15 everything
&
On Thu, Apr 21, 2022 at 09:15:57PM +0200, Stefan Sperling wrote:
> On Thu, Apr 21, 2022 at 08:58:48PM +0200, Sven Wolf wrote:
> > But when I build a new kernel with the sources from 2022-03-15 everything is
> > fine.
> >
> > Maybe this commit causes this behaviour/b
On Thu, Apr 21, 2022 at 08:58:48PM +0200, Sven Wolf wrote:
> But when I build a new kernel with the sources from 2022-03-15 everything is
> fine.
>
> Maybe this commit causes this behaviour/bug
> https://marc.info/?l=openbsd-cvs=16472610775=2
Looks like a bug in ral(4) (uninitialized
On Tue, Apr 05, 2022 at 10:29:17AM +, open...@ploum.eu wrote:
> Trying to install OpenBSD 7.0 from USB key on the following laptop :
>
> Starlabs Star Lite MkII.
>
>
> The install refuse to load the wifi driver with the following error :
Theo already answered this part of your question.
>
On Mon, Apr 04, 2022 at 09:58:09PM -0400, Ashton Fagg wrote:
> >Synopsis:iwx(4) device timeouts on 802.11ac networks
> >Category:Bug/driver issue
> >Environment:
> System : OpenBSD 7.1
> Details : OpenBSD 7.1 (GENERIC.MP) #458: Sun Apr 3 23:10:53 MDT
> 2022
>
On Sun, Mar 20, 2022 at 09:57:03PM +0100, Sven M. Hallberg wrote:
> >Synopsis:Kernel page fault in iwm (related to suspend?)
> >Category:kernel
> >Environment:
> System : OpenBSD 7.1
> Details : OpenBSD 7.1-beta (GENERIC.MP) #422: Tue Mar 15 11:28:22
> MDT 2022
>
On Fri, Jan 21, 2022 at 08:26:18AM +0100, Christian Ehrhardt wrote:
>
> Hi,
>
> On Fri, Jan 21, 2022 at 12:00:54AM -0700, Theo de Raadt wrote:
> > > In addition, I checked the code of dhclient and while it does listen
> > > to the RTM_80211INFO messages it will only use them to do a RESTART
On Thu, Jan 20, 2022 at 05:13:22PM +0100, Christian Ehrhardt wrote:
>
> Hi,
>
> The wpa supplicant (tries to) use routing messages of type
> RTM_80211INFO to detect WLAN access point changes. If the
> SSID or the BSSID changes compared to the last RTM_80211INFO
> message an ASSOC event is
On Sat, Jan 15, 2022 at 09:00:44PM +, Mikolaj Kucharski wrote:
> I'm wondering what is recommended setup for swap with full disk
> encryption. Because swap is encrypted by default I decided to put
> it outside of softraid crypto - sd0b, where OpenBSD is on sd1a and
> I guess kernel expects
On Sat, Jan 15, 2022 at 10:03:07AM -0700, Theo de Raadt wrote:
> Additionally, the /boot code must be able to see that the disk contains
> a hibernate signature, and this may not work if your swap partition
> is at such a far into the disk.
>
> #size offset fstype
On Thu, Jan 13, 2022 at 07:14:28AM +0100, Sven Wolf wrote:
>
>
> On 1/12/22 21:07, Stefan Sperling wrote:
> > On Wed, Jan 12, 2022 at 08:58:28PM +0100, Sven Wolf wrote:
> > > With following patches I got also the wireless nic working.
> >
> > Nice! I am gl
On Wed, Jan 12, 2022 at 08:58:28PM +0100, Sven Wolf wrote:
> With following patches I got also the wireless nic working.
Nice! I am glad to see support for additional iwx devices.
Could you try this patch by Iraklis Karagkiozoglou please?
https://marc.info/?l=openbsd-tech=164194046522312=2
I
On Wed, Jan 12, 2022 at 10:50:50AM +0100, Christian Ehrhardt wrote:
> diff --git a/sys/kern/uipc_mbuf.c b/sys/kern/uipc_mbuf.c
> index 5e4cb5ba88..d8b9e751c6 100644
> --- a/sys/kern/uipc_mbuf.c
> +++ b/sys/kern/uipc_mbuf.c
> @@ -957,8 +957,6 @@ m_pullup(struct mbuf *m0, int len)
>
> head =
On Fri, Jan 07, 2022 at 06:10:09PM +0100, Alessandro De Laurenzis wrote:
> Greetings,
>
> This is one of my hardest reports, since both the symptoms and the overall
> context are rather obscure...
>
> On a Thinkpad T430 (complete dmesg in attachment) equipped with a Intel
> Centrino Ultimate-N
On Fri, Jan 07, 2022 at 08:57:54AM +, Anant Pande wrote:
> In particular, regarding the wifi, the dmesg produced ‘ "Intel Wi-Fi 6
> AX201" rev 0x20 at pci0 dev 20 function 3 not configured ‘, which is what I
> got when I had installed OpenBSD release and snapshot.
>
> 0:20:3: Intel Wi-Fi
On Thu, Jan 06, 2022 at 06:20:11PM +0100, Peter Nicolai Mathias Hansteen wrote:
>
>
> > 6. jan. 2022 kl. 18:00 skrev Anant Pande :
> >
> > Post installation after fw_update ( which did not automatically install the
> > iwx driver, so had to manually do ‘fw_update iwx’), the wifi is not
> >
On Wed, Jan 05, 2022 at 03:11:47PM +0100, Marek Kozlowski wrote:
> :-)
>
> On 1/5/22 11:42, Crystal Kolipe wrote:
> > On Wed, Jan 05, 2022 at 09:12:48AM +0100, Marek Kozlowski wrote:
> > > After I set up the ESSID and WPA-PSK the following message is displayed:
> > >
> > > iwn0: could not read
On Sun, Dec 19, 2021 at 12:20:18PM -0300, João Victor wrote:
> >Synopsis:
> >Category:
> >Environment:
> System : OpenBSD 7.0
> Details : OpenBSD 7.0 (GENERIC.MP) #232: Thu Sep 30 14:25:29
> MDT 2021
> dera...@amd64.openbsd.org:
>
On Sat, Dec 11, 2021 at 06:28:53PM -0700, Ted Bullock wrote:
> On 2021-12-11 5:39 a.m., Mark Kettenis wrote:
> >> Date: Sat, 11 Dec 2021 05:10:41 -0700
> >> From: Ted Bullock
> >
> > The are several reasons why that test can fail though. It can be an
> > endian-ness issue or on sparc64 it could
On Tue, Dec 07, 2021 at 11:38:51AM +, Mikolaj Kucharski wrote:
> More than a week of uptime on both machines:
>
> pce-0041# uptime
> 11:30AM up 8 days, 18:48, 1 user, load averages: 0.02, 0.05, 0.01
>
> pce-0035# uptime
> 11:31AM up 8 days, 18:39, 1 user, load averages: 0.11, 0.14, 0.08
>
On Sun, Dec 05, 2021 at 11:05:32AM -0600, Scott Cheloha wrote:
> > diff 0b61c8235787960f0010ef627ea5b2c6309a81f0
> > de98c050ea709bdb8e26be40ab0cc82ef9afed80
> > blob - 7bb68194dd78417b06c59f81d1ebbff4165203d8
> > blob + 5b9a969258074fde29e21a33ac035cf170ec3b03
> > --- sys/net80211/ieee80211.c
>
On Sat, Dec 04, 2021 at 09:32:40PM +0300, Vitaliy Makkoveev wrote:
> I think rtm_80211info() could follow the if_link_state_change()
> way and use task for that.
Indeed. I did not realize that if_link_state_change() schedules a task.
This means ieee80211_set_link_state() is already deferring
On Sat, Dec 04, 2021 at 07:19:23PM +0100, Stefan Sperling wrote:
> For this particular case, yes.
> But that won't solve ieee80211_set_link_state() being called from
> interrupt context, would it?
Below is a breakdown of all callers by context.
I grepped for direct callers. My search di
On Sat, Dec 04, 2021 at 07:06:35PM +0100, Tobias Heider wrote:
> On Sat, Dec 04, 2021 at 06:50:54PM +0100, Stefan Sperling wrote:
> > On Sat, Dec 04, 2021 at 10:37:53AM -0600, Scott Cheloha wrote:
> > > Hit a witness panic during boot yesterday. Can't repro, have never
&g
On Sat, Dec 04, 2021 at 10:37:53AM -0600, Scott Cheloha wrote:
> Hit a witness panic during boot yesterday. Can't repro, have never
> seen it before. The photo is a mess (ask if you want it) but the
> backtrace is:
>
> panic
> witness_checkorder
> rw_enter_write
> solock
> route input
>
On Wed, Nov 17, 2021 at 07:53:44PM +0100, Stefan Sperling wrote:
> On Wed, Nov 17, 2021 at 03:25:36PM +, Mikolaj Kucharski wrote:
> > On Mon, Nov 15, 2021 at 12:33:09PM +, Mikolaj Kucharski wrote:
> > > I have more panics, with couple of minutes gap between
> >
On Fri, Nov 26, 2021 at 07:14:36PM -0300, Salvador Sabaini wrote:
> Tried booting a newer Linux ISO, its loading QuZ-a0-jf-b0-63.ucode
> version 63.c04f3485.0
>
> It still detects it as being an Intel(R) Wireless-AC 9560
I have added QuZ-a0-jf-b0 iwx-firmware to fw_update in -current.
But I
On Tue, Nov 23, 2021 at 04:05:20PM -0300, s...@rtfm.com.ar wrote:
> >Synopsis:Intel Wi-Fi 6 AX201 driver not getting attached by the kernel.
> >Category:kernel
> >Environment:
> System : OpenBSD 7.0
> Details : OpenBSD 7.0-current (GENERIC.MP) #111: Sun Nov 21
>
On Mon, Nov 22, 2021 at 10:58:08AM +, Laurence Tratt wrote:
> On Sun, Nov 21, 2021 at 06:06:33PM +0100, Stefan Sperling wrote:
>
> Hello Stefan,
>
> >> As of a kernel from a couple of days ago, iwx semi-regularly stops
> >> associating with my wirel
On Sun, Nov 21, 2021 at 09:05:29AM +, Laurence Tratt wrote:
> As of a kernel from a couple of days ago, iwx semi-regularly stops
> associating with my wireless AP. An easy way to trigger this is "pkg_add
> -u": at some point, downloading stops mid-package, and I need to "sh
> /etc/netstart" to
On Wed, Nov 17, 2021 at 07:53:44PM +0100, Stefan Sperling wrote:
> I don't see where and how this could happen, but this seems to be where
> this bug is hiding. Multicast frames are also never encrypted, so they
> would never even trigger any attempt to use a key.
Sorry, I was not ma
On Wed, Nov 17, 2021 at 03:25:36PM +, Mikolaj Kucharski wrote:
> On Mon, Nov 15, 2021 at 12:33:09PM +, Mikolaj Kucharski wrote:
> > I have more panics, with couple of minutes gap between
> > ieee80211_setkeysdone() from ieee80211_proto.c and panic
> > in ieee80211_encrypt() from
On Mon, Nov 08, 2021 at 01:57:53PM +0100, Paul de Weerd wrote:
> Hi all,
>
> After upgrading my laptop to a newer snapshot this weekend, I started
> getting panics. I was running OpenBSD 7.0-current (GENERIC.MP) #60:
> Sun Oct 31 13:27:05 MDT 2021 before the upgrade. Hand-typed from a
>
On Mon, Nov 08, 2021 at 06:37:17AM +, Renato Aguiar wrote:
> OpenBSD 7.0 kernel panics when veb is used with a rule filter to tag
> packets coming from a vlan interface, for example:
>
> ifconfig veb0 rule pass in on vlan10 tag FOO
> panic: kernel diagnostic assertion
On Sat, Nov 06, 2021 at 07:53:57PM +0100, Paul de Weerd wrote:
> It's not so much throughput as it is latency. From the rpi to its
> gateway I see solid RTTs (note that I'm SSH'd into the raspberry to
> run this command):
>
> 64 bytes from 192.168.34.1: icmp_seq=0 ttl=255 time=1.870 ms
> 64
On Mon, Oct 18, 2021 at 07:14:57PM +0200, Richard Ulmer wrote:
> > Something else you could try is downgrading the firmware image.
> > This can be done without patching the kernel by swapping out the
> > firmware file:
> >
> > mv /etc/firmware/iwm-7265D-29 /etc/firmware/iwm-7265D-29.orig
> >
On Mon, Oct 18, 2021 at 12:07:43AM +0200, Stefan Sperling wrote:
> On Sun, Oct 17, 2021 at 08:46:47PM +0200, Richard Ulmer wrote:
> > >Synopsis: iwm sporadically disconnects WI-FI connection
> > >Category: system
> > >Environment:
> > System : OpenB
On Sun, Oct 17, 2021 at 08:46:47PM +0200, Richard Ulmer wrote:
> >Synopsis:iwm sporadically disconnects WI-FI connection
> >Category:system
> >Environment:
> System : OpenBSD 7.0
> Details : OpenBSD 7.0 (GENERIC.MP) #232: Thu Sep 30 14:25:29 MDT
> 2021
>
On Sun, Oct 03, 2021 at 09:35:37AM +0200, Landry Breuil wrote:
> Hi,
>
> i've been having iwm(4) instability on a X1 Gen3 issues since july
> (symptom/reproducer: unable to fetch base70.tgz, stalls after 100Mb and link
> goes down, ifconfig up/down/reassoc 'resolves' it - pkg_add -u also fails
>
On Sat, Sep 25, 2021 at 02:03:40AM +, Mikolaj Kucharski wrote:
> I've added more info, probably mainly for myself. I'm not sure where to
> go with this information yet.
We need to figure out what makes this code use a group key which
has been cleared.
Please add printfs for lines of code
On Fri, Sep 24, 2021 at 06:34:42PM +0200, BESSOT Jean-Michel wrote:
> Hello
>
> I didi test your patch. I run a bkg_add -ui without timeout error now. I
> continue to test to see if it wasn't luck but your patch probably fixed the
> bug.
>
> Thank you
>
> bye
Thanks, I have committed the
On Sun, Sep 19, 2021 at 03:10:01PM +0200, BESSOT Jean-Michel wrote:
> Hello
>
> Here is the problem, I loose the wifi connection after some time on my
> computer . Mostly when I use a cvs -q up -Pd or a pkg_add -ui.. I get the
> error message:
>
> iwm0: device timeout
>
> It gets back after
On Sun, Sep 12, 2021 at 03:03:30PM +, macondo wrote:
> http://www.fmovies.toerror code 102630
> http://www.aljazeera.comerror code: media_err_src_not_supported
> http://www.bbc.comsame
> >From Firefox:To play video you may need to install the required video codecs.
This should fix it: pkg_add
On Sat, Aug 07, 2021 at 08:59:33PM -0700, Bryan Linton wrote:
> On 2021-08-07 16:05:34, Bryan Linton wrote:
> > >Synopsis: The system randomly panics with the message: panic:
> > >config_detach: forced detach of iwm0 failed (45)
> > >Category: system
> > >Environment:
> > System :
On Thu, Jul 08, 2021 at 04:00:15PM +0200, land...@asia.com wrote:
> >Synopsis:
> >Category:
> >Environment:
> System : OpenBSD 6.9
> Details : OpenBSD 6.9 (GENERIC) #4: Mon Jun 7 08:20:14 MDT 2021
>
>
On Mon, May 31, 2021 at 07:04:57PM +0200, Peter N. M. Hansteen wrote:
> yes, the only reason I do not use that at the moment is that for some reason
> that interface is unable to load the firmware correctly (possibly needing a
> variant we have not encountered earlier). What I get is
>
> wx0:
On Mon, May 31, 2021 at 06:10:22PM +0200, Peter N. M. Hansteen wrote:
> I was hoping one of the existing realtek wifi drivers might do the trick
> but apparently not, as of right now.
>
> Sendbug, pcidump and usbdevs output attached.
None of the 11ac realtek adapters are supported yet.
They need
On Fri, May 14, 2021 at 02:39:15PM +0200, Matthias Schmidt wrote:
> I am now running
>
> OpenBSD 6.9-current (GENERIC.MP) #17: Wed May 12 11:14:50 MDT 2021
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
>
> which contains your described fix. Since then I
On Thu, May 13, 2021 at 10:43:59AM +, Martin wrote:
> Hi list,
>
> 'sh /etc/netstart tun1' assign IPv4 address from '/etc/hostname.tun1' to
> 'tun0' interface which must be IPv6 only instead of 'tun1' as argument of
> netstart.
>
> # ifconfig tun0
> tun0: flags=8051< mtu 1500
>
On Tue, May 11, 2021 at 11:44:17AM +0200, Stefan Sperling wrote:
> Can you please run with this and let me know if it changes anything?
I have finally managed to reproduce the problem locally by playing around
with forced background scans and roaming. This patch is a superset of the
previ
On Fri, May 07, 2021 at 10:27:36PM +, Mikolaj Kucharski wrote:
> Yes, I see ieee80211_encap: data frame for node... messages in
> dmesg. Two dmesgs, from two PC Engines machines, in two different
> locations, 150+km apart, below.
>
> Uptime of 12 minutes as hostap from pce-0041:
> athn0:
On Fri, May 07, 2021 at 10:02:56PM +, Mikolaj Kucharski wrote:
> On Tue, Apr 27, 2021 at 11:32:49PM +0200, Stefan Sperling wrote:
> > On Tue, Apr 27, 2021 at 06:36:32PM +, Mikolaj Kucharski wrote:
> > > I got it again, but had official snapshot, so I don't have more inf
On Thu, May 06, 2021 at 11:28:34AM +0200, Matthias Schmidt wrote:
> >Synopsis:Fatal firmware error with iwm
> >Environment:
> System : OpenBSD 6.9
> Details : OpenBSD 6.9-current (GENERIC.MP) #4: Wed May 5 11:06:38
> MDT 2021
>
>
On Thu, May 06, 2021 at 01:17:48PM +, Martin wrote:
> After some testing the issue is quite more complicated than expected.
>
> 1. Using USB dongles as AP allow connections from any device with relatively
> 'old' WiFi modules installed (clients with Intel, Atheros). It works smoothly
> with
1 - 100 of 431 matches
Mail list logo
