Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 02 Mar 2009 16:27:16 -0500
From:      Joe Marcus Clarke <marcus@FreeBSD.org>
To:        Alexander Motin <mav@FreeBSD.org>
Cc:        FreeBSD-Current <freebsd-current@FreeBSD.org>
Subject:   Re: Continuing saga: FreeBSD -CURRENT hangs with ATA code after April
Message-ID:  <1236029236.37252.113.camel@shumai.marcuscom.com>
In-Reply-To: <49AC4DB3.9020007@FreeBSD.org>
References:  <gohee3$2lla$1@FreeBSD.cs.nctu.edu.tw> <49AC4DB3.9020007@FreeBSD.org>

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

--=-31Vw3bJyAeV2RihzrYfW
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Mon, 2009-03-02 at 23:20 +0200, Alexander Motin wrote:
> Joe Marcus Clarke wrote:
> > I started this thread on May 31 of last year:
> >=20
> > http://lists.freebsd.org/pipermail/freebsd-current/2008-May/085923.html
> >=20
> > The problem remains as of:
> >=20
> > FreeBSD fugu.marcuscom.com 8.0-CURRENT FreeBSD 8.0-CURRENT #12: Sun Mar
> > 1 16:10:52 EST 2009
> > gnome@fugu.marcuscom.com:/space/obj/usr/src/sys/FUGU  i386
> >=20
> > The only way I can boot this system is to hack in the ATA code from
> > April 9, 2008.  I would love just to be able to boot this guy on a
> > default -CURRENT.
>=20
> 1) If I understand right, you had working system on April 9, 2008 and=20
> not working on May 31, 2008 and now. Have you tried to narrow down that=20
> interval between working and not working system to find exact point of=20
> breakage? I see no documented changes in Promise support there in CVS=20
> log, but for example, on Apr 10 2008 I see some related changes=20
> unmentioned in commit message.

The April 9 date is the documented date of last working.  It was the
commit on April 10 13:05:05 that broken things:

"Add experimental support for SATA Port Multipliers

Support is working on the Silicon Image SiI3124/3132.
Support is working on some AHCI chips but far from all.

Remember this is WIP, so test reports and (constructive) suggestions are we=
lcome!"

>=20
> 2) To properly associate problem with present sources I would like to=20
> see full problem verbose messages for the current HEAD.

Sure, I'll reboot in a bit.

>=20
> 3) As my mom told me 15 years ago, if you don't understand what's going=20
> on, insert debugging printfs. If system hangs and we have no other=20
> sources of information, I would start from putting
> 	printf("%s\n", __func__);
> wherever it is possible to get readable path. I would start from every=20
> ata_promise_mio_* function beginning of HEAD code.

Thanks!  I was curious on a location.  I'll update the thread with this
info.

Joe

>=20
--=20
Joe Marcus Clarke
FreeBSD GNOME Team      ::      gnome@FreeBSD.org
FreeNode / #freebsd-gnome
http://www.FreeBSD.org/gnome

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (FreeBSD)

iEYEABECAAYFAkmsTzMACgkQb2iPiv4Uz4dRcgCeNZ9o/jTVmy6eBCENMfaLiO6I
vWgAn3cH4W6lxyJQDL3xirG/JtQ1X9Nd
=jRD0
-----END PGP SIGNATURE-----

--=-31Vw3bJyAeV2RihzrYfW--




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