Someone broke USB

classic Classic list List threaded Threaded
39 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Someone broke USB

Steve Kargl
Updated a month old FreeBSD-current to top of tree.
Upon rebooting, the usb no longer functions. No
usb mouse.  No usb external hard drive.  Unplugging
and then re-plugging in external drive does not
cause the drive to spin up.

Logged in as root.`

% usbconfig list
No device match or lack of permissions
% usbsonfig show_ifdrv
No device match or lack of permissions
% usbsonfig dump_all_desc
No device match or lack of permissions
% usbsonfig reset
No device match or lack of permissions

/usr/src/UPDATING does not show any recent entries
for usb.  

So, how does one get usb working, again?

--
Steve

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Someone broke USB

Hans Petter Selasky-6
On 2019-07-06 20:23, Steve Kargl wrote:
> So, how does one get usb working, again?
>
> -- Steve

Can you show dmesg?

--HPS
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Someone broke USB

Steve Kargl
On Sat, Jul 06, 2019 at 08:33:39PM +0200, Hans Petter Selasky wrote:
> On 2019-07-06 20:23, Steve Kargl wrote:
> > So, how does one get usb working, again?
> >
> > -- Steve
>
> Can you show dmesg?
>

This is dmesg.boot for the kernel with the
non-functioning USB stack.  I'll need to
reboot with the older kernel to get the
dmesg.boot for a kernel with a functioning
stack.  Do you need that as well?

---<<BOOT>>---
Copyright (c) 1992-2019 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
        The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 13.0-CURRENT r349777 MOBILE i386
FreeBSD clang version 8.0.1 (branches/release_80 363030) (based on LLVM 8.0.1)
VT(vga): resolution 640x480
CPU: Intel(R) Core(TM)2 Duo CPU     T7250  @ 2.00GHz (1995.05-MHz 686-class CPU)
  Origin="GenuineIntel"  Id=0x6fd  Family=0x6  Model=0xf  Stepping=13
  Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
  Features2=0xe3bd<SSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM>
  AMD Features=0x20100000<NX,LM>
  AMD Features2=0x1<LAHF>
  VT-x: (disabled in BIOS) HLT,PAUSE
  TSC: P-state invariant, performance statistics
real memory  = 4294967296 (4096 MB)
avail memory = 3654860800 (3485 MB)
Event timer "LAPIC" quality 100
ACPI APIC Table: <DELL   M08    >
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
FreeBSD/SMP: 1 package(s) x 2 core(s)
random: unblocking device.
ioapic0: Changing APIC ID to 2
ioapic0 <Version 2.0> irqs 0-23 on motherboard
Launching APs: 1
Timecounter "TSC" frequency 1995047160 Hz quality 1000
random: entropy device external interface
kbd1 at kbdmux0
module_register_init: MOD_LOAD (vesa, 0xf2bd70, 0) error 19
[ath_hal] loaded
[ath_dfs] loaded
[ath_rate] loaded
[ar9300] loaded
[ar5212] loaded
[ar5416] loaded
[ar5211] loaded
[ar5210] loaded
[ath] loaded
nexus0
vtvga0: <VT VGA driver> on motherboard
cryptosoft0: <software crypto> on motherboard
acpi0: <DELL M08    > on motherboard
hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
Timecounter "HPET" frequency 14318180 Hz quality 950
Event timer "HPET" frequency 14318180 Hz quality 450
Event timer "HPET1" frequency 14318180 Hz quality 440
Event timer "HPET2" frequency 14318180 Hz quality 440
cpu0: <ACPI CPU> on acpi0
atrtc0: <AT realtime clock> port 0x70-0x71,0x72-0x77 irq 8 on acpi0
atrtc0: registered as a time-of-day clock, resolution 1.000000s
Event timer "RTC" frequency 32768 Hz quality 0
attimer0: <AT timer> port 0x40-0x43,0x50-0x53 irq 2 on acpi0
Timecounter "i8254" frequency 1193182 Hz quality 0
Event timer "i8254" frequency 1193182 Hz quality 100
Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pcib0: Ignoring 3 range above 4GB (0x120000000-0x317ffffff)
pci0: <ACPI PCI bus> on pcib0
vgapci0: <VGA-compatible display> port 0xeff8-0xefff mem 0xfea00000-0xfeafffff,0xe0000000-0xefffffff irq 16 at device 2.0 on pci0
agp0: <Intel GM965 SVGA controller> on vgapci0
agp0: aperture size is 256M, detected 7676k stolen memory
vgapci0: Boot video device
vgapci1: <VGA-compatible display> mem 0xfeb00000-0xfebfffff at device 2.1 on pci0
uhci0: <Intel 82801H (ICH8) USB controller USB-D> port 0x6f20-0x6f3f irq 20 at device 26.0 on pci0
usbus0 on uhci0
usbus0: 12Mbps Full Speed USB v1.0
uhci1: <Intel 82801H (ICH8) USB controller USB-E> port 0x6f00-0x6f1f irq 21 at device 26.1 on pci0
usbus1 on uhci1
usbus1: 12Mbps Full Speed USB v1.0
ehci0: <Intel 82801H (ICH8) USB 2.0 controller USB2-B> mem 0xfed1c400-0xfed1c7ff irq 22 at device 26.7 on pci0
usbus2: EHCI version 1.0
usbus2 on ehci0
usbus2: 480Mbps High Speed USB v2.0
hdac0: <Intel 82801H HDA Controller> mem 0xfe9fc000-0xfe9fffff irq 21 at device 27.0 on pci0
pcib1: <ACPI PCI-PCI bridge> at device 28.0 on pci0
pcib1: [GIANT-LOCKED]
pcib2: <ACPI PCI-PCI bridge> at device 28.1 on pci0
pcib2: [GIANT-LOCKED]
pci1: <ACPI PCI bus> on pcib2
wpi0: <Intel(R) PRO/Wireless 3945ABG> mem 0xfe8ff000-0xfe8fffff irq 17 at device 0.0 on pci1
pcib3: <ACPI PCI-PCI bridge> at device 28.5 on pci0
pcib3: [GIANT-LOCKED]
pci2: <ACPI PCI bus> on pcib3
bge0: <Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev. 0x00a002> mem 0xfe7f0000-0xfe7fffff irq 17 at device 0.0 on pci2
bge0: CHIP ID 0x0000a002; ASIC REV 0x0a; CHIP REV 0xa0; PCI-E
miibus0: <MII bus> on bge0
brgphy0: <BCM5755 1000BASE-T media interface> PHY 1 on miibus0
brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow
bge0: Ethernet address: 00:1d:09:ba:cc:0d
uhci2: <Intel 82801H (ICH8) USB controller USB-A> port 0x6f80-0x6f9f irq 20 at device 29.0 on pci0
usbus3 on uhci2
usbus3: 12Mbps Full Speed USB v1.0
uhci3: <Intel 82801H (ICH8) USB controller USB-B> port 0x6f60-0x6f7f irq 21 at device 29.1 on pci0
usbus4 on uhci3
usbus4: 12Mbps Full Speed USB v1.0
uhci4: <Intel 82801H (ICH8) USB controller USB-C> port 0x6f40-0x6f5f irq 22 at device 29.2 on pci0
usbus5 on uhci4
usbus5: 12Mbps Full Speed USB v1.0
ehci1: <Intel 82801H (ICH8) USB 2.0 controller USB2-A> mem 0xfed1c000-0xfed1c3ff irq 20 at device 29.7 on pci0
usbus6: EHCI version 1.0
usbus6 on ehci1
usbus6: 480Mbps High Speed USB v2.0
pcib4: <ACPI PCI-PCI bridge> at device 30.0 on pci0
pci3: <ACPI PCI bus> on pcib4
cbb0: <PCI-CardBus Bridge> at device 1.0 on pci3
cardbus0: <CardBus bus> on cbb0
pccard0: <16-bit PCCard bus> on cbb0
pci3: <serial bus, FireWire> at device 1.4 (no driver attached)
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel ICH8M UDMA100 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x6fa0-0x6faf irq 16 at device 31.1 on pci0
ata0: <ATA channel> at channel 0 on atapci0
ahci0: <Intel ICH8M AHCI SATA controller> port 0x6eb0-0x6eb7,0x6eb8-0x6ebb,0x6ec0-0x6ec7,0x6ec8-0x6ecb,0x6ee0-0x6eff mem 0xfe9fb800-0xfe9fbfff irq 17 at device 31.2 on pci0
ahci0: AHCI v1.10 with 3 3Gbps ports, Port Multiplier not supported
ahcich0: <AHCI channel> at channel 0 on ahci0
ahcich2: <AHCI channel> at channel 2 on ahci0
ahciem0: <AHCI enclosure management bridge> on ahci0
acpi_lid0: <Control Method Lid Switch> on acpi0
acpi_button0: <Power Button> on acpi0
acpi_button1: <Sleep Button> on acpi0
acpi_acad0: <AC Adapter> on acpi0
battery0: <ACPI Control Method Battery> on acpi0
battery1: <ACPI Control Method Battery> on acpi0
acpi_tz0: <Thermal Zone> on acpi0
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64,0x62,0x66 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: model GlidePoint, device ID 0
orm0: <ISA Option ROMs> at iomem 0xc0000-0xcefff,0xcf000-0xcffff pnpid ORM0000 on isa0
ppc0: parallel port not found.
est0: <Enhanced SpeedStep Frequency Control> on cpu0
Timecounters tick every 1.000 msec
hdacc0: <Sigmatel STAC9205X HDA CODEC> at cad 0 on hdac0
hdaa0: <Sigmatel STAC9205X Audio Function Group> at nid 1 on hdacc0
pcm0: <Sigmatel STAC9205X (Analog 2.0+HP/2.0)> at nid 13,10 and 12,11 on hdaa0
ugen5.1: <Intel UHCI root HUB> at usbus5
ugen3.1: <Intel UHCI root HUB> at usbus3
ugen1.1: <Intel UHCI root HUB> at usbus1
ugen6.1: <Intel EHCI root HUB> at usbus6
ugen4.1: <Intel UHCI root HUB> at usbus4
ugen2.1: <Intel EHCI root HUB> at usbus2
ugen0.1: <Intel UHCI root HUB> at usbus0
uhub0 on usbus5
uhub0: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus5
uhub1 on usbus3
uhub1: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus3
uhub2 on usbus1
uhub2: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus1
uhub3 on usbus6
uhub3: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus6
uhub5 on usbus2
uhub5: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus2
uhub4 on usbus4
uhub4: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus4
ses0 at ahciem0 bus 0 scbus3 target 0 lun 0
ses0: <AHCI SGPIO Enclosure 2.00 0001> SEMB S-E-S 2.00 device
ses0: SEMB SES Device
ada0 at ahcich0 bus 0 scbus1 target 0 lun 0
ada0: <Patriot Burst SBFM91.0> ACS-4 ATA SATA 3.x device
ada0: Serial Number 1B0607771A0800257271
ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada0: Command Queueing enabled
ada0: 114473MB (234441648 512 byte sectors)
ses0: ada0 in 'Slot 00', SATA Slot: scbus1 target 0
cd0 at ata0 bus 0 scbus0 target 0 lun 0
cd0: <SONY CDRWDVD CRX880A KD09> Removable CD-ROM SCSI device
cd0: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO 65534bytes)
cd0: 680MB (348277 2048 byte sectors)
Trying to mount root from ufs:/dev/ada0s1a [rw]...
uhub1: 2 ports with 2 removable, self powered
uhub0: 2 ports with 2 removable, self powered
uhub2: 2 ports with 2 removable, self powered
uhub4: 2 ports with 2 removable, self powered
uhub5: 4 ports with 4 removable, self powered
uhub3: 6 ports with 6 removable, self powered
wlan0: Ethernet address: 00:1c:bf:90:ab:44
lo0: link state changed to UP
wlan0: link state changed to UP

--
Steve
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Someone broke USB

Steve Kargl
In reply to this post by Hans Petter Selasky-6
On Sat, Jul 06, 2019 at 08:33:39PM +0200, Hans Petter Selasky wrote:
> On 2019-07-06 20:23, Steve Kargl wrote:
> > So, how does one get usb working, again?
> >
> > -- Steve
>
> Can you show dmesg?
>

It looks like the enumeration of busses and devices has changed.
grepping for uhub and usbus of the working and broken dmesg.boot
gives

% grep uhub dmesg.boot.working
uhub0: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus6
uhub1: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus4
uhub2: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus3
uhub3: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus1
uhub4: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus5
uhub5: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus2
uhub6: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0
uhub1: 2 ports with 2 removable, self powered
uhub2: 2 ports with 2 removable, self powered
uhub4: 2 ports with 2 removable, self powered
uhub3: 2 ports with 2 removable, self powered
uhub6: 2 ports with 2 removable, self powered
uhub5: 4 ports with 4 removable, self powered
uhub0: 6 ports with 6 removable, self powered
umass0 on uhub0
ukbd0 on uhub1
ums0 on uhub1
uhid0 on uhub1

% grep uhub dmesg.boot.broken
uhub0 on usbus5
uhub0: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus5
uhub1 on usbus3
uhub1: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus3
uhub2 on usbus1
uhub2: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus1
uhub3 on usbus6
uhub3: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus6
uhub5 on usbus2
uhub5: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus2
uhub4 on usbus4
uhub4: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus4
uhub1: 2 ports with 2 removable, self powered
uhub0: 2 ports with 2 removable, self powered
uhub2: 2 ports with 2 removable, self powered
uhub4: 2 ports with 2 removable, self powered
uhub5: 4 ports with 4 removable, self powered
uhub3: 6 ports with 6 removable, self powered

****
% grep usbus dmesg.boot.working
usbus0 on uhci0
usbus0: 12Mbps Full Speed USB v1.0
usbus1 on uhci1
usbus1: 12Mbps Full Speed USB v1.0
usbus2: EHCI version 1.0
usbus2 on ehci0
usbus2: 480Mbps High Speed USB v2.0
usbus3 on uhci2
usbus3: 12Mbps Full Speed USB v1.0
usbus4 on uhci3
usbus4: 12Mbps Full Speed USB v1.0
usbus5 on uhci4
usbus5: 12Mbps Full Speed USB v1.0
usbus6: EHCI version 1.0
usbus6 on ehci1
usbus6: 480Mbps High Speed USB v2.0
ugen6.1: <Intel EHCI root HUB> at usbus6
uhub0: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus6
ugen4.1: <Intel UHCI root HUB> at usbus4
uhub1: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus4
ugen3.1: <Intel UHCI root HUB> at usbus3
uhub2: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus3
ugen1.1: <Intel UHCI root HUB> at usbus1
uhub3: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus1
ugen5.1: <Intel UHCI root HUB> at usbus5
uhub4: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus5
ugen2.1: <Intel EHCI root HUB> at usbus2
uhub5: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus2
ugen0.1: <Intel UHCI root HUB> at usbus0
uhub6: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0
ugen6.2: <Toshiba External USB HDD> at usbus6
umass0: <Bulk Only Interface> on usbus6
ugen4.2: <Logitech USB Receiver> at usbus4
ukbd0: <Logitech USB Receiver, class 0/0, rev 2.00/12.03, addr 2> on usbus4
ums0: <Logitech USB Receiver, class 0/0, rev 2.00/12.03, addr 2> on usbus4
uhid0: <Logitech USB Receiver, class 0/0, rev 2.00/12.03, addr 2> on usbus4

% grep usbus dmesg.boot.broken
usbus0 on uhci0
usbus0: 12Mbps Full Speed USB v1.0
usbus1 on uhci1
usbus1: 12Mbps Full Speed USB v1.0
usbus2: EHCI version 1.0
usbus2 on ehci0
usbus2: 480Mbps High Speed USB v2.0
usbus3 on uhci2
usbus3: 12Mbps Full Speed USB v1.0
usbus4 on uhci3
usbus4: 12Mbps Full Speed USB v1.0
usbus5 on uhci4
usbus5: 12Mbps Full Speed USB v1.0
usbus6: EHCI version 1.0
usbus6 on ehci1
usbus6: 480Mbps High Speed USB v2.0
ugen5.1: <Intel UHCI root HUB> at usbus5
ugen3.1: <Intel UHCI root HUB> at usbus3
ugen1.1: <Intel UHCI root HUB> at usbus1
ugen6.1: <Intel EHCI root HUB> at usbus6
ugen4.1: <Intel UHCI root HUB> at usbus4
ugen2.1: <Intel EHCI root HUB> at usbus2
ugen0.1: <Intel UHCI root HUB> at usbus0
uhub0 on usbus5
uhub0: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus5
uhub1 on usbus3
uhub1: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus3
uhub2 on usbus1
uhub2: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus1
uhub3 on usbus6
uhub3: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus6
uhub5 on usbus2
uhub5: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus2
uhub4 on usbus4
uhub4: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus4

--
Steve
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Someone broke USB

Hans Petter Selasky-6
On 2019-07-06 21:41, Steve Kargl wrote:

> On Sat, Jul 06, 2019 at 08:33:39PM +0200, Hans Petter Selasky wrote:
>> On 2019-07-06 20:23, Steve Kargl wrote:
>>> So, how does one get usb working, again?
>>>
>>> -- Steve
>>
>> Can you show dmesg?
>>
>
> It looks like the enumeration of busses and devices has changed.
> grepping for uhub and usbus of the working and broken dmesg.boot
> gives
>

Are you able to bisect the commit introducing the bad behaviour?

--HPS

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Someone broke USB

Steve Kargl
On Sat, Jul 06, 2019 at 10:50:59PM +0200, Hans Petter Selasky wrote:

> On 2019-07-06 21:41, Steve Kargl wrote:
> > On Sat, Jul 06, 2019 at 08:33:39PM +0200, Hans Petter Selasky wrote:
> >> On 2019-07-06 20:23, Steve Kargl wrote:
> >>> So, how does one get usb working, again?
> >>>
> >>> -- Steve
> >>
> >> Can you show dmesg?
> >>
> >
> > It looks like the enumeration of busses and devices has changed.
> > grepping for uhub and usbus of the working and broken dmesg.boot
> > gives
> >
>
> Are you able to bisect the commit introducing the bad behaviour?
>

I'll give it a shot.  I have two revision number to work with.

--
Steve
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Someone broke USB

Ian Lepore-3
On Sat, 2019-07-06 at 14:06 -0700, Steve Kargl wrote:

> On Sat, Jul 06, 2019 at 10:50:59PM +0200, Hans Petter Selasky wrote:
> > On 2019-07-06 21:41, Steve Kargl wrote:
> > > On Sat, Jul 06, 2019 at 08:33:39PM +0200, Hans Petter Selasky
> > > wrote:
> > > > On 2019-07-06 20:23, Steve Kargl wrote:
> > > > > So, how does one get usb working, again?
> > > > >
> > > > > -- Steve
> > > >
> > > > Can you show dmesg?
> > > >
> > >
> > > It looks like the enumeration of busses and devices has changed.
> > > grepping for uhub and usbus of the working and broken dmesg.boot
> > > gives
> > >
> >
> > Are you able to bisect the commit introducing the bad behaviour?
> >
>
> I'll give it a shot.  I have two revision number to work with.
>

It seems almost certain to be r349161 that causes the problem.

-- Ian

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Someone broke USB

Hans Petter Selasky-6
Hi Takanori,

Can you have a look at the issues reported in this thread?

Are the ACPI functions you call thread safe? USB will enumerate multiple
busses at the same time.

--HPS

On 2019-07-06 23:08, Ian Lepore wrote:

> On Sat, 2019-07-06 at 14:06 -0700, Steve Kargl wrote:
>> On Sat, Jul 06, 2019 at 10:50:59PM +0200, Hans Petter Selasky wrote:
>>> On 2019-07-06 21:41, Steve Kargl wrote:
>>>> On Sat, Jul 06, 2019 at 08:33:39PM +0200, Hans Petter Selasky
>>>> wrote:
>>>>> On 2019-07-06 20:23, Steve Kargl wrote:
>>>>>> So, how does one get usb working, again?
>>>>>>
>>>>>> -- Steve
>>>>>
>>>>> Can you show dmesg?
>>>>>
>>>>
>>>> It looks like the enumeration of busses and devices has changed.
>>>> grepping for uhub and usbus of the working and broken dmesg.boot
>>>> gives
>>>>
>>>
>>> Are you able to bisect the commit introducing the bad behaviour?
>>>
>>
>> I'll give it a shot.  I have two revision number to work with.
>>
>
> It seems almost certain to be r349161 that causes the problem.
>


_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Someone broke USB

Thomas Laus
In reply to this post by Hans Petter Selasky-6
On 2019-07-06 16:50, Hans Petter Selasky wrote:
>
> Are you able to bisect the commit introducing the bad behaviour?
>
I built and booted r349160.  My 'boot mount waiting for USBUS7 -> USBUS0
issue went away but the startup halted at the 'mounting late
filesystems' step of rc.conf.  I had the USB issue at r349161 but
building and loading the previous commit has other problems.

Tom


--
Public Keys:
PGP KeyID = 0x5F22FDC1
GnuPG KeyID = 0x620836CF
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Someone broke USB

Steve Kargl
In reply to this post by Ian Lepore-3
On Sat, Jul 06, 2019 at 03:08:13PM -0600, Ian Lepore wrote:

> On Sat, 2019-07-06 at 14:06 -0700, Steve Kargl wrote:
> > On Sat, Jul 06, 2019 at 10:50:59PM +0200, Hans Petter Selasky wrote:
> > > On 2019-07-06 21:41, Steve Kargl wrote:
> > > > On Sat, Jul 06, 2019 at 08:33:39PM +0200, Hans Petter Selasky
> > > > wrote:
> > > > > On 2019-07-06 20:23, Steve Kargl wrote:
> > > > > > So, how does one get usb working, again?
> > > > > >
> > > > > > -- Steve
> > > > >
> > > > > Can you show dmesg?
> > > > >
> > > >
> > > > It looks like the enumeration of busses and devices has changed.
> > > > grepping for uhub and usbus of the working and broken dmesg.boot
> > > > gives
> > > >
> > >
> > > Are you able to bisect the commit introducing the bad behaviour?
> > >
> >
> > I'll give it a shot.  I have two revision number to work with.
> >
>
> It seems almost certain to be r349161 that causes the problem.
>

I've backed out the change, and the buildkernel is currently
running.  It won't finish for an hour or so (old hardware and
rebuilding another project).

--
Steve
20170425 https://www.youtube.com/watch?v=VWUpyCsUKR4
20161221 https://www.youtube.com/watch?v=IbCHE-hONow
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Someone broke USB

Steve Kargl
On Sat, Jul 06, 2019 at 04:14:53PM -0700, Steve Kargl wrote:
> On Sat, Jul 06, 2019 at 03:08:13PM -0600, Ian Lepore wrote:
> >
> > It seems almost certain to be r349161 that causes the problem.
> >
>
> I've backed out the change, and the buildkernel is currently
> running.  It won't finish for an hour or so (old hardware and
> rebuilding another project).
>

I can confirm that r349161 is the cause of my problem.

--
Steve
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Someone broke USB

Hans Petter Selasky-6
On 2019-07-07 10:05, Steve Kargl wrote:

> On Sat, Jul 06, 2019 at 04:14:53PM -0700, Steve Kargl wrote:
>> On Sat, Jul 06, 2019 at 03:08:13PM -0600, Ian Lepore wrote:
>>>
>>> It seems almost certain to be r349161 that causes the problem.
>>>
>>
>> I've backed out the change, and the buildkernel is currently
>> running.  It won't finish for an hour or so (old hardware and
>> rebuilding another project).
>>
>
> I can confirm that r349161 is the cause of my problem.
>

Hi,

Can you try the latest -current with:
debug.acpi.disabled="usb"

In /boot/loader.conf ?

Also can you dump the ACPI tables:
acpidump -dt > dump.txt

In the failing and working case can you show the differences in output from:
devinfo

--HPS
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Someone broke USB

Steve Kargl
On Sun, Jul 07, 2019 at 11:53:27AM +0200, Hans Petter Selasky wrote:

> On 2019-07-07 10:05, Steve Kargl wrote:
> > On Sat, Jul 06, 2019 at 04:14:53PM -0700, Steve Kargl wrote:
> >> On Sat, Jul 06, 2019 at 03:08:13PM -0600, Ian Lepore wrote:
> >>>
> >>> It seems almost certain to be r349161 that causes the problem.
> >>>
> >>
> >> I've backed out the change, and the buildkernel is currently
> >> running.  It won't finish for an hour or so (old hardware and
> >> rebuilding another project).
> >>
> >
> > I can confirm that r349161 is the cause of my problem.
> >
>
> Hi,
>
> Can you try the latest -current with:
> debug.acpi.disabled="usb"

Reverting my tree to include r349161, updating to top-of-tree,
the new kernel boots and USB works if the above sysctl is set.

>
> In /boot/loader.conf ?
>
> Also can you dump the ACPI tables:
> acpidump -dt > dump.txt

This a 7720 line, 262KB file, do you want me to send it
to you in private email or put in my home directory on
freefall (i.e., [hidden email]).

>
> In the failing and working case can you show the differences in output from:
> devinfo
>

Here's the diff when r349161 was revert (devinfo.working) and
top-of-tree with the sysctl set.

--- devinfo.working     2019-07-07 08:48:26.906454000 -0700
+++ devinfo.acpi_disabled       2019-07-07 09:44:09.225520000 -0700
@@ -1,8 +1,8 @@
 nexus0
+  cryptosoft0
   vtvga0
   apic0
   ram0
-  cryptosoft0
   acpi0
     cpu0
       acpi_perf0
@@ -67,10 +67,10 @@
             uhub3
         uhci1
           usbus1
-            uhub6
+            uhub2
         ehci0
           usbus2
-            uhub2
+            uhub5
         hdac0
           hdacc0
             hdaa0
@@ -89,7 +89,7 @@
             uhub1
         uhci3
           usbus4
-            uhub5
+            uhub6
               ukbd0
               ums0
               uhid0

--
Steve
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Someone broke USB

Hans Petter Selasky-6
On 2019-07-07 18:54, Steve Kargl wrote:
> This a 7720 line, 262KB file, do you want me to send it
> to you in private email or put in my home directory on
> freefall (i.e.,[hidden email]).

Send it to the people CC'ed, except the list.

--HPS
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Someone broke USB

Hans Petter Selasky-6
On 2019-07-07 18:58, Hans Petter Selasky wrote:
> On 2019-07-07 18:54, Steve Kargl wrote:
>> This a 7720 line, 262KB file, do you want me to send it
>> to you in private email or put in my home directory on
>> freefall (i.e.,[hidden email]).
>
> Send it to the people CC'ed, except the list.
>

Hi,

I'm wondering if there is a race by default, that wee need to explore
the root HUBs in a certain order?

Can you try to reverse the order in usb_needs_explore_all() in
sys/dev/usb and put a pause("W", hz); call between each iteration?

--HPS

> void
> usb_needs_explore_all(void)
> {
>         struct usb_bus *bus;
>         devclass_t dc;
>         device_t dev;
>         int max;
>
>         DPRINTFN(3, "\n");
>
>         dc = usb_devclass_ptr;
>         if (dc == NULL) {
>                 DPRINTFN(0, "no devclass\n");
>                 return;
>         }
>         /*
>          * Explore all USB buses in parallel.
>          */
>         max = devclass_get_maxunit(dc);
>         while (max >= 0) {
>                 dev = devclass_get_device(dc, max);
>                 if (dev) {
>                         bus = device_get_softc(dev);
>                         if (bus) {
>                                 usb_needs_explore(bus, 1);
>                         }
>                 }
>                 max--;
>         }
> }
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Someone broke USB

Steve Kargl
On Sun, Jul 07, 2019 at 08:27:18PM +0200, Hans Petter Selasky wrote:

> On 2019-07-07 18:58, Hans Petter Selasky wrote:
> > On 2019-07-07 18:54, Steve Kargl wrote:
> >> This a 7720 line, 262KB file, do you want me to send it
> >> to you in private email or put in my home directory on
> >> freefall (i.e.,[hidden email]).
> >
> > Send it to the people CC'ed, except the list.
> >
>
>
> I'm wondering if there is a race by default, that wee need to explore
> the root HUBs in a certain order?
>
> Can you try to reverse the order in usb_needs_explore_all() in
> sys/dev/usb and put a pause("W", hz); call between each iteration?
>

I assume the pause goes after "max--;" statement.  I also
assume you want the info with the sysctl removed from
/boot/loader.conf.

I'm in the middle of upgrading ImageMagick6 with portmaster.
As soon as it finishes, I get the info for you.

--
Steve
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Someone broke USB

Hans Petter Selasky-6
On 2019-07-07 20:58, Steve Kargl wrote:
> I assume the pause goes after "max--;" statement.  I also
> assume you want the info with the sysctl removed from
> /boot/loader.conf.

You can play with it and see what happens.

--HPS
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Someone broke USB

Steve Kargl
On Sun, Jul 07, 2019 at 09:10:00PM +0200, Hans Petter Selasky wrote:
> On 2019-07-07 20:58, Steve Kargl wrote:
> > I assume the pause goes after "max--;" statement.  I also
> > assume you want the info with the sysctl removed from
> > /boot/loader.conf.
>
> You can play with it and see what happens.
>

Built kernel with pause() added, and commented out the
sysctl in /boot/loader.conf.  One reboot took a long
time to get to the a login prompt, but all of my USB
devices were found.  A few reboots appeared to hang
after probing the USB mouse (or perhaps I was too
impatient).

On a side note, it seems the wpi0 mapped to wlan0
is now unstable.  Luckily, I have an ath(4) pccard
that I can use instead of the builtin wifi of the
laptop.  The joys of current. :-)

--
Steve
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Someone broke USB

Hans Petter Selasky-6
On 2019-07-07 22:36, Steve Kargl wrote:

> On Sun, Jul 07, 2019 at 09:10:00PM +0200, Hans Petter Selasky wrote:
>> On 2019-07-07 20:58, Steve Kargl wrote:
>>> I assume the pause goes after "max--;" statement.  I also
>>> assume you want the info with the sysctl removed from
>>> /boot/loader.conf.
>>
>> You can play with it and see what happens.
>>
>
> Built kernel with pause() added, and commented out the
> sysctl in /boot/loader.conf.  One reboot took a long
> time to get to the a login prompt, but all of my USB
> devices were found.  A few reboots appeared to hang
> after probing the USB mouse (or perhaps I was too
> impatient).
>
> On a side note, it seems the wpi0 mapped to wlan0
> is now unstable.  Luckily, I have an ath(4) pccard
> that I can use instead of the builtin wifi of the
> laptop.  The joys of current. :-)
>
It sounds like we have a race there and that a wait between the probes
solves it.

Can you try the attached patch on top of -current:

--HPS

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

usb_delay.diff (1K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Someone broke USB

Steve Kargl
On Sun, Jul 07, 2019 at 10:46:10PM +0200, Hans Petter Selasky wrote:

> On 2019-07-07 22:36, Steve Kargl wrote:
> > On Sun, Jul 07, 2019 at 09:10:00PM +0200, Hans Petter Selasky wrote:
> >> On 2019-07-07 20:58, Steve Kargl wrote:
> >>> I assume the pause goes after "max--;" statement.  I also
> >>> assume you want the info with the sysctl removed from
> >>> /boot/loader.conf.
> >>
> >> You can play with it and see what happens.
> >>
> >
> > Built kernel with pause() added, and commented out the
> > sysctl in /boot/loader.conf.  One reboot took a long
> > time to get to the a login prompt, but all of my USB
> > devices were found.  A few reboots appeared to hang
> > after probing the USB mouse (or perhaps I was too
> > impatient).
> >
> > On a side note, it seems the wpi0 mapped to wlan0
> > is now unstable.  Luckily, I have an ath(4) pccard
> > that I can use instead of the builtin wifi of the
> > laptop.  The joys of current. :-)
> >
>
> It sounds like we have a race there and that a wait between the probes
> solves it.
>
> Can you try the attached patch on top of -current:
>

Hans, this patch seems to work.  Just booted a kernel and all
my devices were correctly found.  Thanks for your help.


--
Steve
20170425 https://www.youtube.com/watch?v=VWUpyCsUKR4
20161221 https://www.youtube.com/watch?v=IbCHE-hONow
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
12