Re: Latest snapshot, Logitech keyboard not working.
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 Glocker" wrote: > >> > >> 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 \ > >> keyboard is not sending keypresses. i.e) Pressing the "a" key \ > >> does nothing. There???s an error message saying \ > >> ???uhidev_intr: bad repid 48??? To test that it's not a \ > >> problem with my keyboard I noticed that the function keys still work. \ > >> (The keyboard light). Also to test it's not just my computer I \ > >> plugged in a different keyboard and everything works as it should. \ > >> Below is my dmesg from snapshot: > >> > >> That's probably caused by the new uhidpp driver. A dmesg from a kernel > >> before the upgrade where the keyboard did work would be helpful. > >> > >> Hello, here's a dmesg from 6.8 where the keyboard works: > >> > >> Can you please try to run the -current kernel with uhidpp(4) disabled? > >> > >> I wasn't able to get keyboard input at the UKC prompt so I \ > >> instead ran config(8) and disabled uhidpp there. I hope \ > >> that doesn't impact any debugging. \ > > > > That's fine, too. > > > >> I disabled uhidpp but the problem still persists. There's still \ > >> the error "uhidev_intr: bad repid 48". Below is a dmesg of uhidpp \ > >> disabled: > > > > OK, looks like related to the changes in uhidev(4) made for uhidpp(4). > > Can you please try this diff for a test? > > Since this is the first time I'm doing something like this. I will \ > list out the steps I did to make sure I'm doing this correctly. \ > > # ftp -o - 'https://marc.info/?l=openbsd-bugs=161325400206085=raw' \ > | (cd /usr/src/sys/dev/usb/; patch) > # cd /sys/arch/$(machine)/compile/GENERIC.MP > # make obj > # make config > # make && make install > # reboot > > I noticed the error message is gone now. However the problem remains. \ > Below is the dmesg of the new kernel: Thanks. Sorry, I forgot to mention. Can you please test this diff also with uhidpp(4) disabled?
Re: Latest snapshot, Logitech keyboard not working.
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 Glocker" wrote: >> >> 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 \ >> keyboard is not sending keypresses. i.e) Pressing the "a" key \ >> does nothing. There???s an error message saying \ >> ???uhidev_intr: bad repid 48??? To test that it's not a \ >> problem with my keyboard I noticed that the function keys still work. \ >> (The keyboard light). Also to test it's not just my computer I \ >> plugged in a different keyboard and everything works as it should. \ >> Below is my dmesg from snapshot: >> >> That's probably caused by the new uhidpp driver. A dmesg from a kernel >> before the upgrade where the keyboard did work would be helpful. >> >> Hello, here's a dmesg from 6.8 where the keyboard works: >> >> Can you please try to run the -current kernel with uhidpp(4) disabled? >> >> I wasn't able to get keyboard input at the UKC prompt so I \ >> instead ran config(8) and disabled uhidpp there. I hope \ >> that doesn't impact any debugging. \ > > That's fine, too. > >> I disabled uhidpp but the problem still persists. There's still \ >> the error "uhidev_intr: bad repid 48". Below is a dmesg of uhidpp \ >> disabled: > > OK, looks like related to the changes in uhidev(4) made for uhidpp(4). > Can you please try this diff for a test? Since this is the first time I'm doing something like this. I will \ list out the steps I did to make sure I'm doing this correctly. \ # ftp -o - 'https://marc.info/?l=openbsd-bugs=161325400206085=raw' \ | (cd /usr/src/sys/dev/usb/; patch) # cd /sys/arch/$(machine)/compile/GENERIC.MP # make obj # make config # make && make install # reboot I noticed the error message is gone now. However the problem remains. \ Below is the dmesg of the new kernel: OpenBSD 6.9-beta (GENERIC.MP) #0: Sat Feb 13 20:07:03 EST 2021 mar...@local.hitronhub.home:/sys/arch/amd64/compile/GENERIC.MP real mem = 17111998464 (16319MB) avail mem = 16578056192 (15810MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xe6cf0 (60 entries) bios0: vendor American Megatrends Inc. version "M.60" date 04/18/2020 bios0: Micro-Star International Co., Ltd MS-7B86 acpi0 at bios0: ACPI 6.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT FIDT SSDT SSDT SSDT MCFG HPET UEFI IVRS PCCT SSDT CRAT CDIT SSDT SSDT WSMT acpi0: wakeup devices GPP0(S4) GPP1(S4) GPP3(S4) GPP4(S4) GPP5(S4) GPP6(S4) GPP7(S4) GPP8(S4) GPP9(S4) GPPA(S4) GPPB(S4) GPPC(S4) GPPD(S4) GPPE(S4) GPPF(S4) GP10(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Ryzen 5 3600 6-Core Processor, 3600.49 MHz, 17-71-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,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,IBPB,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu0: 32KB 64b/line 8-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 8-way L2 cache cpu0: ITLB 64 4KB entries fully associative, 64 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 100MHz cpu0: mwait min=64, max=64, C-substates=1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: AMD Ryzen 5 3600 6-Core Processor, 3600.00 MHz, 17-71-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,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,IBPB,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu1: 32KB 64b/line 8-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 8-way L2 cache cpu1: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu1: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: AMD Ryzen 5 3600 6-Core Processor, 3600.00 MHz,
Re: Latest snapshot, Logitech keyboard not working.
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, "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 \ >> keyboard is not sending keypresses. i.e) Pressing the "a" key \ >> does nothing. There???s an error message saying \ >> ???uhidev_intr: bad repid 48??? To test that it's not a \ >> problem with my keyboard I noticed that the function keys still work. \ >> (The keyboard light). Also to test it's not just my computer I \ >> plugged in a different keyboard and everything works as it should. \ >> Below is my dmesg from snapshot: >> >> That's probably caused by the new uhidpp driver. A dmesg from a kernel >> before the upgrade where the keyboard did work would be helpful. >> >> Hello, here's a dmesg from 6.8 where the keyboard works: > > Can you please try to run the -current kernel with uhidpp(4) disabled? I wasn't able to get keyboard input at the UKC prompt so I \ instead ran config(8) and disabled uhidpp there. I hope \ that doesn't impact any debugging. \ I disabled uhidpp but the problem still persists. There's still \ the error "uhidev_intr: bad repid 48". Below is a dmesg of uhidpp \ disabled: OpenBSD 6.9-beta (GENERIC.MP) #332: Fri Feb 12 12:09:40 MST 2021 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17111998464 (16319MB) avail mem = 16578043904 (15810MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xe6cf0 (60 entries) bios0: vendor American Megatrends Inc. version "M.60" date 04/18/2020 bios0: Micro-Star International Co., Ltd MS-7B86 acpi0 at bios0: ACPI 6.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT FIDT SSDT SSDT SSDT MCFG HPET UEFI IVRS PCCT SSDT CRAT CDIT SSDT SSDT WSMT acpi0: wakeup devices GPP0(S4) GPP1(S4) GPP3(S4) GPP4(S4) GPP5(S4) GPP6(S4) GPP7(S4) GPP8(S4) GPP9(S4) GPPA(S4) GPPB(S4) GPPC(S4) GPPD(S4) GPPE(S4) GPPF(S4) GP10(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Ryzen 5 3600 6-Core Processor, 3600.50 MHz, 17-71-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,FFXS ,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,U IP,IBPB,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu0: 32KB 64b/line 8-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 8-way L2 cache cpu0: ITLB 64 4KB entries fully associative, 64 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 100MHz cpu0: mwait min=64, max=64, C-substates=1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: AMD Ryzen 5 3600 6-Core Processor, 3600.02 MHz, 17-71-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,FFXS ,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,U IP,IBPB,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu1: 32KB 64b/line 8-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 8-way L2 cache cpu1: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu1: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: AMD Ryzen 5 3600 6-Core Processor, 3600.01 MHz, 17-71-00 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,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXS ,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,U IP,IBPB,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu2: 32KB 64b/line 8-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 8-way L2 cache cpu2: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu2: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu2: smt 0, core 2, package 0 cpu3 at
Re: Latest snapshot, Logitech keyboard not working.
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, "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 \
> >> keyboard is not sending keypresses. i.e) Pressing the "a" key \
> >> does nothing. There???s an error message saying \
> >> ???uhidev_intr: bad repid 48??? To test that it's not a \
> >> problem with my keyboard I noticed that the function keys still work. \
> >> (The keyboard light). Also to test it's not just my computer I \
> >> plugged in a different keyboard and everything works as it should. \
> >> Below is my dmesg from snapshot:
> >>
> >> That's probably caused by the new uhidpp driver. A dmesg from a kernel
> >> before the upgrade where the keyboard did work would be helpful.
> >>
> >> Hello, here's a dmesg from 6.8 where the keyboard works:
> >
> > Can you please try to run the -current kernel with uhidpp(4) disabled?
>
> I wasn't able to get keyboard input at the UKC prompt so I \
> instead ran config(8) and disabled uhidpp there. I hope \
> that doesn't impact any debugging. \
That's fine, too.
> I disabled uhidpp but the problem still persists. There's still \
> the error "uhidev_intr: bad repid 48". Below is a dmesg of uhidpp \
> disabled:
OK, looks like related to the changes in uhidev(4) made for uhidpp(4).
Can you please try this diff for a test?
Index: uhidev.c
===
RCS file: /cvs/src/sys/dev/usb/uhidev.c,v
retrieving revision 1.88
diff -u -p -u -p -r1.88 uhidev.c
--- uhidev.c11 Feb 2021 06:55:10 - 1.88
+++ uhidev.c13 Feb 2021 22:03:17 -
@@ -256,13 +256,8 @@ uhidev_attach(struct device *parent, str
/* Look for a driver claiming all report IDs first. */
dev = config_found_sm(self, , NULL, uhidevsubmatch);
if (dev != NULL) {
- for (repid = 0; repid < nrepid; repid++) {
- /*
-* Could already be assigned by uhidev_set_report_dev().
-*/
- if (sc->sc_subdevs[repid] == NULL)
- sc->sc_subdevs[repid] = (struct uhidev *)dev;
- }
+ for (repid = 0; repid < nrepid; repid++)
+ sc->sc_subdevs[repid] = (struct uhidev *)dev;
return;
}
@@ -271,10 +266,6 @@ uhidev_attach(struct device *parent, str
if (hid_report_size(desc, size, hid_input, repid) == 0 &&
hid_report_size(desc, size, hid_output, repid) == 0 &&
hid_report_size(desc, size, hid_feature, repid) == 0)
- continue;
-
- /* Could already be assigned by uhidev_set_report_dev(). */
- if (sc->sc_subdevs[repid] != NULL)
continue;
uha.reportid = repid;
Re: Latest snapshot, Logitech keyboard not working.
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 \ >> keyboard is not sending keypresses. i.e) Pressing the "a" key \ >> does nothing. There’s an error message saying \ >> “uhidev_intr: bad repid 48” To test that it's not a \ >> problem with my keyboard I noticed that the function keys still work. \ >> (The keyboard light). Also to test it's not just my computer I \ >> plugged in a different keyboard and everything works as it should. \ >> Below is my dmesg from snapshot: > > That's probably caused by the new uhidpp driver. A dmesg from a kernel > before the upgrade where the keyboard did work would be helpful. Hello, here's a dmesg from 6.8 where the keyboard works: OpenBSD 6.8 (GENERIC.MP) #4: Mon Jan 11 10:35:56 MST 2021 r...@syspatch-68-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17111998464 (16319MB) avail mem = 16578342912 (15810MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xe6cf0 (60 entries) bios0: vendor American Megatrends Inc. version "M.60" date 04/18/2020 bios0: Micro-Star International Co., Ltd MS-7B86 acpi0 at bios0: ACPI 6.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT FIDT SSDT SSDT SSDT MCFG HPET UEFI IVRS PCCT SSDT CRAT CDIT SSDT SSDT WSMT acpi0: wakeup devices GPP0(S4) GPP1(S4) GPP3(S4) GPP4(S4) GPP5(S4) GPP6(S4) GPP7(S4) GPP8(S4) GPP9(S4) GPPA(S4) GPPB(S4) GPPC(S4) GPPD(S4) GPPE(S4) GPPF(S4) GP10(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Ryzen 5 3600 6-Core Processor, 3600.52 MHz, 17-71-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,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,IBPB,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu0: 32KB 64b/line 8-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 8-way L2 cache, 32MB 64b/line disabled L3 cache cpu0: ITLB 64 4KB entries fully associative, 64 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, C-substates=1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: AMD Ryzen 5 3600 6-Core Processor, 3600.00 MHz, 17-71-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,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,IBPB,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu1: 32KB 64b/line 8-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 8-way L2 cache, 32MB 64b/line disabled L3 cache cpu1: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu1: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: AMD Ryzen 5 3600 6-Core Processor, 3600.00 MHz, 17-71-00 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,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,IBPB,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu2: 32KB 64b/line 8-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 8-way L2 cache, 32MB 64b/line disabled L3 cache cpu2: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu2: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 8 (application processor) cpu3: AMD Ryzen 5 3600 6-Core Processor, 3600.01 MHz, 17-71-00 cpu3:
Re: radeondrm AMD A6-3410MX APU with Radeon HD
On 2/13/21 3:55 PM, Jonathan Gray wrote: The 'KASSERT(sc->sc_ecbusy == 0)' in acpiec_gpehandler() fails. Can you try disable acpivideo instead of radeondrm? #gdb (gdb)file bsd.0 (gdb)target kvm bsd.0.core #0 0x811c0730 in dumpsys () (gdb)where #0 0x811c0730 in dumpsys () #1 0x811c0120 in boot () #2 0x81b530ab in reboot () #3 0x8148dcf5 in panic () #4 0x8148ddcb in __assert () #5 0x8148d99f in acpiec_gpehandler () #6 0x81b9c688 in acpi_thread () #7 0x816f942c in proc_trampoline () #8 0x in ?? () I'm not yet sure if this is very useful this is the only thing that seems useful that I've produced following a crash man page, I'll see what comes out of other example usage of these files and append it later assuming no suggestions can be added by this information. I'm trying to understand something but I've never done anything like this. I've rewrote this by hand and made a picture in case, but for now I'll just continue following manual to attempt to produce useful information
Re: radeondrm AMD A6-3410MX APU with Radeon HD
sorry I have replied directly instead of bugs@ before this resending I have done it 3 times slightly differently or with different results 1: boot -c disable acpivideo exit // which provided same black screen as usual 2. boot -dc w db_panic 0 c disable acpivideo exit // which resulted in least informative output I've seen in those messages so far 3. //same steps as in 2 attempt // but this time it triggered some backward 4 digit number sequential output for some time then after reboot I did boot -c disable radeondrm exit //to get back into using machine and it have run, savecore creating 3 files in /var/crash bsd.0 20977746 in size bsd.0.core 8029712920 in size bounds 2 in size so bsd.0 appears as something that could be easily sent over, but that core one is a bit large. How do I proceed ? On 2/13/21 3:55 PM, Jonathan Gray wrote: On Sat, Feb 13, 2021 at 03:01:21PM +0200, V S wrote: If you can see a stack trace on the screen the first few lines of at func_one+0x... at func_two+0x... or a photo would help. I'm suprised the stack trace shows on the screen with db_panic 0 when you mentioned it previously booted to a black screen. The output on the screen seems to be different each time, but repeatedly providing pieces of similar information and seemingly randomly some text is distorted with those white areas which are not always in perfect shape, but I include this URL below which has a bit more consistent piece of text that fits your described pattern. So previous 3 examples were done on yesterdays snapshot, this one after getting another snapshot upgrade an hour or so ago. I'm trying to grasp for how could I provide more information consulting someone on IRC in offtopic channel as I'm also reading man pages for crash and related. And as crash(8) provides an example of looking for information with pattern "function+04711" or similar, something like that is always visible on the screen with your suggested boot options. Disabling swap.encrypt does not seem to aid in genrating anything at /car/crash. But to follow with the example I see that I need to get sources and do stuff that's beyond me especially while any building on that machine takes centuries. SO I'll continue reading these man pages and try to understand how exactly to get more information on this out of the system. I could reinstall back to 6.8 unsure whether that or these snapshots use would be more useful in solving this. I'll just keep it on snapshots for now. Also I forgot to clarify that connecting external monitor when screen is blacked out results in just same black screen on that external monitor, with not responsive keyboard, ctrl_alt_esc does not do anything and I was also trying to adjust ddb.console to 1 that still did not let ctrl_alt_esc to happen from the point which can be seen in the picture. P.S. I havent really used mailing lists before and previously I've attempted to send this with an image attachment, but havent noticed it being delivered for a while now and someone on #openbsd told me it might be better to use an upload service, so I'm resending this with an URL instead of attachment. https://0x0.st/-XcC.jpg The 'KASSERT(sc->sc_ecbusy == 0)' in acpiec_gpehandler() fails. Can you try disable acpivideo instead of radeondrm?
Latest snapshot, Logitech keyboard not working.
On amd64, upgrading from 6.8 stable to snapshot my Logitech G413 \ keyboard is not sending keypresses. i.e) Pressing the "a" key \ does nothing. There’s an error message saying \ “uhidev_intr: bad repid 48” To test that it's not a \ problem with my keyboard I noticed that the function keys still work. \ (The keyboard light). Also to test it's not just my computer I \ plugged in a different keyboard and everything works as it should. \ Below is my dmesg from snapshot: OpenBSD 6.9-beta (GENERIC.MP) #332: Fri Feb 12 12:09:40 MST 2021 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17111998464 (16319MB) avail mem = 16578043904 (15810MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xe6cf0 (60 entries) bios0: vendor American Megatrends Inc. version "M.60" date 04/18/2020 bios0: Micro-Star International Co., Ltd MS-7B86 acpi0 at bios0: ACPI 6.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT FIDT SSDT SSDT SSDT MCFG HPET UEFI IVRS PCCT SSDT CRAT CDIT SSDT SSDT WSMT acpi0: wakeup devices GPP0(S4) GPP1(S4) GPP3(S4) GPP4(S4) GPP5(S4) GPP6(S4) GPP7(S4) GPP8(S4) GPP9(S4) GPPA(S4) GPPB(S4) GPPC(S4) GPPD(S4) GPPE(S4) GPPF(S4) GP10(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Ryzen 5 3600 6-Core Processor, 3600.57 MHz, 17-71-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,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,IBPB,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu0: 32KB 64b/line 8-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 8-way L2 cache cpu0: ITLB 64 4KB entries fully associative, 64 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 100MHz cpu0: mwait min=64, max=64, C-substates=1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: AMD Ryzen 5 3600 6-Core Processor, 3600.01 MHz, 17-71-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,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,IBPB,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu1: 32KB 64b/line 8-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 8-way L2 cache cpu1: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu1: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: AMD Ryzen 5 3600 6-Core Processor, 3600.01 MHz, 17-71-00 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,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,IBPB,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu2: 32KB 64b/line 8-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 8-way L2 cache cpu2: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu2: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 8 (application processor) cpu3: AMD Ryzen 5 3600 6-Core Processor, 3600.01 MHz, 17-71-00 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,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,IBPB,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu3: 32KB 64b/line 8-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 8-way L2 cache cpu3: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu3: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu3: smt 0, core 4, package 0 cpu4 at mainbus0: apid 10 (application processor) cpu4:
Re: Latest snapshot, Logitech keyboard not working.
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 \ > >> keyboard is not sending keypresses. i.e) Pressing the "a" key \ > >> does nothing. There???s an error message saying \ > >> ???uhidev_intr: bad repid 48??? To test that it's not a \ > >> problem with my keyboard I noticed that the function keys still work. \ > >> (The keyboard light). Also to test it's not just my computer I \ > >> plugged in a different keyboard and everything works as it should. \ > >> Below is my dmesg from snapshot: > > > > That's probably caused by the new uhidpp driver. A dmesg from a kernel > > before the upgrade where the keyboard did work would be helpful. > > Hello, here's a dmesg from 6.8 where the keyboard works: Can you please try to run the -current kernel with uhidpp(4) disabled? boot> -c ... UKC> disable uhidpp ...
Re: radeondrm AMD A6-3410MX APU with Radeon HD
If you can see a stack trace on the screen the first few lines of at func_one+0x... at func_two+0x... or a photo would help. I'm suprised the stack trace shows on the screen with db_panic 0 when you mentioned it previously booted to a black screen. The output on the screen seems to be different each time, but repeatedly providing pieces of similar information and seemingly randomly some text is distorted with those white areas which are not always in perfect shape, but I include this URL below which has a bit more consistent piece of text that fits your described pattern. So previous 3 examples were done on yesterdays snapshot, this one after getting another snapshot upgrade an hour or so ago. I'm trying to grasp for how could I provide more information consulting someone on IRC in offtopic channel as I'm also reading man pages for crash and related. And as crash(8) provides an example of looking for information with pattern "function+04711" or similar, something like that is always visible on the screen with your suggested boot options. Disabling swap.encrypt does not seem to aid in genrating anything at /car/crash. But to follow with the example I see that I need to get sources and do stuff that's beyond me especially while any building on that machine takes centuries. SO I'll continue reading these man pages and try to understand how exactly to get more information on this out of the system. I could reinstall back to 6.8 unsure whether that or these snapshots use would be more useful in solving this. I'll just keep it on snapshots for now. Also I forgot to clarify that connecting external monitor when screen is blacked out results in just same black screen on that external monitor, with not responsive keyboard, ctrl_alt_esc does not do anything and I was also trying to adjust ddb.console to 1 that still did not let ctrl_alt_esc to happen from the point which can be seen in the picture. P.S. I havent really used mailing lists before and previously I've attempted to send this with an image attachment, but havent noticed it being delivered for a while now and someone on #openbsd told me it might be better to use an upload service, so I'm resending this with an URL instead of attachment. https://0x0.st/-XcC.jpg
Re: radeondrm AMD A6-3410MX APU with Radeon HD
outputs of some tools after using them with bsd.0 bsd.0.core thing that picks my eye in ps output is that in CPU column last line of radeon-crtc has a number 65554, which is larger than 65535. I'm trying to learn for how to produce something useful but my imagination in this is as limited as crash(8) examples I barely understand what I'm doing, but it is interesting, might keep me up at night. dmesg: OpenBSD 6.9-beta (GENERIC.MP) #332: Fri Feb 12 12:09:40 MST 2021 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8013475840 (7642MB) avail mem = 7755268096 (7396MB) User Kernel Config UKC> disable acpivideo 434 acpivideo* disabled UKC> exit Continuing... random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xe3c80 (26 entries) bios0: vendor Hewlett-Packard version "F.1C" date 01/25/2013 bios0: Hewlett-Packard HP Pavilion dv6 Notebook PC acpi0 at bios0: ACPI 4.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP HPET APIC MCFG ASF! BOOT SLIC WDRT SSDT SSDT acpi0: wakeup devices PB2_(S5) PB3_(S4) PB4_(S5) XPDV(S5) PB5_(S5) PB6_(S5) PB7_(S5) SPB0(S4) SPB1(S4) SPB2(S4) SPB3(S4) GEC_(S4) OHC1(S3) OHC2(S3) OHC3(S3) OHC4(S3) [...] acpitimer0 at acpi0: 3579545 Hz, 32 bits acpihpet0 at acpi0: 14318180 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD A6-3410MX APU with Radeon(tm) HD Graphics, 1598.04 MHz, 12-01-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,MWAIT,CX16,POPCNT,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,ITSC cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 1MB 64b/line 16-way L2 cache cpu0: ITLB 32 4KB entries fully associative, 16 4MB entries fully associative cpu0: DTLB 48 4KB entries fully associative, 48 4MB entries fully associative cpu0: AMD erratum 721 detected and fixed cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 199MHz cpu0: mwait min=64, max=64, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: AMD A6-3410MX APU with Radeon(tm) HD Graphics, 1597.11 MHz, 12-01-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,MWAIT,CX16,POPCNT,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,ITSC cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 1MB 64b/line 16-way L2 cache cpu1: ITLB 32 4KB entries fully associative, 16 4MB entries fully associative cpu1: DTLB 48 4KB entries fully associative, 48 4MB entries fully associative cpu1: AMD erratum 721 detected and fixed cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 2 (application processor) cpu2: AMD A6-3410MX APU with Radeon(tm) HD Graphics, 1597.11 MHz, 12-01-00 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,MWAIT,CX16,POPCNT,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,ITSC cpu2: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 1MB 64b/line 16-way L2 cache cpu2: ITLB 32 4KB entries fully associative, 16 4MB entries fully associative cpu2: DTLB 48 4KB entries fully associative, 48 4MB entries fully associative cpu2: AMD erratum 721 detected and fixed cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: AMD A6-3410MX APU with Radeon(tm) HD Graphics, 1597.11 MHz, 12-01-00 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,MWAIT,CX16,POPCNT,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,ITSC cpu3: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 1MB 64b/line 16-way L2 cache cpu3: ITLB 32 4KB entries fully associative, 16 4MB entries fully associative cpu3: DTLB 48 4KB entries fully associative, 48 4MB entries fully associative cpu3: AMD erratum 721 detected and fixed cpu3: smt 0, core 3, package 0 ioapic0 at mainbus0: apid 4 pa 0xfec0, version 21, 24 pins, remapped acpimcfg0 at acpi0 acpimcfg0: addr 0xf800, bus 0-63 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (PB2_) acpiprt2 at acpi0: bus -1 (PB3_) acpiprt3 at acpi0: bus 2 (PB4_) acpiprt4 at acpi0: bus 3 (PB5_) acpiprt5 at acpi0: bus 4 (PB6_) acpiprt6 at acpi0: bus -1 (PB7_) acpiprt7 at acpi0: bus -1 (SPB0) acpiprt8 at acpi0: bus -1 (SPB1) acpiprt9 at acpi0: bus -1 (SPB2) acpiprt10 at acpi0: bus -1 (SPB3) acpiprt11 at acpi0: bus 5 (P2P_) acpiec0 at acpi0 acpibtn0 at acpi0: PWRB acpipci0 at acpi0 PCI0: 0x 0x0011 0x0001 "HPQ6001" at acpi0 not configured acpicmos0 at acpi0 "SYN1E46" at
Re: Latest snapshot, Logitech keyboard not working.
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 \ > keyboard is not sending keypresses. i.e) Pressing the "a" key \ > does nothing. There’s an error message saying \ > “uhidev_intr: bad repid 48” To test that it's not a \ > problem with my keyboard I noticed that the function keys still work. \ > (The keyboard light). Also to test it's not just my computer I \ > plugged in a different keyboard and everything works as it should. \ > Below is my dmesg from snapshot: That's probably caused by the new uhidpp driver. A dmesg from a kernel before the upgrade where the keyboard did work would be helpful.
Re: radeondrm AMD A6-3410MX APU with Radeon HD
On Sat, Feb 13, 2021 at 03:01:21PM +0200, V S wrote: > > > If you can see a stack trace on the screen the first few lines of > > at func_one+0x... > > at func_two+0x... > > > > or a photo would help. > > > > I'm suprised the stack trace shows on the screen with db_panic 0 > > when you mentioned it previously booted to a black screen. > > > > > > > The output on the screen seems to be different each time, but repeatedly > providing pieces of similar > information and seemingly randomly some text is distorted with those white > areas which are not > always in perfect shape, but I include this URL below which has a bit more > consistent piece of > text that fits your described pattern. So previous 3 examples were done on > yesterdays snapshot, > this one after getting another snapshot upgrade an hour or so ago. > > > I'm trying to grasp for how could I provide more information consulting > someone on IRC in offtopic > channel as I'm also reading man pages for crash and related. And as crash(8) > provides an example > of looking for information with pattern "function+04711" or similar, > something like that is always visible > on the screen with your suggested boot options. > > > Disabling swap.encrypt does not seem to aid in genrating anything at > /car/crash. But to follow with the > example I see that I need to get sources and do stuff that's beyond me > especially while any building > on that machine takes centuries. SO I'll continue reading these man pages > and try to understand how > exactly to get more information on this out of the system. > > > I could reinstall back to 6.8 unsure whether that or these snapshots use > would be more useful in solving > this. I'll just keep it on snapshots for now. Also I forgot to clarify that > connecting external monitor when > screen is blacked out results in just same black screen on that external > monitor, with not responsive > keyboard, ctrl_alt_esc does not do anything and I was also trying to adjust > ddb.console to 1 > > that still did not let ctrl_alt_esc to happen from the point which can be > seen in the picture. > > > P.S. I havent really used mailing lists before and previously I've attempted > to send this with an image > attachment, but havent noticed it being delivered for a while now and > someone on #openbsd told me > it might be better to use an upload service, so I'm resending this with an > URL instead of attachment. > > https://0x0.st/-XcC.jpg The 'KASSERT(sc->sc_ecbusy == 0)' in acpiec_gpehandler() fails. Can you try disable acpivideo instead of radeondrm?
Re: radeondrm AMD A6-3410MX APU with Radeon HD
Please have in mind that I have retyped these by hand from the screen and the first example might not be acurate as I've retyped it of a blurry photo I made. But the other reboot attempts using boot> boot -d ddb> w db_panic 0 ddb> c got different messages on screen some of them might be more informant than others as the last one of these three only had very few whitebackground places at ' [s]c[]p[]i[]ew[]s[]kb[]d[]0a ' (substituting with [] for those places And I also made photos of these in case those could be more useful than this. And I'm writing these because there appears to only be a single file in /var/crash thats called minfree containing text 4096. So in the time being this all I have. I could reproduce some more of these messages assuming they're useful. I'll read these man pages related to gathering useful information in such cases for now. Unless you've got other suggestions 0)r a t ondrm0: 1280x768, 32bpp wsdisplay at radeondrm0 mux 1: consol e ( s t d, vh an le r u+l0axtfif n ), using wskbd0 acpi_thread(8002d170) at wsdisplay0: screen 1-5 added (std, vt100 emulation) acr i d t hore d r + 0 x 1 b 8 R KeSn d trace frame: 0x0, count: 253 End of stack trace. syncing disks... done dumping to dev 4,1 offset 492575 //- radeondrm0: 1280x768, 32bpp awcspdiiesp _ta py n a d l e a de o nd 0 mux 1: console (std, vt100 emulation), using wskbd0 acpi_thread(8002d170) at wsdisplay0: screen 1-5 added (std, vt100 acol_ t h r e a +0x1r a d a n d r m t : oURa g: 0x0, count: 253n End of stack trace. syncing disks... done dumping to dev 4,1 offset 492575 dump // radeondrm0: 1280x768, 32bpp wsdisplay0 at radeon drm0 mux 1: console (std, vt100 emulation), a sc p i ew s kb d 0a ndler(800028400,16,8013b000) at acpiec_gpehandler+0xff wsdisplay0: screen 1-5 added (std, vt100 emulation) radeondrm1: TURKS acpi_thread(8002d170) at acpi_thread+0x1b8 end trace frame: 0x0, count: 253 End of stack trace. syncing disks... done dumping to dev 4,1 offset 492575 dump Are you able to connect an external display to confirm that is the case? Failing that or serial it should also be possible to disable panic and get a trace via /var/crash as described in crash(8). As this likely occurs before the rc script runs you will need to use a kernel with the following diff or boot> boot -d ddb> w db_panic 0 ddb> c Index: sys/kern/subr_prf.c === RCS file: /cvs/src/sys/kern/subr_prf.c,v retrieving revision 1.102 diff -u -p -r1.102 subr_prf.c --- sys/kern/subr_prf.c 28 Nov 2020 17:53:05 - 1.102 +++ sys/kern/subr_prf.c 13 Feb 2021 06:08:57 - @@ -104,7 +104,7 @@ const char *faultstr; /* page fault stri /* * Enter ddb on panic. */ -intdb_panic = 1; +intdb_panic = 0; /* * db_console controls if we can be able to enter ddb by a special key
Re: radeondrm AMD A6-3410MX APU with Radeon HD
On Sat, Feb 13, 2021 at 10:24:42AM +0200, V S wrote: > Please have in mind that I have retyped these by hand from the screen and the > first example might > not be acurate as I've retyped it of a blurry photo I made. But the other > reboot attempts using > > boot> boot -d > ddb> w db_panic 0 > ddb> c > > got different messages on screen some of them might be more informant than > others as the last one of these three > only had very few whitebackground places at ' [s]c[]p[]i[]ew[]s[]kb[]d[]0a ' > (substituting with [] for those places > > And I also made photos of these in case those could be more useful than this. > And I'm writing these because there > appears to only be a single file in /var/crash thats called minfree > containing text 4096. > So in the time being this all I have. I could reproduce some more of these > messages assuming they're useful. I'll read > these man pages related to gathering useful information in such cases for > now. Unless you've got other suggestions If you can see a stack trace on the screen the first few lines of at func_one+0x... at func_two+0x... or a photo would help. I'm suprised the stack trace shows on the screen with db_panic 0 when you mentioned it previously booted to a black screen. > > > 0)r a t ondrm0: 1280x768, 32bpp > wsdisplay at radeondrm0 mux 1: consol e ( s t d, vh an le r u+l0axtfif n > ), using wskbd0 > acpi_thread(8002d170) at wsdisplay0: screen 1-5 added (std, vt100 > emulation) > acr i d t hore d r + 0 x 1 b 8 R > KeSn > d trace frame: 0x0, count: 253 > End of stack trace. > syncing disks... done > > dumping to dev 4,1 offset 492575 > > > > > > //- > > > radeondrm0: 1280x768, 32bpp > awcspdiiesp _ta py n a d l e a de o nd > 0 mux 1: console (std, vt100 emulation), using wskbd0 > acpi_thread(8002d170) at wsdisplay0: screen 1-5 added (std, vt100 > acol_ t h r e a > +0x1r a d > a n d r m t : oURa > g: 0x0, count: 253n > End of stack trace. > syncing disks... done > > dumping to dev 4,1 offset 492575 > dump > > > > > > > > > // > > > radeondrm0: 1280x768, 32bpp > wsdisplay0 at radeon drm0 mux 1: console (std, vt100 emulation), a sc p i ew > s kb d 0a > ndler(800028400,16,8013b000) at acpiec_gpehandler+0xff > wsdisplay0: screen 1-5 added (std, vt100 emulation) > radeondrm1: TURKS > acpi_thread(8002d170) at acpi_thread+0x1b8 > end trace frame: 0x0, count: 253 > End of stack trace. > syncing disks... done > > dumping to dev 4,1 offset 492575 > dump > > > > Are you able to connect an external display to confirm that is the case? > > > Failing that or serial it should also be possible to disable panic and > > > get a trace via /var/crash as described in crash(8). > > > > > > As this likely occurs before the rc script runs you will need to use a > > > kernel with the following diff or > > > > > > boot> boot -d > > > ddb> w db_panic 0 > > > ddb> c > > > > > > Index: sys/kern/subr_prf.c > > > === > > > RCS file: /cvs/src/sys/kern/subr_prf.c,v > > > retrieving revision 1.102 > > > diff -u -p -r1.102 subr_prf.c > > > --- sys/kern/subr_prf.c 28 Nov 2020 17:53:05 - 1.102 > > > +++ sys/kern/subr_prf.c 13 Feb 2021 06:08:57 - > > > @@ -104,7 +104,7 @@ const char *faultstr; /* page fault stri > > > /* > > >* Enter ddb on panic. > > >*/ > > > -int db_panic = 1; > > > +int db_panic = 0; > > > /* > > >* db_console controls if we can be able to enter ddb by a special key > >
Re: uhidev_clear_iface_eps: clear endpoints failed!
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 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:
> >
> > OK, so it's the same basically. I currently really have no idea why
> > the UR_CLEAR_FEATURE for EPs is working on the most of the devices,
> > but fail for some. Therefore, if you back it out from uhidev(4), does
> > the keyboard survive your switch restart again?
> >
> >
> > Index: uhidev.c
> > ===
> > RCS file: /cvs/src/sys/dev/usb/uhidev.c,v
> > retrieving revision 1.88
> > diff -u -p -u -p -r1.88 uhidev.c
> > --- uhidev.c11 Feb 2021 06:55:10 - 1.88
> > +++ uhidev.c11 Feb 2021 15:20:37 -
> > @@ -518,9 +518,6 @@ uhidev_open(struct uhidev *scd)
> > DPRINTF(("uhidev_open: isize=%d, ep=0x%02x\n", sc->sc_isize,
> > sc->sc_iep_addr));
> >
> > - /* Clear device endpoint toggle. */
> > - uhidev_clear_iface_eps(sc, sc->sc_iface);
> > -
> > err = usbd_open_pipe_intr(sc->sc_iface, sc->sc_iep_addr,
> > USBD_SHORT_XFER_OK, >sc_ipipe, sc, sc->sc_ibuf,
> > sc->sc_isize, uhidev_intr, USBD_DEFAULT_INTERVAL);
> > @@ -530,8 +527,6 @@ uhidev_open(struct uhidev *scd)
> > error = EIO;
> > goto out1;
> > }
> > - /* Clear HC endpoint toggle. */
> > - usbd_clear_endpoint_toggle(sc->sc_ipipe);
> >
> > DPRINTF(("uhidev_open: sc->sc_ipipe=%p\n", sc->sc_ipipe));
> >
> > @@ -557,8 +552,6 @@ uhidev_open(struct uhidev *scd)
> > error = EIO;
> > goto out2;
> > }
> > - /* Clear HC endpoint toggle. */
> > - usbd_clear_endpoint_toggle(sc->sc_opipe);
> >
> > DPRINTF(("uhidev_open: sc->sc_opipe=%p\n", sc->sc_opipe));
> >
> >
>
> I worked out this issue with a USB-Hub between the KVM-Switch and the
> devices (webcam, keyboard and mouse). dmesg (without the diff above):
You lost me :-)
You're saying that you have plugged an USB hub between the KVM switch
and your devices, and now you don't face the issue anymore, meaning you
can reset the switch and all of the devices attach back fine?
