© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Hi narr,
Thanks for adding the information. Nothing jumps out at me in the logs as problematic, although there's a few warnings which could be clues:
(WW) VIA(0): [XvMC] Not supported on this chipset.
...
(WW) AIGLX: 3D driver claims to not support visual 0x22
(WW) AIGLX: 3D driver claims to not support visual 0x23
(WW) AIGLX: 3D driver claims to not support visual 0x24
(WW) AIGLX: 3D driver claims to not support visual 0x25
(WW) AIGLX: 3D driver claims to not support visual 0x26
(WW) AIGLX: 3D driver claims to not support visual 0x27
(WW) AIGLX: 3D driver claims to not support visual 0x28
(WW) AIGLX: 3D driver claims to not support visual 0x29
(WW) AIGLX: 3D driver claims to not support visual 0x2a
(WW) AIGLX: 3D driver claims to not support visual 0x2b
(WW) AIGLX: 3D driver claims to not support visual 0x2c
(WW) AIGLX: 3D driver claims to not support visual 0x2d
...
(II) VIA(0): Trying VBE Mode 1024x768 (0xc118)
(II) VIA(0): VBESetVBEMode failed...but worked OK without customized refresh and dotclock.
Thanks for reporting that you crashed the system with glxinfo - that's exactly the right thing to do here. It's useful data that crashing it didn't result in messages to Xorg.0.log.
I see a few similar bugs in via/3d behavior upstream in Xorg's bug tracker, but not sure if any of them are matches:
https:/
https:/
https:/
Can you try running glxgears and see if it too crashes the system, or produces any error messages mentioned on these bugs?
Also, after X has frozen, what steps do you take to recover? Do you do ctrl-alt-bkspace to restart it, or reboot the computer, or something else?
Also, have you ever collected a backtrace before? I think if you do not find a match yourself, our next step would be to get a backtrace of glxinfo. I can give you a sequence of commands to run if you've not done this before, and would like to try this route.