Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 26 Aug 2008 23:22:38 -0400
From:      Robert Noland <rnoland@FreeBSD.org>
To:        Alexander Motin <mav@FreeBSD.org>
Cc:        freebsd-multimedia@freebsd.org
Subject:   Re: Hda patch from this day
Message-ID:  <1219807358.1805.37.camel@wombat.2hip.net>
In-Reply-To: <1219774141.58043.16.camel@squirrel.corp.cox.com>
References:  <20080826133434.060D63EA0E5@smtp4-g19.free.fr> <1219762528.58043.2.camel@squirrel.corp.cox.com> <48B41B44.7060208@FreeBSD.org> <1219774141.58043.16.camel@squirrel.corp.cox.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--=-8RObL0DgBSkfpRspEa2S
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Tue, 2008-08-26 at 14:09 -0400, Robert Noland wrote:
> On Tue, 2008-08-26 at 18:03 +0300, Alexander Motin wrote:
> > Robert Noland wrote:
> > >> with your 20080825 patch:
> > >> cat /dev/sndstat:
> > >> FreeBSD Audio Driver (newpcm: 32bit 2007061600/i386)
> > >> Installed devices:
> > >> pcm0: <HDA codec Realtek ALC260 PCM #0> at hdac0 cad 0
> > >> kld snd_hda [20080825_0100] [GIANT] (0p:0v/1r:1v channels default)
> > >=20
> > > Giant?  That could be the source of my boot hang.  My root filesys is
> > > off of usb, which is also Giant, so if your holding the lock...
> >=20
> > Actually have no idea what does that mean yet. HDA driver itself locked
> > without using Giant, and I don't know where it comes from. May be from
> > sound subsystem, maybe from somewhere else. All I have done is created
> > child device pcm0 from hdac0 and it appeared in a such way. Probably I
> > had to dig deeper into device creation to understand this.
>=20
> Sigh, Ok, today my laptop is not hanging...  and mine is showing MPSAFE,
> so I have no idea what was going on last night.  It is docked right
> now... I'll un-dock it and see if that effects it, but right now it's
> all working good.  Sorry for the noise...

Ok, the dock was the key... When it is not docked, it still hangs.  I'm
not quite sure what output I can send you to help identify the issue,
but I'll give it some thought.  If you can think of anything that might
help, just let me know and I'll gladly send it along.

I did just see that you updated the patch, so I'll give that a shot and
see if it happens to resolve the issue.

robert.

> robert.
>=20

--=-8RObL0DgBSkfpRspEa2S
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (FreeBSD)

iEYEABECAAYFAki0yH4ACgkQM4TrQ4qfROMOvACfRdrUEFGTd4bwiI3ixLdn/pBg
6u4AnAwMlX05u/v+hIojtBYeuTDMYzTd
=Suof
-----END PGP SIGNATURE-----

--=-8RObL0DgBSkfpRspEa2S--




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1219807358.1805.37.camel>