On 19 Feb 2017, at 21:30, Steve Kargl wrote:
>
> Looks like I picked the wrong time to update a month old.
>
> Problem #1: 'kldload -v i915kms.ko' locks up the system. No
> panic. No messages logged. No keyboard response. Black
> screen of death.
>
> Problem #2: 'kldload -v drm2.ko' locks u
On 23/08/2016 11:43, Andriy Gapon wrote:
>
> Please review and test a change to .zfs code that is intended to make the code
> aligned with FreeBSD VFS and, as such, more stable:
> https://reviews.freebsd.org/D7421
>
> The change removes two features.
> .zfs/shares is gone because it was unused on
On Mon, Feb 20, 2017 at 09:04:35AM +0100, Dimitry Andric wrote:
> On 19 Feb 2017, at 21:30, Steve Kargl
> wrote:
> > ===> Building for help2man-1.47.4
> > elf_load_section: truncated ELF file
> > Abort trap
>
> but this looks like a half-written or empty file. Did you do a full
> fsck, and did
While trying to compile akonadi I get the following error:
===> Installing for qtchooser-39===> Checking if qtchooser already
installed===> Registering installation for qtchooser-39 as automaticInstalling
qtchooser-39...pkg-static: qtchooser-39 conflicts with qt4-dbus-4.8.7 (installs
files into
On Sat, Feb 18, 2017 at 04:18:05AM -0800, Mark Millard wrote:
> [Note: I experiment with clang based powerpc64 builds,
> reporting problems that I find. Justin is familiar
> with this, as is Nathan.]
>
> I tried to update the PowerMac G5 (a so-called "Quad Core")
> that I have access to from head
On 2017-Feb-20, at 11:10 AM, Mateusz Guzik wrote:
> On Sat, Feb 18, 2017 at 04:18:05AM -0800, Mark Millard wrote:
>> [Note: I experiment with clang based powerpc64 builds,
>> reporting problems that I find. Justin is familiar
>> with this, as is Nathan.]
>>
>> I tried to update the PowerMac G5 (
On 2017-Feb-20, at 2:58 PM, Mark Millard wrote:
> On 2017-Feb-20, at 11:10 AM, Mateusz Guzik wrote:
>
>> On Sat, Feb 18, 2017 at 04:18:05AM -0800, Mark Millard wrote:
>>> [Note: I experiment with clang based powerpc64 builds,
>>> reporting problems that I find. Justin is familiar
>>> with this,
On Mon, Feb 20, 2017 at 03:10:44PM -0800, Mark Millard wrote:
> On 2017-Feb-20, at 2:58 PM, Mark Millard wrote:
>
> > On 2017-Feb-20, at 11:10 AM, Mateusz Guzik wrote:
> >
> >> On Sat, Feb 18, 2017 at 04:18:05AM -0800, Mark Millard wrote:
> >>> [Note: I experiment with clang based powerpc64 bui
With a kernel and world from r313943 sources (circa
Feb 19, 2017), kldload of either drm2.ko or i915kms.ko
will lock up the system. There is no keyboard response,
screen output, or panic. Just a locked up system.
A kernel from r313027 and its modules boots fine.
'kldload drm2.ko' yields the foll
On Mon, Feb 20, 2017 at 03:52:24PM -0800, Steve Kargl wrote:
> With a kernel and world from r313943 sources (circa
> Feb 19, 2017), kldload of either drm2.ko or i915kms.ko
> will lock up the system. There is no keyboard response,
> screen output, or panic. Just a locked up system.
>
> A kernel f
On Tue, Feb 21, 2017 at 12:58:07AM +0100, Mateusz Guzik wrote:
> On Mon, Feb 20, 2017 at 03:52:24PM -0800, Steve Kargl wrote:
> > With a kernel and world from r313943 sources (circa
> > Feb 19, 2017), kldload of either drm2.ko or i915kms.ko
> > will lock up the system. There is no keyboard respons
On Tue, Feb 21, 2017 at 12:58:07AM +0100, Mateusz Guzik wrote:
> On Mon, Feb 20, 2017 at 03:52:24PM -0800, Steve Kargl wrote:
> > With a kernel and world from r313943 sources (circa
> > Feb 19, 2017), kldload of either drm2.ko or i915kms.ko
> > will lock up the system. There is no keyboard respons
On Mon, Feb 20, 2017 at 04:43:40PM -0800, Steve Kargl wrote:
> On Tue, Feb 21, 2017 at 12:58:07AM +0100, Mateusz Guzik wrote:
> > On Mon, Feb 20, 2017 at 03:52:24PM -0800, Steve Kargl wrote:
> > > With a kernel and world from r313943 sources (circa
> > > Feb 19, 2017), kldload of either drm2.ko or
On 2017-Feb-20, at 3:35 PM, Mateusz Guzik wrote:
> On Mon, Feb 20, 2017 at 03:10:44PM -0800, Mark Millard wrote:
>> On 2017-Feb-20, at 2:58 PM, Mark Millard wrote:
>>
>>> On 2017-Feb-20, at 11:10 AM, Mateusz Guzik wrote:
>>>
On Sat, Feb 18, 2017 at 04:18:05AM -0800, Mark Millard wrote:
>
On Tue, Feb 21, 2017 at 01:50:30AM +0100, Mateusz Guzik wrote:
> On Mon, Feb 20, 2017 at 04:43:40PM -0800, Steve Kargl wrote:
> > On Tue, Feb 21, 2017 at 12:58:07AM +0100, Mateusz Guzik wrote:
> > > On Mon, Feb 20, 2017 at 03:52:24PM -0800, Steve Kargl wrote:
> > > > With a kernel and world from r3
On 2017-Feb-20, at 6:36 PM, Mark Millard wrote:
> On 2017-Feb-20, at 3:35 PM, Mateusz Guzik wrote:
>
>> On Mon, Feb 20, 2017 at 03:10:44PM -0800, Mark Millard wrote:
>>> On 2017-Feb-20, at 2:58 PM, Mark Millard wrote:
>>>
On 2017-Feb-20, at 11:10 AM, Mateusz Guzik wrote:
> On
On Mon, Feb 20, 2017 at 09:39:32PM -0800, Mark Millard wrote:
> Looks like some kernel binary interface (as seen by
> emulators/virtualbox-ose-addition ) has changed:
> rebuilding emulators/virtualbox-ose-addition removed
> the booting crash but uname -apKU still lists 1200021
> and 2100021 for the
Trying to mount root from ufs:/dev/gpt/rootfs [rw]...
<118>Setting hostuuid: 6e6fa481-535f-11cb-9756-be6694d54790.
<118>Setting hostid: 0xa94c64a9.
<118>Starting file system checks:
<118>/dev/gpt/rootfs: FILE SYSTEM CLEAN; SKIPPING CHECKS
<118>/dev/gpt/rootfs: clean, 1877279 free (13871 frags, 232
On Tue, Feb 21, 2017 at 09:51:25AM +0300, Chagin Dmitry wrote:
> 2527 * Remove a prison reference. If that was the last reference, remove
> the
> (kgdb) p *cred->cr_prison
> Cannot access memory at address 0x100fe
> (kgdb) p *cred
> $1 = {cr_ref = 0x0, cr_uid = 0x0, cr_ruid = 0x816f9500
On Tue, Feb 21, 2017 at 07:58:23AM +0100, Mateusz Guzik wrote:
> On Tue, Feb 21, 2017 at 09:51:25AM +0300, Chagin Dmitry wrote:
> > 2527 * Remove a prison reference. If that was the last reference,
> > remove the
> > (kgdb) p *cred->cr_prison
> > Cannot access memory at address 0x1000
For amd64 I run FreeBSD under VirtualBox on macOS. So I use
emulators/virtualbox-ose-additions in the FreeBSD instance.
I've been using virtualbox-ose-additions-5.1.14 for some time
under -r313864 (and some prior versions), no problems, no
need to rebuild virtualbox-ose-additions-5.1.14 along the
21 matches
Mail list logo
