From: Dirk Behme <dirk.behme@googlemail.com>
To: Eduardo Valentin <edubezval@gmail.com>,
linux-omap-open-source@linux.omap.com
Subject: Re: CONFIG_PREEMPT_RT patch on OSK
Date: Thu, 30 Nov 2006 20:43:43 +0100 [thread overview]
Message-ID: <456F346F.8030906@gmail.com> (raw)
In-Reply-To: <a0580c510611301012t3985c696q88834c4960acdf8f@mail.gmail.com>
Eduardo Valentin wrote:
> [ 16.829315] BUG: scheduling while atomic: IRQ 160/0x00000001/709, CPU#0
> [ 18.828186] NETDEV WATCHDOG: eth0: transmit timed out
> [ 21.828155] NETDEV WATCHDOG: eth0: transmit timed out
>
> Have you already faced this problem?
As mentioned in [1] I doubt ethernet as well. For test
purposes I boot using ramdisk instead of NFS, so I had no
network/NFS access at boot time. Then, I manually mounted
NFS from user space and played MP3 via NFS [1].
Anybody with a hint for non-experts what "BUG: scheduling
while atomic" wants to tell us? Any idea what is wrong here?
IRQ 160 is our GPIO eth0 interrupt.
Dirk
[1]
http://linux.omap.com/pipermail/linux-omap-open-source/2006-November/008490.html
prev parent reply other threads:[~2006-11-30 19:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-18 7:47 CONFIG_PREEMPT_RT patch on OSK Dirk Behme
2006-11-30 18:12 ` Eduardo Valentin
2006-11-30 19:43 ` Dirk Behme [this message]
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=456F346F.8030906@gmail.com \
--to=dirk.behme@googlemail.com \
--cc=edubezval@gmail.com \
--cc=linux-omap-open-source@linux.omap.com \
/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.