Bug 3360

Created attachment 1066 [details]
picture of the screen after kernel panic

Hi, thanks for reporting this bug.

can you attach the output of lspcidrake -v and lsmod ?

(don't know what other to ask :/ )

(also added the kernel maintainer)

Assignee: bugsquad => tmb
Source RPM: (none) => kernel

Created attachment 1070 [details]
lsmod

Created attachment 1071 [details]
lspcidrake -v

I should have mentioned that with the previous kernel (2.6.38.8-desktop-6.mga) everything goes fine :)

Hello,

I still have the kernel panic with the last kernel (kernel-desktop-2.6.38.8-9.mga-1-1.mga1)

Is there something I could try ?

(In reply to comment #6)
> Hello,
> 
> I still have the kernel panic with the last kernel
> (kernel-desktop-2.6.38.8-9.mga-1-1.mga1)
> 
> Is there something I could try ?

I have the same bug with kernel-desktop 2.6.38.8-9 but did not have it with kernel-desktop 2.6.38.8-8. Right now 2.6.38.8-8 is fine but system will not boot with 2.6.38.8-9. 
Kernel panic - not syncing. File system load error.
This is with the 32 bit version of Mageia 1.0 and occurred after an update.

CC: (none) => raymac46

Created attachment 1337 [details]
lsmod

Created attachment 1338 [details]
lspcidrake -v

(In reply to comment #7)
> (In reply to comment #6)
> > Hello,
> > 
> > I still have the kernel panic with the last kernel
> > (kernel-desktop-2.6.38.8-9.mga-1-1.mga1)
> > 
> > Is there something I could try ?
> 
> I have the same bug with kernel-desktop 2.6.38.8-9 but did not have it with
> kernel-desktop 2.6.38.8-8. Right now 2.6.38.8-8 is fine but system will not
> boot with 2.6.38.8-9. 
> Kernel panic - not syncing. File system load error.
> This is with the 32 bit version of Mageia 1.0 and occurred after an update.

Now all seems to be OK for me. Reinstall using the graphical MCC instead of the terminal and making sure kernel-desktop-latest was installed appears to have fixed the problem in my case.

I tried to reinstall with mcc, but no luck :(

any idea ?

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: NEW => RESOLVED
Resolution: (none) => WONTFIX