From: Larry Finger <Larry.Finger@lwfinger.net>
To: Robie Basak <rb-oss-3@justgohome.co.uk>
Cc: linux-wireless@vger.kernel.org
Subject: Re: r8187se panic
Date: Fri, 12 Nov 2010 11:28:37 -0600 [thread overview]
Message-ID: <4CDD7945.70005@lwfinger.net> (raw)
In-Reply-To: <slrnidqsld.dlr.rb-oss-3@mal.justgohome.co.uk>
On 11/12/2010 11:00 AM, Robie Basak wrote:
> On 2010-11-12, Larry Finger <Larry.Finger@lwfinger.net> wrote:
>> Apply the new patch and the "change panic to warning" patch and redo your case
>> B. Send me the dmesg output and a description of what happened. That data you
>> can send directly. No need to spam the list with the lengthy dmesg output.
>
> OK this is with change_panic_to_warn and fix_proc_entry_warning. I
> forgot to mention that I'm applying all these patches to Ubuntu's stock
> 10.10 kernel, since module symbols etc. come with the build - and then
> just compiling the one kernel module and copying it over (not much space
> or CPU power on the netbook and the keyboard is tiny!).
>
> Behaviour is the same as case B from before. To clarify, after step 3 in
> case B, wireless has always reconnected no problem. It is after a few
> seconds after removing AC power that it loses connection (or perhaps it
> takes a few seconds for Network Manager to notice). Once it has lost
> connection it does seem to occasionally associate and then loses it
> again (according to Network Manager).
>
> Reloading the kernel module doesn't fix it, but then toggling the
> wireless switch after the reload does.
>
> I reproduced it a second time, this time not reloading the module but
> just toggling the wireless switch afterwards. This seemed to fix it as
> well, so it seems that reloading the module is not required.
What does the following log entry signify?
Nov 12 16:29:03 tiny kernel: [ 160.306731]
=>>>>>>>>>>=============================>set power:0,0!
On my system, switching to battery does not affect the rtl8187se at all.
I will be working on a patch that improves the error handling of the read routines.
Larry
next prev parent reply other threads:[~2010-11-12 17:28 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-12 0:41 r8187se panic Robie Basak
2010-11-12 2:00 ` Larry Finger
2010-11-12 11:06 ` Robie Basak
2010-11-12 13:06 ` Larry Finger
2010-11-12 15:55 ` Robie Basak
2010-11-12 16:09 ` Larry Finger
2010-11-12 17:00 ` Robie Basak
2010-11-12 17:28 ` Larry Finger [this message]
2010-11-12 17:40 ` Robie Basak
2010-11-13 18:18 ` James Womack
2010-11-13 18:44 ` Larry Finger
2010-11-13 19:27 ` James Womack
2010-11-13 20:02 ` Larry Finger
2010-11-14 12:22 ` James Womack
2010-11-14 16:18 ` Larry Finger
2010-11-14 18:49 ` James Womack
2010-11-14 20:23 ` Larry Finger
2010-11-15 21:05 ` James Womack
2010-11-15 23:44 ` Larry Finger
2010-11-16 9:55 ` James Womack
2010-11-16 14:24 ` Larry Finger
2010-11-16 14:46 ` James Womack
2010-11-16 15:00 ` Larry Finger
2010-11-16 15:08 ` Rafał Miłecki
2010-11-16 15:42 ` Larry Finger
2010-11-16 16:55 ` James Womack
2010-11-16 17:16 ` Larry Finger
2010-11-14 19:38 ` James Womack
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=4CDD7945.70005@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=rb-oss-3@justgohome.co.uk \
/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).