[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#283929: xv application lock-ups trident driver

retitle 283929 xserver-xfree86: [trident] XVideo applications lockup machine
# Lockups are important bugs.
severity 283929 important
tag 283929 + upstream moreinfo

On Thu, Dec 02, 2004 at 01:21:34PM +0200, Alexei Chetroi wrote:
> Package: xserver-xfree86
> Version: 4.3.0.dfsg.1-8 
>   Hi,
>   I'm running debian testing on Acer travelmate 354TE which has:
> 0000:01:00.0 VGA compatible controller: Trident Microsystems CyberBlade/i1 (rev 5d)
> videochip installed. The problem is that mplayer with XV video output
> locks up entire box, kernel doesn't response, network dead, sysrq magic
> keys also dead. Tried it on debian's 2.4.27 and custom compiled kernel
> with and without acpi, pci=noacpi in any combination, anyhow it is
> always reprodusable, but it NEVER lock-up when I start mplayer for the
> 1st time, sometimes I can start mplayer for the 2nd and 3rd time, but
> any subsequent mplayers start increase prababilty of system lock.
>   Examining
>   http://cvsweb.xfree86.org/cvsweb/xc/programs/Xserver/hw/xfree86/CHANGELOG?rev=HEAD
>   I see various fixes for the trident driver, which of them are
> incorporated in debian version?

You can review the list of patches we have incorporated by looking at the
source package.

$ apt-get source xfree86

(Warning, this is a big download.)

The file in question is:

> Is there newer debian source package of xserver which I try?

The current version is 4.3.0.dfsg.1-10, but no changes to the trident
driver have been made since -8.

> PS: here's device section of XFree86-4 config file:
> Section "Device"
>         Identifier      "Trident Microsystems CyberBlade/i1"
>         Driver          "trident"
>         Option          "CyberShadow"   "false"
>         Option          "ShadowFB"      "false"
>         Option          "SWcursor"      "false"
>         Option          "PciRetry"      "true"
>         Option          "NoPciBurst"    "true"
>         Option          "NoAccel"       "false"
>         Option          "UseFB"         "false"
> EndSection

We really need more information than this.  I am including some
instructions on gathering it below.

[The following is a form letter.]

Dear bug submitter,

Since the XFree86 X server is a large and complex piece of software, some
more information is required of you before this bug can be handled.  Please
run the following commands from a shell prompt to gather and deliver this
information to us:

$ /usr/share/bug/xserver-xfree86 >/tmp/output 3>&1
$ mailx -s "Re: Bug#283929 followup" 283929@bugs.debian.org </tmp/output

(Do not type the "$" at the beginning of the above lines; they are there
simply to indicate the shell prompt.)

If you do not have a "mailx" command on your system, you can get it by
installing the "mailx" Debian package; for example, with the "aptitude
install mailx" or "apt-get install mailx" commands as root.  Alternatively,
you can also use a mail command that is compatible with mailx's
command-line syntax, such as "mutt".

One very good way to file bugs with the Debian Bug Tracking System is to
use the "reportbug" package and command of the same name.  The reportbug
program does a lot of automatic information-gathering that helps package
maintainers to understand your system configuration, and also ensures that
your message to the Debian Bug Tracking System is well-formed so that it is
processed correctly by the automated tools that manage the reports.  (If
you've ever gotten a "bounce" message from the Debian Bug Tracking System
that tells you your message couldn't be processed, you might appreciate
this latter feature.)

Therefore, I strongly urge you to give "reportbug" a try as your primary
bug reporting tool for the Debian System in the future.

If you *did* use reportbug to file your report, then you're receiving this
message because the information we expected to see was not present.

If you deliberately deleted this information from the report, please don't
do that in the future, even if it seems like it makes the mail too large.
50 kB (kilobytes) of configuration and log data is typical.  Only if the
included information greatly exceeds this amount (more than 100 kB) should
you consider omitting it; instead, put it up on the World Wide Web
somewhere and provide URLs to it in your report, or in subsequent followup
by mailing <283929@bugs.debian.org>.

Thank you!

G. Branden Robinson                |     The more ridiculous a belief
Debian GNU/Linux                   |     system, the higher the probability
branden@debian.org                 |     of its success.
http://people.debian.org/~branden/ |     -- Wayne R. Bartz

Attachment: signature.asc
Description: Digital signature

Reply to: