gl screensaver freeze mesa 7.6.0~git20090817.7c422387-0ubuntu2

[Łukasz Kuryło]

After karmik upgdade to mesa 7.6.0~git20090817.7c422387-0ubuntu2 glMatrix screensaver on my dualscreen setup freezes. SysRq + RSEIUB works most of the time, Ctrl+Alt+F1,2,3.. doesn't work. Reverting to 7.5-1ubuntu1 helps.

[lspci]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 0c)
     Subsystem: Hewlett-Packard Company Device [103c:30c0]

[Łukasz Kuryło (lukasz-kurylo)]

lsb_release -rd
Description: Ubuntu karmic (development branch)
Release: 9.10

[Łukasz Kuryło (lukasz-kurylo)]

00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 0c)
        Subsystem: Hewlett-Packard Company Device 30c0
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
        Latency: 0
        Capabilities: <access denied>
        Kernel driver in use: agpgart-intel
        Kernel modules: intel-agp

00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
        Subsystem: Hewlett-Packard Company Device 30c0
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin A routed to IRQ 29
        Region 0: Memory at e4600000 (64-bit, non-prefetchable) [size=1M]
        Region 2: Memory at d0000000 (64-bit, prefetchable) [size=256M]
        Region 4: I/O ports at 4000 [size=8]
        Capabilities: <access denied>
        Kernel driver in use: i915
        Kernel modules: i915

00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
        Subsystem: Hewlett-Packard Company Device 30c0
        Control: I/O+ Mem+ BusMaster+ SpecCycle- Mem...

[Łukasz Kuryło (lukasz-kurylo)]

Screen 0: minimum 320 x 200, current 3600 x 1200, maximum 8192 x 8192
VGA1 connected 1920x1200+1680+0 (normal left inverted right x axis y axis) 519mm x 324mm
   1920x1200 60.0*+
   1280x1024 75.0
   1152x864 75.0
   1024x768 75.1 70.1 60.0
   832x624 74.6
   800x600 72.2 75.0 60.3
   640x480 72.8 75.0 66.7 60.0
   720x400 70.1
LVDS1 connected 1680x1050+0+0 (normal left inverted right x axis y axis) 331mm x 207mm
   1680x1050 60.1*+
   1600x1024 60.2
   1280x1024 60.0
   1440x900 59.9
   1280x960 60.0
   1360x768 59.8
   1152x864 60.0
   1024x768 60.0
   800x600 60.3
   640x480 59.9
TV1 disconnected (normal left inverted right x axis y axis)

