linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ivo van Doorn <ivdoorn@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: crash with rt61pci when resuming with card ejected
Date: Sun, 2 Nov 2008 00:10:47 +0100	[thread overview]
Message-ID: <200811020010.47762.IvDoorn@gmail.com> (raw)
In-Reply-To: <1225553696.3619.11.camel@johannes.berg>

On Saturday 01 November 2008, Johannes Berg wrote:
> On Sat, 2008-11-01 at 16:25 +0100, Ivo van Doorn wrote:
> > On Saturday 01 November 2008, Johannes Berg wrote:
> > > On Sat, 2008-11-01 at 11:29 +0100, Ivo van Doorn wrote:
> > > > On Saturday 01 November 2008, Johannes Berg wrote:
> > > > > On Sat, 2008-11-01 at 09:58 +0100, Ivo van Doorn wrote:
> > > > > 
> > > > > > Could you try this patch? It doesn't matter if it is on top or as a replacement
> > > > > > of my previous patch.
> > > > > > 
> > > > > > This patch should also fix suspend/resume handling in general, I suddenly realized
> > > > > > there was quite a big bug in there regarding EEPROM/CSR handling. 
> > > > > 
> > > > > Now it just hangs at resume, rather than crashing. At suspend it already
> > > > > logs some MCU errors though.
> > > > 
> > > > Hmm that is strange, those MCU errors could only come from right before the code I
> > > > just changed. :S
> > > > 
> > > > In any case, could you revert the previous patches and try this. This is the same LED patch
> > > > as before, but I have added the check for set_key() to return immediately when this is called
> > > > while the module is busy unloading.
> > > 
> > > Now I've upgraded wireless-testing and am running into the BUG_ON you
> > > added for antenna diversity...
> > 
> > Hmm, that's odd.. I'll look into it. Patches could take some time :(
> 
> That was with that patch applied, but I don't think it caused it. No
> worries, I don't usually actually use the rt61 card, but had used it for
> monitoring the night before I wrote my bug report, suspended, and
> ejected it while suspended the next morning because I had to run... :)

I think I found something, I'm sending a patch series for John in a few minutes,
it will contain a fix for this BUG_ON().

Ivo

      reply	other threads:[~2008-11-01 23:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-30 10:12 crash with rt61pci when resuming with card ejected Johannes Berg
2008-10-30 21:47 ` Ivo van Doorn
2008-10-30 22:07   ` Johannes Berg
2008-10-30 23:07   ` Johannes Berg
2008-10-31 19:31     ` Ivo van Doorn
2008-10-31 21:47       ` Johannes Berg
2008-10-31 22:01         ` Ivo van Doorn
2008-10-31 22:11           ` Johannes Berg
2008-11-01  8:58             ` Ivo van Doorn
2008-11-01  9:15               ` Johannes Berg
2008-11-01 10:29                 ` Ivo van Doorn
2008-11-01 12:05                   ` Johannes Berg
2008-11-01 15:25                     ` Ivo van Doorn
2008-11-01 15:34                       ` Johannes Berg
2008-11-01 23:10                         ` Ivo van Doorn [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=200811020010.47762.IvDoorn@gmail.com \
    --to=ivdoorn@gmail.com \
    --cc=johannes@sipsolutions.net \
    --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).