NetBSD Problem Report #52070
From www@NetBSD.org Tue Mar 14 10:22:01 2017
Return-Path: <www@NetBSD.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client CN "mail.netbsd.org", Issuer "Postmaster NetBSD.org" (verified OK))
by mollari.NetBSD.org (Postfix) with ESMTPS id 0F82D7A16A
for <gnats-bugs@gnats.NetBSD.org>; Tue, 14 Mar 2017 10:22:01 +0000 (UTC)
Message-Id: <20170314102158.DECE67A270@mollari.NetBSD.org>
Date: Tue, 14 Mar 2017 10:21:58 +0000 (UTC)
From: babafou+netbsd@babafou.eu.org
Reply-To: babafou+netbsd@babafou.eu.org
To: gnats-bugs@NetBSD.org
Subject: Keyboard freeze after using touchpad
X-Send-Pr-Version: www-1.0
>Number: 52070
>Category: kern
>Synopsis: Keyboard freeze after using touchpad
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: martin
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue Mar 14 10:25:00 +0000 2017
>Last-Modified: Sun Jan 07 13:10:01 +0000 2024
>Originator: Marc Baudoin
>Release: 7.99.65
>Organization:
>Environment:
NetBSD test.babafou.eu.org 7.99.65 NetBSD 7.99.65 (GENERIC.201703132330Z) amd64
>Description:
On this laptop:
http://www.clevo.com.tw/clevo_prodetail.asp?id=995&lang=en
The keyboard works fine after boot but stops working as soon as the touchpad if used.
The touchpad is not detected by the kernel.
Full dmesg below:
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017
The NetBSD Foundation, Inc. All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
NetBSD 7.99.65 (GENERIC.201703132330Z)
total memory = 16143 MB
avail memory = 15653 MB
cpu_rng: RDSEED
rnd: seeded with 128 bits
timecounter: Timecounters tick every 10.000 msec
Kernelized RAIDframe activated
running cgd selftest aes-xts-256 aes-xts-512 done
timecounter: Timecounter "i8254" frequency 1193182 Hz quality 100
Notebook N750BU (Not Applicable )
mainbus0 (root)
ACPI: RSDP 0x00000000000F05B0 000024 (v02 ALASKA)
ACPI: XSDT 0x000000007F86C0A0 0000C4 (v01 ALASKA A M I 01072009 AMI 00010013)
ACPI: FACP 0x000000007F887640 000114 (v06 ALASKA A M I 01072009 AMI 00010013)
ACPI: DSDT 0x000000007F86C200 01B43D (v02 ALASKA A M I 01072009 INTL 20160422)
ACPI: FACS 0x000000007FBE6C40 000040
ACPI: APIC 0x000000007F887758 000084 (v03 ALASKA A M I 01072009 AMI 00010013)
ACPI: FPDT 0x000000007F8877E0 000044 (v01 ALASKA A M I 01072009 AMI 00010013)
ACPI: MCFG 0x000000007F887828 00003C (v01 ALASKA A M I 01072009 MSFT 00000097)
ACPI: FIDT 0x000000007F887868 00009C (v01 ALASKA A M I 01072009 AMI 00010013)
ACPI: SSDT 0x000000007F887908 003295 (v02 SaSsdt SaSsdt 00003000 INTL 20160422)
ACPI: HPET 0x000000007F88ABA0 000038 (v01 INTEL KBL-ULT 00000001 MSFT 0000005F)
ACPI: SSDT 0x000000007F88ABD8 000024 (v02 INTEL xh_OEMBD 00000000 INTL 20160422)
ACPI: UEFI 0x000000007F88AC00 000042 (v01 INTEL EDK2 00000002 01000013)
ACPI: SSDT 0x000000007F88AC48 000EDE (v02 CpuRef CpuSsdt 00003000 INTL 20160422)
ACPI: SSDT 0x000000007F88BB28 0003E3 (v02 PmRef Cpu0Tst 00003000 INTL 20160422)
ACPI: SSDT 0x000000007F88BF10 000471 (v02 PmRef ApTst 00003000 INTL 20160422)
ACPI: LPIT 0x000000007F88C388 000094 (v01 INTEL KBL-ULT 00000000 MSFT 0000005F)
ACPI: WSMT 0x000000007F88C420 000028 (v01 INTEL KBL-ULT 00000000 MSFT 0000005F)
ACPI: SSDT 0x000000007F88C448 00029F (v02 INTEL sensrhub 00000000 INTL 20160422)
ACPI: SSDT 0x000000007F88C6E8 003002 (v02 INTEL PtidDevc 00001000 INTL 20160422)
ACPI: DBGP 0x000000007F88F6F0 000034 (v01 INTEL 00000002 MSFT 0000005F)
ACPI: DBG2 0x000000007F88F728 000054 (v00 INTEL 00000002 MSFT 0000005F)
ACPI: DMAR 0x000000007F88F780 0000A8 (v01 INTEL KBL 00000001 INTL 00000001)
ACPI: ASF! 0x000000007F88F828 0000A0 (v32 INTEL HCG 00000001 TFSM 000F4240)
ACPI: Executed 21 blocks of module-level executable AML code
ACPI: Executed 1 blocks of module-level executable AML code
ACPI: Executed 1 blocks of module-level executable AML code
ACPI: Executed 1 blocks of module-level executable AML code
ACPI: Executed 1 blocks of module-level executable AML code
ACPI: Executed 1 blocks of module-level executable AML code
ACPI: Executed 1 blocks of module-level executable AML code
ACPI: 8 ACPI AML tables successfully acquired and loaded
ioapic0 at mainbus0 apid 2: pa 0xfec00000, version 0x20, 120 pins
cpu0 at mainbus0 apid 0
cpu0: Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz, id 0x806e9
cpu1 at mainbus0 apid 2
cpu1: Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz, id 0x806e9
cpu2 at mainbus0 apid 1
cpu2: Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz, id 0x806e9
cpu3 at mainbus0 apid 3
cpu3: Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz, id 0x806e9
acpi0 at mainbus0: Intel ACPICA 20170119
acpi0: X/RSDT: OemId <ALASKA, A M I ,01072009>, AslId <AMI ,00010013>
acpi0: invalid PCI address for D02E
acpi0: MCFG: segment 0, bus 0-255, address 0x00000000e0000000
ACPI: Dynamic OEM Table Load:
ACPI: SSDT 0xFFFFFE811CD60010 0003FF (v02 PmRef Cpu0Cst 00003001 INTL 20160422)
ACPI: Executed 1 blocks of module-level executable AML code
ACPI: Dynamic OEM Table Load:
ACPI: SSDT 0xFFFFFE811CDC7810 0006F6 (v02 PmRef Cpu0Ist 00003000 INTL 20160422)
ACPI: Executed 1 blocks of module-level executable AML code
ACPI: Dynamic OEM Table Load:
ACPI: SSDT 0xFFFFFE811CDC7010 00065C (v02 PmRef ApIst 00003000 INTL 20160422)
ACPI: Executed 1 blocks of module-level executable AML code
ACPI: Dynamic OEM Table Load:
ACPI: SSDT 0xFFFFFE846E316710 00018A (v02 PmRef ApCst 00003000 INTL 20160422)
ACPI: Executed 1 blocks of module-level executable AML code
acpi0: SCI interrupting at int 9
timecounter: Timecounter "ACPI-Fast" frequency 3579545 Hz quality 1000
hpet0 at acpi0: high precision event timer (mem 0xfed00000-0xfed00400)
timecounter: Timecounter "hpet0" frequency 24000000 Hz quality 2000
acpiec0 at acpi0 (EC, PNP0C09): io 0x62,0x66
acpivga0 at acpi0 (GFX0): ACPI Display Adapter
acpiout0 at acpivga0 (DD01, 0x0100): ACPI Display Output Device
acpiout1 at acpivga0 (DD02, 0x0002): ACPI Display Output Device
acpiout2 at acpivga0 (DD03, 0x0300): ACPI Display Output Device
acpiout3 at acpivga0 (DD04, 0x0301): ACPI Display Output Device
acpiout4 at acpivga0 (DD05, 0x0302): ACPI Display Output Device
acpiout5 at acpivga0 (DD06, 0x0303): ACPI Display Output Device
acpiout6 at acpivga0 (DD07, 0x0304): ACPI Display Output Device
acpiout7 at acpivga0 (DD08, 0x0305): ACPI Display Output Device
acpiout8 at acpivga0 (DD09, 0x0009): ACPI Display Output Device
acpiout9 at acpivga0 (DD0A, 0x000a): ACPI Display Output Device
acpiout10 at acpivga0 (DD0B, 0x000b): ACPI Display Output Device
acpiout11 at acpivga0 (DD0C, 0x000c): ACPI Display Output Device
acpiout12 at acpivga0 (DD0D, 0x000d): ACPI Display Output Device
acpiout13 at acpivga0 (DD0E, 0x000e): ACPI Display Output Device
acpiout14 at acpivga0 (DD0F, 0x000f): ACPI Display Output Device
acpiout15 at acpivga0 (DD1F, 0x0400): ACPI Display Output Device
acpiout15: brightness levels: [0-100]
acpiout16 at acpivga0 (SKC0, 0xca00): ACPI Display Output Device
acpivga0: unknown output device acpiout0
acpivga0: unknown output device acpiout1
acpivga0: unknown output device acpiout2
acpivga0: unknown output device acpiout3
acpivga0: unknown output device acpiout4
acpivga0: unknown output device acpiout5
acpivga0: unknown output device acpiout6
acpivga0: unknown output device acpiout7
acpivga0: unknown output device acpiout8
acpivga0: unknown output device acpiout9
acpivga0: unknown output device acpiout10
acpivga0: unknown output device acpiout11
acpivga0: unknown output device acpiout12
acpivga0: unknown output device acpiout13
acpivga0: unknown output device acpiout14
acpivga0: unknown output device acpiout16
acpivga0: connected output devices:
acpivga0: 0x0400 (acpiout15): Unknown Output Device, head 0
FWHD (INT0800) at acpi0 not configured
LDRC (PNP0C02) at acpi0 not configured
attimer1 at acpi0 (TIMR, PNP0100): io 0x40-0x43,0x50-0x53 irq 0
CWDT (INT3F0D) at acpi0 not configured
pckbc1 at acpi0 (PS2K, MSFT0001) (kbd port): io 0x60,0x64 irq 1
pckbc2 at acpi0 (SYNM, SYN1222-3) (aux port): irq 12
PDRC (PNP0C02) at acpi0 not configured
IOTR (PNP0C02) at acpi0 not configured
EPC (INT0E0C) at acpi0 not configured
PEPD (INT33A1) at acpi0 not configured
CAI (PNPC000) at acpi0 not configured
acpibut0 at acpi0 (PWRB, PNP0C0C): ACPI Power Button
acpibut1 at acpi0 (SLPB, PNP0C0E): ACPI Sleep Button
acpilid0 at acpi0 (LID0, PNP0C0D): ACPI Lid Switch
acpiacad0 at acpi0 (AC, ACPI0003): ACPI AC Adapter
acpibat0 at acpi0 (BAT0, PNP0C0A-0): ACPI Battery
acpibat0: Notebook LION rechargeable battery
acpibat0: granularity: low->warn 0.064 Ah, warn->full 0.064 Ah
acpiwmi0 at acpi0 (WMI, PNP0C14-0): ACPI WMI Interface
acpiwmibus at acpiwmi0 not configured
PTID (INT340E) at acpi0 not configured
acpitz0 at acpi0 (TZ0)
acpitz0: levels: critical 120.0 C, passive cooling
ACPI: Enabled 4 GPEs in block 00 to 7F
pckbd0 at pckbc1 (kbd slot)
pckbc1: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard
pci0 at mainbus0 bus 0: configuration mode 1
pci0: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok
pchb0 at pci0 dev 0 function 0: vendor 8086 product 5904 (rev. 0x02)
vga0 at pci0 dev 2 function 0: vendor 8086 product 5916 (rev. 0x02)
wsdisplay0 at vga0 kbdmux 1: console (80x25, vt100 emulation), using wskbd0
wsmux1: connecting to wsdisplay0
drm at vga0 not configured
vendor 8086 product 1911 (miscellaneous system) at pci0 dev 8 function 0 not configured
xhci0 at pci0 dev 20 function 0: vendor 8086 product 9d2f (rev. 0x21)
xhci0: interrupting at msi0 vec 0
xhci0: xHCI version 1.0
usb0 at xhci0: USB revision 3.0
usb1 at xhci0: USB revision 2.0
vendor 8086 product 9d31 (miscellaneous DASP, revision 0x21) at pci0 dev 20 function 2 not configured
vendor 8086 product 9d3a (miscellaneous communications, revision 0x21) at pci0 dev 22 function 0 not configured
ahcisata0 at pci0 dev 23 function 0: vendor 8086 product 9d03 (rev. 0x21)
ahcisata0: interrupting at ioapic0 pin 16
ahcisata0: 64-bit DMA
ahcisata0: AHCI revision 1.31, 3 ports, 32 slots, CAP 0xc734ff02<PSC,SSC,PMD,SAM,ISS=0x3=Gen3,SCLO,SAL,SALP,SNCQ,S64A>
atabus0 at ahcisata0 channel 0
atabus1 at ahcisata0 channel 1
atabus2 at ahcisata0 channel 2
ppb0 at pci0 dev 28 function 0: vendor 8086 product 9d10 (rev. 0xf1)
ppb0: PCI Express capability version 2 <Root Port of PCI-E Root Complex> x2 @ 8.0GT/s
pci1 at ppb0 bus 1
pci1: i/o space, memory space enabled, rd/line, wr/inv ok
ppb1 at pci0 dev 28 function 3: vendor 8086 product 9d13 (rev. 0xf1)
ppb1: PCI Express capability version 2 <Root Port of PCI-E Root Complex> x1 @ 8.0GT/s
ppb1: link is x1 @ 2.5GT/s
pci2 at ppb1 bus 2
pci2: i/o space, memory space enabled, rd/line, wr/inv ok
rtsx0 at pci2 dev 0 function 0: vendor 10ec product 5287 (rev. 0x01)
rtsx0: interrupting at msi1 vec 0
sdmmc0 at rtsx0
re0 at pci2 dev 0 function 1: RealTek 8168/8111 PCIe Gigabit Ethernet (rev. 0x12)
re0: interrupting at msi2 vec 0
re0: Ethernet address 80:fa:5b:3e:41:20
re0: using 256 tx descriptors
rgephy0 at re0 phy 7: RTL8251 1000BASE-T media interface, rev. 0
rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT-FDX, auto
ppb2 at pci0 dev 28 function 4: vendor 8086 product 9d14 (rev. 0xf1)
ppb2: PCI Express capability version 2 <Root Port of PCI-E Root Complex> x1 @ 8.0GT/s
ppb2: link is x1 @ 2.5GT/s
pci3 at ppb2 bus 3
pci3: i/o space, memory space enabled, rd/line, wr/inv ok
iwm0 at pci3 dev 0 function 0: vendor 8086 product 24f3 (rev. 0x3a)
iwm0: interrupting at msi3 vec 0
pcib0 at pci0 dev 31 function 0: vendor 8086 product 9d4e (rev. 0x21)
vendor 8086 product 9d21 (miscellaneous memory, revision 0x21) at pci0 dev 31 function 2 not configured
hdaudio0 at pci0 dev 31 function 3: HD Audio Controller
hdaudio0: interrupting at msi4 vec 0
hdafg0 at hdaudio0: vendor 10ec product 0269
hdafg0: DAC00 2ch: HP Out [Jack]
hdafg0: DAC01 2ch: Speaker [Built-In]
hdafg0: ADC02 2ch: Mic In [Built-In]
hdafg0: ADC03 2ch: Mic In [Jack]
hdafg0: 2ch/2ch 32000Hz 44100Hz 48000Hz 88200Hz 96000Hz 192000Hz PCM16 PCM20 PCM24 AC3
audio0 at hdafg0: full duplex, playback, capture, mmap, independent
hdafg0: Virtual format configured - Format SLINEAR, precision 16, channels 2, frequency 48000
spkr0 at audio0: PC Speaker (synthesized)
hdafg1 at hdaudio0: vendor 8086 product 280b
hdafg1: DP00 8ch: Digital Out [Jack]
hdafg1: 8ch/0ch 48000Hz PCM16*
vendor 8086 product 9d23 (SMBus serial bus, revision 0x21) at pci0 dev 31 function 4 not configured
isa0 at pcib0
tpm0 at isa0 iomem 0xfed40000-0xfed44fff irq 7: device 0x001a15d1 rev 0x10
pcppi0 at isa0 port 0x61
spkr1 at pcppi0: PC Speaker
midi0 at pcppi0: PC speaker
sysbeep0 at pcppi0
attimer1: attached to pcppi0
acpicpu0 at cpu0: ACPI CPU
acpicpu0: C1: FFH, lat 1 us, pow 1000 mW
acpicpu0: C2: FFH, lat 151 us, pow 200 mW
acpicpu0: C3: FFH, lat 1034 us, pow 200 mW
acpicpu0: P0: FFH, lat 10 us, pow 15000 mW, 2701 MHz, turbo boost
acpicpu0: P1: FFH, lat 10 us, pow 13633 mW, 2700 MHz
acpicpu0: P2: FFH, lat 10 us, pow 12897 mW, 2600 MHz
acpicpu0: P3: FFH, lat 10 us, pow 12318 mW, 2500 MHz
acpicpu0: P4: FFH, lat 10 us, pow 11608 mW, 2400 MHz
acpicpu0: P5: FFH, lat 10 us, pow 10372 mW, 2200 MHz
acpicpu0: P6: FFH, lat 10 us, pow 9182 mW, 2000 MHz
acpicpu0: P7: FFH, lat 10 us, pow 8173 mW, 1800 MHz
acpicpu0: P8: FFH, lat 10 us, pow 7075 mW, 1600 MHz
acpicpu0: P9: FFH, lat 10 us, pow 6480 mW, 1500 MHz
acpicpu0: P10: FFH, lat 10 us, pow 5453 mW, 1300 MHz
acpicpu0: P11: FFH, lat 10 us, pow 4472 mW, 1100 MHz
acpicpu0: P12: FFH, lat 10 us, pow 3140 mW, 800 MHz
acpicpu0: P13: FFH, lat 10 us, pow 2756 mW, 700 MHz
acpicpu0: P14: FFH, lat 10 us, pow 2267 mW, 600 MHz
acpicpu0: P15: FFH, lat 10 us, pow 1435 mW, 400 MHz
acpicpu0: T0: FFH, lat 1 us, pow 1435 mW, 100 %
acpicpu0: T1: FFH, lat 1 us, pow 1345 mW, 94 %
acpicpu0: T2: FFH, lat 1 us, pow 1255 mW, 88 %
acpicpu0: T3: FFH, lat 1 us, pow 1165 mW, 82 %
acpicpu0: T4: FFH, lat 1 us, pow 1076 mW, 75 %
acpicpu0: T5: FFH, lat 1 us, pow 986 mW, 69 %
acpicpu0: T6: FFH, lat 1 us, pow 896 mW, 63 %
acpicpu0: T7: FFH, lat 1 us, pow 807 mW, 57 %
acpicpu0: T8: FFH, lat 1 us, pow 717 mW, 50 %
acpicpu0: T9: FFH, lat 1 us, pow 627 mW, 44 %
acpicpu0: T10: FFH, lat 1 us, pow 538 mW, 38 %
acpicpu0: T11: FFH, lat 1 us, pow 448 mW, 32 %
acpicpu0: T12: FFH, lat 1 us, pow 358 mW, 25 %
acpicpu0: T13: FFH, lat 1 us, pow 269 mW, 19 %
acpicpu0: T14: FFH, lat 1 us, pow 179 mW, 13 %
acpicpu0: T15: FFH, lat 1 us, pow 89 mW, 7 %
coretemp0 at cpu0: thermal sensor, 1 C resolution, Tjmax=100
acpicpu1 at cpu1: ACPI CPU
coretemp1 at cpu1: thermal sensor, 1 C resolution, Tjmax=100
acpicpu2 at cpu2: ACPI CPU
acpicpu3 at cpu3: ACPI CPU
timecounter: Timecounter "clockinterrupt" frequency 100 Hz quality 0
ERROR: 109572114 cycle TSC drift observed
acpiacad0: AC adapter online.
uhub0 at usb0: vendor 8086 xHCI Root Hub, class 9/0, rev 1.00/1.00, addr 0
uhub0: 6 ports with 6 removable, self powered
uhub1 at usb1: vendor 8086 xHCI Root Hub, class 9/0, rev 2.00/1.00, addr 0
uhub1: 12 ports with 12 removable, self powered
IPsec: Initialized Security Association Processing.
ahcisata0 port 2: device present, speed: 6.0Gb/s
ahcisata0 port 1: device present, speed: 1.5Gb/s
ahcisata0 port 0: device present, speed: 6.0Gb/s
wd0 at atabus0 drive 0
wd0: <ST1000LX015-1U7172>
wd0: drive supports 16-sector PIO transfers, LBA48 addressing
wd0: 931 GB, 1938021 cyl, 16 head, 63 sec, 512 bytes/sect x 1953525168 sectors
wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133)
wd0(ahcisata0:0:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133) (using DMA)
atapibus0 at atabus1: 1 targets
cd0 at atapibus0 drive 0: <Slimtype DVD A DU8A6SH, 415635502142, DP57> cdrom removable
cd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133)
cd0(ahcisata0:1:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133) (using DMA)
wd1 at atabus2 drive 0
wd1: <WDC WDS120G1G0B-00RC30>
wd1: drive supports 1-sector PIO transfers, LBA48 addressing
wd1: 111 GB, 232581 cyl, 16 head, 63 sec, 512 bytes/sect x 234441648 sectors
wd1: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133)
wd1(ahcisata0:2:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133) (using DMA)
rum0 at uhub1 port 3
rum0: Cisco-Linksys Compact Wireless-G USB Adapter, rev 2.00/0.01, addr 1
rum0: MAC/BBP RT2573 (rev 0x2573a), RF RT2528, address 00:22:6b:a9:53:c3
rum0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
rum0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
ubt0 at uhub1 port 5
ubt0: vendor 8087 product 0a2b, rev 2.00/0.01, addr 2
sdmmc0: sdmmc_mem_enable failed with error 60
sdmmc0: couldn't enable card: 60
uvideo0 at uhub1 port 6 configuration 1 interface 0: Bison BisonCam,NB Pro, rev 2.00/6.02, addr 3
video0 at uvideo0: Bison BisonCam,NB Pro, rev 2.00/6.02, addr 3
uhidev0 at uhub1 port 8 configuration 1 interface 0
uhidev0: Logitech USB Receiver, rev 2.00/22.00, addr 4, iclass 3/1
ums0 at uhidev0: 16 buttons, W and Z dirs
wsmouse0 at ums0 mux 0
uhidev1 at uhub1 port 8 configuration 1 interface 1
uhidev1: Logitech USB Receiver, rev 2.00/22.00, addr 4, iclass 3/0
uhidev1: 17 report ids
uhid0 at uhidev1 reportid 3: input=4, output=0, feature=0
uhid1 at uhidev1 reportid 16: input=6, output=6, feature=0
uhid2 at uhidev1 reportid 17: input=19, output=19, feature=0
pad0: outputs: 44100Hz, 16-bit, stereo
audio1 at pad0: half duplex, playback, capture
pad0: Virtual format configured - Format SLINEAR, precision 16, channels 2, frequency 44100
spkr2 at audio1: PC Speaker (synthesized)
WARNING: 19 errors while detecting hardware; check system log.
boot device: wd1
root on wd1a dumps on wd1b
root file system type: ffs
kern.module.path=/stand/amd64/7.99.65/modules
iwm0: hw rev 0x200, fw ver 16.242414.0, address 44:85:00:57:5c:47
iwm0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
iwm0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
iwm0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
sdmmc0: sdmmc_mem_enable failed with error 60
sdmmc0: couldn't enable card: 60
wsdisplay0: screen 1 added (80x25, vt100 emulation)
wsdisplay0: screen 2 added (80x25, vt100 emulation)
wsdisplay0: screen 3 added (80x25, vt100 emulation)
wsdisplay0: screen 4 added (80x25, vt100 emulation)
>How-To-Repeat:
Just touch the touchpad, the keyboard is gone. But it can work properly for hours if the touchpad is not used.
>Fix:
>Release-Note:
>Audit-Trail:
From: Robert Elz <kre@munnari.OZ.AU>
To: gnats-bugs@NetBSD.org
Cc:
Subject: Re: kern/52070: Keyboard freeze after using touchpad
Date: Tue, 14 Mar 2017 19:10:26 +0700
Date: Tue, 14 Mar 2017 10:25:00 +0000 (UTC)
From: babafou+netbsd@babafou.eu.org
Message-ID: <20170314102500.CE9687A2B5@mollari.NetBSD.org>
| http://www.clevo.com.tw/clevo_prodetail.asp?id=995&lang=en
|
| The keyboard works fine after boot but stops working as soon
| as the touchpad if used.
My guess is that this is related to ...
| pckbc1 at acpi0 (PS2K, MSFT0001) (kbd port): io 0x60,0x64 irq 1
| pckbc2 at acpi0 (SYNM, SYN1222-3) (aux port): irq 12
The second of those is (I am assuming) really the touchpad, but it is
being attached as a keyboard controller.
When it does something (when you touch it) I would assume the keyboard
driver attempts to communicate, and not being a keyboard, the touchpad
fails to react as expected. That the real keyboard, and the touchpad
are both ports on the same controller is most probably what stops the
keyboard from working any more - the hardware is waiting for a keyboard
type response from a touchpad.
Note this is all guesswork, and I have no idea at all how to stop the
touchpad from being configured as a keyboard controller, nor why that
is happening in the first place. But perhaps someone who understands
the way all this works inside the NetBSD kernel can figure out something
that could be done to stop it, so we can tell if this really is the root
cause of the problem.
kre
From: Martin Husemann <martin@duskware.de>
To: gnats-bugs@NetBSD.org
Cc: kern-bug-people@netbsd.org, gnats-admin@netbsd.org,
netbsd-bugs@netbsd.org, babafou+netbsd@babafou.eu.org
Subject: Re: kern/52070: Keyboard freeze after using touchpad
Date: Tue, 14 Mar 2017 13:41:42 +0100
On Tue, Mar 14, 2017 at 12:15:00PM +0000, Robert Elz wrote:
> My guess is that this is related to ...
>
> | pckbc1 at acpi0 (PS2K, MSFT0001) (kbd port): io 0x60,0x64 irq 1
> | pckbc2 at acpi0 (SYNM, SYN1222-3) (aux port): irq 12
Actually this is "normal" - there is one device (the keyboard controller)
but ACPI has two nodes for it. So we attach both as pckbc and then
switch the device behind it based on the port (kbd/aux).
So the question is why pms does not attach in your case, like:
pms0 at pckbc1 (aux slot)
pms0: Synaptics touchpad version 7.2
pms0: Extended W mode, Up/down buttons, Palm detect, Multi-finger Report
pckbc1: using irq 12 for aux slot
wsmouse0 at pms0 mux 0
I'd suggest to build a kernel with
options PMSDEBUG
and see if that outputs anything helpfull.
Martin
From: Manuel Bouyer <bouyer@antioche.eu.org>
To: gnats-bugs@NetBSD.org
Cc: kern-bug-people@netbsd.org, gnats-admin@netbsd.org, netbsd-bugs@netbsd.org,
babafou+netbsd@babafou.eu.org
Subject: Re: kern/52070: Keyboard freeze after using touchpad
Date: Tue, 14 Mar 2017 13:46:10 +0100
On Tue, Mar 14, 2017 at 12:15:00PM +0000, Robert Elz wrote:
> The following reply was made to PR kern/52070; it has been noted by GNATS.
>
> From: Robert Elz <kre@munnari.OZ.AU>
> To: gnats-bugs@NetBSD.org
> Cc:
> Subject: Re: kern/52070: Keyboard freeze after using touchpad
> Date: Tue, 14 Mar 2017 19:10:26 +0700
>
> Date: Tue, 14 Mar 2017 10:25:00 +0000 (UTC)
> From: babafou+netbsd@babafou.eu.org
> Message-ID: <20170314102500.CE9687A2B5@mollari.NetBSD.org>
>
> | http://www.clevo.com.tw/clevo_prodetail.asp?id=995&lang=en
> |
> | The keyboard works fine after boot but stops working as soon
> | as the touchpad if used.
>
> My guess is that this is related to ...
>
> | pckbc1 at acpi0 (PS2K, MSFT0001) (kbd port): io 0x60,0x64 irq 1
> | pckbc2 at acpi0 (SYNM, SYN1222-3) (aux port): irq 12
>
> The second of those is (I am assuming) really the touchpad, but it is
> being attached as a keyboard controller.
I think this is expected: this is really a PS/2 controller, and you can
connect either a keyboard or a mouse here.
I would then expect a pckbd to attach to pckbc1, and a pms to attach at
pckbc2. For some reason pms thinks there's nothing here.
As this is really a synaptics touchpad and not a plain PS/2 mouse
I guess the command set is a bit different. We have some synaptics
touchpad support, but maybe a newer hardware uses a different protocol.
--
Manuel Bouyer <bouyer@antioche.eu.org>
NetBSD: 26 ans d'experience feront toujours la difference
--
From: coypu@SDF.ORG
To: gnats-bugs@netbsd.org
Cc:
Subject: Re: kern/52070: Keyboard freeze after using touchpad
Date: Tue, 14 Mar 2017 12:48:56 +0000
For the record I had the same bug but only after resume (xsrc/51390),
but I haven't been able to get anywhere with it.
I think that I might be relying on BIOS PS/2 emulation for it to work
before resume.
Other ideas I had and people suggested:
- Something about disabling SMM and looking at i8kutils for my specific
(dell) hardware
- It might be some low power mode
- synaptics touchpads might default to a mode we don't support. for
synaptics docs:
http://blog.amigas.ru/wp-content/uploads/2014/03/touchpad_RevB.pdf
I might be relying on PS/2 emulation by BIOS for it to work initially.
It tends to be optional. perhaps you can enable it?
The furthest I got is 'making touchpad never work at all', which is
still an improvement.
From: Marc Baudoin <babafou@babafou.eu.org>
To: Martin Husemann <martin@duskware.de>
Cc: gnats-bugs@NetBSD.org, kern-bug-people@netbsd.org,
gnats-admin@netbsd.org, netbsd-bugs@netbsd.org,
babafou+netbsd@babafou.eu.org
Subject: Re: kern/52070: Keyboard freeze after using touchpad
Date: Tue, 14 Mar 2017 13:53:03 +0100
Martin Husemann <martin@duskware.de> écrit :
> On Tue, Mar 14, 2017 at 12:15:00PM +0000, Robert Elz wrote:
> > My guess is that this is related to ...
> >
> > | pckbc1 at acpi0 (PS2K, MSFT0001) (kbd port): io 0x60,0x64 irq 1
> > | pckbc2 at acpi0 (SYNM, SYN1222-3) (aux port): irq 12
>
> Actually this is "normal" - there is one device (the keyboard controller)
> but ACPI has two nodes for it. So we attach both as pckbc and then
> switch the device behind it based on the port (kbd/aux).
>
> So the question is why pms does not attach in your case, like:
>
> pms0 at pckbc1 (aux slot)
> pms0: Synaptics touchpad version 7.2
> pms0: Extended W mode, Up/down buttons, Palm detect, Multi-finger Report
> pckbc1: using irq 12 for aux slot
> wsmouse0 at pms0 mux 0
>
>
> I'd suggest to build a kernel with
>
> options PMSDEBUG
>
> and see if that outputs anything helpfull.
Already tried that a few weeks ago:
http://mail-index.netbsd.org/current-users/2017/02/21/msg031176.html
http://mail-index.netbsd.org/current-users/2017/02/21/msg031177.html
Nothing really interesting :-(
From: Martin Husemann <martin@duskware.de>
To: Marc Baudoin <babafou@babafou.eu.org>
Cc: gnats-bugs@NetBSD.org
Subject: Re: kern/52070: Keyboard freeze after using touchpad
Date: Tue, 14 Mar 2017 14:25:43 +0100
Just to see if this gets us any further, could you try the patch below
(and PMSDEBUG, ...)
Martin
Index: pckbc.c
===================================================================
RCS file: /cvsroot/src/sys/dev/ic/pckbc.c,v
retrieving revision 1.59
diff -u -p -r1.59 pckbc.c
--- pckbc.c 14 Jul 2016 10:19:06 -0000 1.59
+++ pckbc.c 14 Mar 2017 13:24:22 -0000
@@ -278,13 +278,13 @@ pckbc_attach(struct pckbc_softc *sc)
{
struct pckbc_internal *t;
bus_space_tag_t iot;
- bus_space_handle_t ioh_d, ioh_c;
- int res;
+ bus_space_handle_t /* ioh_d, */ ioh_c;
+ // int res;
u_char cmdbits = 0;
t = sc->id;
iot = t->t_iot;
- ioh_d = t->t_ioh_d;
+ // ioh_d = t->t_ioh_d;
ioh_c = t->t_ioh_c;
t->t_pt = pckbport_attach(t, &pckbc_ops);
@@ -348,6 +348,8 @@ pckbc_attach(struct pckbc_softc *sc)
goto nomouse;
}
t->t_haveaux = 1;
+
+#if 0
bus_space_write_1(iot, ioh_d, 0, 0x5a); /* a random value */
res = pckbc_poll_data1(t, PCKBC_AUX_SLOT);
@@ -381,6 +383,7 @@ pckbc_attach(struct pckbc_softc *sc)
#endif
t->t_haveaux = 0;
}
+#endif
nomouse:
/* enable needed interrupts */
From: Marc Baudoin <babafou@babafou.eu.org>
To: Martin Husemann <martin@duskware.de>
Cc: gnats-bugs@NetBSD.org
Subject: Re: kern/52070: Keyboard freeze after using touchpad
Date: Tue, 14 Mar 2017 15:13:31 +0100
Martin Husemann <martin@duskware.de> écrit :
> Just to see if this gets us any further, could you try the patch below
> (and PMSDEBUG, ...)
The keyboard still freezes. Nothing new in the dmesg output.
From: Robert Elz <kre@munnari.OZ.AU>
To: gnats-bugs@NetBSD.org
Cc:
Subject: Re: kern/52070: Keyboard freeze after using touchpad
Date: Tue, 14 Mar 2017 21:28:52 +0700
Date: Tue, 14 Mar 2017 13:30:01 +0000 (UTC)
From: Martin Husemann <martin@duskware.de>
Message-ID: <20170314133001.98DA57A28E@mollari.NetBSD.org>
| Just to see if this gets us any further, could you try the patch below
| (and PMSDEBUG, ...)
And the other debugs as well (PCKBCDEBUG etc).
But I don't think the patch as is will help, it appears to #if 0
away the:
if (pckbc_attach_slot(sc, PCKBC_AUX_SLOT))
cmdbits |= KC8_MENABLE;
and if that doesn't happen nothing is likely improve things.
So, Marc, try Martin's patch, but also try inserting
#endif just before the two lines I included above, and #if 0
immediately after (so those two lines effectively get excluded
from the code that Martin suggests you try deleting.)
kre
|
| Martin
|
| Index: pckbc.c
| ===================================================================
| RCS file: /cvsroot/src/sys/dev/ic/pckbc.c,v
| retrieving revision 1.59
| diff -u -p -r1.59 pckbc.c
| --- pckbc.c 14 Jul 2016 10:19:06 -0000 1.59
| +++ pckbc.c 14 Mar 2017 13:24:22 -0000
| @@ -278,13 +278,13 @@ pckbc_attach(struct pckbc_softc *sc)
| {
| struct pckbc_internal *t;
| bus_space_tag_t iot;
| - bus_space_handle_t ioh_d, ioh_c;
| - int res;
| + bus_space_handle_t /* ioh_d, */ ioh_c;
| + // int res;
| u_char cmdbits = 0;
|
| t = sc->id;
| iot = t->t_iot;
| - ioh_d = t->t_ioh_d;
| + // ioh_d = t->t_ioh_d;
| ioh_c = t->t_ioh_c;
|
| t->t_pt = pckbport_attach(t, &pckbc_ops);
| @@ -348,6 +348,8 @@ pckbc_attach(struct pckbc_softc *sc)
| goto nomouse;
| }
| t->t_haveaux = 1;
| +
| +#if 0
| bus_space_write_1(iot, ioh_d, 0, 0x5a); /* a random value */
| res = pckbc_poll_data1(t, PCKBC_AUX_SLOT);
|
| @@ -381,6 +383,7 @@ pckbc_attach(struct pckbc_softc *sc)
| #endif
| t->t_haveaux = 0;
| }
| +#endif
|
| nomouse:
| /* enable needed interrupts */
|
|
From: Martin Husemann <martin@duskware.de>
To: Robert Elz <kre@munnari.OZ.AU>
Cc: Marc Baudoin <babafou@babafou.eu.org>, kern-bug-people@netbsd.org,
gnats-admin@netbsd.org, netbsd-bugs@netbsd.org,
babafou+netbsd@babafou.eu.org
Subject: Re: kern/52070: Keyboard freeze after using touchpad
Date: Wed, 15 Mar 2017 10:25:36 +0100
On Wed, Mar 15, 2017 at 06:51:22AM +0700, Robert Elz wrote:
> Try the following patch instead, this applies to the original file,
> and includes Martin's patch, as modified the way I intended you to
> modify it.
I guess we should commit a cleaned up version of that - given that we do
not probe the kbd port any more for similar reasons.
Another option would be to check if we are attaching via some direct
config mechanism (like acpi in this case) and then don't question the
wisdom of the bios - but still probe if we come via stupid isa config.
Might not be worth the effort though.
Martin
Responsible-Changed-From-To: kern-bug-people->martin
Responsible-Changed-By: martin@NetBSD.org
Responsible-Changed-When: Wed, 15 Mar 2017 11:48:46 +0000
Responsible-Changed-Why:
Take
From: David Holland <dholland-bugs@netbsd.org>
To: gnats-bugs@netbsd.org
Cc:
Subject: Re: kern/52070: Keyboard freeze after using touchpad
Date: Sun, 11 Mar 2018 23:45:26 +0000
This whole subthread did not make it to the gnats database.
------
From: Marc Baudoin <babafou@babafou.eu.org>
To: Robert Elz <kre@munnari.OZ.AU>
Cc: kern-bug-people@netbsd.org, gnats-admin@netbsd.org, netbsd-bugs@netbsd.org,
babafou+netbsd@babafou.eu.org
Subject: Re: kern/52070: Keyboard freeze after using touchpad
Date: Tue, 14 Mar 2017 13:24:01 +0100
Robert Elz <kre@munnari.OZ.AU> ?crit :
>
> From: Robert Elz <kre@munnari.OZ.AU>
> To: gnats-bugs@NetBSD.org
> Subject: Re: kern/52070: Keyboard freeze after using touchpad
> Date: Tue, 14 Mar 2017 19:10:26 +0700
>
> Date: Tue, 14 Mar 2017 10:25:00 +0000 (UTC)
> From: babafou+netbsd@babafou.eu.org
> Message-ID: <20170314102500.CE9687A2B5@mollari.NetBSD.org>
>
> | http://www.clevo.com.tw/clevo_prodetail.asp?id=995&lang=en
> |
> | The keyboard works fine after boot but stops working as soon
> | as the touchpad if used.
>
> My guess is that this is related to ...
>
> | pckbc1 at acpi0 (PS2K, MSFT0001) (kbd port): io 0x60,0x64 irq 1
> | pckbc2 at acpi0 (SYNM, SYN1222-3) (aux port): irq 12
>
> The second of those is (I am assuming) really the touchpad, but it is
> being attached as a keyboard controller.
I tend to agree on that.
> When it does something (when you touch it) I would assume the keyboard
> driver attempts to communicate, and not being a keyboard, the touchpad
> fails to react as expected. That the real keyboard, and the touchpad
> are both ports on the same controller is most probably what stops the
> keyboard from working any more - the hardware is waiting for a keyboard
> type response from a touchpad.
This seems logical.
> Note this is all guesswork, and I have no idea at all how to stop the
> touchpad from being configured as a keyboard controller, nor why that
> is happening in the first place. But perhaps someone who understands
> the way all this works inside the NetBSD kernel can figure out something
> that could be done to stop it, so we can tell if this really is the root
> cause of the problem.
I'm ready to test any patch anybody can provide.
From: Christos Zoulas <christos@zoulas.com>
To: Marc Baudoin <babafou@babafou.eu.org>, Robert Elz <kre@munnari.OZ.AU>
Cc: kern-bug-people@netbsd.org, gnats-admin@netbsd.org, netbsd-bugs@netbsd.org,
babafou+netbsd@babafou.eu.org
Subject: Re: kern/52070: Keyboard freeze after using touchpad
Date: Tue, 14 Mar 2017 13:38:31 -0400
On Mar 14, 1:24pm, babafou@babafou.eu.org (Marc Baudoin) wrote:
-- Subject: Re: kern/52070: Keyboard freeze after using touchpad
| >
| > | pckbc1 at acpi0 (PS2K, MSFT0001) (kbd port): io 0x60,0x64 irq 1
| > | pckbc2 at acpi0 (SYNM, SYN1222-3) (aux port): irq 12
Try disabling pckbc* at acpi0...
christos
From: Marc Baudoin <babafou@babafou.eu.org>
To: Christos Zoulas <christos@zoulas.com>
Cc: Robert Elz <kre@munnari.OZ.AU>, kern-bug-people@netbsd.org,
gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
Subject: Re: kern/52070: Keyboard freeze after using touchpad
Date: Tue, 14 Mar 2017 19:15:20 +0100
Christos Zoulas <christos@zoulas.com> ?crit :
> On Mar 14, 1:24pm, babafou@babafou.eu.org (Marc Baudoin) wrote:
> -- Subject: Re: kern/52070: Keyboard freeze after using touchpad
>
> | >
> | > | pckbc1 at acpi0 (PS2K, MSFT0001) (kbd port): io 0x60,0x64 irq 1
> | > | pckbc2 at acpi0 (SYNM, SYN1222-3) (aux port): irq 12
>
> Try disabling pckbc* at acpi0...
The keyboard still freezes the same way.
FYI, dmesg diff:
121,122c122,123
< pckbc1 at acpi0 (PS2K, MSFT0001) (kbd port): io 0x60,0x64 irq 1
< pckbc2 at acpi0 (SYNM, SYN1222-3) (aux port): irq 12
---
> PS2K (MSFT0001) at acpi0 not configured
> SYNM (SYN1222) at acpi0 not configured
141,143d141
< pckbd0 at pckbc1 (kbd slot)
< pckbc1: using irq 1 for kbd slot
< wskbd0 at pckbd0: console keyboard
148c146
< wsdisplay0 at vga0 kbdmux 1: console (80x25, vt100 emulation),
using wskbd0
---
> wsdisplay0 at vga0 kbdmux 1: console (80x25, vt100 emulation)
209a208,212
> pckbc0 at isa0 port 0x60-0x64
> pckbd0 at pckbc0 (kbd slot)
> pckbc0: using irq 1 for kbd slot
> wskbd0 at pckbd0: console keyboard, using wsdisplay0
> pckbc: aux echo test failed
From: Marc Baudoin <babafou@babafou.eu.org>
To: Robert Elz <kre@munnari.OZ.AU>
Cc: kern-bug-people@netbsd.org, gnats-admin@netbsd.org, netbsd-bugs@netbsd.org,
babafou+netbsd@babafou.eu.org
Subject: Re: kern/52070: Keyboard freeze after using touchpad
Date: Tue, 14 Mar 2017 16:30:25 +0100
Robert Elz <kre@munnari.OZ.AU> ?crit :
>
> From: Robert Elz <kre@munnari.OZ.AU>
> To: gnats-bugs@NetBSD.org
> Cc:
> Subject: Re: kern/52070: Keyboard freeze after using touchpad
> Date: Tue, 14 Mar 2017 21:28:52 +0700
>
> Date: Tue, 14 Mar 2017 13:30:01 +0000 (UTC)
> From: Martin Husemann <martin@duskware.de>
> Message-ID: <20170314133001.98DA57A28E@mollari.NetBSD.org>
>
> | Just to see if this gets us any further, could you try the patch below
> | (and PMSDEBUG, ...)
>
> And the other debugs as well (PCKBCDEBUG etc).
>
> But I don't think the patch as is will help, it appears to #if 0
> away the:
> if (pckbc_attach_slot(sc, PCKBC_AUX_SLOT))
> cmdbits |= KC8_MENABLE;
> and if that doesn't happen nothing is likely improve things.
>
> So, Marc, try Martin's patch, but also try inserting
>
> #endif just before the two lines I included above, and #if 0
> immediately after (so those two lines effectively get excluded
> from the code that Martin suggests you try deleting.)
I must have missed something because the new kernel crashed at
boot time printing:
wskbd1 at pckbd1panic: kernel diagnostic assertion "wskbd_console_device == NULL" failed file "../../../../dev/wscons/wskbd.c", line 493
Options added to GENERIC config file:
> options PMSDEBUG
> options PCKBCDEBUG
> options PCKBPORTDEBUG
Patch:
--- pckbc.c.orig 2016-07-14 18:41:13.000000000 +0200
+++ pckbc.c 2017-03-14 16:11:34.735104163 +0100
@@ -278,13 +278,13 @@
{
struct pckbc_internal *t;
bus_space_tag_t iot;
- bus_space_handle_t ioh_d, ioh_c;
- int res;
+ bus_space_handle_t /* ioh_d, */ ioh_c;
+ // int res;
u_char cmdbits = 0;
t = sc->id;
iot = t->t_iot;
- ioh_d = t->t_ioh_d;
+ // ioh_d = t->t_ioh_d;
ioh_c = t->t_ioh_c;
t->t_pt = pckbport_attach(t, &pckbc_ops);
@@ -323,8 +323,11 @@
if (res != 0)
printf("pckbc: returned %x on kbd slot test\n", res);
#endif
+#endif
if (pckbc_attach_slot(sc, PCKBC_KBD_SLOT))
cmdbits |= KC8_KENABLE;
+
+#if 0
} else {
printf("pckbc: kbd port test: %x\n", res);
return;
@@ -348,6 +351,8 @@
goto nomouse;
}
t->t_haveaux = 1;
+
+#if 0
bus_space_write_1(iot, ioh_d, 0, 0x5a); /* a random value */
res = pckbc_poll_data1(t, PCKBC_AUX_SLOT);
@@ -381,6 +386,7 @@
#endif
t->t_haveaux = 0;
}
+#endif
nomouse:
/* enable needed interrupts */
From: Martin Husemann <martin@duskware.de>
To: Marc Baudoin <babafou@babafou.eu.org>
Cc: Robert Elz <kre@munnari.OZ.AU>, kern-bug-people@netbsd.org,
gnats-admin@netbsd.org, netbsd-bugs@netbsd.org,
babafou+netbsd@babafou.eu.org
Subject: Re: kern/52070: Keyboard freeze after using touchpad
Date: Tue, 14 Mar 2017 16:33:15 +0100
On Tue, Mar 14, 2017 at 04:30:25PM +0100, Marc Baudoin wrote:
> I must have missed something because the new kernel crashed at
> boot time printing:
>
> wskbd1 at pckbd1panic: kernel diagnostic assertion "wskbd_console_device == NULL" failed file "../../../../dev/wscons/wskbd.c", line 493
Please show more of the output before that.
Martin
From: Marc Baudoin <babafou@babafou.eu.org>
To: Martin Husemann <martin@duskware.de>
Cc: Robert Elz <kre@munnari.OZ.AU>, kern-bug-people@netbsd.org,
gnats-admin@netbsd.org, netbsd-bugs@netbsd.org,
babafou+netbsd@babafou.eu.org
Subject: Re: kern/52070: Keyboard freeze after using touchpad
Date: Tue, 14 Mar 2017 16:37:34 +0100
Martin Husemann <martin@duskware.de> ?crit :
> On Tue, Mar 14, 2017 at 04:30:25PM +0100, Marc Baudoin wrote:
> > I must have missed something because the new kernel crashed at
> > boot time printing:
> >
> > wskbd1 at pckbd1panic: kernel diagnostic assertion "wskbd_console_device == NULL" failed file "../../../../dev/wscons/wskbd.c", line 493
>
> Please show more of the output before that.
pckbd0 at pckbc1 (kbd slot)
pckbc1: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard
pckbd1 at pckbc1 (kbd slot)
pckbc1: using irq 1 for kbd slot
[ then the kernel panic ]
From: Robert Elz <kre@munnari.OZ.AU>
To: Marc Baudoin <babafou@babafou.eu.org>
cc: kern-bug-people@netbsd.org, gnats-admin@netbsd.org, netbsd-bugs@netbsd.org,
babafou+netbsd@babafou.eu.org
Subject: Re: kern/52070: Keyboard freeze after using touchpad
Date: Wed, 15 Mar 2017 06:51:22 +0700
Date: Tue, 14 Mar 2017 16:30:25 +0100
From: Marc Baudoin <babafou@babafou.eu.org>
Message-ID: <20170314153025.GK954@shuttle.babafou.eu.org>
| Patch:
Sorry, that didn't get applied as I intended, I should have sent a diff,
not just words...
Try the following patch instead, this applies to the original file,
and includes Martin's patch, as modified the way I intended you to
modify it.
No guarantee that this will make anything work, but it might supply
some more info.
You can use this with, or without, the acpi config of the pckbc
(which seems to make no difference) - or both ways...
kre
--- /local/netbsd/src/sys/dev/ic/pckbc.c 2016-07-30 13:54:12.000000000 +0700
+++ pckbc.c 2017-03-15 06:48:34.000000000 +0700
@@ -278,13 +278,13 @@
{
struct pckbc_internal *t;
bus_space_tag_t iot;
- bus_space_handle_t ioh_d, ioh_c;
- int res;
+ bus_space_handle_t /* ioh_d, */ ioh_c;
+ // int res;
u_char cmdbits = 0;
t = sc->id;
iot = t->t_iot;
- ioh_d = t->t_ioh_d;
+ // ioh_d = t->t_ioh_d;
ioh_c = t->t_ioh_c;
t->t_pt = pckbport_attach(t, &pckbc_ops);
@@ -348,6 +348,8 @@
goto nomouse;
}
t->t_haveaux = 1;
+
+#if 0
bus_space_write_1(iot, ioh_d, 0, 0x5a); /* a random value */
res = pckbc_poll_data1(t, PCKBC_AUX_SLOT);
@@ -372,8 +374,10 @@
* We are satisfied if there is anything in the
* aux output buffer.
*/
+#endif
if (pckbc_attach_slot(sc, PCKBC_AUX_SLOT))
cmdbits |= KC8_MENABLE;
+#if 0
} else {
#ifdef PCKBCDEBUG
@@ -381,6 +385,7 @@
#endif
t->t_haveaux = 0;
}
+#endif
nomouse:
/* enable needed interrupts */
From: Marc Baudoin <babafou@babafou.eu.org>
To: Robert Elz <kre@munnari.OZ.AU>
Cc: kern-bug-people@netbsd.org, gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
Subject: Re: kern/52070: Keyboard freeze after using touchpad
Date: Wed, 15 Mar 2017 08:49:17 +0100
Robert Elz <kre@munnari.OZ.AU> ?crit :
>
> Sorry, that didn't get applied as I intended, I should have sent a diff,
> not just words...
>
> Try the following patch instead, this applies to the original file,
> and includes Martin's patch, as modified the way I intended you to
> modify it.
>
> No guarantee that this will make anything work, but it might supply
> some more info.
>
> You can use this with, or without, the acpi config of the pckbc
> (which seems to make no difference) - or both ways...
Well, this is *much* better. Now the keyboard doesn't freeze
anymore and the touchpad works as expected.
Thank you very much!
Full dmesg below:
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017
The NetBSD Foundation, Inc. All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
NetBSD 7.99.65 (BABAFOU) #0: Wed Mar 15 08:40:37 CET 2017
babafou@test.babafou.eu.org:/usr/src/sys/arch/amd64/compile/BABAFOU
total memory = 16143 MB
avail memory = 15652 MB
cpu_rng: RDSEED
timecounter: Timecounters tick every 10.000 msec
Kernelized RAIDframe activated
running cgd selftest aes-xts-256 aes-xts-512 done
timecounter: Timecounter "i8254" frequency 1193182 Hz quality 100
Notebook N750BU (Not Applicable )
mainbus0 (root)
ACPI: RSDP 0x00000000000F05B0 000024 (v02 ALASKA)
ACPI: XSDT 0x000000007F86C0A0 0000C4 (v01 ALASKA A M I 01072009 AMI 00010013)
ACPI: FACP 0x000000007F887640 000114 (v06 ALASKA A M I 01072009 AMI 00010013)
ACPI: DSDT 0x000000007F86C200 01B43D (v02 ALASKA A M I 01072009 INTL 20160422)
ACPI: FACS 0x000000007FBE6C40 000040
ACPI: APIC 0x000000007F887758 000084 (v03 ALASKA A M I 01072009 AMI 00010013)
ACPI: FPDT 0x000000007F8877E0 000044 (v01 ALASKA A M I 01072009 AMI 00010013)
ACPI: MCFG 0x000000007F887828 00003C (v01 ALASKA A M I 01072009 MSFT 00000097)
ACPI: FIDT 0x000000007F887868 00009C (v01 ALASKA A M I 01072009 AMI 00010013)
ACPI: SSDT 0x000000007F887908 003295 (v02 SaSsdt SaSsdt 00003000 INTL 20160422)
ACPI: HPET 0x000000007F88ABA0 000038 (v01 INTEL KBL-ULT 00000001 MSFT 0000005F)
ACPI: SSDT 0x000000007F88ABD8 000024 (v02 INTEL xh_OEMBD 00000000 INTL 20160422)
ACPI: UEFI 0x000000007F88AC00 000042 (v01 INTEL EDK2 00000002 01000013)
ACPI: SSDT 0x000000007F88AC48 000EDE (v02 CpuRef CpuSsdt 00003000 INTL 20160422)
ACPI: SSDT 0x000000007F88BB28 0003E3 (v02 PmRef Cpu0Tst 00003000 INTL 20160422)
ACPI: SSDT 0x000000007F88BF10 000471 (v02 PmRef ApTst 00003000 INTL 20160422)
ACPI: LPIT 0x000000007F88C388 000094 (v01 INTEL KBL-ULT 00000000 MSFT 0000005F)
ACPI: WSMT 0x000000007F88C420 000028 (v01 INTEL KBL-ULT 00000000 MSFT 0000005F)
ACPI: SSDT 0x000000007F88C448 00029F (v02 INTEL sensrhub 00000000 INTL 20160422)
ACPI: SSDT 0x000000007F88C6E8 003002 (v02 INTEL PtidDevc 00001000 INTL 20160422)
ACPI: DBGP 0x000000007F88F6F0 000034 (v01 INTEL 00000002 MSFT 0000005F)
ACPI: DBG2 0x000000007F88F728 000054 (v00 INTEL 00000002 MSFT 0000005F)
ACPI: DMAR 0x000000007F88F780 0000A8 (v01 INTEL KBL 00000001 INTL 00000001)
ACPI: ASF! 0x000000007F88F828 0000A0 (v32 INTEL HCG 00000001 TFSM 000F4240)
ACPI: Executed 21 blocks of module-level executable AML code
ACPI: Executed 1 blocks of module-level executable AML code
ACPI: Executed 1 blocks of module-level executable AML code
ACPI: Executed 1 blocks of module-level executable AML code
ACPI: Executed 1 blocks of module-level executable AML code
ACPI: Executed 1 blocks of module-level executable AML code
ACPI: Executed 1 blocks of module-level executable AML code
ACPI: 8 ACPI AML tables successfully acquired and loaded
ioapic0 at mainbus0 apid 2: pa 0xfec00000, version 0x20, 120 pins
cpu0 at mainbus0 apid 0
cpu0: Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz, id 0x806e9
cpu1 at mainbus0 apid 2
cpu1: Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz, id 0x806e9
cpu2 at mainbus0 apid 1
cpu2: Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz, id 0x806e9
cpu3 at mainbus0 apid 3
cpu3: Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz, id 0x806e9
acpi0 at mainbus0: Intel ACPICA 20170119
acpi0: X/RSDT: OemId <ALASKA, A M I ,01072009>, AslId <AMI ,00010013>
acpi0: invalid PCI address for D02E
acpi0: MCFG: segment 0, bus 0-255, address 0x00000000e0000000
ACPI: Dynamic OEM Table Load:
ACPI: SSDT 0xFFFFFE811CD5A010 0003FF (v02 PmRef Cpu0Cst 00003001 INTL 20160422)
ACPI: Executed 1 blocks of module-level executable AML code
ACPI: Dynamic OEM Table Load:
ACPI: SSDT 0xFFFFFE811CDC1810 0006F6 (v02 PmRef Cpu0Ist 00003000 INTL 20160422)
ACPI: Executed 1 blocks of module-level executable AML code
ACPI: Dynamic OEM Table Load:
ACPI: SSDT 0xFFFFFE811CDC1010 00065C (v02 PmRef ApIst 00003000 INTL 20160422)
ACPI: Executed 1 blocks of module-level executable AML code
ACPI: Dynamic OEM Table Load:
ACPI: SSDT 0xFFFFFE846E316710 00018A (v02 PmRef ApCst 00003000 INTL 20160422)
ACPI: Executed 1 blocks of module-level executable AML code
acpi0: SCI interrupting at int 9
timecounter: Timecounter "ACPI-Fast" frequency 3579545 Hz quality 1000
hpet0 at acpi0: high precision event timer (mem 0xfed00000-0xfed00400)
timecounter: Timecounter "hpet0" frequency 24000000 Hz quality 2000
acpiec0 at acpi0 (EC, PNP0C09): io 0x62,0x66
acpivga0 at acpi0 (GFX0): ACPI Display Adapter
acpiout0 at acpivga0 (DD01, 0x0100): ACPI Display Output Device
acpiout1 at acpivga0 (DD02, 0x0002): ACPI Display Output Device
acpiout2 at acpivga0 (DD03, 0x0300): ACPI Display Output Device
acpiout3 at acpivga0 (DD04, 0x0301): ACPI Display Output Device
acpiout4 at acpivga0 (DD05, 0x0302): ACPI Display Output Device
acpiout5 at acpivga0 (DD06, 0x0303): ACPI Display Output Device
acpiout6 at acpivga0 (DD07, 0x0304): ACPI Display Output Device
acpiout7 at acpivga0 (DD08, 0x0305): ACPI Display Output Device
acpiout8 at acpivga0 (DD09, 0x0009): ACPI Display Output Device
acpiout9 at acpivga0 (DD0A, 0x000a): ACPI Display Output Device
acpiout10 at acpivga0 (DD0B, 0x000b): ACPI Display Output Device
acpiout11 at acpivga0 (DD0C, 0x000c): ACPI Display Output Device
acpiout12 at acpivga0 (DD0D, 0x000d): ACPI Display Output Device
acpiout13 at acpivga0 (DD0E, 0x000e): ACPI Display Output Device
acpiout14 at acpivga0 (DD0F, 0x000f): ACPI Display Output Device
acpiout15 at acpivga0 (DD1F, 0x0400): ACPI Display Output Device
acpiout15: brightness levels: [0-100]
acpiout16 at acpivga0 (SKC0, 0xca00): ACPI Display Output Device
acpivga0: unknown output device acpiout0
acpivga0: unknown output device acpiout1
acpivga0: unknown output device acpiout2
acpivga0: unknown output device acpiout3
acpivga0: unknown output device acpiout4
acpivga0: unknown output device acpiout5
acpivga0: unknown output device acpiout6
acpivga0: unknown output device acpiout7
acpivga0: unknown output device acpiout8
acpivga0: unknown output device acpiout9
acpivga0: unknown output device acpiout10
acpivga0: unknown output device acpiout11
acpivga0: unknown output device acpiout12
acpivga0: unknown output device acpiout13
acpivga0: unknown output device acpiout14
acpivga0: unknown output device acpiout16
acpivga0: connected output devices:
acpivga0: 0x0400 (acpiout15): Unknown Output Device, head 0
FWHD (INT0800) at acpi0 not configured
LDRC (PNP0C02) at acpi0 not configured
attimer1 at acpi0 (TIMR, PNP0100): io 0x40-0x43,0x50-0x53 irq 0
CWDT (INT3F0D) at acpi0 not configured
pckbc1 at acpi0 (PS2K, MSFT0001) (kbd port): io 0x60,0x64 irq 1
pckbc2 at acpi0 (SYNM, SYN1222-3) (aux port): irq 12
PDRC (PNP0C02) at acpi0 not configured
IOTR (PNP0C02) at acpi0 not configured
EPC (INT0E0C) at acpi0 not configured
PEPD (INT33A1) at acpi0 not configured
CAI (PNPC000) at acpi0 not configured
acpibut0 at acpi0 (PWRB, PNP0C0C): ACPI Power Button
acpibut1 at acpi0 (SLPB, PNP0C0E): ACPI Sleep Button
acpilid0 at acpi0 (LID0, PNP0C0D): ACPI Lid Switch
acpiacad0 at acpi0 (AC, ACPI0003): ACPI AC Adapter
acpibat0 at acpi0 (BAT0, PNP0C0A-0): ACPI Battery
acpibat0: Notebook LION rechargeable battery
acpibat0: granularity: low->warn 0.064 Ah, warn->full 0.064 Ah
acpiwmi0 at acpi0 (WMI, PNP0C14-0): ACPI WMI Interface
acpiwmibus at acpiwmi0 not configured
PTID (INT340E) at acpi0 not configured
acpitz0 at acpi0 (TZ0)
acpitz0: levels: critical 120.0 C, passive cooling
ACPI: Enabled 4 GPEs in block 00 to 7F
pckbd0 at pckbc1 (kbd slot)
pckbc1: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard
pms0 at pckbc1 (aux slot)
pms0: Synaptics touchpad version 8.2
pms0: Extended W mode, Palm detect, Multi-finger Report, Multi-finger
pckbc1: using irq 12 for aux slot
wsmouse0 at pms0 mux 0
pci0 at mainbus0 bus 0: configuration mode 1
pci0: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok
pchb0 at pci0 dev 0 function 0: vendor 8086 product 5904 (rev. 0x02)
vga0 at pci0 dev 2 function 0: vendor 8086 product 5916 (rev. 0x02)
wsdisplay0 at vga0 kbdmux 1: console (80x25, vt100 emulation), using wskbd0
wsmux1: connecting to wsdisplay0
drm at vga0 not configured
vendor 8086 product 1911 (miscellaneous system) at pci0 dev 8 function 0 not configured
xhci0 at pci0 dev 20 function 0: vendor 8086 product 9d2f (rev. 0x21)
xhci0: interrupting at msi0 vec 0
xhci0: xHCI version 1.0
usb0 at xhci0: USB revision 3.0
usb1 at xhci0: USB revision 2.0
vendor 8086 product 9d31 (miscellaneous DASP, revision 0x21) at pci0 dev 20 function 2 not configured
vendor 8086 product 9d3a (miscellaneous communications, revision 0x21) at pci0 dev 22 function 0 not configured
ahcisata0 at pci0 dev 23 function 0: vendor 8086 product 9d03 (rev. 0x21)
ahcisata0: interrupting at ioapic0 pin 16
ahcisata0: 64-bit DMA
ahcisata0: AHCI revision 1.31, 3 ports, 32 slots, CAP 0xc734ff02<PSC,SSC,PMD,SAM,ISS=0x3=Gen3,SCLO,SAL,SALP,SNCQ,S64A>
atabus0 at ahcisata0 channel 0
atabus1 at ahcisata0 channel 1
atabus2 at ahcisata0 channel 2
ppb0 at pci0 dev 28 function 0: vendor 8086 product 9d10 (rev. 0xf1)
ppb0: PCI Express capability version 2 <Root Port of PCI-E Root Complex> x2 @ 8.0GT/s
pci1 at ppb0 bus 1
pci1: i/o space, memory space enabled, rd/line, wr/inv ok
ppb1 at pci0 dev 28 function 3: vendor 8086 product 9d13 (rev. 0xf1)
ppb1: PCI Express capability version 2 <Root Port of PCI-E Root Complex> x1 @ 8.0GT/s
ppb1: link is x1 @ 2.5GT/s
pci2 at ppb1 bus 2
pci2: i/o space, memory space enabled, rd/line, wr/inv ok
rtsx0 at pci2 dev 0 function 0: vendor 10ec product 5287 (rev. 0x01)
rtsx0: interrupting at msi1 vec 0
sdmmc0 at rtsx0
re0 at pci2 dev 0 function 1: RealTek 8168/8111 PCIe Gigabit Ethernet (rev. 0x12)
re0: interrupting at msi2 vec 0
re0: Ethernet address 80:fa:5b:3e:41:20
re0: using 256 tx descriptors
rgephy0 at re0 phy 7: RTL8251 1000BASE-T media interface, rev. 0
rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT-FDX, auto
ppb2 at pci0 dev 28 function 4: vendor 8086 product 9d14 (rev. 0xf1)
ppb2: PCI Express capability version 2 <Root Port of PCI-E Root Complex> x1 @ 8.0GT/s
ppb2: link is x1 @ 2.5GT/s
pci3 at ppb2 bus 3
pci3: i/o space, memory space enabled, rd/line, wr/inv ok
iwm0 at pci3 dev 0 function 0: vendor 8086 product 24f3 (rev. 0x3a)
iwm0: interrupting at msi3 vec 0
pcib0 at pci0 dev 31 function 0: vendor 8086 product 9d4e (rev. 0x21)
vendor 8086 product 9d21 (miscellaneous memory, revision 0x21) at pci0 dev 31 function 2 not configured
hdaudio0 at pci0 dev 31 function 3: HD Audio Controller
hdaudio0: interrupting at msi4 vec 0
hdafg0 at hdaudio0: vendor 10ec product 0269
hdafg0: DAC00 2ch: HP Out [Jack]
hdafg0: DAC01 2ch: Speaker [Built-In]
hdafg0: ADC02 2ch: Mic In [Built-In]
hdafg0: ADC03 2ch: Mic In [Jack]
hdafg0: 2ch/2ch 32000Hz 44100Hz 48000Hz 88200Hz 96000Hz 192000Hz PCM16 PCM20 PCM24 AC3
audio0 at hdafg0: full duplex, playback, capture, mmap, independent
hdafg0: Virtual format configured - Format SLINEAR, precision 16, channels 2, frequency 48000
spkr0 at audio0: PC Speaker (synthesized)
hdafg1 at hdaudio0: vendor 8086 product 280b
hdafg1: DP00 8ch: Digital Out [Jack]
hdafg1: 8ch/0ch 48000Hz PCM16*
vendor 8086 product 9d23 (SMBus serial bus, revision 0x21) at pci0 dev 31 function 4 not configured
isa0 at pcib0
tpm0 at isa0 iomem 0xfed40000-0xfed44fff irq 7: device 0x001a15d1 rev 0x10
pcppi0 at isa0 port 0x61
spkr1 at pcppi0: PC Speaker
midi0 at pcppi0: PC speaker
sysbeep0 at pcppi0
attimer1: attached to pcppi0
acpicpu0 at cpu0: ACPI CPU
acpicpu0: C1: FFH, lat 1 us, pow 1000 mW
acpicpu0: C2: FFH, lat 151 us, pow 200 mW
acpicpu0: C3: FFH, lat 1034 us, pow 200 mW
acpicpu0: P0: FFH, lat 10 us, pow 15000 mW, 2701 MHz, turbo boost
acpicpu0: P1: FFH, lat 10 us, pow 13633 mW, 2700 MHz
acpicpu0: P2: FFH, lat 10 us, pow 12897 mW, 2600 MHz
acpicpu0: P3: FFH, lat 10 us, pow 12318 mW, 2500 MHz
acpicpu0: P4: FFH, lat 10 us, pow 11608 mW, 2400 MHz
acpicpu0: P5: FFH, lat 10 us, pow 10372 mW, 2200 MHz
acpicpu0: P6: FFH, lat 10 us, pow 9182 mW, 2000 MHz
acpicpu0: P7: FFH, lat 10 us, pow 8173 mW, 1800 MHz
acpicpu0: P8: FFH, lat 10 us, pow 7075 mW, 1600 MHz
acpicpu0: P9: FFH, lat 10 us, pow 6480 mW, 1500 MHz
acpicpu0: P10: FFH, lat 10 us, pow 5453 mW, 1300 MHz
acpicpu0: P11: FFH, lat 10 us, pow 4472 mW, 1100 MHz
acpicpu0: P12: FFH, lat 10 us, pow 3140 mW, 800 MHz
acpicpu0: P13: FFH, lat 10 us, pow 2756 mW, 700 MHz
acpicpu0: P14: FFH, lat 10 us, pow 2267 mW, 600 MHz
acpicpu0: P15: FFH, lat 10 us, pow 1435 mW, 400 MHz
acpicpu0: T0: FFH, lat 1 us, pow 1435 mW, 100 %
acpicpu0: T1: FFH, lat 1 us, pow 1345 mW, 94 %
acpicpu0: T2: FFH, lat 1 us, pow 1255 mW, 88 %
acpicpu0: T3: FFH, lat 1 us, pow 1165 mW, 82 %
acpicpu0: T4: FFH, lat 1 us, pow 1076 mW, 75 %
acpicpu0: T5: FFH, lat 1 us, pow 986 mW, 69 %
acpicpu0: T6: FFH, lat 1 us, pow 896 mW, 63 %
acpicpu0: T7: FFH, lat 1 us, pow 807 mW, 57 %
acpicpu0: T8: FFH, lat 1 us, pow 717 mW, 50 %
acpicpu0: T9: FFH, lat 1 us, pow 627 mW, 44 %
acpicpu0: T10: FFH, lat 1 us, pow 538 mW, 38 %
acpicpu0: T11: FFH, lat 1 us, pow 448 mW, 32 %
acpicpu0: T12: FFH, lat 1 us, pow 358 mW, 25 %
acpicpu0: T13: FFH, lat 1 us, pow 269 mW, 19 %
acpicpu0: T14: FFH, lat 1 us, pow 179 mW, 13 %
acpicpu0: T15: FFH, lat 1 us, pow 89 mW, 7 %
coretemp0 at cpu0: thermal sensor, 1 C resolution, Tjmax=100
acpicpu1 at cpu1: ACPI CPU
coretemp1 at cpu1: thermal sensor, 1 C resolution, Tjmax=100
acpicpu2 at cpu2: ACPI CPU
acpicpu3 at cpu3: ACPI CPU
timecounter: Timecounter "clockinterrupt" frequency 100 Hz quality 0
ERROR: 111113622 cycle TSC drift observed
acpiacad0: AC adapter online.
uhub0 at usb0: vendor 8086 xHCI Root Hub, class 9/0, rev 1.00/1.00, addr 0
uhub0: 6 ports with 6 removable, self powered
uhub1 at usb1: vendor 8086 xHCI Root Hub, class 9/0, rev 2.00/1.00, addr 0
uhub1: 12 ports with 12 removable, self powered
IPsec: Initialized Security Association Processing.
ahcisata0 port 1: device present, speed: 1.5Gb/s
ahcisata0 port 2: device present, speed: 6.0Gb/s
ahcisata0 port 0: device present, speed: 6.0Gb/s
wd0 at atabus0 drive 0
wd0: <ST1000LX015-1U7172>
wd0: drive supports 16-sector PIO transfers, LBA48 addressing
wd0: 931 GB, 1938021 cyl, 16 head, 63 sec, 512 bytes/sect x 1953525168 sectors
wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133)
wd0(ahcisata0:0:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133) (using DMA)
atapibus0 at atabus1: 1 targets
cd0 at atapibus0 drive 0: <Slimtype DVD A DU8A6SH, 415635502142, DP57> cdrom removable
cd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133)
cd0(ahcisata0:1:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133) (using DMA)
wd1 at atabus2 drive 0
wd1: <WDC WDS120G1G0B-00RC30>
wd1: drive supports 1-sector PIO transfers, LBA48 addressing
wd1: 111 GB, 232581 cyl, 16 head, 63 sec, 512 bytes/sect x 234441648 sectors
wd1: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133)
wd1(ahcisata0:2:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133) (using DMA)
rum0 at uhub1 port 3
rum0: Cisco-Linksys Compact Wireless-G USB Adapter, rev 2.00/0.01, addr 1
rum0: MAC/BBP RT2573 (rev 0x2573a), RF RT2528, address 00:22:6b:a9:53:c3
rum0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
rum0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
ubt0 at uhub1 port 5
ubt0: vendor 8087 product 0a2b, rev 2.00/0.01, addr 2
sdmmc0: sdmmc_mem_enable failed with error 60
sdmmc0: couldn't enable card: 60
uvideo0 at uhub1 port 6 configuration 1 interface 0: Bison BisonCam,NB Pro, rev 2.00/6.02, addr 3
video0 at uvideo0: Bison BisonCam,NB Pro, rev 2.00/6.02, addr 3
uhidev0 at uhub1 port 8 configuration 1 interface 0
uhidev0: Logitech USB Receiver, rev 2.00/22.00, addr 4, iclass 3/1
ums0 at uhidev0: 16 buttons, W and Z dirs
wsmouse1 at ums0 mux 0
uhidev1 at uhub1 port 8 configuration 1 interface 1
uhidev1: Logitech USB Receiver, rev 2.00/22.00, addr 4, iclass 3/0
uhidev1: 17 report ids
uhid0 at uhidev1 reportid 3: input=4, output=0, feature=0
uhid1 at uhidev1 reportid 16: input=6, output=6, feature=0
uhid2 at uhidev1 reportid 17: input=19, output=19, feature=0
pad0: outputs: 44100Hz, 16-bit, stereo
audio1 at pad0: half duplex, playback, capture
pad0: Virtual format configured - Format SLINEAR, precision 16, channels 2, frequency 44100
spkr2 at audio1: PC Speaker (synthesized)
WARNING: 19 errors while detecting hardware; check system log.
boot device: wd1
root on wd1a dumps on wd1b
root file system type: ffs
kern.module.path=/stand/amd64/7.99.65/modules
iwm0: hw rev 0x200, fw ver 16.242414.0, address 44:85:00:57:5c:47
iwm0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
iwm0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
iwm0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
sdmmc0: sdmmc_mem_enable failed with error 60
sdmmc0: couldn't enable card: 60
wsdisplay0: screen 1 added (80x25, vt100 emulation)
wsdisplay0: screen 2 added (80x25, vt100 emulation)
wsdisplay0: screen 3 added (80x25, vt100 emulation)
wsdisplay0: screen 4 added (80x25, vt100 emulation)
pms_enable: using synaptics protocol
pms_enable: using synaptics protocol
pms_enable: using synaptics protocol
From: Martin Husemann <martin@duskware.de>
To: Robert Elz <kre@munnari.OZ.AU>
Cc: Marc Baudoin <babafou@babafou.eu.org>, kern-bug-people@netbsd.org,
gnats-admin@netbsd.org, netbsd-bugs@netbsd.org,
babafou+netbsd@babafou.eu.org
Subject: Re: kern/52070: Keyboard freeze after using touchpad
Date: Wed, 15 Mar 2017 10:25:36 +0100
On Wed, Mar 15, 2017 at 06:51:22AM +0700, Robert Elz wrote:
> Try the following patch instead, this applies to the original file,
> and includes Martin's patch, as modified the way I intended you to
> modify it.
I guess we should commit a cleaned up version of that - given that we do
not probe the kbd port any more for similar reasons.
Another option would be to check if we are attaching via some direct
config mechanism (like acpi in this case) and then don't question the
wisdom of the bios - but still probe if we come via stupid isa config.
Might not be worth the effort though.
Martin
From: Robert Elz <kre@munnari.OZ.AU>
To: Martin Husemann <martin@duskware.de>
cc: Marc Baudoin <babafou@babafou.eu.org>, kern-bug-people@netbsd.org,
gnats-admin@netbsd.org, netbsd-bugs@netbsd.org,
babafou+netbsd@babafou.eu.org
Subject: Re: kern/52070: Keyboard freeze after using touchpad
Date: Wed, 15 Mar 2017 18:32:55 +0700
Date: Wed, 15 Mar 2017 10:25:36 +0100
From: Martin Husemann <martin@duskware.de>
Message-ID: <20170315092536.GB26582@mail.duskware.de>
| I guess we should commit a cleaned up version of that - given that we do
| not probe the kbd port any more for similar reasons.
That I will leave for someone who understands PC hardware - my part of this
was no more than noticing that things wouldn't work if the actual attach()
call got omitted...
But it is good to hear that things are better.
kre
From: David Holland <dholland-bugs@netbsd.org>
To: gnats-bugs@netbsd.org
Cc:
Subject: Re: kern/52070: Keyboard freeze after using touchpad
Date: Sat, 1 May 2021 21:55:06 +0000
The following two mails were sent to the wrong place in 2019 and
didn't get to the bug database. Always send to gnats-bugs@ (this is
not always the default when you hit reply) and it will remail.
------
From: Marc Baudoin <babafou@babafou.eu.org>
To: Martin Husemann <martin@duskware.de>
Cc: Robert Elz <kre@munnari.OZ.AU>, kern-bug-people@netbsd.org,
gnats-admin@netbsd.org, netbsd-bugs@netbsd.org,
babafou+netbsd@babafou.eu.org
Subject: Re: kern/52070: Keyboard freeze after using touchpad
Date: Wed, 31 Jul 2019 09:55:06 +0200
Hi,
Martin Husemann <martin@duskware.de> ?crit :
> On Wed, Mar 15, 2017 at 06:51:22AM +0700, Robert Elz wrote:
> > Try the following patch instead, this applies to the original file,
> > and includes Martin's patch, as modified the way I intended you to
> > modify it.
>
> I guess we should commit a cleaned up version of that - given that we do
> not probe the kbd port any more for similar reasons.
Sorry to bother you but I checked if the problem was still
present in the recent NetBSD 9.0_BETA and it is. Any chance to
have a fix committed before release? I'm still using Robert Elz's
patch with 8.1.
Thanks.
From: Marc Baudoin <babafou@babafou.eu.org>
To: Robert Elz <kre@munnari.OZ.AU>
Cc: kern-bug-people@netbsd.org, gnats-admin@netbsd.org, netbsd-bugs@netbsd.org,
babafou+netbsd@babafou.eu.org
Subject: Re: kern/52070: Keyboard freeze after using touchpad
Date: Mon, 2 Dec 2019 20:41:13 +0100
Hi,
Robert Elz <kre@munnari.OZ.AU> ?crit :
> Date: Tue, 14 Mar 2017 16:30:25 +0100
> From: Marc Baudoin <babafou@babafou.eu.org>
> Message-ID: <20170314153025.GK954@shuttle.babafou.eu.org>
>
> | Patch:
>
> Sorry, that didn't get applied as I intended, I should have sent a diff,
> not just words...
>
> Try the following patch instead, this applies to the original file,
> and includes Martin's patch, as modified the way I intended you to
> modify it.
Any news about that? The problem is still in stock 9.0_RC1 and
the patch provided by Robert still applies cleanly and solves the
problem.
From: Paul Goyette <paul@whooppee.com>
To: gnats-bugs@netbsd.org
Cc:
Subject: Re: kern/52070: Keyboard freeze after using touchpad
Date: Mon, 2 May 2022 17:14:17 -0700 (PDT)
There's some concern here that, while the patch might well help
in the submitter's situation, other situations might be adversely
affected. In particular, what is the behaviour of the patch on
systems which have _nothing_ connected to the aux port?
FWIW, it appears that linux takes a bit of a different approach
to probing on the aux port. They send the "random" 0x5a value
with a "loop" command, and fallback to using "echo" if the loop
back fails. (At least that's what I understand from discussion
with jmcneill@ on IRC.)
Any volunteeers who can test the effect of the patch on a system
with _nothing_ on the aux port?
+--------------------+--------------------------+----------------------+
| Paul Goyette | PGP Key fingerprint: | E-mail addresses: |
| (Retired) | FA29 0E3B 35AF E8AE 6651 | paul@whooppee.com |
| Software Developer | 0786 F758 55DE 53BA 7731 | pgoyette@netbsd.org |
| & Network Engineer | | pgoyette99@gmail.com |
+--------------------+--------------------------+----------------------+
From: Martin Husemann <martin@duskware.de>
To: gnats-bugs@netbsd.org
Cc:
Subject: Re: kern/52070: Keyboard freeze after using touchpad
Date: Tue, 3 May 2022 11:49:10 +0200
On Tue, May 03, 2022 at 12:15:02AM +0000, Paul Goyette wrote:
> There's some concern here that, while the patch might well help
> in the submitter's situation, other situations might be adversely
> affected. In particular, what is the behaviour of the patch on
> systems which have _nothing_ connected to the aux port?
My original idea was to avoid the probe when we know (from ACPI) that
there is a "mouse" device on the aux port.
Martin
From: Martin Husemann <martin@duskware.de>
To: gnats-bugs@NetBSD.org
Cc:
Subject: Re: kern/52070: Keyboard freeze after using touchpad
Date: Tue, 10 May 2022 22:22:09 +0200
I was thinking of something like the patch below to skip the probe
in cases where we know the device is there and may be confused by the
random data. That is: check the acpi device name and set
PCKBC_FORCE_AUX_NOPROBE in pckbc_acpi_attach - but I don't understand
the logic there, and why it attaches in this case at all ;-}
The dmesg line says:
pckbc2 at acpi0 (SYNM, SYN1222-3) (aux port): irq 12
and I would suggest to set the flag if the first string starts with SYN.
Is that a good idea?
Martin
Index: pckbc.c
===================================================================
RCS file: /cvsroot/src/sys/dev/ic/pckbc.c,v
retrieving revision 1.62
diff -u -p -r1.62 pckbc.c
--- pckbc.c 1 May 2020 01:34:57 -0000 1.62
+++ pckbc.c 10 May 2022 20:16:52 -0000
@@ -347,8 +347,13 @@ pckbc_attach(struct pckbc_softc *sc)
goto nomouse;
}
t->t_haveaux = 1;
- bus_space_write_1(iot, ioh_d, 0, 0x5a); /* a random value */
- res = pckbc_poll_data1(t, PCKBC_AUX_SLOT);
+ if (ISSET(t->t_flags, PCKBC_FORCE_AUX_NOPROBE)) {
+ /* some devices do not survive the probe sequence */
+ res = 1;
+ } else {
+ bus_space_write_1(iot, ioh_d, 0, 0x5a); /* a random value */
+ res = pckbc_poll_data1(t, PCKBC_AUX_SLOT);
+ }
/*
* The following is needed to find the aux port on the Tadpole
Index: pckbcvar.h
===================================================================
RCS file: /cvsroot/src/sys/dev/ic/pckbcvar.h,v
retrieving revision 1.22
diff -u -p -r1.22 pckbcvar.h
--- pckbcvar.h 7 Dec 2021 19:45:05 -0000 1.22
+++ pckbcvar.h 10 May 2022 20:16:52 -0000
@@ -61,6 +61,7 @@ struct pckbc_internal {
int t_flags;
#define PCKBC_CANT_TRANSLATE 0x0001 /* can't translate to XT scancodes */
#define PCKBC_NEED_AUXWRITE 0x0002 /* need auxwrite command to find aux */
+#define PCKBC_FORCE_AUX_NOPROBE 0x0004 /* force aux port attachement */
int t_haveaux; /* controller has an aux port */
struct pckbc_slotdata *t_slotdata[PCKBC_NSLOTS];
From: Marc Baudoin <babafou@babafou.eu.org>
To: Martin Husemann <martin@duskware.de>
Cc: Robert Elz <kre@munnari.OZ.AU>, kern-bug-people@netbsd.org,
gnats-admin@netbsd.org, netbsd-bugs@netbsd.org,
babafou+netbsd@babafou.eu.org
Subject: Re: kern/52070: Keyboard freeze after using touchpad
Date: Thu, 24 Aug 2023 19:05:21 +0200
Hi,
Marc Baudoin <babafou@babafou.eu.org> écrit :
> Martin Husemann <martin@duskware.de> écrit :
> > On Wed, Mar 15, 2017 at 06:51:22AM +0700, Robert Elz wrote:
> > > Try the following patch instead, this applies to the original file,
> > > and includes Martin's patch, as modified the way I intended you to
> > > modify it.
> >
> > I guess we should commit a cleaned up version of that - given that we do
> > not probe the kbd port any more for similar reasons.
>
> Sorry to bother you but I checked if the problem was still
> present in the recent NetBSD 9.0_BETA and it is.
I just checked and the problem is still here with the latest
NetBSD 10 snapshot.
> Any chance to have a fix committed before release?
Well, before the next release, now...
> I'm still using Robert Elz's patch with 8.1.
It applies to NetBSD 10 sources so it should work as intended but
I didn't compile a new kernel to check that. Anyway, I'd rather
prefer NetBSD to work out of the box on my laptop.
Thanks.
From: Martin Husemann <martin@duskware.de>
To: gnats-bugs@NetBSD.org
Cc:
Subject: Re: kern/52070: Keyboard freeze after using touchpad
Date: Sun, 7 Jan 2024 13:15:41 +0100
Based on a sugestion from Jared - can you test if this far less intrusive
change works for your machine too?
Thanks,
Martin
Index: pckbc.c
===================================================================
RCS file: /cvsroot/src/sys/dev/ic/pckbc.c,v
retrieving revision 1.65
diff -c -u -p -r1.65 pckbc.c
--- pckbc.c 17 Nov 2022 23:57:20 -0000 1.65
+++ pckbc.c 7 Jan 2024 12:14:35 -0000
@@ -342,7 +342,7 @@ pckbc_attach(struct pckbc_softc *sc)
goto nomouse;
}
t->t_haveaux = 1;
- bus_space_write_1(iot, ioh_d, 0, 0x5a); /* a random value */
+ bus_space_write_1(iot, ioh_d, 0, KBC_SETDEFAULT);
res = pckbc_poll_data1(t, PCKBC_AUX_SLOT);
/*
From: Marc Baudoin <babafou@babafou.eu.org>
To: gnats-bugs@netbsd.org
Cc: martin@netbsd.org, gnats-admin@netbsd.org, netbsd-bugs@netbsd.org,
babafou+netbsd@babafou.eu.org
Subject: Re: kern/52070: Keyboard freeze after using touchpad
Date: Sun, 7 Jan 2024 14:08:58 +0100
Hi,
Happy new year, by the way.
Martin Husemann <martin@duskware.de> écrit :
> The following reply was made to PR kern/52070; it has been noted by GNATS.
>
> From: Martin Husemann <martin@duskware.de>
> To: gnats-bugs@NetBSD.org
> Cc:
> Subject: Re: kern/52070: Keyboard freeze after using touchpad
> Date: Sun, 7 Jan 2024 13:15:41 +0100
>
> Based on a sugestion from Jared - can you test if this far less intrusive
> change works for your machine too?
Unfortunately, it does not work (nor using 0xEB instead of
KBC_SETDEFAULT). Touchpad still not working (that, I don't
really care as I don't use it) but touching it for the first time
still hangs the keyborad (that, I use a lot).
> Index: pckbc.c
> ===================================================================
> RCS file: /cvsroot/src/sys/dev/ic/pckbc.c,v
> retrieving revision 1.65
> diff -c -u -p -r1.65 pckbc.c
> --- pckbc.c 17 Nov 2022 23:57:20 -0000 1.65
> +++ pckbc.c 7 Jan 2024 12:14:35 -0000
> @@ -342,7 +342,7 @@ pckbc_attach(struct pckbc_softc *sc)
> goto nomouse;
> }
> t->t_haveaux = 1;
> - bus_space_write_1(iot, ioh_d, 0, 0x5a); /* a random value */
> + bus_space_write_1(iot, ioh_d, 0, KBC_SETDEFAULT);
Using KBC_SETDEFAULT need #include <dev/pckbport/pckbdreg.h>
somewhere. Anyway, it's not working.
>Unformatted:
(Contact us)
$NetBSD: query-full-pr,v 1.47 2022/09/11 19:34:41 kim Exp $
$NetBSD: gnats_config.sh,v 1.9 2014/08/02 14:16:04 spz Exp $
Copyright © 1994-2024
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.
Home