From owner-freebsd-current@FreeBSD.ORG Fri Apr 13 21:40:49 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BDB8516A402 for ; Fri, 13 Apr 2007 21:40:49 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from talk.nabble.com (www.nabble.com [72.21.53.35]) by mx1.freebsd.org (Postfix) with ESMTP id 9225A13C45E for ; Fri, 13 Apr 2007 21:40:49 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from [72.21.53.38] (helo=jubjub.nabble.com) by talk.nabble.com with esmtp (Exim 4.50) id 1HcTVg-0004eL-Re for freebsd-current@freebsd.org; Fri, 13 Apr 2007 14:40:48 -0700 Message-ID: <9986936.post@talk.nabble.com> Date: Fri, 13 Apr 2007 14:40:48 -0700 (PDT) From: Christophe Cap To: freebsd-current@freebsd.org In-Reply-To: <200704111021.44494.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: christophe.cap@GDNMAIL.NET References: <4608A5D9.2010902@root.org> <20070327082823.GA2356@kobe.laptop> <20070327151058.5qk9etifk880g4cc@webmail.leidinger.net> <20070327140741.GA60454@kobe.laptop> <200703271227.14308.jhb@freebsd.org> <20070406211229.GB1078@kobe.laptop> <461BEFD6.2050302@root.org> <200704101922.08255.jhb@freebsd.org> <20070411092104.GD1675@kobe.laptop> <200704111021.44494.jhb@freebsd.org> X-Mailman-Approved-At: Fri, 13 Apr 2007 23:55:05 +0000 Subject: Re: recent commits break via 8235 ata 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, 13 Apr 2007 21:40:49 -0000 I seem to have similare problems on my machine. My 2nd SATA disk does not get detected with 6.2 I've attached some logfiles, both dmesg and pciconf outputs are there for the 6-1 and 6-2 kernel on my machine. Hope you kan do something with them. Kind regards, Christophe http://www.nabble.com/file/7865/dmesg-6-1-sata-OK.log dmesg-6-1-sata-OK.log http://www.nabble.com/file/7866/dmesg-6-2-sata-FAIL.log dmesg-6-2-sata-FAIL.log http://www.nabble.com/file/7867/pciconf-6-1-sata-OK.log pciconf-6-1-sata-OK.log http://www.nabble.com/file/7867/pciconf-6-2-sata-FAIL.log pciconf-6-2-sata-FAIL.log John Baldwin wrote: > > On Wednesday 11 April 2007 05:21, Giorgos Keramidas wrote: >> On 2007-04-10 19:22, John Baldwin wrote: >> >On Tuesday 10 April 2007 16:13, Nate Lawson wrote: >> >>Giorgos Keramidas wrote: >> >>> This is the change which stops snd_hda from working here: >> >>> >> >>> % Revision Changes Path >> >>> % 1.233 +39 -55 src/sys/dev/acpica/acpi.c >> >>> >> >>> If I update my kernel sources to Wed Mar 21 14:39:39 2007 +0000 >> >>> (including the sys/modules/padlock/Makefile commit of Sam Leffler, to >> >>> fix the kernel build from Wed Mar 21 17:37:13 2007 +0000), I can see >> >>> that the snd_hda driver probes my sound card correctly. >> >>> >> >>> Updating after the commit shown above, breaks snd_hda. >> >> >> >> I just finished a binsearch and can verify this exact commit causes >> the >> >> problem for my ATA also. I'll spend some more time debugging it >> later. >> >> >> >> John, can I back out rev 1.233 of acpi.c until you return since it >> >> prevents some machines from booting? >> > >> > Well, it most likely means there are other bugs that just happen to >> > not break with the older stuff. Are you sure that just this one >> > change fixes things rather than the changes to the nexus drivers? >> >> For snd_hda on my Toshiba laptop, I can verify that reverting this >> changeset only makes snd_hda probe correctly again. I resynced to last >> night's HEAD version of CVS, reverted this change only, and the snd_hda >> drives still probes correctly. Rebuilding with rev 1.233 of acpi.c >> results in the same failure to attach with: >> >> pcm0: hdac_get_capabilities: Invalid rirb size (0) >> device_attach: pcm0 attach returned 6 > > Can you get boot verbose dmesg for both kernels? > > -- > John Baldwin > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > -- View this message in context: http://www.nabble.com/recent-commits-break-via-8235-ata-tf3471107.html#a9986936 Sent from the freebsd-current mailing list archive at Nabble.com.