From: Jens Axboe <axboe@suse.de>
To: linux-scsi@vger.kernel.org, mark_salyzyn@adaptec.com
Cc: markh@osdl.org, "Justin T. Gibbs" <gibbs@scsiguy.com>
Subject: Re: aacraid oopses on load
Date: Fri, 12 Mar 2004 12:36:55 +0100 [thread overview]
Message-ID: <20040312113655.GN6955@suse.de> (raw)
In-Reply-To: <20040312113104.GM6955@suse.de>
On Fri, Mar 12 2004, Jens Axboe wrote:
> Hi
>
> 2.6.3(-ish) oopses on load of aacraid:
>
> Oops: 0002 [#1]
> CPU: 0
> EIP: 0060:[<c01d2306>] Not tainted
> EFLAGS: 00010292
> EIP is at kobject_add+0x66/0x130
> eax: c0362840 ebx: e113a11c ecx: e1161e98 edx: e113a138
> esi: e113a120 edi: e113a104 ebp: c0362848 esp: dd497db0
> ds: 007b es: 007b ss: 0068
> Process modprobe (pid: 622, threadinfo=dd496000 task=dd28c080)
> Stack: e113a11c ffffffea e113a104 00000000 c01d2459 e113a11c c03627e0
> c0216b7f
> e113a11c e112b538 e113a0e0 00000000 e113a178 c032e258 c0217008
> 00000001
> 00000046 c03a3a00 00000001 c01db00b c032e268 00000000 c032e258
> e112855a
> Call Trace:
> [<c01d2459>] kobject_register+0x19/0x3f
> [<c0216b7f>] bus_add_driver+0x2f/0x80
> [<c0217008>] driver_register+0x28/0x30
> [<c01db00b>] pci_register_driver+0x4b/0x80
> [<e112855a>] ahc_linux_pci_init+0xa/0x990 [aic7xxx]
> [<e100a19c>] ahc_linux_init+0x19c/0x29b [aic7xxx]
> [<e110f000>] ahc_patch23_func+0x0/0x10 [aic7xxx]
> [<c012f105>] sys_init_module+0x105/0x15a0
> [<c0121120>] __request_region+0x0/0x80
> [<e100a000>] ahc_linux_init+0x0/0x29b [aic7xxx]
> [<c010e5ad>] do_mmap2+0x6d/0xa0
> [<c010e5cf>] do_mmap2+0x8f/0xa0
> [<c010e65d>] old_mmap+0x7d/0xa0
> [<c0108e17>] syscall_call+0x7/0xb
>
> Code: 89 11 8b 43 28 8b 30 8d 4e 48 89 c8 ba ff ff 00 00 0f c1 10
> <6>Red Hat/Adaptec aacraid driver (1.1.2-lk1 Mar 9 2004)
The oops is on aic7xxx of course, _not_ aacraid. Thanks Arjan for
correcting me.
--
Jens Axboe
prev parent reply other threads:[~2004-03-12 11:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-12 11:31 aacraid oopses on load Jens Axboe
2004-03-12 11:36 ` Jens Axboe [this message]
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=20040312113655.GN6955@suse.de \
--to=axboe@suse.de \
--cc=gibbs@scsiguy.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mark_salyzyn@adaptec.com \
--cc=markh@osdl.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