All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Hin-Tak Leung <htl10@users.sourceforge.net>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
	Herton Ronaldo Krzesinski <herton@canonical.com>,
	linux-wireless@vger.kernel.org, kay@redhat.com
Subject: Re: rtl8187 WARN slowpath on suspend with 3.6.11
Date: Wed, 2 Jan 2013 10:47:25 -0500	[thread overview]
Message-ID: <20130102154724.GA2198@tuxdriver.com> (raw)
In-Reply-To: <1357138947.38782.YahooMailClassic@web172305.mail.ir2.yahoo.com>

On Wed, Jan 02, 2013 at 03:02:27PM +0000, Hin-Tak Leung wrote:
> --- On Tue, 1/1/13, Larry Finger <Larry.Finger@lwfinger.net> wrote:
> 
> > On 12/31/2012 06:16 PM, Hin-Tak Leung
> > wrote:
> > > Hi,
> > >
> > > Does either Larry or Herton see the sort of behavior
> > (https://bugzilla.redhat.com/show_bug.cgi?id=891019) on
> > suspend? John, is there anything changed between 3.6.9 and
> > 3.6.11 which would cause this?
> > >
> > > Other than a genuine kernel regression, it is possible
> > that it might be fedora specific - I just went from F17 to
> > F18. F18 seems to have an systemd integrated udevd which
> > might behaves differently from the older udevd's... or
> > general funniness with F18 (I noticed another bug https://bugzilla.redhat.com/show_bug.cgi?id=891018 but
> > that might be unrelated).
> > >
> > > Anyway, other than whole sale downgrade I think I can
> > try booting 3.6.9 (which suspended cleanly under F17) and
> > see whether it is a F18-specific problem.
> > 
> > Hin-Tak,
> > 
> > My system has never done a suspend/resume with any wireless
> > card, thus I cannot 
> > check your result. The test with 3.6.9 is a good idea.
> > 
> > Sorry,
> > 
> > Larry
> 
> Hi Larry,
> 
> Thanks for the reply. I have since rebooted to 3.6.9-2.fc17.x86_64, 3.6.10-2.fc17.x86_64 as well as 3.6.9-4.fc18.x86_64, 3.6.10-5.fc18.x86_64 and 3.6.11-3.fc18.x86_64; and all have the same problem. 3.6.9-2.fc17.x86_64 was the last kernel which I ran for over two weeks and had suspended a few times according to my /var/log/messages*. So this looks like a fedora-18 specific problems brought on by changes in userland
> between F17 and F18. (possibly the systemd integrated udevd).
> 
> I'll add a comment to the bug report and let John reassign as appropriate.

Thanks, Hin-Tak!  I'll ask Kay to investigate.

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

      reply	other threads:[~2013-01-02 16:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-01  0:16 rtl8187 WARN slowpath on suspend with 3.6.11 Hin-Tak Leung
2013-01-01  1:30 ` Larry Finger
2013-01-02 15:02   ` Hin-Tak Leung
2013-01-02 15:47     ` John W. Linville [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=20130102154724.GA2198@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=herton@canonical.com \
    --cc=htl10@users.sourceforge.net \
    --cc=kay@redhat.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.