search for: 0x85

...Report Descriptor: (656 bytes) => 05 84 09 04 a1 01 09 > 0.157431 24 a1 00 85 01 09 fe 75 08 95 01 15 00 Here is the output from that command. Thank you for your help. usbconfig -u 4 -a 2 do_request 0x81 0x06 0x2200 0 0x100 REQUEST = <0x05 0x84 0x09 0x04 0xa1 0x01 0x09 0x24 0xa1 0x00 0x85 0x01 0x09 0xfe 0x75 0x08 0x95 0x01 0x15 0x00 0x26 0xff 0x00 0xb1 0x22 0x85 0x02 0x09 0xff 0xb1 0x22 0x85 0x03 0x05 0x85 0x09 0x8f 0xb1 0x22 0x85 0x04 0x09 0x89 0xb1 0x22 0x85 0x05 0x09 0x8b 0xb1 0x22 0x85 0x06 0x09 0x2c 0xb1 0x22 0x85 0x07 0x75 0x08 0x95 0x05 0x25 0x64 0x09 0x83 0x09 0x8d 0x09 0x8e...

...wMaxPacketSize = 0x0008 ??????? bInterval = 0x000c ??????? bRefresh = 0x0000 ??????? bSynchAddress = 0x0000 usbconfig -u 0 -a 5 do_request 0x81 0x06 0x2200 0 0x100 ?datanas: ~# usbconfig -u 0 -a 5 do_request 0x81 0x06 0x2200 0 0x100 REQUEST = <0x05 0x84 0x09 0x04 0xa1 0x01 0x09 0x24 0xa1 0x00 0x85 0x28 0x09 0xfe 0x79 0x01 0x75 0x08 0x95 0x01 0x15 0x00 0x26 0xff 0x00 0xb1 0x03 0x85 0x29 0x09 0xff 0x79 0x05 0xb1 0x03 0x85 0x2b 0x09 0xfd 0x79 0x03 0xb1 0x03 0x09 0x1a 0xa1 0x02 0x85 0x30 0x09 0x40 0x67 0x21 0xd1 0xf0 0x00 0x55 0x07 0xb1 0x83 0x85 0x31 0x09 0x30 0x75 0x10 0x95 0x01 0x15 0x00 0x27...

...ytes) => 05 84 09 04 a1 01 09 >> 0.157431 24 a1 00 85 01 09 fe 75 08 95 01 15 00 > > Here is the output from that command. Thank you for your help. > > usbconfig -u 4 -a 2 do_request 0x81 0x06 0x2200 0 0x100 > REQUEST = <0x05 0x84 0x09 0x04 0xa1 0x01 0x09 0x24 0xa1 0x00 0x85 0x01 0x09 0xfe > 0x75 0x08 0x95 0x01 0x15 0x00 0x26 0xff 0x00 0xb1 0x22 0x85 0x02 0x09 0xff 0xb1 > 0x22 0x85 0x03 0x05 0x85 0x09 0x8f 0xb1 0x22 0x85 0x04 0x09 0x89 0xb1 0x22 0x85 > 0x05 0x09 0x8b 0xb1 0x22 0x85 0x06 0x09 0x2c 0xb1 0x22 0x85 0x07 0x75 0x08 0x95 > 0x05 0x25 0x64 0x09 0x83...

>> >> The output was also not as big as you made it out to be. > > Well, I didn't expect the driver to fail *that* badly :-) > > Assuming the UPS is still at /dev/ugen4.2, can you try the following command? (Probably needs to be run as root, with the driver stopped.) > > usbconfig -u 4 -a 2 dump_curr_config_desc Here is output of the command. Thank you for

Hi Everyone, I'm having trouble getting TrippLite SMX1500LCDT to work on FreeBSD 11.2, nut 2.7.4 installed from FreeBSD port. The debug output is rather big when I'm starting usbhid-ups initially, Please find that attached (gzipped to comply with message size limit). Subsequently, until I unplug and replug the USB cable, I'm geting a shorter debug output, like this: Network UPS

