Project

General

Profile

Actions

Bug #2354

closed

panic: lwkt_dropmsg() is illegal on port 0xffffffff81d61578 msg 0xffffffe159ad1d88

Added by pavalos about 12 years ago. Updated about 12 years ago.

Status:
Closed
Priority:
High
Assignee:
Category:
-
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:

Description

While loading up with some network traffic today, I got this panic:

lwkt_dropmsg() is illegal on port 0xffffffff81d61578 msg 0xffffffe159ad1d88

(kgdb) bt
#0 _get_mycpu () at ./machine/thread.h:69
#1 md_dumpsys (di=<optimized out>) at /usr/src/sys/platform/pc64/x86_64/dump_machdep.c:265
#2 0xffffffff802bcc02 in dumpsys () at /usr/src/sys/kern/kern_shutdown.c:937
#3 0xffffffff802bd266 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:387
#4 0xffffffff802bd51d in panic (fmt=0xffffffff804c62e8 "lwkt_dropmsg() is illegal on port %p msg %p") at /usr/src/sys/kern/kern_shutdown.c:843
#5 0xffffffff802ccc7b in lwkt_panic_dropmsg (port=<optimized out>, msg=<unavailable>) at /usr/src/sys/kern/lwkt_msgport.c:1125
#6 0xffffffff80377984 in lwkt_dropmsg (msg=<optimized out>) at /usr/src/sys/sys/msgport2.h:112
#7 tcp_destroy_timermsg (tp=<optimized out>) at /usr/src/sys/netinet/tcp_timer.c:723
#8 0xffffffff80374e1e in tcp_close (tp=0xffffffe159ad1a10) at /usr/src/sys/netinet/tcp_subr.c:992
#9 0xffffffff8036e06c in tcp_input (mp=<optimized out>, offp=<optimized out>, proto=<optimized out>) at /usr/src/sys/netinet/tcp_input.c:1611
#10 0xffffffff80365a56 in transport_processing_oncpu (m=0x0, hlen=20, ip=0xffffffe159faf810) at /usr/src/sys/netinet/ip_input.c:394
#11 0xffffffff80367b93 in ip_input (m=0xffffffe129129a00) at /usr/src/sys/netinet/ip_input.c:959
#12 0xffffffff80367bbd in ip_input_handler (msg=<optimized out>) at /usr/src/sys/netinet/ip_input.c:415
#13 0xffffffff80354505 in netisr_handle (num=2, m=0xffffffe129129a00) at /usr/src/sys/net/netisr.c:416
#14 0xffffffff80350dd2 in ether_demux_oncpu (ifp=<optimized out>, m=0xffffffe129129a00) at /usr/src/sys/net/if_ethersubr.c:1162
#15 0xffffffff80350f3a in ether_input_oncpu (ifp=0xffffffe0fd4e5000, m=0xffffffe129129a00) at /usr/src/sys/net/if_ethersubr.c:1248
#16 0xffffffff80351bd3 in ether_input_handler (nmsg=<optimized out>) at /usr/src/sys/net/if_ethersubr.c:1366
#17 0xffffffff80353b6b in netmsg_service_loop (arg=<optimized out>) at /usr/src/sys/net/netisr.c:307
#18 0xffffffff802c83f0 in lwkt_deschedule_self (td=<unavailable>) at /usr/src/sys/kern/lwkt_thread.c:362

kernel and vmcore are on ylem under /var/crash/*.2, and I'll be
uploading them to leaf as well.

--Peter


Files

noname (199 Bytes) noname pavalos, 04/27/2012 02:30 PM
Actions #1

Updated by sepherosa about 12 years ago

On Sat, Apr 28, 2012 at 5:30 AM, Peter Avalos via Redmine
<> wrote:

Issue #2354 has been reported by Peter Avalos.

----------------------------------------
Bug #2354: panic: lwkt_dropmsg() is illegal on port 0xffffffff81d61578 msg 0xffffffe159ad1d88
http://bugs.dragonflybsd.org/issues/2354

Author: Peter Avalos
Status: New
Priority: Normal
Assignee:
Category:
Target version:

While loading up with some network traffic today, I got this panic:

lwkt_dropmsg() is illegal on port 0xffffffff81d61578 msg 0xffffffe159ad1d88

dropmsg is not implemented for spinport. It should have been fixed in
the master by:
89d66f8fc619a10a688ab1f4d864df49093586a0

3_0 branch also has the fix.

Best Regards,
sephe

--
Tomorrow Will Never Die

Actions #2

Updated by vsrinivas about 12 years ago

Has this issue been dealt with?

Thanks,

Actions #3

Updated by pavalos about 12 years ago

  • Status changed from New to Closed
  • Assignee set to sepherosa
  • Priority changed from Normal to High

Fixed in 89d66f8fc619a10a688ab1f4d864df49093586a0.

Actions

Also available in: Atom PDF