[Click] Kernelmode and scheduling while atomic problem

[Torquato Bertani]

Hi Beyers,
yes, the problem occurs only using wireless devices. After some tests
I'm sure about that.
I didn't noticed it before because every config loaded after a config
with wireless report the bug.
If I load only configs without wireless everything run fine.

I'm using wireless madwifi driver and I finally discovered the
problem. It's a patch for madwifi that add napi polling support for
the driver. If I compile madwifi drivers without this patch everything
run. I can't understand why because the patch should only add napi
polling support but shouldn't enable it, probably I'm wrong. I simply
removed it, I know that click is not able to use napi polling drivers,
right?

Thanks
Thor



On 6/22/07, Beyers Cronje <bcronje at gmail.com> wrote:
> Thor,
>
> So this problem does not occur when running the attached config with
> ethernet device?
>
>
> On 6/22/07, Torquato Bertani < torquato at gmail.com> wrote:
> >
> > I can't undestand the problem, I get the error (scheduling while
> > atomic) on two different systems with different architectures, one x86
> > and one mipsel.
> >
> > Here a file with the click config and consequent errors.
> >
> > Does anyone use successfully click in linuxmodule with kernel
> > 2.6.19.2? With wireless devices?
> >
> > Thanks for any help.
> > Thor
> >
> > On 6/20/07, Torquato Bertani <torquato at gmail.com> wrote:
> > > Hi Beyers,
> > > here the grep.
> > > Thor
> > >
> > > # CONFIG_PREEMPT is not set
> > > CONFIG_PREEMPT_NONE=y
> > > # CONFIG_PREEMPT_VOLUNTARY is not set
> > >
> > >
> > > CONFIG_BCM43XX_DEBUG=y
> > > # CONFIG_CIFS_DEBUG2 is not set
> > > # CONFIG_CPU_FREQ_DEBUG is not set
> > > # CONFIG_DEBUG_BUGVERBOSE is not set
> > > # CONFIG_DEBUG_FS is not set
> > > # CONFIG_DEBUG_KERNEL is not set
> > > # CONFIG_DEVFS_DEBUG is not set
> > > # CONFIG_HWMON_DEBUG_CHIP is not set
> > > # CONFIG_I2C_DEBUG_ALGO is not set
> > > # CONFIG_I2C_DEBUG_BUS is not set
> > > # CONFIG_I2C_DEBUG_CHIP is not set
> > > # CONFIG_I2C_DEBUG_CORE is not set
> > > # CONFIG_IEEE80211_DEBUG is not set
> > > # CONFIG_IEEE80211_SOFTMAC_DEBUG is not set
> > > # CONFIG_IPW2100_DEBUG is not set
> > > # CONFIG_IPW2200_DEBUG is not set
> > > # CONFIG_IP_DCCP_CCID2_DEBUG is not set
> > > # CONFIG_IP_NF_MATCH_LAYER7_DEBUG is not set
> > > # CONFIG_JBD_DEBUG is not set
> > > CONFIG_JFFS2_FS_DEBUG=0
> > > # CONFIG_JFS_DEBUG is not set
> > > # CONFIG_MTD_DEBUG is not set
> > > # CONFIG_NETDEBUG is not set
> > > # CONFIG_NETFILTER_DEBUG is not set
> > > # CONFIG_NTFS_DEBUG is not set
> > > # CONFIG_PCMCIA_DEBUG is not set
> > > # CONFIG_PNP_DEBUG is not set
> > > # CONFIG_SCSI_DEBUG is not set
> > > # CONFIG_SND_DEBUG is not set
> > > # CONFIG_USB_DEBUG is not set
> > > # CONFIG_USB_STORAGE_DEBUG is not set
> > > # CONFIG_VIDEO_ADV_DEBUG is not set
> > > # CONFIG_ZD1211RW_DEBUG is not set
> > >
> > >
> > > On 6/20/07, Beyers Cronje <bcronje at gmail.com> wrote:
> > > > Hi Thor,
> > > >
> > > > For interest sake can you mail me output to the following:
> > > >
> > > > grep PREEMPT .config
> > > > grep DEBUG .config
> > > >
> > > > Beyers
> > > >
> > > >
> > > > On 6/20/07, Torquato Bertani <torquato at gmail.com> wrote:
> > > > >
> > > > > Hi all, I'm trying to use click in kernelmode with kernel 2.6.19.2
> but
> > > > > I always get this error: BUG: scheduling while atomic.
> > > > >
> > > > > In the mailing list I found something about a problem with
> preemptive
> > > > > kernel, I checked and in my kernel CONFIG_PREEMPT_NONE=y
> > > > >
> > > > > Anyone has any idea? Any suggestion about where I can look? I can't
> > > > > understand if it is a problem with my kernel or a problem of click.
> Or
> > > > > both.
> > > > >
> > > > > Here the simple config file, it doesn't really work, just for
> example:
> > > > > FromDevice(eth0, PROMISC true) -> Queue(100) -> ToDevice(ath0);
> > > > > FromDevice(ath0, PROMISC true) -> Queue(100) -> ToDevice(eth0);
> > > > >
> > > > > At the end a part o trace errors.
> > > > >
> > > > > Thanks
> > > > > Thor
> > > > >
> > > > > BUG: scheduling while atomic: kclick/0x00000100/716
> > > > > [<c02677df>] __sched_text_start+0x4f/0x4f1
> > > > > [<c8ab959d>]
> > > > _ZN8ToDevice12queue_packetEP6Packet+0xdd/0x170
> [click]
> > > > > [<c8ac3c20>] _ZN13FullNoteQueue4pullEi+0x0/0x130
> [click]
> > > > > [<c8ab9b89>]
> _ZN8ToDevice8run_taskEP4Task+0x289/0x3b0
> > > > [click]
> > > > > [<c8a78623>] _ZN12RouterThread6driverEv+0x2a3/0x2e0
> > > > [click]
> > > > > [<c8b1234f>] _ZN6VectorIiE7reserveEi+0x3f/0x90
> [click]
> > > > > [<c8b05bf4>]
> > > > _Z16click_init_schedP12ErrorHandler+0xd54/0xe10
> [click]
> > > > > [<c8b05b70>]
> > > > _Z16click_init_schedP12ErrorHandler+0xcd0/0xe10
> [click]
> > > > > [<c0102c17>] kernel_thread_helper+0x7/0x10
> > > > > =======================
> > > > > BUG: scheduling while atomic: kclick/0x00000100/716
> > > > > [<c02677df>] __sched_text_start+0x4f/0x4f1
> > > > > [<c8ac3c20>] _ZN13FullNoteQueue4pullEi+0x0/0x130
> [click]
> > > > > [<c8ab9b89>]
> _ZN8ToDevice8run_taskEP4Task+0x289/0x3b0
> > > > [click]
> > > > > [<c8a78623>] _ZN12RouterThread6driverEv+0x2a3/0x2e0
> > > > [click]
> > > > > [<c8b1234f>] _ZN6VectorIiE7reserveEi+0x3f/0x90
> [click]
> > > > > [<c8b05bf4>]
> > > > _Z16click_init_schedP12ErrorHandler+0xd54/0xe10
> [click]
> > > > > [<c8b05b70>]
> > > > _Z16click_init_schedP12ErrorHandler+0xcd0/0xe10
> [click]
> > > > > [<c0102c17>] kernel_thread_helper+0x7/0x10
> > > > > =======================
> > > > > _______________________________________________
> > > > > click mailing list
> > > > > click at amsterdam.lcs.mit.edu
> > > > >
> https://amsterdam.lcs.mit.edu/mailman/listinfo/click
> > > > >
> > > >
> > > >
> > >
> >
> > _______________________________________________
> > click mailing list
> > click at amsterdam.lcs.mit.edu
> > https://amsterdam.lcs.mit.edu/mailman/listinfo/click
> >
> >
> >
>
>