linux-kernel - Re: 2.6.21-rc5-mm1

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:	Wed, 28 Mar 2007 13:31:46 -0700
From:	john stultz <johnstul@...ibm.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Mariusz Koz__owski <m.kozlowski@...land.pl>,
	linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...e.hu>, Adrian Bunk <bunk@...sta.de>
Subject: Re: 2.6.21-rc5-mm1

On Wed, 2007-03-28 at 13:02 -0700, Andrew Morton wrote:
> On Wed, 28 Mar 2007 18:44:57 +0200
> Mariusz Koz__owski <m.kozlowski@...land.pl> wrote:
> > 2) This was found a couple minutes later when the system was
> >    really busy and close to oom condition.
> > 
> >  INFO: lockdep is turned off.
> >  BUG: soft lockup detected on CPU#0!
> >   [<c0104614>] show_trace_log_lvl+0x1a/0x30
> >   [<c01052c9>] show_trace+0x12/0x14
> >   [<c0105355>] dump_stack+0x16/0x18
> >   [<c01467a0>] softlockup_tick+0x81/0xa8
> >   [<c011e4dc>] run_local_timers+0x12/0x14
> >   [<c011e8dd>] update_process_times+0x2b/0x63
> >   [<c012e4be>] tick_sched_timer+0x4d/0x9e
> >   [<c012af00>] hrtimer_interrupt+0x12e/0x1a6
> >   [<c0106f56>] timer_interrupt+0xe/0x15
> >   [<c0146af3>] handle_IRQ_event+0x28/0x59
> >   [<c01480a7>] handle_level_irq+0x6e/0xe7
> >   [<c0105d3e>] do_IRQ+0x3d/0x7f
> >   [<c01041b2>] common_interrupt+0x2e/0x34
> >   [<c011afef>] do_softirq+0x4d/0x50
> >   [<c011b263>] irq_exit+0x7e/0x80
> >   [<c0105d43>] do_IRQ+0x42/0x7f
> >   [<c01041b2>] common_interrupt+0x2e/0x34
> >   [<c0178bf2>] core_sys_select+0x1c6/0x310
> >   [<c0179101>] sys_select+0x39/0x18f
> >   [<c0103f44>] sysenter_past_esp+0x5d/0x99
> >   =======================
> >  Clocksource tsc unstable (delta = 9372804176 ns)
> >  Time: acpi_pm clocksource has been installed.

Hmm.. No clue right off. Does booting w/ clocksource=acpi_pm avoid the
issue?

-john

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