| Summary: | kernel panic? | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Marton Kosa <kosamster> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | tmb |
| Version: | 4 | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
| Attachments: |
Mageia 4 crash image
Another crash image of Mageia 4 |
||
|
Description
Marton Kosa
2014-03-04 19:15:32 CET
David Walser
2014-03-04 19:18:34 CET
Component:
Security =>
RPM Packages Can you take a screenshot of the crash with a digital camera ? CC:
(none) =>
tmb Created attachment 5027 [details]
Mageia 4 crash image
Created attachment 5031 [details]
Another crash image of Mageia 4
(In reply to Marton Kosa from comment #3) The crash occurs also with other distributions. I have tried Mint and Sparky live dvd-s, both produce the error when launching web browsers (but not always...). The kernel 3.13 is suspicious. Mandriva 2010.2 with kernel 2.6.33.7 never produces the error, this weakens the idea that my hardware and/or NVIDIA software could be the culprit. Have you some idea about how to test Mageia 4 with older kernels? Or better to wait for a newer kernel? (In reply to Marton Kosa from comment #3) I guess the errpr characterizes kernels 3.10 through 3.15. Older kernels do not produce it. At last have i found a distro that addresses my problem. This is LinuxMint 17.1: «Solving freezes with some NVIDIA GeForce GPUs If you are unable to boot Linux Mint with an NVIDIA card, or if you are experiencing constant freezes and system lock ups, please append "nomodeset" to your boot arguments. At the boot menu of the live DVD/USB, press Tab to edit the boot arguments and add "nomodeset" at the end of the line. If you're still having issues, you can also remove "quiet splash --" from that same line. Alternatively you can use the "nouveau.noaccel=1" boot argument. Once the system is installed, use the Driver Manager to install the nvidia-304 driver.» See also: "https://bugzilla.kernel.org/show_bug.cgi?id=77841" Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. 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. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you 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. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 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. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/ As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/ Status:
NEW =>
RESOLVED |