Created attachment 43462 [details] dmesg 2.6.37 [31935.833351] Call Trace: [31935.833353] <IRQ> [<ffffffff8111023a>] __alloc_pages_slowpath+0x45a/0x5b0 [31935.833365] [<ffffffff8111051b>] __alloc_pages_nodemask+0x18b/0x1d0 [31935.833372] [<ffffffff815a93b4>] ? _raw_spin_lock_irqsave+0x34/0x50 [31935.833377] [<ffffffff811465a3>] alloc_pages_current+0xa3/0x110 [31935.833380] [<ffffffff8114e205>] allocate_slab+0x175/0x180 [31935.833383] [<ffffffff8114e750>] new_slab+0x30/0x170 [31935.833387] [<ffffffff811503f9>] __slab_alloc+0x1e9/0x250 [31935.833400] [<ffffffffa0117039>] ? ath_rxbuf_alloc+0x39/0xc0 [ath] [31935.833404] [<ffffffff81150b68>] __kmalloc_node_track_caller+0x188/0x1e0 [31935.833408] [<ffffffffa0117039>] ? ath_rxbuf_alloc+0x39/0xc0 [ath] [31935.833412] [<ffffffff814abbdf>] __alloc_skb+0x7f/0x170 [31935.833416] [<ffffffffa0117039>] ath_rxbuf_alloc+0x39/0xc0 [ath] [31935.833424] [<ffffffffa02ee4b4>] ath_rx_tasklet+0x294/0x5e0 [ath9k] [31935.833429] [<ffffffff81095573>] ? tick_dev_program_event+0x33/0xa0 [31935.833433] [<ffffffff8108a0fe>] ? hrtimer_interrupt+0x10e/0x210 [31935.833438] [<ffffffffa02eb46c>] ath9k_tasklet+0x12c/0x1b0 [ath9k] [31935.833442] [<ffffffff8106ba77>] tasklet_action+0x87/0x140 [31935.833445] [<ffffffff8106b3e3>] __do_softirq+0xc3/0x1d0 [31935.833449] [<ffffffff81030aba>] ? ack_apic_level+0x7a/0xf0 [31935.833453] [<ffffffff8100cfdc>] call_softirq+0x1c/0x30 [31935.833456] [<ffffffff8100e965>] do_softirq+0x65/0xa0 [31935.833459] [<ffffffff8106b2a5>] irq_exit+0x85/0x90 [31935.833462] [<ffffffff815b1754>] do_IRQ+0x74/0xe0 [31935.833466] [<ffffffff815a9a53>] ret_from_intr+0x0/0x11
Created attachment 43472 [details] lspci-vvnn_2.6.37-020637-generic
$ uname -a Linux VGN-NS130FE 2.6.37-020637-generic #201101050908 SMP Wed Jan 5 09:09:44 UTC 2011 x86_64 GNU/Linux
¿Bug in module Atheros?
*** Bug 26672 has been marked as a duplicate of this bug. ***
Please change product and component to "Drivers" and "network-wireless"
Please don't, unless you can demonstrate that ath_rxbuf_alloc is somehow calling _dev_alloc_skb incorrectly. It is an order-1 allocation, if that is significant.
*** Bug 27042 has been marked as a duplicate of this bug. ***
Have you played with the /proc/sys/vm/min_free_kbytes?
(In reply to comment #8) > Have you played with the /proc/sys/vm/min_free_kbytes? I have not played with the / proc / sys / vm / min_free_kbytes
Created attachment 44202 [details] messages 2.6.37 Jan 18 20:42:10 VGN-NS130FE kernel: [15823.224606] Call Trace: Jan 18 20:42:10 VGN-NS130FE kernel: [15823.224608] <IRQ> [<ffffffff8111023a>] __alloc_pages_slowpath+0x45a/0x5b0 Jan 18 20:42:10 VGN-NS130FE kernel: [15823.224623] [<ffffffff81055bd1>] ? wakeup_preempt_entity+0x21/0x30 Jan 18 20:42:10 VGN-NS130FE kernel: [15823.224627] [<ffffffff8111051b>] __alloc_pages_nodemask+0x18b/0x1d0 Jan 18 20:42:10 VGN-NS130FE kernel: [15823.224633] [<ffffffff811465a3>] alloc_pages_current+0xa3/0x110 Jan 18 20:42:10 VGN-NS130FE kernel: [15823.224636] [<ffffffff8114e205>] allocate_slab+0x175/0x180 Jan 18 20:42:10 VGN-NS130FE kernel: [15823.224639] [<ffffffff8114e750>] new_slab+0x30/0x170 Jan 18 20:42:10 VGN-NS130FE kernel: [15823.224643] [<ffffffff811503f9>] __slab_alloc+0x1e9/0x250 Jan 18 20:42:10 VGN-NS130FE kernel: [15823.224654] [<ffffffffa0200039>] ? ath_rxbuf_alloc+0x39/0xc0 [ath] Jan 18 20:42:10 VGN-NS130FE kernel: [15823.224658] [<ffffffff81150b68>] __kmalloc_node_track_caller+0x188/0x1e0 Jan 18 20:42:10 VGN-NS130FE kernel: [15823.224662] [<ffffffffa0200039>] ? ath_rxbuf_alloc+0x39/0xc0 [ath] Jan 18 20:42:10 VGN-NS130FE kernel: [15823.224666] [<ffffffff814abbdf>] __alloc_skb+0x7f/0x170 Jan 18 20:42:10 VGN-NS130FE kernel: [15823.224670] [<ffffffffa0200039>] ath_rxbuf_alloc+0x39/0xc0 [ath] Jan 18 20:42:10 VGN-NS130FE kernel: [15823.224677] [<ffffffffa036c4b4>] ath_rx_tasklet+0x294/0x5e0 [ath9k] Jan 18 20:42:10 VGN-NS130FE kernel: [15823.224683] [<ffffffffa036946c>] ath9k_tasklet+0x12c/0x1b0 [ath9k] Jan 18 20:42:10 VGN-NS130FE kernel: [15823.224687] [<ffffffff8106ba77>] tasklet_action+0x87/0x140 Jan 18 20:42:10 VGN-NS130FE kernel: [15823.224690] [<ffffffff8106b3e3>] __do_softirq+0xc3/0x1d0 Jan 18 20:42:10 VGN-NS130FE kernel: [15823.224694] [<ffffffff81030aba>] ? ack_apic_level+0x7a/0xf0 Jan 18 20:42:10 VGN-NS130FE kernel: [15823.224698] [<ffffffff8100cfdc>] call_softirq+0x1c/0x30 Jan 18 20:42:10 VGN-NS130FE kernel: [15823.224702] [<ffffffff8100e965>] do_softirq+0x65/0xa0 Jan 18 20:42:10 VGN-NS130FE kernel: [15823.224704] [<ffffffff8106b2a5>] irq_exit+0x85/0x90 Jan 18 20:42:10 VGN-NS130FE kernel: [15823.224709] [<ffffffff815b1754>] do_IRQ+0x74/0xe0 Jan 18 20:42:10 VGN-NS130FE kernel: [15823.224714] [<ffffffff815a9a53>] ret_from_intr+0x0/0x11 Jan 18 20:42:10 VGN-NS130FE kernel: [15823.224716] <EOI> [<ffffffff8134be96>] ? acpi_idle_enter_c1+0x87/0xa4 Jan 18 20:42:10 VGN-NS130FE kernel: [15823.224722] [<ffffffff8134be8c>] ? acpi_idle_enter_c1+0x7d/0xa4 Jan 18 20:42:10 VGN-NS130FE kernel: [15823.224726] [<ffffffff8148c47d>] cpuidle_idle_call+0x8d/0x130 Jan 18 20:42:10 VGN-NS130FE kernel: [15823.224730] [<ffffffff8100a764>] cpu_idle+0xa4/0x120 Jan 18 20:42:10 VGN-NS130FE kernel: [15823.224735] [<ffffffff8158caa2>] rest_init+0x72/0x80 Jan 18 20:42:10 VGN-NS130FE kernel: [15823.224739] [<ffffffff81ac0f0a>] start_kernel+0x29a/0x380 Jan 18 20:42:10 VGN-NS130FE kernel: [15823.224743] [<ffffffff81ac0140>] ? early_idt_handler+0x0/0x71 Jan 18 20:42:10 VGN-NS130FE kernel: [15823.224746] [<ffffffff81ac032a>] x86_64_start_reservations+0x6a/0xa0 Jan 18 20:42:10 VGN-NS130FE kernel: [15823.224749] [<ffffffff81ac044c>] x86_64_start_kernel+0xcc/0xf0
Set min_free_kbytes to 65535 to see if it helps
*** Bug 27602 has been marked as a duplicate of this bug. ***
Created attachment 46192 [details] dmesg 2.6.38-rc3 I use bittorrent y not mesage in kernel 2.6.38-rc3. Please close report.
*** This bug has been marked as a duplicate of bug 28922 ***