> Date: Tue, 8 Feb 2022 14:21:52 +0100
> From: Stefan Sperling
>
> On Tue, Jan 25, 2022 at 11:22:45AM +0100, Mark Kettenis wrote:
> > > The KASSERT triggers but for the wrong reason: We don't have outstanding
> > > tasks, we have a bad reference counter. Only setting the ref counter to 1
> > > i
On Tue, Jan 25, 2022 at 11:22:45AM +0100, Mark Kettenis wrote:
> > The KASSERT triggers but for the wrong reason: We don't have outstanding
> > tasks, we have a bad reference counter. Only setting the ref counter to 1 if
> > we are about to launch a task during resume should fix it, and this matche
> Date: Tue, 25 Jan 2022 10:00:45 +0100
> From: Stefan Sperling
>
> On Tue, Jan 25, 2022 at 09:32:21AM +0100, Mark Kettenis wrote:
> > Happened again while still on a Jan 16 snapshot kernel. So it is not
> > related to that diff.
> >
> > Here is the panic message and backtrace:
> >
> > panic:
On Tue, Jan 25, 2022 at 09:32:21AM +0100, Mark Kettenis wrote:
> Happened again while still on a Jan 16 snapshot kernel. So it is not
> related to that diff.
>
> Here is the panic message and backtrace:
>
> panic: kernel diagnostic assertion "sc->task_refs.refs == 0" failed: file
> "/usr/src/sy
> Date: Fri, 21 Jan 2022 16:18:28 +0100 (CET)
> From: Mark Kettenis
>
> > Date: Fri, 21 Jan 2022 16:05:49 +0100
> > From: Stefan Sperling
> >
> > On Sun, Jan 16, 2022 at 07:38:11PM +0100, Mark Kettenis wrote:
> > > > Date: Sun, 16 Jan 2022 19:28:06 +0100
> > > > From: Stefan Sperling
> > > >
On Thu, Jan 13 2022, Stefan Sperling wrote:
> At present active scans (which send probe requests, as opposed to
> just listening for beacons) are disabled on iwm 9k and iwx. This
> was done because firmware misbehaved after association.
>
> zxystd from the OpenIntelWireless project has debugged th
> Date: Fri, 21 Jan 2022 16:05:49 +0100
> From: Stefan Sperling
>
> On Sun, Jan 16, 2022 at 07:38:11PM +0100, Mark Kettenis wrote:
> > > Date: Sun, 16 Jan 2022 19:28:06 +0100
> > > From: Stefan Sperling
> > >
> > > On Sun, Jan 16, 2022 at 03:50:55PM +0100, Mark Kettenis wrote:
> > > > However,
On Sun, Jan 16, 2022 at 07:38:11PM +0100, Mark Kettenis wrote:
> > Date: Sun, 16 Jan 2022 19:28:06 +0100
> > From: Stefan Sperling
> >
> > On Sun, Jan 16, 2022 at 03:50:55PM +0100, Mark Kettenis wrote:
> > > However, running this diff I had a problem after resuming my laptop
> > > twice. After re
> Date: Sun, 16 Jan 2022 19:28:06 +0100
> From: Stefan Sperling
>
> On Sun, Jan 16, 2022 at 03:50:55PM +0100, Mark Kettenis wrote:
> > However, running this diff I had a problem after resuming my laptop
> > twice. After resume the interface didn't work and I found the
> > following in dmesg:
> >
On Sun, Jan 16, 2022 at 03:50:55PM +0100, Mark Kettenis wrote:
> However, running this diff I had a problem after resuming my laptop
> twice. After resume the interface didn't work and I found the
> following in dmesg:
>
> iwm0: could not initialize hardware
>
> I tried to reset the interface by
> Date: Thu, 13 Jan 2022 17:45:03 +0100
> From: Stefan Sperling
>
> At present active scans (which send probe requests, as opposed to
> just listening for beacons) are disabled on iwm 9k and iwx. This
> was done because firmware misbehaved after association.
>
> zxystd from the OpenIntelWireless
At present active scans (which send probe requests, as opposed to
just listening for beacons) are disabled on iwm 9k and iwx. This
was done because firmware misbehaved after association.
zxystd from the OpenIntelWireless project has debugged the issue
and has sent me a patch against OpenBSD which
12 matches
Mail list logo
