Bug #2304
closedDFBSD v3.1.0.32.g4d37d - assertion "p" failed in in_pcbbind
Description
Hi,
Got the following panic on i386 after few days of uptime:
panic: assertion "p" failed in in_pcbbind at /home/source/dfbsd/sys/netinet/in_pcb.c:300
cpuid = 0
Trace beginning at frame 0xd6234c8c
panic(ffffffff,0,c0706c58,d6234cc0,c0d69480) at panic+0x19e 0xc038d6a3
panic(c0706c58,c06e7e66,c06b2835,c073d438,12c) at panic+0x19e 0xc038d6a3
in_pcbbind(c5c11ce0,0,d6f40058,e0d,c0d46688) at in_pcbbind+0x60 0xc047e588
udp_send(da63ea18,0,c0d69480,c08220a0,d6234da0) at udp_send+0xf8 0xc0495b48
netmsg_service_loop(0,0,0,0,0) at netmsg_service_loop+0x73 0xc043ba2b
lwkt_exit() at lwkt_exit 0xc0399c5f
boot() called on cpu#0
Uptime: 18d20h10m59s
Physical memory: 2000 MB
Dumping 500 MB: 485 469 453 437 421 405 389 373 357 341 325 309 293 277 261 245 229 213 197 181 165 149 133 117 101
85 69 53 37 21 5
#1 md_dumpsys (di=0xc0ce5fc0) at /home/source/dfbsd/sys/platform/pc32/i386/dump_machdep.c:264
#2 0xc038ce58 in dumpsys () at /home/source/dfbsd/sys/kern/kern_shutdown.c:925
#3 0xc038d46e in boot (howto=<optimized out>) at /home/source/dfbsd/sys/kern/kern_shutdown.c:387
#4 0xc038d6d7 in panic (fmt=0xc0706c58 "assertion \"%s\" failed in %s at %s:%u") at /home/source/dfbsd/sys/kern/kern_shutdown.c:831
#5 0xc047e588 in in_pcbbind (inp=0xc5c11ce0, nam=0x0, td=0xd6f40058) at /home/source/dfbsd/sys/netinet/in_pcb.c:300
#6 0xc0495b48 in udp_output (flags=<optimized out>, td=<optimized out>, dstaddr=<optimized out>, m=<optimized out>, inp=<optimized out>) at /home/source/dfbsd/sys/netinet/udp_usrreq.c:804
#7 udp_send (msg=0xda63ea18) at /home/source/dfbsd/sys/netinet/udp_usrreq.c:1261
#8 0xc043ba2b in netmsg_service_loop (arg=0x0) at /home/source/dfbsd/sys/net/netisr.c:307
#9 0xc0399c5f in lwkt_deschedule_self (td=Cannot access memory at address 0x8
) at /home/source/dfbsd/sys/kern/lwkt_thread.c:362
I have the core dump available on demand.
Cheers,
Antonio Huete
Updated by sepherosa almost 13 years ago
On Sun, Feb 12, 2012 at 1:59 AM, Antonio M. Huete Jimenez via Redmine
<bugtracker-admin@leaf.dragonflybsd.org> wrote:
Issue #2304 has been reported by Antonio M. Huete Jimenez.
----------------------------------------
Bug #2304: DFBSD v3.1.0.32.g4d37d - assertion "p" failed in in_pcbbind
http://bugs.dragonflybsd.org/issues/2304Author: Antonio M. Huete Jimenez
Status: New
Priority: Normal
Assignee:
Category:
Target version:Hi,
Got the following panic on i386 after few days of uptime:
panic: assertion "p" failed in in_pcbbind at /home/source/dfbsd/sys/netinet/in_pcb.c:300
cpuid = 0
Trace beginning at frame 0xd6234c8c
panic(ffffffff,0,c0706c58,d6234cc0,c0d69480) at panic+0x19e 0xc038d6a3
panic(c0706c58,c06e7e66,c06b2835,c073d438,12c) at panic+0x19e 0xc038d6a3
in_pcbbind(c5c11ce0,0,d6f40058,e0d,c0d46688) at in_pcbbind+0x60 0xc047e588
udp_send(da63ea18,0,c0d69480,c08220a0,d6234da0) at udp_send+0xf8 0xc0495b48
netmsg_service_loop(0,0,0,0,0) at netmsg_service_loop+0x73 0xc043ba2b
lwkt_exit() at lwkt_exit 0xc0399c5f
boot() called on cpu#0
Uptime: 18d20h10m59s
Physical memory: 2000 MB
Dumping 500 MB: 485 469 453 437 421 405 389 373 357 341 325 309 293 277 261 245 229 213 197 181 165 149 133 117 101
85 69 53 37 21 5
#1 md_dumpsys (di=0xc0ce5fc0) at /home/source/dfbsd/sys/platform/pc32/i386/dump_machdep.c:264
#2 0xc038ce58 in dumpsys () at /home/source/dfbsd/sys/kern/kern_shutdown.c:925
#3 0xc038d46e in boot (howto=<optimized out>) at /home/source/dfbsd/sys/kern/kern_shutdown.c:387
#4 0xc038d6d7 in panic (fmt=0xc0706c58 "assertion \"%s\" failed in %s at %s:%u") at /home/source/dfbsd/sys/kern/kern_shutdown.c:831
#5 0xc047e588 in in_pcbbind (inp=0xc5c11ce0, nam=0x0, td=0xd6f40058) at /home/source/dfbsd/sys/netinet/in_pcb.c:300
#6 0xc0495b48 in udp_output (flags=<optimized out>, td=<optimized out>, dstaddr=<optimized out>, m=<optimized out>, inp=<optimized out>) at /home/source/dfbsd/sys/netinet/udp_usrreq.c:804
#7 udp_send (msg=0xda63ea18) at /home/source/dfbsd/sys/netinet/udp_usrreq.c:1261
#8 0xc043ba2b in netmsg_service_loop (arg=0x0) at /home/source/dfbsd/sys/net/netisr.c:307
#9 0xc0399c5f in lwkt_deschedule_self (td=Cannot access memory at address 0x8
) at /home/source/dfbsd/sys/kern/lwkt_thread.c:362I have the core dump available on demand.
I believe this has been fixed on the latest master:
23ecc5880dd169ab9c408114e82a49d099f45a8d
Best Regards,
sephe
--
Tomorrow Will Never Die
Updated by tuxillo over 2 years ago
- Description updated (diff)
- Status changed from Feedback to Closed
- Assignee set to tuxillo
No feedback at the time, also we don't support i386 anymore.