public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: lkml@lazy.shacknet.nu
To: linux-kernel@vger.kernel.org
Subject: Re: [Panic] 2.6.8 and ingress scheduling
Date: Sun, 15 Aug 2004 15:06:35 +0200	[thread overview]
Message-ID: <20040815130635.GA3703@lazy.shacknet.nu> (raw)
In-Reply-To: <20040814175233.GA3617@lazy.shacknet.nu>

[-- Attachment #1: Type: text/plain, Size: 1616 bytes --]

hello again,

> the last line (filter add) in the "wondershaper" script does sth. to the
> kernel, that lets it panic on receiving network packets.

actually, the last _two_ commands set up the kernel for panic. please
see attached script; running should produce this console message:

HTB init, kernel part version 3.17
Ingress scheduler: Classifier actions prefered over netfilter

shortly then, the kernel will panic (ifconfig shows up to 500KiB RX before).

with vga selection enabled, and a long;) piece of paper, this is produced:
(omissions marked [...] - these numbers are very hard to not misread)


Unable to handle kernel NULL pointer dereference at virtual address 0000000d
 printing eip:
c02080f60
*pde = 00000000
Oops: 0000 [#1]
Modules linked in: [...]
[...]
 Call Trace:
 ip_rcv_finish
 ing_hook
 nf_iterate
 ip_rcv_finish
 ip_rcv_finish
 ing_hook_slow
 ip_rcv_finish
 ip_rcv
 ip_rcv_finish
 netif_receive
 rtl8139_rx
 rtl8139_poll
 net_rx_action
 __do_softirq
 do_IRQ
 common_interrupt
 default_idle
 cpu_idle
 start_kernel
 unknown_bootoption
Code: 8b 43 0c 39 f0 74 43 3d 00 03 00 00 74 3c 8b 1b 85 db 75 ec
 <0>Kernel panic : Fatal exception in interrupt
In interrupt handler - not syncing

eof.

another time, running iptraf, identical Oops, but first line reads:

Unable to handle kernel paging request at virtual address 000a0f0d
[...]
EIP is at ingress_enqueue+0x20/0x90
[...]

the traffic shaping of upstream packets does not panic the kernel; I
also tried a different timer source, to no success.

regards,

peter

attached: output of shaper status, output of lsmod, minimal shaper script.

[-- Attachment #2: wshaper.status.txt --]
[-- Type: text/plain, Size: 196 bytes --]

qdisc pfifo_fast 0: [Unknown qdisc, optlen=20] 
 Sent 50124 bytes 582 pkts (dropped 0, overlimits 0) 

qdisc ingress ffff: ---------------- 
 Sent 66193 bytes 575 pkts (dropped 0, overlimits 0) 


[-- Attachment #3: lsmod.txt --]
[-- Type: text/plain, Size: 1226 bytes --]

Module                  Size  Used by
snd_via82xx            23204  - 
snd_mpu401_uart         5608  - 
ehci_hcd               25260  - 
uhci_hcd               28568  - 
usbcore               100292  - 
snd_bt87x              10952  - 
tuner                  18680  - 
bttv                  145196  - 
video_buf              16844  - 
i2c_algo_bit            8720  - 
v4l2_common             4712  - 
btcx_risc               3664  - 
videodev                6720  - 
snd_ens1371            18760  - 
snd_rawmidi            19300  - 
snd_seq_device          6256  - 
snd_pcm_oss            48360  - 
snd_mixer_oss          16904  - 
snd_pcm                81704  - 
snd_page_alloc          8752  - 
snd_timer              19628  - 
snd_ac97_codec         65548  - 
snd                    43684  - 
soundcore               6560  - 
8139too                19912  - 
ohci1394               30764  - 
ieee1394               91732  - 
w83627hf               27436  - 
eeprom                  6064  - 
i2c_sensor              2152  - 
i2c_isa                 1480  - 
i2c_viapro              5780  - 
i2c_core               18328  - 
ide_cd                 37824  - 
cdrom                  36892  - 
loop                   11888  - 

[-- Attachment #4: ingress-shaper.sh --]
[-- Type: application/x-sh, Size: 377 bytes --]

  reply	other threads:[~2004-08-15 12:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-14 17:52 [OOPS] 2.6.8 and ingress scheduling lkml
2004-08-15 13:06 ` lkml [this message]
2004-08-15 16:12   ` [Panic] " Patrick McHardy
2004-08-16  2:45     ` David S. Miller

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=20040815130635.GA3703@lazy.shacknet.nu \
    --to=lkml@lazy.shacknet.nu \
    --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