Re: netbsd-8 crash in ixg driver during booting

2017-11-14 Thread 6bone
Does your machine boot with the latest -current? I have tested the current sources from tonignt. https://suse.uni-leipzig.de/crash/crash-current1.jpg https://suse.uni-leipzig.de/crash/crash-current2.jpg Regards Uwe

daily CVS update output

2017-11-14 Thread NetBSD source update
Updating src tree: P src/external/bsd/nvi/dist/vi/vs_refresh.c P src/external/gpl3/gcc/dist/gcc/toplev.c P src/external/gpl3/gcc/dist/libiberty/vprintf-support.c P src/external/gpl3/gcc/lib/liblto_plugin/Makefile P src/external/gpl3/gcc.old/dist/libiberty/vprintf-support.c P

Re: Possible regression in wm(4)?

2017-11-14 Thread Kengo NAKAHARA
Hi, On 2017/11/14 21:53, Bert Kiers wrote: > On Tue, Nov 14, 2017 at 08:07:46PM +0900, Kengo NAKAHARA wrote: >> I'm sorry I cannot solve it... >> Hmm, now I think this problem may relate to MSI/MSI-X interrupts >> setting about ioapic. If it is not a problem, could you try the >> following patch?

Re: Compile failure in nand.c

2017-11-14 Thread Jared McNeill
Hi Chavdar -- This define is generated by config in locators.h (kernel obj directory). Make sure you have sys/dev/flash/files.flash rev 1.4 and that you've run config on your kernel since updating. Cheers, Jared On Tue, 14 Nov 2017, Chavdar Ivanov wrote: Hi, I am getting: ... # compile

Compile failure in nand.c

2017-11-14 Thread Chavdar Ivanov
Hi, I am getting: ... # compile nand/nand.o /home/sysbuild/amd64/tools/bin/x86_64--netbsd-gcc -O2 -g -std=gnu99 -Wall -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-sign- compare -Wsystem-headers -Wno-traditional -Wa,--fatal-warnings -Wreturn-type -Wswitch -Wshadow

Re: Automated report: NetBSD-current/i386 test failure

2017-11-14 Thread Rin Okuyama
On 2017/11/14 23:09, Martin Husemann wrote: On Tue, Nov 14, 2017 at 01:58:54PM +, NetBSD Test Fixture wrote: This is an automatically generated notice of new failures of the NetBSD test suite. The newly failing test cases are: This was fallout fromt the gcc import, it should be fixed

Re: Automated report: NetBSD-current/i386 test failure

2017-11-14 Thread Martin Husemann
On Tue, Nov 14, 2017 at 01:58:54PM +, NetBSD Test Fixture wrote: > This is an automatically generated notice of new failures of the > NetBSD test suite. > > The newly failing test cases are: This was fallout fromt the gcc import, it should be fixed now. Martin

Automated report: NetBSD-current/i386 test failure

2017-11-14 Thread NetBSD Test Fixture
This is an automatically generated notice of new failures of the NetBSD test suite. The newly failing test cases are: share/mk/t_lib:defaults__build_and_install share/mk/t_prog:defaults__build_and_install share/mk/t_prog:without_man__build_and_install share/mk/t_test:one_c

Re: Possible regression in wm(4)?

2017-11-14 Thread Bert Kiers
On Tue, Nov 14, 2017 at 08:07:46PM +0900, Kengo NAKAHARA wrote: > Hi, Hi, > I'm sorry I cannot solve it... > Hmm, now I think this problem may relate to MSI/MSI-X interrupts > setting about ioapic. If it is not a problem, could you try the > following patch? > I believe this patch let wm(4) do

Re: Possible regression in wm(4)?

2017-11-14 Thread Kengo NAKAHARA
Hi, On 2017/11/14 19:33, Bert Kiers wrote: > On Tue, Nov 14, 2017 at 12:34:40PM +0900, Kengo NAKAHARA wrote: > > I am sorry to have to say they both do not fix the problem. > >> == (A) == >> --- a/sys/dev/pci/if_wm.c >> +++ b/sys/dev/pci/if_wm.c >> @@ -4883,8 +4883,8 @@

Re: Possible regression in wm(4)?

2017-11-14 Thread Bert Kiers
On Tue, Nov 14, 2017 at 12:34:40PM +0900, Kengo NAKAHARA wrote: > Hi, Hi, I am sorry to have to say they both do not fix the problem. > == (A) == > --- a/sys/dev/pci/if_wm.c > +++ b/sys/dev/pci/if_wm.c > @@ -4883,8 +4883,8 @@ wm_adjust_qnum(struct wm_softc *sc, int nvectors) >

Re: netbsd 8 (beta) failing to load ixg device

2017-11-14 Thread Masanobu SAITOH
Hi, all. On 2017/11/14 7:01, Jaromír Doleček wrote: I had a very brief look on the crashing function ixgbe_update_stats_count(). The only division there is in the one using adapter->num_queue. Looking at ixgbe_configure_interrups(), seems that one can happily set it to 0 if number of MSI