[opensuse-kernel] 3.5 stable somewhere ?
Hi:
I see Kernel:Stable has been upgraded to 3.6 .. I currently cannot
upgrade a box to 3.6 because the kernel crashes after a while, bug that
still exist in current linus tree.. are 3.5 kernels preserved somewhere.. ?
BTW.. here is the crash.. is just a matter of generating a little load
on apache2-event and something goes crazy.
Sep 30 10:44:40 ex6 kernel: INFO:f- o=15000 jiff- o=15000 jiffi o=15000
jiffies=15000 jiffies)
Sep 30 10:44:40 ex6 kernel: sending NMI to all CPUs:
Sep 30 10:44:40 ex6 kernel: NMI backtrace for cpu 6
Sep 30 10:44:40 ex6 kernel: CPU 6
Sep 30 10:44:40 ex6 kernel: Pid: 7369, comm: httpd2-event Not tainted
3.6.0-rc7-canneverbe-00121-g8110e16-dirty #5 System manufacturer System
Product Name/P8B WS
Sep 30 10:44:40 ex6 kernel: RIP: 0010:[<ffffffff814f0aba>]
[<ffffffff814f0aba>] _raw_spin_lock_bh+0x2a/0x40
Sep 30 10:44:40 ex6 kernel: RSP: 0018:ffff880264f55ee8 EFLAGS: 00000297
Sep 30 10:44:40 ex6 kernel: RAX: 00000000000006f3 RBX: ffff88027b702890
RCX: 0000000000000001
Sep 30 10:44:40 ex6 kernel: RDX: 00000000000006f4 RSI: 0000000000000000
RDI: ffff88027b702890
Sep 30 10:44:40 ex6 kernel: RBP: ffff880264f55ef8 R08: ffff880407933eb0
R09: 0000000000001cc9
Sep 30 10:44:40 ex6 kernel: R10: 00007fdd7c6c5d40 R11: 0000000000000202
R12: 0000000000000002
Sep 30 10:44:40 ex6 kernel: R13: ffff88033480dd00 R14: 00000000ffffffea
R15: 00007fdd840522b8
Sep 30 10:44:40 ex6 kernel: FS: 00007fdd7c6c6700(0000)
GS:ffff88041f380000(0000) knlGS:0000000000000000
Sep 30 10:44:40 ex6 kernel: CS: E000000080050
E00000008005003000000080050033
Sep 30 10:44:40 ex6 kernel: CR2: 00007fdd1f373000 CR3: 0000000264d17000
CR4: 00000000000407e0
Sep 30 10:44:40 ex6 kernel: DR0: 0000000000000000 DR1: 0000000000000000
DR2: 0000000000000000
Sep 30 10:44:40 ex6 kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0
DR7: 0000000000000400
Sep 30 10:44:40 ex6 kernel: Process httpd2-event (pid: 7369, threadinfo
ffff880264f54000, task ffff880264f52040)
Sep 30 10:44:40 ex6 kernel: Stack:
Sep 30 10:44:40 ex6 kernel: ffff880261d112e8 ffff88027b702840
ffff880264f55f18 ffffffff81405795
Sep 30 10:44:40 ex6 kernel: 0000000100000104 ffff88027b702840
ffff880264f55f48 ffffffff81476bd1
Sep 30 10:44:40 ex6 kernel: ffff88033480dd00 0000000000000001
0004cae74d89c0a4 00007fdd8d0f34a0
Sep 30 10:44:40 ex6 kernel: Call Trace:
Sep 30 10:44:40 ex6 kernel: [<ffffffff81405795>] lock_sock_nested+0x15/0x40
Sep 30 10:44:40 ex6 kernel: [<ffffffff81476bd1>] inet_shutdown+0x41/0x130
Sep 30 10:44:40 ex6 kernel: [<ffffffff81402ed5>] sys_shutdown+0x75/0x80
Sep 30 10:44:40 ex6 kernel: [<ffffffff814f8226>]
system_call_fastpath+0x1a/0x1f
Sep 30 10:44:40 ex6 kernel: Code: 90 55 48 89 e5 53 48 89 fb 48 83 ec 08
e8 7f 2c b5 ff b8 00 00 01 00 f0 0f c1 03 89 c2 c1 ea 10 66 39 c2 74 0e
0f 1f 40 00 f3 90 <0f> b7 03 66 39 d0 75 f6 48 83 c4 08 5b 5d c3 0f 1f
80 00 00 00
Sep 30 10:44:40 ex6 kernel: NMI backtrace for cpu 3
Sep 30 10:44:40 ex6 kernel: CPU 3
Sep 30 10:44:40 ex6 kernel: Pid: 0, comm: swapper/3 Not tainted
3.6.0-rc7-canneverbe-00121-g8110e16-dirty #5 System manufacturer System
Product Name/P8B WS
Sep 30 10:44:40 ex6 kernel: RIP: 0010:[<ffffffff812ad91d>]
[<ffffffff812ad91d>] find_next_bit+0x3d/0xc0
Sep 30 10:44:40 ex6 kernel: RSP: 0018:ffff88041f2c37c0 EFLAGS: 00000046
Sep 30 10:44:40 ex6 kernel: RAX: 0000000000000000 RBX: 00000000000000ff
RCX: 0000000000000001
Sep 30 10:44:40 ex6 kernel: RDX: 0000000000000001 RSI: 0000000000000200
RDI: 0000000000000200
Sep 30 10:44:40 ex6 kernel: RBP: ffff88041f2c37c0 R08: ffff88041f2ccec0
R09: 0000000000000000
Sep 30 10:44:40 ex6 kernel: R10: 0000000000000000 R11: 000000000000045a
R12: ffff88041f2ccec0
Sep 30 10:44:40 ex6 kernel: R13: ffff88041f20cf00 R14: 0000000000080000
R15: 000000000000cf40
Sep 30 10:44:40 ex6 kernel: FS: 0000000000000000(0000)
GS:ffff88041f2c0000(0000) knlGS:0000000000000000
Sep 30 10:44:40 ex6 kernel: CS: 0010 DS: 0000 ES: 0000 CR0:
000000008005003b
Sep 30 10:44:40 ex6 kernel: CR2: 00007fdd1f7bf028 CR3: 0000000001a0c000
CR4: 00000000000407e0
Sep 30 10:44:40 ex6 kernel: DR0: 0000000000000000 DR1: 0000000000000000
DR2: 0000000000000000
Sep 30 10:44:40 ex6 kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0
DR7: 0000000000000400
Sep 30 10:44:40 ex6 kernel: Process swapper/3 (pid: 0, threadinfo
ffff88040abb0000, task ffff88040abae300)
Sep 30 10:44:40 ex6 kernel: Stack:
Sep 30 10:44:40 ex6 kernel:
ffff88ffff0000000000ffff000000000000ff00000000000008000000000000082
Sep 30 10:44:40 ex6 kernel: 000000031f2c3840 000000000000cf00
0000000000000002 0000000000000003
Sep 30 10:44:40 ex6 kernel: ffff88041f2c3850 0000000000002710
ffffffff81a2c580 0000000000000003
Sep 30 10:44:40 ex6 kernel: Call Trace:
Sep 30 10:44:40 ex6 kernel: <IRQ>
Sep 30 10:44:40 ex6 kernel: [<ffffffff810288b6>]
__x2apic_send_IPI_mask+0xb6/0x180
Sep 30 10:44:40 ex6 kernel: [<ffffffff81028997>]
x2apic_send_IPI_all+0x17/0x20
Sep 30 10:44:40 ex6 kernel:
4dgetrace+0x544dgetrace+0x54/0getrace+0x54/0xatrace+0x54/0xa0
Sep 30 10:44:40 ex6 kernel: [<ffffffff810cb8ca>] rcu_pending+0x22a/0x580
Sep 30 10:44:40 ex6 kernel: [<ffffffff810765fc>] ?
trigger_load_balance+0x5c/0x220
Sep 30 10:44:40 ex6 kernel: [<ffffffff810cc479>]
rcu_check_callbacks+0x99/0x130
Sep 30 10:44:40 ex6 kernel: [<ffffffff8104c6b3>]
update_process_times+0x43/0x80
Sep 30 10:44:40 ex6 kernel: [<ffffffff8108faeb>] tick_sched_timer+0x6b/0xe0
Sep 30 10:44:40 ex6 kernel: [<ffffffff81061aca>] __run_hrtimer+0x6a/0x1c0
Sep 30 10:44:40 ex6 kernel: [<ffffffff8108fa80>] ?
tick_nohz_handler+0x100/0x100
Sep 30 10:44:40 ex6 kernel: [<ffffffff810623cf>]
hrtimer_interrupt+0xef/0x220
Sep 30 10:44:40 ex6 kernel: [<ffffffff81023c14>]
smp_apic_timer_interrupt+0x64/0xa0
Sep 30 10:44:40 ex6 kernel: [<ffffffff814f8e07>]
apic_timer_interrupt+0x67/0x70
Sep 30 10:44:40 ex6 kernel: [<30start+0x70/030start+0x70/0xastart+0x70/0xa0
Sep 30 10:44:40 ex6 kernel: [<ffffffff8148b926>]
bictcp_cong_avoid+0x56/0x3e0
Sep 30 10:44:40 ex6 kernel: [<ffffffff81042efd>] ? ns_to_timeval+0xd/0x40
Sep 30 10:44:40 ex6 kernel: [<ffffffff8145c182>] tcp_ack+0x572/0x1210
Sep 30 10:44:40 ex6 kernel: [<ffffffff8145d06e>]
tcp_rcv_established+0x24e/0x6e0
Sep 30 10:44:40 ex6 kernel: [<ffffffff81466211>] tcp_v4_do_rcv+0xe1/0x330
Sep 30 10:44:40 ex6 kernel: [<ffffffff81238c61>] ?
security_sock_rcv_skb+0x11/0x20
Sep 30 10:44:40 ex6 kernel: [<ffffffff81428492>] ? sk_filter+0x32/0xd0
Sep 30 10:44:40 ex6 kernel: [<ffffffff814675f3>] tcp_v4_rcv+0x6d3/0x7c0
Sep 30 10:44:40 ex6 kernel: [<ffffffff8143e14c>] ? nf_hook_slow+0x6c/0x130
Sep 30 10:44:40 ex6 kernel: [<ffffffff81444110>] ?
ip_rcv_finish+0x360/0x360
Sep 30 10:44:40 ex6 kernel: [<ffffffff81444180>]
ip_local_deliver_finish+0x70/0x1c0
Sep 30 10:44:40 ex6 kernel: [<ffffffff81444452>] ip_local_deliver+0x42/0x80
Sep 30 10:44:40 ex6 kernel: [<ffffffff81443e2b>] ip_rcv_finish+0x7b/0x360
Sep 30 10:44:40 ex6 kernel: [<ffffffff81444696>] ip_rcv+0x206/0x310
Sep 30 10:44:40 ex6 kernel: [<ffffffff810237b8>] ?
lapic_next_event+0x18/0x20
Sep 30 10:44:40 ex6 kernel: [<ffffffff81416e62>]
__netif_receive_skb+0x5c2/0x730
Sep 30 10:44:40 ex6 kernel: [<ffffffff812a4dc4>] ? timerqueue_add+0x74/0xc0
Sep 30 10:44:40 ex6 kernel: [<6cklog+0x9c/0x6cklog+0x9c/0x17klog+0x9c/0x170
Sep 30 10:44:40 ex6 kernel: [<ffffffff81061f7f>] ?
__hrtimer_start_range_ns+0x1bf/0x410
Sep 30 10:44:40 ex6 kernel: [<ffffffff81417adb>] net_rx_action+0xab/0x190
Sep 30 10:44:40 ex6 kernel: [<ffffffff8104c5bf>] ?
get_next_timer_interrupt+0x1df/0x270
Sep 30 10:44:40 ex6 kernel: [<ffffffff81044090>] __do_softirq+0xc0/0x1f0
Sep 30 10:44:40 ex6 kernel: [<ffffffff81090069>] ?
tick_nohz_stop_idle+0x39/0x40
Sep 30 10:44:40 ex6 kernel: [<ffffffff814f94ec>] call_softirq+0x1c/0x30
Sep 30 10:44:40 ex6 kernel: [<ffffffff810043cd>] do_softirq+0x4d/0x80
Sep 30 10:44:40 ex6 kernel: [<ffffffff81044445>] irq_exit+0xa5/0xb0
Sep 30 10:44:40 ex6 kernel: [<ffffffff81022f7f>]
smp_call_function_single_interrupt+0x2f/0x40
Sep 30 10:44:40 ex6 kernel: [<ffffffff814f8fc7>]
call_function_single_interrupt+0x67/0x70
Sep 30 10:44:40 ex6 kernel: <EOI>
Sep 30 10:44:40 ex6 kernel: [<ffffffff810622da>] ?
hrtimer_get_next_event+0xca/0xd0
Sep 30 10:44:40 ex6 kernel: [<ffffffff812ebe4b>] ? intel_idle+0xeb/0x150
Sep 30 10:44:40 ex6 kernel: [<ffffffff812ebe29>] ? intel_idle+0xc9/0x150
Sep 30 10:44:40 ex6 kernel: [<ffffffff813e1bf9>] cpuidle_enter+0x19/0x20
Sep 30 10:44:40 ex6 kernel: [<ffffffff813e226d>]
cpuidle_idle_call+0x9d/0x1b0
Sep 30 10:44:40 ex6 kernel: [<ffffffff8100ae0f>] cpu_idle+0x5f/0xd0
Sep 30 10:44:40 ex6 kernel: [<ffffffff814dffcb>]
start_secondary+0x1f4/0x1f6
Sep 30 10:44:40 ex6 kernel: Code: d1 49 89 d1 48 c1 e9 06 49 83 e1 c0 4c
8d 04 cf 48 89 f7 48 89 d1 4c 29 cf 83 e1 3f 74 44 48 c7 c0 ff ff ff ff
48 d3 e0 49 23 00 <48> 83 ff 3f 76 45 48 85 c0 75 56 49 83 c0 08 48 83
ef 40 49 83
Sep 30 10:44:40 ex6 kernel: NMI backtrace for cpu 0
Sep 30 10:44:40 ex6 kernel: CPU 0
Sep 30 10:44:40 ex6 kernel: Pid: 0, comm: swapper/0 Not tainted
3.6.0-rc7-canneverbe-00121-g8110e16-dirty #5 System manufacturer System
Product Name/P8B WS
Sep 30 10:44:40 ex6 kernel: RIP: 0010:[<ffffffff812ac144>]
[<ffffffff812ac144>] __bitmap_weight+0x24/0x80
Sep 30 10:44:40 ex6 kernel: RSP: 0018:ffff8FLAGS: 0000020FLAGS: 00000206
Sep 30 10:44:40 ex6 kernel: RAX: 0000000000000000 RBX: ffff88041f2129c0
RCX: 0000000000000000
Sep 30 10:44:40 ex6 kernel: RDX: 0000000000000005 RSI: 0000000000000200
RDI: 0000000000000000
Sep 30 10:44:40 ex6 kernel:
RBP:ce000000000000ce000000000000000000000000000000000000000000008
Sep 30 10:44:40 ex6 kernel: R10: ffff88040a49e558 R11: 0000000000000000
R12: 0000000000000000
Sep 30 10:44:40 ex6 kernel: R13: 0000000000000000 R14: ffff88040a4e7e00
R15: 0000000000000001
Sep 30 10:44:40 ex6 kernel: FS: 0000000000000000(0000)
GS:ffff88041f200000(0000) knlGS:0000000000000000
Sep 30 10:44:40 ex6 kernel: CS: 0010 DS: 0000 ES: 0000 CR0:
000000008005003b
Sep 30 10:44:40 ex6 kernel: CR2: 00007fdd1f361000 CR3: 0000000001a0c000
CR4: 00000000000407f0
Sep 30 10:44:40 ex6 kernel: DR0: 0000000000000000 DR1: 0000000000000000
DR2: 0000000000000000
Sep 30 10:44:40 ex6 kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0
DR7: 0000000000000400
Sep 30 10:44:40 ex6 kernel: Process swapper/0 (pid: 0, threadinfo
ffffffff81a00000, task ffffffff81a14420)
Sep 30 10:44:40 ex6 kernel: Stack:
Sep 30 10:44:40 ex6 kernel: ffff88041f203e00 ffffffff81075952
ffff88041f20d8c0 0000000000000001
Sep 30 10:44:40 ex6 kernel: ffff88041f203d30 ffffffff812a4dc4
ffff88041f20db00 000000001f20db00
Sep 30 10:44:40 ex6 kernel: ffff88041f203e3c ffff88041f20d8c0
ffff88041f203d60 ffffffff00000000
Sep 30 10:44:40 ex6 kernel: Call Trace:
Sep 30 10:44:40 ex6 kernel: <IRQ>
Sep 30 10:44:40 ex6 kernel: [<ffffffff81075952>] load_balance+0xf2/0x830
Sep 30 10:44:40 ex6 kernel: [<ffffffff812a4dc4>] ? timerqueue_add+0x74/0xc0
Sep 30 10:44:40 ex6 kernel: [<ffffffff810887cd>] ? ktime_get+0x4d/0xd0
Sep 30 10:44:40 ex6 kernel: [<ffffffff810237b8>] ?
lapic_next_event+0x18/0x20
Sep 30 10:44:40 ex6 kernel: [<ffffffff8107612d>]
rebalance_domains+0x9d/0x180
Sep 30 10:44:40 ex6 kernel: [<ffffffff81076257>]
run_rebalance_domains+0x47/0x160
Sep 30 10:44:40 ex6 kernel: [<ffffffff81044090>] __do_softirq+0xc0/0x1f0
Sep 30 10:44:40 ex6 kernel: [<ffffffff81090069>] ?
tick_nohz_stop_idle+0x39/0x40
Sep 30 10:44:40 ex6 kernel: [<ffffffff814f94ec>] call_softirq+0x1c/0x30
Sep 30 10:44:40 ex6 kernel: [<ffffffff810043cd>] do_softirq+0x4d/0x80
Sep 30 10:44:40 ex6 kernel: [<ffffffff81044445>] irq_exit+0xa5/0xb0
Sep 30 10:44:40 ex6 kernel: [<ffffffff8106c53d>] scheduler_ipi+0x5d/0x110
Sep 30 10:44:40 ex6 kernel: [<ffffffff81022f05>]
smp_reschedule_interrupt+0x25/0x30
Sep 30 10:44:40 ex6 kernel: [<ffffffff814f90a7>]
reschedule_interrupt+0x67/0x70
Sep 30 10:44:40 ex6 kernel: <EOI>
Sep 30 10:44:40 ex6 kernel: [<ffffffff812ebe4b>] ? intel_idle+0xeb/0x150
Sep 30 10:44:40 ex6 kernel: [<ffffffff812ebe29>] ? intel_idle+0xc9/0x150
Sep 30 10:44:40 ex6 kernel: [<ffffffff813e1bf9>] cpuidle_enter+0x19/0x20
Sep 30 10:44:40 ex6 kernel: [<ffffffff813e226d>]
cpuidle_idle_call+0x9d/0x1b0
Sep 30 10:44:40 ex6 kernel: [<ffffffff8100ae0f>] cpu_idle+0x5f/0xd0
Sep 30 10:44:40 ex6 kernel: [<ffffffff814cfb49>] rest_init+0x6d/0x74
Sep 30 10:44:40 ex6 kernel: [<ffffffff81ab5b7c>] start_kernel+0x36e/0x37b
Sep 30 10:44:40 ex6 kernel: [<ffffffff81ab560d>] ?
repair_env_string+0x5e/0x5e
Sep 30 10:44:40 ex6 kernel: [<ffffffff81ab532d>]
x86_64_start_reservations+0x131/0x135
Sep 30 10:44:40 ex6 kernel: [<ffffffff81ab5409>]
x86_64_start_kernel+0xd8/0xdc
Sep 30 10:44:40 ex6 kernel: Code: 1f 84 00 00 00 00 00 85 f6 55 49 89 fa
44 8d 4e 3f 48 89 e5 44 0f 49 ce 41 c1 f9 06 45 85 c9 7e 51 31 d2 45 31
c0 90 49 8b 3c d2 <48> 83 c2 01 f3 48 0f b8 c7 41 01 c0 41 39 d1 7f eb
40 f6 c6 3f
Sep 30 10:44:40 ex6 kernel: NMI backtrace for cpu 4
Sep 30 10:44:40 ex6 kernel: CPU 4
Sep 30 10:44:40 ex6 kernel: Pid: 0, comm: swapper/4 Not tainted
3.6.0-rc7-canneverbe-00121-g8110e16-dirty #5 System manufacturer System
Product Name/P8B WS
Sep 30 10:44:40 ex6 kernel: RIP: 0010:[<ffffffff812ac150>]
[<ffffffff812ac150>] __bitmap_weight+0x30/0x80
Sep 30 10:44:40 ex6 kernel: RSP: 0018:ffff88041f303cf0 EFLAGS: 00000202
Sep 30 10:44:40 ex6 kernel:
RAX:0041000000000000410000000000004100000000000000000000000000000
Sep 30 10:44:40 ex6 kernel: RDX: 0000000000000005 RSI: 0000000000000200
RDI: 0000000000000000
Sep 30 10:44:40 ex6 kernel: RBP: ffff88041f303cf0 R08: 0000000000000002
R09: 0000000000000008
Sep 30 10:44:40 ex6 kernel: R10: ffff88040a4e8bd8 R11: 0000000000000000
R12: 0000000000000000
Sep 30 10:44:40 ex6 kernel: R13: 0000000000000001 R14: ffff88040a4e9600
R15: 0000000000000001
Sep 30 10:44:40 ex6 kernel: FS: 0000000000000000(0000)
GS:ffff88041f300000(0000) knlGS:0000000000000000
Sep 30 10:44:40 ex6 kernel: CS: E000000080050
E0000000800500300000008005003b
Sep 30 10:44:40 ex6 kernel: CR2: 00007fdd1f595000 CR3: 0000000001a0c000
CR4: 00000000000407e0
Sep 30 10:44:40 ex6 kernel: DR0: 0000000000000000 DR1: 0000000000000000
DR2: 0000000000000000
Sep 30 10:44:40 ex6 kernel:
DR3:000f0000000000000f0000000000000f00000000000040000000000000400
Sep 30 10:44:40 ex6 kernel: Process swapper/4 (pid: 0, threadinfo
ffff88040abb4000, task ffff88040abb2340)
Sep 30 10:44:40 ex6 kernel: Stack:
Sep 30 10:44:40 ex6 kernel: ffff88041f303e10 ffffffff81075952
ffff88041f303d30 ffffffff81444180
Sep 30 10:44:40 ex6 kernel: ffff8804074ccec0 ffff88026e93104e
ffff880407b94000 0000000400000000
Sep 30 10:44:40 ex6 kernel: ffff88041f303e4c ffffffff81444452
ffff880280000000 ffff880400000000
Sep 30 10:44:40 ex6 kernel: Call Trace:
Sep 30 10:44:40 ex6 kernel: <IRQ>
Sep 30 10:44:40 ex6 kernel: [
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/04/2012 09:12 PM, Cristian Rodríguez wrote:
are 3.5 kernels preserved somewhere.. ?
Yes and no. Yes in the git tree and in the OBS history. You can link to the kernel:stable repo just before the update and build the kernel yourself. No, not in binary.
BTW.. here is the crash.. is just a matter of generating a little load on apache2-event and something goes crazy.
Is there a fix known? The traces below look pretty hopeless. Are they the first info printed? What's before them?
Sep 30 10:44:40 ex6 kernel: INFO:f- o=15000 jiff- o=15000 jiffi o=15000 jiffies=15000 jiffies) Sep 30 10:44:40 ex6 kernel: sending NMI to all CPUs: Sep 30 10:44:40 ex6 kernel: NMI backtrace for cpu 6 Sep 30 10:44:40 ex6 kernel: CPU 6 Sep 30 10:44:40 ex6 kernel: Pid: 7369, comm: httpd2-event Not tainted 3.6.0-rc7-canneverbe-00121-g8110e16-dirty #5 System manufacturer System Product Name/P8B WS Sep 30 10:44:40 ex6 kernel: RIP: 0010:[<ffffffff814f0aba>] [<ffffffff814f0aba>] _raw_spin_lock_bh+0x2a/0x40
- -- js suse labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQIcBAEBAgAGBQJQbetYAAoJEL0lsQQGtHBJRBMP/iJKWPV4ibH7n+qyUIjXSpAJ GZldGSCYtBuxqfvAQHwVP054Z8qFVorg9zavX5RC+YV+yWIlEuZmdoy5C50ZMOWE 52bPVFy4u1m8NNVZt73eTK3UOvdoDOeV0Dk28AF1NWB/6d+r1QfzsBJXtz22JmO1 x0KwIn+9RQTm6PWJcxVQTNTMIlXnjTIOK1lGlXA5TWpL5i1X9knbKUfkar/GsCRa egjSiAWSk2RqQmIguICSuEd88bj/V+c1OxsVM2DnbxwEthdeqVU+WIYpMo5iKoJr NYxaHO2mBdzwLOSc5zvINBUBKlYrEIUB4L41Q6FMFokItXKqdO4Acl9nNmsTRqFC DH5pFL+bEAR38SlpoZd3QoT3Ceq9UJjC/MJlw82u4fq7mxpH7F1XWi9BnH9M731Z Zrw8OdgqrJsxVzaD7VGf4BQr6hJitYUbCyHurEt6gh53VofMbVvR/v3CVMQg/X84 j80KoN9Vsqyir10wXHaBMNdHvEsng75Yksuw+mf2k5F64NcwLosQkTEIUz4mmFoi WQVRn9h6x23i7dgY2w4R2OsM64WG5xjJuNR042Nn2UJ5zBHVb4Plrfove/SUXwFk 5mc0ako22KBGsjJ6TkO7uwgtxGu2IEIahodG2IoP8UjDzHNnhMUbwMsE7wlq0PFB l6txVQhOrve/MlMVU93A =rjDf -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
El jue 04 oct 2012 17:02:32 CLST, Jiri Slaby escribió:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 10/04/2012 09:12 PM, Cristian Rodríguez wrote:
are 3.5 kernels preserved somewhere.. ?
Yes and no.
Yes in the git tree and in the OBS history. You can link to the kernel:stable repo just before the update and build the kernel yourself.
No, not in binary.
BTW.. here is the crash.. is just a matter of generating a little load on apache2-event and something goes crazy.
Is there a fix known?
Nope :-| The traces below look pretty hopeless. Are they
the first info printed? What's before them?
That is the first thing displayed in the logs, then the same softlockup repeats ad-nauseum until the machine freezes, if I set it to reboot on panic/softlockup/etcetc.. the machine hangs remains hung and requires hardware reset. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
El 04/10/12 17:02, Jiri Slaby escribió:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 10/04/2012 09:12 PM, Cristian Rodríguez wrote:
are 3.5 kernels preserved somewhere.. ?
Yes and no.
Yes in the git tree and in the OBS history. You can link to the kernel:stable repo just before the update and build the kernel yourself.
No, not in binary.
BTW.. here is the crash.. is just a matter of generating a little load on apache2-event and something goes crazy.
Is there a fix known? The traces below look pretty hopeless. Are they the first info printed? What's before them?
Do You have any hints how to proceed here ? I have both compiled custom kernels and used SUSE packages plus kernel.softlockup_panic = 1 kernel.unknown_nmi_panic = 1 kernel.panic_on_unrecovered_nmi = 1 vm.panic_on_oom = 1 and kdump in order to get a workable backtrace, with no avail, machine hangs and the kernel dump is never written. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
El jue 04 oct 2012 21:01:45 CLST, Cristian Rodríguez escribió:
El 04/10/12 17:02, Jiri Slaby escribió:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 10/04/2012 09:12 PM, Cristian Rodríguez wrote:
are 3.5 kernels preserved somewhere.. ?
Yes and no.
Yes in the git tree and in the OBS history. You can link to the kernel:stable repo just before the update and build the kernel yourself.
No, not in binary.
BTW.. here is the crash.. is just a matter of generating a little load on apache2-event and something goes crazy.
Is there a fix known? The traces below look pretty hopeless. Are they the first info printed? What's before them?
Do You have any hints how to proceed here ? I have both compiled custom kernels and used SUSE packages plus
kernel.softlockup_panic = 1 kernel.unknown_nmi_panic = 1 kernel.panic_on_unrecovered_nmi = 1 vm.panic_on_oom = 1
and kdump in order to get a workable backtrace, with no avail, machine hangs and the kernel dump is never written.
With a debug kernel I get this at shutdown, but I am not sure it is related at all.
Adding netdev. (Cristian is seeing a circular locking dependence in 3.6.) On 10/05/2012 02:48 AM, Cristian Rodríguez wrote:
El jue 04 oct 2012 21:01:45 CLST, Cristian Rodríguez escribió:
El 04/10/12 17:02, Jiri Slaby escribió:
On 10/04/2012 09:12 PM, Cristian Rodríguez wrote:
BTW.. here is the crash.. is just a matter of generating a little load on apache2-event and something goes crazy.
Is there a fix known? The traces below look pretty hopeless. Are they the first info printed? What's before them?
Do You have any hints how to proceed here ? I have both compiled custom kernels and used SUSE packages plus
kernel.softlockup_panic = 1 kernel.unknown_nmi_panic = 1 kernel.panic_on_unrecovered_nmi = 1 vm.panic_on_oom = 1
and kdump in order to get a workable backtrace, with no avail, machine hangs and the kernel dump is never written.
With a debug kernel I get this at shutdown, but I am not sure it is related at all.
Uploaded here: http://www.fi.muni.cz/~xslaby/sklad/panics/lockdep1.png -- js suse labs -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
El 04/10/12 17:02, Jiri Slaby escribió:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 10/04/2012 09:12 PM, Cristian Rodríguez wrote:
are 3.5 kernels preserved somewhere.. ?
Yes and no.
Yes in the git tree and in the OBS history. You can link to the kernel:stable repo just before the update and build the kernel yourself.
No, not in binary.
BTW.. here is the crash.. is just a matter of generating a little load on apache2-event and something goes crazy.
Is there a fix known? The traces below look pretty hopeless. Are they the first info printed? What's before them?
Here is what happends when I tell the kernel to panic when softlockup happends. Ps: IRQ 57 is the ethernet card driver e1000e Model: "Intel 82574L Gigabit Network Connection"
On 10/06/2012 09:10 PM, Cristian Rodríguez wrote:
Here is what happends when I tell the kernel to panic when softlockup happends.
It waits for some lock. So it very looks like the circular lock dependency problem you hit earlier.
Ps: IRQ 57 is the ethernet card driver e1000e Model: "Intel 82574L Gigabit Network Connection"
Hmm, this one is interesting as the kernel disabled the interrupt for the card. It would be interesting to see the cause in the logs. As it happened 30 seconds before the panic triggered by the softlockup detector, you have that in logs, right? -- js suse labs -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
participants (2)
-
Cristian Rodríguez
-
Jiri Slaby