Re: Acer Aspire A315 laptop firmware fails to load with 6.7
On Wed, 19 Aug 2020 02:20:01 +1000 Jonathan Gray wrote: > On Tue, Aug 18, 2020 at 12:09:56PM -0400, Jon Fineman wrote: > > On Wed, 19 Aug 2020 00:06:59 +1000 > > Jonathan Gray wrote: > > > > > On Sun, Aug 16, 2020 at 02:27:46AM +, Jon Fineman wrote: > > > > I was not able to do a proper sendbug report because the PC > > > > hangs. > > > > > > > > I have an Acer Aspire A315 laptop. 6.6 works fine. When I > > > > upgrade to 6.7 Release or Snapshot I get the below firmware > > > > load error. Below that output is the dmesg from a 6.6 boot so > > > > you can see the hardware. > > > > > > The first boot after a new install will not have the firmware. > > > fw_update(1) will run and install it into /etc/firmware/amdgpu/ > > > > > > Does amdgpu still not attach after you've verified the files are > > > present and rebooted? > > > > > > I mounted the memory stick and verified the amd firmware files are > > present in /etc/firmware/amdgpu. I also downloaded the ones from 6.7 > > and copied them to that directory. > > > > When I booted it wanted to update the firmware for amdgpu and vmm. > > > > Then it dies while re-ording the kernel. > > > > I am not sure how I would tell if the amdgpu attached or not. > > > > /var/log/message from this test: > > > > Aug 18 11:54:56 laptop /bsd: softraid0 at root > > Aug 18 11:54:56 laptop /bsd: scsibus4 at softraid0: 256 targets > > Aug 18 11:54:56 laptop /bsd: root on sd1a (c5239493226aa09b.a) swap > > on sd1b dump on sd1b Aug 18 11:54:56 laptop /bsd: initializing > > kernel modesetting (STONEY 0x1002:0x98E4 0x1025:0x1192 0xDA). Aug > > 18 11:54:56 laptop /bsd: amdgpu_irq_add_domain: stub Aug 18 > > 11:54:56 laptop /bsd: amdgpu0: 1366x768, 32bpp Aug 18 11:54:56 > > laptop /bsd: wsdisplay0 at amdgpu0 mux 1: console (std, vt100 > > emulation), using wskbd0 Aug 18 11:54:56 laptop /bsd: wsdisplay0: > > screen 1-5 added (std, vt100 emulation) > > It has attached here. If there is fatal error such as missing > firmware it will detach and efifb or vga will reclaim the console. After comparing the logs from my first and second test I notice the below line from amdgpu_attachhook *ERROR*. Does that imply that the attach failed? > Aug 14 09:58:42 laptop /bsd: drm:pid0:gfx_v8_0_init_microcode *ERROR* > gfx8: Failed to load firmware "amdgpu/stoney_pfp.bin" Aug 14 09:58:42 > laptop /bsd: [drm] *ERROR* Failed to load gfx firmware! Aug 14 > 09:58:42 laptop /bsd: [drm] *ERROR* sw_init of IP block > failed -2 Aug 14 09:58:42 laptop /bsd: drm:pid0:amdgpu_device_init > *ERROR* amdgpu_device_ip_init failed Aug 14 09:58:42 laptop /bsd: > drm:pid0:amdgpu_attachhook *ERROR* Fatal error during GPU init Aug 14 > 09:58:42 laptop /bsd: efifb0 at mainbus0: 1366x768, 32bpp Aug 14 > 09:58:42 laptop /bsd: wsdisplay0 at efifb0 mux 1: console (std, vt100 > emulation), using wskbd0 Aug 14 09:58:42 laptop /bsd: wsdisplay0: > screen 1-5 added (std, vt100 emulation)
Re: uaudio device works on usb2 port; fails on usb3 port
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
> some of my ehci(4) machines when attaching this device.
>
> - It seems like the device gets in to an 'corrupted state' after
> running a couple of control transfer against it. Initially they
> work fine, with smaller and larger transfer sizes, and at one point
> the device hangs up and doesn't recover until re-attaching it.
> While on some ehci(4) machines the uhidev(4) attach works fine, after
> running lsusb against the device, I see transfer errors coming up
> again; On xhci(4) namely XHCI_CODE_TXERR.
>
> - Attaching an USB 2.0 hub doesn't make any difference, no matter if
> attached to an xhci(4) or an ehci(4) controller.
>
> Not sure what is going wrong with this little beast ...
OK, I give up :-) Following my summary report.
This device seems to have issues with two control request types:
- UR_GET_STATUS, not called for this device from the kernel in the
default code path. But e.g. 'lsusb -v' will call it.
- UR_SET_IDLE, as called in uhidev_attach().
UR_GET_STATUS will stall the device for good on *all* controller
drivers.
UR_SET_IDLE works only on ehci(4) - Don't ask me why.
On all the other controller drivers the following UR_GET_REPORT request
will fail, stalling the device as well. I tried all kind of things to
get the UR_SET_IDLE request working on xhci(4), but without any luck.
The good news is that when we skip the UR_SET_IDLE request on xhci(4),
the following UR_GET_REPORT request works, and isoc transfers also work
perfectly fine. You can use the device for audio streaming.
Therefore the only thing I can offer is a quirk to skip the
UR_SET_IDLE request when attaching this device. On ehci(4) the
device continues to work as before with this quirk. Therefore I
didn't include any code to only apply the quirk on non-ehci
controllers.
I know it's not a nice solution, but at least it makes this device
usable on xhci(4) while not impacting other things.
If anyone is OK with that and has no better idea how to fix it, I'm
happy to commit.
Cheers,
Marcus
Index: uhidev.c
===
RCS file: /cvs/src/sys/dev/usb/uhidev.c,v
retrieving revision 1.80
diff -u -p -u -p -r1.80 uhidev.c
--- uhidev.c31 Jul 2020 10:49:33 - 1.80
+++ uhidev.c18 Aug 2020 13:36:13 -
@@ -151,7 +151,8 @@ uhidev_attach(struct device *parent, str
sc->sc_ifaceno = uaa->ifaceno;
id = usbd_get_interface_descriptor(sc->sc_iface);
- usbd_set_idle(sc->sc_udev, sc->sc_ifaceno, 0, 0);
+ if (!(usbd_get_quirks(uaa->device)->uq_flags & UQ_NO_SET_IDLE))
+ usbd_set_idle(sc->sc_udev, sc->sc_ifaceno, 0, 0);
sc->sc_iep_addr = sc->sc_oep_addr = -1;
for (i = 0; i < id->bNumEndpoints; i++) {
Index: usb_quirks.c
===
RCS file: /cvs/src/sys/dev/usb/usb_quirks.c,v
retrieving revision 1.76
diff -u -p -u -p -r1.76 usb_quirks.c
--- usb_quirks.c5 Jan 2020 00:54:13 - 1.76
+++ usb_quirks.c18 Aug 2020 13:36:13 -
@@ -52,6 +52,7 @@ const struct usbd_quirk_entry {
u_int16_t bcdDevice;
struct usbd_quirks quirks;
} usb_quirks[] = {
+ { USB_VENDOR_MICROCHIP, USB_PRODUCT_MICROCHIP_SOUNDKEY, ANY, {
UQ_NO_SET_IDLE }}, { USB_VENDOR_KYE, USB_PRODUCT_KYE_NICHE,
0x100, { UQ_NO_SET_PROTO}}, { USB_VENDOR_INSIDEOUT,
USB_PRODUCT_INSIDEOUT_EDGEPORT4, 0x094, { UQ_SWAP_UNICODE}},
Index: usb_quirks.h
===
RCS file: /cvs/src/sys/dev/usb/usb_quirks.h,v
retrieving revision 1.16
diff -u -p -u -p -r1.16 usb_quirks.h
--- usb_quirks.h19 Jul 2010 05:08:37 - 1.16
+++ usb_quirks.h18 Aug 2020 13:36:13 -
@@ -49,6 +49,7 @@ struct usbd_quirks {
#define UQ_MS_LEADING_BYTE 0x0001 /* mouse sends unknown
leading byte */ #define UQ_EHCI_NEEDTO_DISOWN 0x0002 /* must
hand device over to USB 1.1 if attached to EHCI */
+#define UQ_NO_SET_IDLE 0x0004 /* cannot handle set
idle request */ };
extern const struct usbd_quirks usbd_no_quirk;
Index: usbdevs
===
RCS file: /cvs/src/sys/dev/usb/usbdevs,v
retrieving revision 1.720
diff -u -p -u -p -r1.720 usbdevs
--- usbdevs 3 Aug 2020 14:25:44 - 1.720
+++ usbdevs 18 Aug 2020 13:36:14 -
@@ -3009,6 +3009,7 @@ product MGE UPS2 0x UPS
/* Microchip Technology, Inc. products */
product MICROCHIP USBLCD20X2 0x0002 USB-LCD-20x2
product MICROCHIP USBLCD256X64 0xc002 USB-LCD-256x64
+product MICROCHIP SOUNDKEY 0xf0bf Cyrus soundKey
/* Microdia / Sonix Techonology Co., Ltd. products
Re: Acer Aspire A315 laptop firmware fails to load with 6.7
On Tue, Aug 18, 2020 at 12:09:56PM -0400, Jon Fineman wrote: > On Wed, 19 Aug 2020 00:06:59 +1000 > Jonathan Gray wrote: > > > On Sun, Aug 16, 2020 at 02:27:46AM +, Jon Fineman wrote: > > > I was not able to do a proper sendbug report because the PC hangs. > > > > > > I have an Acer Aspire A315 laptop. 6.6 works fine. When I upgrade > > > to 6.7 Release or Snapshot I get the below firmware load error. > > > Below that output is the dmesg from a 6.6 boot so you can see the > > > hardware. > > > > The first boot after a new install will not have the firmware. > > fw_update(1) will run and install it into /etc/firmware/amdgpu/ > > > > Does amdgpu still not attach after you've verified the files are > > present and rebooted? > > > I mounted the memory stick and verified the amd firmware files are > present in /etc/firmware/amdgpu. I also downloaded the ones from 6.7 > and copied them to that directory. > > When I booted it wanted to update the firmware for amdgpu and vmm. > > Then it dies while re-ording the kernel. > > I am not sure how I would tell if the amdgpu attached or not. > > /var/log/message from this test: > > Aug 18 11:54:56 laptop /bsd: softraid0 at root > Aug 18 11:54:56 laptop /bsd: scsibus4 at softraid0: 256 targets > Aug 18 11:54:56 laptop /bsd: root on sd1a (c5239493226aa09b.a) swap on > sd1b dump on sd1b Aug 18 11:54:56 laptop /bsd: initializing kernel > modesetting (STONEY 0x1002:0x98E4 0x1025:0x1192 0xDA). Aug 18 11:54:56 > laptop /bsd: amdgpu_irq_add_domain: stub Aug 18 11:54:56 laptop /bsd: > amdgpu0: 1366x768, 32bpp Aug 18 11:54:56 laptop /bsd: wsdisplay0 at > amdgpu0 mux 1: console (std, vt100 emulation), using wskbd0 Aug 18 > 11:54:56 laptop /bsd: wsdisplay0: screen 1-5 added (std, vt100 > emulation) It has attached here. If there is fatal error such as missing firmware it will detach and efifb or vga will reclaim the console.
Re: Acer Aspire A315 laptop firmware fails to load with 6.7
On Wed, 19 Aug 2020 00:06:59 +1000 Jonathan Gray wrote: > On Sun, Aug 16, 2020 at 02:27:46AM +, Jon Fineman wrote: > > I was not able to do a proper sendbug report because the PC hangs. > > > > I have an Acer Aspire A315 laptop. 6.6 works fine. When I upgrade > > to 6.7 Release or Snapshot I get the below firmware load error. > > Below that output is the dmesg from a 6.6 boot so you can see the > > hardware. > > The first boot after a new install will not have the firmware. > fw_update(1) will run and install it into /etc/firmware/amdgpu/ > > Does amdgpu still not attach after you've verified the files are > present and rebooted? I mounted the memory stick and verified the amd firmware files are present in /etc/firmware/amdgpu. I also downloaded the ones from 6.7 and copied them to that directory. When I booted it wanted to update the firmware for amdgpu and vmm. Then it dies while re-ording the kernel. I am not sure how I would tell if the amdgpu attached or not. /var/log/message from this test: Aug 18 11:54:56 laptop /bsd: softraid0 at root Aug 18 11:54:56 laptop /bsd: scsibus4 at softraid0: 256 targets Aug 18 11:54:56 laptop /bsd: root on sd1a (c5239493226aa09b.a) swap on sd1b dump on sd1b Aug 18 11:54:56 laptop /bsd: initializing kernel modesetting (STONEY 0x1002:0x98E4 0x1025:0x1192 0xDA). Aug 18 11:54:56 laptop /bsd: amdgpu_irq_add_domain: stub Aug 18 11:54:56 laptop /bsd: amdgpu0: 1366x768, 32bpp Aug 18 11:54:56 laptop /bsd: wsdisplay0 at amdgpu0 mux 1: console (std, vt100 emulation), using wskbd0 Aug 18 11:54:56 laptop /bsd: wsdisplay0: screen 1-5 added (std, vt100 emulation) > > > > > It finishes booting and I get a login prompt. About 30 seconds > > after it boots it powers off. For this test to get the below > > /var/log/messages file I installed 6.7 to a flash drive and booted > > from that. > > > > Any thoughts on what might be causing this or how to get more info > > on it? > > That appears to be an unrelated problem. > > > > > Thanks. > > > > Jon > > > > > > /var/log/messages: > > > > Aug 14 09:58:42 laptop /bsd: ugen0 at uhub2 port 3 "Lite-On > > Technology product 0x3015" rev 2.01/0.01 addr 4 Aug 14 09:58:42 > > laptop /bsd: uvideo0 at uhub2 port 4 configuration 1 interface 0 > > "KSVGA0500171401441LM06 VGA WebCam" rev 2.00/0.06 addr 5 Aug 14 > > 09:58:42 laptop /bsd: video0 at uvideo0 Aug 14 09:58:42 laptop > > /bsd: vscsi0 at root Aug 14 09:58:42 laptop /bsd: scsibus3 at > > vscsi0: 256 targets Aug 14 09:58:42 laptop /bsd: softraid0 at root > > Aug 14 09:58:42 laptop /bsd: scsibus4 at softraid0: 256 targets Aug > > 14 09:58:42 laptop /bsd: root on sd1a (c5239493226aa09b.a) swap on > > sd1b dump on sd1b Aug 14 09:58:42 laptop /bsd: initializing kernel > > modesetting (STONEY 0x1002:0x98E4 0x1025:0x1192 0xDA). Aug 14 > > 09:58:42 laptop /bsd: amdgpu_irq_add_domain: stub Aug 14 09:58:42 > > laptop /bsd: drm:pid0:gfx_v8_0_init_microcode *ERROR* gfx8: Failed > > to load firmware "amdgpu/stoney_pfp.bin" Aug 14 09:58:42 laptop > > /bsd: [drm] *ERROR* Failed to load gfx firmware! Aug 14 09:58:42 > > laptop /bsd: [drm] *ERROR* sw_init of IP block failed -2 > > Aug 14 09:58:42 laptop /bsd: drm:pid0:amdgpu_device_init *ERROR* > > amdgpu_device_ip_init failed Aug 14 09:58:42 laptop /bsd: > > drm:pid0:amdgpu_attachhook *ERROR* Fatal error during GPU init Aug > > 14 09:58:42 laptop /bsd: efifb0 at mainbus0: 1366x768, 32bpp Aug 14 > > 09:58:42 laptop /bsd: wsdisplay0 at efifb0 mux 1: console (std, > > vt100 emulation), using wskbd0 Aug 14 09:58:42 laptop /bsd: > > wsdisplay0: screen 1-5 added (std, vt100 emulation) > > > > > > > > DMESG: > > > > OpenBSD 6.6 (GENERIC.MP) #3: Mon Jul 20 23:21:24 MDT 2020 > > t...@syspatch-66-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > real mem = 5978714112 (5701MB) > > avail mem = 5784797184 (5516MB) > > mpath0 at root > > scsibus0 at mpath0: 256 targets > > mainbus0 at root > > bios0 at mainbus0: SMBIOS rev. 3.0 @ 0xdf266000 (27 entries) > > bios0: vendor Insyde Corp. version "V1.00" date 03/20/2017 > > bios0: Acer Aspire A315-21 > > acpi0 at bios0: ACPI 5.0 > > acpi0: sleep states S0 S3 S4 S5 > > acpi0: tables DSDT FACP MSDM BOOT HPET MCFG WDAT UEFI SSDT IVRS SSDT > > SSDT SSDT UEFI SPCR SSDT CRAT TPM2 FPDT ASF! WDRT VFCT SSDT APIC > > SSDT BGRT acpi0: wakeup devices GPP1(S4) GPP4(S4) GFX0(S4) GFX1(S4) > > GFX2(S4) GFX3(S4) GFX4(S4) EHC1(S3) XHC0(S3) acpitimer0 at acpi0: > > 3579545 Hz, 32 bits acpihpet0 at acpi0: 14318180 Hz acpimcfg0 at > > acpi0 acpimcfg0: addr 0xf800, bus 0-63 > > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > > cpu0 at mainbus0: apid 16 (boot processor) > > cpu0: AMD A9-9420 RADEON R5, 5 COMPUTE CORES 2C+3G, 2994.79 MHz, > > 15-70-00 cpu0: > >
Re: scanimage -L triggers panic, free: size too large 55 > 32
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. > pkg_add usbutils > lsusb > lsusb -d : -v # lsusb -v -d 04e8:3469 Bus 000 Device 002: ID 04e8:3469 Samsung Electronics Co., Ltd Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x04e8 Samsung Electronics Co., Ltd idProduct 0x3469 bcdDevice1.00 iManufacturer 1 Samsung Electronics Co., Ltd. iProduct2 M2070 Series iSerial 3 ZF46B8KM2D02Z1A bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 55 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower2mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x04 EP 4 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 10 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 10 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 7 Printer bInterfaceSubClass 1 Printer bInterfaceProtocol 2 Bidirectional iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 10 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 10 Device Qualifier (for other device speed): bLength10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 bNumConfigurations 1 Device Status: 0x0001 Self Powered -- Regards, Mikolaj
Re: Acer Aspire A315 laptop firmware fails to load with 6.7
On Sun, Aug 16, 2020 at 02:27:46AM +, Jon Fineman wrote: > I was not able to do a proper sendbug report because the PC hangs. > > I have an Acer Aspire A315 laptop. 6.6 works fine. When I upgrade to 6.7 > Release or Snapshot I get the below firmware load error. Below that output is > the dmesg from a 6.6 boot so you can see the hardware. The first boot after a new install will not have the firmware. fw_update(1) will run and install it into /etc/firmware/amdgpu/ Does amdgpu still not attach after you've verified the files are present and rebooted? > > It finishes booting and I get a login prompt. About 30 seconds after it boots > it powers off. For this test to get the below /var/log/messages file I > installed 6.7 to a flash drive and booted from that. > > Any thoughts on what might be causing this or how to get more info on it? That appears to be an unrelated problem. > > Thanks. > > Jon > > > /var/log/messages: > > Aug 14 09:58:42 laptop /bsd: ugen0 at uhub2 port 3 "Lite-On Technology > product 0x3015" rev 2.01/0.01 addr 4 > Aug 14 09:58:42 laptop /bsd: uvideo0 at uhub2 port 4 configuration 1 > interface 0 "KSVGA0500171401441LM06 VGA WebCam" rev 2.00/0.06 addr 5 > Aug 14 09:58:42 laptop /bsd: video0 at uvideo0 > Aug 14 09:58:42 laptop /bsd: vscsi0 at root > Aug 14 09:58:42 laptop /bsd: scsibus3 at vscsi0: 256 targets > Aug 14 09:58:42 laptop /bsd: softraid0 at root > Aug 14 09:58:42 laptop /bsd: scsibus4 at softraid0: 256 targets > Aug 14 09:58:42 laptop /bsd: root on sd1a (c5239493226aa09b.a) swap on sd1b > dump on sd1b > Aug 14 09:58:42 laptop /bsd: initializing kernel modesetting (STONEY > 0x1002:0x98E4 0x1025:0x1192 0xDA). > Aug 14 09:58:42 laptop /bsd: amdgpu_irq_add_domain: stub > Aug 14 09:58:42 laptop /bsd: drm:pid0:gfx_v8_0_init_microcode *ERROR* gfx8: > Failed to load firmware "amdgpu/stoney_pfp.bin" > Aug 14 09:58:42 laptop /bsd: [drm] *ERROR* Failed to load gfx firmware! > Aug 14 09:58:42 laptop /bsd: [drm] *ERROR* sw_init of IP block > failed -2 > Aug 14 09:58:42 laptop /bsd: drm:pid0:amdgpu_device_init *ERROR* > amdgpu_device_ip_init failed > Aug 14 09:58:42 laptop /bsd: drm:pid0:amdgpu_attachhook *ERROR* Fatal error > during GPU init > Aug 14 09:58:42 laptop /bsd: efifb0 at mainbus0: 1366x768, 32bpp > Aug 14 09:58:42 laptop /bsd: wsdisplay0 at efifb0 mux 1: console (std, vt100 > emulation), using wskbd0 > Aug 14 09:58:42 laptop /bsd: wsdisplay0: screen 1-5 added (std, vt100 > emulation) > > > > DMESG: > > OpenBSD 6.6 (GENERIC.MP) #3: Mon Jul 20 23:21:24 MDT 2020 > t...@syspatch-66-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 5978714112 (5701MB) > avail mem = 5784797184 (5516MB) > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 3.0 @ 0xdf266000 (27 entries) > bios0: vendor Insyde Corp. version "V1.00" date 03/20/2017 > bios0: Acer Aspire A315-21 > acpi0 at bios0: ACPI 5.0 > acpi0: sleep states S0 S3 S4 S5 > acpi0: tables DSDT FACP MSDM BOOT HPET MCFG WDAT UEFI SSDT IVRS SSDT > SSDT SSDT UEFI SPCR SSDT CRAT TPM2 FPDT ASF! WDRT VFCT SSDT APIC > SSDT BGRT acpi0: wakeup devices GPP1(S4) GPP4(S4) GFX0(S4) GFX1(S4) > GFX2(S4) GFX3(S4) GFX4(S4) EHC1(S3) XHC0(S3) acpitimer0 at acpi0: > 3579545 Hz, 32 bits acpihpet0 at acpi0: 14318180 Hz acpimcfg0 at > acpi0 acpimcfg0: addr 0xf800, bus 0-63 > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > cpu0 at mainbus0: apid 16 (boot processor) > cpu0: AMD A9-9420 RADEON R5, 5 COMPUTE CORES 2C+3G, 2994.79 MHz, > 15-70-00 cpu0: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,TCE,NODEID,TBM,CPCTR,DBKP,PERFTSC,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,XSAVEOPT > cpu0: 96KB 64b/line 3-way I-cache, 32KB 64b/line 8-way D-cache, 1MB > 64b/line 16-way L2 cache cpu0: ITLB 48 4KB entries fully > associative, 24 4MB entries fully associative cpu0: DTLB 64 4KB > entries fully associative, 64 4MB entries fully associative cpu0: > smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var > ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: > mwait min=64, max=64, IBE cpu1 at mainbus0: apid 17 (application > processor) cpu1: AMD A9-9420 RADEON R5, 5 COMPUTE CORES 2C+3G, > 2994.40 MHz, 15-70-00 cpu1: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,TCE,NODEID,TBM,CPCTR,DBKP,PERFTSC,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,XSAVEOPT > cpu1: 96KB 64b/line 3-way I-cache, 32KB 64b/line 8-way D-cache, 1MB > 64b/line 16-way L2 cache
Re: umb(4) /bsd: usb_insert_transfer: xfer=0xfffffd843de527c0 not free
On 2020-08-18 00:03, Christoph R. Winter wrote: Hello, thanks for your fast answer. Am 17.08.2020 11:29, schrieb Gerhard Roth: The "not on queue" error sounds more like a bug in xhci(4). Could you please try to disable USB3 in the BIOS an see if the problem resolves then. I disabled USB3 in the BIOS but the connection died again randomly. The difference is, without USB3 there are no errors in XConsole nor in /var/log/messages. I also tried the HDD with OpenBSD in a ThinkPad W541 with another LTE card (other card but same model) with exact the same results. To verify that it is no hardware thing, I tried a recent live version of a Linux Mint on booth machines. The download and to run it for some time worked without any connection lose. Regards, Christoph Hi Christoph, MBIM has a method to reset devices. However, this is not implemented in umb(4). So it the device detaches itself from the USB this is almost certainly a firmware bug. Just because you didn't see it with Linux doesn't mean that this has to be a problem with umb(4). On freedesktop.org (the home of libmbim), there have been reports of detaching EM7345, too. And all of them suggest a firmware update. See https://lists.freedesktop.org/archives/libqmi-devel/2018-August/002947.html Could you please check, if there is a newer firmware available an if so, update your device. Gerhard
