Date: Wed, 11 Apr 2007 21:31:58 +0300 From: Giorgos Keramidas <keramida@ceid.upatras.gr> To: John Baldwin <jhb@freebsd.org> Cc: S?ren Schmidt <sos@deepcore.dk>, current@freebsd.org, Ariff Abdullah <ariff@freebsd.org>, Nate Lawson <nate@root.org> Subject: Re: recent commits break via 8235 ata Message-ID: <20070411183158.GA9185@kobe.laptop> In-Reply-To: <200704111021.44494.jhb@freebsd.org> References: <4608A5D9.2010902@root.org> <200704101922.08255.jhb@freebsd.org> <20070411092104.GD1675@kobe.laptop> <200704111021.44494.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2007-04-11 10:21, John Baldwin <jhb@freebsd.org> wrote:
> On Wednesday 11 April 2007 05:21, Giorgos Keramidas wrote:
> > 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?
Sure. I'll try later today, when I'm done with ${REALJOB} real soon
now(TM). I don't have the pre-backout kernel, but it should be very
straightforward to grab dmesg -v output from a new build.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070411183158.GA9185>