From owner-freebsd-current Sat Jan 25 9:17:24 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 84A3537B401 for ; Sat, 25 Jan 2003 09:17:22 -0800 (PST) Received: from is1.mh.itc.u-tokyo.ac.jp (is1.mh.itc.u-tokyo.ac.jp [133.11.205.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6065A43F5B for ; Sat, 25 Jan 2003 09:17:17 -0800 (PST) (envelope-from simokawa@sat.t.u-tokyo.ac.jp) Received: from is1.mh.itc.u-tokyo.ac.jp (is1.mh.itc.u-tokyo.ac.jp [127.0.0.1]) by is1.mh.itc.u-tokyo.ac.jp (Postfix) with ESMTP id 0CD3E218095 for ; Sun, 26 Jan 2003 02:17:10 +0900 (JST) Received: from mailhosting.itc.u-tokyo.ac.jp (IDENT:mirapoint@mailhosting.itc.u-tokyo.ac.jp [133.11.205.3]) by is1.mh.itc.u-tokyo.ac.jp (8.11.3/8.11.3) with ESMTP id h0PHH9c01599; Sun, 26 Jan 2003 02:17:09 +0900 Received: from ett.sat.t.u-tokyo.ac.jp (ett.sat.t.u-tokyo.ac.jp [133.11.135.3]) by mailhosting.itc.u-tokyo.ac.jp (Mirapoint Messaging Server MOS 2.9.3.2) with ESMTP id AHS88793; Sun, 26 Jan 2003 02:17:06 +0900 (JST) Date: Sun, 26 Jan 2003 02:17:06 +0900 Message-ID: From: Hidetoshi Shimokawa To: Andrea Campi Cc: current@freebsd.org Subject: Re: firewire hangs on Thinkpad In-Reply-To: <20030124144823.GA600@webcom.it> References: <20030124144823.GA600@webcom.it> User-Agent: Wanderlust/2.11.0 (Wonderwall) REMI/1.14.3 (Matsudai) FLIM/1.14.3 (=?ISO-8859-1?Q?Unebigory=F2mae?=) APEL/10.3 MULE XEmacs/21.4 (patch 8) (Honest Recruiter) (i386--freebsd) X-Face: OE([KxWyJI0r[R~S/>7ia}SJ)i%a,$-9%7{*yihQk|]gl}2p#"oXmX/fT}Bn7: #j7i14gu$jgR\S*&C3R/pJX List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG hmm, I have no problem with my FireWire CardBus card. If you can get traceback in DDB, please send it to me. cardbus0: Resource not specified in CIS: id=10, size=800 cardbus0: Resource not specified in CIS: id=14, size=4000 fwohci1: mem 0x88004000-0x88007fff,0x88008000-0x880087ff irq 9 at device 0.0 on cardbus0 fwohci1: PCI bus latency was changing to 250. fwohci1: OHCI version 1.0 (ROM=1) fwohci1: No. of Isochronous channel is 4. fwohci1: EUI64 00:c0:d0:00:00:f8:56:6a fwohci1: Phy 1394a available S400, 2 ports. fwohci1: Link S400, max_rec 2048 bytes. firewire1: on fwohci1 if_fwe1: on firewire1 if_fwe1: Fake Ethernet address: 02:c0:d0:f8:56:6a fwohci1: BUS reset fwohci1: node_id = 0x8800ffc0, non CYCLEMASTER mode firewire1: 3 nodes, maxhop <= 2, cable IRM = 2 firewire1: new bus manager 2 firewire1: New S400 device ID:00d03200a412006a firewire1: New S400 device ID:00a0b00a00060633 firewire1: Device SBP-II /\ Hidetoshi Shimokawa \/ simokawa@sat.t.u-tokyo.ac.jp PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html At Fri, 24 Jan 2003 15:48:23 +0100, Andrea Campi wrote: > > Hi all, > > I'm having a bad time trying to get a firewire cardbus adapter to work. > First of all, let me say that I'm under no pressure - I just bought it to > test our firewire implementation but I have no pressing need for it. > > Anyway, new kernel from last night, when I insert the card I get the following: > > cardbus0: Expecting link target, got 0x42 > cardbus0: Resource not specified in CIS: id=10, size=800 > cardbus0: Resource not specified in CIS: id=14, size=4000 > cardbus0: Resource not specified in CIS: id=18, size=800 > fwohci0: mem 0x880 08000-0x880087ff,0x88004000-0x88007fff,0x88008800-0x88008fff irq 11 at device 0.0 on cardbus0 > fwohci0: PCI bus latency was changing to 250. > fwohci0: OHCI version 1.10 (ROM=1) > fwohci0: No. of Isochronous channel is 4. > fwohci0: EUI64 00:01:fb:00:00:00:00:6e > fwohci0: Phy 1394a available S400, 2 ports. > fwohci0: Link S400, max_rec 2048 bytes. > firewire0: on fwohci0 > fwohci0: BUS reset > fwohci0: BUS reset > fwohci0: node_id = 0xc000ffc0, CYCLEMASTER mode > firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) > > > Sometimes it hangs the machine solid to the point I can't enter DDB, other > times it takes a few seconds during which the machine is responsive, other > times DDB is usable. I wasn't able to determine any rule to explain the > different behaviors, but if anybody has any idea, I can try go get to DDB > again and get any required info. > > Bye, > Andrea > > -- > Where do you think you're going today? > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message