From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:184.108.40.206) Gecko/20061108 Fedora/220.127.116.11-1.fc5 Firefox/18.104.22.168
Description of problem:
Tape drive becomes unusable after 5-10 minutes of playing with it. I found the
"kernel BUG at mm/slab.c:594!" error below. I think this bug is affecting more than tapes or scsi, as other people with other devices have mentioned
"kernel BUG at mm/slab.c:594!" I'll include references below.
This just started with the latest FC5 kernel (2.6.18-1.2239.fc5). Several Megariad machines I have also will not boot with the new kernel, but that might not be related.
Bug #217488 mentions a similer error message, but with a USB connection to a phone.
------------[ cut here ]------------
invalid opcode: 0000 [#2]
last sysfs file: /devices/pci0000:03/0000:03:08.1/host1/target1:0:6/1:0:6:0/vend
Modules linked in: ipv6 vmnet(U) vmmon(U) video sbs i2c_ec container button batt
ery asus_acpi ac lp parport_pc parport ohci_hcd floppy st sg serio_raw i2c_piix4
i2c_core cfi_probe gen_probe scb2_flash mtdcore e1000 chipreg map_funcs pcspkr
ide_cd cdrom dm_snapshot dm_zero dm_mirror dm_mod ext3 jbd aacraid aic7xxx scsi_
transport_spi sd_mod scsi_mod
EIP: 0060:[<c045d3ac>] Tainted: P VLI
EFLAGS: 00010206 (2.6.18-1.2239.fc5 #1)
EIP is at kmem_cache_free+0x29/0x62
eax: c001086c ebx: f7ffe860 ecx: f7ff5620 edx: c1800000
esi: f7ffcf40 edi: 00000000 ebp: f21e0124 esp: c8383e28
ds: 007b es: 007b ss: 0068
Process tar (pid: 1219, ti=c8383000 task=f3cde290 task.ti=c8383000)
Stack: f7ffe860 f7ffcf40 00000000 c0448c0e 00000000 def70620 f7ffcf40 def70620
c04653e6 00000800 00000000 c046510c f8843f74 00000800 00000000 00000006
c8383f5c da387660 00000800 00000000 00000002 c1065620 00002000 00000000
[<f8843f74>] scsi_execute_async+0x15a/0x32d [scsi_mod]
[<f8952c57>] st_do_scsi+0x1d1/0x221 [st]
[<f89565d8>] st_read+0x2ed/0x7a6 [st]
DWARF2 unwinder stuck at syscall_call+0x7/0xb
Leftover inexact backtrace:
Code: 5f c3 57 89 d7 8d 92 00 00 00 40 89 c1 c1 ea 0c c1 e2 05 03 15 70 53 79 c0
56 53 8b 02 f6 c4 40 74 03 8b 52 0c 8b 02 84 c0 78 08 <0f> 0b 52 02 e3 f8 61 c0
39 4a 18 74 08 0f 0b 99 0d e3 f8 61 c0
EIP: [<c045d3ac>] kmem_cache_free+0x29/0x62 SS:ESP 0068:c8383e28
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1) Be one of the few people affected by this bug ..
2) have (in my case) a LTO1 tape drive attached to Adaptec AHA-3960D / AIC-7899A U160/m (rev 01) scsi card on a Dell server (unsure which one at this time)
2) Boot to kernel 2.6.18-1.2239.fc5Adaptec AHA-3960D / AIC-7899A U160/m (rev 01)
3) play with tape drive (mt stat; tar blah blah; mt stat; etc..) for 5-10 minutes
Kernel error above prints to screen and tape stops responding
Normal tape operation
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.
If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we are following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
Fixed in upstream kernel 2.6.21. Sorry I didn't close this bug at that time.