Re: Panic with recent -current with interrupt setup
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 really intrusive stuff coming next, so things are really going to break :-) I'll probably check them in around Wednesday midday UTC. Cheers, -- ~cherry
Re: Panic with recent -current with interrupt setup
"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-09-29 and 2018-10-01 panic, but 2018-09-23 doesn't]. This is with >>> trying to use the stock XEN3_DOM0 kernel on a new system I am setting >>> up. The panics seem related to setting up interrupts or printing >>> interrupt information in the intel wm(4) driver. The system in question >>> does not have a serial port on it in any form, but I can probably >>> capture a screen shot of the panic. The keyboard works and ddb seems >>> usable. >> >> I ran an automted test of -current from CVS source date >> 2018.10.01.17.50.08, and can confirm that it also panics >> on my HP DL360 G7, under both Xen 4.8 and 4.11. Logs at: >> >> http://www.gson.org/netbsd/bugs/xen/results/2018-10-02/index.html > > Thanks Andreas, Brad. I'm aware of this problem and the fix (msaitoh@ > tried and confirmed it works), and will sort it out as soon as I'm > confident it's the right approach. > > Sorry for the breakage. I have checked in a couple of changes, which hopefully should fix the problem. I look forward to user reports. Many Thanks, -- ~cherry
Re: Panic with recent -current with interrupt setup
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! -- Andreas Gustafsson, g...@gson.org
Re: Panic with recent -current with interrupt setup
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 of xen/x86/pintr.c 1.6), I get: > > [ 1.030] bnx0 at pci7 dev 0 function 0: Broadcom NetXtreme II BCM5709 > 1000Base-T > [ 1.030] bnx0: Ethernet address 98:4b:e1:67:68:98 > (XEN) irq.c:1943: dom0: pirq 10 or irq 30 already mapped (0,28) > [ 1.030] panic: kernel diagnostic assertion "irq2port[irq] == 0" > failed: file > "/tmp/bracket/build/2018.10.06.16.49.54-amd64/src/sys/arch/x86/x86/ioapic.c", > line 583 > > The full log is at: > > > http://www.gson.org/netbsd/bugs/xen/results/2018-10-07/data-411-current-2018.10.06.16.49.54-amd64/clean.txt Thank you - I've checked in a temporary 'fix'. This will sort itself out once the interrupt rework to merge with native is complete. I hope it works, Many Thanks, -- ~cherry
Re: Panic with recent -current with interrupt setup
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 of xen/x86/pintr.c 1.6), I get: [ 1.030] bnx0 at pci7 dev 0 function 0: Broadcom NetXtreme II BCM5709 1000Base-T [ 1.030] bnx0: Ethernet address 98:4b:e1:67:68:98 (XEN) irq.c:1943: dom0: pirq 10 or irq 30 already mapped (0,28) [ 1.030] panic: kernel diagnostic assertion "irq2port[irq] == 0" failed: file "/tmp/bracket/build/2018.10.06.16.49.54-amd64/src/sys/arch/x86/x86/ioapic.c", line 583 The full log is at: http://www.gson.org/netbsd/bugs/xen/results/2018-10-07/data-411-current-2018.10.06.16.49.54-amd64/clean.txt -- Andreas Gustafsson, g...@gson.org
Re: Panic with recent -current with interrupt setup
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 stock XEN3_DOM0 kernel on a new system I am setting >> up. The panics seem related to setting up interrupts or printing >> interrupt information in the intel wm(4) driver. The system in question >> does not have a serial port on it in any form, but I can probably >> capture a screen shot of the panic. The keyboard works and ddb seems >> usable. > > I ran an automted test of -current from CVS source date > 2018.10.01.17.50.08, and can confirm that it also panics > on my HP DL360 G7, under both Xen 4.8 and 4.11. Logs at: > > http://www.gson.org/netbsd/bugs/xen/results/2018-10-02/index.html Thanks Andreas, Brad. I'm aware of this problem and the fix (msaitoh@ tried and confirmed it works), and will sort it out as soon as I'm confident it's the right approach. Sorry for the breakage. -- ~cherry
Re: Panic with recent -current with interrupt setup
Masanobu SAITOH writes: > On 2018/10/03 5:47, Brad Spencer wrote: >> m...@netbsd.org writes: >> >>> On Tue, Oct 02, 2018 at 06:55:48AM -0400, Brad Spencer wrote: [snip] >> Here is more information: >> >> Screen shot of the panic: >> http://www.netbsd.org/~brad/PANIC_1.jpg >> http://www.netbsd.org/~brad/PANIC_2.jpg >> >> Screen shot of the ddb bt command, sorry for the quality: >> http://www.netbsd.org/~brad/BT_1.jpg >> http://www.netbsd.org/~brad/BT_2.jpg >> http://www.netbsd.org/~brad/BT_3.jpg >> >> Hopefully I also managed to attach a couple of files that are of a >> working NetBSD dmesg and a working xl dmesg. The Xen version I am using >> is 4.8.3 built from source pulled from HEAD on Saturday or so. >> >> This system is pretty new. It has a 4 core Ryzen CPU, 16GB memory. A >> two port Intel NIC is also present, that would be wm0 and wm1 in the >> dmesg. The motherboard has a Intel NIC on it as well, which is wm2. >> >> If I do a dmesg in ddb I can get the reason for the panic: >> >> panic: kernel diagnostic assertion "irq2vect[irq] == 0" failed: >> file"/usr/src/sys/arch/xen/x86/pintr.c", line 202 >> >> It looks like this may have triggered on the onboard wm2 interface. >> > > Try to revert x86/pci/pci_intr_machdep.c rev. 1.45: > > http://mail-index.netbsd.org/source-changes/2018/09/23/msg099361.html Reverting to version 1.44 of x86/pci/pci_intr_machdep.c eliminated the panic and the system boots up. Version 1.45 is a revert itself, but there must be something in it that a Xen DOM0 needs. -- Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
Re: Panic with recent -current with interrupt setup
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 stock XEN3_DOM0 kernel on a new system I am setting > up. The panics seem related to setting up interrupts or printing > interrupt information in the intel wm(4) driver. The system in question > does not have a serial port on it in any form, but I can probably > capture a screen shot of the panic. The keyboard works and ddb seems > usable. I ran an automted test of -current from CVS source date 2018.10.01.17.50.08, and can confirm that it also panics on my HP DL360 G7, under both Xen 4.8 and 4.11. Logs at: http://www.gson.org/netbsd/bugs/xen/results/2018-10-02/index.html -- Andreas Gustafsson, g...@gson.org
Re: Panic with recent -current with interrupt setup
On 2018/10/03 5:47, Brad Spencer wrote: m...@netbsd.org writes: On Tue, Oct 02, 2018 at 06:55:48AM -0400, 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 stock XEN3_DOM0 kernel on a new system I am setting up. The panics seem related to setting up interrupts or printing interrupt information in the intel wm(4) driver. The system in question does not have a serial port on it in any form, but I can probably capture a screen shot of the panic. The keyboard works and ddb seems usable. I assume this is related to cherry's recent xen interrupt work. If you're unable to type at the ddb prompt but can reproduce the crash, but can see the output, it'd be interesting to see if it gives more info with options DDB_COMMANDONENTER="bt" As a kernel option. But having the panic string would be nice too. Here is more information: Screen shot of the panic: http://www.netbsd.org/~brad/PANIC_1.jpg http://www.netbsd.org/~brad/PANIC_2.jpg Screen shot of the ddb bt command, sorry for the quality: http://www.netbsd.org/~brad/BT_1.jpg http://www.netbsd.org/~brad/BT_2.jpg http://www.netbsd.org/~brad/BT_3.jpg Hopefully I also managed to attach a couple of files that are of a working NetBSD dmesg and a working xl dmesg. The Xen version I am using is 4.8.3 built from source pulled from HEAD on Saturday or so. This system is pretty new. It has a 4 core Ryzen CPU, 16GB memory. A two port Intel NIC is also present, that would be wm0 and wm1 in the dmesg. The motherboard has a Intel NIC on it as well, which is wm2. If I do a dmesg in ddb I can get the reason for the panic: panic: kernel diagnostic assertion "irq2vect[irq] == 0" failed: file"/usr/src/sys/arch/xen/x86/pintr.c", line 202 It looks like this may have triggered on the onboard wm2 interface. Try to revert x86/pci/pci_intr_machdep.c rev. 1.45: http://mail-index.netbsd.org/source-changes/2018/09/23/msg099361.html -- --- SAITOH Masanobu (msai...@execsw.org msai...@netbsd.org)
Re: Panic with recent -current with interrupt setup
m...@netbsd.org writes: > On Tue, Oct 02, 2018 at 06:55:48AM -0400, 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 stock XEN3_DOM0 kernel on a new system I am setting >> up. The panics seem related to setting up interrupts or printing >> interrupt information in the intel wm(4) driver. The system in question >> does not have a serial port on it in any form, but I can probably >> capture a screen shot of the panic. The keyboard works and ddb seems >> usable. > > I assume this is related to cherry's recent xen interrupt work. > If you're unable to type at the ddb prompt but can reproduce the crash, > but can see the output, it'd be interesting to see if it gives more > info with > > options DDB_COMMANDONENTER="bt" > > As a kernel option. > > But having the panic string would be nice too. Here is more information: Screen shot of the panic: http://www.netbsd.org/~brad/PANIC_1.jpg http://www.netbsd.org/~brad/PANIC_2.jpg Screen shot of the ddb bt command, sorry for the quality: http://www.netbsd.org/~brad/BT_1.jpg http://www.netbsd.org/~brad/BT_2.jpg http://www.netbsd.org/~brad/BT_3.jpg Hopefully I also managed to attach a couple of files that are of a working NetBSD dmesg and a working xl dmesg. The Xen version I am using is 4.8.3 built from source pulled from HEAD on Saturday or so. This system is pretty new. It has a 4 core Ryzen CPU, 16GB memory. A two port Intel NIC is also present, that would be wm0 and wm1 in the dmesg. The motherboard has a Intel NIC on it as well, which is wm2. If I do a dmesg in ddb I can get the reason for the panic: panic: kernel diagnostic assertion "irq2vect[irq] == 0" failed: file"/usr/src/sys/arch/xen/x86/pintr.c", line 202 It looks like this may have triggered on the onboard wm2 interface. [ 1.00] Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, [ 1.00] 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, [ 1.00] 2018 The NetBSD Foundation, Inc. All rights reserved. [ 1.00] Copyright (c) 1982, 1986, 1989, 1991, 1993 [ 1.00] The Regents of the University of California. All rights reserved. [ 1.00] NetBSD 8.99.25 (XEN3_DOM0) #0: Sat Sep 22 05:24:22 UTC 2018 [ 1.00] mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/xen/compile/XEN3_DOM0 [ 1.00] total memory = 4096 MB [ 1.00] avail memory = 3948 MB [ 1.00] cpu_rng: RDSEED [ 1.00] timecounter: Timecounters tick every 10.000 msec [ 1.00] Kernelized RAIDframe activated [ 1.00] running cgd selftest aes-xts-256 aes-xts-512 done [ 1.00] To Be Filled By O.E.M. To Be Filled By O.E.M. (To Be Filled By O.E.M.) [ 1.00] mainbus0 (root) [ 1.00] ACPI: RSDP 0x000F05B0 24 (v02 ALASKA) [ 1.00] ACPI: XSDT 0xDC0210A0 BC (v01 ALASKA A M I 01072009 AMI 00010013) [ 1.00] ACPI: FACP 0xDC0278F0 000114 (v06 ALASKA A M I 01072009 AMI 00010013) [ 1.00] Firmware Warning (ACPI): Optional FADT field Pm2ControlBlock has valid Length but zero Address: 0x/0x1 (20180810/tbfadt-693) [ 1.00] ACPI: DSDT 0xDC0211F0 0066FC (v02 ALASKA A M I 01072009 INTL 20120913) [ 1.00] ACPI: FACS 0xDC3D1E00 40 [ 1.00] ACPI: APIC 0xDC027A08 DE (v03 ALASKA A M I 01072009 AMI 00010013) [ 1.00] ACPI: FPDT 0xDC027AE8 44 (v01 ALASKA A M I 01072009 AMI 00010013) [ 1.00] ACPI: FIDT 0xDC027B30 9C (v01 ALASKA A M I 01072009 AMI 00010013) [ 1.00] ACPI: SSDT 0xDC027BD0 00533D (v02 AMDAmdTable 0002 MSFT 0202) [ 1.00] ACPI: SSDT 0xDC02CF10 0007DC (v01 AMDAMD CPU 0001 AMD 0001) [ 1.00] ACPI: CRAT 0xDC02D6F0 000810 (v01 AMDAMD CRAT 0001 AMD 0001) [ 1.00] ACPI: CDIT 0xDC02DF00 29 (v01 AMDAMD CDIT 0001 AMD 0001) [ 1.00] ACPI: SSDT 0xDC02DF30 002C9B (v01 AMDAMD AOD 0001 INTL 20120913) [ 1.00] ACPI: MCFG 0xDC030BD0 3C (v01 ALASKA A M I 01072009 MSFT 00010013) [ 1.00] ACPI: AAFT 0xDC030C10 000200 (v01 ALASKA OEMAAFT 01072009 MSFT 0097) [ 1.00] ACPI: HPET 0xDC030E10 38 (v01 ALASKA A M I 01072009 AMI 0005) [ 1.00] ACPI: UEFI 0xDC030E48 42 (v01 ) [ 1.00] ACPI: IVRS 0xDC030E90 D0 (v02 AMDAMD IVRS 0001 AMD ) [ 1.00] ACPI: SSDT 0xDC030F60 000E96 (v01 AMDAmdTable 0001 INTL 20120913) [ 1.00] ACPI: SSDT 0xDC031DF8 000850 (v01 AMD
Re: Panic with recent -current with interrupt setup
On Tue, Oct 02, 2018 at 06:55:48AM -0400, 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 stock XEN3_DOM0 kernel on a new system I am setting > up. The panics seem related to setting up interrupts or printing > interrupt information in the intel wm(4) driver. The system in question > does not have a serial port on it in any form, but I can probably > capture a screen shot of the panic. The keyboard works and ddb seems > usable. I assume this is related to cherry's recent xen interrupt work. If you're unable to type at the ddb prompt but can reproduce the crash, but can see the output, it'd be interesting to see if it gives more info with optionsDDB_COMMANDONENTER="bt" As a kernel option. But having the panic string would be nice too.
Panic with recent -current with interrupt setup
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 stock XEN3_DOM0 kernel on a new system I am setting up. The panics seem related to setting up interrupts or printing interrupt information in the intel wm(4) driver. The system in question does not have a serial port on it in any form, but I can probably capture a screen shot of the panic. The keyboard works and ddb seems usable. -- Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
