| Summary: | Matrox MGA driver causes Kernel Pagefault | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Herbert Poetzl <herbert> |
| Component: | RPM Packages | Assignee: | Thomas Backlund <tmb> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | critical | ||
| Priority: | Normal | CC: | marja11, thierry.vignaud, tmb |
| Version: | 1 | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | kernel-2.6.38.8-5.mga1.src.rpm, x11-server-1.10.1-1.mga1.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Herbert Poetzl
2011-10-04 21:03:34 CEST
I don't know how to determinate for when it is :) Can you try that: https://bugs.mageia.org/show_bug.cgi?id=3183#c3 ? CC:
(none) =>
thierry.vignaud, tmb hmm, what exactly? a) recompiling the 'sisimedia' driver? I can do that, but as that driver is not involed, I don't think it will help b) run "sh ./Xgdb2.sh" I can do that as well, but it won't help when the kernel panics. c) something I missed please clarify (In reply to comment #1) > I don't know how to determinate for when it is :) > > Can you try that: https://bugs.mageia.org/show_bug.cgi?id=3183#c3 ? (In reply to comment #2) > hmm, what exactly? > > a) recompiling the 'sisimedia' driver? > I can do that, but as that driver is not involed, I don't think it will help > > b) run "sh ./Xgdb2.sh" > I can do that as well, but it won't help when the kernel panics. > > c) something I missed > please clarify He referred to comment 3 of bug 3183, so this is about getting a backtrace, just use the x11-driver-video-mga-debug instead of x11-driver-video-sisimedia-debug. And please add the debug package for the kernel you use, too. Feel free to add more debug packages if you think they are useful. You probably know better what to choose than I do. And for the rest, don't forget to install gdb, do as Thierry described and make your system crash. If this bug is still valid, and the version numbers of involved packages changed since you filed it, please change the version numbers to the correct ones. Keywords:
(none) =>
NEEDINFO and of course, a kernel panic will make it impossible to get anything, I agree with that, but what other options are there... what is the use of having a kernel debug package, if you can't ever use it? there is a kernel debug package? I'm curious what it contains, but I couldn't find one with: urpmf --filename kernel | grep debug regarding the test script/gdb, I guess I can do that, as the kernel trace is not critical (i.e. not a panic) (will do as soon as I get around) (In reply to comment #5) > there is a kernel debug package? For the kernel I currently have in "1", there is: kernel-desktop-2.6.38.8-6.mga-debug
> I'm curious what it contains, but I couldn't find one with:
> urpmf --filename kernel | grep debug
>
For me, that command works.
Did you add the debug repositories?
Thierry Vignaud
2011-12-29 19:42:47 CET
Assignee:
bugsquad =>
tmb (In reply to comment #5) > there is a kernel debug package? > I'm curious what it contains, but I couldn't find one with: > urpmf --filename kernel | grep debug > > regarding the test script/gdb, I guess I can do that, as the kernel trace is > not critical (i.e. not a panic) > (will do as soon as I get around) @ Herbert Did you get around to doing it? not yet, I forgot to do that last time I was near that machine :( next chance will be in roughly two weeks AFAICT Could you also check Mageia 2 alpha3 in order to see if it works better with a newer kernel? (In reply to comment #9) > next chance will be in roughly two weeks AFAICT Did you have that chance? (for gdb trace and check Mga2a3?) unfortunately no, otherwise I would have come back to you with the requested data. (In reply to comment #11) > (In reply to comment #9) > > > next chance will be in roughly two weeks AFAICT > > Did you have that chance? (for gdb trace and check Mga2a3?) (In reply to comment #12) > unfortunately no, otherwise I would have come back to you with the requested > data. make that Mga2b1 closing as old for now, please reopen when you have the requested information again: closing as old for now, please reopen when you have the requested information Status:
NEW =>
RESOLVED |