linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: "Nico Schottelius" <nico-kernel20120920@schottelius.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Out of memory on 3.5 kernels
Date: Thu, 20 Sep 2012 15:52:32 +0200	[thread overview]
Message-ID: <505B1FA0.6030100@broadcom.com> (raw)

Thanks, Nico

 > just while running, I got the following brcmsmac related error:
 >
 > [17336.572558] WARNING: at 
drivers/net/wireless/brcm80211/brcmsmac/main.c:7968 
brcms_c_wait_for_tx_completion+0x99/0xb0 [brcmsmac]()
 > [17336.572562] Hardware name: MacBookAir4,2
 > [17336.572565] Modules linked in: sha256_generic snd_hda_codec_hdmi 
snd_hda_codec_cirrus ext4 jbd2 mbcache arc4 uvcvideo brcmsmac 
videobuf2_vmalloc videobuf2_memops cordic brcmutil btusb bluetooth i915 
videobuf2_core mac80211 videodev crc16 acpi_cpufreq snd_hda_intel media 
i2c_algo_bit cfg80211 mperf drm_kms_helper snd_hda_codec rfkill joydev 
bcm5974 iTCO_wdt iTCO_vendor_support i2c_i801 intel_agp lpc_ich applesmc 
evdev microcode drm coretemp input_polldev pcspkr intel_gtt mfd_core 
i2c_core processor bcma snd_hwdep video button battery apple_bl mei ac 
snd_pcm_oss snd_mixer_oss snd_pcm snd_page_alloc snd_timer snd soundcore 
kvm_intel kvm nfs nfs_acl lockd auth_rpcgss sunrpc fscache autofs4 jfs 
xts gf128mul dm_crypt dm_mod sd_mod pata_acpi ata_generic hid_generic 
usb_storage hid_apple usbhid hid uhci_hcd aesni_intel aes_x86_64 
aes_generic ghash_clmulni_intel cryptd crc32c_intel ata_piix libata 
scsi_mod ehci_hcd usbcore usb_common
 > [17336.572716] Pid: 27714, comm: kworker/u:1 Not tainted 3.5.4-1-ARCH #1
 > [17336.572719] Call Trace:
 > [17336.572734]  [<ffffffff81051a3f>] warn_slowpath_common+0x7f/0xc0
 > [17336.572743]  [<ffffffff81051a9a>] warn_slowpath_null+0x1a/0x20
 > [17336.572759]  [<ffffffffa063bd29>] 
brcms_c_wait_for_tx_completion+0x99/0xb0 [brcmsmac]
 > [17336.572769]  [<ffffffffa062e1bb>] brcms_ops_flush+0x3b/0x60 [brcmsmac]

This issue is bugging me for quite a while and some patch do patch up 
the issue, but it is still bleeding. Nasty one to get to the root cause 
of it, but I am testing my pitbull mentality on it ;-)

Gr. AvS


             reply	other threads:[~2012-09-20 13:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-20 13:52 Arend van Spriel [this message]
2012-09-21 19:49 ` Out of memory on 3.5 kernels Nico Schottelius
2012-09-21 21:02   ` Fwd: " Arend van Spriel
2012-09-24 22:43   ` David Rientjes
2012-09-25 15:07     ` Dave Kleikamp
2012-09-26  6:03       ` Nico Schottelius
2012-09-26  6:06     ` Nico Schottelius
2012-09-26  8:57       ` Nico Schottelius
2012-09-27  5:52         ` Nico Schottelius
2012-10-03 21:23           ` Nico Schottelius
2012-10-05 15:48             ` Valdis.Kletnieks
2012-10-05 17:51               ` Nico Schottelius
2012-10-30 10:35                 ` Nico Schottelius
2012-11-01 18:04                   ` [Jfs-discussion] " Tino Reichardt
2012-11-21 22:37                   ` Dave Kleikamp
2012-11-27 15:56                     ` [Jfs-discussion] " Dave Kleikamp
2012-11-27 16:11                       ` Nico Schottelius

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=505B1FA0.6030100@broadcom.com \
    --to=arend@broadcom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=nico-kernel20120920@schottelius.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).