From owner-freebsd-current Sun Feb 9 7:42:10 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 B527537B401 for ; Sun, 9 Feb 2003 07:42:07 -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 6DDED43F3F for ; Sun, 9 Feb 2003 07:42:06 -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 332E22180DC for ; Mon, 10 Feb 2003 00:41:59 +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 h19Ffwc19341; Mon, 10 Feb 2003 00:41:58 +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 AHV09503; Mon, 10 Feb 2003 00:41:55 +0900 (JST) Date: Mon, 10 Feb 2003 00:41:55 +0900 Message-ID: From: Hidetoshi Shimokawa To: "M. Warner Losh" Cc: Andrea Campi , current@FreeBSD.ORG Subject: Re: firewire hangs on Thinkpad In-Reply-To: References: <20030124144823.GA600@webcom.it> <20030125.115501.13766238.imp@bsdimp.com> <20030129114951.GA3635@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 Warner-san, I confirmed that the following problem occurs not only for fwochi but also for if_rl, if_xl, if_dc and ahc_pci. After "kldload if_rl", I got wi0 timeout. (I don't even have those hardware.) All drivers above supports both pci and cardbus... Do you have any idea? /\ Hidetoshi Shimokawa \/ simokawa@sat.t.u-tokyo.ac.jp PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html At Thu, 30 Jan 2003 01:25:19 +0900, Hidetoshi Shimokawa wrote: > > At Wed, 29 Jan 2003 12:49:51 +0100, > Andrea Campi wrote: > > > > On Sat, Jan 25, 2003 at 11:55:01AM -0700, M. Warner Losh wrote: > > > This sounds like it might be an interrupt storm. I'm not sure if the > > > fwohci driver is failing to clear an interrupt source, or if the > > > cardbus bridge is failing. Have you connected a fw device to the > > > firewire card? > > > > I've been able to run a few more tests, even though I've not done abused > > it in every way I have in my mind yet... > > > > The evidence I currently have is: > > - if I load the modules at loader time everything is fine, with or without > > a device attached > > - if I load the modules later on, the kldload doesn't return and the system > > stops responding; I can still enter DDB. The only way to recover from that is > > to eject the card; at that point, the system is usable BUT as soon as there > > is network activity, the system freezes hard (can't get to DDB). > > > > IMHO this is 100% an interrupt problem. Does this ring a bell with one of you, > > or should I provide more info? > > I have another strange firewire and cardbus/pccard interaction. > If I load firewire module while I'm using wi0 in cardbus slot, > the wi0 stop its work and output following messages. > (In my laptop, fwohci is on PCI.) > > wi0: xmit failed > wi0: timeout in wi_cmd 0x010b; event status 0x0000 > ... > > > Even if I replace fwochi_pci_attach() with one line 'return EIO' > (i.e. the doesn't anything), the problem still happens. > > I think this is not a problem of fwohci. > Maybe PCI or Cardbus/PCcard or kldload problem? > > > > /\ Hidetoshi Shimokawa > \/ simokawa@sat.t.u-tokyo.ac.jp > PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message