search for: freepage

Hi, Since we upgraded our server to 3.6, it runs out of memory. This is what I can find in syslog (multiple similar entries): Dec 7 19:52:42 gcclo77 kernel: Out of Memory: Killed process 31375 (nagios). Dec 7 19:52:43 gcclo77 kernel: Mem-info: Dec 7 19:52:43 gcclo77 kernel: Zone:DMA freepages: 2927 min: 0 low: 0 high: 0 Dec 7 19:52:43 gcclo77 kernel: Zone:Normal freepages: 737 min: 766 low: 4031 high: 5791 Dec 7 19:52:43 gcclo77 kernel: Zone:HighMem freepages: 126 min: 255 low: 510 high: 765 Dec 7 19:52:43 gcclo77 kernel: Free pages: 3790 ( 126...

...y, and allocate again. the test result shows 12948535073500: XenPCI --- AllocatePages IRQL = 0, Buf = FFFFFA8000000000 12948535073500: XenPCI XEN_INIT_TYPE_RING - tx-ring-ref = FFFFFA8000000000 12948535073500: XenPCI test - tx-ring-ref = 18446738026395598848 12948535073515: XenPCI --- FreePages IRQL = 0, Buf = FFFFFA8000000000 12948535073515: XenPCI FreePages 1 12948535073515: XenPCI FreePages 2 Log-dirty command enable Log-dirty command disable XenPCI Bug check 0x000000C2 (0x0000000000000042, 0xFFFFFA8000000000, 0x0000000000000000, 0x0000000000000000) reset requested in cpu_handle_i...

...blem. Recently, I thought the network load was filling the physical memory because the error was usually a "Unable to handle kernel virtual memory paging request," however, I have tried both stock kernels and RH kernels with the rmap VM system and both crash. I also increased /proc/sys/vm/freepages to such large numbers that there was always over a meg of free mem while a file transfer was going, but the box still crashed. The stack dump used to be from many different programs, but, after I increased freepages, it seems to always be from the 3c59x module. I have tried 3com's driver i...

I'm very sorry about posting HTML. I know better then that and should have double checked my defaults. I'm reposting this hoping someone Is there a known bug that samba has on older machines in low memory environments? I have set up a 486 with 24Mb of memory with RedHat 7.1. I set it up to run dhcpd, xinetd, and samba. Samba was not run through xinetd. The samba server had a tendency

I have a 2 node cluster of HP DL380G4s. These machines are attached via scsi to an external HP disk enclosure. They run 32bit RH AS 4.0 and OCFS 1.2.4, the latest release. They were upgraded from 1.2.3 only a few days after 1.2.4 was released. I had reported on the mailing list that my developers were happy, and things seemed faster. However, twice in that time, the cluster has gone down due

...> need to test more, can't confidently answer now. > > > How easy can you reprodcue it? Could you bisect it? > > it takes some (um.. random) time to trigger the bug. > I'll try to come up with more details. Could you revert [1] and retest? [1] mm/compaction: split freepages without holding the zone lock > > -ss > > > > kernel: flags: 0x8000000000000000() > > > kernel: page dumped because: nonzero mapcount > > > kernel: Modules linked in: lzo zram zsmalloc mousedev coretemp hwmon crc32c_intel snd_hda_codec_realtek i2c_i801 snd_h...

...> need to test more, can't confidently answer now. > > > How easy can you reprodcue it? Could you bisect it? > > it takes some (um.. random) time to trigger the bug. > I'll try to come up with more details. Could you revert [1] and retest? [1] mm/compaction: split freepages without holding the zone lock > > -ss > > > > kernel: flags: 0x8000000000000000() > > > kernel: page dumped because: nonzero mapcount > > > kernel: Modules linked in: lzo zram zsmalloc mousedev coretemp hwmon crc32c_intel snd_hda_codec_realtek i2c_i801 snd_h...

...> How easy can you reprodcue it? Could you bisect it? > > > > > > it takes some (um.. random) time to trigger the bug. > > > I'll try to come up with more details. > > > > Could you revert [1] and retest? > > > > [1] mm/compaction: split freepages without holding the zone lock > > ok, so this is not related to zsmalloc. finally manged to reproduce > it. will fork a separate thread. The reason I mentioned [1] is that it seems to have a bug. isolate_freepages_block __isolate_free_page if(!zone_watermark_ok()) return 0;...

...> How easy can you reprodcue it? Could you bisect it? > > > > > > it takes some (um.. random) time to trigger the bug. > > > I'll try to come up with more details. > > > > Could you revert [1] and retest? > > > > [1] mm/compaction: split freepages without holding the zone lock > > ok, so this is not related to zsmalloc. finally manged to reproduce > it. will fork a separate thread. The reason I mentioned [1] is that it seems to have a bug. isolate_freepages_block __isolate_free_page if(!zone_watermark_ok()) return 0;...

...0x37c [<f8862806>] kjournald [jbd] 0x136 [<f88626b0>] commit_timeout [jbd] 0x0 [<c0107286>] kernel_thread [kernel] 0x26 [<f88626d0>] kjournald [jbd] 0x0 sysrq memory/registers shows: SysRq : Show Memory Mem-info: Free pages: 383780kB (353072kB HighMem) Zone:DMA freepages: 5792kB min: 4224kB low: 4352kB high: 4480kB Zone:Normal freepages: 24916kB min: 5116kB low: 18176kB high: 25216kB Zone:HighMem freepages:353072kB min: 1020kB low: 49144kB high: 73716kB Free pages: 383780kB (353072kB HighMem) ( Active: 473457, inactive_dirty: 82051, inactive_clean: 1857...

.../Locking b/Documentation/filesystems/Locking > index 619af9bfdcb3..0bb79560abb3 100644 > --- a/Documentation/filesystems/Locking > +++ b/Documentation/filesystems/Locking > @@ -195,7 +195,9 @@ unlocks and drops the reference. > int (*releasepage) (struct page *, int); > void (*freepage)(struct page *); > int (*direct_IO)(struct kiocb *, struct iov_iter *iter, loff_t offset); > + bool (*isolate_page) (struct page *, isolate_mode_t); > int (*migratepage)(struct address_space *, struct page *, struct page *); > + void (*putback_page) (struct page *); > int (*lau...

.../Locking b/Documentation/filesystems/Locking > index 619af9bfdcb3..0bb79560abb3 100644 > --- a/Documentation/filesystems/Locking > +++ b/Documentation/filesystems/Locking > @@ -195,7 +195,9 @@ unlocks and drops the reference. > int (*releasepage) (struct page *, int); > void (*freepage)(struct page *); > int (*direct_IO)(struct kiocb *, struct iov_iter *iter, loff_t offset); > + bool (*isolate_page) (struct page *, isolate_mode_t); > int (*migratepage)(struct address_space *, struct page *, struct page *); > + void (*putback_page) (struct page *); > int (*lau...

This patchset follows the main idea discussed at 2012 LSFMMS section: "Ballooning for transparent huge pages" -- http://lwn.net/Articles/490114/ to introduce the required changes to the virtio_balloon driver, as well as changes to the core compaction & migration bits, in order to allow memory balloon pages become movable within a guest. Rafael Aquini (4): mm: introduce compaction

This patchset follows the main idea discussed at 2012 LSFMMS section: "Ballooning for transparent huge pages" -- http://lwn.net/Articles/490114/ to introduce the required changes to the virtio_balloon driver, as well as changes to the core compaction & migration bits, in order to allow memory balloon pages become movable within a guest. Rafael Aquini (4): mm: introduce compaction

...index 619af9bfdcb3..0bb79560abb3 100644 > > > --- a/Documentation/filesystems/Locking > > > +++ b/Documentation/filesystems/Locking > > > @@ -195,7 +195,9 @@ unlocks and drops the reference. > > > int (*releasepage) (struct page *, int); > > > void (*freepage)(struct page *); > > > int (*direct_IO)(struct kiocb *, struct iov_iter *iter, loff_t offset); > > > + bool (*isolate_page) (struct page *, isolate_mode_t); > > > int (*migratepage)(struct address_space *, struct page *, struct page *); > > > + void (*putback...

...index 619af9bfdcb3..0bb79560abb3 100644 > > > --- a/Documentation/filesystems/Locking > > > +++ b/Documentation/filesystems/Locking > > > @@ -195,7 +195,9 @@ unlocks and drops the reference. > > > int (*releasepage) (struct page *, int); > > > void (*freepage)(struct page *); > > > int (*direct_IO)(struct kiocb *, struct iov_iter *iter, loff_t offset); > > > + bool (*isolate_page) (struct page *, isolate_mode_t); > > > int (*migratepage)(struct address_space *, struct page *, struct page *); > > > + void (*putback...

...it a/Documentation/filesystems/Locking b/Documentation/filesystems/Locking index 619af9bfdcb3..0bb79560abb3 100644 --- a/Documentation/filesystems/Locking +++ b/Documentation/filesystems/Locking @@ -195,7 +195,9 @@ unlocks and drops the reference. int (*releasepage) (struct page *, int); void (*freepage)(struct page *); int (*direct_IO)(struct kiocb *, struct iov_iter *iter, loff_t offset); + bool (*isolate_page) (struct page *, isolate_mode_t); int (*migratepage)(struct address_space *, struct page *, struct page *); + void (*putback_page) (struct page *); int (*launder_page)(struct page *)...

...it a/Documentation/filesystems/Locking b/Documentation/filesystems/Locking index 619af9bfdcb3..0bb79560abb3 100644 --- a/Documentation/filesystems/Locking +++ b/Documentation/filesystems/Locking @@ -195,7 +195,9 @@ unlocks and drops the reference. int (*releasepage) (struct page *, int); void (*freepage)(struct page *); int (*direct_IO)(struct kiocb *, struct iov_iter *iter, loff_t offset); + bool (*isolate_page) (struct page *, isolate_mode_t); int (*migratepage)(struct address_space *, struct page *, struct page *); + void (*putback_page) (struct page *); int (*launder_page)(struct page *)...

Memory fragmentation introduced by ballooning might reduce significantly the number of 2MB contiguous memory blocks that can be used within a guest, thus imposing performance penalties associated with the reduced number of transparent huge pages that could be used by the guest workload. This patch-set follows the main idea discussed at 2012 LSFMMS session: "Ballooning for transparent huge

Memory fragmentation introduced by ballooning might reduce significantly the number of 2MB contiguous memory blocks that can be used within a guest, thus imposing performance penalties associated with the reduced number of transparent huge pages that could be used by the guest workload. This patch-set follows the main idea discussed at 2012 LSFMMS session: "Ballooning for transparent huge