https://bugs.dragonflybsd.org/
https://bugs.dragonflybsd.org/favicon.ico?1629395208
2012-02-13T01:38:24Z
DragonFlyBSD bugtracker
DragonFlyBSD - Bug #2304: DFBSD v3.1.0.32.g4d37d - assertion "p" failed in in_pcbbind
https://bugs.dragonflybsd.org/issues/2304?journal_id=10628
2012-02-13T01:38:24Z
sepherosa
<ul></ul><p>On Sun, Feb 12, 2012 at 1:59 AM, Antonio M. Huete Jimenez via Redmine<br /><<a class="email" href="mailto:bugtracker-admin@leaf.dragonflybsd.org">bugtracker-admin@leaf.dragonflybsd.org</a>> wrote:</p>
<blockquote>
<p>Issue <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: DFBSD v3.1.0.32.g4d37d - assertion "p" failed in in_pcbbind (Closed)" href="https://bugs.dragonflybsd.org/issues/2304">#2304</a> has been reported by Antonio M. Huete Jimenez.</p>
<p>----------------------------------------<br />Bug <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: DFBSD v3.1.0.32.g4d37d - assertion "p" failed in in_pcbbind (Closed)" href="https://bugs.dragonflybsd.org/issues/2304">#2304</a>: DFBSD v3.1.0.32.g4d37d - assertion "p" failed in in_pcbbind<br /><a class="external" href="http://bugs.dragonflybsd.org/issues/2304">http://bugs.dragonflybsd.org/issues/2304</a></p>
<p>Author: Antonio M. Huete Jimenez<br />Status: New<br />Priority: Normal<br />Assignee:<br />Category:<br />Target version:</p>
<p>Hi,</p>
<p>Got the following panic on i386 after few days of uptime:</p>
<p>panic: assertion "p" failed in in_pcbbind at /home/source/dfbsd/sys/netinet/in_pcb.c:300<br />cpuid = 0<br />Trace beginning at frame 0xd6234c8c<br />panic(ffffffff,0,c0706c58,d6234cc0,c0d69480) at panic+0x19e 0xc038d6a3<br />panic(c0706c58,c06e7e66,c06b2835,c073d438,12c) at panic+0x19e 0xc038d6a3<br />in_pcbbind(c5c11ce0,0,d6f40058,e0d,c0d46688) at in_pcbbind+0x60 0xc047e588<br />udp_send(da63ea18,0,c0d69480,c08220a0,d6234da0) at udp_send+0xf8 0xc0495b48<br />netmsg_service_loop(0,0,0,0,0) at netmsg_service_loop+0x73 0xc043ba2b<br />lwkt_exit() at lwkt_exit 0xc0399c5f<br />boot() called on cpu#0<br />Uptime: 18d20h10m59s<br />Physical memory: 2000 MB<br />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<br />85 69 53 37 21 5</p>
<hr />
<p><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: lib/libcr/sys/ cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/1">#1</a> md_dumpsys (di=0xc0ce5fc0) at /home/source/dfbsd/sys/platform/pc32/i386/dump_machdep.c:264<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: K&R -> ANSI cleanup status (Closed)" href="https://bugs.dragonflybsd.org/issues/2">#2</a> 0xc038ce58 in dumpsys () at /home/source/dfbsd/sys/kern/kern_shutdown.c:925<br /><a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: freebsds pipe-reverse test fails on dfly (Closed)" href="https://bugs.dragonflybsd.org/issues/3">#3</a> 0xc038d46e in boot (howto=<optimized out>) at /home/source/dfbsd/sys/kern/kern_shutdown.c:387<br /><a class="issue tracker-1 status-5 priority-5 priority-high3 closed" title="Bug: Rework of nrelease (Closed)" href="https://bugs.dragonflybsd.org/issues/4">#4</a> 0xc038d6d7 in panic (fmt=0xc0706c58 "assertion \"%s\" failed in %s at %s:%u") at /home/source/dfbsd/sys/kern/kern_shutdown.c:831<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: sys/dev cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/5">#5</a> 0xc047e588 in in_pcbbind (inp=0xc5c11ce0, nam=0x0, td=0xd6f40058) at /home/source/dfbsd/sys/netinet/in_pcb.c:300<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: sys/emulation cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/6">#6</a> 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<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: /sys/boot cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/7">#7</a> udp_send (msg=0xda63ea18) at /home/source/dfbsd/sys/netinet/udp_usrreq.c:1261<br /><a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: make upgrade broken (Closed)" href="https://bugs.dragonflybsd.org/issues/8">#8</a> 0xc043ba2b in netmsg_service_loop (arg=0x0) at /home/source/dfbsd/sys/net/netisr.c:307<br /><a class="issue tracker-1 status-5 priority-5 priority-high3 closed" title="Bug: panic with HEAD (Closed)" href="https://bugs.dragonflybsd.org/issues/9">#9</a> 0xc0399c5f in lwkt_deschedule_self (td=Cannot access memory at address 0x8<br />) at /home/source/dfbsd/sys/kern/lwkt_thread.c:362</p>
<p>I have the core dump available on demand.</p>
</blockquote>
<p>I believe this has been fixed on the latest master:<br />23ecc5880dd169ab9c408114e82a49d099f45a8d</p>
<p>Best Regards,<br />sephe</p>
<p>-- <br />Tomorrow Will Never Die</p>
DragonFlyBSD - Bug #2304: DFBSD v3.1.0.32.g4d37d - assertion "p" failed in in_pcbbind
https://bugs.dragonflybsd.org/issues/2304?journal_id=10663
2012-02-24T19:57:41Z
alexh
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li></ul>
DragonFlyBSD - Bug #2304: DFBSD v3.1.0.32.g4d37d - assertion "p" failed in in_pcbbind
https://bugs.dragonflybsd.org/issues/2304?journal_id=14326
2022-05-31T22:56:18Z
tuxillo
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/14326/diff?detail_id=3961">diff</a>)</li><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Closed</i></li><li><strong>Assignee</strong> set to <i>tuxillo</i></li></ul><p>No feedback at the time, also we don't support i386 anymore.</p>