Re: uaudio device works on usb2 port; fails on usb3 port

2020-08-06 Thread Marcus Glocker
On Wed, 5 Aug 2020 15:35:41 +0100 Jason McIntyre wrote: > hi. > > i have a usb hardware dac which shows up as uaudio. i've discovered > that it works when plugged into a usb2 port, but not usb3. i've > verified it fails to work on two different machines with usb3 ports. > all machines are runni

Re: uaudio device works on usb2 port; fails on usb3 port

2020-08-07 Thread Marcus Glocker
On Fri, 7 Aug 2020 12:31:39 +0200 Alexandre Ratchov wrote: > On Fri, Aug 07, 2020 at 10:08:25AM +0100, Patrick Harper wrote: > > I think asynchronous transfers don't work with xhci right now, > > which appears to be how your DAC works. If you can disable USB 3.0 > > in the BIOS/UEFI setup program

Re: uaudio device works on usb2 port; fails on usb3 port

2020-08-08 Thread Marcus Glocker
On Fri, 7 Aug 2020 18:08:23 +0100 Jason McIntyre wrote: > On Fri, Aug 07, 2020 at 01:08:17PM +0200, Marcus Glocker wrote: > > On Fri, 7 Aug 2020 12:31:39 +0200 > > Alexandre Ratchov wrote: > > > > > On Fri, Aug 07, 2020 at 10:08:25AM +0100, Patrick H

Re: uaudio device works on usb2 port; fails on usb3 port

2020-08-08 Thread Marcus Glocker
On Sat, 8 Aug 2020 12:21:45 +0200 Marcus Glocker wrote: > On Fri, 7 Aug 2020 18:08:23 +0100 > Jason McIntyre wrote: > > > On Fri, Aug 07, 2020 at 01:08:17PM +0200, Marcus Glocker wrote: > > > On Fri, 7 Aug 2020 12:31:39 +0200 > > > Alexandre Ratchov wrote:

Re: uaudio device works on usb2 port; fails on usb3 port

2020-08-12 Thread Marcus Glocker
jmc was so nice to send me his trouble device over to do some further investigations. Just some updates on what I've noticed today: - The issue isn't specific to xhci(4). I also see the same issue on some of my ehci(4) machines when attaching this device. - It seems like the device gets in to

Re: scanimage -L triggers panic, free: size too large 55 > 32

2020-08-17 Thread Marcus Glocker
Could you please also send an lsusb -v of the device? pkg_add usbutils lsusb lsusb -d : -v On Sun, Aug 16, 2020 at 07:26:12PM +, Mikolaj Kucharski wrote: > On Sun, Aug 16, 2020 at 06:41:18PM +, Mikolaj Kucharski wrote: > > >Synopsis: scanimage -L triggers panic, free: size too large 55

Re: uaudio device works on usb2 port; fails on usb3 port

2020-08-18 Thread Marcus Glocker
On Wed, 12 Aug 2020 21:39:15 +0200 Marcus Glocker wrote: > jmc was so nice to send me his trouble device over to do some further > investigations. Just some updates on what I've noticed today: > > - The issue isn't specific to xhci(4). I also see the same issue on

Re: uaudio device works on usb2 port; fails on usb3 port

2020-08-19 Thread Marcus Glocker
On Wed, 19 Aug 2020 12:02:23 +0200 Martin Pieuchot wrote: > On 18/08/20(Tue) 18:53, Marcus Glocker wrote: > > On Wed, 12 Aug 2020 21:39:15 +0200 > > Marcus Glocker wrote: > > > > > jmc was so nice to send me his trouble device over to do some > > > fur

Re: uaudio device works on usb2 port; fails on usb3 port

2020-08-19 Thread Marcus Glocker
On Wed, Aug 19, 2020 at 01:21:35PM +0200, Marcus Glocker wrote: > On Wed, 19 Aug 2020 12:02:23 +0200 > Martin Pieuchot wrote: > > > On 18/08/20(Tue) 18:53, Marcus Glocker wrote: > > > On Wed, 12 Aug 2020 21:39:15 +0200 > > > Marcus Glocker wrote: > > >

Re: uaudio device works on usb2 port; fails on usb3 port

2020-08-21 Thread Marcus Glocker
On Wed, 19 Aug 2020 20:31:05 +0200 Marcus Glocker wrote: > On Wed, Aug 19, 2020 at 01:21:35PM +0200, Marcus Glocker wrote: > > > On Wed, 19 Aug 2020 12:02:23 +0200 > > Martin Pieuchot wrote: > > > > > On 18/08/20(Tue) 18:53, Marcus Glocker wrote: > >

Re: scanimage -L triggers panic, free: size too large 55 > 32

2020-08-21 Thread Marcus Glocker
On Tue, 18 Aug 2020 15:46:03 + Mikolaj Kucharski wrote: > On Tue, Aug 18, 2020 at 06:41:13AM +0200, Marcus Glocker wrote: > > Could you please also send an lsusb -v of the device? > > Sure, no problem. Thanks. So 55 bytes for your configuration descriptor seems to be the

Re: scanimage -L triggers panic, free: size too large 55 > 32

2020-08-25 Thread Marcus Glocker
On Mon, 24 Aug 2020 16:46:22 + Mikolaj Kucharski wrote: > On Fri, Aug 21, 2020 at 01:21:28PM +0200, Marcus Glocker wrote: > > On Tue, 18 Aug 2020 15:46:03 + > > Mikolaj Kucharski wrote: > > > > > On Tue, Aug 18, 2020 at 06:41:13AM +0200, Marcus Gloc

Re: scanimage -L triggers panic, free: size too large 55 > 32

