From: Dave Jones <davej@redhat.com>
To: linux-scsi@vger.kernel.org
Subject: Attempting to use SCSI tape drive triggers kernel BUG
Date: Thu, 2 Mar 2006 00:08:52 -0500 [thread overview]
Message-ID: <20060302050852.GA1034@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 85 bytes --]
This has been around for a while, and is still there with latest
rc5-git's.
Dave
[-- Attachment #2: Type: message/rfc822, Size: 6353 bytes --]
From: bugzilla@redhat.com
To: davej@redhat.com
Subject: [Bug 180389] Attempting to use SCSI tape drive triggers kernel BUG
Date: Tue, 28 Feb 2006 12:53:00 -0500
Message-ID: <200602281753.k1SHr0UF020840@www.beta.redhat.com>
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.
Summary: Attempting to use SCSI tape drive triggers kernel BUG
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=180389
fenlason@redhat.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO_REPORTER |ASSIGNED
Status|NEEDINFO_REPORTER |ASSIGNED
------- Additional Comments From fenlason@redhat.com 2006-02-28 12:52 EST -------
2.6.15-1.1991_FC5smp still fails
st0: Block limits 2 - 16777215 bytes.
kfree_debugcheck: out of range ptr fffffffch.
------------[ cut here ]------------
kernel BUG at mm/slab.c:2490!
invalid opcode: 0000 [#1]
SMP
last sysfs file: /block/sda/sda1/size
Modules linked in: nfsd exportfs lockd nfs_acl ipv6 ppdev autofs4 rfcomm l2cap
b
luetooth sunrpc lp parport_pc parport floppy nvram uhci_hcd st sg snd_cmipci
gam
eport snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_pcm_oss
snd_mixer
_oss snd_pcm snd_page_alloc matroxfb_base snd_opl3_lib matroxfb_DAC1064
snd_time
r matroxfb_accel snd_hwdep matroxfb_Ti3026 snd_mpu401_uart matroxfb_g450
snd_raw
midi g450_pll snd_seq_device snd matroxfb_misc soundcore matrox_w1 wire e100
mii
i2c_piix4 i2c_core dm_snapshot dm_zero dm_mirror dm_mod ext3 jbd aic7xxx
scsi_t
ransport_spi sd_mod scsi_mod
CPU: 0
EIP: 0060:[<c015f311>] Not tainted VLI
EFLAGS: 00010086 (2.6.15-1.1991_FC5smp #1)
EIP is at kfree_debugcheck+0x20/0x51
eax: 00000031 ebx: 0003ffff ecx: d4018dfc edx: c0315f6d
esi: fffffffc edi: fffffffc ebp: 00000246 esp: d4018df8
ds: 007b es: 007b ss: 0068
Process amcheck (pid: 2568, threadinfo=d4018000 task=d46d03b0)
Stack: <0>c0315f6d fffffffc 00000000 dffdeb00 c015fa51 c0149d2e 00000000
dffdeb0
0
dffdcb70 00000246 c0161559 dfd6c9d0 c1770170 00000000 de613598 c0149d2e
d463cea0 c1770170 d463cea0 c016822d 00000a00 00000000 c01680e8 e0842418
Call Trace:
[<c015fa51>] cache_free_debugcheck+0x1b/0x1b9 [<c0149d2e>]
mempool_free+0x5
f/0x63
[<c0161559>] kmem_cache_free+0x2a/0x5c [<c0149d2e>]
mempool_free+0x5f/0x63
[<c016822d>] bio_free+0x25/0x30 [<c01680e8>] bio_put+0x28/0x29
[<e0842418>] scsi_execute_async+0x13f/0x317 [scsi_mod] [<e0a38677>]
st_do_s
csi+0x1d3/0x228 [st]
[<e0a3a4f9>] st_sleep_done+0x0/0x3a [st] [<e0a3c439>] st_read+0x2fb/0x78b
[
st]
[<e0a3c13e>] st_read+0x0/0x78b [st] [<c01641c9>] vfs_read+0x9f/0x13e
[<c0164615>] sys_read+0x3c/0x63 [<c0103d81>] syscall_call+0x7/0xb
Code: 26 0a cc 5e 31 c0 58 5b 5e 5f c3 56 53 89 c6 8d 98 00 00 00 40 c1 eb 0c
3b
1d 00 23 48 c0 72 15 50 68 6d 5f 31 c0 e8 16 48 fc ff <0f> 0b ba 09 cc 5e 31
c0
58 5a 6b c3 28 03 05 10 23 48 c0 8b 00
Continuing in 1 seconds.
<3>Debug: sleeping function called from invalid context at
include/linux/rwsem.
h:43
in_atomic():0, irqs_disabled():1
[<c0124881>] profile_task_exit+0x13/0x48 [<c01261a3>] do_exit+0x1c/0x6fc
[<c010526c>] register_die_notifier+0x0/0x2f [<c010584e>]
do_invalid_op+0x0/
0x9d
[<c01058df>] do_invalid_op+0x91/0x9d [<c015f311>]
kfree_debugcheck+0x20/0x5
1
[<c0123993>] vprintk+0x195/0x329 [<c0149d69>] mempool_alloc+0x37/0xd3
[<c0160050>] kmem_cache_alloc+0x7f/0x89 [<c0149d69>]
mempool_alloc+0x37/0xd
3
[<c0149d69>] mempool_alloc+0x37/0xd3 [<c01d2d5a>]
cfq_set_request+0x318/0x4
3a
[<c01048a7>] error_code+0x4f/0x54 [<c015f311>] kfree_debugcheck+0x20/0x51
[<c015fa51>] cache_free_debugcheck+0x1b/0x1b9 [<c0149d2e>]
mempool_free+0x5
f/0x63
[<c0161559>] kmem_cache_free+0x2a/0x5c [<c0149d2e>]
mempool_free+0x5f/0x63
[<c016822d>] bio_free+0x25/0x30 [<c01680e8>] bio_put+0x28/0x29
[<e0842418>] scsi_execute_async+0x13f/0x317 [scsi_mod] [<e0a38677>]
st_do_s
csi+0x1d3/0x228 [st]
[<e0a3a4f9>] st_sleep_done+0x0/0x3a [st] [<e0a3c439>] st_read+0x2fb/0x78b
[
st]
[<e0a3c13e>] st_read+0x0/0x78b [st] [<c01641c9>] vfs_read+0x9f/0x13e
[<c0164615>] sys_read+0x3c/0x63 [<c0103d81>] syscall_call+0x7/0xb
--
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
reply other threads:[~2006-03-02 5:08 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=20060302050852.GA1034@redhat.com \
--to=davej@redhat.com \
--cc=linux-scsi@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.