From owner-freebsd-stable@FreeBSD.ORG Sat Feb 28 01:05:24 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 217F2106564A for ; Sat, 28 Feb 2009 01:05:24 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from mail-ew0-f166.google.com (mail-ew0-f166.google.com [209.85.219.166]) by mx1.freebsd.org (Postfix) with ESMTP id 7C0A98FC08 for ; Sat, 28 Feb 2009 01:05:23 +0000 (UTC) (envelope-from onemda@gmail.com) Received: by ewy10 with SMTP id 10so1439584ewy.43 for ; Fri, 27 Feb 2009 17:05:22 -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=4RvcKsdWlt6mZGL1zdhjcx6+sc5yUmOGwsQzvrSBdPE=; b=mmsEXH8bS346xKffKmtNnjQjfXAtNvPKI3MDG/1IGeFaJHk/YLOitiUJyA9SzOz5vS mzTkeIxQRe3MaNcLx4G4Xi3xgvFmmj73ZKd7UPr3SPV1/Hl2REQ66zAH1bs9n+1brswE QtYz0tPQDGIW6cdhPyUjFMHYplXUlmMQMBJfw= 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=B9xli53LRKNZhgErPNms2Zb7KhEOU9kOt33/vTEkhHukogHALbrjGxXghozTghDkJT MCh4caHWAPbpysysC1hMnfZO7lH6mBvO/D6GKfm0oB1Ias/8g43hUVeCuuq4NMUd7C9j u7Wb7LsvjDu9iWs8YsYBcicpHIkIUBbqn/3pA= MIME-Version: 1.0 Received: by 10.210.89.4 with SMTP id m4mr900580ebb.53.1235783122593; Fri, 27 Feb 2009 17:05:22 -0800 (PST) In-Reply-To: References: <3a142e750902261447k7cac4eb6m457726bc1f4b23d3@mail.gmail.com> <3a142e750902270346m4358ad19p9883e6a69bda9b01@mail.gmail.com> Date: Sat, 28 Feb 2009 02:05:22 +0100 Message-ID: <3a142e750902271705n754aa003v7aa756cff2b54daf@mail.gmail.com> From: "Paul B. Mahol" To: Ross Penner Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: powerd causing crash on Mini-ITX EN1200 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Feb 2009 01:05:24 -0000 On 2/27/09, Ross Penner wrote: > On Fri, Feb 27, 2009 at 3:46 AM, Paul B. Mahol wrote: >> On 2/27/09, Ross Penner wrote: >>> Perhaps, but I rarely run Xorg. I use the machine as a gateway for our >>> network in the house. I've noticed it most often when under a network >>> load but that might not be a real correlation. >>> >>> On Thu, Feb 26, 2009 at 2:47 PM, Paul B. Mahol wrote: >>>> On 2/26/09, Ross Penner wrote: >>>>> Hi, >>>>> >>>>> When I enable powerd, it is only but a matter of time before my >>>>> machine will lock up completely. I've had this problem since I've >>>>> migrated to FreeBSD 7 from 6. FreeBSD 6 never seemed to have any >>>>> problems. I doesn't seem to create a dump so I've had no luck on that >>>>> end. I'm quite perplexed on how to proceed to help get this problem >>>>> documented so it can be fixed. >>>>> >>>>> #uname -a >>>>> FreeBSD rosbox.dyndns.org 7.1-STABLE FreeBSD 7.1-STABLE #0: Thu Feb 26 >>>>> 00:38:44 PST 2009 >>>>> ross@rosbox.dyndns.org:/usr/obj/usr/src/sys/MYKERNEL7 i386 >>>>> >>>>> Is there anything else I con provide that would be of assistance? >>>> >>>> I'm aware of livelock between syscons and powerd which is not trivial >>>> to >>>> reproduce (at least for me). >> >> The locks happens for me only if kernel prints something on console while >> something other is being printed on vtys. >> So it looks like your problem is not related to syscons bugs. >> >> -- >> Paul > > Well, it might not actually be that far off. When I have powerd > enabled, I frequently get a message on the console about 'vge watchdog > timeout' I got that similar one when using "powerd -b min" and transferring big file with ndis vap configured in adhoc mode. Probably I was just lucky that I used min instead of (h)adp. > Does anybody have any ideas on how to try and fix this issue? One nasty fix would be disabling kernel messages on console. I never tested if it actually works, or perhaps I did but forgot about it ;) : echo "kern.consmute=1" >> /boot/sysctl.conf Another, better one would be to make syscons giant free, perhaps rewriting it from scratch .... -- Paul