linux-kernel - Re: 2.6.20-rc6-mm2

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]

Message-ID: <Pine.LNX.4.64.0701291122570.9448@twin.jikos.cz>
Date:	Mon, 29 Jan 2007 12:02:15 +0100 (CET)
From:	Jiri Kosina <jikos@...os.cz>
To:	Andrew Morton <akpm@...l.org>
cc:	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: 2.6.20-rc6-mm2

On Mon, 29 Jan 2007, Andrew Morton wrote:

> 	http://userweb.kernel.org/~akpm/2.6.20-rc6-mm2/

I just got this on suspend/resume cycle on my IBM T42p

pcspkr pcspkr: EARLY resume
vesafb vesafb.0: EARLY resume
serial8250 serial8250: EARLY resume
i8042 i8042: EARLY resume
platform floppy.0: EARLY resume
BUG: soft lockup detected on CPU#0!
 [<c01043ae>] show_trace_log_lvl+0x1a/0x2f
 [<c0104941>] show_trace+0x12/0x14
 [<c01049c5>] dump_stack+0x16/0x18
 [<c0142053>] softlockup_tick+0x93/0xa2
 [<c011eb5b>] run_local_timers+0x12/0x14
 [<c011ed6f>] update_process_times+0x36/0x5a
 [<c012c567>] tick_periodic+0x66/0x72
 [<c012c580>] tick_handle_periodic+0xd/0x3d
 [<c0105d6a>] timer_interrupt+0xe/0x15
 [<c0142310>] handle_IRQ_event+0x1a/0x46
 [<c01435ac>] handle_level_irq+0x7c/0xc4
 [<c0105300>] do_IRQ+0x82/0x9e
 [<c0103f6e>] common_interrupt+0x2e/0x34
 [<c013a78e>] snapshot_ioctl+0x1e7/0x581
 [<c016bc1d>] do_ioctl+0x41/0x51
 [<c016be2d>] vfs_ioctl+0x200/0x217
 [<c016be8d>] sys_ioctl+0x49/0x64
 [<c0103cf8>] sysenter_past_esp+0x5d/0x99
 =======================
platform dock.0: resuming
acpi acpi_system:00: resuming
acpi button_power:00: resuming
ACPI Processor Driver processor:00: resuming

I guess that it's caused by some timer changes (added Thomas and Ingo to 
CC), which confuse the softlockup detector sense of time? 

-- 
Jiri Kosina
-
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/