Date: Sat, 12 Aug 2017 16:32:17 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 221075] regression: 11.1 is unable to mount ZFS / on boot Message-ID: <bug-221075-3630-Q2yrN6UxzA@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-221075-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-221075-3630@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=221075 --- Comment #13 from seschwar@gmail.com --- So I had another go at this... (In reply to Marius Strobl from comment #12) > (is the card reader you mention a USB one?). nope: $ pciconf -lv (...) none2@pci0:11:0:0: class=0x0c0010 card=0x04a31028 chip=0x11f71217 rev=0x05 hdr=0x00 vendor = 'O2 Micro, Inc.' device = 'OZ600 1394a-2000 Controller' class = serial bus subclass = FireWire none3@pci0:11:0:1: class=0x080501 card=0x04a31028 chip=0x83201217 rev=0x05 hdr=0x00 vendor = 'O2 Micro, Inc.' device = 'OZ600RJ1/OZ900RJ1 SD/MMC Card Reader Controller' class = base peripheral subclass = SD host controller none4@pci0:11:0:2: class=0x018000 card=0x04a31028 chip=0x83301217 rev=0x05 hdr=0x00 vendor = 'O2 Micro, Inc.' device = 'OZ600 MS/xD Controller' class = mass storage > The one thing that comes to my mind is that since r318197, mmcsd(4) depends > on geom_flasmap(4) and that the latter might cause some interaction with ZFS. > (...) One - not necessarily conclusive - way to > test the theory of interaction between geom_flasmap(4) and ZFS would be to use > a kernel built from a configuration with mmcsd(4) removed, so this dependency > isn't dragged in. Ok, I've build a 11.1 kernel using the following configuration: $ cat /usr/src/sys/amd64/conf/CUSTOM include GENERIC ident CUSTOM nodevice mmc nodevice mmcsd nodevice sdhci This kernel is indeed capable of mounting the root filesystem on my ZFS pool! So your guess that base r318197 is not actually the cause of this, but merely exposes the issue is probably spot on. 12.0-CURRENT not exhibiting the issue raises the question if the underlying problem is fixed there, or just happens to not be triggered. Is there a way for me to provide more information on this? Maybe boot with kern.geom.debugflags set to some appropriate value? -- 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-221075-3630-Q2yrN6UxzA>