ifconfig iwx0 debug, reconnect:
Feb 16 03:00:17 matebook /bsd: iwx0: using firmware iwx-QuZ-a0-hr-b0-77
Feb 16 03:00:17 matebook /bsd: iwx0: begin active scan
Feb 16 03:00:17 matebook /bsd: iwx0: INIT -> SCAN
Feb 16 03:00:21 matebook /bsd: iwx0: end active scan
Feb 16 03:00:21
>Synopsis: iwx obtains IP via DHCP but no traffic
>Category: network, drivers
>Environment:
System : OpenBSD 7.4
Details : OpenBSD 7.4-current (GENERIC.MP) #1688: Thu Feb 15
10:48:34 MST 2024
On Feb 15, 2024, at 3:01 PM, Miod Vallat wrote:
>
>> Has been running for the last few hours without any issue.
>> OK claudio@ on that diff.
>
> But it's your diff! I only polished it a bit.
>
I have also been testing various versions of my test
program for a few hours as well. It has not
> Has been running for the last few hours without any issue.
> OK claudio@ on that diff.
But it's your diff! I only polished it a bit.
On Thu, Feb 15, 2024 at 04:38:07PM +0100, Claudio Jeker wrote:
> On Thu, Feb 15, 2024 at 03:30:39PM +, Miod Vallat wrote:
> > > > A lot of this points towards a register window error in__tfork() which
> > > > affects only the parent process.
> > >
> > > I think the issue is that cpu_fork()
On Thu, Feb 15, 2024 at 03:30:39PM +, Miod Vallat wrote:
> > > A lot of this points towards a register window error in__tfork() which
> > > affects only the parent process.
> >
> > I think the issue is that cpu_fork() copies the u_pcb from parent to child
> > and with that the special user
> > A lot of this points towards a register window error in__tfork() which
> > affects only the parent process.
>
> I think the issue is that cpu_fork() copies the u_pcb from parent to child
> and with that the special user register windows that got spilled because
> of some TL>0 fault. Since
On Tue, Nov 07, 2023 at 12:09:36PM +0100, Claudio Jeker wrote:
> On Tue, Oct 31, 2023 at 01:18:42PM +0100, Claudio Jeker wrote:
> > On Mon, Oct 23, 2023 at 11:06:53PM +, Kurt Miller wrote:
> > > I experimented with adding a nanosleep after pthread_create() to
> > > see if that would resolve
On 2024/02/13 08:44, Miod Vallat wrote:
> > Does this help?
> >
> > diff --git sys/dev/wscons/wskbd.c sys/dev/wscons/wskbd.c
> > index 7631cd5f701..dd65f61ce63 100644
> > --- sys/dev/wscons/wskbd.c
> > +++ sys/dev/wscons/wskbd.c
> > @@ -1229,7 +1229,10 @@ getkeyrepeat:
> >
> > case
On Tue, Feb 13, 2024 at 08:44:32AM +, Miod Vallat wrote:
>> Does this help?
>>
>> diff --git sys/dev/wscons/wskbd.c sys/dev/wscons/wskbd.c
>> index 7631cd5f701..dd65f61ce63 100644
>> --- sys/dev/wscons/wskbd.c
>> +++ sys/dev/wscons/wskbd.c
>> @@ -1229,7 +1229,10 @@ getkeyrepeat:
>>
>>
Hello
I have installed the OpenBSD 7.4, I have not used this operating system
before all things work perfectly but when use GUI for example xfce the
system hang and nothing can be done except to power off the system by Press
the power button for a few seconds
I try and found by disabling inteldrm
On Wed, Feb 14, 2024 at 12:34:17PM +0100, Mark Kettenis wrote:
Hello Mark,
>> It seems that I have two (at least) lm devices on my motherboard and
>> that it's random which attaches. Here are the two I've seen:
>>
>> lm0 at isa0 port 0x290/8: W83627DHG
>> lm0 at isa0 port 0x290/8: NCT6792D
12 matches
Mail list logo