Bug 720110 - kernel BUG at mm/huge_memory.c:1361
Summary: kernel BUG at mm/huge_memory.c:1361
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 15
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-09 14:06 UTC by John L Magee
Modified: 2011-09-26 20:43 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-09-26 20:43:50 UTC
Type: ---

Attachments (Terms of Use)
system log of incident (5.92 KB, text/plain)
2011-07-09 14:06 UTC, John L Magee 		no flags Details
/var/log/messages (6.36 KB, text/plain)
2011-07-10 20:51 UTC, Stanislaw Czech 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description John L Magee 2011-07-09 14:06:47 UTC 
Created attachment 512043 [details]
system log of incident

Description of problem: kernel BUG at mm/huge_memory.c:1361


Version-Release number of selected component (if applicable): 2.6.38.8-32.fc15.x86_64

How reproducible:Unknown

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Could not ssh or login from console. However the four KVM VMs continued to operate unimpaired.
Comment 1 Stanislaw Czech 2011-07-10 20:51:25 UTC 
Created attachment 512110 [details]
/var/log/messages
Comment 2 Stanislaw Czech 2011-07-10 20:52:17 UTC 
Same problem here. Just my KVM VM were down as well...
Comment 3 Josh Boyer 2011-09-26 20:00:48 UTC 
Does this still happen on the 2.6.40.x F15 kernels?
Comment 4 John L Magee 2011-09-26 20:34:34 UTC 
It has not occurred on kernel-2.6.40.4-5.fc15.x86_64 which we installed on 9/11/2011 but it only  happened once following this trouble report on the previous kernel.
Comment 5 Josh Boyer 2011-09-26 20:43:50 UTC 
OK, thank you for letting us know.  I'm going to close the bug out for now.  If you see it again, please reopen!
Note You need to log in before you can comment on or make changes to this bug.