please update to r334253
On Sat, May 26, 2018 at 11:36 PM, O. Hartmann wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Am Sun, 27 May 2018 03:17:07 +
> "Pieper, Jeffrey E" schrieb:
>
>> I'm seeing this spam dmesg continuously on a build from this afternoon
>> (r334252):
>>
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am Sun, 27 May 2018 03:17:07 +
"Pieper, Jeffrey E" schrieb:
> I'm seeing this spam dmesg continuously on a build from this afternoon
> (r334252):
>
> May 27 03:06:03 u0855 kernel: ifa_ifwithnet failed
> May 27 03:06:03 u0855 syslogd: last mes
From: kmacy...@gmail.com [kmacy...@gmail.com] on behalf of K. Macy
[km...@freebsd.org]
Sent: Saturday, May 26, 2018 8:35 PM
To: Pieper, Jeffrey E
Cc: freebsd-current [freebsd-current@freebsd.org]
Subject: Re: ifa_ifwithnet failed ???
> My guess is that
My guess is that this is caused by my changes. However, this is the
first time I've heard this reported so it would be useful to know how
I might reproduce it.
Thanks.
-M
On Sat, May 26, 2018 at 8:33 PM, Pieper, Jeffrey E
wrote:
>
>
> From: kmacy...@gmail
From: kmacy...@gmail.com [kmacy...@gmail.com] on behalf of K. Macy
[km...@freebsd.org]
Sent: Saturday, May 26, 2018 8:20 PM
To: Pieper, Jeffrey E
Cc: freebsd-current [freebsd-current@freebsd.org]
Subject: Re: ifa_ifwithnet failed ???
On Sat, May 26, 201
On Sat, May 26, 2018 at 8:17 PM, Pieper, Jeffrey E
wrote:
> I'm seeing this spam dmesg continuously on a build from this afternoon
> (r334252):
>
> May 27 03:06:03 u0855 kernel: ifa_ifwithnet failed
> May 27 03:06:03 u0855 syslogd: last message repeated 11 times
> May 27 03:06:03 u0855 kernel: .
I'm seeing this spam dmesg continuously on a build from this afternoon
(r334252):
May 27 03:06:03 u0855 kernel: ifa_ifwithnet failed
May 27 03:06:03 u0855 syslogd: last message repeated 11 times
May 27 03:06:03 u0855 kernel: .
May 27 03:06:05 u0855 kernel: ifa_ifwithnet failed
May 27 03:06:39 u08
I've updated the description and such for:
Bug 213937 - stable/11 -r334246 on BPi-M3 (cortex-a7), amd64, and more, also
head: ktrace misreports bad svc (SIGSYS) number
The primary description is really Comment 2 from Oleksandr Tymoshenko :
> This is not ARM specific, the same bug can be reprodu
Quoting Steve Wills (from Tue, 22 May 2018
08:17:00 -0400):
I may be seeing similar issues. Have you tried leaving top -SHa
running and seeing what threads are using CPU when it hangs? I did
and saw pid 17 [zfskern{txg_thread_enter}] using lots of CPU but no
disk activity happening. Do
On Sat, May 26, 2018 at 08:32:17PM +0800, blubee blubeeme wrote:
Aren't you the guy using the drm-kmod if yes, your custom complied kernel
and not the default kernel causing those issues.
Best,
Owen
I'm indeed using graphics/drm-stable-kmod, but i do not use a custom
kernel:
uname -r
Cross post; FreeBSD-[questions | current | ultimedia]
Where's the midi loopback device in the FreeBSD OSS implementation?
Best,
Owen
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe,
On Sat, May 26, 2018, 19:52 Manuel Stühn wrote:
> Since upgrading my Lenovo T450 from r333740 to r334167 I'm experiencing
> several "Fatal traps 12". Before the update i did not have any of those.
> In all cases the traps occured some time after resume.
>
> Below there is some output found in /va
Since upgrading my Lenovo T450 from r333740 to r334167 I'm experiencing
several "Fatal traps 12". Before the update i did not have any of those.
In all cases the traps occured some time after resume.
Below there is some output found in /var/crash/core.txt
__curthread () at ./machine/pcpu.h:23
===> usb/muge (install)
install -T release -o root -g wheel -m 555 if_muge.ko /boot/kernel/
install: if_muge.ko: No such file or directory
*** Error code 71
Stop.
make[5]: stopped in /usr/src/sys/modules/usb/muge
*** Error code 1
Stop.
make[4]: stopped in /usr/src/sys/modules/usb
*** Error code
On Sat, May 26, 2018 at 11:11 AM Konstantin Belousov
wrote:
> On Sat, May 26, 2018 at 10:59:50AM +0100, Johannes Lundberg wrote:
> > Hi
> >
> > The new AMD graphics drivers use floats in kernel space.
> > Upstream Linux code has something like:
> > kernel_fpu_begin();
> > ...
> > kernel_fpu_end()
On Sat, May 26, 2018 at 10:59:50AM +0100, Johannes Lundberg wrote:
> Hi
>
> The new AMD graphics drivers use floats in kernel space.
> Upstream Linux code has something like:
> kernel_fpu_begin();
> ...
> kernel_fpu_end();
>
> Do we have similar functions to save/restore FPU registers?
Read fpu_k
Hi
The new AMD graphics drivers use floats in kernel space.
Upstream Linux code has something like:
kernel_fpu_begin();
...
kernel_fpu_end();
Do we have similar functions to save/restore FPU registers?
Cheers
___
freebsd-current@freebsd.org mailing lis
17 matches
Mail list logo