...<IN> bmAttributes = 0x0003 <INTERRUPT> wMaxPacketSize = 0x0008 bInterval = 0x000c bRefresh = 0x0000 bSynchAddress = 0x0000 # usbconfig -u 1 -a 3 do_request 0x81 0x06 0x2200 0 0x100 REQUEST = <0x05 0x84 0x09 0x04 0xa1 0x01 0x09 0x24 0xa1 0x00 0x85 0x28 0x09 0xfe 0x79 0x01 0x75 0x08 0x95 0x01 0x15 0x00 0x26 0xff 0x00 0xb1 0x03 0x85 0x29 0x09 0xff 0x79 0x05 0xb1 0x03 0x85 0x2b 0x09 0xfd 0x79 0x03 0xb1 0x03 0x09 0x1a 0xa1 0x02 0x85 0x30 0x09 0x40 0x67 0x21 0xd1 0xf0 0x00 0x55 0x07 0xb1 0x83 0x85 0x31 0x09 0x30 0x75 0x10 0x95 0x01 0x15 0x00 0x27...

...wMaxPacketSize = 0x0008 ??????? bInterval = 0x000c ??????? bRefresh = 0x0000 ??????? bSynchAddress = 0x0000 usbconfig -u 0 -a 5 do_request 0x81 0x06 0x2200 0 0x100 ?datanas: ~# usbconfig -u 0 -a 5 do_request 0x81 0x06 0x2200 0 0x100 REQUEST = <0x05 0x84 0x09 0x04 0xa1 0x01 0x09 0x24 0xa1 0x00 0x85 0x28 0x09 0xfe 0x79 0x01 0x75 0x08 0x95 0x01 0x15 0x00 0x26 0xff 0x00 0xb1 0x03 0x85 0x29 0x09 0xff 0x79 0x05 0xb1 0x03 0x85 0x2b 0x09 0xfd 0x79 0x03 0xb1 0x03 0x09 0x1a 0xa1 0x02 0x85 0x30 0x09 0x40 0x67 0x21 0xd1 0xf0 0x00 0x55 0x07 0xb1 0x83 0x85 0x31 0x09 0x30 0x75 0x10 0x95 0x01 0x15 0x00 0x27...