[Bryce Harrington (bryce)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command in a terminal after reproducing the issue, and it it will automatically gather debugging information needed for this bug:

  apport-collect 419291

(You may need to install the python-launchpadlib package from the universe repository. Additionally, when prompted to give apport-collect permissions for Launchpad you will need to give it at least the ability to "Change Non-Private" data as it will be adding information to your bug report.)

[Bryce Harrington (bryce)]

[While the mesa update likely caused this regression, I have a suspicion the fix may require updating -ati. In any case, it'll be easier to track this bug if filed against xserver-xorg-video-ati so I'm moving it there for now.]

[Łukasz Kuryło (lukasz-kurylo)]

Architecture: amd64
DistroRelease: Ubuntu 9.10
MachineType: Hewlett-Packard HP Compaq 6710b (GB891EA#AKD)
Package: xserver-xorg-video-ati (not installed)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-7-generic root=UUID=8b70f45f-e511-49e8-94e0-2a166cc23b12 ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=pl_PL.UTF-8
 LANGUAGE=pl_PL:pl:en_GB:en
ProcVersionSignature: Ubuntu 2.6.31-7.27-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu5
 libgl1-mesa-glx 7.6.0~git20090817.7c422387-0ubuntu3
 libdrm2 2.4.12+git20090801.45078630-0ubuntu1
 xserver-xorg-video-intel 2:2.8.0-0ubuntu2
 xserver-xorg-video-ati N/A
Uname: Linux 2.6.31-7-generic x86_64
UserGroups: adm admin cdrom dialout lp lpadmin netdev plugdev sambashare vboxusers
XorgConf: Error: [Errno 2] No such file or directory: '/etc/X11/xorg.conf'
dmi.bios.date: 05/22/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68DDU Ver. F.12
dmi.board.name: 30C0
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 71.2E
dmi.chassis.asset.tag: CNU7384669
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68DDUVer.F.12:bd05/22/2008:svnHewlett-Packard:pnHPCompaq6710b(GB891EA#AKD):pvrF.12:rvnHewlett-Packard:rn30C0:rvrKBCVersion71.2E:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP Compaq 6710b (GB891EA#AKD)
dmi.product.version: F.12
dmi.sys.vendor: Hewlett-Packard
fglrx: Not loaded
system:
 distro: Ubuntu
 architecture: x86_64kernel: 2.6.31-7-generic

[Łukasz Kuryło (lukasz-kurylo)]

This info was collected after last crash. When screensaver was about to kick in, SYSTEM RESTARTED.

BTW Don't know if that's all attachments that should be here beacause:
   attachment: xdpyinfo.txt...
   attachment: xkbcomp.txt...
Traceback (most recent call last):
  File "/usr/bin/apport-collect", line 145, in <module>
    upload(report, bug)
  File "/usr/bin/apport-collect", line 65, in upload
    task.transitionToStatus(status='New')
  File "/usr/lib/python2.6/dist-packages/launchpadlib/resource.py", line 346, in __call__
    **args)
  File "/usr/lib/python2.6/dist-packages/wadllib/application.py", line 591, in build_representation
    media_type, param_values, **kw_param_values)
  File "/usr/lib/python2.6/dist-packages/wadllib/application.py", line 690, in representation
    return definition.bind(param_values, **kw_param_values)
  File "/usr/lib/python2.6/dist-packages/wadllib/application.py", line 801, in bind
    params, param_values, **kw_param_values)
  File "/usr/lib/python2.6/dist-packages/wadllib/application.py", line 169, in validate_param_values
    param_values[name], name, '", "'.join(options)))
ValueError: Invalid value '"New"' for parameter 'status': valid values are: "New", "Incomplete", "Invalid", "Won't Fix", "Confirmed", "Triaged", "In Progress", "Fix Committed", "Fix Released", "Unknown"

[Bryce Harrington (bryce)]

[This is an automatic notification.]

A new version of the -ati driver is now available in Karmic.

This is a significant update to -ati which brings in kernel mode-setting
(currently disabled) and scores of fixes for DRI2, EXA, etc.

I've posted the new version of this driver to the following PPA,
would you mind testing it and seeing if it resolves the bug you
reported?

  https://edge.launchpad.net/~bryceharrington/+archive/ppa/+sourcepub/709908/+listing-archive-extra

If you're not running this release of Ubuntu, you can try booting the Karmic
LiveCD and loading the PPA onto it, and then log out/in to restart X.
ISOs are available at http://cdimages.ubuntu.com/releases/

After testing Karmic, report back here whether it's still an issue or not,
and if it is please post a fresh Xorg.0.log and 'dmesg' output.

Note there could be new bugs... please file these as new reports using
the command 'ubuntu-bug xorg'.

[Łukasz Kuryło (lukasz-kurylo)]

OK, am I missing something? But what does xserver-xorg-video-ati have to do with intel graphics? I don't even need this package.

[Bryce Harrington (bryce)]

Huh, weird, it appears I mistakenly refiled this against -ati.

Anyway, you're right this is intel. Also I believe this to be the bug #419264 which we now have a fix for.

[Leann Ogasawara (leannogasawara)]

Unduping this from 419264 for now based on Łukasz Kuryło feedback:

https://bugs.edge.launchpad.net/ubuntu/karmic/+source/linux/+bug/419264/comments/39

"That's a negat. For me mesa 7.6.0~git20090817.7c422387-0ubuntu2 is still no go. Even after kernel upgrade to 2.6.31-10 I got kernel panic when moved mouse while glMatrix screensaver was running. Next time glMatrix just froze and it was better I could do SysRq + RSIUB kungfu.
Mine bug was #419264 marked as dupe of this one maybe it's another issue then."

[Łukasz Kuryło (lukasz-kurylo)]

