Re: USB drive no longer works in 6.7+

2020-10-06 Thread Andrew Daugherity
On Wed, Sep 30, 2020 at 4:27 PM Kenneth R Westerback wrote: > If you can try a 6.8 snapshot it would be helpful. > > If 6.8 still fails, then the output from a 6.8 kernel compiled with > > option SCSIDEBUG > > will be useful. And if you can boot the same machine with a 6.6 kernel > containing the

USB drive no longer works in 6.7+

2020-09-30 Thread Andrew Daugherity
I have a USB thumb drive in my stash which I often use for installer images, etc. It worked fine in OpenBSD 6.6 and older, identifying like this: umass0 at uhub0 port 9 configuration 1 interface 0 "Generic Mass Storage" rev 2.00/1.07 addr 4 umass0: using SCSI over Bulk-Only scsibus6 at umass0: 2 t

Re: USB mouse not working in 6.5 - "uhidev1: no report descriptor"

2019-07-31 Thread Andrew Daugherity
It turns out this is not as consistently reproducible as I thought. The issue happened for at least three consecutive reboots (including one complete power-off) before I sent this bug, but when I later went to test if unplugging/reconnecting the USB device after boot made any difference, I discover

USB mouse not working in 6.5 - "uhidev1: no report descriptor"

2019-05-02 Thread andrew . daugherity
>Synopsis: KVM switch USB mouse not working after 6.5 upgrade - "uhidev1: >no report descriptor" >Category: kernel >Environment: System : OpenBSD 6.5 Details : OpenBSD 6.5 (GENERIC.MP) #3: Sat Apr 13 14:48:43 MDT 2019 dera...@amd64.openb

Re: sasyncd.conf parser bug - "no shared key specified"

2019-03-21 Thread Andrew Daugherity
On Thu, Mar 21, 2019 at 8:05 AM Otto Moerbeek wrote: > > > > There's a diff on tech@ fixing this (and a few other things). > > > > -Otto > > In the meantime a fix has been committed that wil be included in the > upcoming 6.5 release. > > -Otto Thanks, I've verified that both version

sasyncd.conf parser bug - "no shared key specified"

2019-03-19 Thread Andrew Daugherity
>Synopsis: sasyncd.conf parse error - "no shared key specified" >Category: user >Environment: System : OpenBSD 6.4 Details : OpenBSD 6.4 (GENERIC.MP) #7: Thu Feb 28 18:56:25 CET 2019 r...@syspatch-64-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP

Re: slowcgi -u user option does not change socket ownership

2018-08-10 Thread Andrew Daugherity
I think the -U/-u options are a good solution; hopefully that will be merged? I noticed a small inconsistency in the logging: slowcgi_user is logged at warn (which I think is too loud), whereas the chroot and socket paths are at debug, and the new sock_user setting isn't logged at all. I've attach

Re: slowcgi -u user option does not change socket ownership

2018-08-06 Thread Andrew Daugherity
On Fri, Aug 3, 2018 at 2:34 AM Florian Obser wrote: > > On Thu, Aug 02, 2018 at 04:22:35PM -0500, Andrew Daugherity wrote: > > I'm also playing around with a version that accepts "-U user:group" (a > > la chown), which I think would be preferable to a separate gr

Re: slowcgi -u user option does not change socket ownership

2018-08-02 Thread Andrew Daugherity
On Wed, Aug 1, 2018 at 6:09 AM Florian Obser wrote: > > Nice to see it being useful on other systems, too. :) > > Does this work for you? > [diff snipped] Yes, that works great! Although I think you want to capitalize "Change" in the man page. I'm also playing around with a version that accepts

Re: slowcgi -u user option does not change socket ownership

2018-07-31 Thread Andrew Daugherity
On Sun, Jul 29, 2018 at 11:07 AM, Florian Obser wrote: > It is behaving as intended. The slowcgi.sock is for the webserver to > interact with. The specified user is not supposed to interact with the > socket. CGI scripts are executed as this user. > > slowcgi itself can use the socket just fine si

slowcgi -u user option does not change socket ownership

2018-07-26 Thread andrew . daugherity
>Synopsis: slowcgi -u user option does not change socket ownership >Category: user >Environment: System : OpenBSD 6.3 Details : OpenBSD 6.3 (GENERIC.MP) #4: Sun Jun 17 11:22:20 CEST 2018 r...@syspatch-63-amd64.openbsd.org:/usr/src/sys/arc

Re: panic probing wdc0 at isa0

2017-09-25 Thread Andrew Daugherity
On Fri, Sep 22, 2017 at 4:32 PM, Mike Belopuhov wrote: > Please try the attached diff. > > Yup, that fixed it. Thanks!

panic probing wdc0 at isa0

2017-09-22 Thread Andrew Daugherity
>Synopsis: panic on boot during probe of wdc0 at isa0 >Category: kernel >Environment: System : OpenBSD 6.2 Details : OpenBSD 6.2-beta (GENERIC) #132: Fri Sep 15 22:31:00 MDT 2017 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC Architec

Dell PowerEdge R230 hangs on boot after xhci

2016-02-09 Thread Andrew Daugherity
With both 5.8 and a recent snapshot, the machine hangs after enumerating xhci: xhci0 at pci0 dev 20 function 0 "Intel 100 Series xHCI" rev 0x31: msi usb0 at xhci0: USB revision 3.0 uhub0 at usb0 "Intel xHCI root hub" rev 3.00/1.00 addr 1 [ no further output ] If I disable xhci via UKC, the boot i