linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dennis Borgmann <dennis.borgmann@googlemail.com>
To: linux-wireless@vger.kernel.org
Subject: Re: [ath5k] kernel panic while using compat-wireless-2.6.38.2-2
Date: Mon, 23 May 2011 18:21:56 +0200	[thread overview]
Message-ID: <4DDA89A4.5040101@googlemail.com> (raw)
In-Reply-To: <4DCA672E.2080906@googlemail.com>

Hello linux-wireless list!

Is there really no one with an idea? Is there no one among the 
developers, who is interested in this bug, if it is a bug?

I'm starting to lose my hope...

Dennis

Am 11.05.2011 12:38, schrieb Dennis Borgmann:
> Hello linux-wireless list!
>
> I am using a Sparklan WPEA-166G/W with Chipset AR5BXB63 Rev. 11 (it's 
> a MiniPCI-card) in an embedded X86-System (Pipal 2140U, Intel ATOM 
> processor). It's running voyage-0.6.5, which essentially is a Debian 
> Lenny System.
>
> I am running kernel 2.6.33.9-rt31:
>
> demo00000001:~# uname -a
> Linux SSB_wlan-demo00000001 2.6.33.9-rt31-atom-ssb #1 PREEMPT RT Mon 
> May 9 18:25:28 CEST 2011 i686 GNU/Linux
>
> I installed the compat-wireless drivers version 2.6.38.2-2 ( 
> http://www.orbit-lab.org/kernel/compat-wireless-2.6-stable/v2.6.38/compat-wireless-2.6.38.2-2.tar.bz2 
> ) and installed everything I need according to this webpage: 
> http://acx100.erley.org/stable.html
>
> Once issueing modprobe ath5k, putting the interface up and waiting for 
> ~30sec, I get a kernel panic. Could this be a bug or am I doing 
> something wrong?
>
> The error only occurrs after putting the interface up. If I don't do 
> so, the error won't be there.
>
> Here is some output from the machine:
>
> demo00000001:~# modprobe ath5k && ifconfig wlan0 up
> [   48.363894] Compat-wireless backport release: 
> compat-wireless-2.6.38.2-2
> [   48.372351] Backport based on linux-2.6-allstable.git v2.6.38.2
> [   48.411748] cfg80211: Calling CRDA to update world regulatory domain
> [   48.517969] ath5k 0000:09:00.0: using bridge 0000:00:1c.2 INT A to 
> get IRQ 17
> [   48.526919] ath5k 0000:09:00.0: PCI->APIC IRQ transform: INT A -> 
> IRQ 17
> [   48.534315] ath5k 0000:09:00.0: registered as 'phy0'
> [   49.162919] ath5k phy0: Atheros AR2425 chip found (MAC: 0xe2, PHY: 
> 0x70)
> demo00000001:~# [   77.953752] ------------[ cut here ]------------
> [   77.958711] WARNING: at 
> /home/dborgmann/downloads/compat-wireless-2.6.38.2-2/net/mac80211/rx.c:2827 
> ieee80211_rx+0x38/0x6fe [mac80211]()
> [   77.971856] Hardware name: Luna Pier CRB
> [   77.976049] Modules linked in: [last unloaded: scsi_wait_scan]
> [   77.982354] Pid: 9, comm: sirq-tasklet/0 Not tainted 
> 2.6.33.9-rt31-atom-ssb #1
> [   77.990090] Call Trace:
> [   77.992732]  [<c011852f>] warn_slowpath_common+0x65/0x7c
> [   77.998419]  [<e0024ad1>] ? ieee80211_rx+0x38/0x6fe [mac80211]
> [   78.004672]  [<c0118553>] warn_slowpath_null+0xd/0x10
> [   78.010119]  [<e0024ad1>] ieee80211_rx+0x38/0x6fe [mac80211]
> [   78.016157]  [<c022d6e8>] ? __alloc_skb+0x4c/0x110
> [   78.021296]  [<c0106297>] ? nommu_map_page+0x3c/0x51
> [   78.026648]  [<e00992c9>] ? ath5k_rx_skb_alloc+0x99/0x10a [ath5k]
> [   78.033190]  [<e009b989>] ath5k_tasklet_rx+0x59f/0x60b [ath5k]
> [   78.039454]  [<c011c486>] __tasklet_action.clone.8+0x76/0xd1
> [   78.045502]  [<c011c529>] tasklet_action+0x23/0x25
> [   78.050640]  [<c011c285>] run_ksoftirqd+0xf0/0x19b
> [   78.055788]  [<c011c195>] ? run_ksoftirqd+0x0/0x19b
> [   78.061032]  [<c0127829>] kthread+0x5e/0x63
> [   78.065538]  [<c01277cb>] ? kthread+0x0/0x63
> [   78.070107]  [<c0102bb6>] kernel_thread_helper+0x6/0x10
> [   78.075695] ---[ end trace 6b864a3c0aa1a8eb ]---
>
>
> Best regards,
> Dennis


  reply	other threads:[~2011-05-23 16:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-11 10:38 [ath5k] kernel panic while using compat-wireless-2.6.38.2-2 Dennis Borgmann
2011-05-23 16:21 ` Dennis Borgmann [this message]
2011-05-23 16:35   ` Ben Greear
2011-05-24 19:11     ` Dennis Borgmann
2011-05-24 20:03     ` Dennis Borgmann
2011-05-24 20:47       ` Ben Greear

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=4DDA89A4.5040101@googlemail.com \
    --to=dennis.borgmann@googlemail.com \
    --cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).