...abled: > > kernel BUG at include/linux/scatterlist.h:187! > invalid opcode: 0000 [#1] PREEMPT SMP NOPTI > CPU: 7 PID: 930 Comm: (udev-worker) Not tainted 6.9.0-rc3Lyude-Test+ #30 > Hardware name: MSI MS-7A39/A320M GAMING PRO (MS-7A39), BIOS 1.I0 01/22/2019 > RIP: 0010:sg_init_one+0x85/0xa0 > Code: 69 88 32 01 83 e1 03 f6 c3 03 75 20 a8 01 75 1e 48 09 cb 41 89 54 > 24 08 49 89 1c 24 41 89 6c 24 0c 5b 5d 41 5c e9 7b b9 88 00 <0f> 0b 0f 0b > 0f 0b 48 8b 05 5e 46 9a 01 eb b2 66 66 2e 0f 1f 84 00 > RSP: 0018:ffffa776017bf6a0 EFLAGS: 00010246 > RAX: 00000000000000...

...startup, when the iommu is enabled: kernel BUG at include/linux/scatterlist.h:187! invalid opcode: 0000 [#1] PREEMPT SMP NOPTI CPU: 7 PID: 930 Comm: (udev-worker) Not tainted 6.9.0-rc3Lyude-Test+ #30 Hardware name: MSI MS-7A39/A320M GAMING PRO (MS-7A39), BIOS 1.I0 01/22/2019 RIP: 0010:sg_init_one+0x85/0xa0 Code: 69 88 32 01 83 e1 03 f6 c3 03 75 20 a8 01 75 1e 48 09 cb 41 89 54 24 08 49 89 1c 24 41 89 6c 24 0c 5b 5d 41 5c e9 7b b9 88 00 <0f> 0b 0f 0b 0f 0b 48 8b 05 5e 46 9a 01 eb b2 66 66 2e 0f 1f 84 00 RSP: 0018:ffffa776017bf6a0 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffffa77600d87000...

> What does that revision number correspond to in FreeBSD release numbers? (e.g. 9.3, 10.0) FreeBSD 10.2-RELEASE #0 r286738M the last person probably wasn't able to give the ./configure probably because most people uses the precompiled iso to install NAS4Free.? if you need the ./configure I might have to look for their source on GitHub or something. /usr/local/libexec/nut/usbhid-ups -a

...00000000 f7caf400 f71b9df0 f71503d4 ffffffff 00000000 f7159c68 > kernel: Call Trace: > kernel: [<c025eb29>] memcpy_toiovec+0x29/0x50 > kernel: [<c019dbda>] ext3_lookup+0x3a/0xc0 > kernel: [<c0167c8e>] real_lookup+0xae/0xd0 > kernel: [<c0167f35>] do_lookup+0x85/0x90 > kernel: [<c016872f>] __link_path_walk+0x7ef/0xdd0 > kernel: [<c0168d5e>] link_path_walk+0x4e/0xd0 > kernel: [<c016907f>] path_lookup+0x9f/0x170 > kernel: [<c01693cf>] __user_walk+0x2f/0x60 > kernel: [<c0163b5d>] vfs_stat+0x1d/0x60 > kernel...

...to hit a BUG() on startup: kernel BUG at include/linux/scatterlist.h:187! invalid opcode: 0000 [#1] PREEMPT SMP NOPTI CPU: 7 PID: 930 Comm: (udev-worker) Not tainted 6.9.0-rc3Lyude-Test+ #30 Hardware name: MSI MS-7A39/A320M GAMING PRO (MS-7A39), BIOS 1.I0 01/22/2019 RIP: 0010:sg_init_one+0x85/0xa0 Code: 69 88 32 01 83 e1 03 f6 c3 03 75 20 a8 01 75 1e 48 09 cb 41 89 54 24 08 49 89 1c 24 41 89 6c 24 0c 5b 5d 41 5c e9 7b b9 88 00 <0f> 0b 0f 0b 0f 0b 48 8b 05 5e 46 9a 01 eb b2 66 66 2e 0f 1f 84 00 RSP: 0018:ffffa776017bf6a0 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffffa77...

...... yes ------------------------------------------------------------------------ Test Program: #include <stdint.h> #include <string.h> #include <opus.h> #include <stdio.h> #include <assert.h> uint8_t bbKnownBuffer[1920] __attribute__((aligned (8))) = { 0x85, 0x00, 0x92, 0x00, 0xa0, 0x00, 0xab, 0x00, 0x7e, 0x00, 0x88, 0x00, 0x3c, 0x00, 0x4e, 0x00, 0xf5, 0xff, 0x00, 0x00, 0xdb, 0xff, 0xe0, 0xff, 0xc8, 0xff, 0xd2, 0xff, 0xae, 0xff, 0xba, 0xff, 0x89, 0xff, 0x90, 0xff, 0x66, 0xff, 0x81, 0xff, 0x6e, 0xff, 0x7f, 0xff, 0x64, 0xff, 0x87, 0xff,...

...ACPI_VIDEO_DEVICE_NAME "Video Device" -#define ACPI_VIDEO_NOTIFY_SWITCH 0x80 -#define ACPI_VIDEO_NOTIFY_PROBE 0x81 -#define ACPI_VIDEO_NOTIFY_CYCLE 0x82 -#define ACPI_VIDEO_NOTIFY_NEXT_OUTPUT 0x83 -#define ACPI_VIDEO_NOTIFY_PREV_OUTPUT 0x84 - -#define ACPI_VIDEO_NOTIFY_CYCLE_BRIGHTNESS 0x85 -#define ACPI_VIDEO_NOTIFY_INC_BRIGHTNESS 0x86 -#define ACPI_VIDEO_NOTIFY_DEC_BRIGHTNESS 0x87 -#define ACPI_VIDEO_NOTIFY_ZERO_BRIGHTNESS 0x88 -#define ACPI_VIDEO_NOTIFY_DISPLAY_OFF 0x89 #define MAX_NAME_LEN 20 diff --git a/include/acpi/video.h b/include/acpi/video.h index 4536bd3..bfe484d 100...

...0x7fac7f48826b] -> /usr/lib/dovecot/libdovecot.so.0(+0xe8392) [0x7fac7f533392] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x4ffc8) [0x7fac7f814fc8] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_context_deactivate+0x5d) [0x7fac7f52ec5d] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x85) [0x7fac7f52f055] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x10f) [0x7fac7f53092f] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x52) [0x7fac7f52f132] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7fac7f52f358] -> /usr/lib/dovecot/libdovecot...

...can ssh to it. The "issue" I have is that there is nothing interesting (afaict) in any log. Nothing in Xog.0.log, nothing in dmesg. The one intersting thing I've noticed is that with drm debuging on I get a ton of these on dmesg: host [drm:drm_ioctl], pid=2391, cmd=0x40086485, nr=0x85, dev 0xe200, auth=1 And at, or around the hang, there seem to be a an increase of: host [drm:drm_ioctl], ret = fffffff5 Not particilarly enlighening to the uninitiated. Any ideas how to debug these hangs? Are ther any tools around to e.g. reset the GPU? /Anders

