From owner-freebsd-current@FreeBSD.ORG Sun Jan 23 02:44:10 2005 Return-Path: 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 4E2E016A4D3 for ; Sun, 23 Jan 2005 02:44:10 +0000 (GMT) Received: from ank-pki.ru (mercury.ank-pki.ru [213.170.76.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id 28CCB43D1F for ; Sun, 23 Jan 2005 02:44:08 +0000 (GMT) (envelope-from toxa@cterra.ru) Received: (qmail 74694 invoked by uid 0); 23 Jan 2005 05:44:06 +0300 Received: from toxa@cterra.ru by mercury.ank-pki.ru by uid 0 with qmail-scanner-1.22 (spamassassin: 3.0.2. Clear:RC:0(62.89.204.62):SA:0(?/?):. Processed in 10.435036 secs); 23 Jan 2005 02:44:06 -0000 Received: from unknown (HELO localhost) (toxa@62.89.204.62) by mail.ank-pki.ru with SMTP; 23 Jan 2005 05:43:55 +0300 Date: Sun, 23 Jan 2005 05:42:02 +0300 From: Toxa To: FreeBSD-CURRENT X-Comment-To: "Anton Karpov" Message-ID: <20050123024202.GA30616@laptoxa.toxa.lan> Mail-Followup-To: FreeBSD-CURRENT Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline User-Agent: Outluck Express 1.5.6i for MS-DOS 6.22-SMP X-Mailer: See User-Agent above :) X-Operating-System: MS-DOS 6.22-CURRENT on Sony VAIO laptop X-PGP-Public-Key: http://toxahost.org/gpg/pubkey.asc X-Useless-Header: Do Androids Dream of Electric Sheep? X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on mercury.ank-pki.ru X-Spam-Level: X-Spam-Status: No, score=0.1 required=7.0 tests=NORMAL_HTTP_TO_IP autolearn=failed version=3.0.2 Subject: troubles with recent wireless changes X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 23 Jan 2005 02:44:10 -0000 Hi. After january changes in wireless area I've encountered several problems with my sony vaio laptop. 1. Preloading if_wi (in loader.conf) gives me kernel panic. Sorry I have no serial console to put here trap info, so I can only say it gets fatal trap. I know this is quite useless but that's all I can say. Loading if_wi from userland after boot works ok. I didn't try to build device wi support into kernel because I still hope it will work as usual, someday. 2. After serveral hours of wireless working, I have to reload if_wi due to the such failures (wi stops transmitting data but still connected to AP): wi0: timeout in wi_cmd 0x010b; event status 0x8000 wi0: xmit failed wi0: timeout in wi_seek to 152/0 wi0: timeout in wi_seek to 152/0 wi0: timeout in wi_seek to 152/0 wi0: timeout in wi_seek to 152/0 wi0: bad alloc 128 != 13d, cur 1 nxt 1 3. dstumbler doesn't work anymore due to the "error: unable to ioctl device socket: Invalid argument" My wireless interface: wi0: mem 0xf8000000-0xf8000fff irq 9 at device 2.0 on pci2 wi0: [GIANT-LOCKED] wi0: using RF:PRISM2.5 MAC:ISL3874A(Mini-PCI) wi0: Intersil Firmware: Primary (1.1.0), Station (1.4.3) wi0: Ethernet address: 00:d0:59:49:12:52 My dmesg can be reached ffrom http://62.89.204.62/dmesg/laptoxa.txt (I decide not to put it here in order to avoid big message) Big thanks in advance.