Skip to contentSkip to conversation

Kernel 2.8.6.1 & VLAN & E100

DISCUSSION Lawrence Wong 2 participants 3 messages Sep 14, 2004 – Sep 18, 2004

lore
Share & tools
lore
#0 lore 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

#1 lore raw
Quoted 18 lines · Lawrence Wong

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.

Quoted 8 lines

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?

A patch is in the latest bk tree, at least.

Ben

Signature · 2 lines
Ben Greear <[email protected]>
Candela Technologies Inc  http://www.candelatech.com
#2 lore raw

Hi Ben,

I tried rc2-bk1 & rc2-bk3. rc2-bk1 solved the problem but rc2-bk3 crashed on startup when trying to bring up the loopback interface. The error started off with something about fib_.... but I was not able to capture it in the syslog.

I guess I'll stick to rc2-bk1 for now.

Thanks for the great help!

Quoted 32 lines · --- Ben Greear
Quoted 4 lines · Lawrence Wong

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.

Quoted 7 lines

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

Quoted 1 line

use VLAN subinterfaces. The VLAN subinterface

comes up

Quoted 2 lines

fine but the moment I send traffic in/out of the interface (i.e. ping), a huge and neverending

chunk of

Quoted 5 lines

"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

Quoted 1 line

run the system in normal non-VLAN mode, the

problem

Quoted 1 line

does not occur. So I am inclined to believe it

either

Quoted 3 lines

has something to do with the VLAN driver or VLAN driver + INTEL 10/100 driver.

Quoted 12 lines
Quoted 2 lines

Has anyone encountered before or know of any solutions?

A patch is in the latest bk tree, at least.

Ben

Signature · 2 lines
Ben Greear <[email protected]>
Candela Technologies Inc  http://www.candelatech.com

__________________________________
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail