From owner-freebsd-current@FreeBSD.ORG Fri Aug 14 13:39:02 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8D5AD106568B for ; Fri, 14 Aug 2009 13:39:02 +0000 (UTC) (envelope-from ubm.freebsd@googlemail.com) Received: from mail-fx0-f205.google.com (mail-fx0-f205.google.com [209.85.220.205]) by mx1.freebsd.org (Postfix) with ESMTP id 0C2878FC43 for ; Fri, 14 Aug 2009 13:39:01 +0000 (UTC) Received: by fxm1 with SMTP id 1so1096679fxm.7 for ; Fri, 14 Aug 2009 06:39:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:subject :message-id:in-reply-to:references:x-mailer:mime-version :content-type:content-transfer-encoding; bh=oINRLTVtd9DDB/k/P07FKpBZUpYPdN5HKp7/qQqk1yg=; b=lzKQBShM1xtGX9COfBqhAzZcVPJLXdPDwk6fHPGDLLWoWIBVlGFjWxwRUfn+ci0wtx 5SJ/TIyht8rvkVkGtSZe7ps5RsuXknZBbYe1BaC0TTFMbRjoGVOC5Lshjy/px5ZVK1+b Xt/qSL3PmpVPpmXOFb1il9/qBNyqyhdQMgFJg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=date:from:to:subject:message-id:in-reply-to:references:x-mailer :mime-version:content-type:content-transfer-encoding; b=sqZ7YlN+B3hSYh/IEXHaEYvb53DXNw152CMXZTOtS2Dkf/czTVTyeTOuNcEmZ2U3pP kUkxLtwOlsYNzxR7vrJ6LfSAoJI6Onm/DttTj4/S64NedKYimfliiaSQtgyPdwxyyEKu ozIZNZnLe4BzKoCBdNcDIsAo7Xq6JF2+7mLq0= Received: by 10.204.152.27 with SMTP id e27mr1176535bkw.192.1250255916509; Fri, 14 Aug 2009 06:18:36 -0700 (PDT) Received: from ubm.mine.nu (e181059132.adsl.alicedsl.de [85.181.59.132]) by mx.google.com with ESMTPS id 18sm1840325fks.10.2009.08.14.06.18.34 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 14 Aug 2009 06:18:34 -0700 (PDT) Date: Fri, 14 Aug 2009 15:18:26 +0200 From: Marc UBM To: freebsd-current@freebsd.org Message-Id: <20090814151826.66e5077e.ubm.freebsd@gmail.com> In-Reply-To: <20090808235013.eab98028.ubm@u-boot-man.de> References: <20090708192642.6b30167e.ubm@u-boot-man.de> <20090708225048.ec9d9cad.ubm@u-boot-man.de> <20090710200352.72ef6804.ubm@u-boot-man.de> <20090711205837.46b11405.ubm@u-boot-man.de> <20090711222304.fc99056a.ubm@u-boot-man.de> <20090712122316.4f63fc62.ubm@u-boot-man.de> <20090712181034.93811d03.ubm@u-boot-man.de> <20090712194547.9e573116.ubm@u-boot-man.de> <20090722201750.4ff23293.ubm@u-boot-man.de> <20090806230909.d01e844a.ubm@u-boot-man.de> <20090808002354.61c6c5a3.ubm@u-boot-man.de> <20090808235013.eab98028.ubm@u-boot-man.de> X-Mailer: Sylpheed 2.6.0 (GTK+ 2.16.4; i386-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Fri, 14 Aug 2009 16:04:37 +0000 Subject: Re: run interrupt driven hooks: still waiting for xpt_config X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Aug 2009 13:39:02 -0000 On Sat, 8 Aug 2009 23:50:13 +0200 Marc "UBM" Bocklet wrote: > > > I've a friend with a similar problem (also HighPoint controller, > > > also "run interrupt driven hooks: still waiting for xpt_config"), > > > who gets a panic. I'll try to get the panic string and a > > > backtrace, if I do, I'll post it here. > > > > xpt_config basically means that you're waiting on a device driver > > attached to CAM to finish probing, which could point at a number of > > potential problem sources (including things like interrupt routing > > problems). At least in the 7.x line, I've seen firewire and USB at > > various times cause this issue. It might be interesting to compile > > down to the smallest set of cam-related drivers required to support > > necessary hardware (omit firewire, for example) and see if you see > > any improvement. Pinning it down to a specific driver would have > > significant debugging value :-). > > Thanks a lot for the suggestion, I'll be on holiday for one week > starting tomorrow, I'll try narrowing it down as soon as I'm back :-) I just made sure that the problem still exists with a freshly csupped -current (unfortunately, it does), I'll try removing possible culprits from my kernel next. Bye Marc