From: alexandre.belloni@piout.net (Alexandre Belloni)
To: linux-arm-kernel@lists.infradead.org
Subject: [alexandre.belloni@piout.net: AT91SAM9261-EK still broken ?]
Date: Mon, 9 Apr 2012 21:20:55 +0200 [thread overview]
Message-ID: <20120409192055.GA7092@piout.net> (raw)
Hum, I got the wrong list...
----- Forwarded message from Alexandre Belloni <alexandre.belloni@piout.net> -----
Date: Mon, 9 Apr 2012 21:10:25 +0200
From: Alexandre Belloni <alexandre.belloni@piout.net>
To: linux-arm-kernel at lists.arm.linux.org.uk
Cc: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Subject: AT91SAM9261-EK still broken ?
User-Agent: Mutt/1.5.21 (2010-09-15)
Hi Jean-Christophe,
I'm using linux 3.4-rc2 and it seems I'm running in the same issue that
was described there: https://lkml.org/lkml/2011/8/8/355
I didn't have a deep look into it but when I try to use ts_calibrate or
ts_test, the network interface is freezing. As I'm using nfs to boot, I
can't do anything anymore...
Kernel message:
# ts_calibrate
------------[ cut here ]------------
WARNING: at net/sched/sch_generic.c:256 dev_watchdog+0x258/0x278()
NETDEV WATCHDOG: eth0 (dm9000): transmit queue 0 timed out
Modules linked in:
[<c0012614>] (unwind_backtrace+0x0/0xf0) from [<c0019f98>] (warn_slowpath_common+0x4c/0x64)
[<c0019f98>] (warn_slowpath_common+0x4c/0x64) from [<c001a044>] (warn_slowpath_fmt+0x30/0x40)
[<c001a044>] (warn_slowpath_fmt+0x30/0x40) from [<c023fb70>] (dev_watchdog+0x258/0x278)
[<c023fb70>] (dev_watchdog+0x258/0x278) from [<c002370c>] (run_timer_softirq+0xf8/0x230)
[<c002370c>] (run_timer_softirq+0xf8/0x230) from [<c001f140>] (__do_softirq+0x90/0x120)
[<c001f140>] (__do_softirq+0x90/0x120) from [<c001f534>] (irq_exit+0x48/0x50)
[<c001f534>] (irq_exit+0x48/0x50) from [<c000e980>] (handle_IRQ+0x44/0x98)
[<c000e980>] (handle_IRQ+0x44/0x98) from [<c000dd78>] (__irq_svc+0x38/0x60)
[<c000dd78>] (__irq_svc+0x38/0x60) from [<c000eacc>] (default_idle+0x24/0x40)
[<c000eacc>] (default_idle+0x24/0x40) from [<c000ec90>] (cpu_idle+0x84/0xbc)
[<c000ec90>] (cpu_idle+0x84/0xbc) from [<c03e16e0>] (start_kernel+0x24c/0x290)
---[ end trace e6a4b7e1afc454c3 ]---
nfs: server 192.168.1.1 not responding, still trying
Regards,
--
Alexandre Belloni
----- End forwarded message -----
--
Alexandre Belloni
next reply other threads:[~2012-04-09 19:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-09 19:20 Alexandre Belloni [this message]
2012-04-09 20:56 ` [alexandre.belloni@piout.net: AT91SAM9261-EK still broken ?] Alexandre Belloni
2012-04-10 16:32 ` Jean-Christophe PLAGNIOL-VILLARD
2012-04-11 8:23 ` Nicolas Ferre
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=20120409192055.GA7092@piout.net \
--to=alexandre.belloni@piout.net \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.