** Summary changed:

- [i855GME] X crash because of intel driver on intrepid
+ [i855GME] X ring crash on fujitsu-siemens lifebook laptop

** Description changed:

  Binary package hint: xserver-xorg-video-intel
  
  What I report here is probably two ugly X-crash bugs in the new stable
  release of kubuntu. The reason why I file a new bug is that they are
  bugs on the stable intrepid with new X-packages.
  
  They make my fujitsu-siemens lifebook laptop absolutelly hopeless to use
  after upgrade from Hardy to Intrepid:
  
  1) Inpredictable, but frequent x-crashes
  The bug seems to identical bug #220019 that was assumed to be solved on Hardy 
and earlier releases of intrepid. However, on xserver-xorg-video-intel_2.4.1 
the problem makes X very unstable on my laptop.
  
  2) mplayer full screen video and vlc crashes X
  This really ugly as it kills all tty1-7. Your only chance is alternately 
using ctrl-alt-backspace and ctrl-alt-delete. 
  
  I didn't experience these bug on Hardy, not even on kde-4.0 remix
  version.
  
  I would like to try installing the old Hardy drivers, but they conflict
  with the rest of the xorg-core package, so it requires probably that I
  go back to Hardy's X-system ... if that is possible. Incidentally, I
  used the i810-driver on Hardy. But, the intrepid i810 driver makes the
  screen go absolutely crazy with black-white-images passing fastly
  downward on the screen.
  
  I hope I have provided sufficient technical information on the bugs in
  the attached file. If anyone would like more information, please tell
  me.
  
+ Error in I830WaitLpRing(), timeout for 2 seconds
+ pgetbl_ctl: 0x2fee0001 getbl_err: 0x00000000
+ ipeir: 0x00000000 iphdr: 0x01810000
+ LP ring tail: 0x000189f0 head: 0x000189cc len: 0x0001f001 start 0x00000000
+ eir: 0x0000 esr: 0x0000 emr: 0xffff
+ instdone: 0xffc0 instpm: 0x0000
+ memmode: 0x00000108 instps: 0x00000000
+ hwstam: 0xffff ier: 0x0002 imr: 0x0009 iir: 0x02f0
+ Ring at virtual 0xaf71d000 head 0x189cc tail 0x189f0 count 9
+ Ring at virtual 0xaf71d000 head 0x189cc tail 0x189f0 count 9
+       000188cc: 00000000      MI_NOOP                                  1
+       000188d0: 02000011      MI_FLUSH                                 1
+       000188d4: 00000000      MI_NOOP                                  1
+       000188d8: 02000011      MI_FLUSH                                 1
+       000188dc: 00000000      MI_NOOP                                  1
+       000188e0: 02000011      MI_FLUSH                                 1
+       000188e4: 00000000      MI_NOOP                                  1
+       000188e8: 02000011      MI_FLUSH                                 1
+       000188ec: 00000000      MI_NOOP                                  1
+       000188f0: 02000011      MI_FLUSH                                 1
+       000188f4: 00000000      MI_NOOP                                  1
+       000188f8: 02000011      MI_FLUSH                                 1
+       000188fc: 00000000      MI_NOOP                                  1
+       00018900: 10800001      MI_STORE_DATA_INDEX                      3
+       00018904: 00000014
+       00018908: 000499ea
+       0001890c: 00000000      MI_NOOP                                  1
+       00018910: 00000000      MI_NOOP                                  1
+       00018914: 01000000      MI_USER_INTERRUPT                        1
+       00018918: 18800080      MI_BATCH_BUFFER_START                    2
+       0001891c: 02d88001
+ Batch buffer at 0x02d88001 {
+       02d88001: 0054f000      MI_NOOP                                  -1
+ 
  [lspci]
  00:00.0 Host bridge [0600]: Intel Corporation 82852/82855 GM/GME/PM/GMV 
Processor to I/O Controller [8086:3580] (rev 02)
        Subsystem: Fujitsu Limited. Device [10cf:11d5]
  00:02.0 VGA compatible controller [0300]: Intel Corporation 82852/855GM 
Integrated Graphics Device [8086:3582] (rev 02)
        Subsystem: Fujitsu Limited. Device [10cf:1281]

-- 
[i855GME] X ring crash on fujitsu-siemens lifebook laptop
https://bugs.launchpad.net/bugs/293543
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to