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

Bug#279087: Fwd: X crashing

retitle 278654 xserver-xfree86: [ati/r128] problems with existing CCE idle fix
retitle 279087 xserver-xfree86: [ati/r128] X server hanging on Rage 128 RF/SG AGP
severity 279087 important
merge 278654 279087

On Sun, Oct 31, 2004 at 04:40:22PM +0100, Silvério Santos wrote:
> Package: xserver-xfree86
> The error message from /var/log/XFree86.0.log.old in the last line is:
> (EE) R128(0): R128CCEWaitForIdle: (DEBUG) CCE idle took j = 0
> Do you have a cure, as this is getting annoying, because it happens quite
> often? Could you also please answer with PM, as I do not follow the bug
> report lists (except for trouble shooting incidents to avoid RTFM answers)
> and I would prefer not to miss the solution.

I suspect this issue is the same as #278654 <URL:
http://bugs.debian.org/278654 >.

In the future, please use reportbug to file bugs!  The following form
letter explains why.

[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#279087 followup" 279087@bugs.debian.org < /tmp/output

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 <279087@bugs.debian.org>.

Thank you!

G. Branden Robinson                |      Intellectual property is neither
Debian GNU/Linux                   |      intellectual nor property.
branden@debian.org                 |      Discuss.
http://people.debian.org/~branden/ |      -- Linda Richman

Attachment: signature.asc
Description: Digital signature

Reply to: