public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Tesliuk <mike@001admin.com.br>
To: kernel <linux-kernel@vger.kernel.org>
Subject: RE: error on kern.log
Date: Mon, 08 Nov 2004 16:08:08 -0200	[thread overview]
Message-ID: <1099937288.9491.49.camel@001linux> (raw)
In-Reply-To: <2E314DE03538984BA5634F12115B3A4E01BC403D@email1.mitretek.org>

right!! thanks!!!


Em Seg, 2004-11-08 às 15:33, Piszcz, Justin Michael escreveu:
> This is a known bug, it has to do with your network card using TSO
> (tcp-sementation-offload), hopefully, it will be fixed in 2.6.10.
> 
> http://www.ussg.iu.edu/hypermail/linux/kernel/0410.3/1326.html
> http://www.ussg.iu.edu/hypermail/linux/kernel/0410.3/1684.html
> 
> 
> -----Original Message-----
> From: linux-kernel-owner@vger.kernel.org
> [mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Mike Tesliuk
> Sent: Monday, November 08, 2004 11:54 AM
> To: kernel
> Subject: error on kern.log
> 
> Hello for all!!!
> 
> I have a kernel messages like this every time: 
> 
> printk: 9 messages suppressed.
> perl5.6.1: page allocation failure. order:3, mode:0x20
> Call Trace:
>  [<c01351c5>] __alloc_pages+0x2dd/0x2ec
>  [<c01351f1>] __get_free_pages+0x1d/0x38
>  [<c0137d5d>] cache_grow+0xc5/0x2f8
>  [<c013815b>] cache_alloc_refill+0x1cb/0x214
>  [<c0138468>] __kmalloc+0x60/0x7c
>  [<c02eb2cc>] alloc_skb+0x3c/0xd8
>  [<c0312ec5>] tcp_fragment+0x6d/0x2ac
>  [<c0315291>] tcp_write_wakeup+0xd9/0x20c
>  [<c03153d7>] tcp_send_probe0+0x13/0xfc
>  [<c0315f16>] tcp_probe_timer+0xa2/0xac
>  [<c03163be>] tcp_write_timer+0xae/0xe4
>  [<c0316310>] tcp_write_timer+0x0/0xe4
>  [<c0123075>] run_timer_softirq+0x129/0x15c
>  [<c011f2bc>] do_softirq+0x6c/0xcc
>  [<c01131d3>] smp_apic_timer_interrupt+0x13f/0x144
>  [<c010afa2>] apic_timer_interrupt+0x1a/0x20
> 
> 
> ( Im using a kernel 2.6.4 )
> 
> somebody can help me! i have this messages every time!!
> 
> what is this?
> 
> Thanks!!
> 
> Mike Tesliuk (from Brasil)
> 
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel"
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 


  reply	other threads:[~2004-11-08 18:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-08 17:33 error on kern.log Piszcz, Justin Michael
2004-11-08 18:08 ` Mike Tesliuk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-11-08 17:46 Piszcz, Justin Michael
2004-11-08 16:54 Mike Tesliuk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1099937288.9491.49.camel@001linux \
    --to=mike@001admin.com.br \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox