Date: Wed, 28 Sep 2016 11:41:34 +0200 From: Borja Marcos <borjam@sarenet.es> To: Eric van Gyzen <vangyzen@FreeBSD.org> Cc: Jan Henrik Sylvester <me@janh.de>, FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org> Subject: Re: Status of PCIe Hotplug? Message-ID: <C6B66C2F-1F4F-40DA-A04D-33168104A1E5@sarenet.es> In-Reply-To: <58f84457-d775-3023-5727-a326bc8df722@FreeBSD.org> References: <D7E110DB-EF6D-41DD-8D69-A021422916FA@sarenet.es> <791ee95b-ab4e-f07e-6b8d-0e0b6c49ceb0@janh.de> <E9D08BBA-762D-4F27-A853-645764235209@sarenet.es> <58f84457-d775-3023-5727-a326bc8df722@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 27 Sep 2016, at 17:51, Eric van Gyzen <vangyzen@FreeBSD.org> wrote: > > > To my knowledge, all the necessary PCIe-layer code is present. However, > that's just one layer: Many drivers will likely need changes in order > to cope with surprise removal of their devices. Thank you very much, that’s what I needed to know :) I saw that the bits were indeed present, but I was wondering wether I should expect it to work or not. > For that reason, HotPlug needs a lot of testing on a variety of > platforms. The FreeBSD developer base is much smaller than its user > base, of course, so the variety of our testing is rather limited. You > can help immensely by giving us detailed bug reports, either on a > mailing list or in Bugzilla. For a panic, the panic messages and stack > trace of the current thread will be very helpful. Complete crashinfo(8) > output would be great. Of course. Unfortunately, due to poor timing and a DOA server last month, this server is in a countdown to get into production tomorrow running Solaris, but I’ll try to get whatever I can today. Thanks! Borja.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C6B66C2F-1F4F-40DA-A04D-33168104A1E5>