Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 11 Nov 2006 14:02:46 -0500
From:      Kris Kennaway <kris@obsecurity.org>
To:        Gergely CZUCZY <phoemix@harmless.hu>
Cc:        hackers@FreeBSD.org, Kris Kennaway <kris@obsecurity.org>
Subject:   Re: system randomly freezes
Message-ID:  <20061111190245.GA7577@xor.obsecurity.org>
In-Reply-To: <20061111185747.GA56613@harmless.hu>
References:  <20061111172731.GB39999@harmless.hu> <20061111183110.GA6975@xor.obsecurity.org> <20061111183432.GA41296@harmless.hu> <20061111184025.GA7128@xor.obsecurity.org> <20061111184625.GA41463@harmless.hu> <20061111185228.GA7338@xor.obsecurity.org> <20061111185747.GA56613@harmless.hu>

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

--EeQfGwPcQSOJBaQU
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Nov 11, 2006 at 07:57:47PM +0100, Gergely CZUCZY wrote:

> > OK, seems weird to go through all the disruption of changing to a new
> > OS instead of a few minutes work at a console to give us what we need
> > to resolve the matter -- but whatever works for you.
> already done some stuff like these movings... i'm familiars with them.
> it's not about a few minutes work. it's about the few hours' downtime :)

It's a few minutes to perform the additional work at the serial
console when your system hangs, which is *required* for a developer to
help with your problem.  If you're not willing to do this, there's not
much more we can do for you.

> > > > > taking into account these facts, exactly what additional debugging
> > > > > would you recommend?
> > > >=20
> > > > Turn on all the usual debugging checks (WITNESS, INVARIANTS,
> > > > DEBUG_*_LOCKS, etc) and check whether anything turns up.
> > > i've found these in conf/NOTES and i386/conf/NOTES:
> > > options         WITNESS
> > > options         INVARIANTS
> > > options         DEBUG_VFS_LOCKS
> > >=20
> > > anything else?
> >=20
> > Well, yeah...I'd hoped you'd be able to figure it out for yourself
> > though without me spelling it out :) Also add INVARIANT_SUPPORT and
> > DEBUG_LOCKS.
> good. i had some compiling errors :)
> sorry, but i'm not familiar with building a debug kernel
>=20
> > First, try with just altq removed, in case that already fixes it.  If
> > not, then proceed as above.
> okey. when 6.2 comes at, to that on the nearest sunday i will update
> the system anyways, and check it with this new configuration. i wouldn't
> make an unnessecary downtime if it's not required.

After 6.2 is release will of course be too late for you, again.  If
the problem is not fixed by magic then you'll be in the same position
you are now.

I really suggest you get that serial console hooked up, read the
documentation I pointed you at, and then put in the trivial effort
required to let the FreeBSD team help you.

> BTW, currently' i'm not on the list, and these emails are not
> going to be posted there.
> would you be so kind and include the mailing list in your
> next reply's CC list?
> it would be nice if the mailing list could archive this
> discussion.

You were the one who dropped the list from the CC in your reply to
me ;-)

Kris

--EeQfGwPcQSOJBaQU
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFFVh5VWry0BWjoQKURAnfmAKDB4OobJx5BPg0zJ9Ya8RO8p5Yf6wCeLY8C
syNWrrYogFhEXAGqg68rEB0=
=jSPG
-----END PGP SIGNATURE-----

--EeQfGwPcQSOJBaQU--



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