2020-08-26 Thread Marcus Glocker
On Tue, 25 Aug 2020 10:30:50 + Mikolaj Kucharski wrote: > On Tue, Aug 25, 2020 at 12:24:56PM +0200, Marcus Glocker wrote: > > On Mon, 24 Aug 2020 16:46:22 + > > Mikolaj Kucharski wrote: > > > > > > > > # scanimage -L > > > device `xer

Re: scanimage -L triggers panic, free: size too large 55 > 32

2020-08-26 Thread Marcus Glocker
On Wed, 26 Aug 2020 18:54:59 + Mikolaj Kucharski wrote: > On Wed, Aug 26, 2020 at 06:45:28PM +, Mikolaj Kucharski wrote: > > Marcus, > > > > On Wed, Aug 26, 2020 at 01:40:02PM +0200, Marcus Glocker wrote: > > > On Tue, 25 Aug 2020 10:30:50 +

Re: scanimage -L triggers panic, free: size too large 55 > 32

2020-08-26 Thread Marcus Glocker
On Wed, 26 Aug 2020 19:20:26 + Mikolaj Kucharski wrote: > On Wed, Aug 26, 2020 at 06:54:59PM +, Mikolaj Kucharski wrote: > > On Wed, Aug 26, 2020 at 06:45:28PM +, Mikolaj Kucharski wrote: > ... > > > > > > Do you have any theory why first control request is returning > > > wTotalLe

Re: scanimage -L triggers panic, free: size too large 55 > 32

2020-08-27 Thread Marcus Glocker
Hey Mikolaj, On Thu, Aug 27, 2020 at 06:49:12PM +, Mikolaj Kucharski wrote: > On Wed, Aug 26, 2020 at 11:27:21PM +0200, Marcus Glocker wrote: > > On Wed, 26 Aug 2020 19:20:26 + > > Mikolaj Kucharski wrote: > > > > > On Wed, Aug 26, 2020 at 06:54:59PM

Re: scanimage -L triggers panic, free: size too large 55 > 32

2020-08-28 Thread Marcus Glocker
with the last commit we did? Maybe we don't even need the additional diff to workaround that problem ... On Thu, 27 Aug 2020 21:27:30 +0200 Marcus Glocker wrote: > Hey Mikolaj, > > On Thu, Aug 27, 2020 at 06:49:12PM +, Mikolaj Kucharski wrote: > > > On Wed, Aug

Re: scanimage -L triggers panic, free: size too large 55 > 32

2020-08-30 Thread Marcus Glocker
On Sat, 29 Aug 2020 20:07:08 + Mikolaj Kucharski wrote: > Marcus, > > On Fri, Aug 28, 2020 at 10:06:17AM +0200, Marcus Glocker wrote: > > One other ask. > > > > Since we have fixed the free panic with the last commit now, I'm > > wondering whether to

Re: Unresponsive mouse on latest snapshot

2020-08-31 Thread Marcus Glocker
On Mon, 31 Aug 2020 19:47:15 +0200 Patrick Wildt wrote: > On Sat, Aug 29, 2020 at 08:12:37AM -0700, open...@evantann.com wrote: > > >Synopsis: Mouse is not functional in latest snapshot > > >Category: > > >Environment: > > System : OpenBSD 6.7 > > Details : OpenBSD 6.7-current

Re: panic with video(1)

2020-09-06 Thread Marcus Glocker
On Tue, 1 Sep 2020 05:27:56 -0300 Claudio Correa wrote: > Hi? > > I am not sure if there is any interest in the information, it may be a > specific fault in my machine. For your information, I am forwarding an > image of a "panic" when playing video -c. > > Only if there is any interest, I am w

Re: ping(8): a missing space in an error message

2020-09-21 Thread Marcus Glocker
On Mon, 21 Sep 2020 11:20:59 +0200 (CEST) pi...@durlej.net wrote: > --- sbin/ping/ping.c.orig Tue Feb 11 19:41:39 2020 > +++ sbin/ping/ping.c Mon Sep 21 09:11:28 2020 > @@ -351,7 +351,7 @@ main(int argc, char *argv[]) > errx(1, "interval is too small: %s", > opta

Re: panic: ehci_alloc_std: curlen == 0 on 6.8-beta

2020-10-23 Thread Marcus Glocker
Honestly, I haven't spent much time to investigate how the curlen = 0 is getting generated exactly, because for me it will be very difficult to understand that without the hardware on my side re-producing the same. But I had look when the code was introduced to handle curlen == 0 later in the func

Re: panic: ehci_alloc_std: curlen == 0 on 6.8-beta

2020-10-24 Thread Marcus Glocker
Now you have on M less in your tree checkout :-) Thanks for tracking this down. On Fri, Oct 23, 2020 at 06:50:53PM +0200, Marcus Glocker wrote: > Honestly, I haven't spent much time to investigate how the curlen = 0 is > getting generated exactly, because for me it will be very d

Re: MacBook Air brightness control defunct after upgrade to 6.8

2020-10-25 Thread Marcus Glocker
This has been fixed with a commit as of today: CVSROOT:/cvs Module name:src Changes by: mgloc...@cvs.openbsd.org2020/10/25 02:31:40 Modified files: sys/dev/acpi : abl.c Log message: Unbreak brightness setting on MacBooks introduced by abl(4). MacBooks already ha

Re: panic: ehci_alloc_std: curlen == 0 on 6.8-beta

2020-11-27 Thread Marcus Glocker
_chain: multiple QTDs, " > > > On Sun, Nov 22, 2020 at 01:36:10AM +, Mikolaj Kucharski wrote: > > Hi, > > > > Whould below diff be okay, or just simple: > > > > if (curlen > len) > > curlen = len; > > > > b

Re: panic: ehci_alloc_std: curlen == 0 on 6.8-beta

