Date: Thu, 18 May 2017 09:08:45 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 219372] ataraid does not recognized by new kernel Message-ID: <bug-219372-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219372 Bug ID: 219372 Summary: ataraid does not recognized by new kernel Product: Base System Version: 10.0-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: oklaspec@gmail.com Created attachment 182686 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D182686&action= =3Dedit additional options to generic kernel config added The kernel 9.3 works fine long time on two mirror disks onboard nVidia MediaShield conroller. The 10.3 release builded from svn and installed and does not boot. The kernel config is generic with some additions (included in attach). There 8.3 version installed available on separated disk. The 8.3 was loaded and 9.3 kernel was builded from sources. The newely installed kernel 9.3 (builded and installed from 8.3) does not worked now too as 10.3 (may be source slice confused) So 8.3 can see ataraid onboard nVidia "ar0" device. Also 8.3 can see slices like "ad0s1a" on separated disks from raid. And 9.3 and 10.3 does NOT see "ar0". Also 9.3 and 10.3 does NOT see slices like "ada0s1a" on separated disks from raid. Attachments: dmesg of 8.3 (worked) and 9.3 (not worked), kernel additions. Is it bug or what wrong with config for current kernel? Any help or clarifications is very appreciated. --=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-219372-8>