From owner-freebsd-mobile Tue Apr 24 23:13:43 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id F249937B422 for ; Tue, 24 Apr 2001 23:13:39 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.1) with ESMTP id f3P6DS819951; Wed, 25 Apr 2001 00:13:34 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200104250613.f3P6DS819951@harmony.village.org> To: Randy Bush Subject: Re: wi0 timeouts Cc: FreeBSD Laptoppers In-reply-to: Your message of "Tue, 24 Apr 2001 16:39:47 PDT." References: Date: Wed, 25 Apr 2001 00:13:28 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message Randy Bush writes: : i am seeing the following every few minutes or more often : : Apr 24 15:59:14 pccardd[138]: wi0: Lucent Technologies (WaveLAN/IEEE) inserted. : Apr 24 16:00:36 /kernel: wi0: wi_cmd: device timeout (cmd=11, val=f100) : Apr 24 16:04:36 /kernel: wi0: wi_cmd: device timeout (cmd=11, val=f100) : Apr 24 16:06:36 /kernel: wi0: wi_cmd: device timeout (cmd=11, val=f100) : Apr 24 16:15:36 last message repeated 2 times : Apr 24 16:25:36 last message repeated 4 times : Apr 24 16:33:37 last message repeated 2 times : : have not seen it before. device timeout is interesting. Usually you see a can't allocate TX/RX buffer when the interrupt is wrong. irq 7 might be the problem. If you have a parallel port, it might be driving it such that your pccard bridge can't drive it (but that would be a can't allocate TX/RX thing). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message