Re: Softlockup detected with 2.6.23-rc2-mm1

Andy Whitcroft
2007-08-10T09:21:21Z

On Fri, Aug 10, 2007 at 01:06:58PM +0530, Kamalesh Babulal wrote:
> Andrew Morton wrote:
> >On Fri, 10 Aug 2007 11:46:25 +0530 Kamalesh Babulal
> ><kamalesh@linux.vnet.ibm.com> wrote:
> >
> >
> >>I get call trace, when the file system stress is run on the
> >>2.6.23-rc2-mm1 kernel on a Dual Core AMD Opteron
> >>(processor 270)
> >>
> >>============================================\BUG: spinlock bad magic on
> >>CPU#1, fsx-linux/19721
> >>
> >
> >Yes, sorry, mm-dirty-balancing-for-tasks.patch had a bug. Those patches
> >were
> >removed from 2.6.23-rc2-mm2 - please test that instead.
> >-
> >To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> >the body of a message to majordomo@vger.kernel.org
> >More majordomo info at http://vger.kernel.org/majordomo-info.html
> >Please read the FAQ at http://www.tux.org/lkml/
> >
> I get different call trace on AMD Opteron(tm) Processor 844 machine
> , I am not sure where it is related to the same patch
>
> =====================================================
> BUG: soft lockup - CPU#3 stuck for 11s! [pdflush:272]
> CPU 3:
> Modules linked in:
> Pid: 272, comm: pdflush Not tainted 2.6.23-rc2-mm1-autokern1 #1
> RIP: 0010:[<ffffffff8021a9c3>] [<ffffffff8021a9c3>]
> flush_tlb_others+0x69/0x95

Cannot be 100% sure but of the group of machines showing your original
problem one showed this form. Dropping the patches indicated by Andrew
seemed to fix both symptoms. So I think it is highly likely the same
thing.

-apw