6.5 stable SMP (2 processor) Kernel panic when ifconfig is called and there are 2 bridges are running in two different Rdomains

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

6.5 stable SMP (2 processor) Kernel panic when ifconfig is called and there are 2 bridges are running in two different Rdomains

Tom Smyth
Hello
Kernel panic when ifconfig is called and 2 bridges are running in two
different rdomains

cat /etc/hostname.bridge240
rdomain 240
maxaddr 16384
timeout 300
up
add vlan1097 blocknonip vlan1097 -stp vlan1097
add vlan240 blocknonip vlan240 -stp vlan240


cat /etc/hostname.bridge101

 cat /root/hostname.bridge101
maxaddr 16384
timeout 300
up
add vio2 blocknonip vio2 -stp vio2
add vlan101 blocknonip vlan101 -stp vlan101


the crash does not happen when the two bridges are in the same rdomain.

the crash seems to occur if  i run
ifconfig bridge


ifconfig bridge
bridge240: flags=41<UP,RUNNING>
        index 7 llprio 3
        groups: bridge
        priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto
rstp
        designated: id 00:00:00:00:00:00 priority 0
        vlan240 flags=7<LEARNING,DISCOVER,BLOCKNONIP>
                port 14 ifpriority 0 ifcost 0
        vlan1097 flags=7<LEARNING,DISCOVER,BLOCKNONIP>
                port 13 ifpriority 0 ifcost 0
        Addresses (max cache: 16384, timeout: 300):
                7a:cb:d2:c3:28:70 vlan1097 1 flags=0<>
bridge101: flags=41<UP,RUNNING>
        index 16 llprio 3
        groups: bridge
        priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto
rstp
        designated: id 00:00:00:00:00:00 priority 0
        vlan101 flags=7<LEARNING,DISCOVER,BLOCKNONIP>
                port 11 ifpriority 0 ifcost 0
        vio2 flags=7<LEARNING,DISCOVER,BLOCKNONIP>
                port 3 ifpriority 0 ifcost 0
        Addresses (max cache: 16384, timeout: 300):

No further output is observed and the there is a panic msg on the vga
console

I have attached images of the panic and I have tried to follow ddb  output
debugging as best I can

Thanks
Tom smyth





--
Kindest regards,
Tom Smyth.

