linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Mack <daniel@caiaq.de>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
	Sven Neumann <s.neumann@raumfeld.com>,
	Michael Hirsch <m.hirsch@raumfeld.com>,
	ath5k-devel@lists.ath5k.org
Subject: Re: wireless: Problems with ath5k and 2.6.35
Date: Sun, 8 Aug 2010 20:25:58 +0200	[thread overview]
Message-ID: <20100808182558.GC10432@buzzloop.caiaq.de> (raw)
In-Reply-To: <4C5E68C1.9070403@gmail.com>

Hi Jiri,

On Sun, Aug 08, 2010 at 10:20:17AM +0200, Jiri Slaby wrote:
> On 08/07/2010 07:21 PM, Daniel Mack wrote:
> > [    2.142771] ath5k 0000:00:0c.0: guessed PCI INT A -> IRQ 9
> > [    2.148319] ath5k 0000:00:0c.0: sharing IRQ 9 with 0000:00:01.2
> > [    2.154548] ath5k 0000:00:0c.0: registered as 'phy0'
> > [    3.126593] irq 9: nobody cared (try booting with the "irqpoll" option)
> > [    3.130015] Pid: 1, comm: swapper Not tainted 2.6.35+ #1
> > [    3.130015] Call Trace:
> > [    3.130015]  [<c013e984>] __report_bad_irq+0x2e/0x6f
> > [    3.130015]  [<c013eab5>] note_interrupt+0xf0/0x147
> > [    3.130015]  [<c013f076>] handle_level_irq+0x6d/0x99
> > [    3.130015]  [<c0103bf6>] handle_irq+0x1a/0x20
> > [    3.130015]  [<c0103810>] do_IRQ+0x33/0x88
> > [    3.130015]  [<c0102a69>] common_interrupt+0x29/0x30
> > [    3.130015]  [<c0120e3c>] ? __do_softirq+0x34/0xca
> > [    3.130015]  [<c0120ef7>] do_softirq+0x25/0x2a
> > [    3.130015]  [<c0120fb7>] irq_exit+0x28/0x57
> > [    3.130015]  [<c0103850>] do_IRQ+0x73/0x88
> > [    3.130015]  [<c0102a69>] common_interrupt+0x29/0x30
> > [    3.130015]  [<c013007b>] ? __async_schedule+0x38/0xe9
> > [    3.130015]  [<c013e420>] ? __setup_irq+0x1d8/0x259
> > [    3.130015]  [<c013e544>] request_threaded_irq+0xa3/0xd0
> > [    3.130015]  [<c02486e5>] ? ath5k_intr+0x0/0x28b
> > [    3.130015]  [<c032e15c>] ath5k_pci_probe+0x2f4/0x13c5
> 
> The interrupt came right after enabled in probe function with
> ATH_STAT_INVALID still set. Is this really a 2.6.34 regression? The only
> difference I see that we now (in .35) use MIB interrrupts.

I can't tell exactly when things broke, but appearantly, it worked in
2.6.31.4. I'll get back to this issue in some days when I have access to
the hardware again. I would also bisect this topic then if neccessary.


Thanks,
Daniel


      reply	other threads:[~2010-08-08 18:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-07 17:21 wireless: Problems with ath5k and 2.6.35 Daniel Mack
2010-08-08  8:20 ` Jiri Slaby
2010-08-08 18:25   ` Daniel Mack [this message]

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=20100808182558.GC10432@buzzloop.caiaq.de \
    --to=daniel@caiaq.de \
    --cc=ath5k-devel@lists.ath5k.org \
    --cc=jirislaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=m.hirsch@raumfeld.com \
    --cc=s.neumann@raumfeld.com \
    /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).