Re: kern/50186: sparc memfault panic after 7.99.21 ARP changes

[Ryota Ozaki <ozaki-r%netbsd.org@localhost>]

The following reply was made to PR kern/50186; it has been noted by GNATS.

From: Ryota Ozaki <ozaki-r%netbsd.org@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: kern-bug-people%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost, 
	jdbaker%mylinuxisp.com@localhost
Subject: Re: kern/50186: sparc memfault panic after 7.99.21 ARP changes
Date: Thu, 3 Sep 2015 19:35:39 +0900

 Hi,
 
 Thank you for your investigation.
 
 On Wed, Sep 2, 2015 at 8:50 PM, John D. Baker <jdbaker%mylinuxisp.com@localhost> wrote:
 > The following reply was made to PR kern/50186; it has been noted by GNATS.
 >
 > From: "John D. Baker" <jdbaker%mylinuxisp.com@localhost>
 > To: gnats-bugs%NetBSD.org@localhost
 > Cc:
 > Subject: re: kern/50186: sparc memfault panic after 7.99.21 ARP changes
 > Date: Wed, 2 Sep 2015 06:44:47 -0500 (CDT)
 >
 >  I've repeated my observations on a few other machines:
 >
 >  SPARCstation 5, 85MHz, 256MB
 >  SPARCstation 10, 40MHz (SM41 SuperSPARC), 128MB
 >
 >  and most recently:
 >
 >  NetBSD dpe2950 7.99.21 NetBSD 7.99.21 (GENERIC) #63: Mon Aug 31 19:52:42 CDT 2015  sysop%yggdrasil.technoskunk.fur@localhost:/r0/build/current/obj/amd64/sys/arch/amd64/compile/GENERIC amd64
 >
 >  The panic:
 >
 >  panic: kernel diagnostic assertion "rt != NULL" failed: file "/r0/nbsd/current/src/sys/netinet/if_arp.c", line 1431
 >  fatal breakpoint trap in supervisor mode
 >  trap type 1 code 0 rip ffffffff8028a395 cs 8 rflags 246 cr2 ffff8000ddb92800 ilevel 2 rsp fffffe8115ef0e80
 >  curlwp 0xfffffe8115f1ca40 pid 0.50 lowest kstack 0xfffffe8115eed2c0
 >  Stopped in pid 0.50 (system) at netbsd:breakpoint+0x5:  leave
 >  db{6}> bt
 >  breakpoint() at netbsd:breakpoint+0x5
 >  vpanic() at netbsd:vpanic+0x13c
 >  kern_assert() at netbsd:kern_assert+0x4f
 >  arptimer() at netbsd:arptimer+0x1d0
 >  callout_softclock() at netbsd:callout_softclock+0x1d0
 >  softint_dispatch() at netbsd:softint_dispatch+0xd3
 >  DDB lost frame for netbsd:Xsoftintr+0x4f, trying 0xfffffe8115ef0ff0
 >  Xsoftintr() at netbsd:Xsoftintr+0x4f
 >  --- interrupt ---
 >  0:
 >  db{6}>
 
 How do you produce the panic? I don't reproduce on my amd64 machines yet.
 
 >
 >
 >  Excerpt from 'dmesg':
 >
 >  NetBSD 7.99.21 (GENERIC) #63: Mon Aug 31 19:52:42 CDT 2015
 >         sysop%yggdrasil.technoskunk.fur@localhost:/r0/build/current/obj/amd64/sys/arch/amd64/compile/GENERIC
 >  total memory = 12287 MB
 >  avail memory = 11911 MB
 >  [...]
 >  ACPI: RSDP 0x00000000000F2620 000024 (v02 DELL  )
 >  ACPI: XSDT 0x00000000000F26A0 00004C (v01 DELL   PE_SC3   00000001 DELL 00000001)
 >  ACPI: FACP 0x00000000000F27A8 0000F4 (v03 DELL   PE_SC3   00000001 DELL 00000001)
 >  ACPI: DSDT 0x00000000CFFA8000 003C53 (v01 DELL   PE_SC3   00000001 MSFT 0100000E)
 >  ACPI: FACS 0x00000000CFFB7C00 000040
 >  ACPI: FACS 0x00000000CFFB7C00 000040
 >  ACPI: APIC 0x00000000000F289C 0000C8 (v01 DELL   PE_SC3   00000001 DELL 00000001)
 >  ACPI: SPCR 0x00000000000F297D 000050 (v01 DELL   PE_SC3   00000001 DELL 00000001)
 >  ACPI: HPET 0x00000000000F29CD 000038 (v01 DELL   PE_SC3   00000001 DELL 00000001)
 >  ACPI: MCFG 0x00000000000F2A05 00003C (v01 DELL   PE_SC3   00000001 DELL 00000001)
 >  ACPI: All ACPI Tables successfully acquired
 >  ioapic0 at mainbus0 apid 8
 >  ioapic1 at mainbus0 apid 9
 >  cpu0 at mainbus0 apid 0
 >  cpu0: Intel(R) Xeon(R) CPU           E5310  @ 1.60GHz, id 0x6f7
 >  cpu1 at mainbus0 apid 4
 >  cpu1: Intel(R) Xeon(R) CPU           E5310  @ 1.60GHz, id 0x6f7
 >  cpu2 at mainbus0 apid 1
 >  cpu2: Intel(R) Xeon(R) CPU           E5310  @ 1.60GHz, id 0x6f7
 >  cpu3 at mainbus0 apid 5
 >  cpu3: Intel(R) Xeon(R) CPU           E5310  @ 1.60GHz, id 0x6f7
 >  cpu4 at mainbus0 apid 2
 >  cpu4: Intel(R) Xeon(R) CPU           E5310  @ 1.60GHz, id 0x6f7
 >  cpu5 at mainbus0 apid 6
 >  cpu5: Intel(R) Xeon(R) CPU           E5310  @ 1.60GHz, id 0x6f7
 >  cpu6 at mainbus0 apid 3
 >  cpu6: Intel(R) Xeon(R) CPU           E5310  @ 1.60GHz, id 0x6f7
 >  cpu7 at mainbus0 apid 7
 >  cpu7: Intel(R) Xeon(R) CPU           E5310  @ 1.60GHz, id 0x6f7
 >
 >
 >  So, this is not just a SPARC issue.
 >
 >  I see that KASSERTs in "if_arp.c" were recently disabled.
 
 Does the fix suppress the panic on SPARC machines?
 
 Thanks,
   ozaki-r