FreeBSD_HEAD_i386 - Build #644 - Fixed:
Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/644/
Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/644/changes
Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/644/console
Change summaries:
No chan
On Wed, Jul 22, 2015 at 8:38 AM, O. Hartmann
wrote:
> Recent sources (r285785) do not buildkernel due to the bug/error shown below:
>
> [...]
> linking kernel
> vt_core.o: In function `vtterm_cnprobe':
> /usr/src/sys/dev/vt/vt_core.c:(.text+0x42f): undefined reference to
> `vt_logo_sprite_height'
Recent sources (r285785) do not buildkernel due to the bug/error shown below:
[...]
linking kernel
vt_core.o: In function `vtterm_cnprobe':
/usr/src/sys/dev/vt/vt_core.c:(.text+0x42f): undefined reference to
`vt_logo_sprite_height' /usr/src/sys/dev/vt/vt_core.c:(.text+0x46b): undefined
reference t
FreeBSD_HEAD_i386 - Build #643 - Failure:
Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/643/
Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/643/changes
Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/643/console
Change summaries:
No ch
On Tue, Jul 21, 2015 at 03:21:16PM -0500, Eric van Gyzen wrote:
> ...
> >> So it looks like net swi, leaking some udp6 lock.
> > Curiouser and curiouser... While I'm not taking any special pains to
> > avoid building IPv6, I'm not actively actually doing anything with it
> > (IPv6), either (for bo
On 07/21/2015 15:21, Eric van Gyzen wrote:
> On 07/21/2015 15:05, David Wolfskill wrote:
>> On Tue, Jul 21, 2015 at 10:28:32PM +0300, Konstantin Belousov wrote:
>>> ...
>>> Indeed, thank you.
>>> ithread_loop() at ithread_loop+0xa6/frame 0xfe083b9c0a70
>>> fork_exit() at fork_exit+0x84/frame 0x
On 07/21/2015 15:05, David Wolfskill wrote:
> On Tue, Jul 21, 2015 at 10:28:32PM +0300, Konstantin Belousov wrote:
>> ...
>> Indeed, thank you.
>> ithread_loop() at ithread_loop+0xa6/frame 0xfe083b9c0a70
>> fork_exit() at fork_exit+0x84/frame 0xfe083b9c0ab0
>> fork_trampoline() at fork_tram
On Tue, Jul 21, 2015 at 10:28:32PM +0300, Konstantin Belousov wrote:
> ...
> Indeed, thank you.
> ithread_loop() at ithread_loop+0xa6/frame 0xfe083b9c0a70
> fork_exit() at fork_exit+0x84/frame 0xfe083b9c0ab0
> fork_trampoline() at fork_trampoline+0xe/frame 0xfe083b9c0ab0
> --- trap 0, r
On Tue, Jul 21, 2015 at 07:17:43PM +, Mark Johnston wrote:
> On Tue, Jul 21, 2015 at 09:19:27AM -0700, David Wolfskill wrote:
> > On Tue, Jul 21, 2015 at 04:39:07PM +0300, Konstantin Belousov wrote:
> > > On Tue, Jul 21, 2015 at 05:57:34AM -0700, David Wolfskill wrote:
> > > > My laptop had no
On Tue, Jul 21, 2015 at 09:19:27AM -0700, David Wolfskill wrote:
> On Tue, Jul 21, 2015 at 04:39:07PM +0300, Konstantin Belousov wrote:
> > On Tue, Jul 21, 2015 at 05:57:34AM -0700, David Wolfskill wrote:
> > > My laptop had no problems, but the build machine has a panic that
> > > appears quite re
Yes, I think the FreeBSD developers have been doing this since before
Redhat was a thing.
-a
On 20 July 2015 at 23:02, Venkat Duvvuru
wrote:
> Yes, my question was about kernel module compatibililty with FreeBSD's
> major releases of a particular version.
> For example, will FreeBSD makes sur
On Tue, Jul 21, 2015 at 04:39:07PM +0300, Konstantin Belousov wrote:
> On Tue, Jul 21, 2015 at 05:57:34AM -0700, David Wolfskill wrote:
> > My laptop had no problems, but the build machine has a panic that
> > appears quite reproducible (4 "successes" out of 4 tries); here's a bit
> > from the core
On 7/21/15 2:02 PM, Venkat Duvvuru wrote:
Yes, my question was about kernel module compatibililty with FreeBSD's
major releases of a particular version.
For example, will FreeBSD makes sure that the driver built on 10.0 version
of Freebsd seamlessly load on all other 10.x versions of FreeBSD?
Doe
On Tue, Jul 21, 2015 at 05:57:34AM -0700, David Wolfskill wrote:
> My laptop had no problems, but the build machine has a panic that
> appears quite reproducible (4 "successes" out of 4 tries); here's a bit
> from the core.txt file:
There must be kernel messages before the panic string. They are
My laptop had no problems, but the build machine has a panic that
appears quite reproducible (4 "successes" out of 4 tries); here's a bit
from the core.txt file:
freebeast.catwhisker.org dumped core - see /var/crash/vmcore.1
Tue Jul 21 05:36:11 PDT 2015
FreeBSD freebeast.catwhisker.org 11.0-CURR
Yes, my question was about kernel module compatibililty with FreeBSD's
major releases of a particular version.
For example, will FreeBSD makes sure that the driver built on 10.0 version
of Freebsd seamlessly load on all other 10.x versions of FreeBSD?
Does it make sure that the symbols and their pa
Does anyone else have a machine that won't boot from GPT without the
active flag set?
bsdinstall now has a blacklist for these models, and can apply the fix
as part of the installation (ufs or zfs).
If you are also suffering from this, please post your machine's details
to get it added to the bl
FreeBSD_HEAD_i386 - Build #637 - Fixed:
Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/637/
Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/637/changes
Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/637/console
Change summaries:
No chan
FreeBSD_HEAD_i386 - Build #636 - Failure:
Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/636/
Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/636/changes
Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/636/console
Change summaries:
No ch
19 matches
Mail list logo
