Hi!
> > One situation that can cause out of swap errors is large amounts of
> > wired ram.
>
> Indeed: Very large amounts of wired RAM. What happened ? This
> did not happen before the last upgrade ? I'm at r328899.
vfs.zfs.arc_max was at 32345493504
changed that to
vfs.zfs.arc_max=16172746752
Hi!
> One situation that can cause out of swap errors is large amounts of
> wired ram.
Indeed: Very large amounts of wired RAM. What happened ? This
did not happen before the last upgrade ? I'm at r328899.
CPU: 0.0% user, 0.0% nice, 0.1% system, 0.0% interrupt, 99.9% idle
Mem: 2472K Active,
Hi, I have a very small request to those committing into head.
If you commit a fix, then if it is possible to easily do so, can you
give the revision number in which the regression was introduced?
like "this was broken in r329xxx"
this allows people who are looking for specific problems to
Hi Eric,
could you provide a brief update how the work is going?
Br,
Tommi
On Nov 16, 2017 04:29, "Eric McCorkle" wrote:
Right, so basically, the remaining GELI patches are against loader, and
most of them can go in independently of the work on removing boot1.
There's a unanimous consensus
On Tue, 20 Feb 2018 12:39:53 +0100 said
On Mon, 19 Feb 2018 14:18:15 -0800
"Chris H" wrote:
> I'm seeing a number of messages like the following:
> kernel: failed: cg 5, cgp: 0xd11ecd0d != bp: 0x63d3ff1d
>
> and was wondering if it's anything to be concerned with, or whether
> fsck(8) is fi
On Mon, Feb 19, 2018 at 8:21 AM, Juan Ramón Molina Menor wrote:
> [... snip ...]
>
> Moreover, the "boot [kernel]" loader command does not work:
>
> OK ls /boot/kernel.old/kernel
> /boot/kernel.old/kernel
> OK boot kernel.old
> Command failed
> OK boot /boot/kernel.old/kernel
> Command failed
Committed in https://svnweb.freebsd.org/base?view=revision&revision=329660
thanks for reporting
On Tue, Feb 20, 2018 at 6:06 PM, Mateusz Guzik wrote:
> I missed a consumer, try this:
>
> diff --git a/sys/kern/sys_procdesc.c b/sys/kern/sys_procdesc.c
> index 5e8928cb1534..174fffc5c666 100644
> -
On Mon, Feb 19, 2018 at 2:38 PM, Ronald Klop wrote:
> On Mon, 19 Feb 2018 22:05:51 +0100, Konstantin Belousov
> wrote:
>
>> Look at the man page. pkg reads version from the /bin/sh ELF FreeBSD
>
>
> Which man page? I can't find it in pkg help update or pkg help upgrade or
> man pkg.
I had to di
On Tue, Feb 20, 2018 at 05:50:57PM +0100, Juan Ram?n Molina Menor wrote:
> > I committed the fix in
> > https://svnweb.freebsd.org/base?view=revision&revision=329542
> >
> > i.e. should be stable from this point on.
>
> Hi!
>
> It is maybe unrelated, but recent commits have broken my system with
I missed a consumer, try this:
diff --git a/sys/kern/sys_procdesc.c b/sys/kern/sys_procdesc.c
index 5e8928cb1534..174fffc5c666 100644
--- a/sys/kern/sys_procdesc.c
+++ b/sys/kern/sys_procdesc.c
@@ -398,7 +398,6 @@ procdesc_close(struct file *fp, struct thread *td)
* proces
I committed the fix in
https://svnweb.freebsd.org/base?view=revision&revision=329542
i.e. should be stable from this point on.
Hi!
It is maybe unrelated, but recent commits have broken my system with a
similar error. I did not have panics with a system built around
December, but since updati
Le 19/02/2018 à 21:21, Kyle Evans a écrit :> Hello!
On Mon, Feb 19, 2018 at 8:21 AM, Juan Ramón Molina Menor wrote:
I have done a full build of r329555 to test the new Lua boot loader.
Both the new and the old kernels panic after being loaded with:
panic: running without device atpic require
On Tue, Feb 20, 2018 at 1:39 PM, Hans Petter Selasky
wrote:
> On 02/20/18 14:03, Johannes Lundberg wrote:
>
>> On Tue, Feb 20, 2018 at 12:57 PM, Hans Petter Selasky
>> wrote:
>>
>> On 02/20/18 12:39, Johannes Lundberg wrote:
>>>
>>> Before rebuilding world my system was running Linux games fine
On 02/20/18 14:03, Johannes Lundberg wrote:
On Tue, Feb 20, 2018 at 12:57 PM, Hans Petter Selasky
wrote:
On 02/20/18 12:39, Johannes Lundberg wrote:
Before rebuilding world my system was running Linux games fine with a
couple of months old world/kernel and drm-next-kmod.
Since updating worl
On Tue, Feb 20, 2018 at 12:57 PM, Hans Petter Selasky
wrote:
> On 02/20/18 12:39, Johannes Lundberg wrote:
>
>> Before rebuilding world my system was running Linux games fine with a
>> couple of months old world/kernel and drm-next-kmod.
>>
>> Since updating world+kernel last week all Linux 3D ap
On 02/20/18 12:39, Johannes Lundberg wrote:
Before rebuilding world my system was running Linux games fine with a
couple of months old world/kernel and drm-next-kmod.
Since updating world+kernel last week all Linux 3D apps fail (native
binaries like glxgears and supertuxkart works fine).
linux-
Before rebuilding world my system was running Linux games fine with a
couple of months old world/kernel and drm-next-kmod.
Since updating world+kernel last week all Linux 3D apps fail (native
binaries like glxgears and supertuxkart works fine).
linux-c6/c7, intel/modesetting, does no difference
T
On Mon, 19 Feb 2018 14:18:15 -0800
"Chris H" wrote:
> I'm seeing a number of messages like the following:
> kernel: failed: cg 5, cgp: 0xd11ecd0d != bp: 0x63d3ff1d
>
> and was wondering if it's anything to be concerned with, or whether
> fsck(8) is fixing them.
> This began to happen when the po
On Mon, 19 Feb 2018 23:38+0100, Ronald Klop wrote:
> Does this mean I always have to do a *clean* buildworld after every version
> bump? This takes ages.
Yes, I've come to the conclusion that whenever __FreeBSD_version in
sys/sys/param.h is incremented, then it's time to blow away /usr/obj,
rec
# info
- 100% reproducible on starting a bhyve-based vm
- recent current r329611, also panics at r329531
- GENERIC + WITH_CTF=1 and DEBUG=-g
- built WITH_META_MODE=yes & CCACHE_BUILD=yes
# panic dmesg
[36984] panic: mtx_lock_spin: recursed on non-recursive mutex vcpu lock @
/usr/src/sys/amd64/v
20 matches
Mail list logo
