linux-kernel - Re: 2.6.29-rc1 does not resume on Lenove T61

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 20 Jan 2009 12:55:00 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Zdenek Kabelac <zdenek.kabelac@...il.com>,
	Johannes Berg <johannes@...solutions.net>
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>,
	Dmitry Adamushko <dmitry.adamushko@...il.com>,
	Maciej Rutecki <maciej.rutecki@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Henrique de Moraes Holschuh <hmh@....eng.br>,
	dbrownell@...rs.sourceforge.net
Subject: Re: 2.6.29-rc1 does not resume on Lenove T61


(Cc:-ed Johannes Berg)

* Zdenek Kabelac <zdenek.kabelac@...il.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/