Re: netbsd-8 crash in ixg driver during booting

2017-11-15 Thread 6bone 

On Thu, 16 Nov 2017, Masanobu SAITOH wrote:


This problem is different from ixg(4)'s problem. I'll now
working to fix this softint related problem.

This problem is caused by some devices which uses a lot of
softint, could you tell me the machine's spec? e.g.:

number of port of wm(4) and/or ixg(4)
number of nvme(4)
etc.


Hello,

the hardware is an HP G5 with two dual-port Intel 10GE network cards. The 
server is used as a router.


Here is the dmesg output from the netbsd-8 kernel.

Thank you for your efforts

Regards
Uwe


Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017
The NetBSD Foundation, Inc.  All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California.  All rights reserved.

NetBSD 8.0_BETA (MYCONF8.gdb) #0: Mon Aug 28 22:51:59 CEST 2017

r...@gate.ipv6.uni-leipzig.de:/usr/obj/sys/arch/amd64/compile/MYCONF8.gdb
total memory = 24565 MB
avail memory = 23830 MB
timecounter: Timecounters tick every 10.000 msec
Kernelized RAIDframe activated
running cgd selftest aes-xts-256 aes-xts-512 done
timecounter: Timecounter "i8254" frequency 1193182 Hz quality 100
HP ProLiant DL380 G7
mainbus0 (root)
ACPI: RSDP 0x000F4F00 24 (v02 HP)
ACPI: XSDT 0xDF630340 BC (v01 HP ProLiant 0002 ??   
162E)
ACPI: FACP 0xDF630440 F4 (v03 HP ProLiant 0002 ??   
162E)
ACPI BIOS Warning (bug): Invalid length for FADT/Pm1aControlBlock: 32, using 
default 16 (20170303/tbfadt-745)
ACPI BIOS Warning (bug): Invalid length for FADT/Pm2ControlBlock: 32, using 
default 8 (20170303/tbfadt-745)
ACPI: DSDT 0xDF630540 0020BD (v01 HP DSDT 0001 INTL 
20030228)
ACPI: FACS 0xDF62F100 40
ACPI: FACS 0xDF62F100 40
ACPI: SPCR 0xDF62F140 50 (v01 HP SPCRRBSU 0001 ??   
162E)
ACPI: MCFG 0xDF62F1C0 3C (v01 HP ProLiant 0001  
)
ACPI: HPET 0xDF62F200 38 (v01 HP ProLiant 0002 ??   
162E)
ACPI:  0xDF62F240 64 (v02 HP ProLiant 0002 ??   
162E)
ACPI: SPMI 0xDF62F2C0 40 (v05 HP ProLiant 0001 ??   
162E)
ACPI: ERST 0xDF62F300 0001D0 (v01 HP ProLiant 0001 ??   
162E)
ACPI: APIC 0xDF62F500 00015E (v01 HP ProLiant 0002  
)
ACPI: SRAT 0xDF62F680 000570 (v01 HP Proliant 0001 ??   
162E)
ACPI:  0xDF62FC00 000176 (v01 HP ProLiant 0001 ??   
162E)
ACPI: BERT 0xDF62FD80 30 (v01 HP ProLiant 0001 ??   
162E)
ACPI: HEST 0xDF62FDC0 BC (v01 HP ProLiant 0001 ??   
162E)
ACPI: DMAR 0xDF62FE80 00017C (v01 HP ProLiant 0001 ??   
162E)
ACPI: SSDT 0xDF632600 000125 (v03 HP CRSPCI0  0002 HP   
0001)
ACPI: SSDT 0xDF632740 000255 (v03 HP riser1a  0002 INTL 
20061109)
ACPI: SSDT 0xDF6329C0 00025D (v03 HP riser2a  0002 INTL 
20061109)
ACPI: SSDT 0xDF632C40 0003BB (v01 HP pcc  0001 INTL 
20090625)
ACPI: SSDT 0xDF633000 000377 (v01 HP pmab 0001 INTL 
20090625)
ACPI: SSDT 0xDF633380 002B64 (v01 INTEL  PPM RCM  0001 INTL 
20061109)
ACPI: 7 ACPI AML tables successfully acquired and loaded
ioapic0 at mainbus0 apid 8: pa 0xfec0, version 0x20, 24 pins
ioapic1 at mainbus0 apid 0: pa 0xfec8, version 0x20, 24 pins
cpu0 at mainbus0 apid 0
cpu0: Intel(R) Xeon(R) CPU   E5630  @ 2.53GHz, id 0x206c2
cpu0: package 0, core 0, smt 0
cpu1 at mainbus0 apid 32
cpu1: Intel(R) Xeon(R) CPU   E5630  @ 2.53GHz, id 0x206c2
cpu1: package 1, core 0, smt 0
cpu2 at mainbus0 apid 20
cpu2: Intel(R) Xeon(R) CPU   E5630  @ 2.53GHz, id 0x206c2
cpu2: package 0, core 10, smt 0
cpu3 at mainbus0 apid 52
cpu3: Intel(R) Xeon(R) CPU   E5630  @ 2.53GHz, id 0x206c2
cpu3: package 1, core 10, smt 0
cpu4 at mainbus0 apid 2
cpu4: Intel(R) Xeon(R) CPU   E5630  @ 2.53GHz, id 0x206c2
cpu4: package 0, core 1, smt 0
cpu5 at mainbus0 apid 34
cpu5: Intel(R) Xeon(R) CPU   E5630  @ 2.53GHz, id 0x206c2
cpu5: package 1, core 1, smt 0
cpu6 at mainbus0 apid 18
cpu6: Intel(R) Xeon(R) CPU   E5630  @ 2.53GHz, id 0x206c2
cpu6: package 0, core 9, smt 0
cpu7 at mainbus0 apid 50
cpu7: Intel(R) Xeon(R) CPU   E5630  @ 2.53GHz, id 0x206c2
cpu7: package 1, core 9, smt 0
cpu8 at mainbus0 apid 1
cpu8: Intel(R) Xeon(R) CPU   E5630  @ 2.53GHz, id 0x206c2
cpu8: package 0, core 0, smt 1
cpu9 at mainbus0 apid 33
cpu9: Intel(R) Xeon(R) CPU   E5630  @ 2.53GHz, id 0x206c2
cpu9: package 1, core 0, smt 1
cpu10 at mainbus0 apid 21
cpu10: Intel(R) Xeon(R) CPU   E5630  @ 2.53GHz, id 0x206c2
cpu10: package 0, core 10, smt 1
cpu11 at mainbus0 apid 53
cpu11: Intel(R) Xeon(R) CPU   E5630  @ 2.5

