From owner-freebsd-current@FreeBSD.ORG Tue Jan 29 21:08:05 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C5D5216A418 for ; Tue, 29 Jan 2008 21:08:05 +0000 (UTC) (envelope-from cptsalek@gmail.com) Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.187]) by mx1.freebsd.org (Postfix) with ESMTP id 3AB3613C465 for ; Tue, 29 Jan 2008 21:08:04 +0000 (UTC) (envelope-from cptsalek@gmail.com) Received: by mu-out-0910.google.com with SMTP id w9so1240937mue.6 for ; Tue, 29 Jan 2008 13:08:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=dkgr0HWIdh7T06lLFE1bw4ZHnqTNTpYbIrbbrpgzvGM=; b=cC8sfw7cP+pEJAqsnuuGGTR6krZyP0U/88Rb69yLJfli2DFuCTFqgt3kzcO856Stv5kcJkHTnVHB5lNUwddjXqEUC++i4uH79NYFDQy7G/YRjvaGutfM04GURxJD+iIQMs8sgr+/E1PvC7+Qv3QVXbSAW6AE1yFAHJs247N4E+A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=N5iDD2KYa89FIPZBV1XNN2qOlzfPkKE/3LdhswMqfJcW3twSpbWkJe0ed2B6tyAHhpHkVHcgKxI9BFVEhpeQDywuxbXOAxI9T6JGxGtsTN9Pbyt4aYidbE06VtVnjSeJ+iJzHWpPy4iV9UMCT1PEzGSisvP6ev1H2it171Ap5Oo= Received: by 10.82.108.9 with SMTP id g9mr13081433buc.34.1201640883103; Tue, 29 Jan 2008 13:08:03 -0800 (PST) Received: by 10.82.159.19 with HTTP; Tue, 29 Jan 2008 13:08:03 -0800 (PST) Message-ID: <14989d6e0801291308t7490698m219fc1706718a70f@mail.gmail.com> Date: Tue, 29 Jan 2008 21:08:03 +0000 From: "Christian Walther" To: "Stefan Lambrev" In-Reply-To: <14989d6e0801270250p2b6d7411hf2db5d9af4718870@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200801061102.46233.josh@tcbug.org> <47821A0B.7020301@moneybookers.com> <14989d6e0801270250p2b6d7411hf2db5d9af4718870@mail.gmail.com> Cc: Josh Paetzel , current@freebsd.org Subject: Re: state of 7.0-RC1 on an IBM t60p X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 29 Jan 2008 21:08:05 -0000 Hi again, unfortunately I've to correct me myself on the "wpi on T60 issue": On 27/01/2008, Christian Walther wrote: > Hi there, [...] > On 07/01/2008, Stefan Lambrev wrote: > > Hi Josh, > > > > Josh Paetzel wrote: > [...] > > > 1) wpi is nearly non-functional. It seems to associate best to WPA2 networks, > > > struggles with WEP and won't associate at all to open networks. Once it's > > > associated it spams the console with "discarding packet without header" > > > and "wpi_cmd: couldn't set tx power" quite a bit, as well as other random > > > output. The real problem I've had with it is that it panics under moderate > > > data rates, in the 1000-1500K/sec range. > > > > > You can try the latest wpi driver from perforce - > > http://www.clearchain.com/wiki/Wpi > > Also you can disable debugging. > > The latest version of the driver from perforce works on the T60. What > makes me wonder is the fact that I need to specify the channel of the > nearest AP. Otherwise the interface will get no link. wpi works as long as one doesn't do anything that saturates the wlan connection. E.g. running ssh terminal sessions is fine, but trying to scp a bigger file crashes the machine instantaneously. > [...] > > > 3) sutdown output is garbled. This doesn't seem to hurt anything, but at > > > some point in shutdown the console messages start interleaving. > > > > > First time I saw this in RC1 - never with 7-CURRENT or -BETAX (I'm > > talking only about shutdown messages, not boot messages) > > Same here. This is not related to the T60, it's the same on my > Athlon64 based server. Not anymore. > > > > 4) acpi suspend and resume doesn't work, but that's not a huge shock.l > > > > > > 5) ath generates interrupt storms that are throttled. > > > > > Sorry, I do not have idea how to fix this. > > Never had any trouble with interrupt storms on ath. I'm using a D-Link > DWL-G650, the card is identified as: > > ath0: mem 0x88000000-0x8800ffff irq 16 at device 0.0 on cardbus0 > ath0: [ITHREAD] > ath0: using obsoleted if_watchdog interface > ath0: Ethernet address: 00:19:5b:3a:82:be > ath0: mac 7.9 phy 4.5 radio 5.6 > > Seems to be pretty much the same. On my machine (and some more, as reported in another thread) ath freezes when hal is running. As a workaround removing the card during bootup helps. It has just to be configured manually. > > Christian >