linux-kernel - Re: 18rc1 soft lockup

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <1152919839.8885.1.camel@localhost.localdomain>
Date:	Fri, 14 Jul 2006 16:30:38 -0700
From:	john stultz <johnstul@...ibm.com>
To:	Dave Jones <davej@...hat.com>
Cc:	Roman Zippel <zippel@...ux-m68k.org>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: 18rc1 soft lockup

On Fri, 2006-07-14 at 10:09 -0400, Dave Jones wrote:
> On Fri, Jul 14, 2006 at 11:22:47AM +0200, Roman Zippel wrote:
>  > Hi,
>  > 
>  > On Thu, 13 Jul 2006, Dave Jones wrote:
>  > 
>  > > On Thu, Jul 13, 2006 at 03:15:43PM -0700, john stultz wrote:
>  > > 
>  > >  > > Just when I thought it had gotten fixed..
>  > >  > > 2.6.18rc1-git6 this time on x86-64..
>  > >  > > 
>  > >  > > BUG: soft lockup detected on CPU#3!
>  > >  > > 
>  > >  > > Call Trace:
>  > >  > >  [<ffffffff80270865>] show_trace+0xaa/0x23d
>  > >  > >  [<ffffffff80270a0d>] dump_stack+0x15/0x17
>  > >  > >  [<ffffffff802c44e6>] softlockup_tick+0xd5/0xea
>  > >  > >  [<ffffffff80250bea>] run_local_timers+0x13/0x15
>  > >  > >  [<ffffffff8029cc1d>] update_process_times+0x4c/0x79
>  > >  > >  [<ffffffff8027bfeb>] smp_local_timer_interrupt+0x2b/0x50
>  > >  > >  [<ffffffff8027c766>] smp_apic_timer_interrupt+0x58/0x62
>  > >  > >  [<ffffffff802628ae>] apic_timer_interrupt+0x6a/0x70
>  > >  > 
>  > >  > Hmmm.. grumble. Was this on bootup, or after some time period?
>  > > 
>  > > Right at the end of boot up, between the switch from runlevel 3 to 5.
>  > 
>  > When it waits, a SysRq+T might be useful.
> 
> it doesn't wait. this scrolls by within a split second.

Huh. I wonder if the x86-64 lost-tick compensation code is being
triggered. Could you boot w/ "report_lost_ticks" and see if it spits
anything out right before this?

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