Re: netbsd-8 crash in ixg driver during booting

2017-11-15 Thread Masanobu SAITOH 

Hi, Uwe.

On 2017/11/15 15:41, 6b...@6bone.informatik.uni-leipzig.de wrote:


Does your machine boot with the latest -current?


I have tested the current sources from tonight.

https://suse.uni-leipzig.de/crash/crash-current1.jpg
https://suse.uni-leipzig.de/crash/crash-current2.jpg

Regards
Uwe


 Thank you for the report.

 This problem is different from ixg(4)'s problem. I'll now
working to fix this softint related problem.

 This problem is caused by some devices which uses a lot of
softint, could you tell me the machine's spec? e.g.:

number of port of wm(4) and/or ixg(4)
number of nvme(4)
etc.

Thanks in advance.

--
---
SAITOH Masanobu (msai...@execsw.org
 msai...@netbsd.org)

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

Re: netbsd-8 crash in ixg driver during booting

2017-11-13 Thread 6bone 

On Sun, 12 Nov 2017, SAITOH Masanobu wrote:

Hello,

I checked out the current-cvs-source from this morning. I can't compile it 
because of an error:


--- streambuf-inst.o ---
#   compile  libstdc++-v3/streambuf-inst.o
/usr/src/obj/tooldir.NetBSD-8.0_BETA-amd64/bin/x86_64--netbsd-c++ 
-frandom-seed=fd5fac20 -O2 -Wall -Wpointer-arith -Wno-sign-compare 
-Wsystem-headers -Wa,--fatal-warnings -Werror -fPIE 
-fno-implicit-templates -fdiagnostics-show-location=once 
--sysroot=/usr/src/obj/destdir.amd64 
-I/usr/src/external/gpl3/gcc.old/dist/gcc 
-I/usr/src/external/gpl3/gcc.old/dist/include 
-I/usr/src/external/gpl3/gcc.old/dist/libstdc++-v3/libsupc++ 
-I/usr/src/external/gpl3/gcc.old/dist/libgcc 
-I/usr/src/external/gpl3/gcc.old/lib/libstdc++-v3/../libstdc++-v3/arch/x86_64 
-I. -DHAVE_STDLIB_H -DHAVE_STRING_H 
-I/usr/src/external/gpl3/gcc.old/dist/libstdc++-v3/include 
-I/usr/src/external/gpl3/gcc.old/lib/libstdc++-v3/arch/x86_64 
-D_GLIBCXX_SHARED -DGTHREAD_USE_WEAK -DSUPPORTS_WEAK  -c -std=gnu++11 
/usr/src/external/gpl3/gcc.old/dist/libstdc++-v3/src/c++11/streambuf-inst.cc 
-o streambuf-inst.o

--- random.o ---
*** [random.o] Error code 1

nbmake[6]: stopped in /usr/src/external/gpl3/gcc.old/lib/libstdc++-v3
--- iostream-inst.o ---


Regards
Uwe




Does your machine boot with the latest -current?
If it boots, could you show the dmesg output with the
following patch?

http://www.netbsd.org/~msaitoh/ixgbe-current-20171112-0.dif

And, if you can, please test for netbsd-8 using with
the following patch and how the dmesg output:

http://www.netbsd.org/~msaitoh/ixgbe-n8-20171112-0.dif


Thanks in advance.





https://suse.uni-leipzig.de/crash/crash2.jpg
https://suse.uni-leipzig.de/crash/crash3.jpg

My old kernel from August 2017 did not have the problem yet.

