From owner-freebsd-current@FreeBSD.ORG Sun Oct 4 15:15:16 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BC1201065672 for ; Sun, 4 Oct 2009 15:15:16 +0000 (UTC) (envelope-from lwindschuh@googlemail.com) Received: from mail-qy0-f192.google.com (mail-qy0-f192.google.com [209.85.221.192]) by mx1.freebsd.org (Postfix) with ESMTP id 784B98FC62 for ; Sun, 4 Oct 2009 15:15:16 +0000 (UTC) Received: by qyk30 with SMTP id 30so2682203qyk.7 for ; Sun, 04 Oct 2009 08:15:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=qm2y3mHLM7N1cCU2u4J+9W8uALrZNM+6Rz5JY+uPrhQ=; b=Vz3YfufyvBXINGK956sYVDyM9ES3epAV9lpXXQAvylnwcq6CMgl+LZzPHffUPJtFim cj2iDf1qry7Lf+CDUmr0zjyxwLBR7NF7N7YwPL6Y8MmfnA4K/UV8F37GFYiSDdtojLCB 3a6UCWprAQCf4Oa0iJmpF45H8zggXjvFZfsn8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=s5iAfZV2ro6L1lbEc+n6S4B68+2LlDiuLVa40o6JcQek5wsEl/l7hq0UnwvGjm1Dw0 NHY98vTc1WIFGThQ1jFx6QerFvOJMeJdoNWVgSc0CzXALVxNVTiXbjFX2id0lGkJL7nq oe1HfyHwEATZOGcwNMwXicZ9rKV+aTbZ5p2xI= MIME-Version: 1.0 Received: by 10.229.36.195 with SMTP id u3mr3570642qcd.61.1254669315833; Sun, 04 Oct 2009 08:15:15 -0700 (PDT) In-Reply-To: <20091003014251.GI1454@weongyo> References: <90a5caac0907120353k69fb4f23q5e2f0eff35cfa2c5@mail.gmail.com> <20091003014251.GI1454@weongyo> Date: Sun, 4 Oct 2009 17:15:15 +0200 Message-ID: <90a5caac0910040815l1f8a4d8dj3352568227c3c386@mail.gmail.com> From: Lucius Windschuh To: Weongyo Jeong , current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Subject: Re: uath0 issues: eject-caused panic, won't work after a restart. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Oct 2009 15:15:16 -0000 Hi. 2009/10/3 Weongyo Jeong : > On Sun, Jul 12, 2009 at 12:53:38PM +0200, Lucius Windschuh 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: >> > [...] > Already passed about 3 months. =A0:-) > > Could you please test with CURRENT to reproduce this problem? =A0On my > environment it doesn't happen anymore. =A0I'd like to know this issue is > still valid. I can't reproduce this problem either. It seems that this problem is fixed: Pulling the device out in different stages of the shutdown process did not result in a panic. Fine, when time destroys bugs. :-D >> 2nd issue: >> >> With an plugged and firmware-loaded uath device (TRENDnet TEW-504UB in >> my case), reboot the system. It is not initialized by uath until you >> pull and plug it back in. >> The USB descriptors, obtained by usbconfig dump_device_desc, are the >> same before pulling and after reinitializing the device. >> >> Is there anything I can do to help fixing these issues? > > I tried to solve this issue on my amd64 machine but could not find a way > to fix. =A0It looks HAL interface doesn't have a API to reset full H/W an= d > endpoint 0 also don't have a such feature. =A0Only a way looks a bus rese= t > event (EHCI_STS_RESET) currently depending on the system for example, > powerpc I have seems it hasn't this problem but amd64 has. If a bus reset only affects the device and not a whole bus, this is worth a= try. Regards Lucius