Red Hat Bugzilla – Bug 146806
unknown opcodes and card state dumps
Last modified: 2015-01-04 17:16:29 EST
Description of problem:
machine has adaptec AIC-7861 and plexwriter 40/12/40S
running cdrecord causes all types of kernel messages. ultimately
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. cdrecord dev=/dev/scd0 -data burn.iso
unknown opcodes and card dump states...
scsi: unknown opcode 0xe9
scsi: unknown opcode 0xed
scsi: unknown opcode 0x01
scsi: unknown opcode 0xeb
able to burn
i'll attach more of the dmesg. I think this report belongs in kernel,
but I'm not quite sure... thanks
Created attachment 110513 [details]
ok, the scsi card is really a 2940A Ultra card. Sorry about that... so I tried
the aic7xxx_old driver and I still get unknown opcodes and a bunch of new type
of errors such as data overruns detected, BUT I can actually burn a cd now and
i guess this isn't so much an issue untill the _old driver goes away.
Created attachment 111143 [details]
cdrecord run that worked
Created attachment 111144 [details]
here's the real attachment DOH
sorry about that, here's the real log...
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which
may contain a fix for your problem. Please update to this new kernel, and
report whether or not it fixes your problem.
If you have updated to Fedora Core 4 since this bug was opened, and the problem
still occurs with the latest updates for that release, please change the version
field of this bug to 'fc4'.
fc4, 1398 kernel, aic7xxx, still fails in the same way as in comment #1. (A
firmware update to 1.05 of the cdrw didn't help.)
I get the following uknown opcode errors when burning with cdrecord on an ATAPI
Plexwriter 24/10/40A with kernel-2.6.12-1.1398_FC4. It's the same as reported
above, plus 0xF5.
kernel: scsi: unknown opcode 0xe9
kernel: scsi: unknown opcode 0xed
kernel: scsi: unknown opcode 0x01
kernel: scsi: unknown opcode 0xf5
kernel: scsi: unknown opcode 0xeb
The burn fails, and cdrecord hangs and can't be killed.
Mass update to all FC4 bugs:
An update has been released (2.6.13-1.1526_FC4) which rebases to a new upstream
kernel (22.214.171.124). As there were ~3500 changes upstream between this and the
previous kernel, it's possible your bug has been fixed already.
Please retest with this update, and update this bug if necessary.
still fails with 2.6.13-1.1526_FC4. I'll attach a new full dmesg log and an
Created attachment 119562 [details]
full dmesg log (2.6.13)
Created attachment 119563 [details]
I confirm that this has not been fixed by 2.6.13-1.1526_FC4.
2.6.14-1.1637_FC4 has been released as an update for FC4.
Please retest with this update, as a large amount of code has been changed in
this release, which may have fixed your problem.
Under 2.6.14-1.1637_FC4 the "unknown opcode" messages still appear in the log,
but I am able to burn a CD again.
Confirmed! Under 2.6.14-1.1637_FC4 I can burn cds again. My logs are very clean
too... no "unknown opcode" messages showed up for my setup.
This is a mass-update to all currently open kernel bugs.
A new kernel update has been released (Version: 2.6.15-1.1830_FC4)
based upon a new upstream kernel release.
Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.
This bug has been placed in NEEDINFO_REPORTER state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.
Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.
If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.
Unfortunately, I no longer have the hardware to test the cd writing under
2.6.15. In case you missed my note in #15, it worked fine under