From: Peter 'p2' De Schrijver <p2@debian.org>
To: Andreas Barth <aba@not.so.argh.org>
Cc: David Daney <ddaney@caviumnetworks.com>, linux-mips@linux-mips.org
Subject: Re: movidis x16 hard lockup using 2.6.33
Date: Sat, 3 Apr 2010 18:43:12 +0300 [thread overview]
Message-ID: <20100403154312.GY2437@apfelkorn> (raw)
In-Reply-To: <20100402133224.GR27216@mails.so.argh.org>
Hi,
> * David Daney (ddaney@caviumnetworks.com) [100329 18:54]:
> > [...]
>
> I need to admit I'm sorry but I can't read enough from the log file.
> Serial console output is http://alius.ayous.org/~aba/screenlog.0
>
> This kernel is with the NMI-handler but without the "don't reboot"
> patch:
> Linux version 2.6.34-rc2-dsa-octeon (aba@gabrielli) (gcc version 4.4.3
> (Debian 4.4.3-3) ) #5 SMP Sat Mar 27 10:16:03 UTC 2010
>
> and this one has NMI-handler plus the small loop:
> Linux version 2.6.34-rc2-dsa-octeon (aba@gabrielli) (gcc version 4.4.3
> (Debian 4.4.3-3) ) #6 SMP Mon Mar 29 22:23:26 UTC 2010
>
>
> Unfortunatly it looks like we get neither the information nor don't
> reboot, but adding the NMU handler changed behaviour from "machine
> freezes" to "machine reboots".
>
http://zobel.ftbfs.de/.x/lucatelli-nmi-watchdog-output.txt
Dump of one of those hangs. Most cores seem to be stuck in wait
(0xffffffff81100b80), except for core 1 which is in octeon_irq_ciu0_ack
(octeon_irq_ciu0_ack).
Any insight welcome.
Thanks,
Peter.
next prev parent reply other threads:[~2010-04-03 15:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-26 18:41 movidis x16 hard lockup using 2.6.33 Peter 'p2' De Schrijver
2010-03-26 18:57 ` David Daney
2010-03-26 19:05 ` Peter 'p2' De Schrijver
2010-03-27 23:07 ` Andreas Barth
2010-03-29 16:54 ` David Daney
2010-03-29 22:02 ` Andreas Barth
2010-03-29 22:13 ` David Daney
2010-03-29 22:23 ` Andreas Barth
2010-04-02 13:32 ` Andreas Barth
2010-04-03 15:43 ` Peter 'p2' De Schrijver [this message]
2010-04-15 18:43 ` irqbalance on movidis crashes the machine (was: movidis x16 hard lockup using 2.6.33) Andreas Barth
2010-04-15 20:35 ` Andreas Barth
2010-04-25 13:54 ` Andreas Barth
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=20100403154312.GY2437@apfelkorn \
--to=p2@debian.org \
--cc=aba@not.so.argh.org \
--cc=ddaney@caviumnetworks.com \
--cc=linux-mips@linux-mips.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