| Summary: | sisimedia: Hard crash on Acer E261 Desktop | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Panos Christeas <xrg> |
| Component: | RPM Packages | Assignee: | Thierry Vignaud <thierry.vignaud> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | marja11, thierry.vignaud, tmb |
| Version: | 1 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | x11-driver-video-sisimedia-0.9.1-1.20091203.9.mga1.src.rpm | CVE: | |
| Status comment: | |||
| Attachments: | system dmesg + Xorg logs | ||
|
Description
Panos Christeas
2011-10-25 15:22:29 CEST
Created attachment 1008 [details]
system dmesg + Xorg logs
Panos Christeas
2011-10-25 15:26:08 CEST
Summary:
Hard crash on Acer E261 Desktop =>
sisimedia: Hard crash on Acer E261 Desktop Forgot to clarify: The problem occurs upon X startup, always. Tried to play around with the BIOS settings of display RAM (shared with system).
Manuel Hiebel
2011-10-26 00:52:57 CEST
CC:
(none) =>
thierry.vignaud, tmb We would need a GDB trace. Just boot without X11. Then enable the core/debug_release media/repository and install x11-server-debug, x11-driver-video-sisimedia-debug, glibc-debug packages Please download both https://bugs.mageia.org/attachment.cgi?id=121 and https://bugs.mageia.org/attachment.cgi?id=122 Then just run "sh ./Xgdb2.sh" on a text terminal as root (not from a terminal within X11!!! use Ctrl+Alt+F1), then switch back to X11 until it segfaults (Ctrl+Alt+F7). Alternatively you may try to run: service dm start && sleep 1 && gdb --pid $(pidof /etc/X11/X) Keywords:
(none) =>
NEEDINFO I'm afraid that might not work at all. We are talking about a hard freeze here, not just a segfault. As soon as the driver tries to access the hardware, the whole system is no more (next action: keep the power button pressed for a few sec.) Any tests will need remote debugging/log collection. In a few minutes, I will go to that customer (it's not my machine) again, to repeat the tests, with a newly compiled driver. It's possible that the x server has segfaulted but put the hardware in a bad state that prevent it so start again. It "just" prevent you from going back to console, so I hope that the automated script will get a trace. Else the odds are that the X process is only stuck. Then you should try to login remotely and attach a gdb to X to look at where it is and maybe also run strace on it in order to see what's it's doing. Well, AFAICT, the system was completely borked. I perform all my tests using a remote session (ssh), from where I start the X server etc. At the time of this bug report, the system would stop responding to ping, kbd frozen w/o the Oops blinking. ACPI power down wouldn't work either with the single tap of the button. However... Great news, Everybody! with a recompiled version of the 'sisimedia' driver, I was able to get an X session (modelines a bit scrambled, but I already had the 2008.1 config) and login. So far, I can kill the server by requesting Xv, this is a different bug, eventually. https://github.com/xrg/x11-driver-video-sisimedia (In reply to comment #6) > > However... > Great news, Everybody! > > with a recompiled version of the 'sisimedia' driver, I was able to get an X > session (modelines a bit scrambled, but I already had the 2008.1 config) and > login. So far, I can kill the server by requesting Xv, this is a different bug, > eventually. > > > https://github.com/xrg/x11-driver-video-sisimedia @ Panos Congrats with getting it to work and thanks for telling us. Closing Status:
NEW =>
RESOLVED That doesn't solve anything for mga... Status:
RESOLVED =>
REOPENED (In reply to comment #8) > That doesn't solve anything for mga... Assigning to maintainer, because I now understand that although it is impossible for the reporter of this bug to come up with the requested information, that the fact that the github driver works is good enough information to go by. (Does, btw, the fact that it works mean that it is now 100% sure it is a SiS 671/771 card? A reason for closing this report was, that is wasn't sure which video card was involved) Keywords:
NEEDINFO =>
(none) My apologies for not posting a few hours earlier.
The work on github is merely the series of patches needed to derive a working driver out of the loosely-maintained 'sisimedia' sources.
Binaries, as usual, are in:
http://members.hellug.gr/xrg/Mageia/1/RPMS/x86_64/
Since 26 Oct, this driver is in production and the users have not complained (I still believe the Xv bug exists).
But I wouldn't go into the torture of preparing them in SVN. It's silly. You know that.
Please look at the bottom of this mail to see whether you're the assignee of this bug, if you don't already know whether you are. If you're the assignee: We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead. If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard. Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why. Thanks :) **************************** @ the reporter and persons in the cc of this bug: If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us. @ the reporter of this bug If you didn't reply yet to a request for more information, please do so within two weeks from now. Thanks all :-D This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 1's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 1 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- Mageia Bugsquad Status:
REOPENED =>
RESOLVED |