Andreas Gustafsson writes:
> Cherry,
>
> The NetBSD Test Fixture wrote:
>> --- assym.h ---
>> *** [assym.h] Error code 1
>> nbmake[2]: stopped in
>> /tmp/bracket/build/2018.09.23.02.51.06-i386/obj/sys/arch/i386/compile/INSTALL_XEN3PAE_DOMU
>
> Here's a more relevant part of the build
Robert Elz writes:
> Date:Sun, 23 Sep 2018 13:25:23 +0530
> From:"Cherry G.Mathew"
> Message-ID: <87efdkfy1g@zyx.in>
>
> | Should be fixed now.
>
> Not yet,...
>
Thanks for the alert. I have tested the build now it should be fixed.
I would look forward to
Andreas Gustafsson writes:
> Brad Spencer wrote:
>> Just wondering if anyone else has seen this, but I am getting panics on
>> boot during probe with sources after 2018-09-23 [at some point, at least
>> 2018-09-29 and 2018-10-01 panic, but 2018-09-23 doesn't]. This is with
>> trying to use the s
Andreas Gustafsson writes:
> Cherry G. Mathew wrote:
>> I have checked in a couple of changes, which hopefully should fix the
>> problem. I look forward to user reports.
>
> With sources from CVS date 2018.10.06.16.49.54 (that's up to
> and including your commit o
"Cherry G. Mathew" writes:
> Andreas Gustafsson writes:
>
>> Brad Spencer wrote:
>>> Just wondering if anyone else has seen this, but I am getting panics on
>>> boot during probe with sources after 2018-09-23 [at some point, at least
>>> 2018-0
Andreas Gustafsson writes:
> Cherry G.Mathew wrote:
>> Thank you - I've checked in a temporary 'fix'. This will sort itself out
>> once the interrupt rework to merge with native is complete.
>
> A dom0 built from 2018.10.07.20.30.50 boots successfully. Thank you!
That's great news! There's some
Hi Geoff,
Saitoh-san pointed me at this email. I've been looking at MSI briefly -
should have some work in place to sort out this situation. About your
specific situation:
Geoff Wing writes:
> Hi,
> brief background: on an amd64 VM (1 CPU on VMWare ESXi) I had a network
> interface (vmx) faili
On December 22, 2018 2:24:44 AM GMT+05:30, Chavdar Ivanov
wrote:
...
>
>It is interesting also that when NetBSD is ran under XenServer (XCP-NG
>actually) in PV mode, benchmarked against the same 8.99.28 version
>running on a physical machine, everything on a 1GB interface and
>switch, I get maxim
NetBSD Test Fixture writes:
> This is an automatically generated notice of a NetBSD-current/i386
> build failure.
>
> The failure occurred on babylon5.netbsd.org, a NetBSD/amd64 host,
> using sources from CVS date 2018.12.25.07.41.21.
>
> An extract from the build.sh output follows:
>
>pm
Chavdar Ivanov writes:
> Mine is 8.99.34 from 09/02/2019, self build, works just fine. I'll
> build a new kernel now to compare.
>
Just FYI in case this is relevant and can help you with bisecting:
https://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=53984
--
~cherry
On 19 February 2019 11:31:37 PM MYT, Martin Husemann wrote:
>On Tue, Feb 19, 2019 at 03:28:23PM +, Chavdar Ivanov wrote:
>> Any bells ringing?
>
>I think this already has been fixed by Cherry?
>
>Martin
I believe so.
Chavdar, I'd be interested to know if this is happening in -current.
Than
Chavdar Ivanov writes:
> Yes, it is. This happens on:
> ...
> uname -a
> NetBSD nbuild.lorien.lan 8.99.34 NetBSD 8.99.34 (XEN3_DOMU) #0: Tue
> Feb 19 13:23:54 GMT 2019
> sysbu...@nbuild.lorien.lan:/home/sysbuild/amd64/obj/home/sysbuild/src/sys/arch/amd64/compile/XEN3_DOMU
> amd64
>
>
Thank
12 matches
Mail list logo
