From: Bill Davidsen <davidsen@tmr.com>
To: Linux-Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [BUG] 2.5.38-mm2 aha152x module fails (fwd)
Date: Wed, 25 Sep 2002 09:15:43 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.3.96.1020925091353.23244K-300000@gatekeeper.tmr.com> (raw)
[-- Attachment #1: Type: TEXT/PLAIN, Size: 509 bytes --]
Subject: [BUG] 2.5.38-mm2 aha152x module fails
From: root <root@oddball-en.prodigy.com>
Date: Tue, 24 Sep 2002 18:12:05 -0400 (EDT)
To: davidsen@tmr-02.dsl.thebiz.net
I attempted to start my SCSI controller, and got a failure (attach 1),
followed by an oops retrying (att 2).
The comment on addressing is bogus, addresses are set by jumper and are
correct, and work on 2.4.19-ck7.
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
[-- Attachment #2: module probe --]
[-- Type: TEXT/PLAIN, Size: 686 bytes --]
Script started on Tue Sep 24 18:06:21 2002
profile 1.19 1998-07-03 17:42:50-04 mod/noRCS
No common directory available
Session time 18:06:21 on 09/24/02
oddball:root> modprobe aha152x aha152x=0x340,11,7,1,1,1
/lib/modules/2.5.38-mm2-1/kernel/drivers/scsi/aha152x.o: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters
/lib/modules/2.5.38-mm2-1/kernel/drivers/scsi/aha152x.o: insmod /lib/modules/2.5.38-mm2-1/kernel/drivers/scsi/aha152x.o failed
/lib/modules/2.5.38-mm2-1/kernel/drivers/scsi/aha152x.o: insmod aha152x failed
oddball:root> exit
Script done on Tue Sep 24 18:07:15 2002
[-- Attachment #3: ksymoops output --]
[-- Type: TEXT/PLAIN, Size: 2584 bytes --]
ksymoops 2.4.4 on i686 2.5.38-mm2-1. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.5.38-mm2-1/ (default)
-m /boot/System.map-2.5.38-mm2-1 (default)
Sep 24 17:57:57 oddball kernel: kernel BUG at slab.c:861!
Sep 24 17:57:57 oddball kernel: invalid operand: 0000
Sep 24 17:57:57 oddball kernel: CPU: 0
Sep 24 17:57:57 oddball kernel: EIP: 0060:[<c012c34a>] Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
Sep 24 17:57:57 oddball kernel: EFLAGS: 00010202
Sep 24 17:57:57 oddball kernel: eax: c02a3fa0 ebx: c41a0540 ecx: c036c23c edx: c6847bb7
Sep 24 17:57:57 oddball kernel: esi: c6847bc0 edi: c6847bc0 ebp: c41a03b8 esp: c28b3edc
Sep 24 17:57:57 oddball kernel: ds: 0068 es: 0068 ss: 0068
Sep 24 17:57:57 oddball kernel: Stack: c28b3ee4 c0000000 00000060 00000000 00000004 00000000 080b9930 c683a4a1
Sep 24 17:57:57 oddball kernel: c6847bb7 00000080 00000020 00002000 00000000 00000000 ffffffff 00000c68
Sep 24 17:57:57 oddball kernel: c6838000 00000000 c6838000 00000000 c0115d15 00000000 c28cf000 000129e0
Sep 24 17:57:57 oddball kernel: Call Trace: [<c683a4a1>] [<c6847bb7>] [<c0115d15>] [<c6838060>] [<c0108d2f>]
Sep 24 17:57:57 oddball kernel: Code: 0f 0b 5d 03 42 48 2a c0 8b 6d 00 81 fd 58 ad 2e c0 75 93 8b
>>EIP; c012c34a <kmem_cache_create+31a/380> <=====
Trace; c683a4a1 <[scsi_mod]init_scsi+41/150>
Trace; c6847bb7 <[scsi_mod].rodata.end+6cc8/c9b1>
Trace; c0115d15 <sys_init_module+535/620>
Trace; c6838060 <[scsi_mod]__kstrtab_scsi_unregister_host+0/0>
Trace; c0108d2f <syscall_call+7/b>
Code; c012c34a <kmem_cache_create+31a/380>
00000000 <_EIP>:
Code; c012c34a <kmem_cache_create+31a/380> <=====
0: 0f 0b ud2a <=====
Code; c012c34c <kmem_cache_create+31c/380>
2: 5d pop %ebp
Code; c012c34d <kmem_cache_create+31d/380>
3: 03 42 48 add 0x48(%edx),%eax
Code; c012c350 <kmem_cache_create+320/380>
6: 2a c0 sub %al,%al
Code; c012c352 <kmem_cache_create+322/380>
8: 8b 6d 00 mov 0x0(%ebp),%ebp
Code; c012c355 <kmem_cache_create+325/380>
b: 81 fd 58 ad 2e c0 cmp $0xc02ead58,%ebp
Code; c012c35b <kmem_cache_create+32b/380>
11: 75 93 jne ffffffa6 <_EIP+0xffffffa6> c012c2f0 <kmem_cache_create+2c0/380>
Code; c012c35d <kmem_cache_create+32d/380>
13: 8b 00 mov (%eax),%eax
reply other threads:[~2002-09-25 13:17 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=Pine.LNX.3.96.1020925091353.23244K-300000@gatekeeper.tmr.com \
--to=davidsen@tmr.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;
as well as URLs for NNTP newsgroup(s).