Re: ttyC0 floods with error messages
I'm the original poster of this thread, don't mean to whip a dead horse, but this post is to confirm the state of this issue. The most recent -current release before this post has fixed this issue for me. OpenBSD 6.6-current (GENERIC.MP) #573: Sat Dec 28 19:13:57 MST 2019 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP I'm longer greeted with the given train of messages from kernel. >wsmouse0 at ums0 mux 0 >wsmouse0 detached >ums0 detached >uhidev2 detached >uhidev2 at uhub5 port 2 configuration 1 interface 0 "Logitech USB Optical >Mouse" rev 2.00/72.00 addr 3 >uhidev2: iclass 3/1 >ums0 at uhidev2: 3 buttons, Z dir Major props to the OpenBSD Devs for dealing with this successfully and in such a short time.
Re: ttyC0 floods with error messages
"Raymond, David" wrote: > I get similar stuff on console 1 but not on the others on all my > OpenBSD machines. As I use X windows and have clean consoles 2-4 > available if necessary, I just ignore it. > > Dave Raymond > > > On 12/16/19, putridsou...@gmail.com wrote: > > The error does not seem to be a faulty mouse and I > > don't use a KVM switch anyway so it is not the source. > > Following on pervious reply, I tried on a new mouse. > > But was greeted with the same error: > > > > wsmouse0 detached > > ums0 detached > > uhidev0 detached > > uhidev0 at uhub0 port 4 configuration 1 interface 0 "PixArt USB Optical > > Mouse" rev 2.00/1.00 addr 2 > > uhidev0: iclass 3/1 > > ums0 at uhidev0: 3 buttons, Z dir > > wsmouse0 at ums0 mux 0 > > > > Unless I'm the unfortunate person destined to own all faulty > > mice in the world, I look forward to a solution. Is there > > anyone here who uses a desktop setup with a mouse, not greeted > > with these pesky errors. Are experts on here sure this is not > > a bug, or lack of proper driver. More info on the latter, this > > test consisted of Logitech M90 and Dell MS111-P mouse. > > > > > > > -- > David J. Raymond > david.raym...@nmt.edu > http://physics.nmt.edu/~raymond I get this also on my Intel NUC with the mouse connected via an Anker 7 port HUB extender. I was tidying up my cables yesterday and moved my mouse cable to one of the NUC's ports and I haven't been spammed since. The dmesg that was sent in looked like it had a USB HUB and then someone mentioned a KVM switch. So not sure if the mice or host don't like how they are connected.
Re: ttyC0 floods with error messages
On 12-16 10:48, Raymond, David wrote: > I get similar stuff on console 1 but not on the others on all my > OpenBSD machines. As I use X windows and have clean consoles 2-4 > available if necessary, I just ignore it. I get similar messages in dmesg (used to be on the first console), and every couple of days or so (not a consistent period), the mouse just stops working, sometimes working again a few days after I unplug it, so I switch that way between a wireless and wired mouse until they both stop and when I get tired enough of being mouseless then I reboot. Ending message with dmesg output: OpenBSD 6.5 (GENERIC.MP) #5: Thu Aug 29 20:38:30 CEST 2019 r...@syspatch-65-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 16033533952 (15290MB) avail mem = 15537967104 (14818MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xebf90 (49 entries) bios0: vendor American Megatrends Inc. version "204" date 11/20/2014 bios0: ASUSTeK COMPUTER INC. X550ZA acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT ECDT MCFG MSDM HPET UEFI SSDT SSDT CRAT SSDT SSDT SSDT SSDT acpi0: wakeup devices LOM_(S4) SBAZ(S4) ECIR(S4) OHC1(S4) EHC1(S4) OHC2(S4) EHC2(S4) OHC3(S4) EHC3(S4) OHC4(S4) XHC0(S4) XHC1(S4) ODD8(S3) GLAN(S4) LID_(S5) SLPB(S4) acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 16 (boot processor) cpu0: AMD A10-7400P Radeon R6, 10 Compute Cores 4C+6G, 2496.48 MHz, 15-30-01 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,POPCNT,AES,XSAVE,AVX,F16C,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,ITSC,FSGSBASE,BMI1,XSAVEOPT cpu0: 96KB 64b/line 3-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 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 A10-7400P Radeon R6, 10 Compute Cores 4C+6G, 2495.34 MHz, 15-30-01 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,POPCNT,AES,XSAVE,AVX,F16C,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,ITSC,FSGSBASE,BMI1,XSAVEOPT cpu1: 96KB 64b/line 3-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 16-way L2 cache cpu1: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative cpu1: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu1: smt 1, core 0, package 0 cpu2 at mainbus0: apid 18 (application processor) cpu2: AMD A10-7400P Radeon R6, 10 Compute Cores 4C+6G, 2495.34 MHz, 15-30-01 cpu2: 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,POPCNT,AES,XSAVE,AVX,F16C,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,ITSC,FSGSBASE,BMI1,XSAVEOPT cpu2: 96KB 64b/line 3-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 16-way L2 cache cpu2: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative cpu2: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu2: smt 0, core 1, package 0 cpu3 at mainbus0: apid 19 (application processor) cpu3: AMD A10-7400P Radeon R6, 10 Compute Cores 4C+6G, 2495.34 MHz, 15-30-01 cpu3: 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,POPCNT,AES,XSAVE,AVX,F16C,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,ITSC,FSGSBASE,BMI1,XSAVEOPT cpu3: 96KB 64b/line 3-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 16-way L2 cache cpu3: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative cpu3: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 0 pa 0xfec0, version 21, 24 pins ioapic1 at mainbus0: apid 1 pa 0xfec01000, version 21, 32 pins acpiec0 at acpi0 acpimcfg0 at acpi0 acpimcfg0: addr 0xe000, bus 0-255 acpihpet0 at acpi0: 14318180 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PB21) acpiprt2 at acpi0: bus -1 (PB22) acpiprt3 at acpi0: bus -1
Re: ttyC0 floods with error messages
USB subsystem bugs. Whoever said it was your mouse or cable is being an inaccurate jerk. Raymond, David wrote: > I get similar stuff on console 1 but not on the others on all my > OpenBSD machines. As I use X windows and have clean consoles 2-4 > available if necessary, I just ignore it. > > Dave Raymond > > > On 12/16/19, putridsou...@gmail.com wrote: > > The error does not seem to be a faulty mouse and I > > don't use a KVM switch anyway so it is not the source. > > Following on pervious reply, I tried on a new mouse. > > But was greeted with the same error: > > > > wsmouse0 detached > > ums0 detached > > uhidev0 detached > > uhidev0 at uhub0 port 4 configuration 1 interface 0 "PixArt USB Optical > > Mouse" rev 2.00/1.00 addr 2 > > uhidev0: iclass 3/1 > > ums0 at uhidev0: 3 buttons, Z dir > > wsmouse0 at ums0 mux 0 > > > > Unless I'm the unfortunate person destined to own all faulty > > mice in the world, I look forward to a solution. Is there > > anyone here who uses a desktop setup with a mouse, not greeted > > with these pesky errors. Are experts on here sure this is not > > a bug, or lack of proper driver. More info on the latter, this > > test consisted of Logitech M90 and Dell MS111-P mouse. > > > > > > > -- > David J. Raymond > david.raym...@nmt.edu > http://physics.nmt.edu/~raymond >
Re: ttyC0 floods with error messages
I get similar stuff on console 1 but not on the others on all my OpenBSD machines. As I use X windows and have clean consoles 2-4 available if necessary, I just ignore it. Dave Raymond On 12/16/19, putridsou...@gmail.com wrote: > The error does not seem to be a faulty mouse and I > don't use a KVM switch anyway so it is not the source. > Following on pervious reply, I tried on a new mouse. > But was greeted with the same error: > > wsmouse0 detached > ums0 detached > uhidev0 detached > uhidev0 at uhub0 port 4 configuration 1 interface 0 "PixArt USB Optical > Mouse" rev 2.00/1.00 addr 2 > uhidev0: iclass 3/1 > ums0 at uhidev0: 3 buttons, Z dir > wsmouse0 at ums0 mux 0 > > Unless I'm the unfortunate person destined to own all faulty > mice in the world, I look forward to a solution. Is there > anyone here who uses a desktop setup with a mouse, not greeted > with these pesky errors. Are experts on here sure this is not > a bug, or lack of proper driver. More info on the latter, this > test consisted of Logitech M90 and Dell MS111-P mouse. > > -- David J. Raymond david.raym...@nmt.edu http://physics.nmt.edu/~raymond
Re: ttyC0 floods with error messages
The error does not seem to be a faulty mouse and I don't use a KVM switch anyway so it is not the source. Following on pervious reply, I tried on a new mouse. But was greeted with the same error: wsmouse0 detached ums0 detached uhidev0 detached uhidev0 at uhub0 port 4 configuration 1 interface 0 "PixArt USB Optical Mouse" rev 2.00/1.00 addr 2 uhidev0: iclass 3/1 ums0 at uhidev0: 3 buttons, Z dir wsmouse0 at ums0 mux 0 Unless I'm the unfortunate person destined to own all faulty mice in the world, I look forward to a solution. Is there anyone here who uses a desktop setup with a mouse, not greeted with these pesky errors. Are experts on here sure this is not a bug, or lack of proper driver. More info on the latter, this test consisted of Logitech M90 and Dell MS111-P mouse.
Re: ttyC0 floods with error messages
On Fri, Dec 13, 2019 at 8:42 AM wrote: > After boot, the following error message floods the virtual console on > ttyC0 repeatedly, rest of virtuals console stay clear somehow. Is there a > way to > treat this permanently, other than Ctrl-l everytime, or disconnecting the > mouse. > There must be some config to disable this direct dumping of errors onto > console. > > wsmouse0 at ums0 mux 0 > wsmouse0 detached > ums0 detached > uhidev2 detached > uhidev2 at uhub5 port 2 configuration 1 interface 0 "Logitech USB Optical > Mouse" rev 2.00/72.00 addr 3 > uhidev2: iclass 3/1 > ums0 at uhidev2: 3 buttons, Z dir > In my experience when the console is spammed by mouse detach and attach events, it's because the mouse is defective, usually because the cable is wearing out and developing an intermittent fault. Switch to a different mouse, even if the mouse appears to work ok, because it will probably get worse. Another reason for these messages is because you're using a KVM switch that performs the switch operation by disconnecting/reconnecting your USB devices, but I assume that isn't the cause here. Suppressing the errors is probably a bad idea, in that case how would you know your mouse is developing a fault until more serious problems arise? Better to be notified early so you have time to deal with it. -ken
Re: ttyC0 floods with error messages
On Fri, 13 Dec 2019, putridsou...@gmail.com wrote: Date: Fri, 13 Dec 2019 19:12:41 +0530 (IST) From: putridsou...@gmail.com To: misc@openbsd.org Subject: ttyC0 floods with error messages After boot, the following error message floods the virtual console on ttyC0 repeatedly, rest of virtuals console stay clear somehow. Is there a way to treat this permanently, other than Ctrl-l everytime, or disconnecting the mouse. There must be some config to disable this direct dumping of errors onto console. wsmouse0 at ums0 mux 0 wsmouse0 detached ums0 detached uhidev2 detached uhidev2 at uhub5 port 2 configuration 1 interface 0 "Logitech USB Optical Mouse" rev 2.00/72.00 addr 3 uhidev2: iclass 3/1 ums0 at uhidev2: 3 buttons, Z dir For some reason the same happens to me with both OpenBSD & NetBSD, but not with FreeBSD which is rock solid. I tend to just jump up to tty2 or whatever. Of course you can't do that on the installation. Good Luck, Clay clays.sh...@sdf.org SDF Public Access UNIX System - http://sdf.org
ttyC0 floods with error messages
After boot, the following error message floods the virtual console on ttyC0 repeatedly, rest of virtuals console stay clear somehow. Is there a way to treat this permanently, other than Ctrl-l everytime, or disconnecting the mouse. There must be some config to disable this direct dumping of errors onto console. wsmouse0 at ums0 mux 0 wsmouse0 detached ums0 detached uhidev2 detached uhidev2 at uhub5 port 2 configuration 1 interface 0 "Logitech USB Optical Mouse" rev 2.00/72.00 addr 3 uhidev2: iclass 3/1 ums0 at uhidev2: 3 buttons, Z dir
