| Summary: | RIT1355423- Badness at fs/sysfs/dir.c:491 booting RHEL6 Snap13 on standalone P6 | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | IBM Bug Proxy <bugproxy> | ||||||||||
| Component: | kernel | Assignee: | Steve Best <sbest> | ||||||||||
| Status: | CLOSED NOTABUG | QA Contact: | Red Hat Kernel QE team <kernel-qe> | ||||||||||
| Severity: | urgent | Docs Contact: | |||||||||||
| Priority: | urgent | ||||||||||||
| Version: | 6.1 | CC: | arozansk, balkov, jkachuck | ||||||||||
| Target Milestone: | rc | ||||||||||||
| Target Release: | 6.1 | ||||||||||||
| Hardware: | ppc64 | ||||||||||||
| OS: | All | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2011-04-15 09:46:57 UTC | Type: | --- | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Bug Depends On: | |||||||||||||
| Bug Blocks: | 684385, 687961 | ||||||||||||
| Attachments: |
|
||||||||||||
|
Description
IBM Bug Proxy
2011-03-14 08:22:42 UTC
Created attachment 484093 [details]
sosreport
Created attachment 484095 [details]
dmesg output
Created attachment 484096 [details]
Boot log
with this filelineno: bug 584507 bug 619422 with this guiltyfunc: bug 590019 bug 604564 ------- Comment From tpnoonan.com 2011-03-15 15:44 EDT------- please consider as exception for rhel6.1 Created attachment 487128 [details]
Details on the system and disk drives.
------- Comment (attachment only) From hienn.com 2011-03-23 15:37 EDT-------
------- Comment From sbest.com 2011-03-24 09:44 EDT------- Hi Wayne, we could we use some of your scsi expertise. If I'm looking at the log correct drivers/scsi/ses.c sees 3 enclosures ses 0:4:18:0: Attached Enclosure device ses 0:6:18:0: Attached Enclosure device ses 0:8:0:0: Attached Enclosure device and when Hien physically looked at this system there was 1 enclosure with 8 disks. ideas on why ses.c thinks there are 3 enclosures? -Steve ------- Comment From wayneb.com 2011-03-24 15:00 EDT------- The first thing that needs to be done is to upgrade firmware. I've upgraded the firmware on the Cadet-X adapter. It was quite old. The first two enclosure devices are part of the internal Lahaina enclosure. The current firmware level is this: A1700DE2.0001 (04-18-2008) Bring up Code. It needs to be upgraded to A1700DE2.0008, but I need someone to verify the following: Microcode Update/Download directions from 0001 to 0008 ?? Make sure you do NOT have any cable attached to the back of Lahaina during this code update from 0001 to 0008. ( I am talking about the RED cable that goes from Lahaina to the back of the system ) Hien, could you verify that this cable is not attached? If it is, could you disconnect it so that I can do the upgrade? Also, would someone please post the HMC information for this system? ------- Comment From wayneb.com 2011-03-25 12:40 EDT------- (In reply to comment #44) > Hi Wayne, > > we could we use some of your scsi expertise. If I'm looking at the log correct > drivers/scsi/ses.c sees 3 enclosures > > ses 0:4:18:0: Attached Enclosure device > ses 0:6:18:0: Attached Enclosure device > ses 0:8:0:0: Attached Enclosure device > > and when Hien physically looked at this system there was 1 enclosure with 8 > disks. ideas on why ses.c thinks there are 3 enclosures? > > -Steve Steve, To answer your question, the three enclosure devices are expected and are part of the internal SAS architecture. http://ausgsa.ibm.com/~jschwarz/SAS%20Presentation/SAS%20on%20HV8%20&%20HV4.htm The SAS addressing for Lahaina shows the three ses devices. http://ausgsa.ibm.com/~jschwarz/SAS%20Presentation/SAS%20on%20HV8%20&%20HV4.htm#SAS_Addressing In this case 0:4:18:0 and 0:6:18:0 are the 1st and 2nd ses devices. 0:0:8:0 is the virtual ses device. closing upgrading the firmware fixed this issue |