From: Jens Axboe <axboe@suse.de>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: OOPS on module unload 2.5.47-mm1
Date: Wed, 13 Nov 2002 08:22:28 +0100 [thread overview]
Message-ID: <20021113072228.GD832@suse.de> (raw)
In-Reply-To: <200211122349.gACNneB27936@eng2.beaverton.ibm.com>
On Tue, Nov 12 2002, Badari Pulavarty wrote:
> Hi,
>
> I get following panic while rmmod qla driver. (2.5.47-mm1).
>
> Is this a known problem ? Any ideas ?
>
> Thanks,
> Badari
>
>
> Synchronizing SCSI cache:
> Synchronizing SCSI cache:
> Synchronizing SCSI cache:
> Synchronizing SCSI cache:
> Synchronizing SCSI cache:
> Synchronizing SCSI cache:
> Synchronizing SCSI cache:
> Synchronizing SCSI cache:
> Synchronizing SCSI cache:
> Synchronizing SCSI cache:
> Unable to handle kernel paging request at virtual address 5a5a5a5e
> printing eip:
> c025ea85
> *pde = 00000000
> Oops: 0002
> qla2200
> CPU: 0
> EIP: 0060:[<c025ea85>] Not tainted
> EFLAGS: 00010287
> EIP is at __blk_cleanup_queue+0x25/0x70
> eax: 5a5a5a5a ebx: d31c8c94 ecx: d23ab5ac edx: d31c8c94
> esi: 000001ab edi: d31c8c90 ebp: d302f000 esp: d2eebf28
> ds: 0068 es: 0068 ss: 0068
> Process rmmod (pid: 2708, threadinfo=d2eea000 task=d2e48180)
> Stack: 00000800 d2f60000 d31c8c2c c025eae7 d31c8c90 d31c8c00 f89424c0 c02960d9
> d31c8c2c d2f60000 00000006 c0295f22 d2f60000 d2a44000 c0295f10 c0295e2d
> d2f60000 00000006 d2eea000 00000000 c029694e f89424c0 c0295f10 f8915000
> Call Trace:
> [<c025eae7>] blk_cleanup_queue+0x17/0x60
> [<f89424c0>] driver_template+0x0/0x68 [qla2200]
> [<c02960d9>] scsi_remove_host+0x179/0x1b0
> [<c0295f22>] scsi_remove_legacy_host+0x12/0x50
> [<c0295f10>] scsi_remove_legacy_host+0x0/0x50
> [<c0295e2d>] scsi_tp_for_each_host+0x7d/0x110
> [<c029694e>] scsi_unregister_host+0x6e/0xf0
> [<f89424c0>] driver_template+0x0/0x68 [qla2200]
> [<c0295f10>] scsi_remove_legacy_host+0x0/0x50
> [<f8929aba>] exit_this_scsi_driver+0xa/0x10 [qla2200]
> [<f89424c0>] driver_template+0x0/0x68 [qla2200]
> [<c012081e>] free_module+0x1e/0x130
> [<c011faa4>] sys_delete_module+0x1b4/0x410
> [<c0109173>] syscall_call+0x7/0xb
>
> Code: 89 50 04 89 02 89 09 89 49 04 51 8b 0d 0c 43 5c c0 46 51 e8
Hmm, look as if the rq on the freelist has already been free'ed. But if
it had, it shouldn't be on the list. At least there's a small bug there,
the elevator_exit() needs to be before the __blk_cleanup_queue() calls
in blk_cleanup_queue().
Maybe try dumping blk_init_queue() and blk_cleanup_queue() calls to see
if they match up?
--
Jens Axboe
next prev parent reply other threads:[~2002-11-13 7:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-12 23:49 OOPS on module unload 2.5.47-mm1 Badari Pulavarty
2002-11-13 7:22 ` Jens Axboe [this message]
2002-11-13 17:37 ` Patrick Mansfield
2002-11-13 23:35 ` Badari Pulavarty
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=20021113072228.GD832@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@us.ibm.com \
/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