From: Dave Jones <davej@redhat.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: greg@kroah.com
Subject: 2.6.3rc4 compaq hotplug driver go bang on rmmod.
Date: Wed, 18 Feb 2004 02:59:38 +0000 [thread overview]
Message-ID: <20040218025938.GA26304@redhat.com> (raw)
I notice this driver has got its pci_driver remove: method commented out.
Greg, whats the thinking behind that? Surely we can do something
better than the current ...
Dave
cpqphp: Compaq Hot Plug PCI Controller Driver version: 0.9.7
eip: c010a286
------------[ cut here ]------------
kernel BUG at include/asm/spinlock.h:120!
invalid operand: 0000 [#1]
CPU: 0
EIP: 0060:[<c010a2d8>] Not tainted
EFLAGS: 00010082
EIP is at __down+0x52/0x165
eax: 0000000e ebx: c7a08bcc ecx: c02d2517 edx: 00000000
esi: 00000246 edi: c010a286 ebp: c2ccd2f0 esp: c2c8bf04
ds: 007b es: 007b ss: 0068
Process rmmod (pid: 1349, threadinfo=c2c8a000 task=c2ccd2f0)
Stack: c111acc0 c2c8bf20 c2c8bf58 00000000 c2ccd2f0 c01217e4 00000000 00000000
c01c7089 00010000 00000000 c7a08bcc 00000000 00000100 00000000 c010a624
c7a08bcc 00000077 00000000 c7a00a5d c7a08100 c79f996d c7a08100 00000000
Call Trace:
[<c01217e4>] default_wake_function+0x0/0xc
[<c01c7089>] task_has_capability+0x4c/0x54
[<c010a624>] __down_failed+0x8/0xc
[<c7a00a5d>] .text.lock.cpqphp_ctrl+0x119/0x148 [cpqphp]
[<c79f996d>] unload_cpqphpd+0x190/0x1b3 [cpqphp]
[<c7a02ccb>] cpqhpc_cleanup+0x1f/0x43 [cpqphp]
[<c013a805>] sys_delete_module+0x168/0x18a
[<c014ff4d>] unmap_vma_list+0xe/0x17
[<c01503f9>] do_munmap+0x17d/0x189
[<c010b697>] syscall_call+0x7/0xb
Code: 0f 0b 78 00 00 25 2d c0 f0 fe 4b 08 0f 88 96 03 00 00 83 4c
next reply other threads:[~2004-02-18 3:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-18 2:59 Dave Jones [this message]
2004-02-18 4:03 ` 2.6.3rc4 compaq hotplug driver go bang on rmmod Greg KH
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=20040218025938.GA26304@redhat.com \
--to=davej@redhat.com \
--cc=greg@kroah.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox