b43-dev.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: chris at martin.cc <chris@martin.cc>
To: b43-dev@lists.infradead.org
Subject: Switching to 4.174.64.19 firmware for G-PHY cards?
Date: Thu, 3 Mar 2011 16:34:44 +1100	[thread overview]
Message-ID: <AANLkTimYAEDK7aF1aaNS5_CrbRrxChct4UFKfXDZ+2F6@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinHzH2RjoxM+yQGttxmgpr3K=BNdXupHB6nJ-9B@mail.gmail.com>

2011/3/3 Rafa? Mi?ecki <zajec5@gmail.com>:
>
> Also: could you try loading b43 with pio mode instead of dma? To do this:
> rmmod b43
> rmmod ssb
> insmod /lib/modules/2.6.32.x/b43.ko pio=1
>

I reversed the "810-b43_no_pio.patch" patch as Jonas recommended
I also set CONFIG_B43_FORCE_PIO=y
the recompiled.

Just to be sure I also loaded with
    b43 pio=1

NOTE: there is no ssb module in OpenWrt.  perhaps its built in or
included in another module, I'm not sure

I still get the same OoM error, all be it a little bit latter.

The kzalloc() messages are now from the file pio.c - so I'm very sure
that its using polled I/O

root at OpenWrt:/# wifi up
Configuration file: /var/run/hostapd-phy0.conf
compat-wireless-2011-02-25/drivers/net/wireless/b43/main.c:2260
kzalloc 332 bytes
b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
compat-wireless-2011-02-25/drivers/net/wireless/b43/pio.c:143 kzalloc 668 bytes
compat-wireless-2011-02-25/drivers/net/wireless/b43/pio.c:143 kzalloc 668 bytes
compat-wireless-2011-02-25/drivers/net/wireless/b43/pio.c:143 kzalloc 668 bytes
compat-wireless-2011-02-25/drivers/net/wireless/b43/pio.c:143 kzalloc 668 bytes
compat-wireless-2011-02-25/drivers/net/wireless/b43/pio.c:143 kzalloc 668 bytes
compat-wireless-2011-02-25/drivers/net/wireless/b43/pio.c:178 kzalloc 8 bytes
compat-wireless-2011-02-25/drivers/net/wireless/b43/main.c:2260
kzalloc 332 bytes
b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
compat-wireless-2011-02-25/drivers/net/wireless/b43/pio.c:143 kzalloc 668 bytes
compat-wireless-2011-02-25/drivers/net/wireless/b43/pio.c:143 kzalloc 668 bytes
compat-wireless-2011-02-25/drivers/net/wireless/b43/pio.c:143 kzalloc 668 bytes
compat-wireless-2011-02-25/drivers/net/wireless/b43/pio.c:143 kzalloc 668 bytes
compat-wireless-2011-02-25/drivers/net/wireless/b43/pio.c:143 kzalloc 668 bytes
compat-wireless-2011-02-25/drivers/net/wireless/b43/pio.c:178 kzalloc 8 bytes
device wlan0 entered promiscuous mode
br-lan: port 2(wlan0) entering forwarding state
br-lan: port 2(wlan0) entering forwarding state
Using interface wlan0 with hwaddr 00:22:15:5c:e5:82 and ssid 'OpenWrt'
device wlan0 left promiscuous mode
br-lan: port 2(wlan0) entering forwarding state
device wlan0 entered promiscuous mode
br-lan: port 2(wlan0) entering forwarding state
br-lan: port 2(wlan0) entering forwarding state
kworker/0:15 invoked oom-killer: gfp_mask=0xd0, order=0, oom_adj=0,
oom_score_adj=0
Call Trace:
[<80009120>] dump_stack+0x8/0x34
[<8005f828>] dump_header.clone.13+0x4c/0x120
[<8005fa50>] oom_kill_process.clone.15+0x5c/0x2b4
[<800601f8>] out_of_memory+0x2d4/0x364
[<80064074>] __alloc_pages_nodemask+0x45c/0x570
[<8008d214>] cache_alloc_refill+0x280/0x740
[<8008d880>] kmem_cache_alloc+0x84/0xf4
[<80188a38>] skb_clone+0xdc/0x120
[<80117520>] broadcast_uevent+0x64/0xe0
[<81a14678>] 0x81a14678


----------------------------------------------------------
Chris Martin
m: +61 419 812 371
----------------------------------------------------------

  parent reply	other threads:[~2011-03-03  5:34 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-07 12:21 Switching to 4.174.64.19 firmware for G-PHY cards? Rafał Miłecki
2010-12-07 12:28 ` Rafał Miłecki
2010-12-07 15:32   ` Larry Finger
2010-12-07 19:21     ` Hauke Mehrtens
2011-03-01 13:33       ` Rafał Miłecki
2011-03-02  0:11         ` chris at martin.cc
2011-03-02  0:20           ` Rafał Miłecki
2011-03-02  3:30           ` chris at martin.cc
2011-03-02  9:58             ` Rafał Miłecki
2011-03-02 10:52               ` Rafał Miłecki
2011-03-02 11:22                 ` Jonas Gorski
2011-03-02 12:20                 ` chris at martin.cc
2011-03-02 22:00                   ` Larry Finger
2011-03-02 23:02                     ` chris at martin.cc
2011-03-03  4:43                     ` chris at martin.cc
2011-03-03  7:58                       ` Rafał Miłecki
2011-03-03 11:50                         ` Rafał Miłecki
2011-03-03 23:49                           ` chris at martin.cc
2011-03-07 12:35                             ` Rafał Miłecki
2011-03-04  0:37                           ` chris at martin.cc
2011-03-07 12:26                             ` Rafał Miłecki
2011-03-08  1:12                               ` chris at martin.cc
2011-03-07 13:12                             ` Rafał Miłecki
2011-03-07 16:41                               ` Rafał Miłecki
2011-03-08  1:25                               ` chris at martin.cc
2011-03-08 13:26                                 ` Rafał Miłecki
2011-03-09  0:44                                   ` chris at martin.cc
2011-03-09  0:47                                     ` Rafał Miłecki
2011-03-09  0:47                                     ` chris at martin.cc
2011-03-03  4:55                     ` chris at martin.cc
2011-03-02 23:00                   ` chris at martin.cc
2011-03-02 12:14               ` chris at martin.cc
2011-03-02 13:12                 ` Rafał Miłecki
2011-03-02 23:12                   ` Jonas Gorski
2011-03-03  3:40                   ` chris at martin.cc
2011-03-03  7:55                     ` Rafał Miłecki
2011-03-03 15:52                       ` Larry Finger
2011-03-03  5:34                   ` chris at martin.cc [this message]
2011-03-03  4:23                 ` chris at martin.cc
2011-03-02 10:08             ` Rafał Miłecki
2011-03-02 12:17               ` chris at martin.cc
2011-03-03  3:44                 ` chris at martin.cc

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=AANLkTimYAEDK7aF1aaNS5_CrbRrxChct4UFKfXDZ+2F6@mail.gmail.com \
    --to=chris@martin.cc \
    --cc=b43-dev@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).