From: "Michael Chan" <mchan@broadcom.com>
To: "Francois Romieu" <romieu@fr.zoreil.com>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
netdev@vger.kernel.org,
"Stephen Hemminger" <shemminger@linux-foundation.org>,
lpiccilli@gelre.com.br,
"bugme-daemon@kernel-bugs.osdl.org"
<bugme-daemon@bugzilla.kernel.org>
Subject: Re: [Bugme-new] [Bug 7974] New: BUG: scheduling while atomic: swapper/0x10000100/0
Date: Fri, 09 Feb 2007 15:31:54 -0800 [thread overview]
Message-ID: <1171063915.3304.1.camel@rh4> (raw)
In-Reply-To: <20070209223520.GA27634@electric-eye.fr.zoreil.com>
On Fri, 2007-02-09 at 23:35 +0100, Francois Romieu wrote:
> Andrew Morton <akpm@linux-foundation.org> :
> >
> > cond_resched() called from softirq, amongst other problems.
>
> Seems too simple to be right. Btw calling dev_set_mac_address
> may hurt some tg3:
>
> -> tg3_set_mac_addr
> -> tg3_netif_stop (depending on the content of their sram):
> -> netif_poll_disable
> -> schedule_timeout_interruptible
>
Yes, known problem. Bonding calls dev_set_mac_address from unsleepable
context.
next prev parent reply other threads:[~2007-02-09 22:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200702091623.l19GNiUP006513@fire-2.osdl.org>
2007-02-09 21:38 ` [Bugme-new] [Bug 7974] New: BUG: scheduling while atomic: swapper/0x10000100/0 Andrew Morton
2007-02-09 22:35 ` Francois Romieu
2007-02-09 23:31 ` Michael Chan [this message]
2007-02-11 22:53 ` Herbert Xu
2007-02-13 20:29 ` Andy Gospodarek
2007-02-13 22:26 ` Jay Vosburgh
2007-02-13 22:32 ` David Miller
2007-02-13 23:08 ` Andy Gospodarek
2007-02-13 23:33 ` Jay Vosburgh
2007-02-13 23:54 ` Stephen Hemminger
2007-02-14 0:10 ` Andy Gospodarek
2007-02-14 1:31 ` Andy Gospodarek
2007-02-14 2:11 ` Jay Vosburgh
2007-02-15 21:00 ` Andy Gospodarek
2007-02-15 23:45 ` Jay Vosburgh
2007-02-19 21:21 ` Andy Gospodarek
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=1171063915.3304.1.camel@rh4 \
--to=mchan@broadcom.com \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=lpiccilli@gelre.com.br \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
--cc=shemminger@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).