LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Mikael Pettersson <mikpe@it.uu.se>
To: Doug Kehn <rdkehn@yahoo.com>
Cc: linux-kernel@vger.kernel.org, uClinux <uclinux-dev@uclinux.org>
Subject: Re: Soft lockup 2.6.23.14-uc0
Date: Tue, 5 Feb 2008 16:07:46 +0100 [thread overview]
Message-ID: <18344.31682.388710.182172@harpo.it.uu.se> (raw)
In-Reply-To: <394206.41470.qm@web52009.mail.re2.yahoo.com>
Doug Kehn writes:
> Hi All,
>
> I am observing kernel soft lockups when running
> network throughput tests with NUTTCP. The kernel is a
> stock 2.6.23 kernel with patches from uClinux.org. I
> have applied the incremental 2.6.23 patches to produce
> the resulting 2.6.23.14-uc0 kernel. This kernel is
> executing on a 266MHz Intel XScale IXP420 processor
> with 16MB flash (JFFS2) and 64MB RAM. I am also using
> the Intel Access Library v2.4 with patches from
> snapgear.org. (The Intel Access Library is the reason
> for the tainted kernel.) The toolchain to build the
> kernel and all applications is comprised of:
>
> binutils-2.16.tar.gz
> gcc-3.4.4.tar.gz
> glibc-2.3.3.tar.gz
> glibc-linuxthreads-2.3.3.tar.gz
>
> All applications are compiled against uClibc-0.9.27.
>
> A soft lockup dump is provided below. Any help in
> determining the cause of the soft lock will be
> appreciated.
>
> Regards,
> ...doug
>
>
> # BUG: soft lockup - CPU#0 stuck for 11s! [awk:2960]
>
> Pid: 2960, comm: awk
> CPU: 0 Tainted: P (2.6.23.14-uc0 #1)
> PC is at handle_IRQ_event+0x34/0x80
> LR is at handle_level_irq+0x98/0xec
> pc : [<c0058b30>] lr : [<c0059eb0>] psr:
> 40000013
> sp : c353deb0 ip : c353ded0 fp : c353decc
> r10: 4000d090 r9 : c353c000 r8 : 4000515c
> r7 : 00000012 r6 : 00000000 r5 : 00000000 r4 :
> c3f68a60
> r3 : 40000013 r2 : c025151c r1 : c3f68a60 r0 :
> 00000012
> Flags: nZcv IRQs on FIQs on Mode SVC_32 ISA ARM
> Segment user
> Control: 000039ff Table: 03500000 DAC: 00000015
> [<c0020b60>] (show_regs+0x0/0x4c) from [<c005865c>]
> (softlockup_tick+0xe8/0x114)
> r4:00001e13
> [<c0058574>] (softlockup_tick+0x0/0x114) from
> [<c00401b0>] (run_local_timers+0x1
> 8/0x1c)
Is this a new ixp4xx platform or one of the existing
ones in arch/arm/mach-ixp4xx?
Anyway, I can think of two things:
1. There was some very recent patches by Peter Zijlstra
addressing hrtimer breakage on arm and some other
archs in 2.6.24-git. If uclinux has backported some
of that stuff then it might explain this issue.
2. There is a new native Linux driver for ixp4xx
ethernet. Patches for the 2.6.23.14 kernel can
be found in the nslu2-linux group's subversion
repository. (You'll need new firmware files though.)
Replacing Intel's IXP400 drivers with this driver
should at least tell you if the lockups are
related to your use of the Intel drivers.
FWIW, I've never seen these lockups on my ixp4xx
boxes, with the Intel IXP400 drivers or with
the new native Linux drivers.
You should also Cc: the linux arm kernel mailing list,
as the issue probably is platform specific.
next prev parent reply other threads:[~2008-02-05 15:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-04 15:45 Doug Kehn
2008-02-05 15:07 ` Mikael Pettersson [this message]
2008-02-06 13:01 ` Doug Kehn
2008-02-09 13:19 ` Doug Kehn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=18344.31682.388710.182172@harpo.it.uu.se \
--to=mikpe@it.uu.se \
--cc=linux-kernel@vger.kernel.org \
--cc=rdkehn@yahoo.com \
--cc=uclinux-dev@uclinux.org \
--subject='Re: Soft lockup 2.6.23.14-uc0' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).