From owner-freebsd-hackers@FreeBSD.ORG Fri Oct 20 10:56:14 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D877916A412 for ; Fri, 20 Oct 2006 10:56:14 +0000 (UTC) (envelope-from kpielorz@tdx.co.uk) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [62.13.130.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 46D5643D45 for ; Fri, 20 Oct 2006 10:56:13 +0000 (GMT) (envelope-from kpielorz@tdx.co.uk) Received: from Unsupported (thebrick.dmpriest.net.uk [62.13.130.30]) by caladan.tdx.co.uk (8.13.6/8.13.6/Kp) with ESMTP id k9KAuCDm095058 for ; Fri, 20 Oct 2006 11:56:12 +0100 (BST) Date: Fri, 20 Oct 2006 11:56:33 +0100 From: Karl Pielorz To: freebsd-hackers@freebsd.org Message-ID: X-Mailer: Mulberry/4.0.4 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: 6.1-STABLE hangs, ddb shows 'acpi_timer_read'? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Oct 2006 10:56:14 -0000 Hi All, We've got an HP DL380 server, stacked out with drives running Sendmail. The machine is quite busy (LA rarely below 4 - and it's three 'spindle' sets of RAID drives are always busy). It's probably constantly running 200-300 copies of sendmail, plus an assortment of other processes (mostly admin scripts that kind of thing). It's got a Xeon 3.2Ghz CPU (HT disabled), w/2Gb of RAM running a generic kernel, w/out IPv6 support (and with DDB/KDB included obviously) This machine just 'hangs' every couple of days. I have DDB/KDB compiled in - and if I throw it into DDB I get the following: [first couple of lines missed courtesy of screen-dump] db> bt Tracing pid 38 tid 100027 td 0xc6495180 acpi_timer_read(c0aba3c0,c09035c0,e6a05bbc,c0662ef3,c0aba3c0) at acpi_timer_read+0x13 acpi_timer_get_timecout_safe(c0aba3c0) at acpi_timer_get_timecount_safe+0xa binuptime(e6a05be8) at binuptime+0x43 mi_switch(6,c6395900,c639a54,c639500,e6a05c34) at mi_swtich+0x33 maybe_preempt(c6395900) at maybe_preempt+0xc4 sched_add(c639500,4,c6495180,c6395900,c637f280) at sched_add+0x27 setrunqueue(c6395900,4) at setrunqueue+0x63 intr_even_schedule_thread(c637f280) at intr_event_schedule_thread+0xb5 intr_exectue_handlers(c638d6e0,e6a05cac,13,46a05cf4,c08189f3) at intr_execute_handlers+0x118 ... I have a crash dump from it - which I've saved (I'm moderately familiar with working with dumps, but this one is split into two?) If anyone has any pointers, or can do some hand holding to get more info from the dump, or what to do next time it happens? Cheers, -Karl