Bug 156709
Summary: | ide ppc: packet command error; opcode unknown; CD-R | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | John Reiser <jreiser> |
Component: | kernel | Assignee: | Dave Jones <davej> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | bjohnson, byte, davej, dwmw2, pfrields, triage, wtogami, zing |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | powerpc | ||
OS: | Linux | ||
Whiteboard: | bzcl34nup | ||
Fixed In Version: | 2.6.24.4-64.fc8.ppc | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-04-05 03:03:05 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
John Reiser
2005-05-03 15:14:36 UTC
Alan, 1282 was the first kernel where we included your recent ide fixes. Ok this looks like its just logging more than perhaps the user actually cares about. I will double check. Looking at the report this changed before new IDE since it changed at 2.6.11-1.1275 not 2.6.11-1.1282. What IDE or PPC changes went in then I wonder, because power management whacking for ppc might be a good candidate. Adding another Dave in case its a PPC not an IDE triggered change here Hmmm. Nothing obvious here... $ cvs diff -r1.1268 -r1.1275 kernel-2.6.spec | grep -A20 changelog %changelog +* Wed Apr 27 2005 Dave Jones <davej> +- Hopefully fix the random reboots some folks saw on x86-64. + +* Wed Apr 27 2005 Jeremy Katz <katzj> +- fix prereqs for -devel packages + +* Wed Apr 27 2005 Rik van Riel <riel> +- Fix up the vdso stuff so kernel-xen* compile again +- Import upstream bugfix so xenU domains can be started again + * Tue Apr 26 2005 Dave Jones <davej> +- Fix up the vdso again, which broke on the last rebase to -rc3 - Fix the put_user() fix. (#155999) * Mon Apr 25 2005 Dave Jones <davej> Do the messages appear on the console or just in the log ? They appear only in /var/log/messages, and not on the text console. I was perusing the log as a general survey for a testing release: "Let's see what is under this rock." Mass update of -test bugs to update version to fc4. (Please retest on final release, and report results if you have not already done so). Thanks. The same symptoms still appear when booting FC4 final release kernel-2.6.11-1.1369_FC4 on Mac mini (PowerPC32). [This comment has been added as a mass update for all FC4 kernel bugs. If you have migrated this bug from an FC3 bug today, ignore this comment.] Please retest your problem with todays 2.6.12-1.1398_FC4 update. If your problem involved being unable to boot, or some hardware not being detected correctly, please make sure your /etc/modprobe.conf is correct *BEFORE* installing any kernel updates. If in doubt, you can recreate this file using.. mv /etc/sysconfig/hwconf /etc/sysconfig/hwconf.bak mv /etc/modprobe.conf /etc/modprobe.conf.bak kudzu Thank you. The same lines still appear in /var/log/messages under kernel-2.6.12-1.1398_FC4 on ppc32 (Apple Macintosh mini with Matsushita CD-RW). Still looks correct to me - some application is issuing commands the drive does not support so it rejects them. Mass update to all FC4 bugs: An update has been released (2.6.13-1.1526_FC4) which rebases to a new upstream kernel (2.6.13.2). 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. Thanks. Using kernel-2.6.13-1.1526_FC4 and booting directly into single user mode, the same messages appear in output from dmesg, with a new message line "cdrom: open failed" following each "ide: failed opcode was: unknown". 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. Thank you. kernel-2.6.14-1.1637_FC4 still gives the same complaints about hdb: packet command error status=0x51 error=0x54 LastFailedSense=0x05. The messages appear in /var/log/messages and not on the text console. This is PowerPC-32 Apple Mac mini. 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. Thank you. kernel-2.6.15-1.1884_FC5 still gives the same complaints about hdb: packet command error status=0x51 error=0x54 LastFailedSense=0x05. The messages appear in /var/log/messages and not on the text console. This is PowerPC-32 Apple Mac mini. [The FC4 install was wiped, then FC5test1 was installed, then FC5test1 was wiped, then FC5test2 was installed and updated via yum. Changing Version to fc5test2.] Something like this also happens on x86_64. I'm getting these messages from the cdrom drive - hdc - both on the console and syslog on amd64: Mar 4 07:05:25 amd64-3000 kernel: hdc: media error (bad sector): status=0x51 { DriveReady SeekComplete Error } Mar 4 07:05:25 amd64-3000 kernel: hdc: media error (bad sector): error=0x30 { LastFailedSense=0x03 } Mar 4 07:05:25 amd64-3000 kernel: end_request: I/O error, dev hdc, sector 64 Mar 4 07:05:25 amd64-3000 kernel: Buffer I/O error on device hdc, logical block 8 Linux amd64-3000 2.6.15-1.2009.4.2_FC5 As far as I can tell, the drive reads and burns just fine. I've been having a similar problem on an AMD Athlon i386 system. Log Message: kernel: hda: dma_intr: status=0x51 {DriveReady SeekComplete Error} kernel: hda: dma_intr: error=0x84 {DriveStatusError BadCRC} kernel: ide: failed opcode was: unknown This message has repeated itself at varying time intervals, ranging from minutes to hours in the log. I have changed cables, measured cables, 40 wire, 80 wire, nothing has made a real difference. I have tried FC 5 and subsequent kernel updates. I haven't done anything to the kernels, thought I had it fixed when I connected to what would be the normal slave of the cable, but it just took an hour that time. I have tried hdparm -AkS and plan to try more, but these were unknown by default when I did hdparm -I. FIC SD11 MOBO Via82C686a chipset Maxtor 4D040H2 (40 GB 5400 66mhz) udma4, which the MOBO says it supports. I know there are bugs with via and maxtor but should be fixed in bios on my board. umaskirq=1 drive status is: active/idle, just wonder if these could be significant. Everything seems to work fine, accept I build up very large log files over time, and it just seems like there should be a fix. PS: Just since the last reboot, message after 1 min, then 20 min. then 5 min., I just don't get the variable time intervals? I've wondered if this could be something with the system clock, I've never tried overclocking, but this is a pretty old system, just had to change the cmos battery? A new kernel update has been released (Version: 2.6.18-1.2200.fc5) 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 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. In the last few updates, some users upgrading from FC4->FC5 have reported that installing a kernel update has left their systems unbootable. If you have been affected by this problem please check you only have one version of device-mapper & lvm2 installed. See bug 207474 for further details. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. If this bug has been fixed, but you are now experiencing a different problem, please file a separate bug for the new problem. Thank you. The problem was last observed booting kernel-2.6.18-1.2726.fc6 yesterday Oct.16. The problem has not been observed with kernel-2.6.18-1.2784.fc6 today Oct.17, but neither do I see it when going back to 2726 today; sigh. Hardware is PowerPC Apple Macintosh mini. Administrivia: "needinfo?" flag was still set; trying to clear it. Based on the date this bug was created, it appears to have been reported against rawhide during the development of a Fedora release that is no longer maintained. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained. If this bug remains in NEEDINFO thirty (30) days from now, we will automatically close it. If you can reproduce this bug in a maintained Fedora version (7, 8, or rawhide), please change this bug to the respective version and change the status to ASSIGNED. (If you're unable to change the bug's version or status, add a comment to the bug and someone will change it for you.) Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we're following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. The problem has disappeared; I no longer see the message in /var/log/messages. |