ubuntu-x-swat team mailing list archive

[Bryce Harrington <816337@xxxxxxxxxxxxxxxxxx>]

Yes, I think all the bugs with EIR 0x00000010 and PGTBL_ER: 0x00000100
are the same bug.  However, I've noticed some variation between one
person and the next, so am hesistant to continue just duping them all
together, as we don't have a complete understanding of the problem.

I'm perplexed by what might be causing it.  It's not an X.org bug
obviously since it occurs well before X.org ever comes into the picture,
and it seems to not be a kernel bug exactly.  It might be ubuntu-
specific; I've never heard of reports about it from other distros, but I
don't think other distros have as good of tools for capturing crash
reports as us.  It's not a bug in apport, it's a legitimate gpu lockup,
just false.  We thought it was something to do with how video drivers
were being loaded, but andy rejiggered them so we only have one graphics
driver at a time, which should have solved  that, yet people still see
it.  I think it must have something to do with conflicts in the order or
overlapping of kernel driver loading.  It would be nice if someone with
a real thorough knowledge of how kernel drivers are loaded during init
could look into this problem, but admittedly it's a fairly minor issue
since it's a false hang and since it won't appear in the actual release
(since we turn off apport at that point).

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/816337

Title:
  [i965gm] False GPU lockup  EIR: 0x00000010 PGTBL_ER: 0x00000100

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/816337/+subscriptions