Date: Sun, 12 Jul 2009 14:03:34 +0200 From: "Paul B. Mahol" <onemda@gmail.com> To: Lucius Windschuh <lwindschuh@googlemail.com> Cc: current@freebsd.org Subject: Re: uath0 issues: eject-caused panic, won't work after a restart. Message-ID: <3a142e750907120503j286c3cf6o249f9e9801f1573f@mail.gmail.com> In-Reply-To: <90a5caac0907120353k69fb4f23q5e2f0eff35cfa2c5@mail.gmail.com> References: <90a5caac0907120353k69fb4f23q5e2f0eff35cfa2c5@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 7/12/09, Lucius Windschuh <lwindschuh@googlemail.com> wrote: > Hi guys, > I'm using CURRENT r195362MP and have two issues with it. > > 1st: Pulling the device while the kernel was nearly finished shutting > down shutting down resulted in a kernel panic: Try changing order of usbd* calls in uath_detach. I never managed to panic system with USB2 while detaching rum(4) card. Comparing uath(4) with rum(4) usbd_transfer_unsetup is called after 80211 code. So in uath(4) case put usbd_tranfer_unsetup at begining, before 80211 code and test again. -- Paul
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3a142e750907120503j286c3cf6o249f9e9801f1573f>