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-next>] [day] [month] [year] [list]
Message-ID: <4A6F67E3.60201@howardsilvan.com>
Date:	Tue, 28 Jul 2009 14:04:35 -0700
From:	Lee Howard <faxguy@...ardsilvan.com>
To:	linux-kernel@...r.kernel.org
Subject: [Fwd: how to debug: BUG: soft lockup - CPU#3 stuck for 61s!]

I installed Fedora 11 and I'm getting the same thing there, too (kernel
2.6.29.6-213.fc11.x86_64).

What can I do to help fix this?

Jul 28 03:44:08 fangorn kernel: BUG: soft lockup - CPU#2 stuck for 61s!
[md2_raid1:107]
Jul 28 03:44:08 fangorn kernel: Modules linked in: ipv6 cpufreq_ondemand
powernow_k8 freq_table dm_multipath i2c_nforce2 forcedeth i2c_core
pata_amd pcspkr serio_raw ata_generic pata_acpi sata_nv raid1 [last
unloaded: scsi_wait_scan]
Jul 28 03:44:08 fangorn kernel: CPU 2:
Jul 28 03:44:08 fangorn kernel: Modules linked in: ipv6 cpufreq_ondemand
powernow_k8 freq_table dm_multipath i2c_nforce2 forcedeth i2c_core
pata_amd pcspkr serio_raw ata_generic pata_acpi sata_nv raid1 [last
unloaded: scsi_wait_scan]
Jul 28 03:44:08 fangorn kernel: Pid: 107, comm: md2_raid1 Not tainted
2.6.29.6-213.fc11.x86_64 #1 empty
Jul 28 03:44:08 fangorn kernel: RIP: 0010:[<ffffffff811b72dd>]
[<ffffffff811b72dd>] memcmp+0xc/0x22
Jul 28 03:44:08 fangorn kernel: RSP: 0018:ffff8801253c7d80  EFLAGS: 00000206
Jul 28 03:44:08 fangorn kernel: RAX: 0000000000000000 RBX:
ffff8801253c7d80 RCX: 0000000000000000
Jul 28 03:44:08 fangorn kernel: RDX: 0000000000000fc0 RSI:
ffff8801071b6040 RDI: ffff8801041b9040
Jul 28 03:44:08 fangorn kernel: RBP: ffffffff8101211e R08:
ffff880123867c38 R09: 0000000000000003
Jul 28 03:44:08 fangorn kernel: R10: ffff880107184780 R11:
ffff880125133180 R12: ffffffff811b3a58
Jul 28 03:44:08 fangorn kernel: R13: ffff8800a68c7000 R14:
ffff8801253c6000 R15: 0000000000000001
Jul 28 03:44:08 fangorn kernel: FS:  00007f39c0fbc6f0(0000)
GS:ffff880126a74580(0000) knlGS:0000000000000000
Jul 28 03:44:08 fangorn kernel: CS:  0010 DS: 0018 ES: 0018 CR0:
000000008005003b
Jul 28 03:44:08 fangorn kernel: CR2: 0000003644c03088 CR3:
00000001218f4000 CR4: 00000000000006e0
Jul 28 03:44:08 fangorn kernel: DR0: 0000000000000000 DR1:
0000000000000000 DR2: 0000000000000000
Jul 28 03:44:08 fangorn kernel: DR3: 0000000000000000 DR6:
00000000ffff0ff0 DR7: 0000000000000400
Jul 28 03:44:08 fangorn kernel: Call Trace:
Jul 28 03:44:08 fangorn kernel: [<ffffffffa0001c16>] ?
raid1d+0x2d8/0xe59 [raid1]
Jul 28 03:44:08 fangorn kernel: [<ffffffff81011f67>] ? restore_args+0x0/0x30
Jul 28 03:44:08 fangorn kernel: [<ffffffff813aa59a>] ?
schedule_timeout+0x27/0xb5
Jul 28 03:44:08 fangorn kernel: [<ffffffff81029f7f>] ?
default_spin_lock_flags+0x9/0xe
Jul 28 03:44:08 fangorn kernel: [<ffffffff812d65ae>] ? md_thread+0xf1/0x10f
Jul 28 03:44:08 fangorn kernel: [<ffffffff8105c8d7>] ?
autoremove_wake_function+0x0/0x39
Jul 28 03:44:08 fangorn kernel: [<ffffffff812d64bd>] ? md_thread+0x0/0x10f
Jul 28 03:44:08 fangorn kernel: [<ffffffff8105c541>] ? kthread+0x4d/0x78
Jul 28 03:44:08 fangorn kernel: [<ffffffff8101264a>] ? child_rip+0xa/0x20
Jul 28 03:44:08 fangorn kernel: [<ffffffff81011f67>] ? restore_args+0x0/0x30
Jul 28 03:44:08 fangorn kernel: [<ffffffff8105c4f4>] ? kthread+0x0/0x78
Jul 28 03:44:08 fangorn kernel: [<ffffffff81012640>] ? child_rip+0x0/0x20

-------- Original Message --------
Subject: 	how to debug: BUG: soft lockup - CPU#3 stuck for 61s!
Date: 	Sat, 25 Jul 2009 18:11:52 -0700
From: 	Lee Howard <faxguy@...ardsilvan.com>
To: 	linux-kernel@...r.kernel.org



Anywhere from once every two weeks to two times daily I have to
power-cycle a system due to a CPU getting this "soft lockup".  It
happens both with and without "noapic".

Please see the attached syslog information that appears when it occurs.

How do I debug, and how can I assist whoever is able to fix this?

(I'm not subscribed to the list, so please CC me on replies.)

Thanks,

Lee.





View attachment "softlockup.txt" of type "text/plain" (3664 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