public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Brad Laue <brad@brad-x.com>
To: Marc Giger <gigerstyle@gmx.ch>
Cc: jt@hpl.hp.com, linux-kernel@vger.kernel.org, stewart@snerk.org
Subject: Re: Cisco Aironet 340 oops with 2.4.20
Date: Fri, 28 Feb 2003 16:46:08 -0500	[thread overview]
Message-ID: <3E5FD8A0.7070601@brad-x.com> (raw)
In-Reply-To: <20030210125342.4462c25b.gigerstyle@gmx.ch>

I'm reporting mine as well. Using the kernel PCMCIA and airo.o module. 
This occurred after 90 minutes of use, where the card was streaming 
under a megabit of traffic at all times. Lost control of everything but 
video and the USB bus.

Cisco AiroNet 350 card.

Linux Odyssey.brad-x.com 2.4.20 #10 Fri Feb 28 10:57:59 EST 2003 i686

Feb 28 11:01:15 Odyssey kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Feb 28 11:01:15 Odyssey kernel: ac97_codec: AC97 Audio codec, id: 
\203\204v9(SigmaTel STAC9721/23)
Feb 28 14:59:22 Odyssey kernel: cs: memory probe 0xa0000000-0xa0ffffff: 
clean.
Feb 28 16:16:08 Odyssey kernel: Warning: kfree_skb passed an skb still 
on a list (from c01201ba).
Feb 28 16:16:08 Odyssey kernel: kernel BUG at skbuff.c:315!
Feb 28 16:16:08 Odyssey kernel: invalid operand: 0000
Feb 28 16:16:08 Odyssey kernel: CPU:    0
Feb 28 16:16:08 Odyssey kernel: EIP:    0010:[start_request+164/528]    
Tainted: P
Feb 28 16:16:08 Odyssey kernel: EIP:    0010:[<c01dca24>]    Tainted: P
Using defaults from ksymoops -t elf32-i386 -a i386
Feb 28 16:16:08 Odyssey kernel: EFLAGS: 00010286
Feb 28 16:16:08 Odyssey kernel: eax: 00000045   ebx: c8c504a0   ecx: 
cec36000
edx: cec37f7c
Feb 28 16:16:08 Odyssey kernel: esi: c12f1f84   edi: 00000000   ebp: 
c12f0000
esp: c12f1f6c
Feb 28 16:16:08 Odyssey kernel: ds: 0018   es: 0018   ss: 0018
Feb 28 16:16:08 Odyssey kernel: Process keventd (pid: 2, stackpage=c12f1000)
Feb 28 16:16:08 Odyssey kernel: Stack: c0244620 c01201ba 00000000 
c12f1f84 c01201ba c8c504a0 ca2dc2e4 ca2dc2e4
Feb 28 16:16:08 Odyssey kernel:        00000000 00000000 c0128df3 
c0256d70 c12f1fb0 00000000 c12f0560 c12f0570
Feb 28 16:16:08 Odyssey kernel:        c12f0000 00000001 00000000 
c0253fa0 00010000 00000000 00000700 c0128cc0
Feb 28 16:16:08 Odyssey kernel: Call Trace:    
[sys_old_getrlimit+42/224] [sys_old_getrlimit+42/224] 
[vmalloc_area_pages+243/368] [vmfree_area_pages+320/384] [rest_init+0/40]
Feb 28 16:16:08 Odyssey kernel: Call Trace:    [<c01201ba>] [<c01201ba>] 
[<c0128df3>] [<c0128cc0>] [<c0105000>]
Feb 28 16:16:08 Odyssey kernel:   [<c01057ce>] [<c0128cc0>]
Feb 28 16:16:08 Odyssey kernel: Code: 0f 0b 3b 01 b1 38 24 c0 8b 5c 24 
14 e9 0e
ff ff ff 8d 74 26
 
 
 >>EIP; c01dca24 <__kfree_skb+f4/110>   <=====
 
 >>ebx; c8c504a0 <___strtok+897dc6c/1062382c>
 >>ecx; cec36000 <___strtok+e9637cc/1062382c>
 >>edx; cec37f7c <___strtok+e965748/1062382c>
 >>esi; c12f1f84 <___strtok+101f750/1062382c>
 >>ebp; c12f0000 <___strtok+101d7cc/1062382c>
 >>esp; c12f1f6c <___strtok+101f738/1062382c>
 
Trace; c01201ba <__run_task_queue+5a/140>
Trace; c01201ba <__run_task_queue+5a/140>
Trace; c0128df3 <schedule_task+1a3/230>
Trace; c0128cc0 <schedule_task+70/230>
Trace; c0105000 <empty_zero_page+1000/1380>
Trace; c01057ce <kernel_thread+2e/240>
Trace; c0128cc0 <schedule_task+70/230>
 
Code;  c01dca24 <__kfree_skb+f4/110>
00000000 <_EIP>:
Code;  c01dca24 <__kfree_skb+f4/110>   <=====
   0:   0f 0b                     ud2a      <=====
Code;  c01dca26 <__kfree_skb+f6/110>
   2:   3b 01                     cmp    (%ecx),%eax
Code;  c01dca28 <__kfree_skb+f8/110>
   4:   b1 38                     mov    $0x38,%cl
Code;  c01dca2a <__kfree_skb+fa/110>
   6:   24 c0                     and    $0xc0,%al
Code;  c01dca2c <__kfree_skb+fc/110>
   8:   8b 5c 24 14               mov    0x14(%esp,1),%ebx
Code;  c01dca30 <__kfree_skb+100/110>
   c:   e9 0e ff ff ff            jmp    ffffff1f <_EIP+0xffffff1f>
Code;  c01dca35 <__kfree_skb+105/110>
  11:   8d 74 26 00               lea    0x0(%esi,1),%esi

-- 
// -- http://www.BRAD-X.com/ -- //



  parent reply	other threads:[~2003-02-28 21:37 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-10 11:53 Cisco Aironet 340 oops with 2.4.20 Marc Giger
2003-02-13  0:18 ` Tim Pepper
2003-02-13  0:21   ` Jean Tourrilhes
2003-02-13  2:16     ` Tim Pepper
2003-02-13  2:18       ` Jean Tourrilhes
2003-02-13  6:47         ` Marc Giger
2003-02-13 17:20         ` Tim Pepper
2003-02-13  0:54   ` Tomas Szepe
2003-02-13  6:57     ` Marc Giger
2003-02-28 21:46 ` Brad Laue [this message]
2003-03-01 21:10   ` Marc Giger
2003-03-01 23:27     ` Brad Laue
2003-03-01 23:54       ` James Morris
2003-03-02  0:32         ` Brad Laue
2003-03-02 11:13           ` James Morris
2003-03-02 17:01             ` Brad Laue
2003-03-02 19:11               ` Marc Giger
2003-03-02 22:14               ` achirica
2003-03-12 13:54                 ` Marc Giger
2003-03-15  2:58                 ` Tim Pepper
2003-03-04  4:52   ` Tim Pepper
2003-03-01 17:14 ` airo.o + kfree_skb crash - 2.4.20 Brad Laue
  -- strict thread matches above, loose matches on Subject: below --
2003-03-15 18:11 Cisco Aironet 340 oops with 2.4.20 Thomas Hood
2003-03-17  0:33 ` Tim Pepper
2003-03-17  1:28   ` Javier Achirica
2003-03-17 14:29     ` Marc Giger
2003-03-18  1:46     ` Tim Pepper

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=3E5FD8A0.7070601@brad-x.com \
    --to=brad@brad-x.com \
    --cc=gigerstyle@gmx.ch \
    --cc=jt@hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stewart@snerk.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