Bug 1329

Summary: Kernel oops noticed since some days with kernel 2.6.38.6
Product: Mageia Reporter: John Balcaen <balcaen.john>
Component: RPM PackagesAssignee: Thomas Backlund <tmb>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Normal CC: thierry.vignaud
Version: Cauldron   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: kernel-2.6.38.6-1.mga1.src.rpm CVE:
Status comment:
Attachments: oops in dmesg
Dmidecode
lspcidrake -v
lsmod

Description John Balcaen 2011-05-18 11:47:15 CEST 
Description of problem:
I noticed since some days several days of oops with 2.6.38.6
You can find attached the oops,the lspcidrake -v , dmidecode

Version-Release number of selected component (if applicable):
uname -a                                                                                                                              
Linux hatmehyt.lan.littleboboy.net 2.6.38.6-desktop-1.mga #1 SMP Tue May 10 20:30:06 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux   

How reproducible:
sometimes

Steps to Reproduce:
it happened yesterday night @22h01 just after an backup rsync.
Comment 1 John Balcaen 2011-05-18 11:47:37 CEST 
Created attachment 414 [details]
oops in dmesg
Comment 2 John Balcaen 2011-05-18 11:48:02 CEST 
Created attachment 415 [details]
Dmidecode
Comment 3 John Balcaen 2011-05-18 11:48:39 CEST 
Created attachment 416 [details]
lspcidrake -v
Comment 4 John Balcaen 2011-05-18 11:51:06 CEST 
Let me know if there's something i can do to narrow it eventually.
I don't know if it's related but i noticed an other oops two days ago & after i add a corruption of my ext4 /home.
It does not seems related to a hdd problem since others partition on the hdd were not corrupted.
By corruption i mean that after boot i was asked for a fsck for /home which never ends.

Regards,
Comment 5 John Balcaen 2011-05-18 11:54:32 CEST 
The rsync is done over an nfs host (a Qnap TS210 if it can help)
Comment 6 John Balcaen 2011-05-18 11:55:04 CEST 
Created attachment 417 [details]
lsmod
Thierry Vignaud 2011-05-18 15:55:37 CEST

CC: (none) => thierry.vignaud
Assignee: bugsquad => tmb

Comment 7 Thomas Backlund 2011-05-21 22:11:43 CEST 
Is this still an issue with 2.6.38.6-2 ?
Comment 8 John Balcaen 2011-06-01 14:37:29 CEST 
Nop it's fixed

Status: NEW => RESOLVED
Resolution: (none) => FIXED