All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Basse <michael@alpha-unix.de>
To: Helmut Schaa <helmut.schaa@googlemail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] rt2800pci: handle spurious interrupts
Date: Wed, 23 Nov 2011 07:25:29 +0100	[thread overview]
Message-ID: <4ECC91D9.7030902@alpha-unix.de> (raw)
In-Reply-To: <1700561.mj30bDeLIf@helmutmobil.site>

Am 22.11.2011 23:10, schrieb Helmut Schaa:
> Why do you think the panics are produced by rt2800pci? The stacktraces
> attached to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/869502
> don't show rt2x00 related functions ...
> 
> Helmut

Hi Helmut,
i am not sure if the panics are related to rt2800pci. Because of the
following facts i thought it was related to that module.

- all systems facing that kind of panics are using rt2800pci
- with the newest compat wifi-drivers that kind of panics are gone
- panics are not happening when wifi is disabled (using fn-key to
disable wifi)
- i saw the patch from Stanislaw and thought it will fix the issue
because its related to rt2800pci

My problem is that i dont know how to do a better debbuging for that
kind of problem, so i was just trying some things around and thought the
issues are coming from rt2800pci. But all i am doing at the moment is
just guessing, because i am lost with that kind of problem.


Greetings

Michael




  reply	other threads:[~2011-11-23  6:33 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-16 10:09 [PATCH] rt2800pci: handle spurious interrupts Stanislaw Gruszka
2011-11-16 10:14 ` Ivo Van Doorn
2011-11-16 11:17   ` Stanislaw Gruszka
2011-11-16 11:45     ` Ivo Van Doorn
2011-11-16 10:46 ` Helmut Schaa
2011-11-16 10:52   ` Ivo Van Doorn
2011-11-16 11:01     ` Helmut Schaa
2011-11-22 20:33 ` Michael Basse
2011-11-22 22:10   ` Helmut Schaa
2011-11-23  6:25     ` Michael Basse [this message]
     [not found]   ` <20111123073500.GA9833@redhat.com>
2011-11-23 15:50     ` Michael Basse
2011-11-22 21:49 ` John W. Linville
2011-11-23  8:05   ` Stanislaw Gruszka
2011-11-23  8:50     ` Ivo Van Doorn
2011-11-23  8:51     ` Helmut Schaa
2011-11-23 10:51       ` Stanislaw Gruszka
     [not found]         ` <CAHJ2optb4E2r6W2w21oswptZh=_Q9kB+RbQ=F0TWg9zHGjXwZA@mail.gmail.com>
2011-11-23 14:40           ` Stanislaw Gruszka
2011-11-23 14:45             ` Luis Correia
     [not found]         ` <CAN6fvj2=EhimZUy-DKtpzAKq1mpvBt03KtX9vCi0dBTCXWVsRg@mail.gmail.com>
2011-11-23 15:14           ` Stanislaw Gruszka
2011-11-23 15:44             ` Stanislaw Gruszka
2011-11-23 17:00             ` Stanislaw Gruszka
2011-11-23 20:47         ` David Miller

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=4ECC91D9.7030902@alpha-unix.de \
    --to=michael@alpha-unix.de \
    --cc=helmut.schaa@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.