From owner-freebsd-acpi@FreeBSD.ORG Tue Sep 20 14:59:53 2005 Return-Path: X-Original-To: acpi@freebsd.org Delivered-To: freebsd-acpi@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0F6E916A41F for ; Tue, 20 Sep 2005 14:59:53 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from poup.poupinou.org (poup.poupinou.org [195.101.94.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id B2B8C43D4C for ; Tue, 20 Sep 2005 14:59:52 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from ducrot by poup.poupinou.org with local (Exim) id 1EHjam-0000XC-00; Tue, 20 Sep 2005 16:59:32 +0200 Date: Tue, 20 Sep 2005 16:59:32 +0200 To: Maxim Maximov Message-ID: <20050920145932.GB1616@poupinou.org> References: <4330020C.5030302@mcsi.pp.ru> <20050920135958.GA1616@poupinou.org> <433016F8.903@mcsi.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <433016F8.903@mcsi.pp.ru> User-Agent: Mutt/1.5.9i From: Bruno Ducrot Cc: acpi@freebsd.org Subject: Re: Hard hang with powerd X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Sep 2005 14:59:53 -0000 On Tue, Sep 20, 2005 at 06:04:40PM +0400, Maxim Maximov wrote: > Bruno Ducrot wrote: > >On Tue, Sep 20, 2005 at 04:35:24PM +0400, Maxim Maximov wrote: > > > >>Hi, all. > >> > >> I've got hard hangs with latest CURRENT in a few seconds after > >> enabling powerd. Here's loader.conf: > >> > >># cat /boot/loader.conf > >>hw.psm.synaptics_support=1 > >>debug.mpsafevfs=1 > >>acpi_perf_load="YES" > >>cpufreq_load="YES" > >>debug.acpi.disabled="sysres" > >>bcmwl5_sys_load="YES" > >> > >> What else can I do to help debug it? > >> > > > > > >The 2 logical CPUs need to set the same MSRs at the same time, > >but if the second one is forced to be idle, I'm not sure if p4tcc will > >work fine. > > > >Therefore, I'm wondering if this hard hang happens with a SMP kernel > >and hyperthreading is enabled, or if this happens with a UP kernel. > > > > Yes, kernel is SMP one. > > # sysctl machdep.hyperthreading_allowed > machdep.hyperthreading_allowed: 1 > It's weird. Could you please try with a kernel without SMP for testing purpose? -- Bruno Ducrot -- Which is worse: ignorance or apathy? -- Don't know. Don't care.