Re: panic: config_detach: forced detach of iwm0 failed (45)

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 : OpenBSD 6.9 > Details : OpenBS

panic: config_detach: forced detach of iwm0 failed (45)

>Synopsis: The system randomly panics with the message: panic: >config_detach: forced detach of iwm0 failed (45) >Category: system >Environment: System : OpenBSD 6.9 Details : OpenBSD 6.9-current (GENERIC.MP) #69: Fri Jun 11 08:31:52 MDT 2021

System hang + massive memory usage when copying files to a vnd(4)

[ CCing beck@ and tedu@ as a courtesy, because the commit that resulted in the following behavior was checked-in/OKed by them. Also CCing mlarkin@ and Paul de Weerd because the bug report "vmd eating lots of memory" on misc@ may potentially be related: https://marc.info/?t=15636328131=1=2 ]

Re: iwm: unhandled firmware response

On 2019-04-27 15:56:33, Stefan Sperling wrote: > On Sat, Apr 27, 2019 at 12:04:51PM +0200, Krystian Lewandowski wrote: > > I observed similar issues: > > > > iwm0: hw rev 0x230, fw ver 22.361476.0, address e4:0e:ee:81:3d:a0 > > iwm0: unhandled firmware response 0x58/0xc10f rx ring 0[0] > > iwm0:

Re: Plugging in ADB-enabled Android device makes kernel panic with xhci

[CCing visa@ in] On 2018-08-25 21:40:57, Tom Murphy wrote: > On Thu, Aug 23, 2018 at 08:45:54PM +0900, Tom Murphy wrote: > > I've narrowed it down. > > > >Last kernel where adb works: June 24 09:59:46 MDT 2018 > >1st Kernel where adb panics: June 25 13:10:32 MDT 2018 > > > > [...] > > > >

Re: Plugging in ADB-enabled Android device makes kernel panic with xhci

On 2018-08-21 17:00:50, Bryan Linton wrote: > On 2018-08-18 23:02:24, Tom Murphy wrote: > > >Synopsis: Kernel panic in xhci.c when Android phone with ADB > > > > [...] > > > > >How-To-Repeat: > > I can reproduce this every time just by

Re: Plugging in ADB-enabled Android device makes kernel panic with xhci

On 2018-08-18 23:02:24, Tom Murphy wrote: > >Synopsis:Kernel panic in xhci.c when Android phone with ADB > > [...] > > >How-To-Repeat: > I can reproduce this every time just by enabling ADB on the > phone and connecting it to the OpenBSD machine. > I've been seeing the same panics for

Re: em0 losing connectivity, disappearing from systat, mbuf related?

m all back together again. I apologize if I caused any developers to waste their time chasing a bug that I myself caused by tweaking a knob too far into the red. My apologies. -- Bryan On 2017-09-14 19:32:15, Bryan Linton <b...@shoshoni.info> wrote: > FWIW, I get the same behavior

Re: Vertical lines present on fonts (FreeType update related)

I finally had some time to bisect this diff and found that reverting the following line of code to the one that was present in FreeType 2.8.0 fixes the error for me. Is there any way this can go in? This bug significantly affects the legibility of Asian fonts, and while the diff is a one-liner,

Re: Vertical lines present on fonts (FreeType update related)

On 2018-02-17 08:29:15, Bryan Linton <b...@shoshoni.info> wrote: > CCing dcoppa@ > > Ping? > FWIW, I'm still seeing this bug on the following snapshot: OpenBSD 6.2-current (GENERIC.MP) #10: Wed Feb 21 21:26:27 MST 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/

Re: Vertical lines present on fonts (FreeType update related)

CCing dcoppa@ Ping? Can anyone else reproduce the vertical lines I'm seeing with the new FreeType update, or can I assume that there's something weird going on with just my machine that doesn't affect others? -- Bryan On 2018-02-11 22:05:54, Bryan Linton <b...@shoshoni.info>

Vertical lines present on fonts (FreeType update related)

>Synopsis: Asian fonts are rendering with vertical bars after recent >FreeType update >Category: system >Environment: System : OpenBSD 6.2 Details : OpenBSD 6.2-current (GENERIC.MP) #408: Thu Feb 8 04:09:33 MST 2018

Re: em0 losing connectivity, disappearing from systat, mbuf related?

FWIW, I get the same behavior on GENERIC.MP, so I don't think the PPPOE_TERM_UNKNOWN_SESSIONS kernel option is causing this. If I can provide any more information, please let me know. -- Bryan On 2017-09-03 05:59:51, Bryan Linton <b...@shoshoni.info> wrote: > >Synopsis:

Some buttons on USB mouse not working correctly.

>Synopsis: USB mouse generates incorrect keycodes for some button presses. >Category: system >Environment: System : OpenBSD 6.1 Details : OpenBSD 6.1-current (GENERIC.MP-PPPOE_TERM_UNKNOWN_SESSIONS) #17: Thu Jul 20 20:49:09 JST 2017

Re: two audio beep bugs

On 2016-05-13 00:56:52, Ted Unangst wrote: > 1. I have wsconsctl keyboard.bell.volume=0 because I don't like things beeping > at me. This recently stopped working in xterm, where I now get a loud beep. > Related to loss of pcvt? > > I'm not sure where the failure is, but my

panic: "__mp_lock_held(_lock) == 0" failed

>Synopsis: Kernel panics with '"__mp_lock_held(_lock) == 0" failed' >message >Category: system >Environment: System : OpenBSD 5.9 Details : OpenBSD 5.9-beta (GENERIC.MP-PPPOE_TERM_UNKNOWN_SESSIONS) #1: Sat Jan 9 15:34:21 JST 2016

Re: kernel panic - sparc64 on Netra X1 - psycho0: uncorrectable DMA error AFAR

On 2015-12-08 12:22:56, Steven Chamberlain wrote: > > A question for Fred perhaps -- does the Netra T1 105 also use dc(4) > ethernet? Do you know if it's affected by this bug? > I have a Netra T1 105 that's currently in storage awaiting a move to a place where I can use it

Re: em0 interface on Lenovo T60 hangs starting as of OpenBSD 5.7

On 2015-05-09 17:10:56, Brad Smith b...@comstyle.com wrote: On Sun, May 03, 2015 at 12:16:21PM +0200, Mark Kettenis wrote: Date: Sun, 3 May 2015 02:38:12 -0700 From: Bryan Linton b...@shoshoni.info The key difference is the following two lines. The first wedged, the second

Re: em0 interface on Lenovo T60 hangs starting as of OpenBSD 5.7

kern.netlivelocks'. You mention updating packages, I've definitely had systems which have been pretty much flattened with netlivelocks/mitigation while doing this, perhaps some em(4) don't react very well to this...? On 3 May 2015 01:13:19 BST, Bryan Linton b...@shoshoni.info wrote: On 2015-05-02 00

Reproducible USB panic in new snap

Synopsis: Reproducible USB panic in new snap Category: kernel Environment: System : OpenBSD 5.6 Details : OpenBSD 5.6-current (GENERIC) #2: Sun Aug 31 05:02:01 PDT 2014

Re: Regression in cwm grouping after recent commit

On 2014-03-21 10:06:24, Okan Demirmen o...@demirmen.com wrote: On Thu, Mar 20, 2014 at 9:11 PM, b...@shoshoni.info wrote: Synopsis: regression in cwm grouping after recent commit Category: system Environment: System : OpenBSD 5.5 Details : OpenBSD

Re: Mouse forward/back buttons no longer work in new snap, Xorg related

On 2012-02-19 17:23:18, Matthieu Herrb matthieu.he...@laas.fr wrote: On Sat, Feb 18, 2012 at 06:21:12PM -0800, Bryan Linton wrote: Synopsis: Mouse forward/back buttons no longer work in new snap Category: system Environment: System : OpenBSD 5.1 Details : OpenBSD 5.1

Re: kernel/6632: Reproduceable hard crash in new snap, Xorg/radeon related

The following reply was made to PR kernel/6632; it has been noted by GNATS. From: Bryan Linton b...@shoshoni.info To: Owain Ainsworth zer...@googlemail.com Cc: gn...@openbsd.org Subject: Re: kernel/6632: Reproduceable hard crash in new snap, Xorg/radeon related Date: Sun, 19 Jun 2011 09:21:11