All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: bcm43xx-dev@lists.berlios.de
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	Larry Finger <larry.finger@lwfinger.net>,
	wireless <linux-wireless@vger.kernel.org>,
	John Linville <linville@tuxdriver.com>
Subject: Re: [PATCH] bcm43xx: Fix loss of association after resume
Date: Sun, 11 Feb 2007 14:07:07 +0100	[thread overview]
Message-ID: <200702111407.08099.mb@bu3sch.de> (raw)
In-Reply-To: <200702111356.12206.rjw@sisk.pl>

On Sunday 11 February 2007 13:56, Rafael J. Wysocki wrote:
> On Saturday, 10 February 2007 21:33, Larry Finger wrote:
> > Rafael,
> > 
> > Rafael J. Wysocki wrote:
> > > 
> > > I'm running with this patch applied right now, but the association is lost
> > > after the resume anyway.  I have to reload bcm43xx to make it associate with
> > > the AP again (no big deal).
> > 
> > 
> > Please send me the output of iwconfig and ifconfig after the resume, but before you reload bcm43xx.
> 
> albercik:~ # iwconfig
> lo        no wireless extensions.
> 
> eth0      no wireless extensions.
> 
> eth1      IEEE 802.11b/g  ESSID:"DI524"  Nickname:"Broadcom 4311"
>           Mode:Managed  Frequency=2.484 GHz  Access Point: Invalid
>           Bit Rate=1 Mb/s   Tx-Power=18 dBm
>           RTS thr:off   Fragment thr:off
>           Encryption key:off
>           Link Quality=0/100  Signal level=-256 dBm  Noise level=-256 dBm
>           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>           Tx excessive retries:0  Invalid misc:0   Missed beacon:0
> 
> albercik:~ # ifconfig eth1
> eth1      Link encap:Ethernet  HWaddr 00:14:A5:BE:95:31
>           inet addr:192.168.100.101  Bcast:192.168.100.255  Mask:255.255.255.0
>           inet6 addr: fe80::214:a5ff:febe:9531/64 Scope:Link
>           UP BROADCAST MULTICAST  MTU:1500  Metric:1
>           RX packets:5137 errors:0 dropped:120 overruns:0 frame:0
>           TX packets:5703 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:4569090 (4.3 Mb)  TX bytes:156826797 (149.5 Mb)
>           Interrupt:18
> 
> albercik:~ # ifconfig eth1 down
> albercik:~ # ifconfig eth1 up
> SIOCSIFFLAGS: No such device
		^^^^^

I'd like to see dmesg, please.

-- 
Greetings Michael.

  reply	other threads:[~2007-02-11 13:07 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-09 16:18 Larry Finger
2007-02-09 16:18 ` Larry Finger
2007-02-09 16:53 ` Michael Buesch
2007-02-09 16:53   ` Michael Buesch
2007-02-10 17:11   ` Rafael J. Wysocki
2007-02-10 17:11     ` Rafael J. Wysocki
2007-02-10 20:33     ` Larry Finger
2007-02-11 12:56       ` Rafael J. Wysocki
2007-02-11 13:07         ` Michael Buesch [this message]
2007-02-11 14:02           ` Rafael J. Wysocki
2007-02-11 14:14             ` Michael Buesch
2007-02-11 14:41               ` Johannes Berg
2007-02-11 14:45                 ` Rafael J. Wysocki
2007-02-11 14:48                   ` Johannes Berg
2007-02-11 15:59               ` Larry Finger
2007-02-11 16:03                 ` Michael Buesch
2007-02-11 16:16                   ` Michael Buesch
2007-02-11 16:17                   ` Larry Finger
2007-02-12  0:50                 ` Rafael J. Wysocki
2007-02-12  1:18                   ` Larry Finger
2007-02-12 20:48                     ` Rafael J. Wysocki
2007-02-12 22:20                       ` Larry Finger
2007-02-12 23:08                         ` Rafael J. Wysocki
2007-02-12 23:18                           ` Larry Finger
2007-02-12 23:24                           ` Michael Buesch
2007-02-13 16:25                             ` Rafael J. Wysocki

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=200702111407.08099.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=larry.finger@lwfinger.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=rjw@sisk.pl \
    --subject='Re: [PATCH] bcm43xx: Fix loss of association after resume' \
    /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

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.