2020-11-27 Thread Marcus Glocker
On Fri, Nov 27, 2020 at 07:10:49PM +, Mikolaj Kucharski wrote: > On Fri, Nov 27, 2020 at 07:42:52PM +0100, Marcus Glocker wrote: > > On Fri, Nov 27, 2020 at 12:57:02PM +, Mikolaj Kucharski wrote: > > > > > I think something as simple as below would be okay. If r

Re: Multiple panics with ure(4)

2020-12-13 Thread Marcus Glocker
c0 (aux slot) > wsmouse0 at pms0 mux 0 > pcppi0 at isa0 port 0x61 > spkr0 at pcppi0 > aps0 at isa0 port 0x1600/31 > vmm0 at mainbus0: VMX (using slow L1TF mitigation) > ure0 at uhub1 port 2 configuration 1 interface 0 "CMI USB 10/100/1000 > LAN" rev 2.10/30.00 addr 2 ure0: RTL8153 (0x5c30), address > 70:88:6b:80:c1:3c rgephy0 at ure0 phy 0: RTL8251 PHY, rev. 0 > uhub3: device problem, disabling port 1 > vscsi0 at root > scsibus2 at vscsi0: 256 targets > softraid0 at root > scsibus3 at softraid0: 256 targets > softraid0: sd1 was not shutdown properly > sd1 at scsibus3 targ 1 lun 0: > sd1: 152624MB, 512 bytes/sector, 312575168 sectors > root on sd1a (7d38ab8be9ec1a0a.a) swap on sd1b dump on sd1b > WARNING: / was not properly unmounted > inteldrm0: 1280x800, 32bpp > wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation), using > wskbd0 wsdisplay0: screen 1-5 added (std, vt100 emulation) > -- [ Marcus Glocker, mar...@nazgul.ch, http://nazgul.ch ]

Re: Unable to use Canon MG3250 USB scanner more than once

2020-12-29 Thread Marcus Glocker
On Mon, 28 Dec 2020 20:55:33 + miko...@kucharski.name wrote: > >Synopsis:After first successful scan on Canon MG3250 > >scanner, all next ugenread()s timeout Category: kernel > >Environment: > System : OpenBSD 6.8 > Details : OpenBSD 6.8-current (GENERIC.MP) #24

Re: Unable to use Canon MG3250 USB scanner more than once

2020-12-30 Thread Marcus Glocker
On Wed, 30 Dec 2020 16:16:06 + Mikolaj Kucharski wrote: > On Tue, Dec 29, 2020 at 03:03:06PM +0100, Marcus Glocker wrote: > > On Mon, 28 Dec 2020 20:55:33 + > > miko...@kucharski.name wrote: > ... > > > >Fix: > > > Per email threads on tech@

Re: Unable to use Canon MG3250 USB scanner more than once

2021-01-01 Thread Marcus Glocker
On Wed, 30 Dec 2020 19:12:46 +0100 Marcus Glocker wrote: > On Wed, 30 Dec 2020 16:16:06 + > Mikolaj Kucharski wrote: > > > On Tue, Dec 29, 2020 at 03:03:06PM +0100, Marcus Glocker wrote: > > > On Mon, 28 Dec 2020 20:55:33 + > >

Re: Unable to use Canon MG3250 USB scanner more than once

2021-01-01 Thread Marcus Glocker
On Fri, 1 Jan 2021 20:13:02 + Mikolaj Kucharski wrote: > On Fri, Jan 01, 2021 at 06:56:21PM +0100, Marcus Glocker wrote: > > It looks like with xhci(4) for some reason the bulk endpoints are > > stalling after some operations, which isn't happening with ehci(4). > &

Re: Unable to use Canon MG3250 USB scanner more than once

2021-01-02 Thread Marcus Glocker
On Fri, Jan 01, 2021 at 07:15:53PM +, Natasha Kerensikova wrote: > Hello, > > I'm only catching up with the thread now, but thanks a lot for including > me, I am indeed interested in how this topic is evolve. > > FWIW, I have been running with a CURRENT and this patch since April, on > my ma

Re: Unable to use Canon MG3250 USB scanner more than once

2021-01-02 Thread Marcus Glocker
On Sat, Jan 02, 2021 at 10:02:47AM +, Mikolaj Kucharski wrote: > > Index: dev/usb/ugen.c > > === > > RCS file: /cvs/src/sys/dev/usb/ugen.c,v > > retrieving revision 1.109 > > diff -u -p -u -p -r1.109 ugen.c > > --- dev/usb/ugen.c

Re: Unable to use Canon MG3250 USB scanner more than once

2021-01-04 Thread Marcus Glocker
On Sat, 2 Jan 2021 11:11:18 + Natasha Kerensikova wrote: > Hello, > > on Saturday 02 January 2021 at 09:34, Marcus Glocker wrote: > > I was not following up the initial conversation on this thread, so I > > probably missed a lot of what was already discussed

Re: Unable to use Canon MG3250 USB scanner more than once

2021-01-05 Thread Marcus Glocker
On Mon, Jan 04, 2021 at 09:13:12AM +0100, Marcus Glocker wrote: > On Sat, 2 Jan 2021 11:11:18 + > Natasha Kerensikova wrote: > > > Hello, > > > > on Saturday 02 January 2021 at 09:34, Marcus Glocker wrote: > > > I was not following up the initi

Re: Unable to use Canon MG3250 USB scanner more than once

2021-01-09 Thread Marcus Glocker
On Sat, 9 Jan 2021 19:14:07 + Mikolaj Kucharski wrote: > Marcus, > > I'm just catching up here. I know you posted newer diff, but I would > like to comment what I've seen with your below diff. > > I'm running sane-backends with my SANE_CUSTOM_LIBUSB_TIMEOUT diff, as > shown in one of my ear

Re: Unable to use Canon MG3250 USB scanner more than once

2021-01-21 Thread Marcus Glocker
On Thu, 21 Jan 2021 15:51:58 + Mikolaj Kucharski wrote: > I've also tested scanning on: > > # scanimage -L > device `xerox_mfp:libusb:000:002' is a Samsung M2070 Series > multi-function peripheral > > with kernel diff: > > https://marc.info/?l=openbsd-bugs&m=160991986510827&w=2 > >

Re: Unable to use Canon MG3250 USB scanner more than once

2021-01-25 Thread Marcus Glocker
On Thu, Jan 21, 2021 at 05:02:02PM +0100, Marcus Glocker wrote: > On Thu, 21 Jan 2021 15:51:58 + > Mikolaj Kucharski wrote: > > > I've also tested scanning on: > > > > # scanimage -L > > device `xerox_mfp:libusb:000:002' is a Samsung M2070 Series

Re: 6.8-current ifconfig umb0 and Device not configured

2021-02-01 Thread Marcus Glocker
Can you also send a dmesg of the last working kernel please? On Mon, Feb 01, 2021 at 08:03:29PM +, miko...@kucharski.name wrote: > >Synopsis:umb(4) not working, ifconfig: SIOCGWG: Device not configured > >Category:kernel > >Environment: > System : OpenBSD 6.8 > Detail

Re: 6.8-current ifconfig umb0 and Device not configured

2021-02-01 Thread Marcus Glocker
Thanks. There were some changes going in that area recently. I think we need to try reverting some of them, and see which fixes it. Lets start with the most obvious one. Does this change anything? Index: dev/usb/usbdi.c === RCS fil

Re: 6.8-current ifconfig umb0 and Device not configured

2021-02-01 Thread Marcus Glocker
on 1 "Sierra Wireless, Incorporated Sierra > Wireless MC7455 Qualcomm\M-. Snapdragon? X7 LTE-A" rev 2.00/0.06 addr 3 > vscsi0 at root > scsibus2 at vscsi0: 256 targets > softraid0 at root > scsibus3 at softraid0: 256 targets > root on sd0a (f4c61a8acb9563fd.a) swap on sd0b

Re: 6.8-current ifconfig umb0 and Device not configured

2021-02-01 Thread Marcus Glocker
On Mon, Feb 01, 2021 at 10:16:37PM +, Mikolaj Kucharski wrote: > On Mon, Feb 01, 2021 at 10:57:43PM +0100, Marcus Glocker wrote: > > Ok. Then it was the usbd_device2interface_handle() change. > > Fixed one device (uaudio), broke the other device (umb) :-| > > Now le

Re: 6.8-current ifconfig umb0 and Device not configured

2021-02-02 Thread Marcus Glocker
On Tue, Feb 02, 2021 at 10:35:38AM +, Stuart Henderson wrote: > On 2021/02/02 10:02, Edd Barrett wrote: > > Hi, > > > > Apologies for breaking stuff. > > > > On Tue, Feb 02, 2021 at 07:24:34AM +0100, Marcus Glocker wrote: > > > Edd: > > > C

Re: 6.8-current ifconfig umb0 and Device not configured

2021-02-02 Thread Marcus Glocker
On Tue, Feb 02, 2021 at 10:01:32PM +, Mikolaj Kucharski wrote: > Hi Marcus, > > Below diff makes umb(4) work for me. All good now. Cool, thanks for testing Mikolaj. So OK if I commit this fix Edd, Stuart? Index: dev/usb/usbdi.c =

Re: 6.8-current ifconfig umb0 and Device not configured

2021-02-02 Thread Marcus Glocker
On Wed, Feb 03, 2021 at 05:11:41AM +, Mikolaj Kucharski wrote: > On Tue, Feb 02, 2021 at 10:02:57AM +, Edd Barrett wrote: > > Hi, > > > > Apologies for breaking stuff. > > No worries. > > > On Tue, Feb 02, 2021 at 07:24:34AM +0100, Marcus Glocker wr

Re: 6.8-current ifconfig umb0 and Device not configured

2021-02-03 Thread Marcus Glocker
On Wed, 3 Feb 2021 11:41:17 + Edd Barrett wrote: > On Wed, Feb 03, 2021 at 11:17:01AM +, Stuart Henderson wrote: > > btw the problem was seen with umb, it's not just ugen. > > From mglocker@'s explanation, I understood that it is the ugen driver > trying to attach to some part of the d

Re: 6.8-current ifconfig umb0 and Device not configured

2021-02-03 Thread Marcus Glocker
Hello Gerhard, On Wed, 3 Feb 2021 13:20:19 +0100 Gerhard Roth wrote: > On 2/3/21 12:51 PM, Marcus Glocker wrote: > > On Wed, 3 Feb 2021 11:41:17 + > > Edd Barrett wrote: > > > >> On Wed, Feb 03, 2021 at 11:17:01AM +, Stuart Henderson wrote: > >

Re: uhidev_clear_iface_eps: clear endpoints failed!

2021-02-08 Thread Marcus Glocker
On Mon, Feb 08, 2021 at 07:20:21AM +0100, Rafael Sadowski wrote: > Since a few days aka. snapshots I see the following error message after > boot: > > uhidev_clear_iface_eps: clear endpoints failed! > uhidev_clear_iface_eps: clear endpoints failed! > uhidev_clear_iface_eps: clear endpoints failed

Re: uhidev_clear_iface_eps: clear endpoints failed!

2021-02-08 Thread Marcus Glocker
On Mon, Feb 08, 2021 at 05:03:34PM +0100, Rafael Sadowski wrote: > On Mon Feb 08, 2021 at 12:32:54PM +0100, Marcus Glocker wrote: > > On Mon, Feb 08, 2021 at 07:20:21AM +0100, Rafael Sadowski wrote: > > > > > Since a few days aka. snapshots I see the following error

Re: uhidev_clear_iface_eps: clear endpoints failed!

2021-02-09 Thread Marcus Glocker
On Tue, Feb 09, 2021 at 08:28:05AM +0100, Marcus Glocker wrote: > On Mon, Feb 08, 2021 at 05:03:34PM +0100, Rafael Sadowski wrote: > > > On Mon Feb 08, 2021 at 12:32:54PM +0100, Marcus Glocker wrote: > > > On Mon, Feb 08, 2021 at 07:20:21AM +0100, Rafael Sadowski wrote: &

Re: uhidev_clear_iface_eps: clear endpoints failed!

2021-02-10 Thread Marcus Glocker
On Tue, Feb 09, 2021 at 10:00:24PM +0100, Rafael Sadowski wrote: > On Tue Feb 09, 2021 at 01:58:25PM +0100, Marcus Glocker wrote: > > On Tue, Feb 09, 2021 at 08:28:05AM +0100, Marcus Glocker wrote: > > > > > On Mon, Feb 08, 2021 at 05:03:34PM +0100, Rafael Sadowski wrot

Re: uhidev_clear_iface_eps: clear endpoints failed!

2021-02-11 Thread Marcus Glocker
On Thu, Feb 11, 2021 at 07:15:57AM +0100, Rafael Sadowski wrote: [...] > > Thank you. Can you please run the same while plugin the keyboard/mouse > > directly to the host? I would like to understand whether the issue is > > caused by the switch or naively by your device. > > > > Here it is: O

Re: uhidev_clear_iface_eps: clear endpoints failed!

2021-02-13 Thread Marcus Glocker
On Fri, Feb 12, 2021 at 05:59:07PM +0100, Rafael Sadowski wrote: > On Thu Feb 11, 2021 at 04:24:25PM +0100, Marcus Glocker wrote: > > On Thu, Feb 11, 2021 at 07:15:57AM +0100, Rafael Sadowski wrote: > > > > [...] > > > > Thank you. Can you please run the sam

Re: Latest snapshot, Logitech keyboard not working.

2021-02-13 Thread Marcus Glocker
On Sat, Feb 13, 2021 at 04:50:46PM +, martin.qu...@disroot.org wrote: > February 13, 2021 10:44 AM, "Anton Lindqvist" wrote: > > > Hi, > > > > On Sat, Feb 13, 2021 at 01:58:28PM +, martin.qu...@disroot.org wrote: > > > >> On amd64, upgrading from 6.8 stable to snapshot my Logitech G413

Re: Latest snapshot, Logitech keyboard not working.

2021-02-13 Thread Marcus Glocker
On Sat, Feb 13, 2021 at 09:35:31PM +, martin.qu...@disroot.org wrote: > February 13, 2021 12:34 PM, "Marcus Glocker" wrote: > > > On Sat, Feb 13, 2021 at 04:50:46PM +, martin.qu...@disroot.org wrote: > > > >> February 13, 2021 10:44 AM, &q

Re: Latest snapshot, Logitech keyboard not working.

2021-02-13 Thread Marcus Glocker
On Sun, Feb 14, 2021 at 01:16:12AM +, martin.qu...@disroot.org wrote: > February 13, 2021 5:05 PM, "Marcus Glocker" wrote: > > > On Sat, Feb 13, 2021 at 09:35:31PM +, martin.qu...@disroot.org wrote: > > > >> February 13, 2021 12:34 PM, "Marcus

Re: Latest snapshot, Logitech keyboard not working.

2021-02-14 Thread Marcus Glocker
On Sun, Feb 14, 2021 at 01:25:34PM +, martin.qu...@disroot.org wrote: > February 14, 2021 2:30 AM, "Marcus Glocker" wrote: > > > On Sun, Feb 14, 2021 at 01:16:12AM +, martin.qu...@disroot.org wrote: > > > >> February 13, 2021 5:05 PM, "Marcus

Re: Latest snapshot, Logitech keyboard not working.

2021-02-14 Thread Marcus Glocker
On Sun, Feb 14, 2021 at 01:53:19PM +, martin.qu...@disroot.org wrote: > February 14, 2021 8:35 AM, "Marcus Glocker" wrote: > > > On Sun, Feb 14, 2021 at 01:25:34PM +, martin.qu...@disroot.org wrote: > > > >> February 14, 2021 2:30 AM, "Marcus

Re: Latest snapshot, Logitech keyboard not working.

2021-02-15 Thread Marcus Glocker
On Sun, Feb 14, 2021 at 02:56:14PM +0100, Marcus Glocker wrote: [...] > > > For me that looks like the issue isn't directly related to uhidpp(4). > > > And yes, I also think the "uhidev_intr: bad repid 48" message is related > > > to the uh

Re: reboot on amdgpu init if usb mouse is plugged in

2021-02-17 Thread Marcus Glocker
On Wed, Feb 17, 2021 at 07:13:48PM +, Stefmorino wrote: > On Wednesday, February 17, 2021 12:32 PM, Marcus Glocker > wrote: > > > On Wed, Feb 17, 2021 at 02:23:00PM +, Stefmorino wrote: > > > > > > Synopsis: amdgpu fails to init if mouse is plugged in &

Re: SB drive not detected after reboot on PC Engines APU2

2021-02-20 Thread Marcus Glocker
On Fri, Feb 19, 2021 at 04:48:11PM +, marfabastewart wrote: > Synopsis: USB drive not detected after reboot on PC Engines APU2 > Category: amd64 > Environment: > System : OpenBSD 6.9 > Details : OpenBSD 6.9-beta (GENERIC.MP) #343: Thu Feb 18 23:09:55 > MST 2021 >

Re: SB drive not detected after reboot on PC Engines APU2

2021-02-23 Thread Marcus Glocker
On Sun, Feb 21, 2021 at 04:45:19PM +, marfabastewart wrote: [...] > and this is the output of sendbug -P on an APU2 > with the patch compiled in, after plugging in > the USB drive and rebooting. The USB drive is not > detected on the APU2 on boot, but the lines > from the patch are generated:

After 7.3 to 7.4 upgrade on an iMac11,2, the screen turns black

2023-10-18 Thread Marcus Glocker
>Synopsis: After 7.3 to 7.4 upgrade on an iMac11,2, the screen turns black >Category: dev/pci/drm >Environment: System : OpenBSD 7.4 Details : OpenBSD 7.4 (GENERIC.MP) #1397: Tue Oct 10 09:02:37 MDT 2023 dera...@amd64.openbsd.org:/usr/sr

Re: After 7.3 to 7.4 upgrade on an iMac11,2, the screen turns black

2023-10-18 Thread Marcus Glocker
When I revert this commit, the screen on my iMac11,2 works again: https://marc.info/?l=openbsd-cvs&m=167989100718759&w=2 Index: atombios_encoders.c === RCS file: /cvs/src/sys/dev/pci/drm/radeon/atombios_encoders.c,v retrieving revis

Re: After 7.3 to 7.4 upgrade on an iMac11,2, the screen turns black

2023-10-19 Thread Marcus Glocker
On Thu, Oct 19, 2023 at 11:00:42AM +1100, Jonathan Gray wrote: > On Wed, Oct 18, 2023 at 08:31:41PM +0200, Marcus Glocker wrote: > > When I revert this commit, the screen on my iMac11,2 works again: > > > > https://marc.info/?l=openbsd-cvs&m=167989100718759&w=2 >

Re: After 7.3 to 7.4 upgrade on an iMac11,2, the screen turns black

2023-10-24 Thread Marcus Glocker
On Tue, Oct 24, 2023 at 09:14:48PM +1100, Jonathan Gray wrote: > On Wed, Oct 18, 2023 at 08:31:41PM +0200, Marcus Glocker wrote: > > When I revert this commit, the screen on my iMac11,2 works again: > > > > https://marc.info/?l=openbsd-cvs&m=167989100718759&w=2 &

Re: TSO em(4) problem

2024-01-26 Thread Marcus Glocker
On Fri, Jan 26, 2024 at 11:41:49AM +0100, Hrvoje Popovski wrote: > I've manage to reproduce TSO em problem on anoter setup, unfortunatly > production. > > Setup is very simple > > em0 - carp <- uplink > em1 - pfsync > ix1 - vlans - carp Would it be possible that you also share an "ifconfig -a h

Re: TSO em(4) problem

2024-01-27 Thread Marcus Glocker
On Sat, Jan 27, 2024 at 08:01:09AM +0100, Hrvoje Popovski wrote: > On 26.1.2024. 21:56, Marcus Glocker wrote: > > On Fri, Jan 26, 2024 at 11:41:49AM +0100, Hrvoje Popovski wrote: > > > >> I've manage to reproduce TSO em problem on anoter setup, unfortunatly > &

Re: TSO em(4) problem

2024-01-28 Thread Marcus Glocker
On Sun, Jan 28, 2024 at 12:16:20AM +0100, Hrvoje Popovski wrote: > On 27.1.2024. 21:01, Marcus Glocker wrote: > > On Sat, Jan 27, 2024 at 08:01:09AM +0100, Hrvoje Popovski wrote: > > > >> On 26.1.2024. 21:56, Marcus Glocker wrote: > >>> On Fri, Jan 26, 2024

Re: TSO em(4) problem

2024-01-28 Thread Marcus Glocker
On Sun, Jan 28, 2024 at 02:11:37PM +0100, Mark Kettenis wrote: > > Date: Sun, 28 Jan 2024 10:44:25 +0100 > > From: Marcus Glocker > > > > On Sun, Jan 28, 2024 at 12:16:20AM +0100, Hrvoje Popovski wrote: > > > > > On 27.1.2024. 21:01, Marcus Glocker wrote

Re: TSO em(4) problem

2024-01-28 Thread Marcus Glocker
On Sun, Jan 28, 2024 at 02:01:29PM +0100, Hrvoje Popovski wrote: > Hi, > > > with this diff I still see TSOv4 and TSOv6 on i350 is this ok ? Nope, the intention was to disable TSO support for the i350 ... Anyway, the TSO support just has been backed out. Thanks again for all your testing!

Re: 7.2-current USB-related arm64 hang regression since approx #1818

2022-09-17 Thread Marcus Glocker
On Sat, Sep 17, 2022 at 11:22:41AM -0700, Stephan Somogyi wrote: > Starting with arm64 snapshot kernel 1818 and continuing to 1822, the latest > snapshot, I've been experiencing a persistent problem with the RPi3's USB > bus locking up in a way that requires physical access to power cycle, and > i

Re: 7.2-current USB-related arm64 hang regression since approx #1818

2022-09-18 Thread Marcus Glocker
On Sat, Sep 17, 2022 at 10:40:29PM +0200, Marcus Glocker wrote: > On Sat, Sep 17, 2022 at 11:22:41AM -0700, Stephan Somogyi wrote: > > > Starting with arm64 snapshot kernel 1818 and continuing to 1822, the latest > > snapshot, I've been experiencing a persistent prob

Re: 7.2-current USB-related arm64 hang regression since approx #1818

2022-09-18 Thread Marcus Glocker
On Sun, Sep 18, 2022 at 11:35:51AM -0700, Stephan Somogyi wrote: > I won't know for certain for a few more hours, but initially this looks to > have fixed it. Thank you. Cool, thanks for reporting and testing! The fix is committed now. > So far it seems that the fix has also caused a small per

Re: Raspberry Pi 3B+ panic on changing video0 permissions for motion

2021-03-08 Thread Marcus Glocker
On Mon, Mar 08, 2021 at 06:09:52PM +, Marfaba Stewart wrote: > Synopsis: Raspberry Pi 3B+ panic on changing video0 permissions for motion > Category: arm > Environment: > System : OpenBSD 6.9 > Details : OpenBSD 6.9-beta (GENERIC.MP) #1056: Sat Mar >

Re: Raspberry Pi 3B+ panic on changing video0 permissions for motion

2021-03-13 Thread Marcus Glocker
On Tue, Mar 09, 2021 at 04:22:09AM +, Marfaba Stewart wrote: > > On Monday, March 8, 2021 3:47 PM, Marcus Glocker wrote: > > > Does this patch make a difference? > > > > Index: sys/dev/usb/dwc2/dwc2.c > > > > very cool, it didn't take long at

Re: Raspberry Pi 3B+ panic on changing video0 permissions for motion

2021-03-13 Thread Marcus Glocker
On Sat, Mar 13, 2021 at 03:45:42PM +, Marfaba Stewart wrote: > On Saturday, March 13, 2021 9:22 AM, Marcus Glocker wrote: > > Hmm, I was trying to sync this function with the NetBSD code, but it > > looks like the gap between them is too large. Since I can't test this

Re: ure0: usb error on tx: IN_PROGRESS

2021-07-20 Thread Marcus Glocker
On Tue, 20 Jul 2021 11:03:53 -0300 (-03) adrian...@fortix.com.ar wrote: > >Synopsis:the ure driver (RTL8152) under certain conditions > >does not respond. Category: kernel > >Environment: > System : OpenBSD 6.9 > Details : OpenBSD 6.9-current (GENERIC.MP) #133: Sun Jul

Re: ure0: usb error on tx: IN_PROGRESS

2021-07-20 Thread Marcus Glocker
ss 00:e0:4c:38:2b:0f > rgephy0 at ure0 phy 0: RTL8251 PHY, rev. 0 > ure0: usb error on tx: IOERROR > ure0: usb error on tx: IN_PROGRESS > usb_insert_transfer: xfer=0xfd847bccd000 not free > ure0: usb error on tx: IOERROR > ure0: usb error on tx: IN_PROGRESS > usb_insert_t

Re: ure0: usb error on tx: IN_PROGRESS

2021-07-21 Thread Marcus Glocker
On Wed, 21 Jul 2021 08:40:34 +0200 Marcus Glocker wrote: > On Tue, 20 Jul 2021 22:21:11 +0100 > Stuart Henderson wrote: > > > On 2021/07/20 11:03, adrian...@fortix.com.ar wrote: > > > >Description: > > > The ure driver with the RTL8152 adapter does n

Re: ure0: usb error on tx: IN_PROGRESS

2021-07-21 Thread Marcus Glocker
On Wed, 21 Jul 2021 13:46:54 -0300 Adrian Ali wrote: > On Wed, 21 Jul 2021 08:40:34 +0200 > Marcus Glocker wrote: > > > Does this diff fix the issue? > > > > > > Index: if_ure.c > > === > &

Re: ure0: usb error on tx: IN_PROGRESS

2021-07-21 Thread Marcus Glocker
On Wed, 21 Jul 2021 19:23:18 -0300 Adrian Ali wrote: > > On Wed, 21 Jul 2021 13:46:54 -0300 > > Adrian Ali wrote: > > > > > On Wed, 21 Jul 2021 08:40:34 +0200 > > > Marcus Glocker wrote: > > > > > > > Does this di

Re: ure0: usb error on tx: IN_PROGRESS

2021-07-22 Thread Marcus Glocker
On Thu, 22 Jul 2021 07:55:18 +0200 Marcus Glocker wrote: > On Wed, 21 Jul 2021 19:23:18 -0300 > Adrian Ali wrote: > > > > On Wed, 21 Jul 2021 13:46:54 -0300 > > > Adrian Ali wrote: > > > > > > > On Wed, 21 Jul 2021 08:40:34 +0200 > >

Re: ure0: usb error on tx: IN_PROGRESS

2021-07-22 Thread Marcus Glocker
On Thu, 22 Jul 2021 11:25:00 -0300 Adrian Ali wrote: > > On Thu, 22 Jul 2021 07:55:18 +0200 > > Marcus Glocker wrote: > > > > > On Wed, 21 Jul 2021 19:23:18 -0300 > > > Adrian Ali wrote: > > > > > > > > On

Raspberry Pi 4 Model B

2021-07-22 Thread Marcus Glocker
I can install and boot an 6.9 on it (although XHCI fails to initialize), but with a miniroot69.img snapshot of today, I'm getting a panic with the RAMDISK kernel before the installation procedure starts. Is this something known? U-Boot 2021.04 (May 06 2021 - 13:23:28 -0600) DRAM: 7.9 GiB RPI 4

Re: Raspberry Pi 4 Model B

2021-07-22 Thread Marcus Glocker
On Thu, 22 Jul 2021 23:07:30 +0200 (CEST) Mark Kettenis wrote: > > Date: Thu, 22 Jul 2021 22:59:28 +0200 > > From: Marcus Glocker > > > > I can install and boot an 6.9 on it (although XHCI fails to > > initialize), but with a miniroot69.img snapshot of today, I&

Re: Raspberry Pi 4 Model B

2021-07-23 Thread Marcus Glocker
On Thu, 22 Jul 2021 23:44:54 +0200 Marcus Glocker wrote: > On Thu, 22 Jul 2021 23:07:30 +0200 (CEST) > Mark Kettenis wrote: > > > > Date: Thu, 22 Jul 2021 22:59:28 +0200 > > > From: Marcus Glocker > > > > > > I can install and boot an 6.9 on it (

Re: Raspberry Pi 4 Model B

2021-07-23 Thread Marcus Glocker
On Fri, 23 Jul 2021 23:17:47 +1000 Jonathan Gray wrote: > On Fri, Jul 23, 2021 at 02:32:33PM +0200, Mark Kettenis wrote: > > > Date: Fri, 23 Jul 2021 13:13:27 +0200 > > > From: Marcus Glocker > > > > > > On Thu, 22 Jul 2021 23:44:54 +0200 > > >

Re: kernel/6631: DDB during boot on Dell Dimension E521

2011-06-11 Thread Marcus Glocker
On Thu, Jun 09, 2011 at 09:26:04PM +0200, Mark Kettenis wrote: > Can you send me pcidump -vxx output for that machine? Same issue on my machine here with the same chipset as in the bug report. Your diff escapes the panic. Attached dmesg and pcidump. Cheers, Marcus -- [ Marcus Glocker,

Re: kernel/6631: DDB during boot on Dell Dimension E521

2011-06-11 Thread Marcus Glocker
The following reply was made to PR kernel/6631; it has been noted by GNATS. From: Marcus Glocker To: Mark Kettenis Cc: and...@afresh1.com, gn...@openbsd.org, b...@cvs.openbsd.org Subject: Re: kernel/6631: DDB during boot on Dell Dimension E521 Date: Sat, 11 Jun 2011 22:22:11 +0200 On Thu, Jun

Re: riscv64 kernel panic: cpu0: _dmamap_sync: ran off map!

2025-02-02 Thread Marcus Glocker
On Sat, Feb 01, 2025 at 05:01:58PM GMT, Mark Kettenis wrote: > > Date: Sat, 1 Feb 2025 14:56:53 + > > From: Lucas Gabriel Vuotto > > > > >Synopsis: kernel panic: cpu0: _dmamap_sync: ran off map! > > >Category: kernel riscv64 > > >Environment: > > System : OpenBSD 7.6 > > Detai

Re: uvm issue noticed on arm64

2025-01-09 Thread Marcus Glocker
On Thu, Jan 09, 2025 at 10:49:32PM GMT, Mark Kettenis wrote: > > Date: Thu, 9 Jan 2025 17:29:38 +0100 > > From: Marcus Glocker > > > > On Thu, Jan 09, 2025 at 05:05:14PM GMT, Mark Kettenis wrote: > > > > > > Date: Thu, 9 Jan 2025 1

uvm issue noticed on arm64

2025-01-09 Thread Marcus Glocker
Hello bugs@, Martin, Since a while I am noticing processes hanging on my Samsung Galaxy Book4 Edge (arm64/snapdragon-x/12-cores/16gb ram) machine. Those hangs appear very frequent, which makes it hard to work on the machine since things like xterm, ssh, man, etc. just suddenly start to hang. If

Re: uvm issue noticed on arm64

2025-01-09 Thread Marcus Glocker
On Thu, Jan 09, 2025 at 05:05:14PM GMT, Mark Kettenis wrote: > > Date: Thu, 9 Jan 2025 15:48:29 +0100 > > From: Marcus Glocker > > > > Hello bugs@, Martin, > > > > Since a while I am noticing processes hanging on my Samsung Galaxy Book4 > > Edge (arm

Re: MacPro6,1 (trash can) is crashing during shutdown

2025-05-05 Thread Marcus Glocker
On Mon, May 05, 2025 at 04:06:18PM -0700, Philip Guenther wrote: > On Mon, 5 May 2025, Marcus Glocker wrote: > > On Sun, May 04, 2025 at 05:57:56PM -0700, guent...@openbsd.org wrote: > > > On Sun, 4 May 2025, Marcus Glocker wrote: > > > > On Sun, May 04, 2025 at

Re: MacPro6,1 (trash can) is crashing during shutdown

2025-05-05 Thread Marcus Glocker
On Sun, May 04, 2025 at 05:57:56PM -0700, guent...@openbsd.org wrote: > On Sun, 4 May 2025, Marcus Glocker wrote: > > On Sun, May 04, 2025 at 09:36:48AM GMT, Marcus Glocker wrote: > > > > > On Sun, May 04, 2025 at 09:09:37AM GMT, Marcus Glocker wrote: > > > >

Re: MacPro6,1 (trash can) is crashing during shutdown

2025-05-02 Thread Marcus Glocker
Managed to get a stack trace meanwhile: https://nazgul.ch/pub/macpro6,1_st.jpg On Fri, May 02, 2025 at 06:29:10AM GMT, Marcus Glocker wrote: > >Synopsis:MacPro6,1 (trash can) is crashing during shutdown > >Category:kernel / acpi > >Environment: > Syst

Re: MacPro6,1 (trash can) is crashing during shutdown

2025-05-03 Thread Marcus Glocker
On Sat, May 03, 2025 at 09:53:11PM GMT, Marcus Glocker wrote: > On Sat, May 03, 2025 at 02:42:09PM GMT, George Koehler wrote: > > > On Sat, 3 May 2025 08:02:29 +0200 > > Marcus Glocker wrote: > > > > > Managed to get a stack trace meanwhile: > > > &g

Re: MacPro6,1 (trash can) is crashing during shutdown

2025-05-03 Thread Marcus Glocker
On Sat, May 03, 2025 at 02:42:09PM GMT, George Koehler wrote: > On Sat, 3 May 2025 08:02:29 +0200 > Marcus Glocker wrote: > > > Managed to get a stack trace meanwhile: > > > > https://nazgul.ch/pub/macpro6,1_st.jpg > > This is your stack trace, beware of

Re: MacPro6,1 (trash can) is crashing during shutdown

2025-05-03 Thread Marcus Glocker
On Sat, May 03, 2025 at 10:08:15PM GMT, Marcus Glocker wrote: > On Sat, May 03, 2025 at 09:53:11PM GMT, Marcus Glocker wrote: > > > On Sat, May 03, 2025 at 02:42:09PM GMT, George Koehler wrote: > > > > > On Sat, 3 May 2025 08:02:29 +0200 > > > Marcus Glock

  1   2   >