From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] IMQ Runtime error
Date: Mon, 26 Jan 2004 15:09:29 +0000 [thread overview]
Message-ID: <40152DA9.2030004@dsl.pipex.com> (raw)
In-Reply-To: <1075073625.40145259a53ea@mail.psnet.gov.ng>
Roy wrote:
> even if imq is quite useless right now
I thought it was OK for inbound traffic.
What sort of load/traffic do you see crashes with.
I have an old P200 as a gateway and can run bittorrents on it, with IMQ
doing outbound for locally generated traffic (not that I really need
to) and can do > a gig/day without ever crashing. I do close down at
night though, and only have 256/512 bandwidth. Is this way below what
you need to do to crash?
> this eeror is caused probably by other loaded modules for userspace queue
> nf_queue probably
> since imq uses the same function
Yea this is a pain, I would like to run a userspace for up and IMQ for down,
but can't use lib_ipq at the same time as IMQ.
It has been suggested that I can work round this, but I haven't tried yet.
Do you think it's possible?
Andy.
> ----- Original Message -----
> From: "tc" <tc@me.net.ng>
> To: <lartc@mailman.ds9a.nl>
> Sent: Monday, January 26, 2004 1:33 AM
> Subject: [LARTC] IMQ Runtime error
>
>
>
>>hi all, i have applied all patches and compiled the kernel
>>(2.4.21), iptables
>>(1.2.9) and iproute2 (2.4.7-now-ss020116) however when i run '"'modprobe
>
> imq
>
>>numdevs=1'"', the system returns - imq.o: init_module: Device or resource
>
> busy
>
>>the transcript is below -
>>
>>[root@vmlinux project]# modprobe imq numdevs=1
>>/lib/modules/2.4.21-BW/kernel/drivers/net/imq.o: init_module: Device or
>
> resource
>
>>busy
>>Hint: insmod errors can be caused by incorrect module parameters,
>
> including
>
>>invalid IO or IRQ parameters.
>> You may find more information in syslog or the output from dmesg
>>/lib/modules/2.4.21-BW/kernel/drivers/net/imq.o: insmod
>>/lib/modules/2.4.21-BW/kernel/drivers/net/imq.o failed
>>/lib/modules/2.4.21-BW/kernel/drivers/net/imq.o: insmod imq failed
>>
>>what could be wrong? thanks all,
>>bye
>>joseph
>>_______________________________________________
>>LARTC mailing list / LARTC@mailman.ds9a.nl
>>http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>>
>
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-01-26 15:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-25 23:33 [LARTC] IMQ Runtime error tc
2004-01-26 0:50 ` Roy
2004-01-26 15:09 ` Andy Furniss [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=40152DA9.2030004@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.com \
--cc=lartc@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