All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Dan Williams <dcbw@redhat.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	Bob Copeland <me@bobcopeland.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"mabbaswireless@gmail.com" <mabbaswireless@gmail.com>
Subject: Re: [PATCH v2 0/3] mac80211 suspend/resume
Date: Mon, 15 Dec 2008 01:28:57 -0800	[thread overview]
Message-ID: <20081215092857.GE6162@tesla> (raw)
In-Reply-To: <1229354532.12163.24.camel@localhost.localdomain>

On Mon, Dec 15, 2008 at 07:22:12AM -0800, Dan Williams wrote:
> On Mon, 2008-12-15 at 11:14 +0100, Johannes Berg wrote:
> > Sorry, heh, was reading mail in the wrong order I guess.
> >
> > >  - the call to ieee80211_sta_tear_down_BA_sessions was locking up so
> > >    I just dropped it for now in the interest of getting a stable base
> >
> > Probably due to transmitting again? We'll have to look and add it, but I
> > agree that we can work on that later.
> >
> > > I also tracked down the disappearing interface problem.. turns out this
> > > was just gnome-power-manager or HAL.  (I do not have 'network_sleep' set
> > > in gconf, but I didn't bother pinning it down otherwise...)  Using
> > > 'echo mem > /sys/power/state' to suspend keeps the interface up across
> > > suspend.
> >
> > Oh ok, that explains things.
> 
> Could be udev event ordering?  We do need to track this down, otherwise
> stuff simply won't work when we come back.  The best thing to do here is
> run the udev monitoring tool (whatever that is, I forget) 

That would be:

udevadm monitor --environment kernel

> and see what
> events get emitted from the kernel, then run 'lshal --monitor' and see
> what HAL thinks is going on, which it gets from consuming udev events
> and inspecting sysfs.  Stuff like this is sometimes caused by
> mis-ordered kernel events or drivers/subsystems that don't create their
> sysfs directories at the right times, leading to race conditions between
> the kernel and HAL.  A possibility.

  Luis

  reply	other threads:[~2008-12-15 17:28 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-15  3:50 [PATCH v2 0/3] mac80211 suspend/resume Bob Copeland
2008-12-15 10:14 ` Johannes Berg
2008-12-15 15:22   ` Dan Williams
2008-12-15  9:28     ` Luis R. Rodriguez [this message]
2008-12-17 18:21     ` Bob Copeland
2008-12-23 20:30       ` Johannes Berg
2008-12-24  5:49         ` Bob Copeland
2008-12-24  7:16           ` Marcel Holtmann
2009-01-06 16:45             ` Dan Williams
2009-01-06 17:07               ` Bob Copeland
2009-01-06 17:14                 ` Johannes Berg
2009-01-06 17:35                   ` Bob Copeland
2009-01-06 17:43                     ` Johannes Berg
2009-01-06 18:01                       ` Bob Copeland
2009-01-06 18:16                         ` Johannes Berg
2009-01-06 17:12               ` Marcel Holtmann
2009-01-06 18:52                 ` Dan Williams
2009-01-06 19:36                   ` Marcel Holtmann
2009-01-06 20:05                     ` Johannes Berg
2009-01-09 23:53                       ` Tomas Winkler
2009-01-10  9:27                         ` Johannes Berg
2009-01-11 11:11                           ` Tomas Winkler
2009-01-11 14:40                             ` Bob Copeland
2009-01-08 16:39                     ` Dan Williams
2009-01-09  7:55                       ` Kalle Valo
2009-01-09 16:35                         ` Dan Williams
2009-01-09 16:44                           ` Kalle Valo

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=20081215092857.GE6162@tesla \
    --to=lrodriguez@atheros.com \
    --cc=dcbw@redhat.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mabbaswireless@gmail.com \
    --cc=me@bobcopeland.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 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.