Date: Sun, 7 Jul 2013 09:32:51 +0200 From: =?utf-8?Q?Hans_Petter_Selasky?= <hans.petter.selasky@bitfrost.no> To: =?utf-8?Q?Ian_Smith?= <smithi@nimnet.asn.au>, =?utf-8?Q?Adrian_Chadd?= <adrian@freebsd.org> Cc: =?utf-8?Q?freebsd-acpi=40freebsd=2Eorg?= <freebsd-acpi@freebsd.org>, =?utf-8?Q?freebsd-stable=40freebsd=2Eorg?= <freebsd-stable@freebsd.org>, =?utf-8?Q?freebsd-usb=40freebsd=2Eorg?= <freebsd-usb@freebsd.org> Subject: RE: USB ports on Lenovo T400 do not work after a suspend/resume Message-ID: <zarafa.51d919a3.5c6f.493404901d08afeb@mail.lockless.no> In-Reply-To: <20130707154526.O26496@sola.nimnet.asn.au> References: <CAJ-Vmomg2j-nJi%2BqFr3CpCjHKjHEiLE=xyNyx1VGRL5U-r8gzQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi,=0D=0A=0D=0AFYI: The USB stack will currently run a complete controlle= r reset upon resume, like during boot.=0D=0A=0D=0A--HPS=20=0D=0A=0D=0A=20= =0D=0A-----Original message-----=0D=0A> From:Ian Smith <smithi@nimnet.asn= =2Eau <mailto:smithi@nimnet.asn.au> >=0D=0A> Sent: Sunday 7th July 2013 7= :52=0D=0A> To: Adrian Chadd <adrian@freebsd.org <mailto:adrian@freebsd.or= g> >=0D=0A> Cc: freebsd-acpi@freebsd.org <mailto:freebsd-acpi@freebsd.org= > ; freebsd-stable@freebsd.org <mailto:freebsd-stable@freebsd.org> ; free= bsd-usb@freebsd.org <mailto:freebsd-usb@freebsd.org>=20=0D=0A> Subject: R= e: USB ports on Lenovo T400 do not work after a suspend/resume=0D=0A>=20=0D= =0A> On Sun, 30 Jun 2013 15:02:57 -0700, Adrian Chadd wrote:=0D=0A> > On= 30 June 2013 07:22, Ian Smith <smithi@nimnet.asn.au <mailto:smithi@nimne= t.asn.au> > wrote:=0D=0A> [..]=0D=0A> > > Nothing of note that I can see= , if that usb hub-to-bus remapping is=0D=0A> > > normal. As you said, '= CPU0: local APIC error 0x40' looks maybe sus.=0D=0A> > > Maybe someone w= ho knows might comment on that=3F=0D=0A>=20=0D=0A> Does noone know what t= hat signifies=3F Maybe it's not relevant to this.=0D=0A>=20=0D=0A> > > = Just checking: you've tried other USB devices apart from uftdi0=3F=0D=0A>= >=20=0D=0A> > Yup, there's no 5v on the port.=0D=0A>=20=0D=0A> I was r= ather taken aback to hear this. Would not this indicate a=20=0D=0A> fail= ure to reinitialise the basic underlying USB hardware on resume=3F=0D=0A>= =20=0D=0A> More than a bit bemused, Ian=0D=0A> __________________________= _____________________=0D=0A> freebsd-acpi@freebsd.org <mailto:freebsd-acp= i@freebsd.org> mailing list=0D=0A> http://lists.freebsd.org/mailman/list= info/freebsd-acpi <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi= >=20=0D=0A> To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@fr= eebsd.org <mailto:freebsd-acpi-unsubscribe@freebsd.org> "=0D=0A>=20=0D=0A= =0D=0A From owner-freebsd-usb@FreeBSD.ORG Sun Jul 7 07:36:43 2013 Return-Path: <owner-freebsd-usb@FreeBSD.ORG> Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 902ADBD; Sun, 7 Jul 2013 07:36:43 +0000 (UTC) (envelope-from hans.petter.selasky@bitfrost.no) Received: from mta.bitpro.no (mta.bitpro.no [92.42.64.202]) by mx1.freebsd.org (Postfix) with ESMTP id 9FE6115BB; Sun, 7 Jul 2013 07:36:42 +0000 (UTC) Received: from mail.lockless.no (mail.lockless.no [46.29.221.38]) by mta.bitpro.no (Postfix) with ESMTP id B10A67A185; Sun, 7 Jul 2013 09:36:41 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mail.lockless.no (Postfix) with ESMTP id 9C9518ED852; Sun, 7 Jul 2013 09:36:41 +0200 (CEST) X-Virus-Scanned: by amavisd-new-2.6.4 (20090625) (Debian) at lockless.no Received: from mail.lockless.no ([127.0.0.1]) by localhost (mail.lockless.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o6E3vCOiERQs; Sun, 7 Jul 2013 09:36:40 +0200 (CEST) Received: from mail.lockless.no (localhost [127.0.0.1]) by mail.lockless.no (Postfix) with ESMTP id 0A7CD8ED850; Sun, 7 Jul 2013 09:36:40 +0200 (CEST) Subject: RE: XHCI umass support breaks between r248085 and r252560 on 9-STABLE From: =?utf-8?Q?Hans_Petter_Selasky?= <hans.petter.selasky@bitfrost.no> To: =?utf-8?Q?Alexandre_Kovalenko?= <bsd.gaijin@gmail.com>, =?utf-8?Q?freebsd-usb=40freebsd=2Eorg?= <freebsd-usb@freebsd.org> Date: Sun, 7 Jul 2013 09:36:39 +0200 Mime-Version: 1.0 In-Reply-To: <94A3DD2E-F2E2-4302-8197-BAB213641E2F@gmail.com> References: <94A3DD2E-F2E2-4302-8197-BAB213641E2F@gmail.com> X-Priority: 3 (Normal) X-Mailer: Zarafa 7.1.4-41394 Message-Id: <zarafa.51d91a87.5cfd.20d9b227170fae87@mail.lockless.no> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: =?utf-8?Q?mav=40freebsd=2Eorg?= <mav@freebsd.org>, =?utf-8?Q?freebsd-stable=40freebsd=2Eorg?= <freebsd-stable@freebsd.org> X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: FreeBSD support for USB <freebsd-usb.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-usb>, <mailto:freebsd-usb-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-usb>; List-Post: <mailto:freebsd-usb@freebsd.org> List-Help: <mailto:freebsd-usb-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-usb>, <mailto:freebsd-usb-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sun, 07 Jul 2013 07:36:43 -0000 Hi,=0D=0A=0D=0ACheck for CAM/SCSI related changes. There has not been so = many USB changes recently. Possibly not USB related.=0D=0A=0D=0AThank you= ,=0D=0A=0D=0A--HPS=0D=0A=20=0D=0A-----Original message-----=0D=0A> From:A= lexandre Kovalenko <bsd.gaijin@gmail.com <mailto:bsd.gaijin@gmail.com> >=0D= =0A> Sent: Thursday 4th July 2013 20:58=0D=0A> To: freebsd-usb@freebsd.or= g <mailto:freebsd-usb@freebsd.org>=20=0D=0A> Cc: freebsd-stable@freebsd.o= rg <mailto:freebsd-stable@freebsd.org>=20=0D=0A> Subject: XHCI umass supp= ort breaks between r248085 and r252560 on 9-STABLE=0D=0A>=20=0D=0A> Three= different external hard drives (Seagate, Western Digital and noname USB = 3.0 enclosure) refused to be recognized as the umass devices. Reverting /= usr/src/sys/dev/bsd/controller to r248085, building and loading just xhci= module makes drives appear again. Below are snippets from the log in bot= h cases:=0D=0A>=20=0D=0A> Non working:=0D=0A>=20=0D=0A> Jul 4 14:35:17 t= winhead kernel: xhci0: <XHCI (generic) USB 3.0 controller> mem 0xfddfe000= -0xfddfffff irq 16 at device 0.0 on pci2=0D=0A> Jul 4 14:35:17 twinhead = kernel: xhci0: 64 byte context size.=0D=0A> Jul 4 14:35:17 twinhead kern= el: usbus0 on xhci0=0D=0A> Jul 4 14:35:17 twinhead kernel: usbus0: 5.0Gb= ps Super Speed USB v3.0=0D=0A> Jul 4 14:35:17 twinhead kernel: ugen0.1: = <0x1912> at usbus0=0D=0A> Jul 4 14:35:17 twinhead kernel: uhub0: <0x1912= XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0=0D=0A> Jul 4= 14:35:17 twinhead kernel: uhub0: 8 ports with 8 removable, self powered=0D= =0A> Jul 4 14:35:24 twinhead kernel: ugen0.2: <ASMedia> at usbus0=0D=0A>= Jul 4 14:35:24 twinhead kernel: umass0: <ASMedia AS2105, class 0/0, rev= 3.00/0.01, addr 1> on usbus0=0D=0A> Jul 4 14:35:29 twinhead kernel: (pr= obe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 00 00 00 24 00=20=0D=0A> Jul 4 = 14:35:29 twinhead kernel: (probe0:umass-sim0:0:0:0): CAM status: CCB requ= est completed with an error=0D=0A> Jul 4 14:35:29 twinhead kernel: (prob= e0:umass-sim0:0:0:0): Retrying command=0D=0A> Jul 4 14:35:30 twinhead ke= rnel: (probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 00 00 00 24 00=20=0D=0A= > Jul 4 14:35:30 twinhead kernel: (probe0:umass-sim0:0:0:0): CAM status:= CCB request completed with an error=0D=0A> Jul 4 14:35:30 twinhead kern= el: (probe0:umass-sim0:0:0:0): Retrying command=0D=0A> Jul 4 14:35:35 tw= inhead kernel: (probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 00 00 00 24 00= =20=0D=0A> Jul 4 14:35:35 twinhead kernel: (probe0:umass-sim0:0:0:0): CA= M status: CCB request completed with an error=0D=0A> Jul 4 14:35:35 twin= head kernel: (probe0:umass-sim0:0:0:0): Retrying command=0D=0A> Jul 4 14= :35:36 twinhead kernel: (probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 00 00= 00 24 00=20=0D=0A> Jul 4 14:35:36 twinhead kernel: (probe0:umass-sim0:0= :0:0): CAM status: CCB request completed with an error=0D=0A> Jul 4 14:3= 5:36 twinhead kernel: (probe0:umass-sim0:0:0:0): Retrying command=0D=0A> = Jul 4 14:35:41 twinhead kernel: (probe0:umass-sim0:0:0:0): INQUIRY. CDB:= 12 00 00 00 24 00=20=0D=0A> Jul 4 14:35:41 twinhead kernel: (probe0:uma= ss-sim0:0:0:0): CAM status: CCB request completed with an error=0D=0A> Ju= l 4 14:35:41 twinhead kernel: (probe0:umass-sim0:0:0:0): Error 5, Retrie= s exhausted=0D=0A>=20=0D=0A> Working:=0D=0A>=20=0D=0A> Jul 4 14:40:20 tw= inhead kernel: ugen0.2: <ASMedia> at usbus0 (disconnected)=0D=0A> Jul 4 = 14:40:20 twinhead kernel: umass0: at uhub0, port 2, addr 1 (disconnected)= =0D=0A> Jul 4 14:40:27 twinhead kernel: ugen0.2: <vendor 0x174c> at usbu= s0=0D=0A> Jul 4 14:40:27 twinhead kernel: umass0: <vendor 0x174c product= 0x5106, class 0/0, rev 3.00/0.01, addr 1> on usbus0=0D=0A> Jul 4 14:40:= 27 twinhead kernel: (probe0:umass-sim0:0:0:0): REPORT LUNS. CDB: a0 00 00= 00 00 00 00 00 00 10 00 00=20=0D=0A> Jul 4 14:40:27 twinhead kernel: (p= robe0:umass-sim0:0:0:0): CAM status: SCSI Status Error=0D=0A> Jul 4 14:4= 0:27 twinhead kernel: (probe0:umass-sim0:0:0:0): SCSI status: Check Condi= tion=0D=0A> Jul 4 14:40:27 twinhead kernel: (probe0:umass-sim0:0:0:0): S= CSI sense: ILLEGAL REQUEST asc:20,0 (Invalid command operation code)=0D=0A= > Jul 4 14:40:27 twinhead kernel: (probe0:umass-sim0:0:0:0): Error 22, U= nretryable error=0D=0A> Jul 4 14:40:27 twinhead kernel: da0 at umass-sim= 0 bus 0 scbus4 target 0 lun 0=0D=0A> Jul 4 14:40:27 twinhead kernel: da0= : <Hitachi HTS542520K9SA00 BBDO> Fixed Direct Access SCSI-5 device=20=0D=0A= > Jul 4 14:40:27 twinhead kernel: da0: 400.000MB/s transfers=0D=0A> Jul = 4 14:40:27 twinhead kernel: da0: 190782MB (390721968 512 byte sectors: 2= 55H 63S/T 24321C)=0D=0A> Jul 4 14:40:27 twinhead kernel: da0: quirks=3D0= x2<NO_6_BYTE>=0D=0A>=20=0D=0A> I can provide additional information or tr= y patches as necessary.=0D=0A>=20=0D=0A> Alexandre "Sunny" Kovalenko (=D0= =9E=D0=BB=D0=B5=D0=BA=D1=81=D0=B0=D0=BD=D0=B4=D1=80 =D0=9A=D0=BE=D0=B2=D0= =B0=D0=BB=D0=B5=D0=BD=D0=BA=D0=BE)=0D=0A>=20=0D=0A> _____________________= __________________________=0D=0A> freebsd-usb@freebsd.org <mailto:freebsd= -usb@freebsd.org> mailing list=0D=0A> http://lists.freebsd.org/mailman/l= istinfo/freebsd-usb <http://lists.freebsd.org/mailman/listinfo/freebsd-us= b>=20=0D=0A> To unsubscribe, send any mail to "freebsd-usb-unsubscribe@fr= eebsd.org <mailto:freebsd-usb-unsubscribe@freebsd.org> "=0D=0A=0D=0A From owner-freebsd-usb@FreeBSD.ORG Sun Jul 7 10:26:42 2013 Return-Path: <owner-freebsd-usb@FreeBSD.ORG> Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 07763A53; Sun, 7 Jul 2013 10:26:42 +0000 (UTC) (envelope-from jdc@koitsu.org) Received: from relay4-d.mail.gandi.net (relay4-d.mail.gandi.net [217.70.183.196]) by mx1.freebsd.org (Postfix) with ESMTP id B15201E3A; Sun, 7 Jul 2013 10:26:41 +0000 (UTC) Received: from mfilter3-d.gandi.net (mfilter3-d.gandi.net [217.70.178.133]) by relay4-d.mail.gandi.net (Postfix) with ESMTP id AA0BC172071; Sun, 7 Jul 2013 12:26:30 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mfilter3-d.gandi.net Received: from relay4-d.mail.gandi.net ([217.70.183.196]) by mfilter3-d.gandi.net (mfilter3-d.gandi.net [10.0.15.180]) (amavisd-new, port 10024) with ESMTP id TiBcnnYtprZp; Sun, 7 Jul 2013 12:26:29 +0200 (CEST) X-Originating-IP: 76.102.14.35 Received: from jdc.koitsu.org (c-76-102-14-35.hsd1.ca.comcast.net [76.102.14.35]) (Authenticated sender: jdc@koitsu.org) by relay4-d.mail.gandi.net (Postfix) with ESMTPSA id 09BE7172081; Sun, 7 Jul 2013 12:26:25 +0200 (CEST) Received: by icarus.home.lan (Postfix, from userid 1000) id 46AE973A31; Sun, 7 Jul 2013 03:26:24 -0700 (PDT) Date: Sun, 7 Jul 2013 03:26:24 -0700 From: Jeremy Chadwick <jdc@koitsu.org> To: Ian Smith <smithi@nimnet.asn.au> Subject: Re: USB ports on Lenovo T400 do not work after a suspend/resume Message-ID: <20130707102624.GB51445@icarus.home.lan> References: <CAJ-Vmo=W3GW9FzLrTPePhJo_-KY_U--YWCCqA+8aWx8HbLkT+g@mail.gmail.com> <20130626152833.M78748@sola.nimnet.asn.au> <CAJ-Vmo=rhm-9mnRcnwWO1ANOZMNpiFXVkHNTVJ+aeJzpbGgF-g@mail.gmail.com> <20130626195154.GK88288@e-new.0x20.net> <CAJ-VmokEf2_EKKJMB=yqH1pimdNvdmaKvh+3-jJu_6vt5CUakA@mail.gmail.com> <20130627213331.W26984@sola.nimnet.asn.au> <CAJ-VmomUGm7CMpe5k=x4J8g5X9hzP-wV2OEhLf8ySbWx-THJLA@mail.gmail.com> <20130630233640.Y23789@sola.nimnet.asn.au> <CAJ-Vmokh=yAa_NsoE5ud2CdD0gMAiMCthwJ_DqW23_hnav7-Jw@mail.gmail.com> <20130707154526.O26496@sola.nimnet.asn.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130707154526.O26496@sola.nimnet.asn.au> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org, John Baldwin <jhb@freebsd.org>, freebsd-acpi@freebsd.org, freebsd-usb@freebsd.org X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: FreeBSD support for USB <freebsd-usb.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-usb>, <mailto:freebsd-usb-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-usb>; List-Post: <mailto:freebsd-usb@freebsd.org> List-Help: <mailto:freebsd-usb-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-usb>, <mailto:freebsd-usb-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sun, 07 Jul 2013 10:26:42 -0000 On Sun, Jul 07, 2013 at 03:51:12PM +1000, Ian Smith wrote: > On Sun, 30 Jun 2013 15:02:57 -0700, Adrian Chadd wrote: > > On 30 June 2013 07:22, Ian Smith <smithi@nimnet.asn.au> wrote: > [..] > > > Nothing of note that I can see, if that usb hub-to-bus remapping is > > > normal. As you said, 'CPU0: local APIC error 0x40' looks maybe sus. > > > Maybe someone who knows might comment on that? > > Does noone know what that signifies? Maybe it's not relevant to this. It's too vague to know. The error comes from lapic_handle_error(), which is a generic/small routine which pulls the local APIC error status register. (Note I'm saying APIC, not ACPI -- two different things) apic_vector.S sets this up/makes use of this function, and its done as an interrupt handler. I think this is one of those situations where you have to know *what* is being set up/done at that moment in time for the error code to mean something. Maybe booting verbose would give more information as to what was being done that lead up to the line. I've CC'd John Baldwin who might have some ideas. -- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Making life hard for others since 1977. PGP 4BD6C0CB |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?zarafa.51d919a3.5c6f.493404901d08afeb>