From: Doug Kehn <rdkehn@yahoo.com>
To: linux-kernel@vger.kernel.org, uClinux <uclinux-dev@uclinux.org>
Cc: Mikael Pettersson <mikpe@it.uu.se>
Subject: Re: Soft lockup 2.6.23.14-uc0
Date: Wed, 6 Feb 2008 05:01:23 -0800 (PST) [thread overview]
Message-ID: <478718.75314.qm@web52006.mail.re2.yahoo.com> (raw)
In-Reply-To: <18344.31682.388710.182172@harpo.it.uu.se>
Hi Mikael,
--- Mikael Pettersson wrote:
>
> Is this a new ixp4xx platform or one of the existing
> ones in arch/arm/mach-ixp4xx?
>
The machine type (arch/arm/tools/mach-types) is
ct_dfs. However, the platform is a copy of the coyote
platform 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.
>
Thanks for the tips. I'll check in to these.
Regards,
...doug
____________________________________________________________________________________
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs
next prev parent reply other threads:[~2008-02-06 13: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
2008-02-06 13:01 ` Doug Kehn [this message]
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=478718.75314.qm@web52006.mail.re2.yahoo.com \
--to=rdkehn@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
--cc=uclinux-dev@uclinux.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®