[DragonFlyBSD - Bug #2557] stock 3.4.1 kernel halts during booting if dm and dm_target_crypt are loaded and RAID controller is present
Pierre Abbat via Redmine
bugtracker-admin at leaf.dragonflybsd.org
Sun May 12 22:38:27 PDT 2013
Issue #2557 has been reported by phma.
Bug #2557: stock 3.4.1 kernel halts during booting if dm and dm_target_crypt are loaded and RAID controller is present
Two computers: darner and zyxomma. Darner is 32-bit running 3.5.0. Zyxomma is 64-bit running 3.4.1 copied from the thumb drive. Both have an encrypted partition.
If the dm lines are not commented out, and I boot it in verbose mode, I get the following:
FQ scheduler policy version 1.1 loaded
wdog: In-kernel automatic watchdog reset enabled
wlan: <802.11 Link Layer>
kbd: new array size 4
kbd1 at kbdmux0
crypto: <crypto core>
No policy for md0 specified, or policy not found
disk scheduler: set policy of md0 to noop
md0: Malloc disk
md0: invalid primary partition table: no magic
hpt27xx: RocketRAID 27xx controller driver v1.0 (Apr 24 2013 20:01:00)
hptrr: RocketRAID 17xx/2xxx SATA controller driver v1.2
If I comment out the lines, it boots normally, but I have to load the dm module manually before starting cryptdisks, and dntpd doesn't work. I had to mount the crypt partition and run dntpd in debug mode to get it to work.
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
More information about the Bugs