linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Zdenek Kabelac <zdenek.kabelac@gmail.com>,
	Johannes Berg <johannes@sipsolutions.net>
Cc: "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: Tue, 20 Jan 2009 12:55:00 +0100	[thread overview]
Message-ID: <20090120115500.GA4442@elte.hu> (raw)
In-Reply-To: <c4e36d110901200348n4009800dyebaf932039babf30@mail.gmail.com>


(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]
>  [<ffffffff8053fb5f>] ? _spin_unlock_bh+0x2f/0x40
>  [<ffffffff804c8d3a>] ? dev_deactivate+0x1aa/0x1d0
>  [<ffffffff804b751c>] ? dev_close+0x7c/0xd0
>  [<ffffffff804b70dd>] ? dev_change_flags+0x9d/0x1e0
>  [<ffffffff804c05a5>] ? do_setlink+0x2b5/0x440
>  [<ffffffff8053fb26>] ? _read_unlock+0x26/0x30
>  [<ffffffff804c0905>] ? rtnl_setlink+0x115/0x160
>  [<ffffffff8053dc54>] ? mutex_lock_nested+0x284/0x360
>  [<ffffffff804c187a>] ? rtnetlink_rcv+0x1a/0x40
>  [<ffffffff804c1a2d>] ? rtnetlink_rcv_msg+0x18d/0x240
>  [<ffffffff804c18a0>] ? rtnetlink_rcv_msg+0x0/0x240
>  [<ffffffff804cc879>] ? netlink_rcv_skb+0x89/0xb0
>  [<ffffffff804c1889>] ? rtnetlink_rcv+0x29/0x40
>  [<ffffffff804cc274>] ? netlink_unicast+0x2c4/0x2e0
>  [<ffffffff804ae57e>] ? __alloc_skb+0x6e/0x150
>  [<ffffffff804cc4a4>] ? netlink_sendmsg+0x214/0x310
>  [<ffffffff804a59d7>] ? sock_sendmsg+0x127/0x140
>  [<ffffffff8025d1f0>] ? autoremove_wake_function+0x0/0x40
>  [<ffffffff8027222b>] ? lock_release_non_nested+0x9b/0x2e0
>  [<ffffffff802dbd96>] ? fget_light+0x106/0x110
>  [<ffffffff804a6737>] ? move_addr_to_kernel+0x57/0x60
>  [<ffffffff804afa4f>] ? verify_iovec+0x3f/0xe0
>  [<ffffffff804a5b79>] ? sys_sendmsg+0x189/0x320
>  [<ffffffff804a683f>] ? sys_sendto+0xff/0x120
>  [<ffffffff802f4a8a>] ? mntput_no_expire+0x2a/0x170
>  [<ffffffff802dc06a>] ? __fput+0x17a/0x1f0
>  [<ffffffff8026ee5a>] ? trace_hardirqs_on_caller+0x16a/0x1d0
>  [<ffffffff8029232e>] ? audit_syscall_entry+0x17e/0x1a0
>  [<ffffffff8053f6de>] ? trace_hardirqs_on_thunk+0x3a/0x3f
>  [<ffffffff8020c51b>] ? system_call_fastpath+0x16/0x1b

	Ingo

  reply	other threads:[~2009-01-20 11:55 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 [this message]
2009-01-22 15:14                                         ` Zdenek Kabelac
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=20090120115500.GA4442@elte.hu \
    --to=mingo@elte.hu \
    --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=rjw@sisk.pl \
    --cc=zdenek.kabelac@gmail.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;
as well as URLs for NNTP newsgroup(s).