mach-ddbcpu-0.png (35K) Download Attachment
ps-list01.png (35K) Download Attachment
mach-ddbcpu-1.png (34K) Download Attachment
Bridge-bug01.png (31K) Download Attachment
6.5stop.png (93K) Download Attachment
ps-list02.png (35K) Download Attachment
mach-ddbcpu-1-trace.png (31K) Download Attachment
ps-list03.png (35K) Download Attachment
mach-ddbcpu-0-trace.png (35K) Download Attachment
show-panic.png (31K) Download Attachment
kernlock.c-shownindump.png (29K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: 6.5 stable SMP (2 processor) Kernel panic when ifconfig is called and there are 2 bridges are running in two different Rdomains

Tom Smyth
Further testing

show that Rdomains and the bridge may not be the issue,  as starting both
bridges from boot in the same rdomain (rdomain0 )

and then running ifconfig bridge
caused the crash
Ill try to isolate the exact config that is causing the issue further

On Thu, 23 May 2019 at 02:29, Tom Smyth <[hidden email]>
wrote:

> Hello
> Kernel panic when ifconfig is called and 2 bridges are running in two
> different rdomains
>
> cat /etc/hostname.bridge240
> rdomain 240
> maxaddr 16384
> timeout 300
> up
> add vlan1097 blocknonip vlan1097 -stp vlan1097
> add vlan240 blocknonip vlan240 -stp vlan240
>
>
> cat /etc/hostname.bridge101
>
>  cat /root/hostname.bridge101
> maxaddr 16384
> timeout 300
> up
> add vio2 blocknonip vio2 -stp vio2
> add vlan101 blocknonip vlan101 -stp vlan101
>
>
> the crash does not happen when the two bridges are in the same rdomain.
>
> the crash seems to occur if  i run
> ifconfig bridge
>
>
> ifconfig bridge
> bridge240: flags=41<UP,RUNNING>
>         index 7 llprio 3
>         groups: bridge
>         priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto
> rstp
>         designated: id 00:00:00:00:00:00 priority 0
>         vlan240 flags=7<LEARNING,DISCOVER,BLOCKNONIP>
>                 port 14 ifpriority 0 ifcost 0
>         vlan1097 flags=7<LEARNING,DISCOVER,BLOCKNONIP>
>                 port 13 ifpriority 0 ifcost 0
>         Addresses (max cache: 16384, timeout: 300):
>                 7a:cb:d2:c3:28:70 vlan1097 1 flags=0<>
> bridge101: flags=41<UP,RUNNING>
>         index 16 llprio 3
>         groups: bridge
>         priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto
> rstp
>         designated: id 00:00:00:00:00:00 priority 0
>         vlan101 flags=7<LEARNING,DISCOVER,BLOCKNONIP>
>                 port 11 ifpriority 0 ifcost 0
>         vio2 flags=7<LEARNING,DISCOVER,BLOCKNONIP>
>                 port 3 ifpriority 0 ifcost 0
>         Addresses (max cache: 16384, timeout: 300):
>
> No further output is observed and the there is a panic msg on the vga
> console
>
> I have attached images of the panic and I have tried to follow ddb  output
> debugging as best I can
>
> Thanks
> Tom smyth
>
>
>
>
>
> --
> Kindest regards,
> Tom Smyth.
>


--
Kindest regards,
Tom Smyth.
Reply | Threaded
Open this post in threaded view
|

Re: 6.5 stable SMP (2 processor) Kernel panic when ifconfig is called and there are 2 bridges are running in two different Rdomains

Tom Smyth
Hello all,

the issue was not related to 2 bridges, or 2 rdomains as previously thought

it seems to be related to the bridge and the virtio network driver vio

by adding 1 virtio  vio interface into just 1 bridge
and then running ifconfig bridge causes the kernel panic

demsg is shown below

WARNING: SPL NOT LOWERED ON SYSCALL 54 3 EXIT 0 9
Stopped at      savectx+0xb1:   movl    $0,%gs:0x508
ddb{0}> rebooting...
OpenBSD 6.5 (GENERIC.MP) #3: Sat Apr 13 14:48:43 MDT 2019
    [hidden email]:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 4278042624 (4079MB)
avail mem = 4138766336 (3947MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xf69e0 (10 entries)
bios0: vendor SeaBIOS version "
rel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org" date 04/01/2014
bios0: QEMU Standard PC (i440FX + PIIX, 1996)
acpi0 at bios0: rev 0
acpi0: sleep states S3 S4 S5
acpi0: tables DSDT FACP APIC HPET SRAT
acpi0: wakeup devices
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Xeon(R) CPU E5-2660 v2 @ 2.20GHz, 486.78 MHz, 06-3e-04
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SS,HTT,SSE3,PCLMUL,SSSE3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,OSXSAVE,AVX,F16C,RDRAND,HV,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,FSGSBASE,SMEP,ERMS,ARAT,XSAVEOPT,MELTDOWN
cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB
64b/line 16-way L2 cache
cpu0: ITLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped
cpu0: DTLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 999MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Xeon(R) CPU E5-2660 v2 @ 2.20GHz, 681.80 MHz, 06-3e-04
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SS,HTT,SSE3,PCLMUL,SSSE3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,OSXSAVE,AVX,F16C,RDRAND,HV,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,FSGSBASE,SMEP,ERMS,ARAT,XSAVEOPT,MELTDOWN
cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB
64b/line 16-way L2 cache
cpu1: ITLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped
cpu1: DTLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped
cpu1: smt 0, core 1, package 0
ioapic0 at mainbus0: apid 0 pa 0xfec00000, version 11, 24 pins
acpihpet0 at acpi0: 100000000 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpicpu0 at acpi0: C1(@1 halt!)
acpicpu1 at acpi0: C1(@1 halt!)
"ACPI0006" at acpi0 not configured
acpipci0 at acpi0 PCI0: _OSC failed
acpicmos0 at acpi0
"PNP0A06" at acpi0 not configured
"PNP0A06" at acpi0 not configured
"PNP0A06" at acpi0 not configured
"QEMU0002" at acpi0 not configured
"ACPI0010" at acpi0 not configured
pvbus0 at mainbus0: KVM
pvclock0 at pvbus0
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel 82441FX" rev 0x02
pcib0 at pci0 dev 1 function 0 "Intel 82371SB ISA" rev 0x00
pciide0 at pci0 dev 1 function 1 "Intel 82371SB IDE" rev 0x00: DMA, channel
0 wired to compatibility, channel 1 wired to compatibility
pciide0: channel 0 disabled (no drives)
atapiscsi0 at pciide0 channel 1 drive 0
scsibus1 at atapiscsi0: 2 targets
cd0 at scsibus1 targ 0 lun 0: <QEMU, QEMU DVD-ROM, 2.5+> ATAPI 5/cdrom
removable
cd0(pciide0:1:0): using PIO mode 4, DMA mode 2
uhci0 at pci0 dev 1 function 2 "Intel 82371SB USB" rev 0x01: apic 0 int 11
piixpm0 at pci0 dev 1 function 3 "Intel 82371AB Power" rev 0x03: apic 0 int
9
iic0 at piixpm0
vga1 at pci0 dev 2 function 0 "Cirrus Logic CL-GD5446" rev 0x00
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
virtio0 at pci0 dev 5 function 0 "Qumranet Virtio SCSI" rev 0x00
vioscsi0 at virtio0: qsize 128
scsibus2 at vioscsi0: 255 targets
sd0 at scsibus2 targ 0 lun 0: <QEMU, QEMU HARDDISK, 2.5+> SCSI3 0/direct
fixed
sd0: 10240MB, 512 bytes/sector, 20971520 sectors, thin
virtio0: msix shared
virtio1 at pci0 dev 18 function 0 "Qumranet Virtio Network" rev 0x00
vio0 at virtio1: address aa:02:1f:b0:88:4f
virtio1: msix shared
virtio2 at pci0 dev 19 function 0 "Qumranet Virtio Network" rev 0x00
vio1 at virtio2: address 46:61:59:0f:0a:5b
virtio2: msix shared
virtio3 at pci0 dev 20 function 0 "Qumranet Virtio Network" rev 0x00
vio2 at virtio3: address 5a:1f:d8:36:03:ba
virtio3: msix shared
virtio4 at pci0 dev 21 function 0 "Qumranet Virtio Network" rev 0x00
vio3 at virtio4: address e2:c4:9e:98:90:1f
virtio4: msix shared
ppb0 at pci0 dev 30 function 0 "Red Hat Qemu PCI-PCI" rev 0x00
pci1 at ppb0 bus 1
ppb1 at pci0 dev 31 function 0 "Red Hat Qemu PCI-PCI" rev 0x00
pci2 at ppb1 bus 2
isa0 at pcib0
isadma0 at isa0
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pms0 at pckbc0 (aux slot)
wsmouse0 at pms0 mux 0
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
usb0 at uhci0: USB revision 1.0
uhub0 at usb0 configuration 1 interface 0 "Intel UHCI root hub" rev
1.00/1.00 addr 1
vscsi0 at root
scsibus3 at vscsi0: 256 targets
softraid0 at root
scsibus4 at softraid0: 256 targets
root on sd0a (1daaa231ebc31d47.a) swap on sd0b dump on sd0b
WARNING: / was not properly unmounted
fd0 at fdc0 drive 1: density unknown

I hope this helps,


Tom Smyth



I hope this helps

Tom Smyth


On Thu, 23 May 2019 at 02:47, Tom Smyth <[hidden email]>
wrote:

> Further testing
>
> show that Rdomains and the bridge may not be the issue,  as starting both
> bridges from boot in the same rdomain (rdomain0 )
>
> and then running ifconfig bridge
> caused the crash
> Ill try to isolate the exact config that is causing the issue further
>
> On Thu, 23 May 2019 at 02:29, Tom Smyth <[hidden email]>
> wrote:
>
>> Hello
>> Kernel panic when ifconfig is called and 2 bridges are running in two
>> different rdomains
>>
>> cat /etc/hostname.bridge240
>> rdomain 240
>> maxaddr 16384
>> timeout 300
>> up
>> add vlan1097 blocknonip vlan1097 -stp vlan1097
>> add vlan240 blocknonip vlan240 -stp vlan240
>>
>>
>> cat /etc/hostname.bridge101
>>
>>  cat /root/hostname.bridge101
>> maxaddr 16384
>> timeout 300
>> up
>> add vio2 blocknonip vio2 -stp vio2
>> add vlan101 blocknonip vlan101 -stp vlan101
>>
>>
>> the crash does not happen when the two bridges are in the same rdomain.
>>
>> the crash seems to occur if  i run
>> ifconfig bridge
>>
>>
>> ifconfig bridge
>> bridge240: flags=41<UP,RUNNING>
>>         index 7 llprio 3
>>         groups: bridge
>>         priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto
>> rstp
>>         designated: id 00:00:00:00:00:00 priority 0
>>         vlan240 flags=7<LEARNING,DISCOVER,BLOCKNONIP>
>>                 port 14 ifpriority 0 ifcost 0
>>         vlan1097 flags=7<LEARNING,DISCOVER,BLOCKNONIP>
>>                 port 13 ifpriority 0 ifcost 0
>>         Addresses (max cache: 16384, timeout: 300):
>>                 7a:cb:d2:c3:28:70 vlan1097 1 flags=0<>
>> bridge101: flags=41<UP,RUNNING>
>>         index 16 llprio 3
>>         groups: bridge
>>         priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto
>> rstp
>>         designated: id 00:00:00:00:00:00 priority 0
>>         vlan101 flags=7<LEARNING,DISCOVER,BLOCKNONIP>
>>                 port 11 ifpriority 0 ifcost 0
>>         vio2 flags=7<LEARNING,DISCOVER,BLOCKNONIP>
>>                 port 3 ifpriority 0 ifcost 0
>>         Addresses (max cache: 16384, timeout: 300):
>>
>> No further output is observed and the there is a panic msg on the vga
>> console
>>
>> I have attached images of the panic and I have tried to follow ddb
>> output debugging as best I can
>>
>> Thanks
>> Tom smyth
>>
>>
>>
>>
>>
>> --
>> Kindest regards,
>> Tom Smyth.
>>
>
>
> --
> Kindest regards,
> Tom Smyth.
>


--
Kindest regards,
Tom Smyth.
Reply | Threaded
Open this post in threaded view
|

Re: 6.5 stable SMP (2 processor) Kernel panic when ifconfig is called and there are 2 bridges are running in two different Rdomains

Tom Smyth
hello

I can confim that bridge with a virtio vio interface seems to be the
only interface affected by this bug ...

I have tried em vlan tap vmx also and these seem to be bug free

I hope this helps

On Thu, 23 May 2019 at 03:36, Tom Smyth <[hidden email]>
wrote:

> Hello all,
>
> the issue was not related to 2 bridges, or 2 rdomains as previously
> thought
>
> it seems to be related to the bridge and the virtio network driver vio
>
> by adding 1 virtio  vio interface into just 1 bridge
> and then running ifconfig bridge causes the kernel panic
>
> demsg is shown below
>
> WARNING: SPL NOT LOWERED ON SYSCALL 54 3 EXIT 0 9
> Stopped at      savectx+0xb1:   movl    $0,%gs:0x508
> ddb{0}> rebooting...
> OpenBSD 6.5 (GENERIC.MP) #3: Sat Apr 13 14:48:43 MDT 2019
>     [hidden email]:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> real mem = 4278042624 (4079MB)
> avail mem = 4138766336 (3947MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xf69e0 (10 entries)
> bios0: vendor SeaBIOS version "
> rel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org" date 04/01/2014
> bios0: QEMU Standard PC (i440FX + PIIX, 1996)
> acpi0 at bios0: rev 0
> acpi0: sleep states S3 S4 S5
> acpi0: tables DSDT FACP APIC HPET SRAT
> acpi0: wakeup devices
> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: Intel(R) Xeon(R) CPU E5-2660 v2 @ 2.20GHz, 486.78 MHz, 06-3e-04
> cpu0:
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SS,HTT,SSE3,PCLMUL,SSSE3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,OSXSAVE,AVX,F16C,RDRAND,HV,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,FSGSBASE,SMEP,ERMS,ARAT,XSAVEOPT,MELTDOWN
> cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB
> 64b/line 16-way L2 cache
> cpu0: ITLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped
> cpu0: DTLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped
> cpu0: smt 0, core 0, package 0
> mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
> cpu0: apic clock running at 999MHz
> cpu1 at mainbus0: apid 1 (application processor)
> cpu1: Intel(R) Xeon(R) CPU E5-2660 v2 @ 2.20GHz, 681.80 MHz, 06-3e-04
> cpu1:
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SS,HTT,SSE3,PCLMUL,SSSE3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,OSXSAVE,AVX,F16C,RDRAND,HV,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,FSGSBASE,SMEP,ERMS,ARAT,XSAVEOPT,MELTDOWN
> cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB
> 64b/line 16-way L2 cache
> cpu1: ITLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped
> cpu1: DTLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped
> cpu1: smt 0, core 1, package 0
> ioapic0 at mainbus0: apid 0 pa 0xfec00000, version 11, 24 pins
> acpihpet0 at acpi0: 100000000 Hz
> acpiprt0 at acpi0: bus 0 (PCI0)
> acpicpu0 at acpi0: C1(@1 halt!)
> acpicpu1 at acpi0: C1(@1 halt!)
> "ACPI0006" at acpi0 not configured
> acpipci0 at acpi0 PCI0: _OSC failed
> acpicmos0 at acpi0
> "PNP0A06" at acpi0 not configured
> "PNP0A06" at acpi0 not configured
> "PNP0A06" at acpi0 not configured
> "QEMU0002" at acpi0 not configured
> "ACPI0010" at acpi0 not configured
> pvbus0 at mainbus0: KVM
> pvclock0 at pvbus0
> pci0 at mainbus0 bus 0
> pchb0 at pci0 dev 0 function 0 "Intel 82441FX" rev 0x02
> pcib0 at pci0 dev 1 function 0 "Intel 82371SB ISA" rev 0x00
> pciide0 at pci0 dev 1 function 1 "Intel 82371SB IDE" rev 0x00: DMA,
> channel 0 wired to compatibility, channel 1 wired to compatibility
> pciide0: channel 0 disabled (no drives)
> atapiscsi0 at pciide0 channel 1 drive 0
> scsibus1 at atapiscsi0: 2 targets
> cd0 at scsibus1 targ 0 lun 0: <QEMU, QEMU DVD-ROM, 2.5+> ATAPI 5/cdrom
> removable
> cd0(pciide0:1:0): using PIO mode 4, DMA mode 2
> uhci0 at pci0 dev 1 function 2 "Intel 82371SB USB" rev 0x01: apic 0 int 11
> piixpm0 at pci0 dev 1 function 3 "Intel 82371AB Power" rev 0x03: apic 0
> int 9
> iic0 at piixpm0
> vga1 at pci0 dev 2 function 0 "Cirrus Logic CL-GD5446" rev 0x00
> wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
> wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
> virtio0 at pci0 dev 5 function 0 "Qumranet Virtio SCSI" rev 0x00
> vioscsi0 at virtio0: qsize 128
> scsibus2 at vioscsi0: 255 targets
> sd0 at scsibus2 targ 0 lun 0: <QEMU, QEMU HARDDISK, 2.5+> SCSI3 0/direct
> fixed
> sd0: 10240MB, 512 bytes/sector, 20971520 sectors, thin
> virtio0: msix shared
> virtio1 at pci0 dev 18 function 0 "Qumranet Virtio Network" rev 0x00
> vio0 at virtio1: address aa:02:1f:b0:88:4f
> virtio1: msix shared
> virtio2 at pci0 dev 19 function 0 "Qumranet Virtio Network" rev 0x00
> vio1 at virtio2: address 46:61:59:0f:0a:5b
> virtio2: msix shared
> virtio3 at pci0 dev 20 function 0 "Qumranet Virtio Network" rev 0x00
> vio2 at virtio3: address 5a:1f:d8:36:03:ba
> virtio3: msix shared
> virtio4 at pci0 dev 21 function 0 "Qumranet Virtio Network" rev 0x00
> vio3 at virtio4: address e2:c4:9e:98:90:1f
> virtio4: msix shared
> ppb0 at pci0 dev 30 function 0 "Red Hat Qemu PCI-PCI" rev 0x00
> pci1 at ppb0 bus 1
> ppb1 at pci0 dev 31 function 0 "Red Hat Qemu PCI-PCI" rev 0x00
> pci2 at ppb1 bus 2
> isa0 at pcib0
> isadma0 at isa0
> fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
> pckbc0 at isa0 port 0x60/5 irq 1 irq 12
> pckbd0 at pckbc0 (kbd slot)
> wskbd0 at pckbd0: console keyboard, using wsdisplay0
> pms0 at pckbc0 (aux slot)
> wsmouse0 at pms0 mux 0
> pcppi0 at isa0 port 0x61
> spkr0 at pcppi0
> usb0 at uhci0: USB revision 1.0
> uhub0 at usb0 configuration 1 interface 0 "Intel UHCI root hub" rev
> 1.00/1.00 addr 1
> vscsi0 at root
> scsibus3 at vscsi0: 256 targets
> softraid0 at root
> scsibus4 at softraid0: 256 targets
> root on sd0a (1daaa231ebc31d47.a) swap on sd0b dump on sd0b
> WARNING: / was not properly unmounted
> fd0 at fdc0 drive 1: density unknown
>
> I hope this helps,
>
>
> Tom Smyth
>
>
>
> I hope this helps
>
> Tom Smyth
>
>
> On Thu, 23 May 2019 at 02:47, Tom Smyth <[hidden email]>
> wrote:
>
>> Further testing
>>
>> show that Rdomains and the bridge may not be the issue,  as starting both
>> bridges from boot in the same rdomain (rdomain0 )
>>
>> and then running ifconfig bridge
>> caused the crash
>> Ill try to isolate the exact config that is causing the issue further
>>
>> On Thu, 23 May 2019 at 02:29, Tom Smyth <[hidden email]>
>> wrote:
>>
>>> Hello
>>> Kernel panic when ifconfig is called and 2 bridges are running in two
>>> different rdomains
>>>
>>> cat /etc/hostname.bridge240
>>> rdomain 240
>>> maxaddr 16384
>>> timeout 300
>>> up
>>> add vlan1097 blocknonip vlan1097 -stp vlan1097
>>> add vlan240 blocknonip vlan240 -stp vlan240
>>>
>>>
>>> cat /etc/hostname.bridge101
>>>
>>>  cat /root/hostname.bridge101
>>> maxaddr 16384
>>> timeout 300
>>> up
>>> add vio2 blocknonip vio2 -stp vio2
>>> add vlan101 blocknonip vlan101 -stp vlan101
>>>
>>>
>>> the crash does not happen when the two bridges are in the same rdomain.
>>>
>>> the crash seems to occur if  i run
>>> ifconfig bridge
>>>
>>>
>>> ifconfig bridge
>>> bridge240: flags=41<UP,RUNNING>
>>>         index 7 llprio 3
>>>         groups: bridge
>>>         priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto
>>> rstp
>>>         designated: id 00:00:00:00:00:00 priority 0
>>>         vlan240 flags=7<LEARNING,DISCOVER,BLOCKNONIP>
>>>                 port 14 ifpriority 0 ifcost 0
>>>         vlan1097 flags=7<LEARNING,DISCOVER,BLOCKNONIP>
>>>                 port 13 ifpriority 0 ifcost 0
>>>         Addresses (max cache: 16384, timeout: 300):
>>>                 7a:cb:d2:c3:28:70 vlan1097 1 flags=0<>
>>> bridge101: flags=41<UP,RUNNING>
>>>         index 16 llprio 3
>>>         groups: bridge
>>>         priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto
>>> rstp
>>>         designated: id 00:00:00:00:00:00 priority 0
>>>         vlan101 flags=7<LEARNING,DISCOVER,BLOCKNONIP>
>>>                 port 11 ifpriority 0 ifcost 0
>>>         vio2 flags=7<LEARNING,DISCOVER,BLOCKNONIP>
>>>                 port 3 ifpriority 0 ifcost 0
>>>         Addresses (max cache: 16384, timeout: 300):
>>>
>>> No further output is observed and the there is a panic msg on the vga
>>> console
>>>
>>> I have attached images of the panic and I have tried to follow ddb
>>> output debugging as best I can
>>>
>>> Thanks
>>> Tom smyth
>>>
>>>
>>>
>>>
>>>
>>> --
>>> Kindest regards,
>>> Tom Smyth.
>>>
>>
>>
>> --
>> Kindest regards,
>> Tom Smyth.
>>
>
>
> --
> Kindest regards,
> Tom Smyth.
>


--
Kindest regards,
Tom Smyth.
Reply | Threaded
Open this post in threaded view
|

Re: 6.5 stable SMP (2 processor) Kernel panic when ifconfig is called and there are 2 bridges are running in two different Rdomains

Martin Pieuchot
In reply to this post by Tom Smyth
On 23/05/19(Thu) 02:29, Tom Smyth wrote:
> Hello
> Kernel panic when ifconfig is called and 2 bridges are running in two
> different rdomains

Your trace shows that a context switch occurs while a thread is still
holding a mutex.  It isn't clear which thread is that.

The traces shows that a userland process gets preempted via Xsyscall/ast
/preempt.  Which raises the question: is the assertwaitok() happening
too late?

If you can easily reproduce the problem, please enable WITNESS in your
kernel and try again.

Reply | Threaded
Open this post in threaded view
|

Re: 6.5 stable SMP (2 processor) Kernel panic when ifconfig is called and there are 2 bridges are running in two different Rdomains

Tom Smyth
Ill have a go at enabling witness, in the kernel,  and re -running...


On Thu, 23 May 2019 at 12:41, Martin Pieuchot <[hidden email]> wrote:

> On 23/05/19(Thu) 02:29, Tom Smyth wrote:
> > Hello
> > Kernel panic when ifconfig is called and 2 bridges are running in two
> > different rdomains
>
> Your trace shows that a context switch occurs while a thread is still
> holding a mutex.  It isn't clear which thread is that.
>
> The traces shows that a userland process gets preempted via Xsyscall/ast
> /preempt.  Which raises the question: is the assertwaitok() happening
> too late?
>
> If you can easily reproduce the problem, please enable WITNESS in your
> kernel and try again.
>


--
Kindest regards,
Tom Smyth.