- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- kernel: __alloc_pages: 0-order allocation failed.
Operating System - Linux
1822707
Members
3643
Online
109644
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-29-2004 08:36 PM
01-29-2004 08:36 PM
hello:
I am implementing a very critical system running on redhat 7.1 ,but I found a kernel error message "kernel: __alloc_pages: 0-order allocation failed." . Anybody knows how to solve this problem, patches or other.I check the redhat network, somebody also met the same situation before, but no one could reply this question. I also check the imformation in the internet, and find someone told that it's file
system problem but no solution. If you know how to solve this problem , please tell me .Thank you very much.
steven chang
I am implementing a very critical system running on redhat 7.1 ,but I found a kernel error message "kernel: __alloc_pages: 0-order allocation failed." . Anybody knows how to solve this problem, patches or other.I check the redhat network, somebody also met the same situation before, but no one could reply this question. I also check the imformation in the internet, and find someone told that it's file
system problem but no solution. If you know how to solve this problem , please tell me .Thank you very much.
steven chang
steven
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-29-2004 08:45 PM
01-29-2004 08:45 PM
Solution
This seems to be related to the virtual memory subsystem and you do have choices as to which system you choose. However, that will mean going with one of the trees not supported by Red Hat.
This is what Linus Torvalds has to say about it.
"These are bounce buffer allocations - they do fail, but the failures
should be temporary and the machine should make progress.
There are some nasty issues with HIGHMEM that will be seriously improved
during 2.5.x when we start doing IO directly from highmem for
controllers that can handle it, but that 2.4.x is not likely to really
fix. So you should expect to see messages like the above that are about
"we couldn't allocate memory for bounce buffers", and they _will_ imply
that performance isn't going to be as good as it possibly should be, but
at the same time it shouldn't be a real problem either."
It may get better with an upgrade in the 2.4 series but 2.6 (at all good shops now) seems to be your best bet.
This is what Linus Torvalds has to say about it.
"These are bounce buffer allocations - they do fail, but the failures
should be temporary and the machine should make progress.
There are some nasty issues with HIGHMEM that will be seriously improved
during 2.5.x when we start doing IO directly from highmem for
controllers that can handle it, but that 2.4.x is not likely to really
fix. So you should expect to see messages like the above that are about
"we couldn't allocate memory for bounce buffers", and they _will_ imply
that performance isn't going to be as good as it possibly should be, but
at the same time it shouldn't be a real problem either."
It may get better with an upgrade in the 2.4 series but 2.6 (at all good shops now) seems to be your best bet.
Never preceed any demonstration with anything more predictive than "watch this"
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP