Date: Sat, 19 Sep 2015 12:14:41 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-threads@FreeBSD.org Subject: [Bug 201421] locking issues prevent new process creation Message-ID: <bug-201421-16-vxQe9molEA@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-201421-16@https.bugs.freebsd.org/bugzilla/> References: <bug-201421-16@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201421 FreeBSD@ShaneWare.Biz changed: What |Removed |Added ---------------------------------------------------------------------------- Component|threads |usb --- Comment #2 from FreeBSD@ShaneWare.Biz --- Now running -FreeBSD leader.local 10.2-STABLE FreeBSD 10.2-STABLE #17 r287561: Fri Sep 11 12:15:25 ACST 2015 root@leader.local:/usr/obj/usr/src/sys/GENERIC amd64 It seems I can add some useful light to this issue. The issue appears to be usb related, as I mentioned I have had times of being unable to mount usb memsticks which has been getting more frequent, when this fails I have recently been able to go as long as 3 weeks uptime. After a recent time of usb memstick failing, I checked that I was able to mount the device when inserted into a rear usb3 port, also while mounting the memstick fails I can turn on a midi keyboard (connected to rear usb2 port), have devd load the snd_uaudio kmod and have it work as expected. The memstick device insertion shows in dmesg (including specifying da4 for the device) but the device entry fails to get created, or the partition device fails, that is sometimes /dev/da4 will exist but not /dev/da4s1, further removal and insertion will keep showing in dmesg but not /dev. This would indicate that the failing to create devices is restricted to one usb bus. This lead me to recall that as well as the front mounted usb ports I have an internal usb multi card reader connected to the motherboard. After installing 9.0 I was unable to mount cards inserted into this reader so have never used it since. I have noticed this device appears to go to sleep and it's devices get removed (da0-da3) after which adding a memstick will get da0 instead of the normal da4. After disconnecting this device I am now approaching 3 days uptime which is the best I have had in a year while still being able to mount usb memsticks. So it would appear that after installing 10.1 this device is causing the usb scanning/device creation to fail, which is a regression from 9.x. Possibly it is the device going to sleep or failing to wake that causes a long response which holds a lock too long? This machine has an ASUS P8H61-M LE/USB3 motherboard http://www.asus.com/au/Motherboards/P8H61M_LEUSB3/specifications/ which has an Intel H61 express chipset and Asmedia USB3 controller With the full boot.dmesg attached the usb bus and the card reader device was showing up as -- ehci0: <EHCI (generic) USB 2.0 controller> mem 0xfb307000-0xfb3073ff irq 23 at device 26.0 on pci0 usbus0: EHCI version 1.0 usbus0 on ehci0 xhci0: <ASMedia ASM1042 USB 3.0 controller> mem 0xfb100000-0xfb107fff irq 19 at device 0.0 on pci5 xhci0: 32 byte context size. usbus1 on xhci0 pcib6: <ACPI PCI-PCI bridge> irq 17 at device 28.4 on pci0 pci6: <ACPI PCI bus> on pcib6 pcib7: <ACPI PCI-PCI bridge> irq 16 at device 0.0 on pci6 pci7: <ACPI PCI bus> on pcib7 pcib8: <ACPI PCI-PCI bridge> irq 16 at device 28.5 on pci0 pci8: <ACPI PCI bus> on pcib8 ehci1: <EHCI (generic) USB 2.0 controller> mem 0xfb306000-0xfb3063ff irq 23 at device 29.0 on pci0 usbus2: EHCI version 1.0 usbus2 on ehci1 usbus1: 5.0Gbps Super Speed USB v3.0 usbus2: 480Mbps High Speed USB v2.0 ugen0.1: <Intel> at usbus0 uhub0: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus0 ugen1.1: <0x1b21> at usbus1 uhub1: <0x1b21 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus1 ugen2.1: <Intel> at usbus2 uhub2: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus2 Root mount waiting for: usbus2 usbus0 uhub0: 2 ports with 2 removable, self powered uhub2: 2 ports with 2 removable, self powered Root mount waiting for: usbus2 usbus0 ugen0.2: <vendor 0x8087> at usbus0 uhub3: <vendor 0x8087 product 0x0024, class 9/0, rev 2.00/0.00, addr 2> on usbus0 ugen2.2: <vendor 0x8087> at usbus2 uhub4: <vendor 0x8087 product 0x0024, class 9/0, rev 2.00/0.00, addr 2> on usbus2 uhub3: 4 ports with 4 removable, self powered Root mount waiting for: usbus2 usbus0 uhub4: 6 ports with 6 removable, self powered ugen0.3: <Generic> at usbus0 umass0: <Generic Mass Storage Device, class 0/0, rev 2.00/1.29, addr 3> on usbus0 umass0: SCSI over Bulk-Only; quirks = 0x4001 umass0:5:0:-1: Attached to scbus5 da0 at umass-sim0 bus 0 scbus5 target 0 lun 0 da0: <Generic USB SD Reader 1.00> Removable Direct Access SCSI-0 device da0: Serial Number 058F312D81B da0: 40.000MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present da0: quirks=0x2<NO_6_BYTE> da1 at umass-sim0 bus 0 scbus5 target 0 lun 1 da1: <Generic USB CF Reader 1.01> Removable Direct Access SCSI-0 device da1: Serial Number 058F312D81B da1: 40.000MB/s transfers da1: Attempt to query device size failed: NOT READY, Medium not present da1: quirks=0x2<NO_6_BYTE> da2 at umass-sim0 bus 0 scbus5 target 0 lun 2 da2: <Generic USB SM Reader 1.02> Removable Direct Access SCSI-0 device da2: Serial Number 058F312D81B da2: 40.000MB/s transfers da2: Attempt to query device size failed: NOT READY, Medium not present da2: quirks=0x2<NO_6_BYTE> ugen2.3: <vendor 0x1a40> at usbus2 uhub5: <vendor 0x1a40 USB 2.0 Hub, class 9/0, rev 2.00/1.11, addr 3> on usbus2 da3 at umass-sim0 bus 0 scbus5 target 0 lun 3 da3: <Generic USB MS Reader 1.03> Removable Direct Access SCSI-0 device da3: Serial Number 058F312D81B da3: 40.000MB/s transfers da3: Attempt to query device size failed: NOT READY, Medium not present da3: quirks=0x2<NO_6_BYTE> -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-201421-16-vxQe9molEA>