From: Zdenek Kabelac <zdenek.kabelac@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Johannes Berg <johannes@sipsolutions.net>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Dmitry Adamushko <dmitry.adamushko@gmail.com>,
Maciej Rutecki <maciej.rutecki@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
dbrownell@users.sourceforge.net
Subject: Re: 2.6.29-rc1 does not resume on Lenove T61
Date: Thu, 22 Jan 2009 16:14:42 +0100 [thread overview]
Message-ID: <c4e36d110901220714j524343c5k2673d5626aef2460@mail.gmail.com> (raw)
In-Reply-To: <20090120115500.GA4442@elte.hu>
2009/1/20 Ingo Molnar <mingo@elte.hu>:
>
> (Cc:-ed Johannes Berg)
>
> * Zdenek Kabelac <zdenek.kabelac@gmail.com> wrote:
>
>> With network enabled - the error is back - thus it might be a bug in
>> ieee80211 stack ??
>
> yes, the crash implicates the ieee80211 stack [ieee80211_stop() in
> net/mac80211/iface.c]:
>
>> general protection fault: 0000 [#1] SMP
>> RIP: 0010:[<ffffffff8053ce01>] [<ffffffff8053ce01>] wait_for_common+0x131/0x190
>> Process NetworkManager (pid: 2265, threadinfo ffff88006b508000, task
>> Call Trace:
>> [<ffffffff8025a735>] synchronize_rcu+0x35/0x40
>> [<ffffffff8025a620>] ? wakeme_after_rcu+0x0/0x10
>> [<ffffffff8053ce3f>] ? wait_for_common+0x16f/0x190
>> [<ffffffff8024b424>] ? local_bh_enable+0xa4/0x110
>> [<ffffffff804c8ce1>] ? dev_deactivate+0x151/0x1d0
>> [<ffffffff804b750d>] ? dev_close+0x6d/0xd0
>> [<ffffffffa016b042>] ? ieee80211_stop+0x562/0x570 [mac80211]
>> [<ffffffffa016ab59>] ? ieee80211_stop+0x79/0x570 [mac80211]
Any progress with this problem ?
Btw - I've tried your branch tip-latest
(52a4061e1d88ad242c8022f68df3686c3bc05159)
- and this branch now resets my machine during resume. (it suspends -
auto-wake-up and reboots)
- so it this branch actually suggested to be used/tested ?
Zdenek
next prev parent reply other threads:[~2009-01-22 15:14 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-11 19:52 2.6.29-rc1 does not resume on Lenove T61 Zdenek Kabelac
2009-01-11 20:15 ` Maciej Rutecki
2009-01-11 22:59 ` Zdenek Kabelac
2009-01-12 8:03 ` Rafael J. Wysocki
2009-01-12 9:15 ` Maciej Rutecki
2009-01-12 9:23 ` Oliver Neukum
2009-01-12 12:14 ` Zdenek Kabelac
2009-01-12 12:40 ` Rafael J. Wysocki
2009-01-12 12:50 ` Zdenek Kabelac
2009-01-12 17:19 ` Rafael J. Wysocki
2009-01-13 22:36 ` Zdenek Kabelac
2009-01-13 22:41 ` Zdenek Kabelac
2009-01-19 9:54 ` Zdenek Kabelac
2009-01-19 15:59 ` Dmitry Adamushko
2009-01-19 16:13 ` Ingo Molnar
2009-01-19 16:41 ` Dmitry Adamushko
2009-01-19 16:44 ` Ingo Molnar
2009-01-19 19:25 ` Rafael J. Wysocki
2009-01-19 22:31 ` Zdenek Kabelac
2009-01-19 23:49 ` Ingo Molnar
2009-01-20 10:41 ` Zdenek Kabelac
2009-01-20 11:48 ` Zdenek Kabelac
2009-01-20 11:55 ` Ingo Molnar
2009-01-22 15:14 ` Zdenek Kabelac [this message]
2009-01-22 21:17 ` Rafael J. Wysocki
2009-01-28 11:05 ` Zdenek Kabelac
2009-02-02 14:41 ` Zdenek Kabelac
2009-01-13 14:04 ` Michal Hocko
2009-01-12 0:48 ` Heiko Carstens
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=c4e36d110901220714j524343c5k2673d5626aef2460@mail.gmail.com \
--to=zdenek.kabelac@gmail.com \
--cc=dbrownell@users.sourceforge.net \
--cc=dmitry.adamushko@gmail.com \
--cc=hmh@hmh.eng.br \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.rutecki@gmail.com \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
/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).