From owner-freebsd-mobile@FreeBSD.ORG Mon Feb 9 02:59:52 2009 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 32A5C1065672 for ; Mon, 9 Feb 2009 02:59:52 +0000 (UTC) (envelope-from charlie1337@bigpond.com) Received: from nskntqsrv03p.mx.bigpond.com (nskntqsrv03p.mx.bigpond.com [61.9.168.237]) by mx1.freebsd.org (Postfix) with ESMTP id C44FC8FC12 for ; Mon, 9 Feb 2009 02:59:51 +0000 (UTC) (envelope-from charlie1337@bigpond.com) Received: from nskntotgx03p.mx.bigpond.com ([58.171.180.170]) by nskntmtas01p.mx.bigpond.com with ESMTP id <20090209022820.JLDS6186.nskntmtas01p.mx.bigpond.com@nskntotgx03p.mx.bigpond.com> for ; Mon, 9 Feb 2009 02:28:20 +0000 Received: from [127.0.0.1] (really [58.171.180.170]) by nskntotgx03p.mx.bigpond.com with ESMTP id <20090209022819.RUII5528.nskntotgx03p.mx.bigpond.com@[127.0.0.1]> for ; Mon, 9 Feb 2009 02:28:19 +0000 Message-ID: <498F94BC.6090301@bigpond.com> Date: Mon, 09 Feb 2009 13:28:12 +1100 From: Wilyarti Howard User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: freebsd-mobile@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH PLAIN at nskntotgx03p.mx.bigpond.com from [58.171.180.170] using ID charlie1337 at Mon, 9 Feb 2009 02:28:19 +0000 X-RPD-ScanID: Class unknown; VirusThreatLevel unknown, RefID str=0001.0A150201.498F94C4.0047,ss=1,fgs=0 Subject: EeePC 701SD X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2009 02:59:52 -0000 I am new to this list and wish to inform all those internested that I have got FreeBSD 7.1 RELEASE on the EeePC going well. The only things that DO NOT work are Camera and Wireless. There were huge problems with speed until I enabled tmpfs for ALL tmp directories and put noatime in /etc/fstab. I also couldnt partion the hard drive for space reason. Also it will not boot if you have another umass storage device besides the SD card because freebsd assigns the USB stick to da0 not the hard drive. Is there a demand or need by the FreeBSD developers for me to test drivers or post info of my Kernel configuration, dmesg and such? Or is this not a great achievment :) By the way powerd works with eeemon.ko and you can controll CPU speed, screen resolution and see all hardware information. If anyone desire such information as /etc/rc.conf, /etc/fstab custom kernal conf and /boot/loader.conf files I would be happy to supply them! If only I had such information when I started the 5 day adventure.... Cheers! -Wilyarti Howard From owner-freebsd-mobile@FreeBSD.ORG Mon Feb 9 05:56:38 2009 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 34364106566B for ; Mon, 9 Feb 2009 05:56:38 +0000 (UTC) (envelope-from matthias.apitz@oclc.org) Received: from hunter.Sisis.de (hunter.sisis.de [193.31.11.194]) by mx1.freebsd.org (Postfix) with ESMTP id 8CFBD8FC16 for ; Mon, 9 Feb 2009 05:56:37 +0000 (UTC) (envelope-from matthias.apitz@oclc.org) Received: (from mail@localhost) by hunter.Sisis.de (8.8.8/8.8.8) id GAA19131; Mon, 9 Feb 2009 06:45:42 +0100 (CET) (envelope-from matthias.apitz@oclc.org) Received: from ppp-93-104-115-94.dynamic.mnet-online.de(93.104.115.94) by hunter.Sisis.de via smap (V2.1) id xma019129; Mon, 9 Feb 09 06:45:40 +0100 Received: (from guru@localhost) by rebelion.Sisis.de (8.14.2/8.13.8/Submit) id n195svp4002607; Mon, 9 Feb 2009 06:54:57 +0100 (CET) (envelope-from matthias.apitz@oclc.org) X-Authentication-Warning: rebelion.Sisis.de: guru set sender to matthias.apitz@oclc.org using -f Date: Mon, 9 Feb 2009 06:54:57 +0100 From: Matthias Apitz To: Wilyarti Howard Message-ID: <20090209055457.GA1821@rebelion.Sisis.de> References: <498F94BC.6090301@bigpond.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <498F94BC.6090301@bigpond.com> User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.0-STABLE (i386) Cc: freebsd-mobile@freebsd.org Subject: Re: EeePC 701SD X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Matthias Apitz List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2009 05:56:38 -0000 El día Monday, February 09, 2009 a las 01:28:12PM +1100, Wilyarti Howard escribió: > I am new to this list and wish to inform all those internested that I > have got FreeBSD 7.1 RELEASE on the EeePC going well. > > The only things that DO NOT work are Camera and Wireless. > > There were huge problems with speed until I enabled tmpfs for ALL tmp > directories and put noatime in /etc/fstab. > > I also couldnt partion the hard drive for space reason. > > Also it will not boot if you have another umass storage device besides > the SD card because freebsd assigns the USB stick to da0 not the hard drive. > > Is there a demand or need by the FreeBSD developers for me to test > drivers or post info of my Kernel configuration, dmesg and such? > > Or is this not a great achievment :) > > By the way powerd works with eeemon.ko and you can controll CPU speed, > screen resolution and see all hardware information. > > If anyone desire such information as /etc/rc.conf, /etc/fstab custom > kernal conf and /boot/loader.conf files I would be happy to supply them! > > If only I had such information when I started the 5 day adventure.... It's a bit late, but maybe you can reflect your work with some ideas from here: http://www.unixarea.de/installEeePC.txt http://wiki.freebsd.org/AsusEee :-) matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ From owner-freebsd-mobile@FreeBSD.ORG Mon Feb 9 10:45:19 2009 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2581B106564A for ; Mon, 9 Feb 2009 10:45:19 +0000 (UTC) (envelope-from bengta@P142.sics.se) Received: from sink.sics.se (sink.sics.se [193.10.64.88]) by mx1.freebsd.org (Postfix) with ESMTP id BD8418FC19 for ; Mon, 9 Feb 2009 10:45:18 +0000 (UTC) (envelope-from bengta@P142.sics.se) Received: from P142.sics.se (P142.sics.se [193.10.66.253]) by sink.sics.se (8.14.3/8.14.3) with ESMTP id n19ADjPa009710 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 9 Feb 2009 11:13:45 +0100 (CET) (envelope-from bengta@P142.sics.se) Received: from P142.sics.se (localhost [127.0.0.1]) by P142.sics.se (8.14.3/8.14.3) with ESMTP id n19AGUbg001405; Mon, 9 Feb 2009 11:16:30 +0100 (CET) (envelope-from bengta@P142.sics.se) Received: (from bengta@localhost) by P142.sics.se (8.14.3/8.14.3/Submit) id n19AGUX3001404; Mon, 9 Feb 2009 11:16:30 +0100 (CET) (envelope-from bengta@P142.sics.se) To: freebsd-mobile@freebsd.org From: Bengt Ahlgren User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (berkeley-unix) Date: Mon, 09 Feb 2009 11:16:30 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Problems with ath at kern.hz=100 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2009 10:45:19 -0000 Hello! I was changing kern.hz to 100 on my IBM X40 (Pentium-M) laptop to see whether that saves some battery, but ran into problems with ath not working properly. At first I thought that my hardware was failing, but changing hz back to 1000 solved the problem. I am running 7.1-RELEASE-p1 and have the following Atheros chip: Feb 9 11:13:10 P142 kernel: ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) Feb 9 11:13:10 P142 kernel: ath0: mem 0xd0200000-0xd020ffff irq 11 at device 2.0 on pci2 Feb 9 11:13:10 P142 kernel: ath0: [ITHREAD] Feb 9 11:13:10 P142 kernel: ath0: WARNING: using obsoleted if_watchdog interface Feb 9 11:13:10 P142 kernel: ath0: Ethernet address: 00:05:4e:4e:1f:c7 Feb 9 11:13:10 P142 kernel: ath0: mac 5.6 phy 4.1 5ghz radio 1.7 2ghz radio 2.3 The symptom is that ath stops sending packets out. They seem to be buffered somewhere. After a while it gets going again, albeit some packets are lost. "A while" can be from 5 secs to a minute or so when continously running a ping. In the below logs, a ping is started when ath has stopped sending. "netstat -I ath0 1" reports that no packets are sent, but the byte count is still incremented. When it gets going again, 18 packets are sent, but the byte count does not reflect that (which perpaps is logical): 1 0 56 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 98 0 1 0 56 0 0 98 0 1 0 56 0 0 98 0 input (ath0) output packets errs bytes packets errs bytes colls 0 0 0 0 0 98 0 1 0 56 0 0 98 0 1 0 56 0 0 98 0 1 0 56 0 0 98 0 0 0 0 0 0 98 0 0 0 0 0 0 98 0 0 0 0 0 0 98 0 0 0 0 0 0 98 0 0 0 0 0 0 98 0 1 0 56 0 0 98 0 1 0 56 0 0 98 0 2 0 112 0 0 98 0 0 0 0 0 0 98 0 4 0 350 18 0 140 0 2 0 112 0 0 0 0 1 1 56 0 0 0 0 1 0 56 0 0 0 0 0 0 0 0 0 0 0 ^C Here is a tcpdump of the same event: 18:40:59.025364 arp who-has 10.1.1.72 tell 10.1.7.250 18:41:00.049385 arp who-has 10.1.1.72 tell 10.1.7.250 18:41:00.868608 arp who-has 10.1.6.253 tell 10.1.7.250 18:41:01.073387 arp who-has 10.1.1.72 tell 10.1.7.250 18:41:02.761445 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 0, length 64 18:41:02.761456 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 1, length 64 18:41:02.761461 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 2, length 64 18:41:02.761466 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 3, length 64 18:41:02.761470 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 4, length 64 18:41:02.761474 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 5, length 64 18:41:02.761479 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 6, length 64 18:41:02.761483 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 7, length 64 18:41:02.761487 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 8, length 64 18:41:02.761492 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 9, length 64 18:41:02.761497 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 10, length 64 18:41:02.761502 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 11, length 64 18:41:02.761506 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 12, length 64 18:41:02.761510 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 13, length 64 18:41:02.761515 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 14, length 64 18:41:02.761519 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 15, length 64 18:41:02.761523 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 16, length 64 18:41:02.916556 arp who-has 10.1.1.107 tell 10.1.7.250 18:41:02.916579 arp reply 10.1.1.107 is-at 00:05:4e:4e:1f:c7 18:41:02.917707 IP 193.10.65.193 > 10.1.1.107: ICMP echo reply, id 63239, seq 14, length 64 18:41:02.917906 IP 193.10.65.193 > 10.1.1.107: ICMP echo reply, id 63239, seq 15, length 64 18:41:02.918187 IP 193.10.65.193 > 10.1.1.107: ICMP echo reply, id 63239, seq 16, length 64 18:41:03.531108 arp who-has 10.1.1.72 tell 10.1.7.250 18:41:04.350185 arp who-has 10.1.6.166 tell 10.1.7.250 18:41:04.554984 arp who-has 10.1.1.72 tell 10.1.7.250 18:41:05.578972 arp who-has 10.1.1.72 tell 10.1.7.250 ^C 289 packets captured 289 packets received by filter 0 packets dropped by kernel Any idea on what the problem can be, or how do debug this further? Regards, Bengt From owner-freebsd-mobile@FreeBSD.ORG Mon Feb 9 14:03:35 2009 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 963BF1065672 for ; Mon, 9 Feb 2009 14:03:35 +0000 (UTC) (envelope-from dsh@wizard.volgograd.ru) Received: from dsh.falconknight.com (dsh.falconknight.com [66.160.163.23]) by mx1.freebsd.org (Postfix) with ESMTP id 820C98FC24 for ; Mon, 9 Feb 2009 14:03:35 +0000 (UTC) (envelope-from dsh@wizard.volgograd.ru) Received: from dsh.falconknight.com (dsh [66.160.163.23]) by dsh.falconknight.com (Postfix) with ESMTP id 2DD2E5BCB5AB for ; Mon, 9 Feb 2009 05:48:24 -0800 (PST) Received: from localhost (unknown [85.173.92.192]) by dsh.falconknight.com (Postfix) with ESMTPSA id 4B9C25BCB528 for ; Mon, 9 Feb 2009 05:48:23 -0800 (PST) Date: Mon, 9 Feb 2009 16:48:20 +0300 From: Denis Shaposhnikov To: freebsd-mobile@freebsd.org Message-ID: <20090209164820.00be4837@wizard.volgograd.ru> X-Mailer: Claws Mail 3.7.0 (GTK+ 2.14.7; i386-portbld-freebsd7.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: RELENG7 on Samsung R510-FA0K (JFYI) X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2009 14:03:36 -0000 Hello, This is just a report about my new notebook with FreeBSD 7.1-STABLE #2: Mon Feb 9 04:36:30 MSK 2009 1. Xorg works with x11-drivers/xf86-video-intel and resolution 1280x800. 2. SD card reader just works. 3. WLAN works with ath_hal-20080528.tgz ath0: mem 0xf3000000-0xf300ffff irq 16 at device 0.0 on pci2 4. Audio works with snd_hda. 5. Touchpad just works: psm0: flags 0x4 irq 12 on atkbdc0 psm0: model Synaptics Touchpad, device ID 0 6. Bluetooth seems don't work: ugen1: on acpi0 ACPI Error (dsopcode-0350): No pointer back to NS node in buffer obj 0xc4dff7c0 [20070320] ACPI Exception (dswexec-0556): AE_AML_INTERNAL, While resolving operands for [OpcodeName unavailable] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_PR_.CPU0._OSC] (Node 0xc4d32380), AE_AML_INTERNAL acpi_throttle0: on cpu0 cpu1: on acpi0 ACPI Error (dsopcode-0350): No pointer back to NS node in buffer obj 0xc4dff300 [20070320] ACPI Exception (dswexec-0556): AE_AML_INTERNAL, While resolving operands for [OpcodeName unavailable] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_PR_.CPU1._OSC] (Node 0xc4d322a0), AE_AML_INTERNAL acpi_throttle1: on cpu1 acpi_throttle1: failed to attach P_CNT device_attach: acpi_throttle1 attach returned 6 From owner-freebsd-mobile@FreeBSD.ORG Mon Feb 9 16:03:33 2009 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 55C2C106566B for ; Mon, 9 Feb 2009 16:03:33 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from mail-gx0-f21.google.com (mail-gx0-f21.google.com [209.85.217.21]) by mx1.freebsd.org (Postfix) with ESMTP id 0DCC08FC0C for ; Mon, 9 Feb 2009 16:03:32 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: by gxk14 with SMTP id 14so2137949gxk.19 for ; Mon, 09 Feb 2009 08:03:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=iLEYqU+pXDrb8/K1ocbfGGJso5F0rgDF6OeCj1cqDSE=; b=PrwKvCWoxPPq9fWX4YGOiaGH0sRrW+74RZA0JSdU+tdl1xUmFi4ivsGKmxxrAZY37E jZ4FjDcWOviBQCD1EnlhcBeVQU/SXmMQZ2vXr4Xql7WE2TvpIRhHxOGXMQqwD5+Q81rV aRFqfwA6X61BJd5xZ3FXULOj/+6NKc5ZrnkwA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=L8jMzZ+LH+Lfr+QqKl0f8NmXbxuAxZq+fQYxpgqGitQ1qDI/phF8wS7XRGVpu1MGTw A9HIsVuE4YALVd3FWHNOJQC0S/5wEJiYrwmntoKDrK2oz+nwBtqbJwmU5ioTzYQZCnJ3 Tw+PDNvbb0mtAFRIPJqcIHb0jrBU7DLve3jl8= MIME-Version: 1.0 Received: by 10.150.152.17 with SMTP id z17mr5007109ybd.127.1234194204279; Mon, 09 Feb 2009 07:43:24 -0800 (PST) In-Reply-To: <20090209164820.00be4837@wizard.volgograd.ru> References: <20090209164820.00be4837@wizard.volgograd.ru> Date: Mon, 9 Feb 2009 07:43:24 -0800 Message-ID: From: Maksim Yevmenkin To: Denis Shaposhnikov Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-mobile@freebsd.org Subject: Re: RELENG7 on Samsung R510-FA0K (JFYI) X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2009 16:03:33 -0000 On Mon, Feb 9, 2009 at 5:48 AM, Denis Shaposhnikov wrote: [...] > 6. Bluetooth seems don't work: > > ugen1: on uhub6 > > Does anybody know about this anything? did you load the driver? ng_ubt(4) for usb1 or usb_bluetooth_ng for usb2. thanks, max From owner-freebsd-mobile@FreeBSD.ORG Mon Feb 9 16:17:49 2009 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 167DF106566C for ; Mon, 9 Feb 2009 16:17:49 +0000 (UTC) (envelope-from dsh@wizard.volgograd.ru) Received: from dsh.falconknight.com (dsh.falconknight.com [66.160.163.23]) by mx1.freebsd.org (Postfix) with ESMTP id 0147D8FC1B for ; Mon, 9 Feb 2009 16:17:48 +0000 (UTC) (envelope-from dsh@wizard.volgograd.ru) Received: from dsh.falconknight.com (dsh [66.160.163.23]) by dsh.falconknight.com (Postfix) with ESMTP id B405B5BCB3EB; Mon, 9 Feb 2009 08:17:48 -0800 (PST) Received: from localhost (unknown [85.173.92.192]) by dsh.falconknight.com (Postfix) with ESMTPSA id 8711F5BCB359; Mon, 9 Feb 2009 08:17:46 -0800 (PST) Date: Mon, 9 Feb 2009 19:17:40 +0300 From: Denis Shaposhnikov To: Maksim Yevmenkin Message-ID: <20090209191740.548cffca@wizard.volgograd.ru> In-Reply-To: References: <20090209164820.00be4837@wizard.volgograd.ru> X-Mailer: Claws Mail 3.7.0 (GTK+ 2.14.7; i386-portbld-freebsd7.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-mobile@freebsd.org Subject: Re: RELENG7 on Samsung R510-FA0K (JFYI) X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2009 16:17:49 -0000 Hello, On Mon, 9 Feb 2009 07:43:24 -0800 Maksim Yevmenkin wrote: > > ugen1: > addr on uhub6 > did you load the driver? ng_ubt(4) for usb1 or usb_bluetooth_ng for > usb2. I've just tried it [dsh@localhost ~]% kldstat | tail 15 1 0xc093f000 5500 acpi_video.ko 16 2 0xc0945000 6a44c acpi.ko 17 1 0xc09b0000 4c70 atapicam.ko 18 1 0xc09b5000 8130 atapicd.ko 19 1 0xc09be000 2dec wlan_wep.ko 20 1 0xc09c1000 5208 wlan_scan_sta.ko 21 1 0xc53df000 b000 i915.ko 22 1 0xc53ea000 13000 drm.ko 23 1 0xc5e42000 7000 ng_ubt.ko 24 1 0xc5e49000 b000 netgraph.ko and I don't see anything about it in dmesg output. From owner-freebsd-mobile@FreeBSD.ORG Mon Feb 9 16:22:21 2009 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3A29C1065672 for ; Mon, 9 Feb 2009 16:22:21 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from rn-out-0910.google.com (rn-out-0910.google.com [64.233.170.185]) by mx1.freebsd.org (Postfix) with ESMTP id E60798FC08 for ; Mon, 9 Feb 2009 16:22:20 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: by rn-out-0910.google.com with SMTP id k32so1285822rnd.12 for ; Mon, 09 Feb 2009 08:22:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=5LNmRiaAmO6M/VJosGs06Djj++uTfTDecF4IlPr2G98=; b=bon0QIoj1hY5ZqSO7ZYqBZ9zcQxSTrkHgAqe11aN/5nz9q6bO8i8EOp6YT43etV6V3 MkZN3kA3Flr+owltyQ9Mx6S55JFnoucxwBkHhQYQnFjNXWfLLmtH46DLd5w6bjliTDFK iAqI4PSSRyxHHjqmhRt/+UYebN+nSFKQnc9Is= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=e2BhJm77rlBbK9yL3gIGAlmtlhIugH/CZvqDd0FqbrQxc52toFBfUtyJZaoxXBTSij xbLKfkGx2UwinBTY7OsKtHAQZeYaFO23XZsfgX3WdiZOfhTL3PNV+P+C42cSTDd8lF4S D1mw4MujBEEdeCUDkTGYlBEU5X64nYIF5PX+w= MIME-Version: 1.0 Received: by 10.150.211.4 with SMTP id j4mr912682ybg.233.1234196540334; Mon, 09 Feb 2009 08:22:20 -0800 (PST) In-Reply-To: <20090209191740.548cffca@wizard.volgograd.ru> References: <20090209164820.00be4837@wizard.volgograd.ru> <20090209191740.548cffca@wizard.volgograd.ru> Date: Mon, 9 Feb 2009 08:22:20 -0800 Message-ID: From: Maksim Yevmenkin To: Denis Shaposhnikov Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-mobile@freebsd.org Subject: Re: RELENG7 on Samsung R510-FA0K (JFYI) X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2009 16:22:21 -0000 2009/2/9 Denis Shaposhnikov : > Hello, > > On Mon, 9 Feb 2009 07:43:24 -0800 > Maksim Yevmenkin wrote: > >> > ugen1: > > addr on uhub6 > >> did you load the driver? ng_ubt(4) for usb1 or usb_bluetooth_ng for >> usb2. > > I've just tried it > > [dsh@localhost ~]% kldstat | tail > 15 1 0xc093f000 5500 acpi_video.ko > 16 2 0xc0945000 6a44c acpi.ko > 17 1 0xc09b0000 4c70 atapicam.ko > 18 1 0xc09b5000 8130 atapicd.ko > 19 1 0xc09be000 2dec wlan_wep.ko > 20 1 0xc09c1000 5208 wlan_scan_sta.ko > 21 1 0xc53df000 b000 i915.ko > 22 1 0xc53ea000 13000 drm.ko > 23 1 0xc5e42000 7000 ng_ubt.ko > 24 1 0xc5e49000 b000 netgraph.ko > > and I don't see anything about it in dmesg output. now you need to unplug/replug the device (or use off/on button if you have it on your laptop). you also can add ng_ubt_load="YES" to your loader.conf and reboot thanks, max From owner-freebsd-mobile@FreeBSD.ORG Mon Feb 9 16:27:01 2009 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B5D49106566B for ; Mon, 9 Feb 2009 16:27:01 +0000 (UTC) (envelope-from webmaster@kibab.com) Received: from mx0.deglitch.com (backbone.deglitch.com [IPv6:2001:16d8:fffb:4::abba]) by mx1.freebsd.org (Postfix) with ESMTP id 6D8038FC0C for ; Mon, 9 Feb 2009 16:27:01 +0000 (UTC) (envelope-from webmaster@kibab.com) Received: from kibab-nb.kibab.com (ppp83-237-168-127.pppoe.mtu-net.ru [83.237.168.127]) by mx0.deglitch.com (Postfix) with ESMTPA id 169228FC27; Mon, 9 Feb 2009 19:26:59 +0300 (MSK) Date: Mon, 9 Feb 2009 19:26:56 +0300 From: Ilya Bakulin To: Denis Shaposhnikov Message-Id: <20090209192656.e92af17c.webmaster@kibab.com> In-Reply-To: <20090209191740.548cffca@wizard.volgograd.ru> References: <20090209164820.00be4837@wizard.volgograd.ru> <20090209191740.548cffca@wizard.volgograd.ru> Organization: Deglitch Networks X-Mailer: Sylpheed 2.6.0 (GTK+ 2.14.7; i386-portbld-freebsd7.1) Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="PGP-SHA1"; boundary="Signature=_Mon__9_Feb_2009_19_26_56_+0300_bX89T.MXmJ37AwhB" Cc: freebsd-mobile@freebsd.org, Maksim Yevmenkin Subject: Re: RELENG7 on Samsung R510-FA0K (JFYI) X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2009 16:27:02 -0000 --Signature=_Mon__9_Feb_2009_19_26_56_+0300_bX89T.MXmJ37AwhB Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, 9 Feb 2009 19:17:40 +0300 Denis Shaposhnikov wrote: > and I don't see anything about it in dmesg output. Add the following line in /boot/loader.conf: ng_ubt_load=3D"YES" This driver should be loaded in kernel _before_ USB unumeration. > 7. Web camera seems don't work: > ugen0: 2.00/1.00, addr on uhub3 Class 239/2 is USB Video Class compliant web camera. UVC is not supported i= n FreeBSD [yet?]. > 9. ACPI seems to work, but I see strange messages on boot 1st thing you should do is updating your system BIOS. If it doesn't help, y= ou may try to repair AML code by hand (see FreeBSD handbook for further ins= tructions) or, at last, write on freebsd-acpi@ about this problem. --=20 Ilya Bakulin xmpp://kibab612@jabber.ru --Signature=_Mon__9_Feb_2009_19_26_56_+0300_bX89T.MXmJ37AwhB Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkmQWVUACgkQo9vlj1oadwhBtACg7DGC/i0rYS688SMdBXvDdpY3 TwUAmQGTl4oWU/LuWrU0NfR4yPEz/uhw =M6B8 -----END PGP SIGNATURE----- --Signature=_Mon__9_Feb_2009_19_26_56_+0300_bX89T.MXmJ37AwhB-- From owner-freebsd-mobile@FreeBSD.ORG Tue Feb 10 05:34:16 2009 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 00B6B106564A for ; Tue, 10 Feb 2009 05:34:16 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [220.233.188.227]) by mx1.freebsd.org (Postfix) with ESMTP id 3454B8FC17 for ; Tue, 10 Feb 2009 05:34:14 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id n1A5DOYD023470; Tue, 10 Feb 2009 16:13:24 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Tue, 10 Feb 2009 16:13:23 +1100 (EST) From: Ian Smith To: Bengt Ahlgren In-Reply-To: Message-ID: <20090210154047.N38905@sola.nimnet.asn.au> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-mobile@freebsd.org Subject: Re: Problems with ath at kern.hz=100 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Feb 2009 05:34:16 -0000 On Mon, 9 Feb 2009, Bengt Ahlgren wrote: > I was changing kern.hz to 100 on my IBM X40 (Pentium-M) laptop to see > whether that saves some battery, but ran into problems with ath not > working properly. At first I thought that my hardware was failing, > but changing hz back to 1000 solved the problem. I am running > 7.1-RELEASE-p1 and have the following Atheros chip: > > Feb 9 11:13:10 P142 kernel: ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) > Feb 9 11:13:10 P142 kernel: ath0: mem 0xd0200000-0xd020ffff irq 11 at device 2.0 on pci2 > Feb 9 11:13:10 P142 kernel: ath0: [ITHREAD] > Feb 9 11:13:10 P142 kernel: ath0: WARNING: using obsoleted if_watchdog interface > Feb 9 11:13:10 P142 kernel: ath0: Ethernet address: 00:05:4e:4e:1f:c7 > Feb 9 11:13:10 P142 kernel: ath0: mac 5.6 phy 4.1 5ghz radio 1.7 2ghz radio 2.3 There's an order of magnitude room to move between 100 and 1000 Hz. You could also try with maybe 250 or 500? What speed is your Pentium-M? Are you using powerd? If so, what minimum CPU freq does it drop back to (sysctl debug.cpufreq.lowest)? Sam has talked of a problem with ath (and maybe other) interrupt rates overwhelming slow CPUs to the extent that userland (ie powerd) doesn't get a look-in for a while, as I understand it. A fast CPU clocked back to less than say 300MHz IS a slow CPU, until powerd gets to crank it up. You might find that rc.conf setting economy_cx_lowest="LOW" can save you some battery, though this benefit seems somewhat processor-dependent. HTH, Ian > The symptom is that ath stops sending packets out. They seem to be > buffered somewhere. After a while it gets going again, albeit some > packets are lost. "A while" can be from 5 secs to a minute or so when > continously running a ping. In the below logs, a ping is started when > ath has stopped sending. > > "netstat -I ath0 1" reports that no packets are sent, but the byte > count is still incremented. When it gets going again, 18 packets are > sent, but the byte count does not reflect that (which perpaps is > logical): > > 1 0 56 0 0 0 0 > 0 0 0 0 0 0 0 > 0 0 0 0 0 98 0 > 1 0 56 0 0 98 0 > 1 0 56 0 0 98 0 > input (ath0) output > packets errs bytes packets errs bytes colls > 0 0 0 0 0 98 0 > 1 0 56 0 0 98 0 > 1 0 56 0 0 98 0 > 1 0 56 0 0 98 0 > 0 0 0 0 0 98 0 > 0 0 0 0 0 98 0 > 0 0 0 0 0 98 0 > 0 0 0 0 0 98 0 > 0 0 0 0 0 98 0 > 1 0 56 0 0 98 0 > 1 0 56 0 0 98 0 > 2 0 112 0 0 98 0 > 0 0 0 0 0 98 0 > 4 0 350 18 0 140 0 > 2 0 112 0 0 0 0 > 1 1 56 0 0 0 0 > 1 0 56 0 0 0 0 > 0 0 0 0 0 0 0 > ^C > > Here is a tcpdump of the same event: > > 18:40:59.025364 arp who-has 10.1.1.72 tell 10.1.7.250 > 18:41:00.049385 arp who-has 10.1.1.72 tell 10.1.7.250 > 18:41:00.868608 arp who-has 10.1.6.253 tell 10.1.7.250 > 18:41:01.073387 arp who-has 10.1.1.72 tell 10.1.7.250 > 18:41:02.761445 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 0, length 64 > 18:41:02.761456 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 1, length 64 > 18:41:02.761461 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 2, length 64 > 18:41:02.761466 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 3, length 64 > 18:41:02.761470 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 4, length 64 > 18:41:02.761474 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 5, length 64 > 18:41:02.761479 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 6, length 64 > 18:41:02.761483 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 7, length 64 > 18:41:02.761487 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 8, length 64 > 18:41:02.761492 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 9, length 64 > 18:41:02.761497 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 10, length 64 > 18:41:02.761502 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 11, length 64 > 18:41:02.761506 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 12, length 64 > 18:41:02.761510 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 13, length 64 > 18:41:02.761515 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 14, length 64 > 18:41:02.761519 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 15, length 64 > 18:41:02.761523 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 16, length 64 > 18:41:02.916556 arp who-has 10.1.1.107 tell 10.1.7.250 > 18:41:02.916579 arp reply 10.1.1.107 is-at 00:05:4e:4e:1f:c7 > 18:41:02.917707 IP 193.10.65.193 > 10.1.1.107: ICMP echo reply, id 63239, seq 14, length 64 > 18:41:02.917906 IP 193.10.65.193 > 10.1.1.107: ICMP echo reply, id 63239, seq 15, length 64 > 18:41:02.918187 IP 193.10.65.193 > 10.1.1.107: ICMP echo reply, id 63239, seq 16, length 64 > 18:41:03.531108 arp who-has 10.1.1.72 tell 10.1.7.250 > 18:41:04.350185 arp who-has 10.1.6.166 tell 10.1.7.250 > 18:41:04.554984 arp who-has 10.1.1.72 tell 10.1.7.250 > 18:41:05.578972 arp who-has 10.1.1.72 tell 10.1.7.250 > ^C > 289 packets captured > 289 packets received by filter > 0 packets dropped by kernel > > Any idea on what the problem can be, or how do debug this further? > > Regards, > > Bengt From owner-freebsd-mobile@FreeBSD.ORG Tue Feb 10 14:18:08 2009 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4A074106566C for ; Tue, 10 Feb 2009 14:18:08 +0000 (UTC) (envelope-from dsh@wizard.volgograd.ru) Received: from dsh.falconknight.com (dsh.falconknight.com [66.160.163.23]) by mx1.freebsd.org (Postfix) with ESMTP id 3161D8FC12 for ; Tue, 10 Feb 2009 14:18:08 +0000 (UTC) (envelope-from dsh@wizard.volgograd.ru) Received: from dsh.falconknight.com (dsh [66.160.163.23]) by dsh.falconknight.com (Postfix) with ESMTP id C5F895BCB679; Tue, 10 Feb 2009 06:18:07 -0800 (PST) Received: from localhost (unknown [85.173.92.192]) by dsh.falconknight.com (Postfix) with ESMTPSA id 3797B5BCB66F; Tue, 10 Feb 2009 06:18:04 -0800 (PST) Date: Tue, 10 Feb 2009 17:18:00 +0300 From: Denis Shaposhnikov To: Maksim Yevmenkin Message-ID: <20090210171800.0314597e@wizard.volgograd.ru> In-Reply-To: References: <20090209164820.00be4837@wizard.volgograd.ru> <20090209191740.548cffca@wizard.volgograd.ru> X-Mailer: Claws Mail 3.7.0 (GTK+ 2.14.7; i386-portbld-freebsd7.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-mobile@freebsd.org Subject: Re: RELENG7 on Samsung R510-FA0K (JFYI) X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Feb 2009 14:18:08 -0000 Hello, On Mon, 9 Feb 2009 08:22:20 -0800 Maksim Yevmenkin wrote: > have it on your laptop). you also can add > > ng_ubt_load="YES" > > to your loader.conf and reboot Thank you, it works now! ubt0: on uhub6 ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 ubt0: Interface 1 (alt.config 4) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=64; nframes=5, buffer size=320 From owner-freebsd-mobile@FreeBSD.ORG Tue Feb 10 16:08:49 2009 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DEAAA106566B for ; Tue, 10 Feb 2009 16:08:49 +0000 (UTC) (envelope-from bengta@P142.sics.se) Received: from sink.sics.se (sink.sics.se [193.10.64.88]) by mx1.freebsd.org (Postfix) with ESMTP id 6DFF28FC1A for ; Tue, 10 Feb 2009 16:08:49 +0000 (UTC) (envelope-from bengta@P142.sics.se) Received: from P142.sics.se (P142.sics.se [193.10.66.253]) by sink.sics.se (8.14.3/8.14.3) with ESMTP id n1AG7ltt015562 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 10 Feb 2009 17:07:49 +0100 (CET) (envelope-from bengta@P142.sics.se) Received: from P142.sics.se (localhost [127.0.0.1]) by P142.sics.se (8.14.3/8.14.3) with ESMTP id n1AG7V8X001283; Tue, 10 Feb 2009 17:07:31 +0100 (CET) (envelope-from bengta@P142.sics.se) Received: (from bengta@localhost) by P142.sics.se (8.14.3/8.14.3/Submit) id n1AG7Mde001281; Tue, 10 Feb 2009 17:07:22 +0100 (CET) (envelope-from bengta@P142.sics.se) To: Ian Smith From: Bengt Ahlgren In-Reply-To: <20090210154047.N38905@sola.nimnet.asn.au> (Ian Smith's message of "Tue\, 10 Feb 2009 16\:13\:23 +1100 \(EST\)") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (berkeley-unix) References: <20090210154047.N38905@sola.nimnet.asn.au> Date: Tue, 10 Feb 2009 17:07:22 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-mobile@freebsd.org Subject: Re: Problems with ath at kern.hz=100 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Feb 2009 16:08:50 -0000 Ian Smith writes: > On Mon, 9 Feb 2009, Bengt Ahlgren wrote: > > > I was changing kern.hz to 100 on my IBM X40 (Pentium-M) laptop to see > > whether that saves some battery, but ran into problems with ath not > > working properly. At first I thought that my hardware was failing, > > but changing hz back to 1000 solved the problem. I am running > > 7.1-RELEASE-p1 and have the following Atheros chip: > > > > Feb 9 11:13:10 P142 kernel: ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) > > Feb 9 11:13:10 P142 kernel: ath0: mem 0xd0200000-0xd020ffff irq 11 at device 2.0 on pci2 > > Feb 9 11:13:10 P142 kernel: ath0: [ITHREAD] > > Feb 9 11:13:10 P142 kernel: ath0: WARNING: using obsoleted if_watchdog interface > > Feb 9 11:13:10 P142 kernel: ath0: Ethernet address: 00:05:4e:4e:1f:c7 > > Feb 9 11:13:10 P142 kernel: ath0: mac 5.6 phy 4.1 5ghz radio 1.7 2ghz radio 2.3 > > There's an order of magnitude room to move between 100 and 1000 Hz. > You could also try with maybe 250 or 500? I have been running with hz=250 for a while now without the problem occuring. > What speed is your Pentium-M? Are you using powerd? If so, what > minimum CPU freq does it drop back to (sysctl debug.cpufreq.lowest)? It is a 1200MHz. I have debug.cpufreq.lowest=600 in order to only use EST. I ran for a while at 1200MHz with no powerd and ath still stopped sending. > Sam has talked of a problem with ath (and maybe other) interrupt rates > overwhelming slow CPUs to the extent that userland (ie powerd) doesn't > get a look-in for a while, as I understand it. A fast CPU clocked back > to less than say 300MHz IS a slow CPU, until powerd gets to crank it up. > > You might find that rc.conf setting economy_cx_lowest="LOW" can save you > some battery, though this benefit seems somewhat processor-dependent. I tried with dev.cpu.0.cx_lowest=C1 (at 1200MHz), but with no difference - the problem is still there. Bengt From owner-freebsd-mobile@FreeBSD.ORG Tue Feb 10 16:10:46 2009 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 249EE106566C for ; Tue, 10 Feb 2009 16:10:46 +0000 (UTC) (envelope-from bengta@P142.sics.se) Received: from sink.sics.se (sink.sics.se [193.10.64.88]) by mx1.freebsd.org (Postfix) with ESMTP id A6F9A8FC1E for ; Tue, 10 Feb 2009 16:10:45 +0000 (UTC) (envelope-from bengta@P142.sics.se) Received: from P142.sics.se (P142.sics.se [193.10.66.253]) by sink.sics.se (8.14.3/8.14.3) with ESMTP id n1AG9k3x015565 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 10 Feb 2009 17:09:47 +0100 (CET) (envelope-from bengta@P142.sics.se) Received: from P142.sics.se (localhost [127.0.0.1]) by P142.sics.se (8.14.3/8.14.3) with ESMTP id n1AG9UwN001302; Tue, 10 Feb 2009 17:09:30 +0100 (CET) (envelope-from bengta@P142.sics.se) Received: (from bengta@localhost) by P142.sics.se (8.14.3/8.14.3/Submit) id n1AG9UJp001301; Tue, 10 Feb 2009 17:09:30 +0100 (CET) (envelope-from bengta@P142.sics.se) To: Ian Smith From: Bengt Ahlgren In-Reply-To: (Bengt Ahlgren's message of "Tue\, 10 Feb 2009 17\:07\:22 +0100") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (berkeley-unix) References: <20090210154047.N38905@sola.nimnet.asn.au> Date: Tue, 10 Feb 2009 17:09:30 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-mobile@freebsd.org Subject: Re: Problems with ath at kern.hz=100 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Feb 2009 16:10:46 -0000 Bengt Ahlgren writes: > Ian Smith writes: > >> On Mon, 9 Feb 2009, Bengt Ahlgren wrote: >> >> > I was changing kern.hz to 100 on my IBM X40 (Pentium-M) laptop to see >> > whether that saves some battery, but ran into problems with ath not >> > working properly. At first I thought that my hardware was failing, >> > but changing hz back to 1000 solved the problem. I am running >> > 7.1-RELEASE-p1 and have the following Atheros chip: >> > >> > Feb 9 11:13:10 P142 kernel: ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) >> > Feb 9 11:13:10 P142 kernel: ath0: mem 0xd0200000-0xd020ffff irq 11 at device 2.0 on pci2 >> > Feb 9 11:13:10 P142 kernel: ath0: [ITHREAD] >> > Feb 9 11:13:10 P142 kernel: ath0: WARNING: using obsoleted if_watchdog interface >> > Feb 9 11:13:10 P142 kernel: ath0: Ethernet address: 00:05:4e:4e:1f:c7 >> > Feb 9 11:13:10 P142 kernel: ath0: mac 5.6 phy 4.1 5ghz radio 1.7 2ghz radio 2.3 >> >> There's an order of magnitude room to move between 100 and 1000 Hz. >> You could also try with maybe 250 or 500? > > I have been running with hz=250 for a while now without the problem > occuring. Just when sending this off, it also happened with hz=250. Bengt From owner-freebsd-mobile@FreeBSD.ORG Tue Feb 10 16:45:28 2009 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B6FDE1065677 for ; Tue, 10 Feb 2009 16:45:28 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 7425A8FC13 for ; Tue, 10 Feb 2009 16:45:28 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id n1AGUOKW027500 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 10 Feb 2009 08:30:24 -0800 (PST) (envelope-from sam@freebsd.org) Message-ID: <4991ABA0.4050300@freebsd.org> Date: Tue, 10 Feb 2009 08:30:24 -0800 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.18 (X11/20081209) MIME-Version: 1.0 To: Ian Smith References: <20090210154047.N38905@sola.nimnet.asn.au> In-Reply-To: <20090210154047.N38905@sola.nimnet.asn.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC-sonic.net-Metrics: ebb.errno.com; whitelist Cc: freebsd-mobile@freebsd.org Subject: Re: Problems with ath at kern.hz=100 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Feb 2009 16:45:29 -0000 Ian Smith wrote: > On Mon, 9 Feb 2009, Bengt Ahlgren wrote: > > > I was changing kern.hz to 100 on my IBM X40 (Pentium-M) laptop to see > > whether that saves some battery, but ran into problems with ath not > > working properly. At first I thought that my hardware was failing, > > but changing hz back to 1000 solved the problem. I am running > > 7.1-RELEASE-p1 and have the following Atheros chip: > > > > Feb 9 11:13:10 P142 kernel: ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) > > Feb 9 11:13:10 P142 kernel: ath0: mem 0xd0200000-0xd020ffff irq 11 at device 2.0 on pci2 > > Feb 9 11:13:10 P142 kernel: ath0: [ITHREAD] > > Feb 9 11:13:10 P142 kernel: ath0: WARNING: using obsoleted if_watchdog interface > > Feb 9 11:13:10 P142 kernel: ath0: Ethernet address: 00:05:4e:4e:1f:c7 > > Feb 9 11:13:10 P142 kernel: ath0: mac 5.6 phy 4.1 5ghz radio 1.7 2ghz radio 2.3 > > There's an order of magnitude room to move between 100 and 1000 Hz. > You could also try with maybe 250 or 500? > > What speed is your Pentium-M? Are you using powerd? If so, what > minimum CPU freq does it drop back to (sysctl debug.cpufreq.lowest)? > > Sam has talked of a problem with ath (and maybe other) interrupt rates > overwhelming slow CPUs to the extent that userland (ie powerd) doesn't > get a look-in for a while, as I understand it. A fast CPU clocked back > to less than say 300MHz IS a slow CPU, until powerd gets to crank it up. > If powerd starvation were happening you'd see livelock not slow traffic. The problem was that MIB overflow interrupts from the card were pounding the host but since the cpu clock was lowered they were not serviced fast enough. FWIW I believe the MIB interrupt storm issue is fixed in head. I posted a patch to stable@ to enable backmerge of the necessary code but received ~zero feedback in >1 month so RELENG_7 will continue to rot w/ old code. > You might find that rc.conf setting economy_cx_lowest="LOW" can save you > some battery, though this benefit seems somewhat processor-dependent. > > HTH, Ian > > > > The symptom is that ath stops sending packets out. They seem to be > > buffered somewhere. After a while it gets going again, albeit some > > packets are lost. "A while" can be from 5 secs to a minute or so when > > continously running a ping. In the below logs, a ping is started when > > ath has stopped sending. > > > > > "netstat -I ath0 1" reports that no packets are sent, but the byte > > count is still incremented. When it gets going again, 18 packets are > > sent, but the byte count does not reflect that (which perpaps is > > logical): > > > > 1 0 56 0 0 0 0 > > 0 0 0 0 0 0 0 > > 0 0 0 0 0 98 0 > > 1 0 56 0 0 98 0 > > 1 0 56 0 0 98 0 > > input (ath0) output > > packets errs bytes packets errs bytes colls > > 0 0 0 0 0 98 0 > > 1 0 56 0 0 98 0 > > 1 0 56 0 0 98 0 > > 1 0 56 0 0 98 0 > > 0 0 0 0 0 98 0 > > 0 0 0 0 0 98 0 > > 0 0 0 0 0 98 0 > > 0 0 0 0 0 98 0 > > 0 0 0 0 0 98 0 > > 1 0 56 0 0 98 0 > > 1 0 56 0 0 98 0 > > 2 0 112 0 0 98 0 > > 0 0 0 0 0 98 0 > > 4 0 350 18 0 140 0 > > 2 0 112 0 0 0 0 > > 1 1 56 0 0 0 0 > > 1 0 56 0 0 0 0 > > 0 0 0 0 0 0 0 > > ^C > > > > Here is a tcpdump of the same event: > > > > 18:40:59.025364 arp who-has 10.1.1.72 tell 10.1.7.250 > > 18:41:00.049385 arp who-has 10.1.1.72 tell 10.1.7.250 > > 18:41:00.868608 arp who-has 10.1.6.253 tell 10.1.7.250 > > 18:41:01.073387 arp who-has 10.1.1.72 tell 10.1.7.250 > > 18:41:02.761445 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 0, length 64 > > 18:41:02.761456 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 1, length 64 > > 18:41:02.761461 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 2, length 64 > > 18:41:02.761466 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 3, length 64 > > 18:41:02.761470 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 4, length 64 > > 18:41:02.761474 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 5, length 64 > > 18:41:02.761479 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 6, length 64 > > 18:41:02.761483 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 7, length 64 > > 18:41:02.761487 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 8, length 64 > > 18:41:02.761492 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 9, length 64 > > 18:41:02.761497 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 10, length 64 > > 18:41:02.761502 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 11, length 64 > > 18:41:02.761506 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 12, length 64 > > 18:41:02.761510 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 13, length 64 > > 18:41:02.761515 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 14, length 64 > > 18:41:02.761519 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 15, length 64 > > 18:41:02.761523 IP 10.1.1.107 > 193.10.65.193: ICMP echo request, id 63239, seq 16, length 64 > > 18:41:02.916556 arp who-has 10.1.1.107 tell 10.1.7.250 > > 18:41:02.916579 arp reply 10.1.1.107 is-at 00:05:4e:4e:1f:c7 > > 18:41:02.917707 IP 193.10.65.193 > 10.1.1.107: ICMP echo reply, id 63239, seq 14, length 64 > > 18:41:02.917906 IP 193.10.65.193 > 10.1.1.107: ICMP echo reply, id 63239, seq 15, length 64 > > 18:41:02.918187 IP 193.10.65.193 > 10.1.1.107: ICMP echo reply, id 63239, seq 16, length 64 > > 18:41:03.531108 arp who-has 10.1.1.72 tell 10.1.7.250 > > 18:41:04.350185 arp who-has 10.1.6.166 tell 10.1.7.250 > > 18:41:04.554984 arp who-has 10.1.1.72 tell 10.1.7.250 > > 18:41:05.578972 arp who-has 10.1.1.72 tell 10.1.7.250 > > ^C > > 289 packets captured > > 289 packets received by filter > > 0 packets dropped by kernel > > > > Any idea on what the problem can be, or how do debug this further? > > You can use tcpdump to monitor traffic at multiple levels in the hierarchy: tcpdump -i ath0 -n # tap at 802.3 level tcpdump -i ath0 -n -y IEEE802_11 # tap at 802.11 level tcpdump -i ath0 -n -y IEEE802_11_RADIO # tap at driver level and/or you can check statistics using athstats and wlanstats or you can turn on debugging msgs in net80211 or the ath driver using wlandebug and athdebug. Some of these may require you to build your kernel w/ debug options (e.g. ATH_DEBUG). Sam From owner-freebsd-mobile@FreeBSD.ORG Tue Feb 10 17:40:18 2009 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B00361065672 for ; Tue, 10 Feb 2009 17:40:18 +0000 (UTC) (envelope-from bengta@P142.sics.se) Received: from sink.sics.se (sink.sics.se [193.10.64.88]) by mx1.freebsd.org (Postfix) with ESMTP id 28C5D8FC21 for ; Tue, 10 Feb 2009 17:40:17 +0000 (UTC) (envelope-from bengta@P142.sics.se) Received: from P142.sics.se (P142.sics.se [193.10.66.253]) by sink.sics.se (8.14.3/8.14.3) with ESMTP id n1AHdHdi015811 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 10 Feb 2009 18:39:18 +0100 (CET) (envelope-from bengta@P142.sics.se) Received: from P142.sics.se (localhost [127.0.0.1]) by P142.sics.se (8.14.3/8.14.3) with ESMTP id n1AHg5DE001323; Tue, 10 Feb 2009 18:42:05 +0100 (CET) (envelope-from bengta@P142.sics.se) Received: (from bengta@localhost) by P142.sics.se (8.14.3/8.14.3/Submit) id n1AHg3iI001322; Tue, 10 Feb 2009 18:42:03 +0100 (CET) (envelope-from bengta@P142.sics.se) To: Sam Leffler From: Bengt Ahlgren In-Reply-To: <4991ABA0.4050300@freebsd.org> (Sam Leffler's message of "Tue\, 10 Feb 2009 08\:30\:24 -0800") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (berkeley-unix) References: <20090210154047.N38905@sola.nimnet.asn.au> <4991ABA0.4050300@freebsd.org> Date: Tue, 10 Feb 2009 18:42:03 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Ian Smith , freebsd-mobile@freebsd.org Subject: Re: Problems with ath at kern.hz=100 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Feb 2009 17:40:19 -0000 Sam Leffler writes: > Ian Smith wrote: >> On Mon, 9 Feb 2009, Bengt Ahlgren wrote: [...] >> Sam has talked of a problem with ath (and maybe other) interrupt >> rates overwhelming slow CPUs to the extent that userland (ie powerd) >> doesn't get a look-in for a while, as I understand it. A fast CPU >> clocked back to less than say 300MHz IS a slow CPU, until powerd >> gets to crank it up. >> > > If powerd starvation were happening you'd see livelock not slow > traffic. The problem was that MIB overflow interrupts from the card > were pounding the host but since the cpu clock was lowered they were > not serviced fast enough. > > FWIW I believe the MIB interrupt storm issue is fixed in head. I > posted a patch to stable@ to enable backmerge of the necessary code > but received ~zero feedback in >1 month so RELENG_7 will continue to > rot w/ old code. The system was not livelocked - it was fully working except for ath not sending out packets. I can however try the patch if you think it is worthwhile. [...] >> > > Any idea on what the problem can be, or how do debug this >> further? >> >> > > You can use tcpdump to monitor traffic at multiple levels in the hierarchy: > > tcpdump -i ath0 -n # tap at 802.3 level > tcpdump -i ath0 -n -y IEEE802_11 # tap at 802.11 level > tcpdump -i ath0 -n -y IEEE802_11_RADIO # tap at driver level > > and/or you can check statistics using athstats and wlanstats or you > can turn on debugging msgs in net80211 or the ath driver using > wlandebug and athdebug. Some of these may require you to build your > kernel w/ debug options (e.g. ATH_DEBUG). Does the following mean anything to you? I did athdebug watchdog+xmit+calibrate+xmit_proc - more or less random choice, since I don't know what it really means. I see a lot of those ath_calibrate:s with low "x" in "next +x" when it is not sending. When it is operating normally, it mostly says "next +30" with "tries 0". But there is no strict correlation, it can sometimes send packets even when it says "!iqCalDone". ath_tx_dmasetup: m 0xc37d4a00 len 178 TODS 00:05:4e:4e:1f:c7->00:14:4f:0f:ae:f6(00:13:1a:47:7a:33) data 54M 0801 2c00 0013 1a47 7a33 0005 4e4e 1fc7 0014 4f0f aef6 f007 aaaa 0300 0000 0800 4500 0092 0128 4000 4006 3426 c10a 42fd c10a 4006 f506 008f 3433 0198 3326 9ce6 5018 ffff c1f2 0000 1703 0100 200d 2e0f 8857 2590 18d0 745b ce33 3874 4089 c851 5aab e5de ef81 8a43 ab98 ad4b 8b17 0301 0040 6b34 58a9 a0e4 b41b 9868 fa90 c69c 95a3 dc6c 99f9 c942 1bf4 219d 5b5f 5711 174d a810 c6d8 2dff 0c88 bb42 c566 6eae 8b7c acff bba3 847b 09d0 a77a e597 fc87 a6c8 ath_tx_handoff: 0: 00000000 014cea3c c12200b6 0000a0b2 0004006c 01e0000c ath_tx_handoff: link[1](0xdecd8900)=0x14b1bcc0 (0xdecd8cc0) depth 2 ath_tx_processq: tx queue 1 head 0x14b1bcc0 link 0xdecd8cc0 ath_tx_dmasetup: m 0xc37d7800 len 162 TODS 00:05:4e:4e:1f:c7->00:14:4f:0f:ae:f6(00:13:1a:47:7a:33) data 54M 0801 2c00 0013 1a47 7a33 0005 4e4e 1fc7 0014 4f0f aef6 0008 aaaa 0300 0000 0800 4500 0082 0129 4000 4006 3435 c10a 42fd c10a 4006 f506 008f 3433 0202 3326 9d4b 5018 ffff 24fa 0000 1703 0100 206c 06b7 7a5e 1427 c691 772f b923 07be 4c94 4fa0 80e8 4130 5192 e751 970e 8092 c617 0301 0030 0124 d75d c26b 0a82 13ce 8044 73e8 2cb1 74ab d1f9 ce01 5aca 116d f95c 79db 058e 6f58 c86d 51d2 31b9 345d 02b4 836e fb26 ath_tx_handoff: 0: 00000000 014d183c c12200a6 0000a0a2 0004006c 01e0000c ath_tx_handoff: link[1](0xdecd8cc0)=0x14b1c080 (0xdecd9080) depth 2 ath_tx_processq: tx queue 1 head 0x14b1c080 link 0xdecd9080 ath_tx_dmasetup: m 0xc37d5200 len 162 TODS 00:05:4e:4e:1f:c7->00:14:4f:0f:ae:f6(00:13:1a:47:7a:33) data 54M 0801 2c00 0013 1a47 7a33 0005 4e4e 1fc7 0014 4f0f aef6 1008 aaaa 0300 0000 0800 4500 0082 012a 4000 4006 3434 c10a 42fd c10a 4006 f506 008f 3433 025c 3326 9db0 5018 ffff 0df1 0000 1703 0100 20bf 5e4c fea5 c3d7 37af 29f1 3071 9791 6e7d 5cad 559b 00aa 204b e704 eea9 58b4 8017 0301 0030 f92c e0f3 3511 5618 19db fb48 5408 86d2 365b 3a0a ca5a 86c0 cd67 3b33 1333 3a73 ed6a 4410 491a e454 5901 e1b3 4e33 d3f8 ath_tx_handoff: 0: 00000000 014cf23c c12200a6 0000a0a2 0004006c 01e0000c ath_tx_handoff: link[1](0xdecd9080)=0x14b1c440 (0xdecd9440) depth 2 ath_tx_processq: tx queue 1 head 0x14b1c440 link 0xdecd9440 ath_tx_dmasetup: m 0xc37d4200 len 109 TODS 00:05:4e:4e:1f:c7->00:14:4f:0f:ae:f6(00:13:1a:47:7a:33) data 54M 0801 2c00 0013 1a47 7a33 0005 4e4e 1fc7 0014 4f0f aef6 2008 aaaa 0300 0000 0800 4500 004d 012b 4000 4006 3468 c10a 42fd c10a 4006 f506 008f 3433 02b6 3326 9e05 5018 ffff a6cb 0000 1503 0100 20c4 db33 8cb3 dbfd 8f42 a0da 812c 1415 7ccd 8031 ada1 d5b3 48f8 45d4 ad00 c2eb 47 ath_tx_handoff: 0: 00000000 014ce23c c1220071 0000a06d 00040064 01e0000c ath_tx_handoff: link[1](0xdecd9440)=0x14b1c300 (0xdecd9300) depth 2 ath_tx_dmasetup: m 0xc37d3800 len 72 TODS 00:05:4e:4e:1f:c7->00:14:4f:0f:ae:f6(00:13:1a:47:7a:33) data 54M 0801 2c00 0013 1a47 7a33 0005 4e4e 1fc7 0014 4f0f aef6 3008 aaaa 0300 0000 0800 4500 0028 012c 4000 4006 348c c10a 42fd c10a 4006 f506 008f 3433 02db 3326 9e05 5011 ffff aceb 0000 ath_tx_handoff: 0: 00000000 014cd83c c122004c 0000a048 0004005c 01e0000c ath_tx_handoff: link[1](0xdecd9300)=0x14b1ca80 (0xdecd9a80) depth 3 ath_tx_processq: tx queue 1 head 0x14b1ca80 link 0xdecd9a80 ath_calibrate: next +2 (!iqCalDone tries 2) ath_calibrate: next +2 (!iqCalDone tries 3) ath_calibrate: next +2 (!iqCalDone tries 4) ath_calibrate: next +4 (!iqCalDone tries 0) ath_calibrate: next +4 (!iqCalDone tries 1) ath_calibrate: next +4 (!iqCalDone tries 2) ath_calibrate: next +4 (!iqCalDone tries 3) After a while I also saw some: ath0: [00:13:1a:47:7a:33] pwr save q overflow, drops 19 (size 50) athstats says: [root@P142 ~]# athstats 306 data frames received 335 data frames transmit 336 long on-chip tx retries 48 tx failed 'cuz too many retries 48M current transmit rate 9 beacon miss interrupts 107 tx management frames 199 tx frames discarded prior to association 78 tx frames with no ack marked 407 tx frames with short preamble 259 tx frames with 11g protection 11791 rx failed 'cuz of bad CRC 201147 rx failed 'cuz of PHY err 116925 OFDM timing 1 OFDM restart 84126 CCK timing 95 CCK restart 243 periodic calibrations 31 avg recv rssi -97 rx noise floor 4997 switched default/rx antenna Antenna profile: [1] tx 363 rx 53933 [2] tx 14 rx 18762 and ifconfig -v: ath0: flags=8847 metric 0 mtu 1500 ether 00:05:4e:4e:1f:c7 inet 193.10.66.253 netmask 0xfffffc00 broadcast 193.10.67.255 media: IEEE 802.11 Wireless Ethernet autoselect (OFDM/48Mbps) status: associated ssid SICS channel 11 (2462 Mhz 11g) bssid 00:13:1a:47:7a:33 authmode OPEN privacy OFF deftxkey UNDEF powersavemode OFF powersavesleep 100 txpower 31.5 txpowmax 17.0 rtsthreshold 2346 fragthreshold 2346 bmiss 7 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi11a 7 roam:rate11a 12 roam:rssi11b 7 roam:rate11b 1 roam:rssi11g 7 roam:rate11g 5 -pureg protmode CTS -ht -htcompat -ampdu ampdulimit 8k ampdudensity - -amsdu -shortgi htprotmode RTSCTS -puren -wme burst -ff -dturbo roaming AUTO bintval 100 Bengt From owner-freebsd-mobile@FreeBSD.ORG Tue Feb 10 19:53:04 2009 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CA89C1065670 for ; Tue, 10 Feb 2009 19:53:04 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 8612A8FC23 for ; Tue, 10 Feb 2009 19:53:04 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id n1AJr3sP028610 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 10 Feb 2009 11:53:04 -0800 (PST) (envelope-from sam@freebsd.org) Message-ID: <4991DB1F.7060809@freebsd.org> Date: Tue, 10 Feb 2009 11:53:03 -0800 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.18 (X11/20081209) MIME-Version: 1.0 To: Bengt Ahlgren References: <20090210154047.N38905@sola.nimnet.asn.au> <4991ABA0.4050300@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC-sonic.net-Metrics: ebb.errno.com; whitelist Cc: Ian Smith , freebsd-mobile@freebsd.org Subject: Re: Problems with ath at kern.hz=100 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Feb 2009 19:53:05 -0000 Bengt Ahlgren wrote: > Sam Leffler writes: > > >> Ian Smith wrote: >> >>> On Mon, 9 Feb 2009, Bengt Ahlgren wrote: >>> > > [...] > > >>> Sam has talked of a problem with ath (and maybe other) interrupt >>> rates overwhelming slow CPUs to the extent that userland (ie powerd) >>> doesn't get a look-in for a while, as I understand it. A fast CPU >>> clocked back to less than say 300MHz IS a slow CPU, until powerd >>> gets to crank it up. >>> >>> >> If powerd starvation were happening you'd see livelock not slow >> traffic. The problem was that MIB overflow interrupts from the card >> were pounding the host but since the cpu clock was lowered they were >> not serviced fast enough. >> >> FWIW I believe the MIB interrupt storm issue is fixed in head. I >> posted a patch to stable@ to enable backmerge of the necessary code >> but received ~zero feedback in >1 month so RELENG_7 will continue to >> rot w/ old code. >> > > The system was not livelocked - it was fully working except for ath > not sending out packets. I can however try the patch if you think it > is worthwhile. > > [...] > > >>> > > Any idea on what the problem can be, or how do debug this >>> further? >>> >>> >>> >> You can use tcpdump to monitor traffic at multiple levels in the hierarchy: >> >> tcpdump -i ath0 -n # tap at 802.3 level >> tcpdump -i ath0 -n -y IEEE802_11 # tap at 802.11 level >> tcpdump -i ath0 -n -y IEEE802_11_RADIO # tap at driver level >> >> and/or you can check statistics using athstats and wlanstats or you >> can turn on debugging msgs in net80211 or the ath driver using >> wlandebug and athdebug. Some of these may require you to build your >> kernel w/ debug options (e.g. ATH_DEBUG). >> > > Does the following mean anything to you? I did athdebug > watchdog+xmit+calibrate+xmit_proc - more or less random choice, since > I don't know what it really means. I see a lot of those > ath_calibrate:s with low "x" in "next +x" when it is not sending. > When it is operating normally, it mostly says "next +30" with "tries > 0". But there is no strict correlation, it can sometimes send packets > even when it says "!iqCalDone". > Typically you want to work from the top down; turning on athdebug gives you info at the lowest parts of the system which rarely is meaningful unless you've already narrowed down a problem. > ath_tx_dmasetup: m 0xc37d4a00 len 178 > TODS 00:05:4e:4e:1f:c7->00:14:4f:0f:ae:f6(00:13:1a:47:7a:33) data 54M > 0801 2c00 0013 1a47 7a33 0005 4e4e 1fc7 0014 4f0f aef6 f007 aaaa 0300 0000 0800 4500 0092 0128 4000 4006 3426 c10a 42fd c10a 4006 f506 008f 3433 0198 3326 9ce6 5018 ffff c1f2 0000 1703 0100 200d 2e0f 8857 2590 18d0 745b ce33 3874 4089 c851 5aab e5de ef81 8a43 ab98 ad4b 8b17 0301 0040 6b34 58a9 a0e4 b41b 9868 fa90 c69c 95a3 dc6c 99f9 c942 1bf4 219d 5b5f 5711 174d a810 c6d8 2dff 0c88 bb42 c566 6eae 8b7c acff bba3 847b 09d0 a77a e597 fc87 a6c8 > ath_tx_handoff: 0: 00000000 014cea3c c12200b6 0000a0b2 0004006c 01e0000c > ath_tx_handoff: link[1](0xdecd8900)=0x14b1bcc0 (0xdecd8cc0) depth 2 > ath_tx_processq: tx queue 1 head 0x14b1bcc0 link 0xdecd8cc0 > ath_tx_dmasetup: m 0xc37d7800 len 162 > TODS 00:05:4e:4e:1f:c7->00:14:4f:0f:ae:f6(00:13:1a:47:7a:33) data 54M > 0801 2c00 0013 1a47 7a33 0005 4e4e 1fc7 0014 4f0f aef6 0008 aaaa 0300 0000 0800 4500 0082 0129 4000 4006 3435 c10a 42fd c10a 4006 f506 008f 3433 0202 3326 9d4b 5018 ffff 24fa 0000 1703 0100 206c 06b7 7a5e 1427 c691 772f b923 07be 4c94 4fa0 80e8 4130 5192 e751 970e 8092 c617 0301 0030 0124 d75d c26b 0a82 13ce 8044 73e8 2cb1 74ab d1f9 ce01 5aca 116d f95c 79db 058e 6f58 c86d 51d2 31b9 345d 02b4 836e fb26 > ath_tx_handoff: 0: 00000000 014d183c c12200a6 0000a0a2 0004006c 01e0000c > ath_tx_handoff: link[1](0xdecd8cc0)=0x14b1c080 (0xdecd9080) depth 2 > ath_tx_processq: tx queue 1 head 0x14b1c080 link 0xdecd9080 > ath_tx_dmasetup: m 0xc37d5200 len 162 > TODS 00:05:4e:4e:1f:c7->00:14:4f:0f:ae:f6(00:13:1a:47:7a:33) data 54M > 0801 2c00 0013 1a47 7a33 0005 4e4e 1fc7 0014 4f0f aef6 1008 aaaa 0300 0000 0800 4500 0082 012a 4000 4006 3434 c10a 42fd c10a 4006 f506 008f 3433 025c 3326 9db0 5018 ffff 0df1 0000 1703 0100 20bf 5e4c fea5 c3d7 37af 29f1 3071 9791 6e7d 5cad 559b 00aa 204b e704 eea9 58b4 8017 0301 0030 f92c e0f3 3511 5618 19db fb48 5408 86d2 365b 3a0a ca5a 86c0 cd67 3b33 1333 3a73 ed6a 4410 491a e454 5901 e1b3 4e33 d3f8 > ath_tx_handoff: 0: 00000000 014cf23c c12200a6 0000a0a2 0004006c 01e0000c > ath_tx_handoff: link[1](0xdecd9080)=0x14b1c440 (0xdecd9440) depth 2 > ath_tx_processq: tx queue 1 head 0x14b1c440 link 0xdecd9440 > ath_tx_dmasetup: m 0xc37d4200 len 109 > TODS 00:05:4e:4e:1f:c7->00:14:4f:0f:ae:f6(00:13:1a:47:7a:33) data 54M > 0801 2c00 0013 1a47 7a33 0005 4e4e 1fc7 0014 4f0f aef6 2008 aaaa 0300 0000 0800 4500 004d 012b 4000 4006 3468 c10a 42fd c10a 4006 f506 008f 3433 02b6 3326 9e05 5018 ffff a6cb 0000 1503 0100 20c4 db33 8cb3 dbfd 8f42 a0da 812c 1415 7ccd 8031 ada1 d5b3 48f8 45d4 ad00 c2eb 47 > ath_tx_handoff: 0: 00000000 014ce23c c1220071 0000a06d 00040064 01e0000c > ath_tx_handoff: link[1](0xdecd9440)=0x14b1c300 (0xdecd9300) depth 2 > ath_tx_dmasetup: m 0xc37d3800 len 72 > TODS 00:05:4e:4e:1f:c7->00:14:4f:0f:ae:f6(00:13:1a:47:7a:33) data 54M > 0801 2c00 0013 1a47 7a33 0005 4e4e 1fc7 0014 4f0f aef6 3008 aaaa 0300 0000 0800 4500 0028 012c 4000 4006 348c c10a 42fd c10a 4006 f506 008f 3433 02db 3326 9e05 5011 ffff aceb 0000 > ath_tx_handoff: 0: 00000000 014cd83c c122004c 0000a048 0004005c 01e0000c > ath_tx_handoff: link[1](0xdecd9300)=0x14b1ca80 (0xdecd9a80) depth 3 > ath_tx_processq: tx queue 1 head 0x14b1ca80 link 0xdecd9a80 > ath_calibrate: next +2 (!iqCalDone tries 2) > ath_calibrate: next +2 (!iqCalDone tries 3) > ath_calibrate: next +2 (!iqCalDone tries 4) > ath_calibrate: next +4 (!iqCalDone tries 0) > ath_calibrate: next +4 (!iqCalDone tries 1) > ath_calibrate: next +4 (!iqCalDone tries 2) > ath_calibrate: next +4 (!iqCalDone tries 3) > > After a while I also saw some: > > ath0: [00:13:1a:47:7a:33] pwr save q overflow, drops 19 (size 50) > Er, did you ever say you were operating in ap mode? > athstats says: > > [root@P142 ~]# athstats > 306 data frames received > 335 data frames transmit > 336 long on-chip tx retries > 48 tx failed 'cuz too many retries > 48M current transmit rate > 9 beacon miss interrupts > 107 tx management frames > 199 tx frames discarded prior to association > 78 tx frames with no ack marked > 407 tx frames with short preamble > 259 tx frames with 11g protection > 11791 rx failed 'cuz of bad CRC > 201147 rx failed 'cuz of PHY err > 116925 OFDM timing > 1 OFDM restart > 84126 CCK timing > 95 CCK restart > 243 periodic calibrations > 31 avg recv rssi > -97 rx noise floor > 4997 switched default/rx antenna > Antenna profile: > [1] tx 363 rx 53933 > [2] tx 14 rx 18762 > > and ifconfig -v: > > ath0: flags=8847 metric 0 mtu 1500 > ether 00:05:4e:4e:1f:c7 > inet 193.10.66.253 netmask 0xfffffc00 broadcast 193.10.67.255 > media: IEEE 802.11 Wireless Ethernet autoselect (OFDM/48Mbps) > status: associated > ssid SICS channel 11 (2462 Mhz 11g) bssid 00:13:1a:47:7a:33 > authmode OPEN privacy OFF deftxkey UNDEF powersavemode OFF > powersavesleep 100 txpower 31.5 txpowmax 17.0 rtsthreshold 2346 > fragthreshold 2346 bmiss 7 scanvalid 60 bgscan bgscanintvl 300 > bgscanidle 250 roam:rssi11a 7 roam:rate11a 12 roam:rssi11b 7 > roam:rate11b 1 roam:rssi11g 7 roam:rate11g 5 -pureg protmode CTS -ht > -htcompat -ampdu ampdulimit 8k ampdudensity - -amsdu -shortgi > htprotmode RTSCTS -puren -wme burst -ff -dturbo roaming AUTO > bintval 100 > > You've removed all the context of the original problem; I can't recall what you were trying to fix. The ps q drops might be caused by a bug that was fixed (I think in RELENG_7). I don't see what version of code you're running so can't tell. Sam From owner-freebsd-mobile@FreeBSD.ORG Wed Feb 11 13:47:48 2009 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 82C0F106564A for ; Wed, 11 Feb 2009 13:47:48 +0000 (UTC) (envelope-from lists@braisel.com) Received: from jehuda.cx2.org (jehuda.cx2.org [85.214.71.246]) by mx1.freebsd.org (Postfix) with ESMTP id EE8028FC17 for ; Wed, 11 Feb 2009 13:47:47 +0000 (UTC) (envelope-from lists@braisel.com) Received: from localhost (mail.glave.de [213.170.191.74]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by jehuda.cx2.org (Postfix) with ESMTP id 8B15BBB19 for ; Wed, 11 Feb 2009 14:43:22 +0100 (CET) Date: Wed, 11 Feb 2009 14:29:39 +0100 From: =?iso-8859-1?Q?Andr=E9?= Braselmann To: freebsd-mobile@freebsd.org Message-ID: <20090211132939.GA845@trashbin.none.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-XMPP-ID: ab@braisel.com X-Accepted-File-Formats: ASCII PDF - *NO* MS Office Files! User-Agent: Mutt/1.5.18 (2008-05-17) Subject: Acer 5101 AWLMI X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Feb 2009 13:47:48 -0000 Hi there, i've got that "crappy" model from Acer mentioned above. "Crappy" because the Acer 5100 series is famous for broken motherboards, ideally when you are just 2 month out of the guarantee time. Anyway, the USB Ports are broken under any OS, EHCI produces just errors. This machine is running with 7.1-R amd64 smoothy, also acpi for the battery is working. Below is a dmesg from a kernel built with removed ehci/ohci/uhci devices. What's really annoying is that the synaptics trackpad is hanging after approx. 3 seconds of moving the mouse pointer (console also in xorg), moused says in foreground/debug mode nothing. This also occurs under OpenBSD 4.4 amd64 and in ubuntu versions prior to 8.10. Anyone seen that behaviour before? Or just broken? The other question: sysctl says S3/S4/S5 states are supported. But when i invoke them, it says that it's not supported??? Under ubuntu 8.10 hibernate2disk is supported and works out of the box (sorry for mentioning it ;-) ThX K.André Braselmann -- "I have a good reason for finding the system inappropriate for my intended deployment platform" --- snip dmesg --- Copyright (c) 1992-2009 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.1-RELEASE #0: Sun Feb 8 18:28:05 CET 2009 root@trashbin.none.lan:/usr/obj/usr/src/sys/TRASHBIN Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Turion(tm) 64 Mobile Technology MK-36 (1995.01-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x40fc2 Stepping = 2 Features=0x78bfbff Features2=0x2001 AMD Features=0xea500800 AMD Features2=0x1d usable memory = 2068725760 (1972 MB) avail memory = 1996247040 (1903 MB) ACPI APIC Table: MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, 1000 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 acpi_ec0: port 0x62,0x66 on acpi0 acpi_lid0: on acpi0 acpi_button0: on acpi0 acpi_button1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0x9000-0x90ff mem 0xf8000000-0xfbffffff,0xfc000000-0xfc00ffff irq 17 at device 5.0 on pci1 acpi_video0: on vgapci0 pcib2: at device 4.0 on pci0 pci2: on pcib2 pcib3: at device 5.0 on pci0 pci4: on pcib3 pci0: at device 19.0 (no driver attached) pci0: at device 19.1 (no driver attached) pci0: at device 19.2 (no driver attached) pci0: at device 20.0 (no driver attached) atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x8420-0x842f at device 20.1 on pci0 ata0: on atapci0 ata0: [ITHREAD] ata1: on atapci0 ata1: [ITHREAD] pcm0: mem 0xfc400000-0xfc403fff irq 16 at device 20.2 on pci0 pcm0: [ITHREAD] isab0: at device 20.3 on pci0 isa0: on isab0 pcib4: at device 20.4 on pci0 pci6: on pcib4 rl0: port 0xa000-0xa0ff mem 0xfc100000-0xfc1000ff irq 21 at device 1.0 on pci6 miibus0: on rl0 rlphy0: PHY 0 on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:16:d4:1e:53:06 rl0: [ITHREAD] ath0: mem 0xfc110000-0xfc11ffff irq 22 at device 2.0 on pci6 ath0: [ITHREAD] ath0: WARNING: using obsoleted if_watchdog interface ath0: Ethernet address: 00:16:cf:6d:49:81 ath0: mac 7.8 phy 4.5 radio 5.6 cbb0: mem 0xfc101000-0xfc101fff irq 20 at device 4.0 on pci6 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 cbb0: [ITHREAD] pci6: at device 4.1 (no driver attached) pci6: at device 4.2 (no driver attached) pci6: at device 4.3 (no driver attached) pci6: at device 4.4 (no driver attached) acpi_tz0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model Generic PS/2 mouse, device ID 0 battery0: on acpi0 acpi_acad0: on acpi0 cpu0: on acpi0 powernow0: on cpu0 orm0: at iomem 0xc0000-0xcefff on isa0 ppc0: cannot reserve I/O port range sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 or not responding sio0: [FILTER] sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounter "TSC" frequency 1995010378 Hz quality 800 Timecounters tick every 1.000 msec ad0: 114473MB at ata0-master UDMA100 acd0: DVDR at ata0-slave UDMA33 pcm0: pcm0: Trying to mount root from ufs:/dev/ad0s1a --- snap dmesg --- From owner-freebsd-mobile@FreeBSD.ORG Wed Feb 11 17:42:17 2009 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8140C106566C for ; Wed, 11 Feb 2009 17:42:17 +0000 (UTC) (envelope-from admin@lissyara.su) Received: from hosting.lissyara.su (hosting.lissyara.su [77.221.149.162]) by mx1.freebsd.org (Postfix) with ESMTP id 3D7278FC1F for ; Wed, 11 Feb 2009 17:42:16 +0000 (UTC) (envelope-from admin@lissyara.su) Received: from [89.178.145.99] (port=48754 helo=HP.lissyara.su) by hosting.lissyara.su with esmtpa (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LXIk0-0009bd-MP; Wed, 11 Feb 2009 20:19:16 +0300 Message-ID: <49930898.7070605@lissyara.su> Date: Wed, 11 Feb 2009 20:19:20 +0300 From: Alex Keda User-Agent: Thunderbird 2.0.0.19 (X11/20090209) MIME-Version: 1.0 To: =?UTF-8?B?QW5kcsOpIEJyYXNlbG1hbm4=?= References: <20090211132939.GA845@trashbin.none.lan> In-Reply-To: <20090211132939.GA845@trashbin.none.lan> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Description: if spam count > 60 - this is spam X-Spam-Count: 0 X-Spam-Description: if spam count > 60 - this is spam X-Spam-Count: 0 X-Descriptions: powered by www.lissyara.su X-Bounce-ID: hosting.lissyara.su Cc: freebsd-mobile@freebsd.org Subject: Re: Acer 5101 AWLMI X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Feb 2009 17:42:17 -0000 André Braselmann пишет: > Hi there, > > i've got that "crappy" model from Acer mentioned above. "Crappy" because > the Acer 5100 series is famous for broken motherboards, ideally when > you are just 2 month out of the guarantee time. > > Anyway, the USB Ports are broken under any OS, EHCI produces just > errors. This machine is running with 7.1-R amd64 smoothy, also acpi for > the battery is working. Below is a dmesg from a kernel built > with removed ehci/ohci/uhci devices. > With CURRENT, 2 or 3 month ago it works correct. I do not how it laptop now, and cannot test today CURRENT with new USB2 stack > What's really annoying is that the synaptics trackpad is hanging after > approx. 3 seconds of moving the mouse pointer (console also in xorg), > moused says in foreground/debug mode nothing. This also occurs under > OpenBSD 4.4 amd64 and in ubuntu versions prior to 8.10. > Anyone seen that behaviour before? Or just broken? > For CURRENT, I use hw.psm.synaptics_support=1 in /boot/loader.conf and all work OK, last year, or above > The other question: sysctl says S3/S4/S5 states are supported. But when i > invoke them, it says that it's not supported??? Under ubuntu 8.10 > hibernate2disk is supported and works out of the box (sorry for mentioning it > ;-) uname -a, please. With amd64 it not work. From owner-freebsd-mobile@FreeBSD.ORG Thu Feb 12 02:49:44 2009 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1C3B8106564A for ; Thu, 12 Feb 2009 02:49:44 +0000 (UTC) (envelope-from jmt@twilley.org) Received: from alpha.twilley.org (alpha.twilley.org [204.152.189.135]) by mx1.freebsd.org (Postfix) with ESMTP id 066728FC0C for ; Thu, 12 Feb 2009 02:49:43 +0000 (UTC) (envelope-from jmt@twilley.org) Received: from [192.168.1.107] (c-24-6-104-13.hsd1.ca.comcast.net [24.6.104.13]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "twilley.org", Issuer "CA Cert Signing Authority" (verified OK)) by alpha.twilley.org (Postfix) with ESMTPSA id 4B6E623383C; Wed, 11 Feb 2009 18:49:42 -0800 (PST) Message-ID: <49938E13.4060102@twilley.org> Date: Wed, 11 Feb 2009 18:48:51 -0800 From: Jack Twilley User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Alexander Motin References: <1233145383.00067348.1233133205@10.7.7.3> <49817333.8070708@mavhome.dp.ua> <49898716.701@unsane.co.uk> <498988F9.40106@mavhome.dp.ua> In-Reply-To: <498988F9.40106@mavhome.dp.ua> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-mobile@freebsd.org, Vincent Hoffman Subject: Re: Tethering with HTC Touch Pro -- how? X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Feb 2009 02:49:44 -0000 Alexander Motin wrote: > Vincent Hoffman wrote: >> On 29/1/09 09:13, Alexander Motin wrote: >>> Jack Twilley wrote: >>> >>>> I have enabled internet connection sharing on my HTC Touch Pro by >>>> modifying the registry. The phone works for tethering on my Vista box >>>> as expected. How do I make it work on FreeBSD? >>>> >>> I am successfully using my Qtek S200 with WM6.1 as plain Bluetooth >>> GPRS/EDGE modem. BT PAN profile could be better for internet sharing; I >>> haven't seen it implemented, but there were some activity. Sharing via >>> USB cable requires RNDIS support, which is also not implemented, AFAIK >>> due to buggy and undocumented protocol. >>> >> Just as a quick appendium, bluetooth PAN support got added to -CURRENT a >> couple of days ago. >> I'll try and dig out my old HTC Hermes and test it, will report back if >> I do. > > I have even tested it already and replied on freebsd-bluetooth@. It > works fine with my Qtek S200 with WM6.1. > I went to the freebsd-bluetooth mailing list archives and saw that it worked, but nobody's actually posted anything on how to do it, starting from a system with a recent -CURRENT and a phone that can do the right thing. I was able to use the FreeBSD Handbook chapter on Bluetooth to do stuff like successfully pair my phone and my laptop. I was able to search for nap and opush with sdpcontrol and see a screen or so each of output but I didn't quite see what to do next. The chapter talks about searching and browsing services, and I can run the commands and get output, but it doesn't quite make enough sense for me to move forward. If you can document what you did to make it work, what commands and configuration files and all, that'd be really really helpful to those of us who aren't as familiar with Bluetooth as you guys and just want to tether our laptops. Thanks! Jack. From owner-freebsd-mobile@FreeBSD.ORG Thu Feb 12 07:28:13 2009 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E26021065686 for ; Thu, 12 Feb 2009 07:28:13 +0000 (UTC) (envelope-from mav@mavhome.dp.ua) Received: from cmail.optima.ua (cmail.optima.ua [195.248.191.121]) by mx1.freebsd.org (Postfix) with ESMTP id 660578FC13 for ; Thu, 12 Feb 2009 07:28:12 +0000 (UTC) (envelope-from mav@mavhome.dp.ua) X-Spam-Flag: SKIP X-Spam-Yversion: Spamooborona-2.1.0 Received: from [212.86.226.226] (account mav@alkar.net HELO mavbook.mavhome.dp.ua) by cmail.optima.ua (CommuniGate Pro SMTP 5.2.9) with ESMTPSA id 234363143; Thu, 12 Feb 2009 09:28:12 +0200 Message-ID: <4993CF8B.2030103@mavhome.dp.ua> Date: Thu, 12 Feb 2009 09:28:11 +0200 From: Alexander Motin User-Agent: Thunderbird 2.0.0.19 (X11/20090118) MIME-Version: 1.0 To: Jack Twilley References: <1233145383.00067348.1233133205@10.7.7.3> <1233231789.00067817.1233220802@10.7.7.3> <1233761002.00070820.1233750002@10.7.7.3> <1233761005.00070824.1233750602@10.7.7.3> <1234419790.00074006.1234407602@10.7.7.3> In-Reply-To: <1234419790.00074006.1234407602@10.7.7.3> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Vincent Hoffman , freebsd-mobile@freebsd.org Subject: Re: Tethering with HTC Touch Pro -- how? X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Feb 2009 07:28:14 -0000 Jack Twilley wrote: > Alexander Motin wrote: >> Vincent Hoffman wrote: >>> On 29/1/09 09:13, Alexander Motin wrote: >>>> Jack Twilley wrote: >>>> >>>>> I have enabled internet connection sharing on my HTC Touch Pro by >>>>> modifying the registry. The phone works for tethering on my Vista box >>>>> as expected. How do I make it work on FreeBSD? >>>>> >>>> I am successfully using my Qtek S200 with WM6.1 as plain Bluetooth >>>> GPRS/EDGE modem. BT PAN profile could be better for internet sharing; I >>>> haven't seen it implemented, but there were some activity. Sharing via >>>> USB cable requires RNDIS support, which is also not implemented, AFAIK >>>> due to buggy and undocumented protocol. >>>> >>> Just as a quick appendium, bluetooth PAN support got added to -CURRENT a >>> couple of days ago. >>> I'll try and dig out my old HTC Hermes and test it, will report back if >>> I do. >> >> I have even tested it already and replied on freebsd-bluetooth@. It >> works fine with my Qtek S200 with WM6.1. > > I went to the freebsd-bluetooth mailing list archives and saw that it > worked, but nobody's actually posted anything on how to do it, starting > from a system with a recent -CURRENT and a phone that can do the right > thing. > > I was able to use the FreeBSD Handbook chapter on Bluetooth to do stuff > like successfully pair my phone and my laptop. I was able to search for > nap and opush with sdpcontrol and see a screen or so each of output but > I didn't quite see what to do next. The chapter talks about searching > and browsing services, and I can run the commands and get output, but it > doesn't quite make enough sense for me to move forward. If you can > document what you did to make it work, what commands and configuration > files and all, that'd be really really helpful to those of us who aren't > as familiar with Bluetooth as you guys and just want to tether our laptops. I have written such script for myself: #!/bin/sh trap "/usr/bin/killall btpand" SIGINT ifconfig tap10 create && \ btpand -d acer -a s200 -s NAP -i tap10 && \ sleep 1 && \ dhclient tap10 && \ echo Running... && \ while pgrep btpand >/dev/null do sleep 2 done && printf 'Terminated\a' echo ifconfig tap10 destroy acer is the my system name and s200 is my phone name, both addresses added to /etc/bluetooth/hosts. If devices are peered, no other configuration required. The only thing needed in my case is to l2ping phone several times before connecting, to wake it's BT up. -- Alexander Motin From owner-freebsd-mobile@FreeBSD.ORG Thu Feb 12 07:30:41 2009 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D883A106566C for ; Thu, 12 Feb 2009 07:30:41 +0000 (UTC) (envelope-from mav@mavhome.dp.ua) Received: from cmail.optima.ua (cmail.optima.ua [195.248.191.121]) by mx1.freebsd.org (Postfix) with ESMTP id 596648FC0C for ; Thu, 12 Feb 2009 07:30:41 +0000 (UTC) (envelope-from mav@mavhome.dp.ua) X-Spam-Flag: SKIP X-Spam-Yversion: Spamooborona-2.1.0 Received: from [212.86.226.226] (account mav@alkar.net HELO mavbook.mavhome.dp.ua) by cmail.optima.ua (CommuniGate Pro SMTP 5.2.9) with ESMTPSA id 234363506; Thu, 12 Feb 2009 09:30:40 +0200 Message-ID: <4993D01F.5070507@mavhome.dp.ua> Date: Thu, 12 Feb 2009 09:30:39 +0200 From: Alexander Motin User-Agent: Thunderbird 2.0.0.19 (X11/20090118) MIME-Version: 1.0 To: Jack Twilley References: <1233145383.00067348.1233133205@10.7.7.3> <1233231789.00067817.1233220802@10.7.7.3> <1233761002.00070820.1233750002@10.7.7.3> <1233761005.00070824.1233750602@10.7.7.3> <1234419790.00074006.1234407602@10.7.7.3> <4993CF8B.2030103@mavhome.dp.ua> In-Reply-To: <4993CF8B.2030103@mavhome.dp.ua> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Vincent Hoffman , freebsd-mobile@freebsd.org Subject: Re: Tethering with HTC Touch Pro -- how? X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Feb 2009 07:30:42 -0000 Alexander Motin wrote: > Jack Twilley wrote: >> Alexander Motin wrote: >>> Vincent Hoffman wrote: >>>> On 29/1/09 09:13, Alexander Motin wrote: >>>>> Jack Twilley wrote: >>>>> >>>>>> I have enabled internet connection sharing on my HTC Touch Pro by >>>>>> modifying the registry. The phone works for tethering on my Vista >>>>>> box >>>>>> as expected. How do I make it work on FreeBSD? >>>>>> >>>>> I am successfully using my Qtek S200 with WM6.1 as plain Bluetooth >>>>> GPRS/EDGE modem. BT PAN profile could be better for internet >>>>> sharing; I >>>>> haven't seen it implemented, but there were some activity. Sharing via >>>>> USB cable requires RNDIS support, which is also not implemented, AFAIK >>>>> due to buggy and undocumented protocol. >>>>> >>>> Just as a quick appendium, bluetooth PAN support got added to >>>> -CURRENT a >>>> couple of days ago. >>>> I'll try and dig out my old HTC Hermes and test it, will report >>>> back if >>>> I do. >>> >>> I have even tested it already and replied on freebsd-bluetooth@. It >>> works fine with my Qtek S200 with WM6.1. >> >> I went to the freebsd-bluetooth mailing list archives and saw that it >> worked, but nobody's actually posted anything on how to do it, >> starting from a system with a recent -CURRENT and a phone that can do >> the right thing. >> >> I was able to use the FreeBSD Handbook chapter on Bluetooth to do >> stuff like successfully pair my phone and my laptop. I was able to >> search for nap and opush with sdpcontrol and see a screen or so each >> of output but I didn't quite see what to do next. The chapter talks >> about searching and browsing services, and I can run the commands and >> get output, but it doesn't quite make enough sense for me to move >> forward. If you can document what you did to make it work, what >> commands and configuration files and all, that'd be really really >> helpful to those of us who aren't as familiar with Bluetooth as you >> guys and just want to tether our laptops. > > I have written such script for myself: > > #!/bin/sh > > trap "/usr/bin/killall btpand" SIGINT > > ifconfig tap10 create && \ > btpand -d acer -a s200 -s NAP -i tap10 && \ > sleep 1 && \ > dhclient tap10 && \ > echo Running... && \ > while pgrep btpand >/dev/null > do > sleep 2 > done && > printf 'Terminated\a' > echo > ifconfig tap10 destroy > > acer is the my system name and s200 is my phone name, both addresses > added to /etc/bluetooth/hosts. If devices are peered, no other > configuration required. The only thing needed in my case is to l2ping > phone several times before connecting, to wake it's BT up. Surely you should also run "Internet sharing" application on phone. -- Alexander Motin From owner-freebsd-mobile@FreeBSD.ORG Fri Feb 13 06:08:37 2009 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9996B106566B for ; Fri, 13 Feb 2009 06:08:37 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [220.233.188.227]) by mx1.freebsd.org (Postfix) with ESMTP id E333A8FC17 for ; Fri, 13 Feb 2009 06:08:36 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id n1D68YiM078321; Fri, 13 Feb 2009 17:08:35 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Fri, 13 Feb 2009 17:08:34 +1100 (EST) From: Ian Smith To: Sam Leffler In-Reply-To: <4991ABA0.4050300@freebsd.org> Message-ID: <20090213165848.N38905@sola.nimnet.asn.au> References: <20090210154047.N38905@sola.nimnet.asn.au> <4991ABA0.4050300@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-mobile@freebsd.org Subject: Re: Problems with ath at kern.hz=100 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Feb 2009 06:08:37 -0000 On Tue, 10 Feb 2009, Sam Leffler wrote: > Ian Smith wrote: > > On Mon, 9 Feb 2009, Bengt Ahlgren wrote: > > > > > I was changing kern.hz to 100 on my IBM X40 (Pentium-M) laptop to see > > > whether that saves some battery, but ran into problems with ath not > > > working properly. At first I thought that my hardware was failing, > > > but changing hz back to 1000 solved the problem. I am running > > > 7.1-RELEASE-p1 and have the following Atheros chip: > > > > Feb 9 11:13:10 P142 kernel: ath_hal: 0.9.20.3 (AR5210, AR5211, > > AR5212, RF5111, RF5112, RF2413, RF5413) > > > Feb 9 11:13:10 P142 kernel: ath0: mem > > 0xd0200000-0xd020ffff irq 11 at device 2.0 on pci2 > > > Feb 9 11:13:10 P142 kernel: ath0: [ITHREAD] > > > Feb 9 11:13:10 P142 kernel: ath0: WARNING: using obsoleted if_watchdog > > interface > > > Feb 9 11:13:10 P142 kernel: ath0: Ethernet address: 00:05:4e:4e:1f:c7 > > > Feb 9 11:13:10 P142 kernel: ath0: mac 5.6 phy 4.1 5ghz radio 1.7 2ghz > > radio 2.3 > > > > There's an order of magnitude room to move between 100 and 1000 Hz. You > > could also try with maybe 250 or 500? > > > > What speed is your Pentium-M? Are you using powerd? If so, what minimum > > CPU freq does it drop back to (sysctl debug.cpufreq.lowest)? > > > > Sam has talked of a problem with ath (and maybe other) interrupt rates > > overwhelming slow CPUs to the extent that userland (ie powerd) doesn't get > > a look-in for a while, as I understand it. A fast CPU clocked back to less > > than say 300MHz IS a slow CPU, until powerd gets to crank it up. > > > > If powerd starvation were happening you'd see livelock not slow traffic. The > problem was that MIB overflow interrupts from the card were pounding the host > but since the cpu clock was lowered they were not serviced fast enough. > > FWIW I believe the MIB interrupt storm issue is fixed in head. I posted a > patch to stable@ to enable backmerge of the necessary code but received ~zero > feedback in >1 month so RELENG_7 will continue to rot w/ old code. Thanks for the clarification, Sam. I did see your patch but due to ongoing Severe Weather Events here I've not had enough (solar) power to even upgrade my thinkpad to RELENG_7 for months, and the nearest access point is kilometres away, so I've had to shelve wireless dreaming until I can move house. Lame excuses i know .. [..] > You can use tcpdump to monitor traffic at multiple levels in the hierarchy: > > tcpdump -i ath0 -n # tap at 802.3 level > tcpdump -i ath0 -n -y IEEE802_11 # tap at 802.11 level > tcpdump -i ath0 -n -y IEEE802_11_RADIO # tap at driver level > > and/or you can check statistics using athstats and wlanstats or you can turn > on debugging msgs in net80211 or the ath driver using wlandebug and athdebug. > Some of these may require you to build your kernel w/ debug options (e.g. > ATH_DEBUG). All filed for now. cheers, Ian From owner-freebsd-mobile@FreeBSD.ORG Fri Feb 13 22:01:55 2009 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CAB65106564A for ; Fri, 13 Feb 2009 22:01:55 +0000 (UTC) (envelope-from jmt@twilley.org) Received: from alpha.twilley.org (alpha.twilley.org [204.152.189.135]) by mx1.freebsd.org (Postfix) with ESMTP id A6E088FC0C for ; Fri, 13 Feb 2009 22:01:55 +0000 (UTC) (envelope-from jmt@twilley.org) Received: from [10.103.8.209] (205.158.109.36.ptr.us.xo.net [205.158.109.36]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by alpha.twilley.org (Postfix) with ESMTPSA id 80C16233858; Fri, 13 Feb 2009 14:01:54 -0800 (PST) Message-ID: <4995EDCC.1090207@twilley.org> Date: Fri, 13 Feb 2009 14:01:48 -0800 From: Jack Twilley User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Alexander Motin References: <1233145383.00067348.1233133205@10.7.7.3> <1233231789.00067817.1233220802@10.7.7.3> <1233761002.00070820.1233750002@10.7.7.3> <1233761005.00070824.1233750602@10.7.7.3> <1234419790.00074006.1234407602@10.7.7.3> <4993CF8B.2030103@mavhome.dp.ua> <4993D01F.5070507@mavhome.dp.ua> In-Reply-To: <4993D01F.5070507@mavhome.dp.ua> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-mobile@freebsd.org, Vincent Hoffman Subject: Re: Tethering with HTC Touch Pro -- how? X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Feb 2009 22:01:56 -0000 Alexander Motin wrote: > Alexander Motin wrote: >> Jack Twilley wrote: >>> Alexander Motin wrote: >>>> Vincent Hoffman wrote: >>>>> On 29/1/09 09:13, Alexander Motin wrote: >>>>>> Jack Twilley wrote: >>>>>> >>>>>>> I have enabled internet connection sharing on my HTC Touch Pro by >>>>>>> modifying the registry. The phone works for tethering on my >>>>>>> Vista box >>>>>>> as expected. How do I make it work on FreeBSD? >>>>>>> >>>>>> I am successfully using my Qtek S200 with WM6.1 as plain Bluetooth >>>>>> GPRS/EDGE modem. BT PAN profile could be better for internet >>>>>> sharing; I >>>>>> haven't seen it implemented, but there were some activity. Sharing >>>>>> via >>>>>> USB cable requires RNDIS support, which is also not implemented, >>>>>> AFAIK >>>>>> due to buggy and undocumented protocol. >>>>>> >>>>> Just as a quick appendium, bluetooth PAN support got added to >>>>> -CURRENT a >>>>> couple of days ago. >>>>> I'll try and dig out my old HTC Hermes and test it, will report >>>>> back if >>>>> I do. >>>> >>>> I have even tested it already and replied on freebsd-bluetooth@. It >>>> works fine with my Qtek S200 with WM6.1. >>> >>> I went to the freebsd-bluetooth mailing list archives and saw that it >>> worked, but nobody's actually posted anything on how to do it, >>> starting from a system with a recent -CURRENT and a phone that can do >>> the right thing. >>> >>> I was able to use the FreeBSD Handbook chapter on Bluetooth to do >>> stuff like successfully pair my phone and my laptop. I was able to >>> search for nap and opush with sdpcontrol and see a screen or so each >>> of output but I didn't quite see what to do next. The chapter talks >>> about searching and browsing services, and I can run the commands and >>> get output, but it doesn't quite make enough sense for me to move >>> forward. If you can document what you did to make it work, what >>> commands and configuration files and all, that'd be really really >>> helpful to those of us who aren't as familiar with Bluetooth as you >>> guys and just want to tether our laptops. >> >> I have written such script for myself: >> >> #!/bin/sh >> >> trap "/usr/bin/killall btpand" SIGINT >> >> ifconfig tap10 create && \ >> btpand -d acer -a s200 -s NAP -i tap10 && \ >> sleep 1 && \ >> dhclient tap10 && \ >> echo Running... && \ >> while pgrep btpand >/dev/null >> do >> sleep 2 >> done && >> printf 'Terminated\a' >> echo >> ifconfig tap10 destroy >> >> acer is the my system name and s200 is my phone name, both addresses >> added to /etc/bluetooth/hosts. If devices are peered, no other >> configuration required. The only thing needed in my case is to l2ping >> phone several times before connecting, to wake it's BT up. > > Surely you should also run "Internet sharing" application on phone. > Your script was great. I was able to get a connection, and DHCP configured the interface. I was able to ping hosts on the Internet and resolve names, but I couldn't ssh to my colo box nor was I able to browse the web or chat via IM. Still some work to be done but I can't blame FreeBSD. :-) Thank you again for all your help! Jack. From owner-freebsd-mobile@FreeBSD.ORG Sat Feb 14 14:10:08 2009 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 978161065670 for ; Sat, 14 Feb 2009 14:10:08 +0000 (UTC) (envelope-from ivakras1@gmail.com) Received: from mail-fx0-f11.google.com (mail-fx0-f11.google.com [209.85.220.11]) by mx1.freebsd.org (Postfix) with ESMTP id F2B0E8FC15 for ; Sat, 14 Feb 2009 14:10:07 +0000 (UTC) (envelope-from ivakras1@gmail.com) Received: by fxm4 with SMTP id 4so429808fxm.19 for ; Sat, 14 Feb 2009 06:10:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :user-agent:references:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:message-id; bh=NMsidLl8JO7EgDatCwIO6tqlMUBUkzbj0FjGG8FJnyA=; b=Tf65l5UQljxUqtaEdxaivPLnWsC1F1GAaeOgj/aAy8hbP1ieBtitp0vFLY+bY+THW+ 813ObuhLfgtVd8dJyaptCH/qOta8pyAgVH386SfbM8Ta308oMf8tP6agxp+xaqxD0LDW 1iO/FHSnu3zi3DnU/1vCyIfzfQjloxjQ9lUco= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:references:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :message-id; b=gR8MSIleFXjYh72MkpfUatKcULaebRWDK1UXccqDkY3caCageQj0UFB3ZYEXTpTS7S Gy68Qmk8d3Q95EVJqrW98wmSmfKLUTDxBWq3lz39eGo55LR0zjDhVOQ30VCDjkfIvLo7 YTFD5Fgkk6wUtBDJmxNRUwNIOAl76+KmmBR2U= Received: by 10.223.111.71 with SMTP id r7mr85523fap.59.1234619221234; Sat, 14 Feb 2009 05:47:01 -0800 (PST) Received: from ?192.168.15.129? ([92.50.244.162]) by mx.google.com with ESMTPS id e34sm26535524ugd.20.2009.02.14.05.46.59 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 14 Feb 2009 05:47:00 -0800 (PST) From: Dmitry Kolosov To: freebsd-mobile@freebsd.org Date: Sat, 14 Feb 2009 16:46:02 +0300 User-Agent: KMail/1.9.10 References: <1233145383.00067348.1233133205@10.7.7.3> <49898716.701@unsane.co.uk> <498988F9.40106@mavhome.dp.ua> In-Reply-To: <498988F9.40106@mavhome.dp.ua> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200902141646.02359.ivakras1@gmail.com> Subject: Re: Tethering with HTC Touch Pro -- how? X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Feb 2009 14:10:08 -0000 On Wednesday 04 February 2009 15:24:25 Alexander Motin wrote: > Vincent Hoffman wrote: > > On 29/1/09 09:13, Alexander Motin wrote: > >> Jack Twilley wrote: > >>> I have enabled internet connection sharing on my HTC Touch Pro by > >>> modifying the registry. The phone works for tethering on my Vista box > >>> as expected. How do I make it work on FreeBSD? > >> > >> I am successfully using my Qtek S200 with WM6.1 as plain Bluetooth > >> GPRS/EDGE modem. BT PAN profile could be better for internet sharing; I > >> haven't seen it implemented, but there were some activity. Sharing via > >> USB cable requires RNDIS support, which is also not implemented, AFAIK > >> due to buggy and undocumented protocol. > > > > Just as a quick appendium, bluetooth PAN support got added to -CURRENT a > > couple of days ago. > > I'll try and dig out my old HTC Hermes and test it, will report back if > > I do. > > I have even tested it already and replied on freebsd-bluetooth@. It > works fine with my Qtek S200 with WM6.1. I cant find any instrustions how\where to download\install\configure btpand for 7-STABLE environment. Or maybe i should just wait some time and btpand will be included in 7-STABLE update? If so, how long that time will be? From owner-freebsd-mobile@FreeBSD.ORG Sat Feb 14 18:46:31 2009 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9A249106564A for ; Sat, 14 Feb 2009 18:46:31 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from mail-gx0-f224.google.com (mail-gx0-f224.google.com [209.85.217.224]) by mx1.freebsd.org (Postfix) with ESMTP id 53AFB8FC1A for ; Sat, 14 Feb 2009 18:46:31 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: by gxk24 with SMTP id 24so2265761gxk.19 for ; Sat, 14 Feb 2009 10:46:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=taxqExAvTle/PlH564tWvWTjq1r5FSd/K0M0Qxm8Xfs=; b=T6ZNKWg1vBaZBb8Isk0Eh5f869q+W4D3qTEf6nRDPlfF2aps79C/gUBBi5ehCYQVHY r5zZpfZUAT/obr+Gj5Q/6/3FkykEymC15bhkCfMua6I0G18ztFyb0GlFSGbagwUbswEW bC7fGa9tgw60SjkKecVy79G3nsPjHIABBySfA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=R4YunjZIGHl9ZR6QjCwfekawP3r8GSgTxQh3+jk2mFVImEJ/MSgbMhLfPaOqfh7h1e towrpXOpThD11JIYz4jSro3+jESUdQAontAirK8VSGsYuREQoHa8jZAPw2aYFI+z+ryt q5wKLAlaDc33QIPebYymqMsS6eLcI4MHaWVos= MIME-Version: 1.0 Received: by 10.150.133.18 with SMTP id g18mr261681ybd.166.1234637190709; Sat, 14 Feb 2009 10:46:30 -0800 (PST) In-Reply-To: <200902141646.02359.ivakras1@gmail.com> References: <1233145383.00067348.1233133205@10.7.7.3> <49898716.701@unsane.co.uk> <498988F9.40106@mavhome.dp.ua> <200902141646.02359.ivakras1@gmail.com> Date: Sat, 14 Feb 2009 10:46:30 -0800 Message-ID: From: Maksim Yevmenkin To: Dmitry Kolosov Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-mobile@freebsd.org Subject: Re: Tethering with HTC Touch Pro -- how? X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Feb 2009 18:46:31 -0000 On Sat, Feb 14, 2009 at 5:46 AM, Dmitry Kolosov wrote: > On Wednesday 04 February 2009 15:24:25 Alexander Motin wrote: >> Vincent Hoffman wrote: >> > On 29/1/09 09:13, Alexander Motin wrote: >> >> Jack Twilley wrote: >> >>> I have enabled internet connection sharing on my HTC Touch Pro by >> >>> modifying the registry. The phone works for tethering on my Vista box >> >>> as expected. How do I make it work on FreeBSD? >> >> >> >> I am successfully using my Qtek S200 with WM6.1 as plain Bluetooth >> >> GPRS/EDGE modem. BT PAN profile could be better for internet sharing; I >> >> haven't seen it implemented, but there were some activity. Sharing via >> >> USB cable requires RNDIS support, which is also not implemented, AFAIK >> >> due to buggy and undocumented protocol. >> > >> > Just as a quick appendium, bluetooth PAN support got added to -CURRENT a >> > couple of days ago. >> > I'll try and dig out my old HTC Hermes and test it, will report back if >> > I do. >> >> I have even tested it already and replied on freebsd-bluetooth@. It >> works fine with my Qtek S200 with WM6.1. > > I cant find any instrustions how\where to download\install\configure btpand for > 7-STABLE environment. Or maybe i should just wait some time and btpand will be > included in 7-STABLE update? If so, how long that time will be? svn/cvs is your friend :) === SVN rev 187938 on 2009-01-30 22:23:21Z by emax Add btpand(8) daemon from NetBSD. This daemon provides support for Bluetooth Network Access Point (NAP), Group Ad-hoc Network (GN) and Personal Area Network User (PANU) profiles. Obtained from: NetBSD MFC after: 1 month === thanks, max