| 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
| ||
|
Date: Sat, 16 Feb 2013 11:25:54 -0800 From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com> To: Linus Torvalds <torvalds@...ux-foundation.org> Cc: Frederic Weisbecker <fweisbec@...il.com>, Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...nel.org>, Peter Zijlstra <peterz@...radead.org>, Dave Jones <davej@...hat.com>, Hugh Dickins <hughd@...gle.com>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Paul McKenney <paul.mckenney@...aro.org> Subject: Re: Debugging Thinkpad T430s occasional suspend failure. On Fri, Feb 15, 2013 at 10:50:31AM -0800, Linus Torvalds wrote: > On Fri, Feb 15, 2013 at 10:35 AM, Linus Torvalds > <torvalds@...ux-foundation.org> wrote: > > On Fri, Feb 15, 2013 at 10:34 AM, Linus Torvalds > > <torvalds@...ux-foundation.org> wrote: > >> > >> Something like this ENTIRELY UNTESTED patch. > > > > .. and let's actually attach the patch this time. > > That's odd. I got a "server error" from gmail. And again no attachment. > > Maybe THIS time. Sorry for the delay in testing this, but there was a need to upgrade my laptop, and bozo here figured "why not go to 64 bits while I am at it?" -- and then proceeded to learn the hard way that it is necessary to do "make mrproper" before doing a build in 64-bit mode. :-/ The kernel build system's way of telling you this at the moment is: arch/x86/built-in.o:(.rodata+0x4990): undefined reference to `stub32_sigaltstack' Anyway, with this patch, I see CPU stall warnings when running rcutorture as shown below. This is not a hard failure: [ 32.553647] rcu-torture: rtc: ffffffff836a57a0 ver: 131 tfle: 0 rta: 131 rtaf: 0 rtf: 93 rtmbe: 0 rtbke: 0 rtbre: 0 rtbf: 0 rtb: 0 nt: 27 onoff: 0/0:0/0 -1,0:-1,0 0:0 (HZ=1000) barrier: 6/7:0 Note the "ver: 131", which means that rcutorture successfully did 131 grace periods before the failure. It manages to offline a CPU subsequently, but then appears to hang while onlining it. Thanx, Paul [ 23.706051] INFO: rcu_preempt self-detected stall on CPU[ 23.707053] INFO: rcu_preempt self-detected stall on CPU [ 23.707053] 1: (20976 ticks this GP) idle=883/140000000000001/0 drain=5 . timer not pending [ 23.707053] (t=21000 jiffies g=85 c=84 q=6756) [ 23.707053] Pid: 606, comm: rcu_torture_rea Not tainted 3.8.0-rc7+ #2 [ 23.707053] Call Trace: [ 23.707053] <IRQ> [<ffffffff810c12b2>] rcu_pending+0x192/0x7a0 [ 23.707053] [<ffffffff810c590b>] rcu_check_callbacks+0xbb/0x220 [ 23.707053] [<ffffffff8104c193>] update_process_times+0x43/0x80 [ 23.707053] [<ffffffff8108f901>] tick_sched_handle.isra.8+0x31/0x40 [ 23.707053] [<ffffffff8108f9f7>] tick_sched_timer+0x47/0x70 [ 23.707053] [<ffffffff8106619c>] __run_hrtimer+0x7c/0x240 [ 23.707053] [<ffffffff8108f9b0>] ? tick_nohz_handler+0xa0/0xa0 [ 23.707053] [<ffffffff81089617>] ? ktime_get_update_offsets+0x47/0xd0 [ 23.707053] [<ffffffff81066a37>] hrtimer_interrupt+0xf7/0x240 [ 23.707053] [<ffffffff81025883>] smp_apic_timer_interrupt+0x63/0xa0 [ 23.707053] [<ffffffff817b6e8a>] apic_timer_interrupt+0x6a/0x70 [ 23.707053] <EOI> [<ffffffff817af17d>] ? _raw_spin_unlock_irq+0xd/0x40 [ 23.707053] [<ffffffff817ae2aa>] __schedule+0x68a/0x790 [ 23.707053] [<ffffffff817ae4c4>] schedule+0x24/0x70 [ 23.707053] [<ffffffff810c05b7>] rcu_torture_reader+0xd7/0x2d0 [ 23.707053] [<ffffffff810c07b0>] ? rcu_torture_reader+0x2d0/0x2d0 [ 23.707053] [<ffffffff810c04e0>] ? rcutorture_trace_dump+0x50/0x50 [ 23.707053] [<ffffffff81061e6b>] kthread+0xbb/0xc0 [ 23.707053] [<ffffffff817a0000>] ? timer_cpu_notify+0x1e9/0x300 [ 23.707053] [<ffffffff81061db0>] ? flush_kthread_worker+0xa0/0xa0 [ 23.707053] [<ffffffff817b626c>] ret_from_fork+0x7c/0xb0 [ 23.707053] [<ffffffff81061db0>] ? flush_kthread_worker+0xa0/0xa0 [ 23.706051] [ 23.706051] 0: (1 GPs behind) idle=429/140000000000001/0 drain=5 . timer not pending [ 23.706051] (t=21000 jiffies g=85 c=84 q=6756) [ 23.706051] Pid: 603, comm: rcu_torture_rea Not tainted 3.8.0-rc7+ #2 [ 23.706051] Call Trace: [ 23.706051] <IRQ> [<ffffffff810c12b2>] rcu_pending+0x192/0x7a0 [ 23.706051] [<ffffffff810c590b>] rcu_check_callbacks+0xbb/0x220 [ 23.706051] [<ffffffff8104c193>] update_process_times+0x43/0x80 [ 23.706051] [<ffffffff8108f901>] tick_sched_handle.isra.8+0x31/0x40 [ 23.706051] [<ffffffff8108f9f7>] tick_sched_timer+0x47/0x70 [ 23.706051] [<ffffffff8106619c>] __run_hrtimer+0x7c/0x240 [ 23.706051] [<ffffffff8108f9b0>] ? tick_nohz_handler+0xa0/0xa0 [ 23.706051] [<ffffffff81089617>] ? ktime_get_update_offsets+0x47/0xd0 [ 23.706051] [<ffffffff81066a37>] hrtimer_interrupt+0xf7/0x240 [ 23.706051] [<ffffffff81025883>] smp_apic_timer_interrupt+0x63/0xa0 [ 23.706051] [<ffffffff817b6e8a>] apic_timer_interrupt+0x6a/0x70 [ 23.706051] <EOI> [<ffffffff817b2ae0>] ? add_preempt_count+0x30/0x90 [ 23.706051] [<ffffffff817adc5d>] __schedule+0x3d/0x790 [ 23.706051] [<ffffffff817ae4c4>] schedule+0x24/0x70 [ 23.706051] [<ffffffff810c05b7>] rcu_torture_reader+0xd7/0x2d0 [ 23.706051] [<ffffffff810c07b0>] ? rcu_torture_reader+0x2d0/0x2d0 [ 23.706051] [<ffffffff810c04e0>] ? rcutorture_trace_dump+0x50/0x50 [ 23.706051] [<ffffffff81061e6b>] kthread+0xbb/0xc0 [ 23.706051] [<ffffffff817a0000>] ? timer_cpu_notify+0x1e9/0x300 [ 23.706051] [<ffffffff81061db0>] ? flush_kthread_worker+0xa0/0xa0 [ 23.706051] [<ffffffff817b626c>] ret_from_fork+0x7c/0xb0 [ 23.706051] [<ffffffff81061db0>] ? flush_kthread_worker+0xa0/0xa0 -- 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/
Powered by blists - more mailing lists