https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
--- Comment #28 from Stephen McConnell <s...@freebsd.org> --- Hi Karli, I don't see anything in the logs that makes me think this is the same issue as the original issue. Can you explain why you think so? The original problem was a spinup delay that the driver needed to account for. There were messages regarding SATA Identify in the original logs. For your current issue, I don't see anything in the logs that makes me think this is a driver problem. What is happening is that the driver is getting SAS Topology Change List events when you insert the SATA disk. But, in order for the driver to enumerate that disk, the PhyStatus must by "Target Added". In your case, the PhyStatus is always "PHY Link Status Change" and never "Target Added". So, this tells me that the Firmware is never getting enough information from that disk to add it. All I can think of is that something is wrong with your disk. Do you have this issue with any other disk? Do you know that this disk is operating normally in other cases? Right now, I don't see any problem with the driver for this. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
