All of lore.kernel.org
 help / color / mirror / Atom feed
From: Niccolo Rigacci <niccolo@rigacci.org>
To: linux-kernel@vger.kernel.org
Cc: iiitac@pyr.swan.ac.uk, rzsfl@rz.uni-sb.de
Subject: PROBLEM: kernel BUG at net/core/skbuff.c:1341!
Date: Thu, 27 Sep 2007 11:33:46 +0200	[thread overview]
Message-ID: <20070927093346.GA29101@rigacci.org> (raw)

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

1. kernel BUG at net/core/skbuff.c:1341!

2. I got a kernel panic, the hardware is a good IBM 206m server 
with 2 Gb ECC memory, Memtest86+ run several times without 
problem. The message on the console is quite explicit, so is this 
really a kernel bug?

The box is a web server with moderate network activity. The panic 
occurred at 2007-09-26 13:15:54, during standard load
(here the MRTG graphs: http://paros.rigacci.org/mrtg/).

3. Kernel is 2.6.21, from Debian Testing linux-image package

4. Linux version 2.6.21-2-686 (Debian 2.6.21-6) 
(waldi@debian.org) (gcc version 4.1.3 20070629 (prerelease) 
(Debian 4.1.2-13)) #1 SMP Wed Jul 11 03:53:02 UTC 2007

5. No problem for several month with kernel 2.6.17

6. Here it is the transcription of the console screen. An image 
of the actual screenshot is here: 
http://www.rigacci.org/wiki/lib/exe/fetch.php/doc/appunti/linux/sa/kernel_panic_2007-09-26.jpg?cache=cache


Shorewall:net2all:DROP:IN=eth1 OUT= MAC=00:0a:cd:10:bc:24:00:50:7f:1f:45:d9:08:00
SRC=217.58.146.18 DST=88.57.16.26 LEN=88 TOS=0x00 PREC=0x00 TTL=60 ID=0 DF
PROTO=UDP SPT=5004 DPT=1194 LEN=68
Shorewall:net2all:DROP:IN=eth1 OUT= MAC=00:0a:cd:10:bc:24:00:50:7f:1f:45:d9:08:00
SRC=217.58.146.18 DST=88.57.16.26 LEN=88 TOS=0x00 PREC=0x00 TTL=60 ID=0 DF
PROTO=UDP SPT=5004 DPT=1194 LEN=68
audit(1190732795.310:2): dev=eth1 prom=256 old_prom=0 auid=4294967295
audit(1190732797.310:3): dev=eth1 prom=0 old_prom=256 auid=4294967295
------------[ cut here ]------------
kernel BUG at net/core/skbuff.c:1341!
invalid opcode: 0000 [#1]
SMP
Modules linked in: usblp sha256 cbc blkcipher nfsd exportfs lockd nfs_acl sunrpc
ppdev lp parport tun sch_sfq act_police cls_u32 sch_ingress sch_htb ip6table_filter
iptable_raw xt_comment xt_policy xt_multiport ipt_ULOG ipt_TTL ipt_ttl ipt_TOS
ipt_tos ipt_SAME ipt_REJECT ipt_REDIRECT ipt_recent ipt_owner ipt_NETMAP ipt_MASQUERADE
ipt_LOG ipt_iprange ipt_ECN ipt_ecn ipt_CLUSTERIP ipt_ah ipt_addrtype
nf_nat_tftp nf_nat_snmp_basic nf_nat_sip nf_nat_pptp nf_nat_proto_gre nf_nat_irc
nf_nat_h323 nf_nat_ftp nf_nat_amanda ts_kmp nf_conntrack_amanda nf_conntrack_tftp
nf_conntrack_sip nf_conntrack_proto_sctp nf_conntrack_pptp nf_conntrack_proto_gre
nf_conntrack_netlink nf_conntrack_netbios_ns nf_conntrack_irc nf_conntrack_h323
nf_conntrack_ftp xt_tcpmss xt_pkttype xt_physdev xt_NFQUEUE xt_NFLOG xt_MARK
xt_mark xt_mac xt_limit xt_length xt_helper xt_hashlimit ip6_tables xt_dccp
xt_conntrack xt_CONNMARK xt_connmark xt_CLASSIFY xt_tcpudp xt_state iptable_nat
nf_nat nf_conntrack_ipv4 nf_conntrack iptable_mangle nfnetlink iptable_filter
ip_tables x_tables ipv6 dm_snapshot dm_mirror twofish twofish_common dm_crypt
dm_mod tcp_diag inet_diag ipmi_si ipmi_devintf ipmi_msghandler evdev serio_raw
i2c_i801 i2c_core iTCO_wdt rtc pcspkr ext3 jbd mbcache raid1 md_mod ide_generic
sd_mod ide_cd cdrom ata_piix ata_generic libata scsi_mod piix ehci_hcd generic
uhci_hcd 8139too mii ide_core tg3 usbcore thermal processor fan
CPU:    1
EIP:    0060:[<c023df85>]    Not tainted VLI
EFLAGS: 00010206   (2.6.21-2-686 #1)
EIP is at skb_copy_and_csum_bits+0x2b6/0x300
eax: 00000002   ebx: fffad000   ecx: c0004eb4   edx: cfeb1120
esi: 00000000   edi: 0000000c   ebp: 000005c0   esp: c2103e30
ds: 007b   es: 007b   fs: 00d8  gs: 0000  ss: 0068
Process swapper (pid: 0, ti=c2102000 task=dfa07540 task.ti=c2102000)
Stack: fffad000 f78c26b7 00000509 00000000 00000000 00000000 00000020 f78c2bc0
       d4447eb0 000005c0 00000002 0000059e 000005c0 00000008 00000509 00000022
       00000000 f78c2622 d4447eb0 c023ecdd 000005aa 944099dd f78c2600 d4447eb0
Call Trace:
 [<c023ecdd>] skb_copy_and_csum_dev+0x75/0xac
 [<f8852d05>] rtl8139_start_xmit+0x5f/0x109 [8139too]
 [<c024291e>] dev_hard_start_xmit+0x1be/0x21d
 [<c02514b2>] __qdisc_run+oxe1/0x196
 [<c0243abc>] net_tx_action+0xcf/0xf4
 [<c0126102>] __do_softirq+0x66/0xcc
 [<c01261ab>] do_softirq+0x43/0x51
 [<c012640f>] irq_exit+0x38/0x6b
 [<c0114bc2>] smp_apic_timer_interrupt+0x71/0x7d
 [<c010481c>] apic_timer_interrupt+0x28/0x30
 [<c0102241>] mwait_idle_with_hints+0x3b/0x3f
 [<c01023b5>] cpu_idle+0xb5/0xd6
 =======================
Code: c0 0f b6 c0 01 c2 29 df 89 54 24 54 74 5b 01 5c 24 1c 01 dd 01 5c 24 2c 8b
 36 8b 44 24 34 89 44 24 24 e9 46 ff ff ff 85 ff 74 3e <0f> 0b eb fe 8b 54 24 54
 8b 44 24 1c c7 44 24 14 00 00 00 00 c7
EIP: [<c023df85>] skb_copy_and_csum_bits+0x2b6/0x300 SS:ESP 0068:c2103e30
Kernel panic - not syncing: Fatal exception in interrupt

8. Environment: see the attached gzipped files.

Thanks, and let me know if more info or testing is needed.

-- 
Niccolo Rigacci
Firenze - Italy

[-- Attachment #2: lspci_vvv.gz --]
[-- Type: application/octet-stream, Size: 2340 bytes --]

[-- Attachment #3: proc_cpuinfo.gz --]
[-- Type: application/octet-stream, Size: 412 bytes --]

[-- Attachment #4: proc_iomem.gz --]
[-- Type: application/octet-stream, Size: 417 bytes --]

[-- Attachment #5: proc_ioports.gz --]
[-- Type: application/octet-stream, Size: 515 bytes --]

[-- Attachment #6: proc_modules.gz --]
[-- Type: application/octet-stream, Size: 2096 bytes --]

[-- Attachment #7: proc_scsi_scsi.gz --]
[-- Type: application/octet-stream, Size: 177 bytes --]

[-- Attachment #8: ver_linux.gz --]
[-- Type: application/octet-stream, Size: 1034 bytes --]

                 reply	other threads:[~2007-09-27 10:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20070927093346.GA29101@rigacci.org \
    --to=niccolo@rigacci.org \
    --cc=iiitac@pyr.swan.ac.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rzsfl@rz.uni-sb.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.