From: Johannes Berg <johannes@sipsolutions.net>
To: "Carlos R. Mafra" <crmafra2@gmail.com>
Cc: Soeren Sonnenburg <kernel@nn7.de>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
linux-kernel@vger.kernel.org, tomas.winkler@intel.com,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org
Subject: Re: Suspend to RAM regression in 2.6.28-rc2 (bisected)
Date: Mon, 27 Oct 2008 20:13:43 +0100 [thread overview]
Message-ID: <1225134823.3796.45.camel@johannes.berg> (raw)
In-Reply-To: <20081027191118.GA4058@localhost.aei.mpg.de>
[-- Attachment #1: Type: text/plain, Size: 789 bytes --]
On Mon, 2008-10-27 at 20:11 +0100, Carlos R. Mafra wrote:
> > Do you get any kernel messages output? If you do, could you put messages
> > into each line of ieee80211_set_disassoc to see where it hangs?
>
> No messages appear, just a black screen.
>
> But I can use the SysRq keys, and when I umount the
> screen shows the message that umount succeed. I also tried SysRq+t but
> the messages appear to fast to read.
Ok, but that means you _can_ get messages, it would help a lot if you
could put a few printks into the set_disassoc function before/after each
other function call, so we know where exactly it hangs. Pretty much all
of them could possibly hang if there is some sort of locking error
happening or anything relies on userspace to be running...
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2008-10-27 19:14 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-27 16:20 Carlos R. Mafra
2008-10-27 17:32 ` Rafael J. Wysocki
2008-10-27 18:07 ` Soeren Sonnenburg
2008-10-27 18:31 ` Johannes Berg
2008-10-27 18:44 ` Johannes Berg
2008-10-27 19:00 ` Carlos R. Mafra
2008-10-27 19:03 ` Johannes Berg
2008-10-27 19:11 ` Carlos R. Mafra
2008-10-27 19:13 ` Johannes Berg [this message]
2008-10-27 20:39 ` Carlos R. Mafra
2008-10-27 20:51 ` Rafael J. Wysocki
2008-10-27 20:52 ` Carlos R. Mafra
2008-10-27 21:07 ` Rafael J. Wysocki
2008-10-27 22:05 ` Carlos R. Mafra
2008-10-27 21:07 ` Tomas Winkler
2008-10-27 22:28 ` Carlos R. Mafra
2008-10-27 22:40 ` Tomas Winkler
2008-10-27 22:50 ` Rafael J. Wysocki
2008-10-27 23:12 ` Tomas Winkler
2008-10-27 23:23 ` Harvey Harrison
2008-10-28 15:30 ` Rafael J. Wysocki
2008-10-28 16:12 ` Tomas Winkler
2008-10-28 6:32 ` Christian Borntraeger
2008-10-27 19:06 ` Jens Axboe
2008-10-27 19:09 ` Johannes Berg
2008-10-27 19:13 ` Jens Axboe
2008-10-27 19:16 ` Johannes Berg
2008-10-27 19:20 ` Jens Axboe
2008-10-27 17:39 ` Rafael J. Wysocki
2008-10-27 17:57 ` Carlos R. Mafra
2008-10-27 18:00 ` John W. Linville
2008-10-27 18:16 ` Rafael J. Wysocki
2008-10-27 18:36 ` Carlos R. Mafra
2008-10-27 18:51 ` Carlos R. Mafra
2008-10-27 20:59 ` Christian Borntraeger
2008-10-27 21:06 ` Harvey Harrison
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=1225134823.3796.45.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=crmafra2@gmail.com \
--cc=kernel@nn7.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=rjw@sisk.pl \
--cc=tomas.winkler@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®