| Summary: | System PANICS during RHEL5u5 install | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | PaulB <pbunyan> | ||||||
| Component: | kernel | Assignee: | David Milburn <dmilburn> | ||||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | Red Hat Kernel QE team <kernel-qe> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 5.5 | CC: | dmilburn, jarod, jburke, jfeeney, peterm, shiyer | ||||||
| Target Milestone: | rc | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2011-10-24 01:29:11 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
|
Description
PaulB
2011-01-25 18:19:41 UTC
Paul, is this reproducible? P. Prarit,
I can reproduce these errors on dell-per415-01 on an upstream kernel
hda: drive not ready for command
hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hda: possibly failed opcode: 0xa1
[root@dell-per415-01 ~]# uname -a
Linux dell-per415-01.lab.bos.redhat.com 2.6.37 #1 SMP Tue Feb 1 10:12:42 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
Created attachment 477411 [details]
per515_RHEL5u5_PANIC_Reproduced
(In reply to comment #3) > Prarit, > > I can reproduce these errors on dell-per415-01 on an upstream kernel > > hda: drive not ready for command > hda: status error: status=0x58 { DriveReady SeekComplete DataRequest } > hda: possibly failed opcode: 0xa1 > > > [root@dell-per415-01 ~]# uname -a > Linux dell-per415-01.lab.bos.redhat.com 2.6.37 #1 SMP Tue Feb 1 10:12:42 EST > 2011 x86_64 x86_64 x86_64 GNU/Linux David ... I wonder if this is the "running smartd on a non-smartd capable drive leads to a system panic" issue I've heard about? I'll try and grab a system to see what is going on... P. Prarit, You are correct, I stopped the smartd and no longer saw the dmesg output. [root@dell-per415-01 ~]# smartctl -i /dev/hda smartctl version 5.38 [x86_64-redhat-linux-gnu] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: ���������������������������������������� Serial Number: 10100405173221 ���� Firmware Version: �������� User Capacity: 2,199,023,255,040 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 1 ATA Standard is: Not recognized. Minor revision code: 0xffff Local Time is: Thu Feb 10 09:08:06 2011 EST SMART is only available in ATA Version 3 Revision 3 or greater. We will try to proceed in spite of this. SMART support is: Unavailable - Packet Interface Devices [this device: CD/DVD] don't support ATA SMART A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. Previously, I had noticed wierd status (BUSY_STAT | READY_STAT), and I had tried to increase the wait time, but still could reproduce. Thanks, David Also, to note, John mentioned in previous email this system had been certified with samsung sh-s162L, different drive so we didn't see the problem before. Looks like maybe spinlock issue in ide/ati driver. |