Can someone take a look at the problem?

Thank you for your Efforts

Regards
Uwe







--
---
   SAITOH Masanobu (msai...@execsw.org
msai...@netbsd.org)

Re: netbsd-8 crash in ixg driver during booting

2017-11-11 Thread SAITOH Masanobu 
 Hi, Uwe.

On 2017/11/12 8:53, SAITOH Masanobu wrote:
>  Hi, all.
> 
> 
> On 2017/11/10 0:02, Chavdar Ivanov wrote:
>> My (very uneducated) guess would be that for some reason adapter->num_queues 
>> does not get initialised. There have been quite a few commits recently here 
>> (although I am looking at -current, I suppose they have been done to 8 as 
>> well). 
> 
>  It might be easy to fix this panic but I can't because I'm now
> attending BSDTW17 in Taipei. I'll be back to Tokyo Monday night.
> 
>  A lot of changes and fixes have done in -current but the pullup
> request for netbsd-8 have not been sent yet. It would take a few
> weeks or more.
> 
>  Thanks.
> 
> 
>> Chavdar Ivanov
>>
>> On Thu, 9 Nov 2017 at 14:18 <6b...@6bone.informatik.uni-leipzig.de 
>> > wrote:
>>
>> the current version of netbsd-8 crashes while booting during the
>> initialization of the network driver.
>>
>> https://suse.uni-leipzig.de/crash/crash1.jpg

 Does your machine boot with the latest -current?
If it boots, could you show the dmesg output with the
following patch?

http://www.netbsd.org/~msaitoh/ixgbe-current-20171112-0.dif

And, if you can, please test for netbsd-8 using with
the following patch and how the dmesg output:

http://www.netbsd.org/~msaitoh/ixgbe-n8-20171112-0.dif


 Thanks in advance.




>> https://suse.uni-leipzig.de/crash/crash2.jpg
>> https://suse.uni-leipzig.de/crash/crash3.jpg
>>
>> My old kernel from August 2017 did not have the problem yet.
>>
>> Can someone take a look at the problem?
>>
>> Thank you for your Efforts
>>
>> Regards
>> Uwe
>>
> 
> 


-- 
---
SAITOH Masanobu (msai...@execsw.org
 msai...@netbsd.org)

Re: netbsd-8 crash in ixg driver during booting

2017-11-11 Thread SAITOH Masanobu 
 Hi, all.


On 2017/11/10 0:02, Chavdar Ivanov wrote:
> My (very uneducated) guess would be that for some reason adapter->num_queues 
> does not get initialised. There have been quite a few commits recently here 
> (although I am looking at -current, I suppose they have been done to 8 as 
> well). 

 It might be easy to fix this panic but I can't because I'm now
attending BSDTW17 in Taipei. I'll be back to Tokyo Monday night.

 A lot of changes and fixes have done in -current but the pullup
request for netbsd-8 have not been sent yet. It would take a few
weeks or more.

 Thanks.


> Chavdar Ivanov
> 
> On Thu, 9 Nov 2017 at 14:18 <6b...@6bone.informatik.uni-leipzig.de 
> > wrote:
> 
> the current version of netbsd-8 crashes while booting during the
> initialization of the network driver.
> 
> https://suse.uni-leipzig.de/crash/crash1.jpg
> https://suse.uni-leipzig.de/crash/crash2.jpg
> https://suse.uni-leipzig.de/crash/crash3.jpg
> 
> My old kernel from August 2017 did not have the problem yet.
> 
> Can someone take a look at the problem?
> 
> Thank you for your Efforts
> 
> Regards
> Uwe
> 


-- 
---
SAITOH Masanobu (msai...@execsw.org
 msai...@netbsd.org)

Re: netbsd-8 crash in ixg driver during booting

2017-11-09 Thread Chavdar Ivanov 
My (very uneducated) guess would be that for some reason
adapter->num_queues does not get initialised. There have been quite a few
commits recently here (although I am looking at -current, I suppose they
have been done to 8 as well).

Chavdar Ivanov

On Thu, 9 Nov 2017 at 14:18 <6b...@6bone.informatik.uni-leipzig.de> wrote:

> the current version of netbsd-8 crashes while booting during the
> initialization of the network driver.
>
> https://suse.uni-leipzig.de/crash/crash1.jpg
> https://suse.uni-leipzig.de/crash/crash2.jpg
> https://suse.uni-leipzig.de/crash/crash3.jpg
>
> My old kernel from August 2017 did not have the problem yet.
>
> Can someone take a look at the problem?
>
> Thank you for your Efforts
>
> Regards
> Uwe
>

netbsd-8 crash in ixg driver during booting

2017-11-09 Thread 6bone 
the current version of netbsd-8 crashes while booting during the 
initialization of the network driver.


https://suse.uni-leipzig.de/crash/crash1.jpg
https://suse.uni-leipzig.de/crash/crash2.jpg
https://suse.uni-leipzig.de/crash/crash3.jpg

My old kernel from August 2017 did not have the problem yet.

Can someone take a look at the problem?

Thank you for your Efforts

Regards
Uwe