From: Juan Pedro Paredes <juampe@iquis.com>
To: kernel <linux-kernel@vger.kernel.org>
Subject: [BUG 2.6.0-test1]: workqueue & airo
Date: Fri, 18 Jul 2003 17:46:36 +0200 [thread overview]
Message-ID: <3F18165C.6000900@iquis.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 69 bytes --]
When I try to use my aironet 350 pcmcia card:
kernel bug or gcc bug?
[-- Attachment #2: workqueue --]
[-- Type: text/plain, Size: 2009 bytes --]
Fri Jul 18 16:33:10 CEST 2003
airo: Probing for PCI adapters
airo: Finished probing for PCI adapters
airo: MAC enabled eth1 0:7:eb:31:1:e6
eth1: index 0x05: Vcc 5.0, Vpp 5.0, irq 3, io 0x0100-0x013f
------------[ cut here ]------------
kernel BUG at kernel/workqueue.c:77!
invalid operand: 0000 [#1]
CPU: 0
EIP: 0060:[<c012f0bd>] Not tainted
EFLAGS: 00010213
EIP is at queue_work+0x6d/0x80
eax: 00000000 ebx: dcad037c ecx: dcad2bc8 edx: 00000000
esi: dcad2bcc edi: dffd0c20 ebp: dca3fce0 esp: dca3fcd4
ds: 007b es: 007b ss: 0068
Process ifconfig (pid: 424, threadinfo=dca3e000 task=dca2d9c0)
Stack: dcad037c dcad0220 00000000 dca3fd30 e097f85c c0339b81 df7479a0 00000001
00000000 dffb4e20 dca3fd24 c0348596 df7479a0 c03398b8 00000000 00000000
00000000 df7479a0 df2bd4c0 dca3fe2c dca3fd30 dcad0220 04000001 dca3fdbc
Call Trace:
[<e097f85c>] airo_read_mic+0x8c/0x90 [airo]
[<c0339b81>] __kfree_skb+0x81/0x110
[<c0348596>] netlink_broadcast+0x156/0x280
[<c03398b8>] alloc_skb+0x48/0xf0
[<e09800a0>] airo_interrupt+0x840/0x8e0 [airo]
[<e098099d>] issuecommand+0x6d/0x90 [airo]
[<c011e5c6>] scheduler_tick+0x116/0x300
[<c0128c76>] update_process_times+0x46/0x50
[<c0128ae6>] update_wall_time+0x16/0x40
[<c0128f00>] do_timer+0xe0/0xf0
[<c010d20b>] handle_IRQ_event+0x3b/0x70
[<c010d4fe>] do_IRQ+0x8e/0x120
[<c010ba7c>] common_interrupt+0x18/0x20
[<e098019e>] IN4500+0x1e/0x40 [airo]
[<e0980976>] issuecommand+0x46/0x90 [airo]
[<e098023c>] enable_MAC+0x7c/0xb0 [airo]
[<e097e660>] airo_open+0x50/0x80 [airo]
[<c037d3fc>] fib_inetaddr_event+0x4c/0x80
[<c033d74c>] dev_open+0x7c/0x90
[<c033ec68>] dev_change_flags+0x58/0x130
[<c0375d43>] devinet_ioctl+0x2a3/0x660
[<c03782c0>] inet_ioctl+0xc0/0x110
[<c0336834>] sock_ioctl+0xc4/0x270
[<c0165881>] sys_ioctl+0xb1/0x230
[<c010b10f>] syscall_call+0x7/0xb
Code: 0f 0b 4d 00 0b f5 3c c0 eb b2 89 f6 8d bc 27 00 00 00 00 55
<0>Kernel panic: Fatal exception in interrupt
In interrupt handler - not syncing
[-- Attachment #3: workqueue2 --]
[-- Type: text/plain, Size: 1144 bytes --]
00000000 <queue_work>:
0: 55 push %ebp
1: 89 d1 mov %edx,%ecx
3: 89 e5 mov %esp,%ebp
...
...
6c: c3 ret
6d: 0f 0b ud2a
6f: 4d dec %ebp
70: 00 00 add %al,(%eax)
72: 00 00 add %al,(%eax)
74: 00 eb add %ch,%bl
76: b2 89 mov $0x89,%dl
78: f6 8d bc 27 00 00 (bad) 0x27bc(%ebp)
...
What it's the meaning of bad (instruction)?
gcc -v
Reading specs from /usr/lib/gcc-lib/i386-linux/3.3.1/specs
Configured with: ../src/configure -v --enable-languages=c,c++,java,f77,pascal,objc,ada,treelang --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info
--with-gxx-include-dir=/usr/include/c++/3.3 --enable-shared --with-system-zlib --enable-nls --without-included-gettext --enable-__cxa_atexit --enable-clocale=gnu --enable-debug --enable-java-gc=boehm --enable-java-awt=xlib --enable-objc-gc
i386-linux
Thread model: posix
gcc version 3.3.1 20030626 (Debian prerelease)
reply other threads:[~2003-07-18 15:36 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=3F18165C.6000900@iquis.com \
--to=juampe@iquis.com \
--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 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.