Bug 1050990

Summary:	cannot allocate memory with kernels 3.12.5-200.fc19.x86_64 and 3.12.6-200.fc19.x86_64
Product:	[Fedora] Fedora	Reporter:	Amata <m_amata>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	19	CC:	gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, trevor
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-03-10 18:09:34 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Amata 2014-01-09 13:23:16 UTC

Description of problem:

cannot allocate memory with kernels 3.12.5-200.fc19.x86_64 and 3.12.6-200.fc19.x86_64

Version-Release number of selected component (if applicable):

kernels 3.12.5-200.fc19.x86_64 and 3.12.6-200.fc19.x86_64

How reproducible:

Using the software GAIA - Graphical Astronomy and Image Analysis Tool

Steps to Reproduce:
1. open the gaia tool
2. load an image and a catalog (my image contains 12kx12k pixel and the catalog has more than 50000 detections) 
3. use the tool Image-Analysis --> positions --> select positions and grab the loaded catalog

Actual results:
Gaia crash with the following error: cannot allocate memory

Expected results:
By using kernel 3.11.10-200.fc19.x86_64 the softwar load positions

Additional info:
with kernels 3.11.10-200.fc19.x86_64 and older this problem is not present.

Comment 1 Trevor Cordes 2014-02-13 11:53:38 UTC

Maybe related to bug #1064076.  If so, perhaps merged discussion there.

Comment 2 Amata 2014-02-13 12:56:56 UTC

You are right, The two bugs are related. Do you know I can I merge the two bugs?

Comment 3 Trevor Cordes 2014-02-13 13:04:07 UTC

No idea, I can never make bugzilla do what I want.  I think perhaps only admins can do stuff like that.  Often it is sufficient to make a note in a comment to close this bug or merge with the other.  I've already made a note in the other so people will see the cross-reference and can view this bug.

I would hold off for a brief while until you/we are sure they are the same bug, though so far it looks quite promising.  Try to trigger the bug and do the tests I mention in the other bug, I'm curious to see what you get.  Also perhaps try to capture:

mkdir /tmp/OOM
cat /sys/kernel/debug/frontswap/*       > /tmp/OOM/frontswap
cat /proc/meminfo                       > /tmp/OOM/meminfo
cat /proc/vmstat                        > /tmp/OOM/vmstat

(use a non-/tmp dir if your /tmp is tmpfs, ie not a real, non-volatile disk)

Comment 4 Amata 2014-02-13 13:07:14 UTC

OK! 
I will make tests you suggest, thanks!

Comment 5 Justin M. Forbes 2014-03-10 14:50:12 UTC

*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs.

Fedora 19 has now been rebased to 3.13.5-100.fc19.  Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you experience different issues, please open a new bug report for those.

Comment 6 Amata 2014-03-10 17:46:37 UTC

Dear Justin,

with the new release 3.13.5-100.fc19 the issue has been resolved!

Thank you,
Amata

Comment 7 Josh Boyer 2014-03-10 18:09:34 UTC

Thanks.