Date: Mon, 17 Nov 2014 20:59:46 +0100 From: Kurt Jaeger <lists@opsec.eu> To: Steven Hartland <killing@multiplay.co.uk> Cc: freebsd-stable@freebsd.org Subject: Re: aacraid drives missing after update 10.0 -> 10.1 ? Message-ID: <20141117195946.GM44537@home.opsec.eu> In-Reply-To: <546A24CD.6040600@multiplay.co.uk> References: <20141116213910.GF44537@home.opsec.eu> <CAHEMsqbKHFatgWuVRbibxpFdmPLnnB76WWMfhcjoQjtk8g8udw@mail.gmail.com> <20141117143323.GH44537@home.opsec.eu> <5133298B-F884-4203-92A0-7D0FCFF72FE1@sarenet.es> <20141117145204.GI44537@home.opsec.eu> <D9A7B574-3C8D-4F6C-A87F-321B92C9A12A@sarenet.es> <546A24CD.6040600@multiplay.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi! > >>>> It's the GENERIC kernel. > >>> That's curious. In order to have direct access to the disks I > >>> had to patch aac_cam.c. Maybe you were > >>> using a patched file and you forgot? > >> I upgraded using freebsd-update and upgraded GENERIC. What additional > >> patch would be needed ? > > Beware, it's just my case, not necessarily others'. [...] > As you say that looks very hack. I'm wondering if the following commit > was the cause: > https://svnweb.freebsd.org/base?view=revision&revision=257847 > > Specifically: > https://svnweb.freebsd.org/base/head/sys/dev/aacraid/aacraid_cam.c?annotate=257847&pathrev=257847#l1231 > > Could you try backing that out and see if it fixes it for you? I've opened PR 195119 to track this. -- pi@opsec.eu +49 171 3101372 6 years to go !
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20141117195946.GM44537>