Date: Tue, 04 Jul 2023 08:57:23 +0000 From: bugzilla-noreply@freebsd.org To: usb@FreeBSD.org Subject: [Bug 272360] System crash when drive goes idle Message-ID: <bug-272360-19105-l8ws6aAgRf@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-272360-19105@https.bugs.freebsd.org/bugzilla/> References: <bug-272360-19105@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=3D272360 Tomoaki AOKI <junchoon@dec.sakura.ne.jp> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |junchoon@dec.sakura.ne.jp --- Comment #2 from Tomoaki AOKI <junchoon@dec.sakura.ne.jp> --- Just a annoying possibility, but if you attach ThunderBolt-only (or possibly ThunderBolt-capable) external drive to ThunderBolt-capable Type-C port ON B= OOT, it may be recognized as PCIe-attached controller and attached drive. This case, if the drive goes sleep WITH ITS CONTROLLER, it means that PCIe-attached controller suddernly disappear from FreeBSD side. It surely causes hang, unless the port and controller are considered as pluggable. For me, if I attach TB3-only SSD to TB3-capable Type-C port on my ThinkPad = P52, *attaching BEFORE powering on: Recognized as ada drive. *attaching AFTER boot: Not at all recognized. Nothing happenes. On-developing hps@'s USB4/TB3 driver [1] doesn't recognize the drive on both cases. It would be because ntel Titan Ridge Thunderbolt 3 USB controller on my P52= is noto yet supported enough. nhi_wmi0: <Thunderbolt WMI Endpoint> on acpi_wmi0 appears on dmesg, but tha= t's all. Always treated as xchi1. [1] https://github.com/hselasky/usb4 --=20 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-272360-19105-l8ws6aAgRf>