Date: Tue, 6 Jun 2017 03:46:19 -0700 From: Mark Millard <markmi@dsl-only.net> To: Justin Hibbits <jhibbits@FreeBSD.org>, Nathan Whitehorn <nwhitehorn@freebsd.org>, FreeBSD PowerPC ML <freebsd-ppc@freebsd.org>, freebsd-hackers@freebsd.org Subject: A different 32-bit powerpc head -r317820 panic on old PowerMac G5: dual backtraces from "timeout stopping cpus" (dump failed though): any comments? Message-ID: <D69CB244-69E2-4319-BD63-07BC7F763279@dsl-only.net>
next in thread | raw e-mail | index | archive | help
I'm not sure what to make of this. May be someone has
some idea.
One of the bt's is for "irq53: smudoorbell0" (tid 100055) the other is =
for usb.
spinlock 0xefbbf00 (sched lock 1) held by 0x593d6c0 (tid 100055) too =
long
spinlock 0xxf2e1f8 (sleepq chain) help by 0x17606c0 (tid 100049) too =
long
timeout stopping cpus
usb. . .
(I omit any "at kdb_backtrace" lines)
0xe56636d0: at vpanic+0x210
0xe5663740: at panic+0x54
0xe5663790: at _mtx_lock_spin_failed_+0x54
0xe56637b0: at _mtx_lock_spin_cookie+0x19c
0xe5663810: at sched_add+0x140
0xe5663850: at sched_wakeup+0xa4
0xe5663870: at setrunnable+0x9c
0xe5663890: at sleepq_resume_thread+0x17c
0xe56638c0: at sleepq_signal+0xa4
0xe56638f0: at cv_signal+0x94
0xe5663910: at usbd_do_request_callback+0x80
0xe5663930: at usb_request_callback_0x28
0xe5663950: at usbd_callback_wrapper+0xa98
0xe5663990: at usb_command_wrapper+0x14c
0xe56639d0: at usb_callback_proc+0x190
0xe5663a00: at usb_process+0x1d0
0xe5663a50: at fork_exit+0xf4
0xe5663a80: at fork_trampoline+0xc
irq53: smudoorbell0. . .
0xe56e4460: at vpanic+0x22c
0xe56e44d0: at panic+0x54
0xe56e4520: at _mtx_lock_spin_failed+0x54
0xe56e4540: at thread_lock_flags_0x1bc
0xe56e45b0: at sleepq_timeout+0x44
0xe56e45f0: at softclock_call_cc+0x1bc
0xe56e4660: at callout_process+0x27c
0xe56e46c0: at handleevents+0x2ac
0xe56e4710: at timercb+0x4c4
0xe56e4790: at decr_intr+0xf0
0xe56e47b0: at powerpc_intrerrupt+0xf4
0xe56e47e0: at kernel DECR trap
by _mtx_lock_spin_cookie+0x194
srr1=3D 0x9032
r1=3D 0xe56e48a0
cr=3D 0x20000002
xer=3D 0
ctr=3D 0
0xe56e48a0: at _mtx_lock+_spin_cookie+0x190
0xe56e4900: at sleepq_lock+0xac
0xe56e4930: at wakeup+0x24
0xe56e4950: at smu_doorbell_intr+0x128
0xe56e4980: at intr_event_execute_handler+0x220
0xe56e49f0: at ithread_loop+0xf0
0xe56e4a50: at fork_exit+0xf4
0xe56e4a80: at fork_trampoline+0xc
For reference acttrace also reported
(that looks odd after the first 2
stack lines):
powerpd pid 960 tid 100097 td 0x5ba1999 (CPU 2)
0xd2418510: at uma_zalloc_arg+0x178
0xd2418580: at mmu_unmapdev+desc+0x8
0x00fcf9dc: at primes+0x68
0x00d026b0: at moe64_page_exists_quick+0x1d8
0x00ce0ff8: at mmu_unmapdev_desc+0x8
(CPU3 had an empty backtrace for pid 11's
tid 100006.)
I had another example of sorts but it did not
get far before hanging up:
spinlock 0xefbbf00 (sched lock 1) held by 0x146d360 (tid 100004) too =
long
spinlock 0xefbbf00 (sched lock 1) held by 0x146d360 (tid 100004) too =
long
(Note: Two different colored lines above but the
same otherwise.)
timeout stopping cpus
Note: The partial backtrace was:
("cpuid =3D 2", all in the first color above)
0xdf6bb5c0: at vpanic+0x210
0xdf6bb630: at panic++0x54
0xdf6bb680: at _mtx_lock_spin_failed+0x54
0xdf6bb6a0: at _mtx_lock_spin_cookie+0x190
0xdf6bb700: at sched_add+0x140
0xdf6bb740: at sched_wakeup+0xa4
0xdf6bb760: at=20
(and that is as far as it got for the backtrace(s))
=3D=3D=3D
Mark Millard
markmi at dsl-only.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D69CB244-69E2-4319-BD63-07BC7F763279>