[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: kern/51079: Accessing unconfigured cgd causes panic
On Apr 21, 12:00am, john%ziaspace.com@localhost (John Klos) wrote:
-- Subject: Re: kern/51079: Accessing unconfigured cgd causes panic
| The following reply was made to PR kern/51079; it has been noted by GNATS.
| From: John Klos <john%ziaspace.com@localhost>
| To: gnats-bugs%NetBSD.org@localhost
| Subject: Re: kern/51079: Accessing unconfigured cgd causes panic
| Date: Wed, 20 Apr 2016 23:44:37 +0000 (UTC)
| More information:
| This doesn't happen with a properly configured cgd. I get "DIOCGDINFO:
| Device not configured". So this only happens when you disklabel a device
| and put the first 4.2BSD partition at the beginning of a disk instead of
| 32 blocks (or however many - don't know what the threshold is) away from
| the beginning. After running cgdconfig, attempts to access the cgd give a
| write error. After running cgdconfig -u and trying to access the cgd, the
| machine panics.
| It might be worth mentioning in the documentation that full disk
| encryption can't be used by specifying a disklabel slice which covers the
| whole disk.
We should fix the panic anyway...
Main Index |
Thread Index |