...78, 0x79, 0x7b }, { 0x78, 0x79, 0x7a, 0x7c }, { 0x79, 0x7a, 0x7b, 0x7d }, { 0x7a, 0x7b, 0x7c, 0x7e }, { 0x7b, 0x7c, 0x7d, 0x7f }, { 0x7c, 0x7d, 0x7e, 0x80 }, { 0x7d, 0x7e, 0x7f, 0x81 }, { 0x7e, 0x7f, 0x80, 0x82 }, { 0x7f, 0x80, 0x81, 0x83 }, { 0x80, 0x81, 0x82, 0x84 }, { 0x81, 0x82, 0x83, 0x85 }, { 0x82, 0x83, 0x84, 0x86 }, { 0x83, 0x84, 0x85, 0x87 }, { 0x84, 0x85, 0x86, 0x88 }, { 0x85, 0x86, 0x87, 0x89 }, { 0x86, 0x87, 0x88, 0x8a }, { 0x87, 0x88, 0x89, 0x8b }, { 0x88, 0x89, 0x8a, 0x8c }, { 0x89, 0x8a, 0x8b, 0x8d }, { 0x8a, 0x8b, 0x8c, 0x8e }, { 0x8b, 0x8c, 0x8d, 0x8f }, { 0x8...

...78, 0x79, 0x7b }, { 0x78, 0x79, 0x7a, 0x7c }, { 0x79, 0x7a, 0x7b, 0x7d }, { 0x7a, 0x7b, 0x7c, 0x7e }, { 0x7b, 0x7c, 0x7d, 0x7f }, { 0x7c, 0x7d, 0x7e, 0x80 }, { 0x7d, 0x7e, 0x7f, 0x81 }, { 0x7e, 0x7f, 0x80, 0x82 }, { 0x7f, 0x80, 0x81, 0x83 }, { 0x80, 0x81, 0x82, 0x84 }, { 0x81, 0x82, 0x83, 0x85 }, { 0x82, 0x83, 0x84, 0x86 }, { 0x83, 0x84, 0x85, 0x87 }, { 0x84, 0x85, 0x86, 0x88 }, { 0x85, 0x86, 0x87, 0x89 }, { 0x86, 0x87, 0x88, 0x8a }, { 0x87, 0x88, 0x89, 0x8b }, { 0x88, 0x89, 0x8a, 0x8c }, { 0x89, 0x8a, 0x8b, 0x8d }, { 0x8a, 0x8b, 0x8c, 0x8e }, { 0x8b, 0x8c, 0x8d, 0x8f }, { 0x8...

...node_trace+0x141/0x2c0 [<ffffffff8133ba23>] alloc_cpumask_var_node+0x23/0x80 [<ffffffff8133ba8e>] alloc_cpumask_var+0xe/0x10 [<ffffffff813fdb3d>] vp_try_to_find_vqs+0x25d/0x810 [<ffffffff813fe171>] vp_find_vqs+0x81/0xb0 [<ffffffffa00d2a05>] init_vqs+0x85/0x120 [virtio_balloon] [<ffffffffa00d2c29>] virtballoon_probe+0xf9/0x1a0 [virtio_balloon] [<ffffffff813fb61e>] virtio_dev_probe+0xde/0x140 [<ffffffff814452b8>] driver_probe_device+0x98/0x3a0 [<ffffffff8144566b>] __driver_attach+0xab/0xb0 [<ffffffff8144...

...node_trace+0x141/0x2c0 [<ffffffff8133ba23>] alloc_cpumask_var_node+0x23/0x80 [<ffffffff8133ba8e>] alloc_cpumask_var+0xe/0x10 [<ffffffff813fdb3d>] vp_try_to_find_vqs+0x25d/0x810 [<ffffffff813fe171>] vp_find_vqs+0x81/0xb0 [<ffffffffa00d2a05>] init_vqs+0x85/0x120 [virtio_balloon] [<ffffffffa00d2c29>] virtballoon_probe+0xf9/0x1a0 [virtio_balloon] [<ffffffff813fb61e>] virtio_dev_probe+0xde/0x140 [<ffffffff814452b8>] driver_probe_device+0x98/0x3a0 [<ffffffff8144566b>] __driver_attach+0xab/0xb0 [<ffffffff8144...