From: Lawrence Wong <lawrencewong72@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: Kernel 2.8.6.1 & VLAN & E100
Date: Tue, 14 Sep 2004 07:33:39 -0700 (PDT) [thread overview]
Message-ID: <20040914143339.30588.qmail@web53501.mail.yahoo.com> (raw)
Hi everyone,
I am currently using Fedora Core 2 on a P3 w/512MB
RAM, 2 x 18.2GB SCSI in RAID1 via an IBM ServeRAID-4M.
Network card is an Intel 100 S controller.
All except the kernel is stock FC2. The kernel is
2.6.8.1 and compiled from the tarball found on
ftp.kernel.org .
Everything works fine until I tried to enable VLAN and
use VLAN subinterfaces. The VLAN subinterface comes up
fine but the moment I send traffic in/out of the
interface (i.e. ping), a huge and neverending chunk of
"bad scheduling while atomic" errors pop up
immediately and does not go away until I press
CTRL+ALT+DEL.
An extract of the error can be found below. But when I
run the system in normal non-VLAN mode, the problem
does not occur. So I am inclined to believe it either
has something to do with the VLAN driver or VLAN
driver + INTEL 10/100 driver.
Has anyone encountered before or know of any
solutions?
Please reply to me off-list as I am not subscribed to
the mailing list.
TIA!
Sep 14 19:16:17 testserver kernel: bad: scheduling
while atomic!
Sep 14 19:16:17 testserver kernel: [<c02e72e9>]
schedule+0x499/0x4a0
Sep 14 19:16:17 testserver kernel: [<c0104898>]
common_interrupt+0x18/0x20
Sep 14 19:16:17 testserver kernel: [<c010206b>]
cpu_idle+0x3b/0x40
Sep 14 19:16:17 testserver kernel: [<c03be73d>]
start_kernel+0x14d/0x170
Sep 14 19:16:17 testserver kernel: [<c03be370>]
unknown_bootoption+0x0/0x160
Sep 14 19:16:17 testserver kernel: bad: scheduling
while atomic!
Sep 14 19:16:17 testserver kernel: [<c02e72e9>]
schedule+0x499/0x4a0
Sep 14 19:16:17 testserver kernel: [<c0104898>]
common_interrupt+0x18/0x20
Sep 14 19:16:17 testserver kernel: [<c010206b>]
cpu_idle+0x3b/0x40
Sep 14 19:16:17 testserver kernel: [<c03be73d>]
start_kernel+0x14d/0x170
Sep 14 19:16:17 testserver kernel: [<c03be370>]
unknown_bootoption+0x0/0x160
Sep 14 19:16:17 testserver kernel: bad: scheduling
while atomic!
Sep 14 19:16:17 testserver kernel: [<c02e72e9>]
schedule+0x499/0x4a0
Sep 14 19:16:17 testserver kernel: [<c0104898>]
common_interrupt+0x18/0x20
Sep 14 19:16:17 testserver kernel: [<c010206b>]
cpu_idle+0x3b/0x40
Sep 14 19:16:17 testserver kernel: [<c03be73d>]
start_kernel+0x14d/0x170
Sep 14 19:16:17 testserver kernel: [<c03be370>]
unknown_bootoption+0x0/0x160
Sep 14 19:16:17 testserver kernel: bad: scheduling
while atomic!
Sep 14 19:16:18 testserver kernel: [<c02e72e9>]
schedule+0x499/0x4a0
Sep 14 19:16:18 testserver kernel: [<c0104898>]
common_interrupt+0x18/0x20
Sep 14 19:16:18 testserver kernel: [<c010206b>]
cpu_idle+0x3b/0x40
Sep 14 19:16:18 testserver kernel: [<c03be73d>]
start_kernel+0x14d/0x170
Sep 14 19:16:18 testserver kernel: [<c03be370>]
unknown_bootoption+0x0/0x160
Sep 14 19:16:18 testserver kernel: bad: scheduling
while atomic!
Sep 14 19:16:18 testserver kernel: [<c02e72e9>]
schedule+0x499/0x4a0
Sep 14 19:16:18 testserver kernel: [<c0104898>]
common_interrupt+0x18/0x20
Sep 14 19:16:18 testserver kernel: [<c010206b>]
cpu_idle+0x3b/0x40
Sep 14 19:16:18 testserver kernel: [<c03be73d>]
start_kernel+0x14d/0x170
Sep 14 19:16:18 testserver kernel: [<c03be370>]
unknown_bootoption+0x0/0x160
Sep 14 19:16:18 testserver kernel: bad: scheduling
while atomic!
Sep 14 19:16:18 testserver kernel: [<c02e72e9>]
schedule+0x499/0x4a0
Sep 14 19:16:19 testserver kernel: [<c0104898>]
common_interrupt+0x18/0x20
Sep 14 19:16:19 testserver kernel: [<c010206b>]
cpu_idle+0x3b/0x40
Sep 14 19:16:19 testserver kernel: [<c03be73d>]
start_kernel+0x14d/0x170
Sep 14 19:16:19 testserver kernel: [<c03be370>]
unknown_bootoption+0x0/0x160
Sep 14 19:16:19 testserver kernel: bad: scheduling
while atomic!
Sep 14 19:16:19 testserver kernel: [<c02e72e9>]
schedule+0x499/0x4a0
Sep 14 19:16:19 testserver kernel: [<c0104898>]
common_interrupt+0x18/0x20
Sep 14 19:16:19 testserver kernel: [<c010206b>]
cpu_idle+0x3b/0x40
Sep 14 19:16:19 testserver kernel: [<c03be73d>]
start_kernel+0x14d/0x170
Sep 14 19:16:19 testserver kernel: [<c03be370>]
unknown_bootoption+0x0/0x160
Sep 14 19:16:20 testserver kernel: bad: scheduling
while atomic!
Sep 14 19:16:20 testserver kernel: [<c02e72e9>]
schedule+0x499/0x4a0
Sep 14 19:16:20 testserver kernel: [<c0104898>]
common_interrupt+0x18/0x20
Sep 14 19:16:20 testserver kernel: [<c010206b>]
cpu_idle+0x3b/0x40
Sep 14 19:16:20 testserver kernel: [<c03be73d>]
start_kernel+0x14d/0x170
Sep 14 19:16:20 testserver kernel: [<c03be370>]
unknown_bootoption+0x0/0x160
Sep 14 19:16:20 testserver kernel: bad: scheduling
while atomic!
Sep 14 19:16:20 testserver kernel: [<c02e72e9>]
schedule+0x499/0x4a0
Sep 14 19:16:20 testserver kernel: [<c0104898>]
common_interrupt+0x18/0x20
Sep 14 19:16:20 testserver kernel: [<c010206b>]
cpu_idle+0x3b/0x40
Sep 14 19:16:20 testserver kernel: [<c03be73d>]
start_kernel+0x14d/0x170
Sep 14 19:16:20 testserver kernel: [<c03be370>]
unknown_bootoption+0x0/0x160
Sep 14 19:16:20 testserver kernel: bad: scheduling
while atomic!
Sep 14 19:16:21 testserver kernel: [<c02e72e9>]
schedule+0x499/0x4a0
Sep 14 19:16:21 testserver kernel: [<c0104898>]
common_interrupt+0x18/0x20
Sep 14 19:16:21 testserver kernel: [<c010206b>]
cpu_idle+0x3b/0x40
Sep 14 19:16:21 testserver kernel: [<c03be73d>]
start_kernel+0x14d/0x170
Sep 14 19:16:21 testserver kernel: [<c03be370>]
unknown_bootoption+0x0/0x160
Sep 14 19:16:21 testserver kernel: bad: scheduling
while atomic!
Sep 14 19:16:21 testserver kernel: [<c02e72e9>]
schedule+0x499/0x4a0
Sep 14 19:16:21 testserver kernel: [<c0104898>]
common_interrupt+0x18/0x20
Sep 14 19:16:21 testserver kernel: [<c010206b>]
cpu_idle+0x3b/0x40
Sep 14 19:16:21 testserver kernel: [<c03be73d>]
start_kernel+0x14d/0x170
Sep 14 19:16:21 testserver kernel: [<c03be370>]
unknown_bootoption+0x0/0x160
Sep 14 19:16:17 testserver kernel: bad: scheduling
while atomic!
Sep 14 19:16:17 testserver kernel: [<c02e72e9>]
schedule+0x499/0x4a0
Sep 14 19:16:17 testserver kernel: [<c0104898>]
common_interrupt+0x18/0x20
Sep 14 19:16:17 testserver kernel: [<c010206b>]
cpu_idle+0x3b/0x40
Sep 14 19:16:17 testserver kernel: [<c03be73d>]
start_kernel+0x14d/0x170
Sep 14 19:16:17 testserver kernel: [<c03be370>]
unknown_bootoption+0x0/0x160
Sep 14 19:16:17 testserver kernel: bad: scheduling
while atomic!
Sep 14 19:16:17 testserver kernel: [<c02e72e9>]
schedule+0x499/0x4a0
Sep 14 19:16:17 testserver kernel: [<c0104898>]
common_interrupt+0x18/0x20
Sep 14 19:16:17 testserver kernel: [<c010206b>]
cpu_idle+0x3b/0x40
Sep 14 19:16:17 testserver kernel: [<c03be73d>]
start_kernel+0x14d/0x170
Sep 14 19:16:17 testserver kernel: [<c03be370>]
unknown_bootoption+0x0/0x160
Sep 14 19:16:17 testserver kernel: bad: scheduling
while atomic!
Sep 14 19:16:17 testserver kernel: [<c02e72e9>]
schedule+0x499/0x4a0
Sep 14 19:16:17 testserver kernel: [<c0104898>]
common_interrupt+0x18/0x20
Sep 14 19:16:17 testserver kernel: [<c010206b>]
cpu_idle+0x3b/0x40
Sep 14 19:16:17 testserver kernel: [<c03be73d>]
start_kernel+0x14d/0x170
Sep 14 19:16:17 testserver kernel: [<c03be370>]
unknown_bootoption+0x0/0x160
Sep 14 19:16:17 testserver kernel: bad: scheduling
while atomic!
Sep 14 19:16:18 testserver kernel: [<c02e72e9>]
schedule+0x499/0x4a0
Sep 14 19:16:18 testserver kernel: [<c0104898>]
common_interrupt+0x18/0x20
Sep 14 19:16:18 testserver kernel: [<c010206b>]
cpu_idle+0x3b/0x40
Sep 14 19:16:18 testserver kernel: [<c03be73d>]
start_kernel+0x14d/0x170
Sep 14 19:16:18 testserver kernel: [<c03be370>]
unknown_bootoption+0x0/0x160
Sep 14 19:16:18 testserver kernel: bad: scheduling
while atomic!
Sep 14 19:16:18 testserver kernel: [<c02e72e9>]
schedule+0x499/0x4a0
Sep 14 19:16:18 testserver kernel: [<c0104898>]
common_interrupt+0x18/0x20
Sep 14 19:16:18 testserver kernel: [<c010206b>]
cpu_idle+0x3b/0x40
Sep 14 19:16:18 testserver kernel: [<c03be73d>]
start_kernel+0x14d/0x170
Sep 14 19:16:18 testserver kernel: [<c03be370>]
unknown_bootoption+0x0/0x160
Sep 14 19:16:18 testserver kernel: bad: scheduling
while atomic!
Sep 14 19:16:18 testserver kernel: [<c02e72e9>]
schedule+0x499/0x4a0
Sep 14 19:16:19 testserver kernel: [<c0104898>]
common_interrupt+0x18/0x20
Sep 14 19:16:19 testserver kernel: [<c010206b>]
cpu_idle+0x3b/0x40
Sep 14 19:16:19 testserver kernel: [<c03be73d>]
start_kernel+0x14d/0x170
Sep 14 19:16:19 testserver kernel: [<c03be370>]
unknown_bootoption+0x0/0x160
Sep 14 19:16:19 testserver kernel: bad: scheduling
while atomic!
Sep 14 19:16:19 testserver kernel: [<c02e72e9>]
schedule+0x499/0x4a0
Sep 14 19:16:19 testserver kernel: [<c0104898>]
common_interrupt+0x18/0x20
Sep 14 19:16:19 testserver kernel: [<c010206b>]
cpu_idle+0x3b/0x40
Sep 14 19:16:19 testserver kernel: [<c03be73d>]
start_kernel+0x14d/0x170
Sep 14 19:16:19 testserver kernel: [<c03be370>]
unknown_bootoption+0x0/0x160
Sep 14 19:16:20 testserver kernel: bad: scheduling
while atomic!
Sep 14 19:16:20 testserver kernel: [<c02e72e9>]
schedule+0x499/0x4a0
Sep 14 19:16:20 testserver kernel: [<c0104898>]
common_interrupt+0x18/0x20
Sep 14 19:16:20 testserver kernel: [<c010206b>]
cpu_idle+0x3b/0x40
Sep 14 19:16:20 testserver kernel: [<c03be73d>]
start_kernel+0x14d/0x170
Sep 14 19:16:20 testserver kernel: [<c03be370>]
unknown_bootoption+0x0/0x160
Sep 14 19:16:20 testserver kernel: bad: scheduling
while atomic!
Sep 14 19:16:20 testserver kernel: [<c02e72e9>]
schedule+0x499/0x4a0
Sep 14 19:16:20 testserver kernel: [<c0104898>]
common_interrupt+0x18/0x20
Sep 14 19:16:20 testserver kernel: [<c010206b>]
cpu_idle+0x3b/0x40
Sep 14 19:16:20 testserver kernel: [<c03be73d>]
start_kernel+0x14d/0x170
Sep 14 19:16:20 testserver kernel: [<c03be370>]
unknown_bootoption+0x0/0x160
Sep 14 19:16:20 testserver kernel: bad: scheduling
while atomic!
Sep 14 19:16:21 testserver kernel: [<c02e72e9>]
schedule+0x499/0x4a0
Sep 14 19:16:21 testserver kernel: [<c0104898>]
common_interrupt+0x18/0x20
Sep 14 19:16:21 testserver kernel: [<c010206b>]
cpu_idle+0x3b/0x40
Sep 14 19:16:21 testserver kernel: [<c03be73d>]
start_kernel+0x14d/0x170
Sep 14 19:16:21 testserver kernel: [<c03be370>]
unknown_bootoption+0x0/0x160
Sep 14 19:16:21 testserver kernel: bad: scheduling
while atomic!
Sep 14 19:16:21 testserver kernel: [<c02e72e9>]
schedule+0x499/0x4a0
Sep 14 19:16:21 testserver kernel: [<c0104898>]
common_interrupt+0x18/0x20
Sep 14 19:16:21 testserver kernel: [<c010206b>]
cpu_idle+0x3b/0x40
Sep 14 19:16:21 testserver kernel: [<c03be73d>]
start_kernel+0x14d/0x170
Sep 14 19:16:21 testserver kernel: [<c03be370>]
unknown_bootoption+0x0/0x160
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com
next reply other threads:[~2004-09-14 14:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-14 14:33 Lawrence Wong [this message]
2004-09-15 0:21 ` Ben Greear
2004-09-18 14:33 ` Lawrence Wong
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=20040914143339.30588.qmail@web53501.mail.yahoo.com \
--to=lawrencewong72@yahoo.com \
--cc=linux-kernel@vger.kernel.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®