> > > 3.0 worked fine, 3.1-rc9 worked fine, I think -rc10 too. 3.1 release
> > > hangs in random places while using X.
>
> Do you have VT-d enabled in the BIOS?
Disabled VT-d in BIOS and 3.2-rc3 has been running stable since then. SO
it seems to be the same problem.
--
Meelis Roos (mr...@linu
> > Yes, VT-x and VT-d are both enabled from BIOS setup.
>
> Any reason for that? We've found all kinds of problems with DMAR enabled
> on these machines that is only resolved by completely turning it
> off. You might try with intel_iommu=off and make sure that's stable.
Well, there is reason for
On Wed, 23 Nov 2011 09:28:52 +0200 (EET), Meelis Roos wrote:
> Yes, VT-x and VT-d are both enabled from BIOS setup.
Any reason for that? We've found all kinds of problems with DMAR enabled
on these machines that is only resolved by completely turning it
off. You might try with intel_iommu=off an
> > > 3.0 worked fine, 3.1-rc9 worked fine, I think -rc10 too. 3.1 release
> > > hangs in random places while using X.
Also found out that 3.1-rc10 was already bad, will redo the bisect but
it takes days sinc I'm not at the machine most of the time.
> Do you have VT-d enabled in the BIOS?
Yes,
On Tue, 22 Nov 2011 13:08:06 +0200 (EET), Meelis Roos wrote:
> > 3.0 worked fine, 3.1-rc9 worked fine, I think -rc10 too. 3.1 release
> > hangs in random places while using X.
Do you have VT-d enabled in the BIOS?
--
keith.pack...@intel.com
pgpDDQsjBrQss.pgp
Description: PGP signature
_
On Tue, Nov 22, 2011 at 12:15:24PM +0200, Meelis Roos wrote:
> 3.0 worked fine, 3.1-rc9 worked fine, I think -rc10 too. 3.1 release
> hangs in random places while using X.
>
> Core i5 660, lspci below. Running 64-bit Debian unstable.
>
> lspci -nn
>
> 00:00.0 Host bridge [0600]: Intel Corporati
