[x]
Posted via EE Mobile

Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again.
11/02/2007 at 11:09AM PDT, ID: 22935516
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!
9.8

Backup Data Transfer causes NIC messages?

Asked by e_sandrs in Linux Administration, Backup & Restore Software, Network Cards & Adapters

Tags: 0, suse

We're getting pretty much a "continuous flood" of the informational message below on a SUSE OpenLinux box running the CA BrightStor ArcServe 11.5 SP3 client and communicating with a Windows box running the full version of ArcServe (same version and patch level).

Anyone have any ideas on how to diagnose or fix this?  More info as requested...
-----------------------
The following is only an harmless informational message.
Unless you get a _continuous_flood_ of these messages it means
everything is working fine. Allocations from irqs cannot be
perfectly reliable and the kernel is designed to handle that.
swapper: page allocation failure. order:0, mode:0x20

Call Trace:
 <IRQ> [<ffffffff8020dc1e>] __alloc_pages+0x2d8/0x2f1
 [<ffffffff80215375>] cache_grow+0x137/0x343
 [<ffffffff802573fd>] cache_alloc_refill+0x17e/0x1cc
 [<ffffffff802bdf50>] __kmalloc+0x95/0x9f
 [<ffffffff8022c3ac>] __alloc_skb+0x5c/0x123
 [<ffffffff80395011>] __netdev_alloc_skb+0x12/0x2d
 [<ffffffff88173238>] :e1000:e1000_alloc_rx_buffers+0xf8/0x380
 [<ffffffff881739c6>] :e1000:e1000_clean_rx_irq+0x506/0x540
 [<ffffffff88172414>] :e1000:e1000_clean+0x84/0x2c0
 [<ffffffff8020b9a2>] net_rx_action+0xa4/0x1b0
 [<ffffffff8020fef1>] __do_softirq+0x5e/0xd5
 [<ffffffff8031db46>] end_msi_irq_wo_maskbit+0x9/0x16
 [<ffffffff802591e4>] call_softirq+0x1c/0x28
 [<ffffffff80265da2>] do_softirq+0x2c/0x7d
 [<ffffffff80265d6d>] do_IRQ+0x6a/0x73
 [<ffffffff80252cae>] mwait_idle+0x0/0x4a
 [<ffffffff80258509>] ret_from_intr+0x0/0xa
 <EOI> [<ffffffff80252ce4>] mwait_idle+0x36/0x4a
 [<ffffffff802451ba>] cpu_idle+0x95/0xb8
 [<ffffffff805da7a3>] start_kernel+0x21b/0x220
 [<ffffffff805da28a>] _sinittext+0x28a/0x28e

Mem-info:
Node 0 DMA per-cpu:
cpu 0 hot: high 0, batch 1 used:0
cpu 0 cold: high 0, batch 1 used:0
cpu 1 hot: high 0, batch 1 used:0
cpu 1 cold: high 0, batch 1 used:0
Node 0 DMA32 per-cpu:
cpu 0 hot: high 186, batch 31 used:30
cpu 0 cold: high 62, batch 15 used:51
cpu 1 hot: high 186, batch 31 used:20
cpu 1 cold: high 62, batch 15 used:10
Node 0 Normal per-cpu: empty
Node 0 HighMem per-cpu: empty
Free pages:        3804kB (0kB HighMem)
Active:195589 inactive:295150 dirty:57148 writeback:1 unstable:0 free:951 slab:18829 mapped:4486 pagetables:524
Node 0 DMA free:1756kB min:32kB low:40kB high:48kB active:0kB inactive:0kB present:11572kB pages_scanned:0 all_unreclaimable? yes
lowmem_reserve[]: 0 2000 2000 2000
Node 0 DMA32 free:2048kB min:5704kB low:7128kB high:8556kB active:782356kB inactive:1180600kB present:2048920kB pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 0 0 0
Node 0 Normal free:0kB min:0kB low:0kB high:0kB active:0kB inactive:0kB present:0kB pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 0 0 0
Node 0 HighMem free:0kB min:128kB low:128kB high:128kB active:0kB inactive:0kB present:0kB pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 0 0 0
Node 0 DMA: 3*4kB 4*8kB 3*16kB 2*32kB 1*64kB 2*128kB 1*256kB 0*512kB 1*1024kB 0*2048kB 0*4096kB = 1756kB
Node 0 DMA32: 0*4kB 0*8kB 0*16kB 0*32kB 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 1*2048kB 0*4096kB = 2048kB
Node 0 Normal: empty
Node 0 HighMem: empty
Swap cache: add 31, delete 31, find 0/0, race 0+0
Free swap  = 4008056kB
Total swap = 4008176kB
Free swap:       4008056kB
524032 pages of RAM
9707 reserved pages
398871 pages shared
0 pages swap cached
The following is only an harmless informational message.
Unless you get a _continuous_flood_ of these messages it means
everything is working fine. Allocations from irqs cannot be
perfectly reliable and the kernel is designed to handle that.
klogd: page allocation failure. order:0, mode:0x20