What I need to add to "unincomplete" this bug?

[Łukasz Kuryło (lukasz-kurylo)]

Update:
single output -> works OK.
dual screen -> not OK.

I'll focus on dualscreen then.
when screensaver turns on it works for about a 60sec and I can get back to work with no problems.
After that time only part of the second display is redrawn, looks like part with y coordinate not covered by first display. So no movement on first screen and no movement on upper part of second screen.
LVDS1 display 1 1680x1050
VGA1 display 2 1920x1200
so after event only lower 150 (1200 - 1050) pixels of second display are being redrawn.
I had a luck and it didn't crash when moved mouse.
I ran xrandr --output VGA1 --off and strange thing happened. After clicking on KDE menu it popped up, but some 150 pixels to high and wasn't all drawn. I ran terminal program and my input wasn't shown until I moved it's wobbly window. Also top 150 pixels of screen wasn't usable.

So: wobbly windows movement -> whole screen redraw shows my typed input
      menu is to high and top of the screen not refreshing -> some coordinates messed up

I managed to fix this situation by:
xrandr --output LVDS1 --off
yes it left me with no display at the moment
and then xrandr --output LVDS1 --auto
and all was back to normal.

Another observation, some time ago sync to vblank started to work for compiz and even for dualscreen. But it seems broken now. When I move windows between monitors I believe their
"covering crtc" isn't chosen correctly ie. it's allways 1 or allwas 2 regardles of where the window is.

[Łukasz Kuryło (lukasz-kurylo)]

For the loast few days I was working with screensaver disabled and it was OK.
Today I gave it a try and glmatrix crashed in brw_validate_state().

[Łukasz Kuryło (lukasz-kurylo)]

Today I was unable to reproduce the issue, screensaver kicked in several times and no crash.

[Łukasz Kuryło (lukasz-kurylo)]

I'm no longer able to reproduce this bug. Don't know which update fixed it though. It was somewhere around 17.09.2009 when it got fixed.

[Łukasz Kuryło (lukasz-kurylo)]

Wolfgang do you know what was that fix? It would be nice to know what was wrong.

[Łukasz Kuryło (lukasz-kurylo)]

This part from my comment on 2009-09-10 is still valid:
I ran xrandr --output VGA1 --off and strange thing happened. After clicking on KDE menu it popped up, but some 150 pixels to high and wasn't all drawn. I ran terminal program and my input wasn't shown until I moved it's wobbly window. Also top 150 pixels of screen wasn't usable.

So: wobbly windows movement -> whole screen redraw shows my typed input
      menu is to high and top of the screen not refreshing -> some coordinates messed up

I managed to fix this situation by:
xrandr --output LVDS1 --off
yes it left me with no display at the moment
and then xrandr --output LVDS1 --auto
and all was back to normal.

It happened when I got my notebook from work to home.
At work: LVDS1 + VGA1 then suspended and disconnected notebook from external monitor (in that order)
At home: wake up. X still uses screen size of 2 monitors. I tried to turn off VGA1 (xrandr --output VGA1 --off) and then situation described above occurs.

[Łukasz Kuryło (lukasz-kurylo)]

Update:
- those symptoms that I still confirm are also present after downgrade to mesa 7.5-1ubuntu1

Scenarios:

Precondition: Both LVDS1 and VGA1 active with configuration:
LVDS1 1680x1050
VGA1 1920x1200 right of LVDS1

First case:
VGA1 is disconnected, issuing xrandr --output VGA1 --off
top part of the screen is black. Only full screen redraws (moving wobbly windows) shows typed in commands in konsole.

Second case:
VGA1 still plugged, issuing xrandr --output VGA1 --off
All is OK even after subsequent disconnecting of VGA1.

In short: issuing xrandr --output VGA1 --off AFTER disconnecting monitor breaks display.

[Łukasz Kuryło (lukasz-kurylo)]

After disconnecting VGA1 and turning it of using arandr.

[Łukasz Kuryło (lukasz-kurylo)]

Now it's fixed for me. After disconnecting VGA1 I can safely turn it off and display stays intact. Only for brief moment at the top of the screen is a black stripe. But after desktop refreshes it disappears and all is fine.