https://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082006-11-08T06:13:01ZDragonFlyBSD bugtrackerDragonFlyBSD - Bug #361: uplcom(4) update from FreeBSDhttps://bugs.dragonflybsd.org/issues/361?journal_id=15492006-11-08T06:13:01ZJohannes.Hofmann
<ul></ul><p>Ok, I finally got a core dump. The dump device was too small after<br />a memory upgrade...</p>
<p>Here is what I got:</p>
<p>(kgdb) bt<br />#0 dumpsys () at thread.h:83<br /><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> 0xc028d3c3 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:355<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> 0xc028da56 in panic (<br /> fmt=0xc06cb0e8 "uhci_abort_xfer: not in process context")<br /> at /usr/src/sys/kern/kern_shutdown.c:757<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> 0xc06b802b in uhci_abort_xfer (xfer=0xc330c920, status=USBD_CANCELLED)<br /> at /usr/src/sys/bus/usb/usb/../../../bus/usb/uhci.c:1934<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> 0xc06b7f80 in uhci_device_bulk_abort (xfer=0x0)<br /> at /usr/src/sys/bus/usb/usb/../../../bus/usb/uhci.c:1900<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> 0xc06b4d6e in usbd_ar_pipe (pipe=0xc328bfe0)<br /> at /usr/src/sys/bus/usb/usb/../../../bus/usb/usbdi.c:746<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> 0xc06b4a6d in usbd_abort_pipe (pipe=0x0)<br /> at /usr/src/sys/bus/usb/usb/../../../bus/usb/usbdi.c:548<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> 0xc06e477d in ucomstopread ()<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> 0xc06e41b5 in ucomstop ()<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> 0xc02b1f91 in ttyflush (tp=0xea7e2190, rw=3)<br /> at /usr/src/sys/kern/tty.c:1323<br /><a class="issue tracker-1 status-5 priority-5 priority-high3 closed" title="Bug: make buildworld broken (Closed)" href="https://bugs.dragonflybsd.org/issues/10">#10</a> 0xc02b02ca in ttyinput (c=3, tp=0xea7e2190) at /usr/src/sys/kern/tty.c:459<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: libstand cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/11">#11</a> 0xc06e4639 in ucomreadcb ()<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: /sys/net cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/12">#12</a> 0xc06b4e90 in usb_transfer_complete (xfer=0xea7e2190)<br /> at /usr/src/sys/bus/usb/usb/../../../bus/usb/usbdi.c:830<br /><a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Buildworld error/panic (Closed)" href="https://bugs.dragonflybsd.org/issues/13">#13</a> 0xc06b76d2 in uhci_idone (ii=0x0)<br /> at /usr/src/sys/bus/usb/usb/../../../bus/usb/uhci.c:1480<br />---Type <return> to continue, or q <return> to quit---<br /><a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: zombie processes waiting for a lock, smth to worry about? (Closed)" href="https://bugs.dragonflybsd.org/issues/14">#14</a> 0xc06b75b4 in uhci_check_intr (sc=0xd6f345c0, ii=0xc330c990)<br /> at /usr/src/sys/bus/usb/usb/../../../bus/usb/uhci.c:1355<br /><a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: savecore -z patch (Closed)" href="https://bugs.dragonflybsd.org/issues/15">#15</a> 0xc06b750e in uhci_softintr (v=0xd6f345c0)<br /> at /usr/src/sys/bus/usb/usb/../../../bus/usb/uhci.c:1282<br /><a class="issue tracker-1 status-5 priority-5 priority-high3 closed" title="Bug: install: net/bridge/*.h: No such file or directory (Closed)" href="https://bugs.dragonflybsd.org/issues/16">#16</a> 0xc06b23aa in usb_schedsoftintr (bus=0x0)<br /> at /usr/src/sys/bus/usb/usb/../../../bus/usb/usb.c:831<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: Minor typos (Closed)" href="https://bugs.dragonflybsd.org/issues/17">#17</a> 0xc06b74cc in uhci_intr1 (sc=0xd6f345c0)<br /> at /usr/src/sys/bus/usb/usb/../../../bus/usb/uhci.c:1246<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: extern uint64_t tsc_frequency missing (Closed)" href="https://bugs.dragonflybsd.org/issues/18">#18</a> 0xc06b734e in uhci_intr (arg=0xd6f345c0)<br /> at /usr/src/sys/bus/usb/usb/../../../bus/usb/uhci.c:1161<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: usched questions and a patch (Closed)" href="https://bugs.dragonflybsd.org/issues/19">#19</a> 0xc02716dd in ithread_handler (arg=0xb)<br /> at /usr/src/sys/kern/kern_intr.c:766<br /><a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: No detection of 8169S Gb interface (Closed)" href="https://bugs.dragonflybsd.org/issues/20">#20</a> 0xc0293f30 in lwkt_create (func=0, arg=0x0, tdp=0xc05abfe8, template=0x0, <br /> tdflags=Cannot access memory at address 0x18<br />) at /usr/src/sys/kern/lwkt_thread.c:1290<br />Previous frame inner to this frame (corrupt stack?)<br />(kgdb)</p>
<p>This after some ^C and cable pulling while using /dev/ucom0.</p>
<p>Regards,<br />Johannes</p> DragonFlyBSD - Bug #361: uplcom(4) update from FreeBSDhttps://bugs.dragonflybsd.org/issues/361?journal_id=15502006-11-08T06:40:02Zqhwt+dfly
<ul></ul><p>Hi,<br />On Tue, Nov 07, 2006 at 10:01:17PM +0000, Johannes Hofmann wrote:</p>
<blockquote>
<p>Johannes Hofmann <<a class="email" href="mailto:Johannes.Hofmann@gmx.de">Johannes.Hofmann@gmx.de</a>> wrote:</p>
<blockquote>
<p>Hi Sascha, me objects :-) <br />I just got two crashes while accessing the updated driver... <br />Unfortunately no dumps though. I will try to fix this.</p>
</blockquote>
<p>Ok, I finally got a core dump. The dump device was too small after<br />a memory upgrade...</p>
<p>Here is what I got:</p>
<p>(kgdb) bt<br />#0 dumpsys () at thread.h:83<br /><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> 0xc028d3c3 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:355<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> 0xc028da56 in panic (<br />fmt=0xc06cb0e8 "uhci_abort_xfer: not in process context")<br />at /usr/src/sys/kern/kern_shutdown.c:757<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> 0xc06b802b in uhci_abort_xfer (xfer=0xc330c920, status=USBD_CANCELLED)</p>
</blockquote>
:
<blockquote>
<p>(kgdb)</p>
<p>This after some ^C and cable pulling while using /dev/ucom0.</p>
</blockquote>
<p>Apparently uplcom.c in FreeBSD now uses taskqueue to avoid this situation.<br />I'm not sure we can do it the same way, though.</p>
<pre><code>revision 1.27<br /> date: 2005-01-31 22:58:10 +0900; author: akiyama; state: Exp; lines: +18 -0;<br /> Use a taskqueue to handle port status changes.<br /> Calling ucom layer directly from interrupt context make a panic.</code></pre>
<pre><code>MFC after: 1 week</code></pre>
<p>Cheers.</p> DragonFlyBSD - Bug #361: uplcom(4) update from FreeBSDhttps://bugs.dragonflybsd.org/issues/361?journal_id=15542006-11-09T02:03:00Zdillon
<ul></ul><p>:...<br />:<br />:Apparently uplcom.c in FreeBSD now uses taskqueue to avoid this situation.<br />:I'm not sure we can do it the same way, though.<br />:<br />: revision 1.27<br />: date: 2005-01-31 22:58:10 +0900; author: akiyama; state: Exp; lines: +18 -0;<br />: Use a taskqueue to handle port status changes.<br />: Calling ucom layer directly from interrupt context make a panic.<br />:<br />: MFC after: 1 week<br />:<br />:Cheers.</p>
<pre><code>Yah, you'll have to port the taskqueue change.</code></pre>
<pre><code>The panic is not <strong>actually</strong> due to a missing process context, because<br /> the curproc check was removed from that particular codepath. It's due<br /> to the routine being called from an interrupt. The procedure does<br /> some nasty stuff, including calling tsleep(), so it really can't be<br /> called directly from an interrupt.</code></pre>
<pre><code>-Matt<br /> Matthew Dillon <br /> &lt;<a class="email" href="mailto:dillon@backplane.com">dillon@backplane.com</a>&gt;</code></pre> DragonFlyBSD - Bug #361: uplcom(4) update from FreeBSDhttps://bugs.dragonflybsd.org/issues/361?journal_id=15672006-11-12T01:24:01ZJohannes.Hofmann
<ul></ul><p>Thanks for the hint! I have an updated patch at<br /><a class="external" href="http://www.ecademix.com/JohannesHofmann/uplcom2.diff.gz">http://www.ecademix.com/JohannesHofmann/uplcom2.diff.gz</a></p>
<p>No crashes so far.</p>
<pre><code>Johannes</code></pre> DragonFlyBSD - Bug #361: uplcom(4) update from FreeBSDhttps://bugs.dragonflybsd.org/issues/361?journal_id=15692006-11-12T02:37:00Zdillon
<ul></ul><p>:Thanks for the hint! I have an updated patch at<br />:http://www.ecademix.com/JohannesHofmann/uplcom2.diff.gz<br />:<br />:No crashes so far.<br />:<br />: Johannes</p>
<pre><code>The patch looks very good. Do you think its ready for commit on Monday<br /> or do you want some more time to work on it?</code></pre>
<pre><code>-Matt<br /> Matthew Dillon <br /> &lt;<a class="email" href="mailto:dillon@backplane.com">dillon@backplane.com</a>&gt;</code></pre> DragonFlyBSD - Bug #361: uplcom(4) update from FreeBSDhttps://bugs.dragonflybsd.org/issues/361?journal_id=15752006-11-12T18:18:01ZJohannes.Hofmann
<ul></ul><p>I think it's ready for commit. However I am also thinking about porting <br />some changes to the generic ucom driver from FreeBSD.<br />But that should probabely be done separately.</p> DragonFlyBSD - Bug #361: uplcom(4) update from FreeBSDhttps://bugs.dragonflybsd.org/issues/361?journal_id=15852006-11-14T05:49:00Zswildner
<ul></ul><p>Allright, I've committed it. Thanks for submitting.</p>
<p>Sascha</p> DragonFlyBSD - Bug #361: uplcom(4) update from FreeBSDhttps://bugs.dragonflybsd.org/issues/361?journal_id=16122006-11-19T10:16:59Zjustin
<ul></ul><p>Committed by Sascha:<br /><a class="external" href="http://www.dragonflybsd.org/cvsweb/src/sys/dev/usbmisc/uplcom/uplcom.c?rev=1.9&content-type=text/x-cvsweb-markup">http://www.dragonflybsd.org/cvsweb/src/sys/dev/usbmisc/uplcom/uplcom.c?rev=1.9&content-type=text/x-cvsweb-markup</a></p>