--=_courier-2387-1042526143-0001-2
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Lately, using the nForce IDE driver I have noticed a few glitches with=20
it that affect stability.
I use the BK tree for my kernel source. Lately, if I 1) clone a fresh=20
tree (i pull from a few places so sometimes there are some boggling=20
conflicts that a fresh tree fixes) or 2) run a bk pull, X will SEGV out=20
of nowhere. At first I thought it was the amount of disk activity.
But after reading the saga of the flukey tty code in the kernel, I am=20
thinking this could also be because of that? Lots of stuff scrolls by=20
when doing a bk clone, and when resolve runs after a bk pull there is=20
often lots of output.
There is no oops at all, nor anything that might be of help in dmesg.
Any ideas? I started noticing it around halfway through 2.5.56...
Regards
Josh
--=_courier-2387-1042526143-0001-2
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+I6+R6TRUxq22Mx4RAt1+AKC32imc2Qhf5Jejm2S89rCV01A95ACfZ/OZ
mnWVDEsMPdLiOcrTSK5ummc=
=FhYF
-----END PGP SIGNATURE-----
--=_courier-2387-1042526143-0001-2--