Call Trace:
 <IRQ> [<ffffffff8020dc1e>] __alloc_pages+0x2d8/0x2f1
 [<ffffffff80215375>] cache_grow+0x137/0x343
 [<ffffffff802573fd>] cache_alloc_refill+0x17e/0x1cc
 [<ffffffff802bdf50>] __kmalloc+0x95/0x9f
 [<ffffffff8022c3ac>] __alloc_skb+0x5c/0x123
 [<ffffffff80395011>] __netdev_alloc_skb+0x12/0x2d
 [<ffffffff88173238>] :e1000:e1000_alloc_rx_buffers+0xf8/0x380
 [<ffffffff88173965>] :e1000:e1000_clean_rx_irq+0x4a5/0x540
 [<ffffffff88172414>] :e1000:e1000_clean+0x84/0x2c0
 [<ffffffff8020b9a2>] net_rx_action+0xa4/0x1b0
 [<ffffffff8020fef1>] __do_softirq+0x5e/0xd5
 [<ffffffff8031db46>] end_msi_irq_wo_maskbit+0x9/0x16
 [<ffffffff802591e4>] call_softirq+0x1c/0x28
 [<ffffffff80265da2>] do_softirq+0x2c/0x7d
 [<ffffffff80265d6d>] do_IRQ+0x6a/0x73
 [<ffffffff80258509>] ret_from_intr+0x0/0xa
 <EOI> [<ffffffff80284338>] do_syslog+0x173/0x3be
 [<ffffffff8028434f>] do_syslog+0x18a/0x3be
 [<ffffffff80292876>] autoremove_wake_function+0x0/0x2e
 [<ffffffff802e5105>] kmsg_read+0x3a/0x44
 [<ffffffff8020a9d1>] vfs_read+0xcb/0x171
 [<ffffffff8020f72f>] sys_read+0x45/0x6e
 [<ffffffff8025800e>] system_call+0x7e/0x83

Mem-info:
Node 0 DMA per-cpu:
cpu 0 hot: high 0, batch 1 used:0
cpu 0 cold: high 0, batch 1 used:0
cpu 1 hot: high 0, batch 1 used:0
cpu 1 cold: high 0, batch 1 used:0
Node 0 DMA32 per-cpu:
cpu 0 hot: high 186, batch 31 used:30
cpu 0 cold: high 62, batch 15 used:51
cpu 1 hot: high 186, batch 31 used:20
cpu 1 cold: high 62, batch 15 used:10
Node 0 Normal per-cpu: empty
Node 0 HighMem per-cpu: empty
Free pages:        3804kB (0kB HighMem)
Active:195589 inactive:295150 dirty:57148 writeback:1 unstable:0 free:951 slab:18829 mapped:4486 pagetables:524
Node 0 DMA free:1756kB min:32kB low:40kB high:48kB active:0kB inactive:0kB present:11572kB pages_scanned:0 all_unreclaimable? yes
lowmem_reserve[]: 0 2000 2000 2000
Node 0 DMA32 free:2048kB min:5704kB low:7128kB high:8556kB active:782356kB inactive:1180600kB present:2048920kB pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 0 0 0
Node 0 Normal free:0kB min:0kB low:0kB high:0kB active:0kB inactive:0kB present:0kB pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 0 0 0
Node 0 HighMem free:0kB min:128kB low:128kB high:128kB active:0kB inactive:0kB present:0kB pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 0 0 0
Node 0 DMA: 3*4kB 4*8kB 3*16kB 2*32kB 1*64kB 2*128kB 1*256kB 0*512kB 1*1024kB 0*2048kB 0*4096kB = 1756kB
Node 0 DMA32: 0*4kB 0*8kB 0*16kB 0*32kB 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 1*2048kB 0*4096kB = 2048kB
Node 0 Normal: empty
Node 0 HighMem: empty
Swap cache: add 31, delete 31, find 0/0, race 0+0
Free swap  = 4008056kB
Total swap = 4008176kB
Free swap:       4008056kB
524032 pages of RAM
9707 reserved pages
398871 pages shared
0 pages swap cached
[+][-]11/02/07 11:31 AM, ID: 20203279

View this solution now by starting your 30-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zones: Linux Administration, Backup & Restore Software, Network Cards & Adapters
Tags: 0, suse
Sign Up Now!
Solution Provided By: ravenpl
Participating Experts: 2
Solution Grade: A
 
 
[+][-]11/02/07 12:06 PM, ID: 20203512

Assisted solutions are selected by the member who asked the question as a comment that contributed to their question's solution.

Start your 30-day free trial to view this Assisted Solution or ask the Experts your question.

 
[+][-]11/02/07 12:07 PM, ID: 20203518

Often, when Experts are collaborating with members who have asked questions, they will request additional information about the problem. Askers respond with an author comment like this one.

Start your 30-day free trial to view this Author Comment or ask the Experts your question.

 
[+][-]11/02/07 12:12 PM, ID: 20203562

Often, when Experts are collaborating with members who have asked questions, they will request additional information about the problem. Askers respond with an author comment like this one.

Start your 30-day free trial to view this Author Comment or ask the Experts your question.

 
[+][-]11/20/07 06:41 AM, ID: 20319966

Often, when Experts are collaborating with members who have asked questions, they will request additional information about the problem. Askers respond with an author comment like this one.

Start your 30-day free trial to view this Author Comment or ask the Experts your question.

 
 
Loading Advertisement...
20091111-EE-VQP-91 / EE_QW_2_20070628