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

Bug#771387: marked as done (siliconmotion graphic card driver segfault and unusable.)

Your message dated Sat, 30 Apr 2016 10:10:22 +0000
with message-id <1462011022.5024.1.camel@gmail.com>
and subject line bug fixed in sid, submitter cannot reproduce this bug, hence closing
has caused the Debian Bug report #771387,
regarding siliconmotion graphic card driver segfault and unusable.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
771387: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771387
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: xserver-xorg-video-siliconmotion
Source: xserver-xorg-video-siliconmotion (1:1.7.7-2)
Version: 1:1.7.7-2+b2
Severity: serious
Tags: moreinfo

Hi,

The xserver-xorg-video-siliconmotion segfaults right away once I started
X, and then the X is totally unuseable on my machine (mipsel,
loongson-2f).

```
(==) Log file: "/var/log/Xorg.0.log", Time: Sat Nov 29 11:07:18 2014
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(EE) 
(EE) Backtrace:
(EE) 0: X (xorg_backtrace+0x84) [0x77e2ede4]
(EE) 
(EE) Segmentation fault at address 0x3c4
(EE) 
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE) 
(EE) 
```

I have read http://x.debian.net/howto/use-gdb.html and
http://x.debian.net/howto/report-bugs.html
but I feel hard to generate coredump/backtrace,
as I'm not familiar with gdb.

This issue also affects debian wheezy (even the save segfault addr).
And another useful information is,
someone fixed this problem and put that fixed version (1.7.6-1loongson)
onto a forum, it works indeed. I can send that fix privately.[1]

And then, what "moreinfo" should I exactly offer?
P.S. the /var/log/Xorg.0.log seems doesn't help, so not attached.

thanks:)

[1] I tried to apply that fix for jessie, but ABI's not happy.
-- 
Regards,
  C.D.Luminate

--- End Message ---
--- Begin Message --- 
bug fixed in sid, submitter cannot reproduce this bug, hence closing

--- End Message ---
Reply to: