Rainer, I'm all up and running and clean with the latest again, if it
still doesn't work after your next try, send me your step-by-step to
patch and i'll try it here. I'm using ryzen video so I have to disable
stuff to even see the fault messages.
On 9/22/20 1:06 AM, Rainer Hurling wrote:
Am
Am 22.09.20 um 00:13 schrieb Konstantin Belousov:
On Mon, Sep 21, 2020 at 08:57:46PM +0200, Rainer Hurling wrote:
Fatal trap 12: page fault while in kernel mode
cpuid = 31; apic id = 1f
fault virtual address = 0x25407efa
This address is very suspicious.
I cannot claim it as the fact, but mos
On 2020-Sep-21, at 16:16, Mark Millard wrote:
> On 2020-Sep-21, at 13:38, Mark Millard wrote:
>
>> Context: head -r365932 (on a Rock64). But this could well not
>> be new.
>>
>> First a look at the / context and then the /mnt/ :
>>
>> # ls -laT /
>> total 225
>> drwxr-xr-x 24 root wheel
On 2020-Sep-21, at 13:38, Mark Millard wrote:
> Context: head -r365932 (on a Rock64). But this could well not
> be new.
>
> First a look at the / context and then the /mnt/ :
>
> # ls -laT /
> total 225
> drwxr-xr-x 24 root wheel 512 Sep 21 02:20:37 2020 .
> drwxr-xr-x 24 root whee
Hi,
I just put a patch up in phabricator (D26521) which avoids always
malloc()'ng a large MAX_NGROUPS sized groups list by having a
small one in the structure and then only malloc()'ng when a large
groups list is needed.
I've listed kib@ and freqlabs@ as reviewers, but anyone else is
welcome to r
Context: head -r365932 (on a Rock64). But this could well not
be new.
First a look at the / context and then the /mnt/ :
# ls -laT /
total 225
drwxr-xr-x 24 root wheel 512 Sep 21 02:20:37 2020 .
drwxr-xr-x 24 root wheel 512 Sep 21 02:20:37 2020 ..
-rw-r--r-- 2 root wheel 1
Possibly check ForwardX11Timeout .
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
I don't know if it's just coincidental or if it's because of some change in
13-CURRENT, but I recently migrated from 12.1-STABLE, and now I am unable
to forward X11 apps over ssh. The only app I was accustomed to running this
way was Handbrake. It worked fine before, but now i get this:
$ ghb
Unab
Warner Losh wrote in
:
|On Mon, Sep 21, 2020 at 2:55 PM Steffen Nurpmeso \
|wrote:
|> Lev Serebryakov wrote in
|> <23e7fc1c-6769-ceaf-4089-46e5cc575...@freebsd.org>:
|>|On 19.09.2020 19:05, Bakul Shah wrote:
|>|>> These are the main ones. The three down sides are lack of $FreeBSD$ \
|>|>>
On Mon, Sep 21, 2020 at 08:57:46PM +0200, Rainer Hurling wrote:
> Fatal trap 12: page fault while in kernel mode
> cpuid = 31; apic id = 1f
> fault virtual address = 0x25407efa
This address is very suspicious.
I cannot claim it as the fact, but most likely cause for such garbage
pointer value is
On 2020-09-21, Pete Wright wrote:
> I believe the most detailed report on this was in the 2020-04 quarterly
> status report:
> https://www.freebsd.org/news/status/report-2020-04-2020-06.html#Git-Migration-Working-Group
I saw that at the time. It basically says that the conversion of
the reposi
On Mon, Sep 21, 2020 at 2:55 PM Steffen Nurpmeso wrote:
> Lev Serebryakov wrote in
> <23e7fc1c-6769-ceaf-4089-46e5cc575...@freebsd.org>:
> |On 19.09.2020 19:05, Bakul Shah wrote:
> |>> These are the main ones. The three down sides are lack of $FreeBSD$ \
> |>> support
> |>> and tags in gener
Lev Serebryakov wrote in
<23e7fc1c-6769-ceaf-4089-46e5cc575...@freebsd.org>:
|On 19.09.2020 19:05, Bakul Shah wrote:
|>> These are the main ones. The three down sides are lack of $FreeBSD$ \
|>> support
|>> and tags in general.
|>
|> Can a git hook be used for this?
|
|git filters could b
On 9/21/20 12:49 PM, Christian Weisgerber wrote:
On 2020-09-21, Alexander Leidinger wrote:
In my opinion the people which drive this didn't keep it behind
closed curtains, and they went step by step more public, as they
made progress. To me it looks like now, that they have something
which
> On Sep 21, 2020, at 4:22 AM, Alexander Leidinger
> wrote:
>
> Quoting Pete Wright (from Sun, 20 Sep 2020 08:41:13
> -0700):
>
> Not responding to Pete directly, but in general to this topic with some parts
> of what Pete considers good as something to hook into.
>
making quarterly r
On 2020-09-21, Alexander Leidinger wrote:
> In my opinion the people which drive this didn't keep it behind
> closed curtains, and they went step by step more public, as they
> made progress. To me it looks like now, that they have something
> which is presentable to the world (and not only to c
On 20.09.20 22:35, Rainer Hurling wrote:
> On 20.09.20 22:07, Konstantin Belousov wrote:
>> On Sun, Sep 20, 2020 at 10:55:26PM +0300, Konstantin Belousov wrote:
>>> On Sun, Sep 20, 2020 at 03:11:26PM +0200, Rainer Hurling wrote:
Am 20.09.20 um 11:38 schrieb Konstantin Belousov:
> On Sun, S
Le dim. 20 sept. 2020 à 16:59, Mark Murray a écrit :
>
> Hi *
>
> I've been getting these build failures for a while (weeks/months). The
> machine is a MacchiatoBin DoubleShot (arm64, Quad core). with SATA disks and
> zfs filesystem. If I empty out /usr/obj, then the build works, but takes a
>
On Mon, Sep 21, 2020 at 09:57:40AM +0200, Kristof Provost wrote:
> On 21 Sep 2020, at 2:52, Shawn Webb wrote:
> >> From latest HEAD on a Dell Precision 7550 laptop:
> >
> > https://gist.github.com/lattera/a0803f31f58bcf8ead51ac1ebbc447e2
> >
> > The last working boot environment was 14 Aug 2020. If
Quoting Pete Wright (from Sun, 20 Sep 2020
08:41:13 -0700):
Not responding to Pete directly, but in general to this topic with
some parts of what Pete considers good as something to hook into.
making quarterly reports about this for almost a years as well. We put out
calls for people to h
On 21 Sep 2020, at 2:52, Shawn Webb wrote:
>> From latest HEAD on a Dell Precision 7550 laptop:
>
> https://gist.github.com/lattera/a0803f31f58bcf8ead51ac1ebbc447e2
>
> The last working boot environment was 14 Aug 2020. If I get some time to
> bisect commits, I'll try to figure out the culprit.
>
T
On Mon, 21 Sep 2020, 07:38 Adrian Chadd, wrote:
> So, the big list of unknown symbols was my fault! Whoops.
>
> i've gotten further using gcc-6.4 by fixing some of the warnings/issues
> that have crept up.
>
> Here's a review for one of them:
>
> https://reviews.freebsd.org/D26504
>
> However, no
22 matches
Mail list logo
