Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 485238

Summary: net-fs/openafs-1.6.2-r1 causes kernel panic after waking from sleep for 3rd time
Product: Gentoo Linux Reporter: Colleen <cjoseph>
Component: [OLD] ServerAssignee: Andrej Filipcic <andrej.filipcic>
Status: RESOLVED TEST-REQUEST    
Severity: normal CC: bircoph, net-fs, proxy-maint
Priority: Normal    
Version: unspecified   
Hardware: AMD64   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: kernel config
image of kernel panic

Description Colleen 2013-09-17 19:47:48 UTC
Created attachment 358894 [details]
kernel config

After waking the system from sleep for a third time and then performing "aklog <cell>", the machine kernel panics and I must reboot. Works as expected after first and second sleep, as well as after rebooting.

I have not tried more recent versions, as they do not compile, but since this issue has popped up I'll try and get a more recent version running.

Running kernel 3.8.13 on an x86_64 machine.

Kernel config and a photo of the kernel panic are attached.
Comment 1 Ian Stakenvicius (RETIRED) gentoo-dev 2013-09-17 19:51:18 UTC
On an unrelated note, could you open a bug regarding the compilation failures you're getting with the newer version?  is the compilation failure in openafs or openafs-kernel?  

Also, back to this bug, is the kernel panic due to openafs or openafs-kernel, or both?
Comment 2 Colleen 2013-09-17 19:51:41 UTC
Created attachment 358896 [details]
image of kernel panic
Comment 3 Colleen 2013-09-17 19:54:44 UTC
(In reply to Ian Stakenvicius from comment #1)
> On an unrelated note, could you open a bug regarding the compilation
> failures you're getting with the newer version?  is the compilation failure
> in openafs or openafs-kernel?  
> 
> Also, back to this bug, is the kernel panic due to openafs or
> openafs-kernel, or both?

I will add a bug about the compilation failure.

As far as openafs vs openafs-kernel causing the panic, I'm not sure. I just attached an image of the panic. The panic happens right after I execute 'aklog' and the panic message has 'afs' in it a number of times.
Comment 4 Colleen 2013-09-17 20:01:45 UTC
(In reply to Colleen from comment #3)
> (In reply to Ian Stakenvicius from comment #1)
> > On an unrelated note, could you open a bug regarding the compilation
> > failures you're getting with the newer version?  is the compilation failure
> > in openafs or openafs-kernel?  
> > 
> > Also, back to this bug, is the kernel panic due to openafs or
> > openafs-kernel, or both?
> 
> I will add a bug about the compilation failure.
> 
> As far as openafs vs openafs-kernel causing the panic, I'm not sure. I just
> attached an image of the panic. The panic happens right after I execute
> 'aklog' and the panic message has 'afs' in it a number of times.
Comment 5 Colleen 2013-09-17 20:34:59 UTC
(In reply to Colleen from comment #4)
> (In reply to Colleen from comment #3)
> > (In reply to Ian Stakenvicius from comment #1)
> > > On an unrelated note, could you open a bug regarding the compilation
> > > failures you're getting with the newer version?  is the compilation failure
> > > in openafs or openafs-kernel?  
> > > 
> > > Also, back to this bug, is the kernel panic due to openafs or
> > > openafs-kernel, or both?
> > 
> > I will add a bug about the compilation failure.
> > 
> > As far as openafs vs openafs-kernel causing the panic, I'm not sure. I just
> > attached an image of the panic. The panic happens right after I execute
> > 'aklog' and the panic message has 'afs' in it a number of times.

It's the openafs causing the compile error, not openafs-kernel.

https://bugs.gentoo.org/show_bug.cgi?id=485240
Comment 6 Andrej Filipcic 2013-09-19 05:40:52 UTC
the kernel 3.8 patches were not very stable at the time of release. openafs-1.6.5 should be used for kernels >=3.8.
Comment 7 Andrew Savchenko gentoo-dev 2015-03-22 21:20:42 UTC
Please test with 1.6.11 version.
Comment 8 Andrew Savchenko gentoo-dev 2015-05-01 08:44:38 UTC
Feel free to reopen if the issue is still present in 1.6.11.