[i855] dual-head configs are ill

Bug #26341 reported by John Fettig
32
Affects Status Importance Assigned to Milestone
xserver-xorg-driver-i810 (Ubuntu)
Fix Released
Medium
Reinhard Tartler

Bug Description

Using a config that worked in hoary, I try to run with a external monitor hooked
up to my laptop (a Dell Inspiron 700m). This causes xorg to crash with the
primary error being:

(EE) I810(0): vm86() syscall generated signal 11.

After this crash, if I replace the xorg.conf with one that works for single
display (on the laptop LCD) and restart X, X will not start. Only after the
machine has been rebooted will the X server start again. My video hardware:

0000:00:02.1 Display controller: Intel Corp. 82852/855GM Integrated Graphics
Device (rev 02)

I will attach the xorg.conf that produces the problem, as well as the Xorg.0.log.

https://bugs.freedesktop.org/show_bug.cgi?id=3105: https://bugs.freedesktop.org/show_bug.cgi?id=3105

Revision history for this message
John Fettig (jfettig) wrote :

Created an attachment (id=5094)
Xorg.0.log logfile with crash

Revision history for this message
John Fettig (jfettig) wrote :

Created an attachment (id=5095)
xorg.conf that produces the crash

Revision history for this message
John Fettig (jfettig) wrote :

Also, this issue seems very similar to a bug filed at freedesktop.org, however,
the signals generated are different:

https://bugs.freedesktop.org/show_bug.cgi?id=3105

Revision history for this message
Jozef Kotlár (kotlar) wrote :

I have the same problem on my Toshiba Satellite A50. Just the signal number is 4.
Would be a temporal solution for me to compile the xorg with gcc-3.3?

Revision history for this message
Daniel Stone (daniels) wrote :

you can try gcc3 if you want, but it didn't seem to help any here

Revision history for this message
Jozef Kotlár (kotlar) wrote :

I would like to report that patch provided in associated upstream issue
(https://bugs.freedesktop.org/attachment.cgi?id=4178) works for me in breezy.

Revision history for this message
Jozef Kotlár (kotlar) wrote :

(In reply to comment #6)
> I would like to report that patch provided in associated upstream issue
> (https://bugs.freedesktop.org/attachment.cgi?id=4178) works for me in breezy.

I have to correct myself: my case was the latter one case mentioned in the issue
and not this one which appears actually sooner.

Revision history for this message
Daniel Stone (daniels) wrote :

i'm tracking the upstream bug quite closely

Revision history for this message
John Fettig (jfettig) wrote :

This patch -- https://bugs.freedesktop.org/attachment.cgi?id=4323
fixes my problem when applied to the version of i810 in dapper: xserver-xorg-driver-i810-1.4.1.3. I think you might consider applying it to the official package in dapper.

Revision history for this message
John Fettig (jfettig) wrote :

Oh, that attachment is associated with this bug: https://bugs.freedesktop.org/show_bug.cgi?id=3105

Daniel Stone (daniels)
Changed in xserver-xorg-driver-i810:
assignee: daniels → nobody
Paul Sladen (sladen)
Changed in xserver-xorg-driver-i810:
assignee: nobody → swat
assignee: swat → ubuntu-x-swat
Revision history for this message
John Fettig (jfettig) wrote :

I created a howto that explains how to patch the breezy package:

http://ubuntuforums.org/showthread.php?t=155762

Revision history for this message
Reinhard Tartler (siretart) wrote :

xserver-xorg-driver-i810 (1:1.4.1.3-0ubuntu3) dapper; urgency=low

  * Apply patch from freedesktop for fixing segfault in i810 dualhead configs
    (setPipeAccess, see https://bugs.freedesktop.org/show_bug.cgi?id=3105)
    Closes: M#26341
  * Use dpatch

 -- Reinhard Tartler <email address hidden> Fri, 21 Apr 2006 21:44:25 +0200

Changed in xserver-xorg-driver-i810:
assignee: ubuntu-x-swat → siretart
status: Unconfirmed → Fix Committed
Changed in xserver-xorg-driver-i810:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.