Bug #2420

panic: Bad link elm prev->next != elm on shutdown of Asus M5A87

Added by davshao almost 2 years ago. Updated about 1 month ago.

Status:ClosedStart date:09/12/2012
Priority:NormalDue date:
Assignee:davshao% Done:

0%

Category:Other
Target version:3.8.0

Description

Asus M5A87 motherboard AMD-based, chipset AMD 870 / SB850, ufs filesystem, x86_64, updated through commit 3abced87f950dd62d00360daeb83276e5d5a1d47 netisr: rename cpu_portfn() to netisr_portfn().
pkgsrc current through Wednesday morning.

On
shutdown -p now
from within kde4,

Stopping devd.
.
Sep 12 13:35:48 syslogd: exiting on signal 15
panic: Bad link elm 0xffffffe1fac47d00 prev->next != elm
cpuid = 1
Trace beginning at frame 0xffffffe1fb732708
panic() at panic+0x1fb 0xffffffff804ed358
panic() at panic+0x1fb 0xffffffff804ed358
unp_detach() at unp_detach+05f 0xffffffff805410f2
unp_free() at unp_free+0x4d 0xffffffff8054140a
uipc_send() at uipc_send+0x579 0xffffffff80541d61
netmsg_sync_putport() at netmsg_sync_putport+0x40 0xffffffff80598055
lwkt_domsg() at lwkt_domsg+0x5c 0xffffffff80537145
sosend() at sosend+0x4c9 0xffffffff80539b6b
kern_sendmsg() at kern_sendmsg+0x179 0xffffffff8053e235
sys_sendto() at sys_sendto+0xa2 0xffffffff8053e86b
syscall2() at syscall2+0x370 0xffffffff8089bcb1
Xfast_syscall() at Xfast_syscall+0xcb 0xffffffff8088561b
Debugger("panic")

History

#1 Updated by davshao almost 2 years ago

The problem has not manifested itself since, in particular no incidents after commit fb4ca0183366cda0c6df8282b88ada2fab64a3b1 "Implement segment pmap optimizations for x86-64 (3)", pkgsrc current has been considerably updated since in preparation for a new freeze and release, and the problem only manifested itself on that one Asus M5A87 machine. It would be reasonable to close this bug.

#2 Updated by tuxillo about 1 month ago

  • Description updated (diff)
  • Category set to Other
  • Status changed from New to Closed
  • Assignee set to davshao
  • Target version set to 3.8.0

Caller confirms closure.

Also available in: Atom PDF