On Thu, Jul 02, 2015 at 10:52:00AM -0400, Kurt Lidl wrote:
> >Kurt, can you re-enable the ipv6 line in rc.conf(5), and add '-tso6' to
> >your rc.conf(5) lines?
> >
> >  ifconfig_bge0="DHCP"
> >  ifconfig_bge0_ipv6="inet6 accept_rtadv -tso6"
> >
> 
> I tried this, and it panic'd in the same manner.  (Note - I've upgraded
> this machine to the second 10.2-PRELEASE build.)
> 

Okay, thank you for testing.  The last commits that I see specifically
referencing this bge(4) model were a long time ago, but TSO was
mentioned.  It was worth a shot.

> [...]
> 
> I've also seen (now that it's been running a bit longer), a couple of
> other occurrences of the "spin lock held too long" panic. So while
> having the IPv6 configuration in /etc/rc.conf causes this crash to
> occur most of the time on boot, the same crash occurs at other times
> too, which don't appear to IPv6 related.
> 

Can you update the PR with this information, please?

> 1) when making the requested change, I editted my /etc/rc.conf file,
> and then issued "reboot".  The machine panic'd during the reboot
> processing:
> 
> root@spork:~ # reboot
> Jul  2 09:48:53 spork reboot: rebooted by root
> Jul  2 09:48:53 spork syslogd: exiting on signal 15
> Waiting (max 60 seconds) for system process `vnlru' to stop...done
> Waiting (max 60 seconds) for system process `bufdaemon' to stop...done
> Waiting (max 60 seconds) for system process `syncer' to stop...
> Syncing disks, vnodes remaining...0 0 0 0 done
> All buffers synced.
> Uptime: 14h34m16s
> GEOM_MIRROR: Device gswap: provider mirror/gswap destroyed.
> GEOM_MIRROR: Device gswap destroyed.
> pid 1 (init), uid 0: exited on signal 4
> spin lock 0xc0cba338 (smp rendezvous) held by 0xfffff8000bbbe920 (tid
> 100367) too long
> timeout stopping cpus
> panic: spin lock held too long
> cpuid = 1
> KDB: stack backtrace:
> #0 0xc05757c0 at panic+0x20
> #1 0xc0559250 at _mtx_lock_spin_failed+0x50
> #2 0xc0559318 at _mtx_lock_spin_cookie+0xb8
> #3 0xc08d801c at tick_get_timecount_mp+0xdc
> #4 0xc05840c8 at binuptime+0x48
> #5 0xc08a400c at timercb+0x6c
> #6 0xc08d8380 at tick_intr+0x220
> Uptime: 14h34m16s
> Automatic reboot in 15 seconds - press a key on the console to abort
> Rebooting...
> timeout stopping cpus
> timeout shutting down CPUs.
> 
> SC Alert: Host System has Reset
> 
> Note: the "SC Alert:" message comes the Sparc's ALOM management system,
> so that's from the hardware directly, not from FreeBSD's kernel.
> 

Hmm.  Any chance this could be hardware (failure) related?

> It didn't crashdump, so I don't have any other backtrace other than
> what I just copied here.
> 
> 2) After I rebooted with the "-tso" flag in place and it crashed,
> I booted again, single user, so I could edit the /etc/rc.conf again
> and manually did a savecore:
> 

Okay, thank you for checking, in any case.

Glen

Attachment: pgp6s3pfx16ZI.pgp
Description: PGP signature

Reply via email to