Hello List! My distribution is SuSE 7.3 Prof. I''ve successfully installed the iproute2 packet. If I enter some tc-rules the machine returns no errors, but the rules do not affect the bandwidth! Does this mean that the kernel is not compiled with the necessary options? Where can I see, which options the kernel was compiled with (sorry, but I''m newbie)? I didn''t change anything, it''s a normal SuSE 7.3 distribution. If I knew that the modules are working, I could go on trying to install some rules, or could anyone be so kind and post a simple rule that is slowing down my eth0 interface? I''d just like to see if the tc-command and the kernel is working... Thanks in advance!! -- Yours sincerely, Christian Meier mailto:email2chris@gmx.net _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
* Christian Meier; <email2chris@gmx.net> on 24 Nov, 2002 wrote:>Does this mean that the kernel is not compiled with the necessary >options? Where can I see, which options the kernel was compiled with >(sorry, but I''m newbie)? I didn''t change anything, it''s a normal SuSE >7.3 distribution.If it is a default SuSE kernel everything you should be already there. Nevertheless if you want to see the config of the kernel. Note that HTB is not there zcat /proc/config.gz will show you the config options set. If you want to add things and then recompile the folowing command will make it as a kernel config file make cloneconfig You may want to have a look at http://susefaq.sf.net/sectionkernel.html -- Togan Muftuoglu Unofficial SuSE FAQ Maintainer http://dinamizm.ath.cx _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
On Sunday 24 November 2002 20:19, Christian Meier wrote:> Hello List! > > My distribution is SuSE 7.3 Prof. I''ve successfully installed the > iproute2 packet. If I enter some tc-rules the machine returns no > errors, but the rules do not affect the bandwidth!If you have no errors, you have all the support in the kernel you need.> Does this mean that the kernel is not compiled with the necessary > options? Where can I see, which options the kernel was compiled with > (sorry, but I''m newbie)? I didn''t change anything, it''s a normal SuSE > 7.3 distribution.Maybe you can find a config file in the /boot directory.> If I knew that the modules are working, I could go on trying to > install some rules, or could anyone be so kind and post a simple rule > that is slowing down my eth0 interface? I''d just like to see if the > tc-command and the kernel is working...I have some scripts on www.docm.org. You can also try to add a tvb qdisc as root qdisc. This will limit all outgoing traffic. Stef -- stef.coene@docum.org "Using Linux as bandwidth manager" http://www.docum.org/ #lartc @ irc.oftc.net _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Thanks for your fast answers, Togan and Stef! My sample configuration works now.> Note that HTB is not thereWell, then I''ll have to learn howto patch a kernel, because it''s too difficult without HTB.> zcat /proc/config.gz will show you the config options set.Thanks it works> If you want to add things and then recompile the folowing command > will make it as a kernel config file > make cloneconfigI''ll try it.> You may want to have a look at http://susefaq.sf.net/sectionkernel.htmlOk If I''ll have any further questions to htb, I''ll ask you again ;-)... -- Yours, sincerely Christian Meier mailto:email2chris@gmx.net _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Hello,
Does following oops say something ?
I post it to LARTC because I get it when playing with QoS tools.
--
ksymoops 2.4.5 on i686 2.4.18-grsec. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.18-grsec/ (default)
-m /boot/System.map-2.4.18-grsec (default)
Warning: You did not tell me where to find symbol information. I will
assume that the log matches the kernel and modules that are running
right now and I''ll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc. ksymoops -h explains the options.
CPU: 0
EIP: 0010:[<cc097c26>] Not tained
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010283
eax: 9812f7e0 ebx: cc904d28 ecx: 00000006 edx: cc904e60
esi: cc904e48 edi: cc8f5600 ebp: cc904c60 esp: c021fd84
ds: 0018 es: 0018 ss: 0018
Process (pid: 0, stackpage=c021f000)
Stack: d08768a3 cc097bc0 ffffffff 00000000 00000000 cc904c00 cc8f5600
cc8d6e00
00000040 cc904d28 cc904e48 cc8f5600 d0876c2d cc904c60 00000006
00000000
cc904c00 cfe52800 00000000 c01a994c cc904e28 cc904f68 00000001
cc904c60
Call Trace: [<d08768a3>] [<d0876c2d>] [<c01a994c>]
[<c019c693>]
[<c0196503>]
[<c01e99dd>] [<c019bec6>] [<c01a6bf0>] [<c01a9932>]
[<c01a994c>]
[<c01a6c3a>]
[<c019bec6>] [<c01a6b9b>] [<c01a6bf0>] [<c01a5f79>]
[<c01a5db8>]
[<c019bec6>]
[<c01e5c26>] [<c01a5db8>] [<c0196a9d>] [<c011554a>]
[<c0107f5d>]
[<c0105150>]
[<c0105150>] [<c010a2d8>] [<c0105150>] [<c0105150>]
[<c0105173>]
[<c01051d9>]
[<c0105000>] [<c0105027>]
Code: 00 00 00 20 8e cc 00 00 00 00 03 00 00 00 00 40 89 cc 00 00
>>EIP; cc097c26 <_end+be1ac9e/1058e078> <====
>>eax; 9812f7e0 Before first symbol
>>ebx; cc904d28 <_end+c687da0/1058e078>
>>edx; cc904e60 <_end+c687ed8/1058e078>
>>esi; cc904e48 <_end+c687ec0/1058e078>
>>edi; cc8f5600 <_end+c678678/1058e078>
>>ebp; cc904c60 <_end+c687cd8/1058e078>
>>esp; c021fd84 <init_task_union+1d84/2000>
Trace; d08768a3 <[sch_sfq]sfq_reset+17/34>
Trace; d0876c2d <[sch_sfq].text.end+4e/e1>
Trace; c01a994c <ip_finish_output2+0/d0>
Trace; c019c693 <qdisc_restart+13/d8>
Trace; c0196503 <dev_queue_xmit+f7/238>
Trace; c01e99dd <Unused_offset+1ad9/bdc0>
Trace; c019bec6 <nf_hook_slow+ee/144>
Trace; c01a6bf0 <ip_forward_finish+0/50>
Trace; c01a9932 <ip_finish_output+102/108>
Trace; c01a994c <ip_finish_output2+0/d0>
Trace; c01a6c3a <ip_forward_finish+4a/50>
Trace; c019bec6 <nf_hook_slow+ee/144>
Trace; c01a6b9b <ip_forward+1eb/240>
Trace; c01a6bf0 <ip_forward_finish+0/50>
Trace; c01a5f79 <ip_rcv_finish+1c1/1f8>
Trace; c01a5db8 <ip_rcv_finish+0/1f8>
Trace; c019bec6 <nf_hook_slow+ee/144>
Trace; c01e5c26 <_etext+5122/617c>
Trace; c01a5db8 <ip_rcv_finish+0/1f8>
Trace; c0196a9d <net_rx_action+1a5/280>
Trace; c011554a <do_softirq+5a/ac>
Trace; c0107f5d <do_IRQ+a1/b4>
Trace; c0105150 <default_idle+0/28>
Trace; c0105150 <default_idle+0/28>
Trace; c010a2d8 <call_do_IRQ+5/d>
Trace; c0105150 <default_idle+0/28>
Trace; c0105150 <default_idle+0/28>
Trace; c0105173 <default_idle+23/28>
Trace; c01051d9 <cpu_idle+41/54>
Trace; c0105000 <_stext+0/0>
Trace; c0105027 <rest_init+27/28>
Code; cc097c26 <_end+be1ac9e/1058e078>
00000000 <_EIP>:
Code; cc097c26 <_end+be1ac9e/1058e078> <==== 0: 00 00
add %al,(%eax) <====Code; cc097c28 <_end+be1aca0/1058e078>
2: 00 20 add %ah,(%eax)
Code; cc097c2a <_end+be1aca2/1058e078>
4: 8e cc mov %esp,%cs
Code; cc097c2c <_end+be1aca4/1058e078>
6: 00 00 add %al,(%eax)
Code; cc097c2e <_end+be1aca6/1058e078>
8: 00 00 add %al,(%eax)
Code; cc097c30 <_end+be1aca8/1058e078>
a: 03 00 add (%eax),%eax
Code; cc097c32 <_end+be1acaa/1058e078>
c: 00 00 add %al,(%eax)
Code; cc097c34 <_end+be1acac/1058e078>
e: 00 40 89 add %al,0xffffff89(%eax)
Code; cc097c37 <_end+be1acaf/1058e078>
11: cc int3
<0>Kernel panic: Aiee, killing interrupt handler!
1 warning issued. Results may not be reliable.
--
Regards
tw
--
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/