S3 ProSavageDDR K4M266 hard locks on X init when DRI is enabled

Bug #336311 reported by Toni Spets on 2009-03-01
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
xserver-xorg-video-savage (Ubuntu)
Undecided
Unassigned
Declined for Lucid by Bryce Harrington

Bug Description

Binary package hint: xserver-xorg-video-savage

On Acer Aspire 1200 series the graphics adapter, S3 Inc. 86C380 ProSavageDDR K4M266 hard locks on X startup if DRI is enabled in xorg.conf. This happens before any visual feedback and I only see a black screen. Just plain X, no dm/wm loaded.

Option "DRI" "false" lets the X session start up correctly.

No previous Linux experience with this particular laptop model so I don't know if it has been working on previous releases. I can't get a good Xorg log file because of the hard lock, no response to ping or ssh and the log file itself after reboot is empty (the buffer was never written).

Happens on both, intrepid and jaunty.

package version: 2.2.1-1build2

Bryce Harrington (bryce) wrote :

Hi toni-spets,

Please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log (and maybe Xorg.0.log.old) file from after reproducing this issue. If you've made any customizations to your /etc/X11/xorg.conf please attach that as well.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

Changed in xserver-xorg-video-savage:
status: New → Incomplete
Tormod Volden (tormodvolden) wrote :

Please also try
 Option "BusType" "PCI"
instead of disabling DRI.

Eric Drechsel (ericdrex) wrote :

Confirming with S3 Inc. 86C380 [ProSavageDDR K4M266] (rev 02) in generic VIA laptop.

Setting Option "DRI" "false" avoids the lockup. Thanks for the sleuthing Toni.

Setting Option "BusType" "PCI" causes a slightly different lockup, with vertical black and white bars (without this option, the screen remains blank). X apparently gets further in the startup process before locking with the option set. Attached is X log from this session.

X log for unmodified xorg.conf to follow.

Eric Drechsel (ericdrex) wrote :
Eric Drechsel (ericdrex) wrote :
Eric Drechsel (ericdrex) wrote :

oops, that log is with the workaround enabled

fbusse (frank-busse) wrote :

Don't now if it's the same bug, but an at least very similar behaviour struck me with an FSC Amilo M 6300, 166 MHz Celeron, 1 GB RAM, 86C380 ProSavageDDR K4M266 after clean install of Jaunty (Kubuntu or Xubuntu from alternate CD): hard lock on X startup, xorg.conf is empty, lshal yells

error: dbus_bus_get: org.freedesktop.DBus.Error.FileNotFound:
Failed to connect to socket /var/run/dbus/system_bus_socket:
No such file or directory

However, the same system is running fine with Hardy (Kubuntu, after clean install from alternate CD). xorg.conf and lshal output attached for reference.

I will provide lspci -vvnn and Xorg.0.log for both systems and keep both systems unchanged for at least a week in case further information would be helpful

fbusse (frank-busse) wrote :
fbusse (frank-busse) wrote :
fbusse (frank-busse) wrote :
fbusse (frank-busse) wrote :
Bryce Harrington (bryce) on 2009-09-02
tags: added: jaunty

This also bug also affect my Amilo D you can see some info at http://www.familie-prokop.de/amilo-d/index_en.html
please fix it...

Tormod Volden (tormodvolden) wrote :

Toni, did Option "BusType" "PCI" help you any?

Toni Spets (hifi) wrote :

I think I tested it and I think it didn't help. I still have the laptop and will retest with Karmic when I get the chance.

fbusse (frank-busse) wrote :

confirming behaviour described 2009-07-13 with Karmic

Tormod Volden (tormodvolden) wrote :

Does Option "BusType" "PCI" help?

Tormod Volden (tormodvolden) wrote :

Oh wait, PCI should be default now. Please attach your Xorg.0.log.

fbusse (frank-busse) wrote :

@Tormod Volden:

current status: System as mentioned in #7 and following, "startx" from recovery mode, system locked with black screen, hard reset

<console>
root@beta:~# file /var/log/Xorg.0.log
/var/log/Xorg.0.log: empty
</console>

Changed in xserver-xorg-video-savage (Ubuntu):
status: Incomplete → Confirmed
Bryce Harrington (bryce) wrote :

[This is an automatic notification.]

Hi Toni,

This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?

Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
normal support channels, please see:

    http://www.ubuntu.com/support

If you are the original reporter and can still reproduce the issue on
Lucid, please run the following command to refresh the report:

  apport-collect 336311

If you are not the original reporter, please file a new bug report, so
we can work with you as the original reporter instead (you can reference
bug 336311 in your report if you think it may be related):

  ubuntu-bug xorg

If by chance you can no longer reproduce the issue on Lucid or if you
feel it is no longer relevant, please mark the bug report 'Fix Released'
or 'Invalid' as appropriate, at the following URL:

  https://bugs.launchpad.net/ubuntu/+bug/336311

Changed in xserver-xorg-video-savage (Ubuntu):
status: Confirmed → Incomplete
tags: added: needs-retested-on-lucid-by-june
fbusse (frank-busse) wrote :

appears to be solved for Lucid for the system mentioned 2009-07-13 - great work, thanx to the team!

btw, would someone from the team mind telling us out in the wild what the problem was about?

fbusse (frank-busse) wrote :

some additional information:

fresh install from the Kubuntu 10.04 desktop CD did it, only the bootsplash image appears to be displayed with 8 colors (similar to attachment).

starting (not installing) Kubuntu from the same CD got me a "hanging" system again.

fbusse (frank-busse) wrote :

corrupt bootsplash image appears to be known plymouth bug #571567

Launchpad Janitor (janitor) wrote :

[Expired for xserver-xorg-video-savage (Ubuntu) because there has been no activity for 60 days.]

Changed in xserver-xorg-video-savage (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.