Hi
I'm working on getting the graphics drivers up to Linux 4.16 version and
there has been a patch for Intel gpus that require some code in early boot.
The problem is that no all bios report the memory allocated for the gpu,
called stolen memory, correctly so on some configurations the OS can
rec
Hi,
On Tue, 7 Aug 2018 00:09:15 -0400
Allan Jude wrote:
> On 2018-08-06 23:11, Erich Dollansky wrote:
> >>> The message is always:
> >>>
> >>> Bad system call (core dumped)
>
> compare the output of: `uname -K` and `uname -U`
>
both outputs are
1200076
I got just access to that machine aga
On Tue, Aug 07, 2018 at 09:04:57AM +0100, Johannes Lundberg wrote:
> Hi
>
> I'm working on getting the graphics drivers up to Linux 4.16 version and
> there has been a patch for Intel gpus that require some code in early boot.
>
> The problem is that no all bios report the memory allocated for th
Hi,
During testing of the pNFS server I get an ffs_truncate3 panic every once in a
while.
A few things that might be relevant:
- Seems to happen more often when soft update journaling is enabled, but will
happen when it is disabled.
- Normally happens when a fairly large subtree of the file sys
hi,
latest change to dhclient added chroot if there is no capsicum - my case,
so chroot failes because /var/empty belongs to root and setgid/setgid/seteuid
to user dhclient is performed before.
need a pr?
danny
___
freebsd-current@freebsd.org maili
On Tue, Aug 07, 2018 at 12:28:33PM +, Rick Macklem wrote:
> Hi,
>
> During testing of the pNFS server I get an ffs_truncate3 panic every once in
> a while.
> A few things that might be relevant:
> - Seems to happen more often when soft update journaling is enabled, but will
> happen when it
On Tue, Aug 07, 2018 at 03:48:31PM +0300, Daniel Braniss wrote:
> hi,
> latest change to dhclient added chroot if there is no capsicum - my case,
> so chroot failes because /var/empty belongs to root and
> setgid/setgid/seteuid to user dhclient is performed before.
>
> need a pr?
Thanks, please
I recently started having severe instability on a workstation with
VirtualBox. I'm not sure if it was caused by the recent large ports
update, or a recent commit that affected SMAP. I can't seem to find
that revision, would someone please post it and also the workaround to
disable it, I would lik
Alan Somers wrote this message on Sun, Aug 05, 2018 at 11:35 -0600:
> On Sun, Aug 5, 2018 at 5:39 AM, Jeffrey Bouquet
> wrote:
>
> >
> >
> > On Sun, 5 Aug 2018 03:19:48 +0200, Lars Schotte wrote:
> >
> > > somehow installworld fails lately
> > >
> > > ===> share/examples (install)
> > > if [ -L
Update:
I found the revision:
https://svnweb.freebsd.org/base?view=revision&revision=336876
Use SMAP on amd64.
Could this possibly cause VBox to crash and reboot the system? Is
there a sysctl to disable?
Thanks
On Tue, Aug 7, 2018 at 10:46 AM, AN wrote:
> I recently started having severe ins
# zpool status
pool: zroot
state: ONLINE
scan: scrub in progress since Tue Aug 7 21:21:51 2018
804G scanned at 163M/s, 1,06T issued at 219M/s, 834G total
0 repaired, 129,87% done, 929637 days 13:43:01 to go
config:
NAMESTATE READ WRITE CKSUM
zroot
On Tue, Aug 7, 2018 at 12:09 AM, Eitan Adler wrote:
> On Mon, 6 Aug 2018 at 11:27, Kyle Evans wrote:
>>
>> On Sun, Aug 5, 2018 at 5:43 AM, Konstantin Belousov
>> wrote:
>> > On Sat, Aug 04, 2018 at 09:46:39PM -0500, Kyle Evans wrote:
>> >>
>> >> He now gets a little further, but ends up with th
On Tue, Aug 07, 2018 at 11:50:44AM -0500, Kyle Evans wrote:
> On Tue, Aug 7, 2018 at 12:09 AM, Eitan Adler wrote:
> > On Mon, 6 Aug 2018 at 11:27, Kyle Evans wrote:
> >>
> >> On Sun, Aug 5, 2018 at 5:43 AM, Konstantin Belousov
> >> wrote:
> >> > On Sat, Aug 04, 2018 at 09:46:39PM -0500, Kyle Ev
On 8/6/18 8:11 PM, Erich Dollansky wrote:
> Hi,
>
> On Mon, 6 Aug 2018 15:57:53 -0700
> John Baldwin wrote:
>
>> On 8/4/18 4:38 PM, Erich Dollansky wrote:
>>> Hi,
>>>
>>> I compiled me yesterday this system:
>>>
>>> 12.0-CURRENT FreeBSD 12.0-CURRENT #1 r337285:
>>>
>>> When restarting fortune co
Hi
I seem to have some unkillable Linux processes...
This is on my AMD Ryzen, the exact same installation on my Broadwell laptop
does not show this behavior.
At the second top output, the three remaining processes' cpu usage is
fluctuating, just as when they are running normally.
Kernel is from on
On Tue, Aug 07, 2018 at 08:54:39PM +0100, Johannes Lundberg wrote:
> Hi
>
> I seem to have some unkillable Linux processes...
> This is on my AMD Ryzen, the exact same installation on my Broadwell laptop
> does not show this behavior.
> At the second top output, the three remaining processes' cpu
On Tue, Aug 7, 2018 at 21:16 Konstantin Belousov
wrote:
> On Tue, Aug 07, 2018 at 08:54:39PM +0100, Johannes Lundberg wrote:
> > Hi
> >
> > I seem to have some unkillable Linux processes...
> > This is on my AMD Ryzen, the exact same installation on my Broadwell
> laptop
> > does not show this be
On Tue, Aug 07, 2018 at 08:29:49PM +0300, Konstantin Belousov wrote:
| On Tue, Aug 07, 2018 at 11:50:44AM -0500, Kyle Evans wrote:
| > On Tue, Aug 7, 2018 at 12:09 AM, Eitan Adler wrote:
| > > On Mon, 6 Aug 2018 at 11:27, Kyle Evans wrote:
| > >>
| > >> On Sun, Aug 5, 2018 at 5:43 AM, Konstantin
On Tue, Aug 07, 2018 at 02:49:10PM -0700, Doug Ambrisko wrote:
> On Tue, Aug 07, 2018 at 08:29:49PM +0300, Konstantin Belousov wrote:
> | On Tue, Aug 07, 2018 at 11:50:44AM -0500, Kyle Evans wrote:
> | > On Tue, Aug 7, 2018 at 12:09 AM, Eitan Adler wrote:
> | > > On Mon, 6 Aug 2018 at 11:27, Kyle
On Wed, Aug 08, 2018 at 01:42:07AM +0300, Konstantin Belousov wrote:
| On Tue, Aug 07, 2018 at 02:49:10PM -0700, Doug Ambrisko wrote:
| > On Tue, Aug 07, 2018 at 08:29:49PM +0300, Konstantin Belousov wrote:
| > | On Tue, Aug 07, 2018 at 11:50:44AM -0500, Kyle Evans wrote:
| > | > On Tue, Aug 7, 201
Hi,
On Tue, 7 Aug 2018 11:59:11 -0700
John Baldwin wrote:
> On 8/6/18 8:11 PM, Erich Dollansky wrote:
> > On Mon, 6 Aug 2018 15:57:53 -0700
> > John Baldwin wrote:
> >
> >> On 8/4/18 4:38 PM, Erich Dollansky wrote:
> >>> Bad system call (core dumped)
> >>
> >> Did you upgrade from stable/
21 matches
Mail list logo
